# CVE-2025-40132: ASoC: Intel: sof_sdw: Prevent jump to NULL add_sidecar callback

> A missing null check in the Linux kernel's Intel SoundWire driver allows a local attacker to cause a system crash via a null pointer dereference.

- **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:** 12 Nov 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-40132, DEBIAN-CVE-2025-40132, GHSA-29v4-89fg-g7q9, ROOT-OS-DEBIAN-13-CVE-2025-40132, UBUNTU-CVE-2025-40132

## What is CVE-2025-40132?

CVE-2025-40132 is a vulnerability in Linux, published on 12 Nov 2025. 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: sof_sdw: Prevent jump to NULL add_sidecar callback

In create_sdw_dailink() check that sof_end->codec_info->add_sidecar
is not NULL before calling it.

The original code assumed that if include_sidecar is true, the codec
on that link has an add_sidecar callback. But there could be other
codecs on the same link that do not have an add_sidecar callback.

## Which versions are affected by CVE-2025-40132?


## How do I fix CVE-2025-40132?

Apply the vendor's patch.

## Is CVE-2025-40132 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40132 and fix it if it is affected.

What it is: CVE-2025-40132 is a vulnerability in Linux, published on 12 Nov 2025. 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-2025-40132 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-2025-40132/ (Markdown: https://insights.sbomify.com/CVE-2025-40132/index.md)
```

## Sources

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

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