CVE-2026-98612: Linux kernel · net: usb: catc: bound the RX packet length in catc_rx_done()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in dd9c6f8f05170223edec2dac476606cd40d9acb7 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in dd9c6f8f05170223edec2dac476606cd40d9acb7, 3942557938f846e7481f6ccb2b41ccbdee61baa1, 801e21cf7dd6bcee31db907625d5045f21c9c1d9 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
This vulnerability has been fixed in the Linux kernel. Users should update to a kernel version that includes the fix identified by the referenced commits. No additional mitigation is required once the kernel is updated.
Description
A vulnerability in the Linux kernel's USB CATC driver (catc_rx_done function) allowed crafted packet headers to cause out-of-bounds reads and processing of runt packets. This was due to improper bounds checking of RX packet lengths, which could lead to reading uninitialized memory. The issue has been fixed by properly validating packet lengths and rejecting malformed packets.
References
- git.kernel.org/stable/c/3942557938f846e7481f6ccb2b41ccbdee61baa1 (opens in a new tab)
- git.kernel.org/stable/c/2f87bbd5a7bf6ee79d598f7e22cf77810d29ae87 (opens in a new tab)
- git.kernel.org/stable/c/4cc0a8eb2f9336cfa3e4ac329bc5585ca970ced3 (opens in a new tab)
- git.kernel.org/stable/c/21e206dd88b3de6e36bb607dec3797c59bc3007b (opens in a new tab)
- git.kernel.org/stable/c/801e21cf7dd6bcee31db907625d5045f21c9c1d9 (opens in a new tab)
- git.kernel.org/stable/c/dd9c6f8f05170223edec2dac476606cd40d9acb7 (opens in a new tab)
- git.kernel.org/stable/c/9d4be026bdff2c1da7b6c7e01c0a47f2df409e97 (opens in a new tab)
- git.kernel.org/stable/c/9d565b6b72fe3f41fd43636e143072848105189f (opens in a new tab)