CVE-2026-98612: net: usb: catc: bound the RX packet length in catc_rx_done()
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.19% (FIRST EPSS).
- Fixed version: Linux Linux 21e206dd88b3de6e36bb607dec3797c59bc3007b, 2f87bbd5a7bf6ee79d598f7e22cf77810d29ae87, 3942557938f846e7481f6ccb2b41ccbdee61baa1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 21e206dd88b3de6e36bb607dec3797c59bc3007b, 2f87bbd5a7bf6ee79d598f7e22cf77810d29ae87, 3942557938f846e7481f6ccb2b41ccbdee61baa1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.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: usb: catc: bound the RX packet length in catc_rx_done() catc_rx_done() walks a multi-packet URB, reading a two-byte length from each packet header. Its bound, pkt_len > urb->actual_length, ignores the header offset and compares against the whole transfer rather than the bytes left from pkt_start, so a crafted packet header makes skb_copy_to_linear_data() read past the buffer. A length below ETH_HLEN is also accepted, including zero, and eth_type_trans() then reads a MAC header from the uninitialised tailroom of a shorter skb. The is_f5u011 branch takes its length straight from the transfer, so a zero-length URB reaches the same path. Track the bytes remaining from the current packet, and reject a header that does not fit, a length past what is left, and a length below an Ethernet header. A transfer shorter than an Ethernet header, including a zero-length one, previously became a runt skb passed to netif_rx() and counted as received; it is now counted in rx_length_errors and ends the walk.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 8th 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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3942557938f846e7481f6ccb2b41ccbdee61baa1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2f87bbd5a7bf6ee79d598f7e22cf77810d29ae87affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4cc0a8eb2f9336cfa3e4ac329bc5585ca970ced3affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 21e206dd88b3de6e36bb607dec3797c59bc3007baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 801e21cf7dd6bcee31db907625d5045f21c9c1d9affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before dd9c6f8f05170223edec2dac476606cd40d9acb7affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9d4be026bdff2c1da7b6c7e01c0a47f2df409e97affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9d565b6b72fe3f41fd43636e143072848105189faffected · git
- before 2.6.12not 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 | 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.9-1 | 7.2.9-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-98610Oct 18, 2026 · net/sched: sch_hfsc: bound the classify inner-filter walk with a drift budget0Monitor
- ← EarlierCVE-2026-98611Oct 18, 2026 · bpf: Check params size before reading reserved fields0Monitor
- Later →CVE-2026-98613Oct 18, 2026 · bpf: Bound ownership depth through local kptrs and graph roots0Monitor
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 | 21e206dd88b3de6e36bb607dec3797c59bc3007b | Vendor (CNA) |
| Linux Linux | 2f87bbd5a7bf6ee79d598f7e22cf77810d29ae87 | Vendor (CNA) |
| Linux Linux | 3942557938f846e7481f6ccb2b41ccbdee61baa1 | Vendor (CNA) |
| Linux Linux | 4cc0a8eb2f9336cfa3e4ac329bc5585ca970ced3 | Vendor (CNA) |
| Linux Linux | 801e21cf7dd6bcee31db907625d5045f21c9c1d9 | Vendor (CNA) |
| Linux Linux | 9d4be026bdff2c1da7b6c7e01c0a47f2df409e97 | Vendor (CNA) |
| Linux Linux | 9d565b6b72fe3f41fd43636e143072848105189f | Vendor (CNA) |
| Linux Linux | dd9c6f8f05170223edec2dac476606cd40d9acb7 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | 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 7, 2026+20 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
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/2f87bbd5a7bf6ee79d598f7e22cf77810d29ae87
- git.kernel.org/stable/c/3942557938f846e7481f6ccb2b41ccbdee61baa1
- git.kernel.org/stable/c/4cc0a8eb2f9336cfa3e4ac329bc5585ca970ced3
- git.kernel.org/stable/c/801e21cf7dd6bcee31db907625d5045f21c9c1d9
- git.kernel.org/stable/c/9d4be026bdff2c1da7b6c7e01c0a47f2df409e97
- git.kernel.org/stable/c/9d565b6b72fe3f41fd43636e143072848105189f
- git.kernel.org/stable/c/dd9c6f8f05170223edec2dac476606cd40d9acb7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.