CVE-2026-46184: sound: ua101: fix division by zero at probe
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0ff2b713f406e9ecadb406014d74e7a020ac12b1, 593dd7e6c890d8e4ca21b3e2f796b7cb8e8da983, 6162e8212e88c39492d981b248b5e37002486c66.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0ff2b713f406e9ecadb406014d74e7a020ac12b1, 593dd7e6c890d8e4ca21b3e2f796b7cb8e8da983, 6162e8212e88c39492d981b248b5e37002486c66 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 28, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-369
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.34affected
- 63978ab3e3e963db28093b53bb4598f2702e1ad7 and later · before e02897c5b041c9b980055fa9a6167023d6dc5cafaffected · git
- 63978ab3e3e963db28093b53bb4598f2702e1ad7 and later · before aae1498c59f48d03ee358df84f07a5af9885f827affected · git
- 63978ab3e3e963db28093b53bb4598f2702e1ad7 and later · before 66d9c2ed081f299cfb201d9e9c4faf920e56e0bfaffected · git
- 63978ab3e3e963db28093b53bb4598f2702e1ad7 and later · before 6162e8212e88c39492d981b248b5e37002486c66affected · git
- 63978ab3e3e963db28093b53bb4598f2702e1ad7 and later · before 593dd7e6c890d8e4ca21b3e2f796b7cb8e8da983affected · git
- 63978ab3e3e963db28093b53bb4598f2702e1ad7 and later · before 0ff2b713f406e9ecadb406014d74e7a020ac12b1affected · git
- 63978ab3e3e963db28093b53bb4598f2702e1ad7 and later · before f1862dbf09080254c52175a448290c784dd7d3deaffected · git
- 63978ab3e3e963db28093b53bb4598f2702e1ad7 and later · before d1f73f169c1014463b5060e3f60813e13ddc7b87affected · git
- before 2.6.34not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.34 and later · before 5.10.258
- linux linux kernel5.11 and later · before 5.15.209
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.140
- linux linux kernel6.7 and later · before 6.12.88
- linux linux kernel6.13 and later · before 6.18.30
- linux linux kernel6.19 and later · before 7.0.7
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.88-1 | 6.12.88-1 |
| Debian:14 | linux | before 7.0.7-1 | 7.0.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46181May 28, 2026 · RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event()31Monitor
- ← EarlierCVE-2026-46182May 28, 2026 · pseries/papr-hvpipe: Prevent kernel stack memory leak to userspace22Monitor
- Later →CVE-2026-46185May 28, 2026 · smb/client: fix out-of-bounds read in symlink_data()36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ff2b713f406e9ecadb406014d74e7a020ac12b1 | Vendor (CNA) |
| Linux Linux | 593dd7e6c890d8e4ca21b3e2f796b7cb8e8da983 | Vendor (CNA) |
| Linux Linux | 6162e8212e88c39492d981b248b5e37002486c66 | Vendor (CNA) |
| Linux Linux | 66d9c2ed081f299cfb201d9e9c4faf920e56e0bf | Vendor (CNA) |
| Linux Linux | aae1498c59f48d03ee358df84f07a5af9885f827 | Vendor (CNA) |
| Linux Linux | d1f73f169c1014463b5060e3f60813e13ddc7b87 | Vendor (CNA) |
| Linux Linux | e02897c5b041c9b980055fa9a6167023d6dc5caf | Vendor (CNA) |
| Linux Linux | f1862dbf09080254c52175a448290c784dd7d3de | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-461610 days apartmd/raid10: fix divide-by-zero in setup_geo() with zero far_copies22Monitor
- CVE-2026-458411 days apartnetfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO22Monitor
- CVE-2026-458891 days apartmptcp: do not account for OoO in mptcp_rcvbuf_grow()22Monitor
- CVE-2026-4335420 days apartiio: proximity: hx9023s: Protect against division by zero in set_samp_freq22Monitor
- CVE-2026-4341120 days aparttipc: fix divide-by-zero in tipc_sk_filter_connect()22Monitor
- CVE-2026-4318222 days apartmedia: ccs: Avoid possible division by zero22Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-369 · Divide By ZeroCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/593dd7e6c890d8e4ca21b3e2f796b7cb8e8da983
- git.kernel.org/stable/c/6162e8212e88c39492d981b248b5e37002486c66
- git.kernel.org/stable/c/66d9c2ed081f299cfb201d9e9c4faf920e56e0bf
- git.kernel.org/stable/c/aae1498c59f48d03ee358df84f07a5af9885f827
- git.kernel.org/stable/c/d1f73f169c1014463b5060e3f60813e13ddc7b87
- git.kernel.org/stable/c/e02897c5b041c9b980055fa9a6167023d6dc5caf
- git.kernel.org/stable/c/f1862dbf09080254c52175a448290c784dd7d3de
Vendor advisories and official records. Exploit/PoC links are deliberately left out.