LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21916: usb: atm: cxacru: fix a flaw in existing endpoint checks

In the Linux kernel, the following vulnerability has been resolved: usb: atm: cxacru: fix a flaw in existing endpoint checks Syzbot once again identified a flaw in usb endpoint checking, see [1]. This time the issue stems from a commit authored by me (2eabb655a968 ("usb: atm: cxacru: fix endpoint checking in cxacru_bind()")). While using usb_find_common_endpoints() may usually be enough to discard devices with wrong endpoints, in this case one needs more than just finding and identifying the sufficient number of endpoints of correct types - one needs to check the endpoint's address as well. Since cxacru_bind() fills URBs with CXACRU_EP_CMD address in mind, switch the endpoint verification approach to usb_check_XXX_endpoints() instead to fix incomplete ep testing. [1] Syzbot report: usb 5-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 0 PID: 1378 at drivers/usb/core/urb.c:504 usb_submit_urb+0xc4e/0x18c0 drivers/usb/core/urb.c:503 ... RIP: 0010:usb_submit_urb+0xc4e/0x18c0 drivers/usb/core/urb.c:503 ... Call Trace: <TASK> cxacru_cm+0x3c8/0xe50 drivers/usb/atm/cxacru.c:649 cxacru_card_status drivers/usb/atm/cxacru.c:760 [inline] cxacru_bind+0xcf9/0x1150 drivers/usb/atm/cxacru.c:1223 usbatm_usb_probe+0x314/0x1d30 drivers/usb/atm/usbatm.c:1058 cxacru_usb_probe+0x184/0x220 drivers/usb/atm/cxacru.c:1377 usb_probe_interface+0x641/0xbb0 drivers/usb/core/driver.c:396 really_probe+0x2b9/0xad0 drivers/base/dd.c:658 __driver_probe_device+0x1a2/0x390 drivers/base/dd.c:800 driver_probe_device+0x50/0x430 drivers/base/dd.c:830 ...

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel USB driver flaw in the cxacru USB ATM driver. A specially malformed or incompatible USB device can pass incomplete endpoint checks and trigger invalid USB request handling. The public sources show a kernel fix, but no evidence of active exploitation or broad remote exposure.

Executive priority

Treat as a targeted kernel maintenance issue, not an emergency remote-exploitation event. Prioritize patching where untrusted USB devices or virtualized USB passthrough exist, and fold the fix into standard kernel update cycles elsewhere.

Technical view

cxacru_bind() accepted endpoints based on type and count without verifying the endpoint address expected by CXACRU_EP_CMD. Syzbot reported a usb_submit_urb warning caused by a bogus transfer type. The fix changes endpoint verification to address-aware usb_check_* endpoint checks in stable Linux commits.

Likely exposure

Exposure is mainly on Linux systems that include and can load the cxacru USB ATM driver, especially where physical USB access, USB passthrough, or untrusted USB devices are possible. Internet-facing exposure is not indicated by the sources.

Exploitation context

The provided sources cite Syzbot discovery and kernel remediation. CISA KEV status is false, and the bundle provides no public evidence of active exploitation, exploit availability, privilege impact, or remote attack path.

Researcher notes

Evidence supports an endpoint-validation flaw in drivers/usb/atm/cxacru.c found by Syzbot and fixed upstream. The bundle lacks CVSS, CWE, impact classification, and exploitability detail, so severity and practical impact remain partly uncertain.

Mitigation direction

  • Apply the relevant Linux kernel or distribution security update.
  • Review the referenced stable kernel commits for fixed branches.
  • Check Debian LTS advisories if running Debian-based systems.
  • Limit untrusted USB device access until patched.
  • Follow vendor guidance for temporary controls if updates are delayed.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Check whether the cxacru USB ATM driver is present or loadable.
  • Confirm patched kernel versions or referenced fixes are installed.
  • Review asset classes with USB passthrough or physical USB exposure.
  • Track vendor advisories for distribution-specific fixed package versions.
Prepared
Confidence
medium
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-21916 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
11Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux23926d316d2836315cb113569f91393266eb5b47, 75ddbf776dd04a09fb9e5267ead5d0c989f84506, 1aac4be1aaa5177506219f01dce5e29194e5e95a, 5584c776a1af7807ca815ee6265f2c1429fc5727, f536f09eb45e4de8d1b9accee9d992aa1846f1d4, 2eabb655a968b862bc0c31629a09f0fbf3c80d51, 2eabb655a968b862bc0c31629a09f0fbf3c80d51, 2eabb655a968b862bc0c31629a09f0fbf3c80d51, 5159a81924311c1ec786ad9fdef784ead8676a6a, ac9007520e392541a29daebaae8b9109007bc781, 5.4.279, 5.10.221, 5.15.162, 6.1.97, 6.6.37, 4.19.317, 6.9.8unaffected
LinuxLinux6.10, 0, 5.4.291, 5.10.235, 5.15.179, 6.1.131, 6.6.83, 6.12.19, 6.13.7, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.