Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c2f811314be351d86b6ab41e9297ae80d8da6f86 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:48 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in c2f811314be351d86b6ab41e9297ae80d8da6f86, 61093d7f1144f6a15bac505df35e5f535ade2ac1, 6133b461058316e3ccba7331f974d110d4c08b23 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1b0e614652344a2d39eb336f3dc07651782883bf, < c2f811314be351d86b6ab41e9297ae80d8da6f86
Fixed in
  • c2f811314be351d86b6ab41e9297ae80d8da6f86
LinuxLinuxAffected
  • ≥ 1b0e614652344a2d39eb336f3dc07651782883bf, < 61093d7f1144f6a15bac505df35e5f535ade2ac1
Fixed in
  • 61093d7f1144f6a15bac505df35e5f535ade2ac1
LinuxLinuxAffected
  • ≥ 1b0e614652344a2d39eb336f3dc07651782883bf, < 6133b461058316e3ccba7331f974d110d4c08b23
Fixed in
  • 6133b461058316e3ccba7331f974d110d4c08b23
LinuxLinuxAffected
  • ≥ 1b0e614652344a2d39eb336f3dc07651782883bf, < 993f7677949e3d72e360e86eed1f41c2511f75ed
Fixed in
  • 993f7677949e3d72e360e86eed1f41c2511f75ed
LinuxLinuxAffected
  • ≥ 1b0e614652344a2d39eb336f3dc07651782883bf, < 939b6a41f681aea52af678053072ee443068e93e
Fixed in
  • 939b6a41f681aea52af678053072ee443068e93e
LinuxLinuxAffected
  • ≥ 1b0e614652344a2d39eb336f3dc07651782883bf, < 645d98dbccdbfdbf0129f48822af7183492de091
Fixed in
  • 645d98dbccdbfdbf0129f48822af7183492de091

AI-suggested

A fix is available and has been applied in the Linux kernel. Users should update to a kernel version that includes the fix identified by the provided commit hashes. No additional mitigation is required once the fix is applied.

Description

A vulnerability in the Linux kernel's usb atm cxacru driver caused the rcv_urb USB request block to remain active if an error occurred during the cxacru_cm() function. This improper handling could trigger warnings and unstable behavior during device initialization. The issue has been fixed by ensuring the rcv_urb is properly killed on error.

References

Community reviews

Loading reviews…