CVE-2026-98233: net/packet: clear RX owner on VNET header error
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 23cd30498891d29a69ec9b75bd92f8a0f21f1342, 2daa618e7ff19eefcbda281bc4c5998c4140f9cf, 33ff111d7ba3beb86e28938d6382bb5beabd865a; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 23cd30498891d29a69ec9b75bd92f8a0f21f1342, 2daa618e7ff19eefcbda281bc4c5998c4140f9cf, 33ff111d7ba3beb86e28938d6382bb5beabd865a; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: 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.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th 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.1%
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
- 2975472e042e0bbfeeabddc5023cb8c011ec5a07, 6fb0e4385928900ccb8697748555b3f54bba5193, 86137342fd4cf52882842aa8d1318b2661f08e8a, b06e4d3ed4044c2facf10a511d809f9aa29d960e, 5.6affected
- 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 and later · before bb10a0084c03a94364aeec542beddc5d49b59f59affected · git
- 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 and later · before b8c0cb3069058c2d67b5c7c833b2833381ecffdcaffected · git
- 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 and later · before 2daa618e7ff19eefcbda281bc4c5998c4140f9cfaffected · git
- 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 and later · before 23cd30498891d29a69ec9b75bd92f8a0f21f1342affected · git
- 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 and later · before 49a48a5aaf85fe69d2dc3fb334b4854fadf44e39affected · git
- 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 and later · before 805edbdcb8681da5f7ee43b3c3c809f7a8c31208affected · git
- 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 and later · before 693209a237fc548791cf402441db8b68d1da7d38affected · git
- 61fad6816fc10fb8793a925d5c1256d1c3db0cd2 and later · before 33ff111d7ba3beb86e28938d6382bb5beabd865aaffected · git
- 4.14.175 and later · before 4.15affected · 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 | before 6.1.190-1 | 6.1.190-1 |
| 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.8-1 | 7.2.8-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-98231Oct 6, 2026 · xfrm: serialize state GC with device state flush0Monitor
- ← EarlierCVE-2026-98232Oct 6, 2026 · scsi: core: Validate MODE SENSE lengths in scsi_cdl_enable()0Monitor
- Later →CVE-2026-98234Oct 6, 2026 · net/sched: hhf: cap hh_flows_limit at change time0Monitor
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 | 23cd30498891d29a69ec9b75bd92f8a0f21f1342 | Vendor (CNA) |
| Linux Linux | 2daa618e7ff19eefcbda281bc4c5998c4140f9cf | Vendor (CNA) |
| Linux Linux | 33ff111d7ba3beb86e28938d6382bb5beabd865a | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 49a48a5aaf85fe69d2dc3fb334b4854fadf44e39 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5.6 | Vendor (CNA) |
| Linux Linux | 693209a237fc548791cf402441db8b68d1da7d38 | Vendor (CNA) |
| Linux Linux | 805edbdcb8681da5f7ee43b3c3c809f7a8c31208 | Vendor (CNA) |
| Linux Linux | b8c0cb3069058c2d67b5c7c833b2833381ecffdc | Vendor (CNA) |
| Linux Linux | bb10a0084c03a94364aeec542beddc5d49b59f59 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | 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
- TodayOct 27, 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/2daa618e7ff19eefcbda281bc4c5998c4140f9cf
- git.kernel.org/stable/c/33ff111d7ba3beb86e28938d6382bb5beabd865a
- git.kernel.org/stable/c/49a48a5aaf85fe69d2dc3fb334b4854fadf44e39
- git.kernel.org/stable/c/693209a237fc548791cf402441db8b68d1da7d38
- git.kernel.org/stable/c/805edbdcb8681da5f7ee43b3c3c809f7a8c31208
- git.kernel.org/stable/c/b8c0cb3069058c2d67b5c7c833b2833381ecffdc
- git.kernel.org/stable/c/bb10a0084c03a94364aeec542beddc5d49b59f59
Vendor advisories and official records. Exploit/PoC links are deliberately left out.