CVE-2026-53091

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH 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 — 3 sources updated this week
8.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
EPSS
2.4%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 30, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 43× 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-07 05:08 UTCEG score recompute
  2. 2026-07-07 05:08 UTCGHSA enrichment
  3. 2026-07-06 16:50 UTCEG score recompute
  4. 2026-07-06 16:50 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 04:31 UTCEG score recompute
  8. 2026-07-06 04:30 UTCGHSA enrichment
  9. 2026-07-05 15:59 UTCEG score recompute
  10. 2026-07-05 15:59 UTCGHSA enrichment
  11. 2026-07-05 03:42 UTCEG score recompute
  12. 2026-07-05 03:42 UTCGHSA enrichment
  13. 2026-07-04 15:20 UTCEG score recompute
  14. 2026-07-04 15:19 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 02:59 UTCEG score recompute
  17. 2026-07-04 02:59 UTCGHSA enrichment
  18. 2026-07-03 14:32 UTCEG score recompute
  19. 2026-07-03 14:31 UTCGHSA enrichment
  20. 2026-07-03 02:15 UTCEG score recompute
  21. 2026-07-03 02:15 UTCGHSA enrichment
  22. 2026-07-02 13:57 UTCEG score recompute
  23. 2026-07-02 13:57 UTCGHSA enrichment
  24. 2026-07-02 01:40 UTCEG score recompute
  25. 2026-07-02 01:40 UTCGHSA enrichment
Show 18 more
  1. 2026-07-01 15:07 UTCEPSS rescore
  2. 2026-07-01 13:23 UTCEG score recompute
  3. 2026-07-01 13:23 UTCGHSA enrichment
  4. 2026-07-01 01:07 UTCEG score recompute▲ 8.40
  5. 2026-07-01 01:06 UTCGHSA enrichment
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-27 21:40 UTCEG score recompute
  14. 2026-06-27 21:39 UTCGHSA enrichment
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 18:12 UTCEG score recompute
  18. 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 June 30, 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 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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