LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46184: sound: ua101: fix division by zero at probe

In the Linux kernel, the following vulnerability has been resolved: sound: ua101: fix division by zero at probe Add a missing sanity check for bNrChannels in detect_usb_format() to prevent a division by zero in playback_urb_complete() and capture_urb_complete(). USB core does not validate class-specific descriptor fields such as bNrChannels, so drivers must verify them before use. If a device provides bNrChannels = 0, frame_bytes becomes zero and is later used as a divisor in the URB completion handlers, leading to a kernel crash.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A malformed USB audio device can make the Linux ua101 sound driver divide by zero and crash the kernel. The impact described is availability loss, not data theft. Exposure is mainly systems that can connect USB audio hardware using this driver.

Executive priority

Treat as a targeted availability risk. Prioritize patching systems where physical USB access is possible or USB audio devices are used, but do not rank it above remotely exploitable or privilege-escalation kernel issues without additional evidence.

Technical view

The bug is a missing sanity check for bNrChannels in detect_usb_format(). USB core does not validate this class-specific descriptor. When bNrChannels is zero, frame_bytes becomes zero and later reaches playback_urb_complete() or capture_urb_complete() as a divisor, causing a kernel crash.

Likely exposure

Linux systems with affected kernel versions and the ua101 USB audio driver reachable through connected USB audio devices. Risk is highest for endpoints, workstations, labs, kiosks, or servers where untrusted physical USB devices can be attached.

Exploitation context

The source bundle reports no KEV listing and provides no evidence of active exploitation. Practical abuse appears to require a device presenting a malformed USB audio descriptor to the affected driver, causing denial of service through kernel crash.

Researcher notes

The CVE data lacks CVSS, CWE, and exploitability detail. The vulnerability is bounded to descriptor validation in the ua101 driver path, with the documented outcome being kernel crash. Further assessment should map fixed stable commits to distribution package versions.

Mitigation direction

  • Apply a distribution kernel update containing the ua101 bNrChannels sanity-check fix.
  • Track the listed Linux stable commits for the relevant kernel branch.
  • Restrict untrusted USB audio device access until patched.
  • Check vendor guidance before changing driver availability or USB device policy.

Validation and detection

  • Inventory Linux hosts running affected kernel versions listed in the CVE record.
  • Check whether the ua101 driver is present or loaded on exposed systems.
  • Verify the installed kernel includes the stable ua101 fix.
  • Review crash logs for USB audio or ua101-related kernel crashes.
Prepared
Confidence
medium
Sources
10

Public sources used

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-2026-46184 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
0ADP providers
9Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux63978ab3e3e963db28093b53bb4598f2702e1ad7, 63978ab3e3e963db28093b53bb4598f2702e1ad7, 63978ab3e3e963db28093b53bb4598f2702e1ad7, 63978ab3e3e963db28093b53bb4598f2702e1ad7, 63978ab3e3e963db28093b53bb4598f2702e1ad7, 63978ab3e3e963db28093b53bb4598f2702e1ad7, 63978ab3e3e963db28093b53bb4598f2702e1ad7, 63978ab3e3e963db28093b53bb4598f2702e1ad7unaffected
LinuxLinux2.6.34, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7, 7.1affected
Weakness

CWE details

No CWE listed

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