CVE-2026-80925
vlan: fix skb_under_panic and races when toggling HW VLAN offload
Reported by linux · Published September 9, 2026
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: 1. 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. 2. 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")
EPSS 0.16% · 5.4th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.18-modules-extra-common | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| Linux | Linux | b38d7a4bc9c17e1d437696da25f9fbc286614d9d, 69f2fc6e761ee68a4c0c8e416ae88c573d4d7319, 2.6.12 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| Linux | Linux | 2.6.12, 0, 6.1.191 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| Linux | Linux | 7.3, 7.2.3, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| linux | linux_kernel | 2.6.12, 2.6.12, 2.6.12 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel-livepatch-6.18.51-120.162 | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | perf6.18 | 0 |
…and 7 more
Timeline
- Sep 9, 2026 Coalition ESS Score
- Sep 9, 2026 CVE Published
- Sep 10, 2026 EPSS Score (13 in total, the first dated here)
- Oct 30, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80925
vulnetix vdb fixes CVE-2026-80925
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80925/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart