Linux Kernel up to 6.6.144/6.12.96/6.18.39/7.1.4 ASoC SOF Topology sof_parse_token_sets data authenticity

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.8$0-$5k0.00+

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.6.144/6.12.96/6.18.39/7.1.4. It has been declared as very critical. This issue affects the function sof_parse_token_sets of the component ASoC SOF Topology. The manipulation results in data authenticity. This vulnerability is known as CVE-2026-72300. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Linux Kernel up to 6.6.144/6.12.96/6.18.39/7.1.4. Affected is the function sof_parse_token_sets of the component ASoC SOF Topology. The manipulation with an unknown input leads to a data authenticity vulnerability. CWE is classifying the issue as CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-72300 since 08/09/2026. The exploitability is told to be easy. The attack needs to be approached locally. The exploitation requires an enhanced level of successful authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/15/2026).

Upgrading to version 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch 7c6d2d2baeb1e62dc8c6951d27edc16c5ea6e3aa/a40e250414b463e953c54cd2a829c9a9a49a78c3/d34deef34c99bb4b3ebd2ac51058857827a20e7e/201b60c4d15538fcc3c0c2ea9b75dd7d0f58022c/8468dd79cfb2ffbdeaf7c353f63d64941cb8ba05 is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.2
VulDB Meta Temp Score: 7.8

VulDB Base Score: 8.2
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Data authenticity
CWE: CWE-345
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc1
Patch: 7c6d2d2baeb1e62dc8c6951d27edc16c5ea6e3aa/a40e250414b463e953c54cd2a829c9a9a49a78c3/d34deef34c99bb4b3ebd2ac51058857827a20e7e/201b60c4d15538fcc3c0c2ea9b75dd7d0f58022c/8468dd79cfb2ffbdeaf7c353f63d64941cb8ba05

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72300 (🔒)
GCVE (CVE): GCVE-0-2026-72300
GCVE (VulDB): GCVE-100-390900

Entryinfo

Created: 08/15/2026 16:08
Changes: 08/15/2026 16:08 (59)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!