LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux audio-driver memory allocation error can leave too little space for Sound Open Firmware IPC4 byte-control data. A locally authenticated, low-privileged user may be able to trigger memory corruption, potentially compromising confidentiality, integrity, and availability. The supplied CVSS score is 7.8.

Executive priority

Treat as a high-priority endpoint and multi-user Linux update, especially where untrusted users have local accounts. It is less urgent than an unauthenticated remote flaw, but the stated impact includes complete compromise of confidentiality, integrity, and availability. Follow normal emergency-change controls rather than delaying broadly deployed fixes.

Technical view

The SOF IPC4 topology code allocated space using a topology-provided max_size that covered the ABI header and payload, but omitted sizeof(struct sof_ipc4_control_data). The linked stable changes add that kernel-only structure to the allocation. The source bundle does not establish the precise corruption outcome or exploitation method.

Likely exposure

Exposure is limited to affected Linux kernels where the ASoC SOF IPC4 topology bytes-control path is present and reachable. The supplied version data identifies Linux 6.4 through listed later releases as affected, but its exact range semantics are unclear. Distribution kernels may backport the fix independently.

Exploitation context

The CVSS vector describes local access, low privileges, low complexity, no user interaction, unchanged scope, and potentially high confidentiality, integrity, and availability impact. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit.

Researcher notes

The defect is an undersized allocation caused by excluding struct sof_ipc4_control_data from storage for bytes controls. The supplied record contains no CWE, crash trace, affected configuration matrix, public proof of concept, or confirmed exploitation. Validate reachability and fixed-version status against the relevant distribution rather than relying solely on upstream version labels.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable linked stable fix.
  • Check distribution advisories because package versions may include backported fixes.
  • Prioritize systems allowing untrusted or numerous local users.
  • Restrict unnecessary local access until affected kernels are updated.

Validation and detection

  • Inventory kernel versions and distribution package release identifiers.
  • Confirm whether the kernel enables and uses the SOF IPC4 audio path.
  • Match vendor changelogs against CVE-2025-71286 or the linked fix commits.
  • After updating, verify the running kernel matches the remediated package.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71286 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-71286Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa382082ff74b036944cbc5b6ad29b65f633acd3a, a382082ff74b036944cbc5b6ad29b65f633acd3a, a382082ff74b036944cbc5b6ad29b65f633acd3a, a382082ff74b036944cbc5b6ad29b65f633acd3a, a382082ff74b036944cbc5b6ad29b65f633acd3aunaffected
LinuxLinux6.4, 0, 6.6.128, 6.12.75, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.