Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 5c37bd025068381f5bdbbf6a5ae3a1da8f6ed928 – < 7c6d2d2baeb1e62dc8c6951d27edc16c5ea6e3aa
    • affected 06d4938e41d62af7b5b3f39eb239f58b21f50443 – < a40e250414b463e953c54cd2a829c9a9a49a78c3
    • affected 55024322915539098f7a7dd318351c7a003ff041 – < d34deef34c99bb4b3ebd2ac51058857827a20e7e
    • affected 215e5fe75881a7e2425df04aeeed47a903d5cd5d – < 201b60c4d15538fcc3c0c2ea9b75dd7d0f58022c
    • affected 215e5fe75881a7e2425df04aeeed47a903d5cd5d – < 8468dd79cfb2ffbdeaf7c353f63d64941cb8ba05
    • affected 756c48bdf23050def518e85929be6edea9ae6823
    • affected 6.6.136 – < 6.6.145
    • affected 6.12.83 – < 6.12.97
    • affected 6.18.24 – < 6.18.40
    • affected 6.19.14 – < 6.20
  • Linux · Linux

    • affected 7.0
    • unaffected < 7.0
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72300 badge
[![CVE-2026-72300](https://cveledger.app/badge/CVE-2026-72300.svg)](https://cveledger.app/cve/CVE-2026-72300)

Record last updated .