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()… (CVE-2026-74680)
A vulnerability in the Linux kernel's usb: atm: cxacru driver was resolved by ensuring that the receive URB (rcv_urb) is properly killed on error in the cxacru_cm() function. Previously, if cxacru_cm() encountered an error while submitting or waiting for the send URB (snd_urb), it aborted without killing the already submitted rcv_urb, leaving it active. This could cause warnings and potential instability during device initialization when the driver attempts to resubmit an active URB. The fix involves calling usb_kill_urb() on rcv_urb in the error path to safely terminate it.
AI Analysis
Technical Summary
The Linux kernel's usb: atm: cxacru driver had a flaw in the cxacru_cm() function where an error during submission or waiting for snd_urb caused the function to abort without killing the already submitted rcv_urb. This left rcv_urb active, which could lead to warnings and improper behavior when the driver retried operations during initialization. The issue was fixed by ensuring usb_kill_urb() is called on rcv_urb in the error path, which safely kills the URB whether it is active or not, preventing the warning and potential instability.
Potential Impact
The vulnerability could cause warnings and potential instability in the USB ATM driver during device initialization due to an active URB being resubmitted. This may affect device functionality or stability but does not explicitly indicate a security breach or data compromise. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to properly kill the rcv_urb on error in cxacru_cm(). Users should update to a kernel version that includes this fix once available. Since this is a kernel driver issue, applying the official kernel update is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should check the vendor or kernel advisory for the exact fixed versions and update accordingly.
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()… (CVE-2026-74680)
Description
A vulnerability in the Linux kernel's usb: atm: cxacru driver was resolved by ensuring that the receive URB (rcv_urb) is properly killed on error in the cxacru_cm() function. Previously, if cxacru_cm() encountered an error while submitting or waiting for the send URB (snd_urb), it aborted without killing the already submitted rcv_urb, leaving it active. This could cause warnings and potential instability during device initialization when the driver attempts to resubmit an active URB. The fix involves calling usb_kill_urb() on rcv_urb in the error path to safely terminate it.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's usb: atm: cxacru driver had a flaw in the cxacru_cm() function where an error during submission or waiting for snd_urb caused the function to abort without killing the already submitted rcv_urb. This left rcv_urb active, which could lead to warnings and improper behavior when the driver retried operations during initialization. The issue was fixed by ensuring usb_kill_urb() is called on rcv_urb in the error path, which safely kills the URB whether it is active or not, preventing the warning and potential instability.
Potential Impact
The vulnerability could cause warnings and potential instability in the USB ATM driver during device initialization due to an active URB being resubmitted. This may affect device functionality or stability but does not explicitly indicate a security breach or data compromise. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to properly kill the rcv_urb on error in cxacru_cm(). Users should update to a kernel version that includes this fix once available. Since this is a kernel driver issue, applying the official kernel update is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should check the vendor or kernel advisory for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-29mq-wp6x-9hp3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74680"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f1acd9273b499bc786
Added to database: 08/22/2026, 22:51:29 UTC
Last enriched: 08/23/2026, 00:10:36 UTC
Last updated: 08/23/2026, 01:32:06 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.