# ASoC: SOF: ipc3-topology: Correct get_control_data for non bytes payload

CVE record · `CVE-2022-49518`

- **Identifiers:** `CVE-2022-49518`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:13 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: `d29d41e28eea65493395dda0b6d1fff23ca374f4 to before 896b03bb7c7010042786cfae2115083d4c241dd3` (git)
  - affected: `d29d41e28eea65493395dda0b6d1fff23ca374f4 to before a962890a5a3cce903ff7c7a19fadee63ed9efdc7` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.14`
  - unaffected: `before 5.14` (semver)
  - unaffected: `5.18.3 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 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 SOF (Sound Open Firmware) ASoC ipc3-topology code is affected in versions from commit d29d41e28eea65493395dda0b6d1fff23ca374f4 before the fixes 896b03bb7c7010042786cfae2115083d4c241dd3 and a962890a5a3cce903ff7c7a19fadee63ed9efdc7; the CNA lists affected 5.14 and unaffected earlier releases and from 5.18.3 onward. A crafted topology can cause sof_get_control_data() to perform out-of-bounds access, because it assumes it is only called for bytes-type payloads. The source gives few details on the exploitation conditions or impact. Upgrade to a kernel that includes the fix.

Written 16 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.0025, the 16th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Feb 2025, 02:13 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49518)
- 26 Feb 2025, 07:01 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49518)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/896b03bb7c7010042786cfae2115083d4c241dd3>
- <https://git.kernel.org/stable/c/a962890a5a3cce903ff7c7a19fadee63ed9efdc7>

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-2022-49518>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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