ALSA: ymfpci: check snd_ctl_new1() return value
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.18% (FIRST EPSS).
- Fixed version: Linux Linux 02f33c2062c75e28abc7ad58ce86451cf3140455, 18ec7d7785be7a4ee8ea11e355122282caad4267, 6.1.178.
Low priority for now. Upgrade to Linux Linux 02f33c2062c75e28abc7ad58ce86451cf3140455, 18ec7d7785be7a4ee8ea11e355122282caad4267, 6.1.178 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: ALSA: ymfpci: check snd_ctl_new1() return value snd_ctl_new1() can return NULL when memory allocation fails. snd_ymfpci_create_spdif_controls() does not check the return value before dereferencing kctl->id.device, which can lead to a NULL pointer dereference. Add NULL checks after snd_ctl_new1() calls and return -ENOMEM if any fails.
- Published
- Jul 25, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 7th 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
- cf671d2462d9af50c328bcc185d2c7b9726f8093, 6.4affected
- 1f6c520932bca5be9e8dec137fccb2fc094a80fe and later · before d7c71dfd4b80f0eacac2c157a8a3a4c6e8b2e0d1affected · git
- c9b83ae4a1609b1914ba7fc70826a3f3a8b234db and later · before 91095474eea29b95c9a8bceb9b501a2702b6c55faffected · git
- c9b83ae4a1609b1914ba7fc70826a3f3a8b234db and later · before 02f33c2062c75e28abc7ad58ce86451cf3140455affected · git
- c9b83ae4a1609b1914ba7fc70826a3f3a8b234db and later · before f6538a318947b627710b08a268bc80a48c23bde7affected · git
- c9b83ae4a1609b1914ba7fc70826a3f3a8b234db and later · before 18ec7d7785be7a4ee8ea11e355122282caad4267affected · git
- c9b83ae4a1609b1914ba7fc70826a3f3a8b234db and later · before e64d170346d00b580c0043de3e5ccb3e331c47d4affected · git
- 6.1.34 and later · before 6.1.178affected · semver
- 6.3.8 and later · before 6.4affected · semver
- before 6.4not 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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-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-64487Jul 25, 2026 · ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser0Monitor
- ← EarlierCVE-2026-64488Jul 25, 2026 · ALSA: aoa: check snd_ctl_new1() return value0Monitor
- Later →CVE-2026-64491Jul 25, 2026 · ALSA: usx2y: us144mkii: fix work UAF on disconnect0Monitor
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 | 02f33c2062c75e28abc7ad58ce86451cf3140455 | Vendor (CNA) |
| Linux Linux | 18ec7d7785be7a4ee8ea11e355122282caad4267 | Vendor (CNA) |
| Linux Linux | 6.1.178 | Vendor (CNA) |
| Linux Linux | 6.4 | Vendor (CNA) |
| Linux Linux | 91095474eea29b95c9a8bceb9b501a2702b6c55f | Vendor (CNA) |
| Linux Linux | d7c71dfd4b80f0eacac2c157a8a3a4c6e8b2e0d1 | Vendor (CNA) |
| Linux Linux | e64d170346d00b580c0043de3e5ccb3e331c47d4 | Vendor (CNA) |
| Linux Linux | f6538a318947b627710b08a268bc80a48c23bde7 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-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/18ec7d7785be7a4ee8ea11e355122282caad4267
- git.kernel.org/stable/c/91095474eea29b95c9a8bceb9b501a2702b6c55f
- git.kernel.org/stable/c/d7c71dfd4b80f0eacac2c157a8a3a4c6e8b2e0d1
- git.kernel.org/stable/c/e64d170346d00b580c0043de3e5ccb3e331c47d4
- git.kernel.org/stable/c/f6538a318947b627710b08a268bc80a48c23bde7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.