Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53091: net: pull headers in qdisc_pkt_len_segs_init()

HighCVSS 8.4 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 33/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.13% (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 5895cfc76924a629c6eaa5e5f049de642860045f, 7564dc804d8289d2e5c6edb8173754051b71bff4, 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 5895cfc76924a629c6eaa5e5f049de642860045f, 7564dc804d8289d2e5c6edb8173754051b71bff4, 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.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: pull headers in qdisc_pkt_len_segs_init() Most ndo_start_xmit() methods expects headers of gso packets to be already in skb->head. net/core/tso.c users are particularly at risk, because tso_build_hdr() does a memcpy(hdr, skb->data, hdr_len); qdisc_pkt_len_segs_init() already does a dissection of gso packets. Use pskb_may_pull() instead of skb_header_pointer() to make sure drivers do not have to reimplement this. Some malicious packets could be fed, detect them so that we can drop them sooner with a new SKB_DROP_REASON_SKB_BAD_GSO drop_reason.

Published
Jun 24, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
33 / 40 · 8.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
8.4
NVD has not scored this yet; the score shown is the CNA’s.

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-2026-53091

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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

    • 3.16affected
    • e876f208af18b074f800656e4d1b99da75b2135f and later · before 5895cfc76924a629c6eaa5e5f049de642860045faffected · git
    • e876f208af18b074f800656e4d1b99da75b2135f and later · before 7564dc804d8289d2e5c6edb8173754051b71bff4affected · git
    • e876f208af18b074f800656e4d1b99da75b2135f and later · before 9d4f5c68f5ad4ab425f3ce1500c97c9f9743999aaffected · git
    • e876f208af18b074f800656e4d1b99da75b2135f and later · before 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4affected · git
    • before 3.16not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver
    • 6.12.114 and later · up to and including 6.12.*not affected · semver
    • 7.0.10 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Affected versions

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

  • linux linux kernel3.16 and later · before 7.0.10

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.53.1.el10_26.12.0-211.53.1.el10_2

+96

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-2026-53089Jun 24, 2026 · bpf: Fix use-after-free in offloaded map/prog info fill
    31Monitor
  • ← EarlierCVE-2026-53090Jun 24, 2026 · bpf: Fix ld_{abs,ind} failure path analysis in subprogs
    31Monitor
  • Later →CVE-2026-53092Jun 24, 2026 · bpf: Fix linked reg delta tracking when src_reg == dst_reg
    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 Linux5895cfc76924a629c6eaa5e5f049de642860045fVendor (CNA)
Linux Linux7564dc804d8289d2e5c6edb8173754051b71bff4Vendor (CNA)
Linux Linux7fb4c19670110f052c04e1ec1d2b953b9f4f57e4Vendor (CNA)
Linux Linux9d4f5c68f5ad4ab425f3ce1500c97c9f9743999aVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.53.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)
debian:linux7.0.10-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.115-2~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2Package 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.

Variant candidates

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

  • CVE-2026-3147863 days apartksmbd: replace hardcoded hdr2_len with offsetof() in smb2_calc_max_out_buf_len()
    39Monitor
  • CVE-2026-5336622 days apartipv4: account for fraggap on the paged allocation path
    31Monitor
  • CVE-2026-6403925 days apartdrm/msm/snapshot: fix dumping of the unaligned regions
    30Monitor
  • CVE-2026-4330247 days apartdrm/v3d: Set DMA segment size to avoid debug warnings
    22Monitor
  • CVE-2025-7128649 days apartASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls
    22Monitor
  • CVE-2026-4310749 days apartxfrm: account XFRMA_IF_ID in aevent size calculation
    22Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

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
high · data can be read
Integrity
none
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
None
Availability impact
High

CVSS vector

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

nvd-secondary

Attack context

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

References

All records