CVE-2026-80925

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 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:

vlan: fix skb_under_panic and races when toggling HW VLAN offload

Toggling hardware VLAN TX offload (NETIF_F_HW_VLAN_CTAG_TX or NETIF_F_HW_VLAN_STAG_TX) on a lower device invokes vlan_transfer_features(), which dynamically changed vlandev->hard_header_len.

This causes two issues:

  • Lockless TX paths (e.g. packet_snd in af_packet.c, ip6_finish_output2)
read dev->hard_header_len without holding RTNL lock. Mutating hard_header_len dynamically under RTNL creates a data race where upper layers reserve insufficient headroom based on a stale hard_header_len, resulting in skb_under_panic when vlan_dev_hard_header() is called.
  • In addition, vlan_transfer_features() updated hard_header_len without
updating header_ops, causing a mismatch between allocated headroom and header creation.

Always setting dev->hard_header_len = real_dev->hard_header_len and dev->needed_headroom = real_dev->needed_headroom + VLAN_HLEN unconditionally ensures:

  • dev->hard_header_len remains 100% static and immutable at real_dev->hard_header_len,
eliminating all dynamic runtime updates and data races on hard_header_len.
  • Upper layers allocating skbs via LL_RESERVED_SPACE() will always reserve
sufficient headroom for software VLAN tag insertion (real_dev->hard_header_len + real_dev->needed_headroom + VLAN_HLEN).
  • vlandev inherits real_dev->needed_tailroom so underlying trailer/padding/ICV
requirements are honored.
  • AF_PACKET SOCK_RAW network header offsets remain correctly aligned at
real_dev->hard_header_len.
  • vlan_header_ops is used unconditionally.

Note to stable teams: Make sure to backport these commits:

e16e960d55a4 ("ipvlan: inherit needed_headroom and needed_tailroom from phy_dev") cef51860becd ("macvlan: inherit needed_headroom and needed_tailroom from lowerdev")

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 11, 2026

References (3)

Vendor Advisories for CVE-2026-80925(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 21× 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-09-19 14:24 UTCVendor advisory
  2. 2026-09-19 14:24 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-16 21:13 UTCVendor advisory
  5. 2026-09-16 21:13 UTCGHSA enrichment
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 03:35 UTCVendor advisory
  11. 2026-09-14 03:35 UTCGHSA enrichment
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 10:23 UTCGHSA enrichment
  15. 2026-09-11 10:21 UTCNVD update
  16. 2026-09-11 10:07 UTCEG score recompute
  17. 2026-09-11 10:06 UTCGHSA enrichment
  18. 2026-09-11 10:04 UTCMITRE cvelistV5
  19. 2026-09-09 17:27 UTCNVD update
  20. 2026-09-09 16:29 UTCEG score recompute
  21. 2026-09-09 16:25 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80925?
CVE-2026-80925 is a publicly disclosed vulnerability published on September 9, 2026. In the Linux kernel, the following vulnerability has been resolved: vlan: fix skbunderpanic and races when toggling HW VLAN offload Toggling hardware VLAN TX offload (NETIFFHWVLANCTAG_TX or NETIFFHWVLANSTAGTX) on a lower device invokes vlantransfer_features(), which dynamically changed…
When was CVE-2026-80925 disclosed?
CVE-2026-80925 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80925 actively exploited?
CVE-2026-80925 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 95.0% of all scored CVEs.
How do I remediate CVE-2026-80925?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80925, 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-80925

Explore →

Is Your Infrastructure Affected by CVE-2026-80925?

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

Start Free Scan →Browse All CVEs