CVE-2026-80841
net/packet: defer vmalloc TX_RING free until skbs finish
Reported by linux · Published September 4, 2026
In the Linux kernel, the following vulnerability has been resolved: net/packet: defer vmalloc TX_RING free until skbs finish AF_PACKET TX_RING skbs keep a raw pointer to their ring frame. The skb page references preserve page-backed ring blocks after pg_vec is freed, but they do not preserve a vmalloc mapping. tpacket_destruct_skb() currently drops the pending reference before writing the timestamp and TP_STATUS_AVAILABLE to the frame. Move the decrement after those stores. The smp_wmb() in __packet_set_status() orders the frame stores before the decrement. Also recheck pending TX frames under pg_vec_lock before non-closing ring replacement, so a racing send cannot add a pending skb between the initial check and the ring swap. Ring allocation can produce a mixture of page-backed and vmalloc-backed blocks. Allocate deferred-work storage during TX ring setup when the first vmalloc-backed block is encountered, and keep its pointer in the pg_vec allocation header. If allocation fails, return -ENOMEM from ring setup. On socket close, a non-NULL pointer identifies a vmalloc-backed vector without a scan. If TX skbs remain, defer the whole vector to system_long_wq. After pg_vec is detached, a late destructor can skip the pending decrement. Use socket write-memory accounting as the deferred lifetime gate instead: an skb remains charged through its final sock_wfree(), after all ring-frame accesses. The delayed work retains a socket reference and reschedules itself until no TX skbs remain. Move pending_refcnt release to packet_sock_destruct() so late skb destructors and deferred cleanup can safely use it after packet_release(). Page-backed teardown remains synchronous, and no lock is added to the TX completion hot path.
EPSS 0.17% · 6.8th 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 |
|---|---|---|
| python3-perf6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.111-136.204.amzn2023 |
| kernel6.18-tools-devel | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| perf6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| bpftool6.12 | Amazon Linux | 1:6.12.111-136.204.amzn2023 |
| kernel6.18-headers | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.12-modules-extra-common | Amazon Linux | 1:6.12.111-136.204.amzn2023 |
| kernel-livepatch-6.18.51-120.162 | Amazon Linux | 1:1.0-0.amzn2023 |
| python3-perf6.12 | Amazon Linux | 1:6.12.111-136.204.amzn2023 |
| kernel-livepatch-6.12.111-136.204 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel6.18-tools | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.12-tools-devel | Amazon Linux | 1:6.12.111-136.204.amzn2023 |
3 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | b013840810c221f2b0cf641d01531526052dc1fb, b013840810c221f2b0cf641d01531526052dc1fb, b013840810c221f2b0cf641d01531526052dc1fb |
| Linux | Linux | 3.14, 0, 6.1.191 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel-livepatch-6.18.51-120.162 | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel-livepatch-6.12.111-136.204 | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | kernel6.18 | 0 |
| Linux | Linux | 7.3, *, * |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
…and 7 more
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (14 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-80841
vulnetix vdb fixes CVE-2026-80841
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-80841/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart