Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72300: ASoC: SOF: topology: validate vendor array size before parsing

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 201b60c4d15538fcc3c0c2ea9b75dd7d0f58022c, 6.12.97, 6.18.40.

Low priority for now. Upgrade to Linux Linux 201b60c4d15538fcc3c0c2ea9b75dd7d0f58022c, 6.12.97, 6.18.40 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72300

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 756c48bdf23050def518e85929be6edea9ae6823, 7.0affected
    • 5c37bd025068381f5bdbbf6a5ae3a1da8f6ed928 and later · before 7c6d2d2baeb1e62dc8c6951d27edc16c5ea6e3aaaffected · git
    • 06d4938e41d62af7b5b3f39eb239f58b21f50443 and later · before a40e250414b463e953c54cd2a829c9a9a49a78c3affected · git
    • 55024322915539098f7a7dd318351c7a003ff041 and later · before d34deef34c99bb4b3ebd2ac51058857827a20e7eaffected · git
    • 215e5fe75881a7e2425df04aeeed47a903d5cd5d and later · before 201b60c4d15538fcc3c0c2ea9b75dd7d0f58022caffected · git
    • 215e5fe75881a7e2425df04aeeed47a903d5cd5d and later · before 8468dd79cfb2ffbdeaf7c353f63d64941cb8ba05affected · git
    • 6.6.136 and later · before 6.6.145affected · semver
    • 6.12.83 and later · before 6.12.97affected · semver
    • 6.18.24 and later · before 6.18.40affected · semver
    • 6.19.14 and later · before 6.20affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72294Aug 15, 2026 · LoongArch: KVM: Check irq validity in kvm_vcpu_ioctl_interrupt()
    35Monitor
  • ← EarlierCVE-2026-72295Aug 15, 2026 · LoongArch: KVM: Validate irqchip index in irqfd routing
    35Monitor
  • Later →CVE-2026-72307Aug 15, 2026 · mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux201b60c4d15538fcc3c0c2ea9b75dd7d0f58022cVendor (CNA)
Linux Linux6.12.97Vendor (CNA)
Linux Linux6.18.40Vendor (CNA)
Linux Linux6.20Vendor (CNA)
Linux Linux6.6.145Vendor (CNA)
Linux Linux7c6d2d2baeb1e62dc8c6951d27edc16c5ea6e3aaVendor (CNA)
Linux Linux8468dd79cfb2ffbdeaf7c353f63d64941cb8ba05Vendor (CNA)
Linux Linuxa40e250414b463e953c54cd2a829c9a9a49a78c3Vendor (CNA)
Linux Linuxd34deef34c99bb4b3ebd2ac51058857827a20e7eVendor (CNA)
debian:linux6.12.100-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records