Not yet scoredPublished Aug 22, 2026

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

Updated under an hour ago (Oct 27, 2026, 3:40 PM ET)

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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).

CVSS: Not yet scored
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Received
Record last updated: Aug 22, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 1b0e614652344a2d39eb336f3dc07651782883bf before 6133b461058316e3ccba7331f974d110d4c08b23; from 1b0e614652344a2d39eb336f3dc07651782883bf before 61093d7f1144f6a15bac505df35e5f535ade2ac1; from 1b0e614652344a2d39eb336f3dc07651782883bf before 645d98dbccdbfdbf0129f48822af7183492de091; from 1b0e614652344a2d39eb336f3dc07651782883bf before 993f7677949e3d72e360e86eed1f41c2511f75ed; from 1b0e614652344a2d39eb336f3dc07651782883bf before 939b6a41f681aea52af678053072ee443068e93e; from 1b0e614652344a2d39eb336f3dc07651782883bf before 2f73a065791d2a8e3f0bdf29248e33600359e865; 1b0e614652344a2d39eb336f3dc07651782883bf builds before 0af047703dbed8224552587ed436f14a24371b46; from 1b0e614652344a2d39eb336f3dc07651782883bf before c2f811314be351d86b6ab41e9297ae80d8da6f86	CNA record

References

References

https://git.kernel.org/stable/c/6133b461058316e3ccba7331f974d110d4c08b23
https://git.kernel.org/stable/c/61093d7f1144f6a15bac505df35e5f535ade2ac1
https://git.kernel.org/stable/c/645d98dbccdbfdbf0129f48822af7183492de091
https://git.kernel.org/stable/c/993f7677949e3d72e360e86eed1f41c2511f75ed
https://git.kernel.org/stable/c/939b6a41f681aea52af678053072ee443068e93e
https://git.kernel.org/stable/c/2f73a065791d2a8e3f0bdf29248e33600359e865
https://git.kernel.org/stable/c/0af047703dbed8224552587ed436f14a24371b46
https://git.kernel.org/stable/c/c2f811314be351d86b6ab41e9297ae80d8da6f86

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.