CVE-2026-74291: ASoC: topology: Check PCM and DAI name strings before use
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 473f7d25d93e80db526a9d05887f0071abdc6d9b, 5c2537cf24d673956b4e58029001667f89586fa2, b7e44d1986d6671342c19b82192189ca5db5dab7; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 473f7d25d93e80db526a9d05887f0071abdc6d9b, 5c2537cf24d673956b4e58029001667f89586fa2, b7e44d1986d6671342c19b82192189ca5db5dab7; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 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: 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.
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 4.6affected
- 64527e8a352968bda529f01df1c9dd5fe581ff04 and later · before d09dad8dff862c4b5aac48b1223e512074ffeb08affected · git
- 64527e8a352968bda529f01df1c9dd5fe581ff04 and later · before c405b07246bf179e9457de57501c3470175b165eaffected · git
- 64527e8a352968bda529f01df1c9dd5fe581ff04 and later · before 473f7d25d93e80db526a9d05887f0071abdc6d9baffected · git
- 64527e8a352968bda529f01df1c9dd5fe581ff04 and later · before 5c2537cf24d673956b4e58029001667f89586fa2affected · git
- 64527e8a352968bda529f01df1c9dd5fe581ff04 and later · before ba37b62ed0a443b8e23f53a7477e7f2537fd34c7affected · git
- 64527e8a352968bda529f01df1c9dd5fe581ff04 and later · before b7e44d1986d6671342c19b82192189ca5db5dab7affected · git
- before 4.6not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74288Aug 15, 2026 · net: fib_rules: Don't dump dying fib_rule in fib_rules_dump().31Monitor
- ← EarlierCVE-2026-74289Aug 15, 2026 · ipv4: fib: Don't dump dying fib_info in fib_leaf_notify().31Monitor
- Later →CVE-2026-74292Aug 15, 2026 · ASoC: tegra: tegra210_ahub: Validate written enum value28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 473f7d25d93e80db526a9d05887f0071abdc6d9b | Vendor (CNA) |
| Linux Linux | 5c2537cf24d673956b4e58029001667f89586fa2 | Vendor (CNA) |
| Linux Linux | b7e44d1986d6671342c19b82192189ca5db5dab7 | Vendor (CNA) |
| Linux Linux | ba37b62ed0a443b8e23f53a7477e7f2537fd34c7 | Vendor (CNA) |
| Linux Linux | c405b07246bf179e9457de57501c3470175b165e | Vendor (CNA) |
| Linux Linux | d09dad8dff862c4b5aac48b1223e512074ffeb08 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package 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.
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 researchersFinders, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/5c2537cf24d673956b4e58029001667f89586fa2
- git.kernel.org/stable/c/b7e44d1986d6671342c19b82192189ca5db5dab7
- git.kernel.org/stable/c/ba37b62ed0a443b8e23f53a7477e7f2537fd34c7
- git.kernel.org/stable/c/c405b07246bf179e9457de57501c3470175b165e
- git.kernel.org/stable/c/d09dad8dff862c4b5aac48b1223e512074ffeb08
Vendor advisories and official records. Exploit/PoC links are deliberately left out.