Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0b27828ebd1ed3107d7929c3737adbe862e99e74, 238e03d0466239410b72294b79494e43d4fabe77, 3264881431e308b9c72cb8a0159d57a56d67dd79; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 0b27828ebd1ed3107d7929c3737adbe862e99e74, 238e03d0466239410b72294b79494e43d4fabe77, 3264881431e308b9c72cb8a0159d57a56d67dd79; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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().

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jan 23, 2026
Updated
Oct 15, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-22979

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15.154 and later · before 5.16
  • linux linux kernel6.1.85 and later · before 6.1.161
  • linux linux kernel6.6.26 and later · before 6.6.121
  • linux linux kernel6.8.5 and later · before 6.9
  • linux linux kernel6.9.1 and later · before 6.12.66
  • linux linux kernel6.13 and later · before 6.18.6
  • linux linux kernel6.19
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • d225b0ac96dc40d7e8ae2bc227eb2c56e130975f, 5b3b67f731296027cceb3efad881ae281213f86f, 6.9affected
    • 2eeab8c47c3c0276e0746bc382f405c9a236a5ad and later · before 0b27828ebd1ed3107d7929c3737adbe862e99e74affected · git
    • fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6 and later · before 88bea149db2057112af3aaf63534b24fab5858abaffected · git
    • ed4cccef64c1d0d5b91e69f7a8a6697c3a865486 and later · before 3264881431e308b9c72cb8a0159d57a56d67dd79affected · git
    • ed4cccef64c1d0d5b91e69f7a8a6697c3a865486 and later · before c114a32a2e70b82d447f409f7ffcfa3058f9d5bdaffected · git
    • ed4cccef64c1d0d5b91e69f7a8a6697c3a865486 and later · before 238e03d0466239410b72294b79494e43d4fabe77affected · git
    • 6.1.85 and later · before 6.1.161affected · semver
    • 6.6.26 and later · before 6.6.121affected · semver
    • 5.15.154 and later · before 5.16affected · semver
    • 6.8.5 and later · before 6.9affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-develbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-corebefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-cross-headersbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-debugbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-debug-corebefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-debug-develbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-687.25.1.el9_85.14.0-687.25.1.el9_8

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-71154Jan 23, 2026 · net: usb: rtl8150: fix memory leak on usb_submit_urb() failure
    22Monitor
  • ← EarlierCVE-2025-71161Jan 23, 2026 · dm-verity: disable recursive forward error correction
    22Monitor
  • Later →CVE-2026-22980Jan 23, 2026 · nfsd: provide locking for v4_end_grace
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0b27828ebd1ed3107d7929c3737adbe862e99e74Vendor (CNA)
Linux Linux238e03d0466239410b72294b79494e43d4fabe77Vendor (CNA)
Linux Linux3264881431e308b9c72cb8a0159d57a56d67dd79Vendor (CNA)
Linux Linux5.16Vendor (CNA)
Linux Linux6.1.161Vendor (CNA)
Linux Linux6.6.121Vendor (CNA)
Linux Linux6.9Vendor (CNA)
Linux Linux88bea149db2057112af3aaf63534b24fab5858abVendor (CNA)
Linux Linuxc114a32a2e70b82d447f409f7ffcfa3058f9d5bdVendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.25.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.25.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.25.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.25.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.25.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.25.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.25.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+6

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records