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-74291ASoC: topology: Check PCM and DAI name strings before use

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: topology: Check PCM and DAI name strings before use Topology objects store several PCM and DAI names in fixed-size UAPI arrays. Other topology parser paths validate these fields with bounded strnlen() checks before using them as C strings, but the PCM and DAI paths still pass some fixed-size arrays directly to strlen(), devm_kstrdup(), DAI lookup, and diagnostic prints. A malformed topology blob with a non-NUL-terminated PCM, DAI, or stream capability name can therefore make the parser read past the end of the fixed-size field. Reject unterminated PCM and DAI name fields before consuming them as C strings.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months 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.17% · top 93% of all CVEs (12 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 64527e8a352968bda529f01df1c9dd5fe581ff04 – < d09dad8dff862c4b5aac48b1223e512074ffeb08
    • affected 64527e8a352968bda529f01df1c9dd5fe581ff04 – < c405b07246bf179e9457de57501c3470175b165e
    • affected 64527e8a352968bda529f01df1c9dd5fe581ff04 – < 473f7d25d93e80db526a9d05887f0071abdc6d9b
    • affected 64527e8a352968bda529f01df1c9dd5fe581ff04 – < 5c2537cf24d673956b4e58029001667f89586fa2
    • affected 64527e8a352968bda529f01df1c9dd5fe581ff04 – < ba37b62ed0a443b8e23f53a7477e7f2537fd34c7
    • affected 64527e8a352968bda529f01df1c9dd5fe581ff04 – < b7e44d1986d6671342c19b82192189ca5db5dab7
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .