CVE-2026-72300

ASoC: SOF: topology: validate vendor array size before parsing

N/A
Published: August 15, 2026 at 05:55 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: topology: validate vendor array size before parsing sof_parse_token_sets() reads array->size while iterating over topology private data. The loop condition only checks that some data remains, so a malformed topology with a truncated trailing vendor array can make the parser read the size field before a full vendor-array header is available. Validate that the remaining private data contains a complete snd_soc_tplg_vendor_array header before reading array->size. The declared array size check also needs to remain signed. asize is an int, but sizeof(*array) has type size_t, so comparing them directly promotes negative asize values to unsigned and lets them pass the check, as reported in the stable review thread reference below. Cast sizeof(*array) to int when validating the declared array size. This rejects negative, zero and otherwise too-small sizes before the parser dispatches to the tuple-specific code.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.19.146.12.83 ≤ v < 6.12.976.18.24 ≤ v < 6.18.406.19.14 ≤ v < 6.206.6.136 ≤ v < 6.6.1457.0 ≤ v < 7.1.57.0 ≤ v < 7.2215e5fe75881a7e2425df04aeeed47a903d5cd5d55024322915539098f7a7dd318351c7a003ff0415c37bd025068381f5bdbbf6a5ae3a1da8f6ed9286.12.836.18.246.19.146.6.1366d4938e41d62af7b5b3f39eb239f58b21f504437.0756c48bdf23050def518e85929be6edea9ae6823
Vendor states this is fixed in 201b60c4d15538fcc3c0c2ea9b75dd7d0f58022c (fixed)
Vendor states this is fixed in 7c6d2d2baeb1e62dc8c6951d27edc16c5ea6e3aa (fixed)
Vendor states this is fixed in 8468dd79cfb2ffbdeaf7c353f63d64941cb8ba05 (fixed)
Vendor states this is fixed in a40e250414b463e953c54cd2a829c9a9a49a78c3 (fixed)
Vendor states this is fixed in d34deef34c99bb4b3ebd2ac51058857827a20e7e (fixed)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card