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-98233net/packet: clear RX owner on VNET header error

Description

In the Linux kernel, the following vulnerability has been resolved: net/packet: clear RX owner on VNET header error Commit 61fad6816fc1 ("net/packet: tpacket_rcv: avoid a producer race condition") added rx_owner_map and made tpacket_rcv() claim a V1 or V2 ring slot before converting the virtio-net header. If the conversion fails, the drop path leaves the slot claimed. With a one-frame TPACKET_V2 ring, an unsupported UDP GSO packet leaves the only slot unavailable, so the ring also drops the next valid packet. Clear the ownership bit on this error path. TPACKET_V3 already clears its block state here.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 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.18% · 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 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 – < bb10a0084c03a94364aeec542beddc5d49b59f59
    • affected 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 – < b8c0cb3069058c2d67b5c7c833b2833381ecffdc
    • affected 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 – < 2daa618e7ff19eefcbda281bc4c5998c4140f9cf
    • affected 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 – < 23cd30498891d29a69ec9b75bd92f8a0f21f1342
    • affected 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 – < 49a48a5aaf85fe69d2dc3fb334b4854fadf44e39
    • affected 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 – < 805edbdcb8681da5f7ee43b3c3c809f7a8c31208
    • affected 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 – < 693209a237fc548791cf402441db8b68d1da7d38
    • affected 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 – < 33ff111d7ba3beb86e28938d6382bb5beabd865a
    • affected 2975472e042e0bbfeeabddc5023cb8c011ec5a07
    • affected 6fb0e4385928900ccb8697748555b3f54bba5193
    • affected 86137342fd4cf52882842aa8d1318b2661f08e8a
    • affected b06e4d3ed4044c2facf10a511d809f9aa29d960e
    • affected 4.14.175 – < 4.15
    • affected 4.19.114 – < 4.20
    • affected 5.4.29 – < 5.5
    • affected 5.5.14 – < 5.6
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .