Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High · fixed in 7564dc804d8289d2e5c6edb8173754051b71bff4 : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in 7564dc804d8289d2e5c6edb8173754051b71bff4, 5895cfc76924a629c6eaa5e5f049de642860045f, 9d4f5c68f5ad4ab425f3ce1500c97c9f9743999a +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to 7564dc804d8289d2e5c6edb8173754051b71bff4, 5895cfc76924a629c6eaa5e5f049de642860045f, 9d4f5c68f5ad4ab425f3ce1500c97c9f9743999a or 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e876f208af18b074f800656e4d1b99da75b2135f, < 7564dc804d8289d2e5c6edb8173754051b71bff4
Fixed in
  • 7564dc804d8289d2e5c6edb8173754051b71bff4
LinuxLinuxAffected
  • ≥ e876f208af18b074f800656e4d1b99da75b2135f, < 5895cfc76924a629c6eaa5e5f049de642860045f
Fixed in
  • 5895cfc76924a629c6eaa5e5f049de642860045f
LinuxLinuxAffected
  • ≥ e876f208af18b074f800656e4d1b99da75b2135f, < 9d4f5c68f5ad4ab425f3ce1500c97c9f9743999a
Fixed in
  • 9d4f5c68f5ad4ab425f3ce1500c97c9f9743999a
LinuxLinuxAffected
  • ≥ e876f208af18b074f800656e4d1b99da75b2135f, < 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4
Fixed in
  • 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4
LinuxLinuxAffected
  • =3.16
Fixed in–

Description

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.

References

Community reviews

Loading reviews…