CVE-2026-74680: usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm()
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 0af047703dbed8224552587ed436f14a24371b46, 2f73a065791d2a8e3f0bdf29248e33600359e865, 61093d7f1144f6a15bac505df35e5f535ade2ac1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0af047703dbed8224552587ed436f14a24371b46, 2f73a065791d2a8e3f0bdf29248e33600359e865, 61093d7f1144f6a15bac505df35e5f535ade2ac1 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: usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm() If cxacru_cm() encounters an error while submitting or waiting for snd_urb, it aborts and returns the error without killing the already submitted rcv_urb. This leaves the rcv_urb active. When this happens during initialization (e.g., in cxacru_atm_start()), the driver may ignore the error and proceed to call cxacru_poll_status(), which invokes cxacru_cm() again. Attempting to submit the still-active rcv_urb triggers a warning in usb_submit_urb(): cxacru 1-1:1.0: send of cm 0x84 failed (-104) ATM dev 0: cxacru_atm_start: CHIP_ADSL_LINE_START returned -104 ------------[ cut here ]------------ URB ffff88812658d200 submitted while active WARNING: drivers/usb/core/urb.c:379 at usb_submit_urb+0x79/0x18b0 drivers/usb/core/urb.c:379 ... Call Trace: <TASK> cxacru_cm+0x21a/0xf10 drivers/usb/atm/cxacru.c:631 cxacru_cm_get_array drivers/usb/atm/cxacru.c:722 [inline] cxacru_poll_status+0x178/0x1110 drivers/usb/atm/cxacru.c:828 cxacru_atm_start+0x185/0x360 drivers/usb/atm/cxacru.c:814 usbatm_atm_init+0x144/0x3a0 drivers/usb/atm/usbatm.c:927 usbatm_usb_probe+0x15cb/0x1db0 drivers/usb/atm/usbatm.c:1178 cxacru_usb_probe+0x17f/0x220 drivers/usb/atm/cxacru.c:1370 ... To fix this, ensure that rcv_urb is properly killed if cxacru_cm() aborts early. We can safely call usb_kill_urb() on rcv_urb in the error path, as it is safe to call even if the URB is not active (e.g., if it failed to submit in the first place, or if it already completed).
- Published
- Aug 22, 2026
- Updated
- Nov 6, 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%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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.13affected
- 1b0e614652344a2d39eb336f3dc07651782883bf and later · before 6133b461058316e3ccba7331f974d110d4c08b23affected · git
- 1b0e614652344a2d39eb336f3dc07651782883bf and later · before 61093d7f1144f6a15bac505df35e5f535ade2ac1affected · git
- 1b0e614652344a2d39eb336f3dc07651782883bf and later · before 645d98dbccdbfdbf0129f48822af7183492de091affected · git
- 1b0e614652344a2d39eb336f3dc07651782883bf and later · before 993f7677949e3d72e360e86eed1f41c2511f75edaffected · git
- 1b0e614652344a2d39eb336f3dc07651782883bf and later · before 939b6a41f681aea52af678053072ee443068e93eaffected · git
- 1b0e614652344a2d39eb336f3dc07651782883bf and later · before 2f73a065791d2a8e3f0bdf29248e33600359e865affected · git
- 1b0e614652344a2d39eb336f3dc07651782883bf and later · before 0af047703dbed8224552587ed436f14a24371b46affected · git
- 1b0e614652344a2d39eb336f3dc07651782883bf and later · before c2f811314be351d86b6ab41e9297ae80d8da6f86affected · git
- before 2.6.13not 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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.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-74678Aug 22, 2026 · net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup()30Monitor
- ← EarlierCVE-2026-74679Aug 22, 2026 · usb: gadget: f_ncm: Use unsigned int for ndp_index0Monitor
- Later →CVE-2026-74681Aug 22, 2026 · usb: misc: usbio: check ibuf_len against rxbuf_len in bulk msg0Monitor
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 | 0af047703dbed8224552587ed436f14a24371b46 | Vendor (CNA) |
| Linux Linux | 2f73a065791d2a8e3f0bdf29248e33600359e865 | Vendor (CNA) |
| Linux Linux | 61093d7f1144f6a15bac505df35e5f535ade2ac1 | Vendor (CNA) |
| Linux Linux | 6133b461058316e3ccba7331f974d110d4c08b23 | Vendor (CNA) |
| Linux Linux | 645d98dbccdbfdbf0129f48822af7183492de091 | Vendor (CNA) |
| Linux Linux | 939b6a41f681aea52af678053072ee443068e93e | Vendor (CNA) |
| Linux Linux | 993f7677949e3d72e360e86eed1f41c2511f75ed | Vendor (CNA) |
| Linux Linux | c2f811314be351d86b6ab41e9297ae80d8da6f86 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-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.
No dated events beyond publication.
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-0893 · Aug 24, 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
- SSVC exploitation— → 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/2f73a065791d2a8e3f0bdf29248e33600359e865
- git.kernel.org/stable/c/61093d7f1144f6a15bac505df35e5f535ade2ac1
- git.kernel.org/stable/c/6133b461058316e3ccba7331f974d110d4c08b23
- git.kernel.org/stable/c/645d98dbccdbfdbf0129f48822af7183492de091
- git.kernel.org/stable/c/939b6a41f681aea52af678053072ee443068e93e
- git.kernel.org/stable/c/993f7677949e3d72e360e86eed1f41c2511f75ed
- git.kernel.org/stable/c/c2f811314be351d86b6ab41e9297ae80d8da6f86
Vendor advisories and official records. Exploit/PoC links are deliberately left out.