Menu

Star on GitHub · 3.2k

CVE-2026-72300

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 to…

Published Aug 15, 2026EPSS 0.21%

Overview

CVE-2026-72300 is a known-severity vulnerability. It was published on August 15, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-72300?

CVE-2026-72300 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-72300?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-72300?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-72300?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-72300 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.