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-98850net/packet: prevent TX_RING byte count overflow

Description

In the Linux kernel, the following vulnerability has been resolved: net/packet: prevent TX_RING byte count overflow tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size. After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel. Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call. A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 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.20% · top 90% of all CVEs (17 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 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 1e6ee93cea4b77253b1b81eb5759899f959ebee3
    • affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 70fefff0801d4c5405e515592d1e7ad1351530cd
    • affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 4848c175b5984e6358bcca794ac1dee4d527efcc
    • affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < ae169d318d5d23bac76ece90a7e2b5cb760ed043
    • affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < be12b221c0301111eeb023be04add3c6ad7c21fe
    • affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 69ca64bbb528898916f309552053c32a04a36ebc
    • affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 9fd63d284e251332f4874ef9023cde472f315f86
    • affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 2cf81fc9505b148b1b70068303ea6ea4b1212403
  • Linux · Linux

    • affected 2.6.31
    • unaffected < 2.6.31
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 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-98850 badge
[![CVE-2026-98850](https://cveledger.app/badge/CVE-2026-98850.svg)](https://cveledger.app/cve/CVE-2026-98850)

Record last updated .