Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 56 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b013840810c221f2b0cf641d01531526052dc1fb – < ed126ca71d4d949ad99f40b974a8f7685e808f8b
    • affected b013840810c221f2b0cf641d01531526052dc1fb – < debf9f50140b3df3949ebcb97d4450f8993fe32d
    • affected b013840810c221f2b0cf641d01531526052dc1fb – < 4ce6e2d2e38055b2012bd5fdb0c8a8183c8a1b0c
    • affected b013840810c221f2b0cf641d01531526052dc1fb – < ed25ed29034ddc3dbe451ccbaa58ab9932f99d8b
    • affected b013840810c221f2b0cf641d01531526052dc1fb – < 0189dce07db2dc059ae0570e06758ec4233c6e11
    • affected b013840810c221f2b0cf641d01531526052dc1fb – < 550d00aa58193fb649a09a9c9e338c685adad784
    • affected b013840810c221f2b0cf641d01531526052dc1fb – < 992cc9f94ca924089a506ba9b327caa9af797529
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.1.13 – ≤ 7.1.*
    • unaffected 7.2.3 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80841 badge
[![CVE-2026-80841](https://cveledger.app/badge/CVE-2026-80841.svg)](https://cveledger.app/cve/CVE-2026-80841)

Record last updated .