{"id":"CVE-2026-98850","title":"net/packet: prevent TX_RING byte count overflow","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/packet: prevent TX_RING byte count overflow\n\ntpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds\neach valid packet length to the signed int len_sum.…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 < be12b221c0301111eeb023be04add3c6ad7c21fe","Linux >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 < 69ca64bbb528898916f309552053c32a04a36ebc","Linux >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 < 9fd63d284e251332f4874ef9023cde472f315f86","Linux >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 < 2cf81fc9505b148b1b70068303ea6ea4b1212403","Linux 2.6.31"],"published":"2026-10-18","updated":"2026-10-18","sourceUpdated":"2026-10-18T15:50:50.062Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-98850","references":[{"url":"https://git.kernel.org/stable/c/be12b221c0301111eeb023be04add3c6ad7c21fe"},{"url":"https://git.kernel.org/stable/c/69ca64bbb528898916f309552053c32a04a36ebc"},{"url":"https://git.kernel.org/stable/c/9fd63d284e251332f4874ef9023cde472f315f86"},{"url":"https://git.kernel.org/stable/c/2cf81fc9505b148b1b70068303ea6ea4b1212403"}],"tags":["cve.org"],"ingestedAt":"2026-10-18T16:47:32.464Z","slug":"CVE-2026-98850","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/packet: prevent TX_RING byte count overflow\n\ntpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds\neach valid packet length to the signed int len_sum. Userspace can\nrecycle completed frames concurrently, so a single blocking send call\nis not bounded by the ring size.\n\nAfter enough successful transmissions len_sum wraps into the negative\nrange. In particular, 65536 65535-byte frames followed by a 65007-byte\nframe produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats\nthat as an impossible return and triggers a BUG. On systems configured\nto panic on oops, a CAP_NET_RAW holder can panic the host kernel.\n\nStop before the next frame would make the byte count exceed INT_MAX.\nThe positive short count leaves that frame pending for a later send\ncall.\n\nA two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build\nof Linux 7.3-rc4. With this change, the same reproducer returned the\nexpected positive short count without an oops.\n\n## Affected\n\n- `Linux >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 < be12b221c0301111eeb023be04add3c6ad7c21fe`\n- `Linux >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 < 69ca64bbb528898916f309552053c32a04a36ebc`\n- `Linux >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 < 9fd63d284e251332f4874ef9023cde472f315f86`\n- `Linux >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 < 2cf81fc9505b148b1b70068303ea6ea4b1212403`\n- `Linux 2.6.31`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}