CVE-2026-98850: net/packet: prevent TX_RING byte count overflow
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 1e6ee93cea4b77253b1b81eb5759899f959ebee3, 2cf81fc9505b148b1b70068303ea6ea4b1212403, 4848c175b5984e6358bcca794ac1dee4d527efcc; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 1e6ee93cea4b77253b1b81eb5759899f959ebee3, 2cf81fc9505b148b1b70068303ea6ea4b1212403, 4848c175b5984e6358bcca794ac1dee4d527efcc; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.31affected
- 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 and later · before 1e6ee93cea4b77253b1b81eb5759899f959ebee3affected · git
- 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 and later · before 70fefff0801d4c5405e515592d1e7ad1351530cdaffected · git
- 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 and later · before 4848c175b5984e6358bcca794ac1dee4d527efccaffected · git
- 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 and later · before ae169d318d5d23bac76ece90a7e2b5cb760ed043affected · git
- 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 and later · before be12b221c0301111eeb023be04add3c6ad7c21feaffected · git
- 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 and later · before 69ca64bbb528898916f309552053c32a04a36ebcaffected · git
- 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 and later · before 9fd63d284e251332f4874ef9023cde472f315f86affected · git
- 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 and later · before 2cf81fc9505b148b1b70068303ea6ea4b1212403affected · git
- before 2.6.31not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98848Oct 18, 2026 · rtc: ac100: Assign .num before accessing .hws0Monitor
- ← EarlierCVE-2026-98849Oct 18, 2026 · pfcp: fix socket lifetime on netdevice registration failure0Monitor
- Later →CVE-2026-98851Oct 18, 2026 · netfilter: nft_flow_offload: drop flowtable reference on init error path0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1e6ee93cea4b77253b1b81eb5759899f959ebee3 | Vendor (CNA) |
| Linux Linux | 2cf81fc9505b148b1b70068303ea6ea4b1212403 | Vendor (CNA) |
| Linux Linux | 4848c175b5984e6358bcca794ac1dee4d527efcc | Vendor (CNA) |
| Linux Linux | 69ca64bbb528898916f309552053c32a04a36ebc | Vendor (CNA) |
| Linux Linux | 70fefff0801d4c5405e515592d1e7ad1351530cd | Vendor (CNA) |
| Linux Linux | 9fd63d284e251332f4874ef9023cde472f315f86 | Vendor (CNA) |
| Linux Linux | ae169d318d5d23bac76ece90a7e2b5cb760ed043 | Vendor (CNA) |
| Linux Linux | be12b221c0301111eeb023be04add3c6ad7c21fe | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 8, 2026+21 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2cf81fc9505b148b1b70068303ea6ea4b1212403
- git.kernel.org/stable/c/4848c175b5984e6358bcca794ac1dee4d527efcc
- git.kernel.org/stable/c/69ca64bbb528898916f309552053c32a04a36ebc
- git.kernel.org/stable/c/70fefff0801d4c5405e515592d1e7ad1351530cd
- git.kernel.org/stable/c/9fd63d284e251332f4874ef9023cde472f315f86
- git.kernel.org/stable/c/ae169d318d5d23bac76ece90a7e2b5cb760ed043
- git.kernel.org/stable/c/be12b221c0301111eeb023be04add3c6ad7c21fe
Vendor advisories and official records. Exploit/PoC links are deliberately left out.