Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

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 f1862dbf09080254c52175a448290c784dd7d3de, e02897c5b041c9b980055fa9a6167023d6dc5caf, d1f73f169c1014463b5060e3f60813e13ddc7b87 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 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
  • ≥ 63978ab3e3e963db28093b53bb4598f2702e1ad7, < f1862dbf09080254c52175a448290c784dd7d3de
Fixed in
  • f1862dbf09080254c52175a448290c784dd7d3de
LinuxLinuxAffected
  • ≥ 63978ab3e3e963db28093b53bb4598f2702e1ad7, < e02897c5b041c9b980055fa9a6167023d6dc5caf
Fixed in
  • e02897c5b041c9b980055fa9a6167023d6dc5caf
LinuxLinuxAffected
  • ≥ 63978ab3e3e963db28093b53bb4598f2702e1ad7, < d1f73f169c1014463b5060e3f60813e13ddc7b87
Fixed in
  • d1f73f169c1014463b5060e3f60813e13ddc7b87
LinuxLinuxAffected
  • ≥ 63978ab3e3e963db28093b53bb4598f2702e1ad7, < aae1498c59f48d03ee358df84f07a5af9885f827
Fixed in
  • aae1498c59f48d03ee358df84f07a5af9885f827
LinuxLinuxAffected
  • ≥ 63978ab3e3e963db28093b53bb4598f2702e1ad7, < 6162e8212e88c39492d981b248b5e37002486c66
Fixed in
  • 6162e8212e88c39492d981b248b5e37002486c66
LinuxLinuxAffected
  • ≥ 63978ab3e3e963db28093b53bb4598f2702e1ad7, < 593dd7e6c890d8e4ca21b3e2f796b7cb8e8da983
Fixed in
  • 593dd7e6c890d8e4ca21b3e2f796b7cb8e8da983

Description

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.

References

Community reviews

Loading reviews…