Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-22979— net: fix memory leak in skb_segment_list for GRO packets

EPSS 0.02% · P5
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-22979

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
net: fix memory leak in skb_segment_list for GRO packets
Source: NVD (National Vulnerability Database)
Vulnerability 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().
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于skb_segment_list存在内存泄漏,可能导致内存泄漏。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 2eeab8c47c3c0276e0746bc382f405c9a236a5ad ~ 0b27828ebd1ed3107d7929c3737adbe862e99e74 -
LinuxLinux 6.9 -

II. Public POCs for CVE-2026-22979

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-22979

登录查看更多情报信息。

Same Patch Batch · Linux · 2026-01-23 · 34 CVEs total

CVE-2026-229849.8 CRITICALlibceph: prevent potential out-of-bounds reads in handle_auth_done()
CVE-2026-229887.8 HIGHarp: do not assume dev_hard_header() does not change skb->head
CVE-2026-229807.8 HIGHnfsd: provide locking for v4_end_grace
CVE-2026-229927.5 HIGHlibceph: return the handler error from mon_handle_auth_done()
CVE-2026-229917.5 HIGHlibceph: make free_choose_arg_map() resilient to partial allocation
CVE-2026-229907.5 HIGHlibceph: replace overzealous BUG_ON in osdmap_apply_incremental()
CVE-2026-22993idpf: Fix RSS LUT NULL ptr issue after soft reset
CVE-2026-22989nfsd: check that server is running in unlock_filesystem
CVE-2026-22978wifi: avoid kernel-infoleak from struct iw_point
CVE-2026-22987net/sched: act_api: avoid dereferencing ERR_PTR in tcf_idrinfo_destroy
CVE-2026-22986gpiolib: fix race condition for gdev->srcu
CVE-2026-22985idpf: Fix RSS LUT NULL pointer crash on early ethtool operations
CVE-2026-22994bpf: Fix reference count leak in bpf_prog_test_run_xdp()
CVE-2026-22983net: do not write to msg_get_inq in callee
CVE-2026-22982net: mscc: ocelot: Fix crash when adding interface under a lag
CVE-2026-22981idpf: detach and close netdevs while handling a reset
CVE-2026-22995ublk: fix use-after-free in ublk_partition_scan_work
CVE-2025-71145usb: phy: isp1301: fix non-OF device reference imbalance
CVE-2025-71161dm-verity: disable recursive forward error correction
CVE-2025-71160netfilter: nf_tables: avoid chain re-validation if possible

Showing top 20 of 34 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2026-22979

No comments yet


Leave a comment