Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49872: net: gso: fix panic on frag_list with mixed head alloc types

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.51% (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 0a9f56e525ea871d3950b90076912f5c7494f00f, 4.14.300, 4.19.267.
  • Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 0a9f56e525ea871d3950b90076912f5c7494f00f, 4.14.300, 4.19.267 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: gso: fix panic on frag_list with mixed head alloc types Since commit 3dcbdb134f32 ("net: gso: Fix skb_segment splat when splitting gso_size mangled skb having linear-headed frag_list"), it is allowed to change gso_size of a GRO packet. However, that commit assumes that "checking the first list_skb member suffices; i.e if either of the list_skb members have non head_frag head, then the first one has too". It turns out this assumption does not hold. We've seen BUG_ON being hit in skb_segment when skbs on the frag_list had differing head_frag with the vmxnet3 driver. This happens because __netdev_alloc_skb and __napi_alloc_skb can return a skb that is page backed or kmalloced depending on the requested size. As the result, the last small skb in the GRO packet can be kmalloced. There are three different locations where this can be fixed: (1) We could check head_frag in GRO and not allow GROing skbs with different head_frag. However, that would lead to performance regression on normal forward paths with unmodified gso_size, where !head_frag in the last packet is not a problem. (2) Set a flag in bpf_skb_net_grow and bpf_skb_net_shrink indicating that NETIF_F_SG is undesirable. That would need to eat a bit in sk_buff. Furthermore, that flag can be unset when all skbs on the frag_list are page backed. To retain good performance, bpf_skb_net_grow/shrink would have to walk the frag_list. (3) Walk the frag_list in skb_segment when determining whether NETIF_F_SG should be cleared. This of course slows things down. This patch implements (3). To limit the performance impact in skb_segment, the list is walked only for skbs with SKB_GSO_DODGY set that have gso_size changed. Normal paths thus will not hit it. We could check only the last skb but since we need to walk the whole list anyway, let's stay on the safe side.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 1, 2025
Updated
Aug 5, 2026
EPSS
0.5% · 43th percentile
CWE
—

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.5%

CNA vs NVD score

NVD
5.5
CNA · Linux
7.5
2.0 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-2022-49872

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 kernel4.9.194 and later · before 4.9.334
  • linux linux kernel4.14.145 and later · before 4.14.300
  • linux linux kernel4.19.74 and later · before 4.19.267
  • linux linux kernel5.2.16 and later · before 5.3
  • linux linux kernel5.3.1 and later · before 5.4.225
  • linux linux kernel5.5 and later · before 5.10.155
  • linux linux kernel5.11 and later · before 5.15.79
  • linux linux kernel5.16 and later · before 6.0.9
  • linux linux kernel5.3
  • linux linux kernel6.1

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

    • 92984818ff8cfd97311a5e0ac27f148a00df2b54, 5.3affected
    • 162a5a8c3aff15c449e6b38355cdf80ab4f77a5a and later · before 5876b7f249a1ecbbcc8e35072c3828d6526d1c3aaffected · git
    • 55fb612bef7fd237fb70068e2b6ff1cd1543a8ef and later · before 0a9f56e525ea871d3950b90076912f5c7494f00faffected · git
    • 821302dd0c51d29269ef73a595bdff294419e2cd and later · before bd5362e58721e4d0d1a37796593bd6e51536ce7aaffected · git
    • 3dcbdb134f329842a38f0e6797191b885ab00a00 and later · before 65ad047fd83502447269fda8fd26c99077a9af47affected · git
    • 3dcbdb134f329842a38f0e6797191b885ab00a00 and later · before 50868de7dc4e7f0fcadd6029f32bf4387c102ee6affected · git
    • 3dcbdb134f329842a38f0e6797191b885ab00a00 and later · before ad25a115f50800c6847e0d841c5c7992a9f7c1b3affected · git
    • 3dcbdb134f329842a38f0e6797191b885ab00a00 and later · before 598d9e30927b15731e83797fbd700ecf399f42ddaffected · git
    • 3dcbdb134f329842a38f0e6797191b885ab00a00 and later · before 9e4b7a99a03aefd37ba7bb1f022c8efab5019165affected · git
    • 4.9.194 and later · before 4.9.334affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.10-16.0.10-1

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-2022-49870May 1, 2025 · capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
    28Monitor
  • ← EarlierCVE-2022-49871May 1, 2025 · net: tun: Fix memory leaks of napi_get_frags
    22Monitor
  • Later →CVE-2022-49873May 1, 2025 · bpf: Fix wrong reg type conversion in release_reference()
    22Monitor

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 Linux0a9f56e525ea871d3950b90076912f5c7494f00fVendor (CNA)
Linux Linux4.14.300Vendor (CNA)
Linux Linux4.19.267Vendor (CNA)
Linux Linux4.9.334Vendor (CNA)
Linux Linux5.3Vendor (CNA)
Linux Linux50868de7dc4e7f0fcadd6029f32bf4387c102ee6Vendor (CNA)
Linux Linux5876b7f249a1ecbbcc8e35072c3828d6526d1c3aVendor (CNA)
Linux Linux598d9e30927b15731e83797fbd700ecf399f42ddVendor (CNA)
Linux Linux65ad047fd83502447269fda8fd26c99077a9af47Vendor (CNA)
Linux Linux9e4b7a99a03aefd37ba7bb1f022c8efab5019165Vendor (CNA)
Linux Linuxad25a115f50800c6847e0d841c5c7992a9f7c1b3Vendor (CNA)
Linux Linuxbd5362e58721e4d0d1a37796593bd6e51536ce7aVendor (CNA)
debian:linux6.0.10-1 · Debian:12Package registry (OSV)

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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)

—

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

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

All records