Vulnerability · Published Sep 4, 2026 · Assigned by Linux

CVE-2026-80841net/packet: defer vmalloc TX_RING free until skbs finish

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 93.3% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-80841
Debian:13linux6.12.111-1DEBIAN-CVE-2026-80841
Debian:14linux7.1.13-1DEBIAN-CVE-2026-80841
Debian:12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-80841
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-80841
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-80841
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-80841
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-80841

Affected products (as reported)

VendorProductVersions
Linux Linux b013840810c221f2b0cf641d01531526052dc1fb – before ed126ca71d4d949ad99f40b974a8f7685e808f8bb013840810c221f2b0cf641d01531526052dc1fb – before debf9f50140b3df3949ebcb97d4450f8993fe32db013840810c221f2b0cf641d01531526052dc1fb – before 4ce6e2d2e38055b2012bd5fdb0c8a8183c8a1b0cb013840810c221f2b0cf641d01531526052dc1fb – before ed25ed29034ddc3dbe451ccbaa58ab9932f99d8bb013840810c221f2b0cf641d01531526052dc1fb – before 0189dce07db2dc059ae0570e06758ec4233c6e11b013840810c221f2b0cf641d01531526052dc1fb – before 550d00aa58193fb649a09a9c9e338c685adad784b013840810c221f2b0cf641d01531526052dc1fb – before 992cc9f94ca924089a506ba9b327caa9af797529
Linux Linux 3.14

References