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 — 4 sources updated 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

July 23, 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

Vendor Advisories for CVE-2026-53091(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-07-26ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-07-26ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-07-26ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-26ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-26ubuntu

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.

Weakness Classification(1)

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

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 78× 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.

  1. 2026-07-27 06:10 UTCGHSA enrichment
  2. 2026-07-26 17:40 UTCEG score recompute
  3. 2026-07-26 17:40 UTCVendor advisory
  4. 2026-07-26 17:39 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 05:11 UTCEG score recompute
  7. 2026-07-26 05:11 UTCGHSA enrichment
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:19 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:25 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 02:29 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-17 00:49 UTCGHSA enrichment
  20. 2026-07-16 17:03 UTCEPSS rescore
  21. 2026-07-16 12:31 UTCGHSA enrichment
  22. 2026-07-16 00:15 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 11:58 UTCGHSA enrichment
Show 57 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 22:27 UTCGHSA enrichment
  4. 2026-07-14 10:10 UTCGHSA enrichment
  5. 2026-07-13 22:31 UTCEPSS rescore
  6. 2026-07-13 21:54 UTCGHSA enrichment
  7. 2026-07-13 09:36 UTCGHSA enrichment
  8. 2026-07-12 21:19 UTCGHSA enrichment
  9. 2026-07-12 08:41 UTCGHSA enrichment
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 20:23 UTCGHSA enrichment
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 08:06 UTCGHSA enrichment
  15. 2026-07-10 19:49 UTCGHSA enrichment
  16. 2026-07-10 07:32 UTCGHSA enrichment
  17. 2026-07-09 19:12 UTCGHSA enrichment
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 06:45 UTCGHSA enrichment
  21. 2026-07-08 18:28 UTCGHSA enrichment
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 06:11 UTCGHSA enrichment
  25. 2026-07-07 17:54 UTCGHSA enrichment
  26. 2026-07-07 13:46 UTCEPSS rescore
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 05:08 UTCGHSA enrichment
  29. 2026-07-06 16:50 UTCGHSA enrichment
  30. 2026-07-06 16:27 UTCEPSS rescore
  31. 2026-07-06 16:27 UTCEPSS rescore
  32. 2026-07-06 04:30 UTCGHSA enrichment
  33. 2026-07-05 15:59 UTCGHSA enrichment
  34. 2026-07-05 03:42 UTCGHSA enrichment
  35. 2026-07-04 15:19 UTCGHSA enrichment
  36. 2026-07-04 06:31 UTCEPSS rescore
  37. 2026-07-04 02:59 UTCGHSA enrichment
  38. 2026-07-03 14:31 UTCGHSA enrichment
  39. 2026-07-03 02:15 UTCGHSA enrichment
  40. 2026-07-02 13:57 UTCGHSA enrichment
  41. 2026-07-02 01:40 UTCGHSA enrichment
  42. 2026-07-01 15:07 UTCEPSS rescore
  43. 2026-07-01 13:23 UTCGHSA enrichment
  44. 2026-07-01 01:07 UTCEG score recompute▲ 8.40
  45. 2026-07-01 01:06 UTCGHSA enrichment
  46. 2026-06-30 23:22 UTCEPSS rescore
  47. 2026-06-29 14:06 UTCEPSS rescore
  48. 2026-06-29 14:06 UTCEPSS rescore
  49. 2026-06-28 14:07 UTCEPSS rescore
  50. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  51. 2026-06-28 04:56 UTCEPSS rescore
  52. 2026-06-28 04:56 UTCEPSS rescore
  53. 2026-06-27 21:39 UTCGHSA enrichment
  54. 2026-06-27 03:08 UTCEPSS rescore
  55. 2026-06-25 13:49 UTCEPSS rescore
  56. 2026-06-24 18:12 UTCEG score recompute
  57. 2026-06-24 18:03 UTCNVD updatefirst tracked

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 July 23, 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 97.1% 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs