CVE-2026-46179: ASoC: SOF: Don't allow pointer operations on unconfigured streams
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: Don't allow pointer operations on unconfigured streams
When reporting the pointer for a compressed stream we report the current
I/O frame position by dividing the position by the number of channels
multiplied by the number of container bytes. These values default to 0 and
are only configured as part of setting the stream parameters so this allows
a divide by zero to be configured. Validate that they are non zero,
returning an error if not
Security readout for executives and security teams
Plain-English summary
CVE-2026-46179 is a Linux kernel flaw in the Sound Open Firmware audio path. A compressed audio stream can reach a pointer-reporting operation before stream parameters are configured, causing a divide-by-zero condition. The public record does not provide CVSS, confirmed impact, or evidence of active exploitation.
Executive priority
Treat this as a kernel maintenance item with uncertain severity. It does not currently justify emergency response based on the supplied evidence, but unmanaged Linux endpoints with audio hardware should be included in the next patch cycle.
Technical view
The ASoC SOF compressed-stream pointer calculation divides position by channels multiplied by container bytes. Those values default to zero until stream parameters are set. The kernel fix validates both values are nonzero and returns an error for unconfigured streams instead of performing the division.
Likely exposure
Exposure appears limited to Linux systems using affected kernel versions and the ASoC SOF compressed audio path. Distro package impact is not directly mapped in the source bundle, so confirm with your Linux vendor or kernel build inventory.
Exploitation context
CISA KEV is false in the supplied bundle, and no cited source claims active exploitation. The available evidence only describes a configurable divide-by-zero condition in a kernel audio subsystem path.
Researcher notes
The record lacks CVSS, CWE, exploit status, and detailed affected distribution mapping. Analysis should focus on reachability of compressed audio pointer operations before parameter setup and whether downstream vendors backported the nonzero validation fix.
Mitigation direction
Update affected Linux kernels to vendor builds containing the referenced stable fixes.
Check Linux distribution advisories for package names and backport status.
Prioritize endpoints, kiosks, and shared systems with SOF audio enabled.
Track kernel updates through normal change control if SOF audio is not used.
Validation and detection
Inventory Linux kernel versions across exposed endpoint and server fleets.
Confirm whether systems use ASoC SOF or compressed audio functionality.
Compare installed kernels against vendor advisories and referenced stable commits.
After patching, verify the running kernel matches the approved fixed package.
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.
description · low confidence lookup
Container behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 28, 2026, 09:36 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.