CVE-2026-22979

Advisory lineage Upstream: 0 Downstream: 27
Analyzed
Published: 23 Jan 2026, 15:24
Last modified:14 Jul 2026, 12:45

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.12% LOW
0% probability +0.10%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

23 Jan 2026, 15:24
Published
Vulnerability first disclosed
14 Jul 2026, 12:45
Last Modified
Vulnerability information updated

Description

In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in skb_segment_list for GRO packets When skb_segment_list() is called during packet forwarding, it handles packets that were aggregated by the GRO engine. Historically, the segmentation logic in skb_segment_list assumes that individual segments are split from a parent SKB and may need to carry their own socket memory accounting. Accordingly, the code transfers truesize from the parent to the newly created segments. Prior to commit ed4cccef64c1 ("gro: fix ownership transfer"), this truesize subtraction in skb_segment_list() was valid because fragments still carry a reference to the original socket. However, commit ed4cccef64c1 ("gro: fix ownership transfer") changed this behavior by ensuring that fraglist entries are explicitly orphaned (skb->sk = NULL) to prevent illegal orphaning later in the stack. This change meant that the entire socket memory charge remained with the head SKB, but the corresponding accounting logic in skb_segment_list() was never updated. As a result, the current code unconditionally adds each fragment's truesize to delta_truesize and subtracts it from the parent SKB. Since the fragments are no longer charged to the socket, this subtraction results in an effective under-count of memory when the head is freed. This causes sk_wmem_alloc to remain non-zero, preventing socket destruction and leading to a persistent memory leak. The leak can be observed via KMEMLEAK when tearing down the networking environment: unreferenced object 0xffff8881e6eb9100 (size 2048): comm "ping", pid 6720, jiffies 4295492526 backtrace: kmem_cache_alloc_noprof+0x5c6/0x800 sk_prot_alloc+0x5b/0x220 sk_alloc+0x35/0xa00 inet6_create.part.0+0x303/0x10d0 __sock_create+0x248/0x640 __sys_socket+0x11b/0x1d0 Since skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST packets constructed by GRO, the truesize adjustment is removed. The call to skb_release_head_state() must be preserved. As documented in commit cf673ed0e057 ("net: fix fraglist segmentation reference count leak"), it is still required to correctly drop references to SKB extensions that may be overwritten during __copy_skb_header().

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.12%• Percentile: 2%

Techniques & Countermeasures

  • CWE-401•Missing Release of Memory after Effective Lifetime

    The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Systems

  • linux•linux

    ≥ 2eeab8c47c3c0276e0746bc382f405c9a236a5ad, < 0b27828ebd1ed3107d7929c3737adbe862e99e74 | ≥ fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6, < 88bea149db2057112af3aaf63534b24fab5858ab | ≥ ed4cccef64c1d0d5b91e69f7a8a6697c3a865486, < 3264881431e308b9c72cb8a0159d57a56d67dd79 | ≥ ed4cccef64c1d0d5b91e69f7a8a6697c3a865486, < c114a32a2e70b82d447f409f7ffcfa3058f9d5bd | ≥ ed4cccef64c1d0d5b91e69f7a8a6697c3a865486, < 238e03d0466239410b72294b79494e43d4fabe77 | d225b0ac96dc40d7e8ae2bc227eb2c56e130975f | 5b3b67f731296027cceb3efad881ae281213f86f | ≥ 6.1.85, < 6.1.161 | ≥ 6.6.26, < 6.6.121 | ≥ 5.15.154, < 5.16 | ≥ 6.8.5, < 6.9 | 6.9

  • linux•linux kernel

    ≥ 5.15.154, < 5.16 | ≥ 6.1.85, < 6.1.161 | ≥ 6.6.26, < 6.6.121 | ≥ 6.8.5, < 6.9 | ≥ 6.9.1, < 6.12.66 | ≥ 6.13, < 6.18.6 | 6.9 | 6.9:rc3 | 6.9:rc4 | 6.9:rc5 | 6.9:rc6 | 6.9:rc7 | 6.19:rc1 | 6.19:rc2 | 6.19:rc3 | 6.19:rc4

References (6)