Unknown

CVE-2026-74680 — usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm()

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 Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 14, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 1b0e614652344a2d39eb336f3dc07651782883bf and < 6133b461058316e3ccba7331f974d110d4c08b23≥ 1b0e614652344a2d39eb336f3dc07651782883bf and < 61093d7f1144f6a15bac505df35e5f535ade2ac1≥ 1b0e614652344a2d39eb336f3dc07651782883bf and < 645d98dbccdbfdbf0129f48822af7183492de091≥ 1b0e614652344a2d39eb336f3dc07651782883bf and < 993f7677949e3d72e360e86eed1f41c2511f75ed≥ 1b0e614652344a2d39eb336f3dc07651782883bf and < 939b6a41f681aea52af678053072ee443068e93e≥ 1b0e614652344a2d39eb336f3dc07651782883bf and < 2f73a065791d2a8e3f0bdf29248e33600359e865≥ 1b0e614652344a2d39eb336f3dc07651782883bf and < 0af047703dbed8224552587ed436f14a24371b46≥ 1b0e614652344a2d39eb336f3dc07651782883bf and < c2f811314be351d86b6ab41e9297ae80d8da6f86 and 1 more version 2.6.13	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 14, 2026
Affected products added · linux/linux
Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 14, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 14, 2026 · NIST National Vulnerability Database
CVE published
Aug 22, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 14, 2026 – Oct 14, 2026
1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

10 on the record

git.kernel.org/stable/c/0af047703dbed8224552587ed436f14a24371b46
NIST National Vulnerability Database
git.kernel.org/stable/c/6133b461058316e3ccba7331f974d110d4c08b23
NIST National Vulnerability Database
git.kernel.org/stable/c/2f73a065791d2a8e3f0bdf29248e33600359e865
NIST National Vulnerability Database
git.kernel.org/stable/c/993f7677949e3d72e360e86eed1f41c2511f75ed
NIST National Vulnerability Database
github.com/advisories/GHSA-29mq-wp6x-9hp3
GitHub Security Advisories
git.kernel.org/stable/c/61093d7f1144f6a15bac505df35e5f535ade2ac1
NIST National Vulnerability Database
git.kernel.org/stable/c/939b6a41f681aea52af678053072ee443068e93e
NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2026-74680
GitHub Security Advisories
git.kernel.org/stable/c/c2f811314be351d86b6ab41e9297ae80d8da6f86
NIST National Vulnerability Database
git.kernel.org/stable/c/645d98dbccdbfdbf0129f48822af7183492de091
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 7h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 7h
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-74680 is "usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.