Answer in brief
CVE-2026-98850 records a Unknown severity vulnerability in net/packet: prevent TX_RING byte count overflow. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <be12b221c0301111eeb023be04add3c6ad7c21fe || >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <69ca64bbb528898916f309552053c32a04a36ebc || >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <9fd63d284e251332f4874ef9023cde472f315f86 || >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <2cf81fc9505b148b1b70068303ea6ea4b1212403 | be12b221c0301111eeb023be04add3c6ad7c21fe, 69ca64bbb528898916f309552053c32a04a36ebc, 9fd63d284e251332f4874ef9023cde472f315f86, 2cf81fc9505b148b1b70068303ea6ea4b1212403 |
| Linux/Linuxgeneric | 2.6.31 | Not reported |
| Linux/Linuxgeneric | >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <ae169d318d5d23bac76ece90a7e2b5cb760ed043 || >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <be12b221c0301111eeb023be04add3c6ad7c21fe || >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <69ca64bbb528898916f309552053c32a04a36ebc || >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <9fd63d284e251332f4874ef9023cde472f315f86 || >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <2cf81fc9505b148b1b70068303ea6ea4b1212403 | ae169d318d5d23bac76ece90a7e2b5cb760ed043, be12b221c0301111eeb023be04add3c6ad7c21fe, 69ca64bbb528898916f309552053c32a04a36ebc, 9fd63d284e251332f4874ef9023cde472f315f86, 2cf81fc9505b148b1b70068303ea6ea4b1212403 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.