CVE-2025-71286
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-131
- Record status
- Modified
Affected
- Linux Kernel < 6.6.128
- Linux Kernel < 6.12.75
- Linux Kernel < 6.18.16
- Linux Kernel < 6.19.6
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-71286.md and follow it. Check whether this project is affected by CVE-2025-71286. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1237cd9ff198cb882402572f29569e5247190974
- https://git.kernel.org/stable/c/491956b45b5f4933632ea6d8a8bdfdf045ab81e1
- https://git.kernel.org/stable/c/59fe643f21b9d59bcbedb0dfbf988ee455c23736
- https://git.kernel.org/stable/c/a653820700b81c9e6f05ac23b7969ecec1a18e85
- https://git.kernel.org/stable/c/a704a1a4394b5877b9adc31b2c3165ad0b541896
References
- https://git.kernel.org/stable/c/1237cd9ff198cb882402572f29569e5247190974
- https://git.kernel.org/stable/c/491956b45b5f4933632ea6d8a8bdfdf045ab81e1
- https://git.kernel.org/stable/c/59fe643f21b9d59bcbedb0dfbf988ee455c23736
- https://git.kernel.org/stable/c/a653820700b81c9e6f05ac23b7969ecec1a18e85
- https://git.kernel.org/stable/c/a704a1a4394b5877b9adc31b2c3165ad0b541896