CVE-2026-53091

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

net: pull headers in qdisc_pkt_len_segs_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d4f5c68f5ad4ab425f3ce1500c97c9f9743999a
generic

net: pull headers in qdisc_pkt_len_segs_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7fb4c19670110f052c04e1ec1d2b953b9f4f57e4

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 21× in last 7d / 76× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 285 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 07:52 UTCEG score recompute
  3. 2026-09-18 07:52 UTCVendor advisory
  4. 2026-09-18 07:52 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 13:38 UTCEG score recompute
  8. 2026-09-14 13:38 UTCVendor advisory
  9. 2026-09-14 13:38 UTCGHSA enrichment
  10. 2026-09-14 12:34 UTCEG score recompute
  11. 2026-09-14 12:34 UTCVendor advisory
  12. 2026-09-14 12:34 UTCGHSA enrichment
  13. 2026-09-14 01:38 UTCEG score recompute
  14. 2026-09-14 01:38 UTCVendor advisory
  15. 2026-09-14 01:38 UTCGHSA enrichment
  16. 2026-09-13 16:47 UTCEPSS rescore
  17. 2026-09-13 09:48 UTCVendor advisory
  18. 2026-09-13 09:48 UTCGHSA enrichment
  19. 2026-09-12 16:12 UTCEG score recompute
  20. 2026-09-12 16:12 UTCVendor advisory
  21. 2026-09-12 16:12 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-10 13:38 UTCEG score recompute
  24. 2026-09-10 13:38 UTCVendor advisory
  25. 2026-09-10 13:37 UTCGHSA enrichment
Show 75 more
  1. 2026-09-10 12:25 UTCEG score recompute
  2. 2026-09-10 12:25 UTCVendor advisory
  3. 2026-09-10 12:25 UTCGHSA enrichment
  4. 2026-09-10 09:35 UTCEPSS rescore
  5. 2026-09-09 13:39 UTCEG score recompute
  6. 2026-09-09 13:39 UTCVendor advisory
  7. 2026-09-09 13:39 UTCGHSA enrichment
  8. 2026-09-09 12:37 UTCEG score recompute
  9. 2026-09-09 12:37 UTCVendor advisory
  10. 2026-09-09 12:37 UTCGHSA enrichment
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-08-30 19:54 UTCEG score recompute
  18. 2026-08-30 19:54 UTCVendor advisory
  19. 2026-08-30 19:54 UTCGHSA enrichment
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-28 03:44 UTCEG score recompute
  24. 2026-08-28 03:44 UTCVendor advisory
  25. 2026-08-28 03:43 UTCGHSA enrichment
  26. 2026-08-27 14:25 UTCEPSS rescore
  27. 2026-08-26 14:46 UTCEPSS rescore
  28. 2026-08-25 01:44 UTCEG score recompute
  29. 2026-08-25 01:44 UTCVendor advisory
  30. 2026-08-25 01:43 UTCGHSA enrichment
  31. 2026-08-24 13:27 UTCEG score recompute
  32. 2026-08-24 13:27 UTCVendor advisory
  33. 2026-08-24 13:27 UTCGHSA enrichment
  34. 2026-08-24 00:26 UTCVendor advisory
  35. 2026-08-24 00:25 UTCGHSA enrichment
  36. 2026-08-23 12:08 UTCEG score recompute
  37. 2026-08-23 12:08 UTCVendor advisory
  38. 2026-08-23 12:08 UTCGHSA enrichment
  39. 2026-08-23 00:19 UTCEPSS rescore
  40. 2026-08-22 23:49 UTCVendor advisory
  41. 2026-08-22 23:49 UTCGHSA enrichment
  42. 2026-08-22 11:32 UTCEG score recompute
  43. 2026-08-22 11:32 UTCVendor advisory
  44. 2026-08-22 11:32 UTCGHSA enrichment
  45. 2026-08-21 23:49 UTCEPSS rescore
  46. 2026-08-21 20:10 UTCVendor advisory
  47. 2026-08-21 20:10 UTCGHSA enrichment
  48. 2026-08-21 07:53 UTCVendor advisory
  49. 2026-08-21 07:53 UTCGHSA enrichment
  50. 2026-08-20 19:36 UTCVendor advisory
  51. 2026-08-20 19:36 UTCGHSA enrichment
  52. 2026-08-20 07:19 UTCEG score recompute
  53. 2026-08-20 07:19 UTCVendor advisory
  54. 2026-08-20 07:19 UTCGHSA enrichment
  55. 2026-08-19 17:04 UTCEPSS rescore
  56. 2026-08-19 14:51 UTCVendor advisory
  57. 2026-08-19 14:50 UTCGHSA enrichment
  58. 2026-08-19 02:03 UTCEG score recompute
  59. 2026-08-19 02:03 UTCVendor advisory
  60. 2026-08-19 02:03 UTCGHSA enrichment
  61. 2026-08-18 13:48 UTCEPSS rescore
  62. 2026-08-17 13:47 UTCEPSS rescore
  63. 2026-08-17 10:03 UTCVendor advisory
  64. 2026-08-17 10:03 UTCGHSA enrichment
  65. 2026-08-16 21:47 UTCEG score recompute
  66. 2026-08-16 21:47 UTCVendor advisory
  67. 2026-08-16 21:47 UTCGHSA enrichment
  68. 2026-08-16 14:56 UTCEPSS rescore
  69. 2026-08-16 09:30 UTCEG score recompute
  70. 2026-08-16 09:30 UTCVendor advisory
  71. 2026-08-16 09:30 UTCGHSA enrichment
  72. 2026-08-16 02:14 UTCEPSS rescore
  73. 2026-08-15 21:14 UTCVendor advisory
  74. 2026-08-15 21:14 UTCGHSA enrichment
  75. 2026-08-15 08:57 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53091?
CVE-2026-53091 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: net: pull headers in qdiscpktlensegsinit() Most ndostartxmit() methods expects headers of gso packets to be already in skb->head. net/core/tso.c users are particularly at risk, because tsobuildhdr() does a memcpy(hdr, skb->data,…
When was CVE-2026-53091 disclosed?
CVE-2026-53091 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53091 actively exploited?
CVE-2026-53091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53091?
CVE-2026-53091 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-53091?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53091, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53091

Explore →

Is Your Infrastructure Affected by CVE-2026-53091?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.