# CVE-2026-99182: ASoC: SOF: ipc4-topology: Fix shift-out-of-bounds for aggregated ALH capture


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111347, BELL-CVE-2026-99182, DEBIAN-CVE-2026-99182, GHSA-v4wc-fj92-8998, UBUNTU-CVE-2026-99182

## What is CVE-2026-99182?

CVE-2026-99182 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ASoC: SOF: ipc4-topology: Fix shift-out-of-bounds for aggregated ALH capture

When ch_count is smaller than blob->alh_cfg.device_count (e.g. a mono
capture stream, such as a SmartMic, aggregated across multiple SDW
links), step = ch_count / blob->alh_cfg.device_count truncates to 0.
The subsequent GENMASK(step - 1, 0) then underflows step - 1 (u32) to
UINT_MAX, causing GENMASK()'s internal shift to use an out-of-bounds
exponent:

  UBSAN: shift-out-of-bounds in sound/soc/sof/ipc4-topology.c:2363:13
  shift exponent 18446744069414584384 is too large for 64-bit type 'long unsigned int'

Treat ch_count < device_count the same way as the existing "channels
equal to output reference channels" case: apply the same ch_mask to
every aggregated device instead of trying to split channels that
can't be evenly divided.

## Which versions are affected by CVE-2026-99182?


## How do I fix CVE-2026-99182?

Upgrade to a fixed version.

## Is CVE-2026-99182 being exploited?

There is no known exploitation of CVE-2026-99182 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99182 and fix it if it is affected.

What it is: CVE-2026-99182 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99182 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99182/ (Markdown: https://insights.sbomify.com/CVE-2026-99182/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99182
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99182
- OSV: https://osv.dev/vulnerability/CVE-2026-99182

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99182/
Summaries are generated and may contain mistakes; the official description above is the record.