# ASoC: codecs: rt1011: Use component to get the dapm context in spk_mode_put

CVE record · `CVE-2026-43478`

- **Identifiers:** `CVE-2026-43478`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 13 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 13 May 2026, 15:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `5b35bb517f27fc2401ec3cfd8c02a127627a0188 to before b10b2b15b45923ff2807eeb034d91a39b0a3e690` (git)
  - affected: `5b35bb517f27fc2401ec3cfd8c02a127627a0188 to before 30e4b2290cc2a8d1b9ddb9dcb9c981df1f2a7399` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `6.19.9 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's rt1011 audio codec driver is affected in 6.19 before 6.19.9. Its speaker mode control handler retrieves the wrong context, so it receives a NULL pointer, and the source gives few details on who can trigger this or what the impact is. Upgrade to 6.19.9 or later, or to 7.0 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0010, the 1st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 13 May 2026, 15:08 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43478)
- 13 May 2026, 16:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43478)

## Sources

- [CVE List: CVE-2026-43478](https://www.cve.org/CVERecord?id=CVE-2026-43478)
- [NVD: CVE-2026-43478](https://nvd.nist.gov/vuln/detail/CVE-2026-43478)

### References from the CNA

- <https://git.kernel.org/stable/c/b10b2b15b45923ff2807eeb034d91a39b0a3e690>
- <https://git.kernel.org/stable/c/30e4b2290cc2a8d1b9ddb9dcb9c981df1f2a7399>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43478>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43478/>. Everything for agents: <https://agentprime.io/llms.txt>.
