# CVE-2026-98055: ASoC: Intel: avs: Clean up the bus when fetching ML caps fails

> A missing cleanup in the Intel AVS audio driver can cause resource leaks or instability when capability fetching fails, potentially leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104375, BELL-CVE-2026-98055, DEBIAN-CVE-2026-98055, GHSA-38h3-q9xp-263p, UBUNTU-CVE-2026-98055

## What is CVE-2026-98055?

CVE-2026-98055 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

ASoC: Intel: avs: Clean up the bus when fetching ML caps fails

snd_hdac_ext_bus_get_ml_capabilities() may fail and its return code
shall be checked and accounted for. Address the issue by updating the
error-path for avs_pci_probe().

At the same time, if the function in question succeeds but the next part
of avs_pci_probe() fails, the hlink list shall be cleaned up before
leaving the scope.

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


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

Apply the vendor's patch.

## Is CVE-2026-98055 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98055 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98055 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-98055/ (Markdown: https://insights.sbomify.com/CVE-2026-98055/index.md)
```

## Sources

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

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