CVE-2026-64001: ALSA: pcm: oss: Fix setup list UAF on proc write error
Noroxi assessment
Priority: Monitor (action score 31/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4cc54bdd54b337e77115be5b55577d1c58608eae, 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce, be387230dc22d870afd0e5d35912b07c2bc323bd.
Low priority for now. Upgrade to Linux Linux 4cc54bdd54b337e77115be5b55577d1c58608eae, 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce, be387230dc22d870afd0e5d35912b07c2bc323bd 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: pcm: oss: Fix setup list UAF on proc write error snd_pcm_oss_proc_write() links a newly allocated setup entry into the OSS setup list before duplicating the task name. If the task-name allocation fails, the error path frees the already linked entry and leaves setup_list pointing at freed memory. A later OSS device open can then walk the stale list entry in snd_pcm_oss_look_for_setup() and dereference freed memory. Allocate the task name and initialize the setup entry before publishing the entry on setup_list. Also fetch the initial proc read iterator only after taking setup_mutex, so all setup_list traversal follows the same list lifetime rules.
- Published
- Jul 19, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- 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.
Is your version affected? Check itNoroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 2.6.17affected
- 060d77b9c04acd7aef60790398a53f731db8c8fe and later · before d9df965284abde27ba6bfbdfc8407697cf6802f1affected · git
- 060d77b9c04acd7aef60790398a53f731db8c8fe and later · before 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ceaffected · git
- 060d77b9c04acd7aef60790398a53f731db8c8fe and later · before e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3caffected · git
- 060d77b9c04acd7aef60790398a53f731db8c8fe and later · before be387230dc22d870afd0e5d35912b07c2bc323bdaffected · git
- 060d77b9c04acd7aef60790398a53f731db8c8fe and later · before 4cc54bdd54b337e77115be5b55577d1c58608eaeaffected · git
- before 2.6.17not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.93 and later · up to and including 6.12.*not affected · semver
- 6.18.35 and later · up to and including 6.18.*not affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.17 and later · before 6.12.93
- linux linux kernel6.13 and later · before 6.18.35
- linux linux kernel6.19 and later · before 7.0.12
- linux linux kernel7.1
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:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63999Jul 19, 2026 · ethtool: rss: fix indir_table and hkey leak on get_rxfh failure22Monitor
- ← EarlierCVE-2026-64000Jul 19, 2026 · net: hsr: fix potential OOB access in supervision frame handling39Monitor
- Later →CVE-2026-64002Jul 19, 2026 · ipv4: free net->ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table()31Monitor
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 | 4cc54bdd54b337e77115be5b55577d1c58608eae | Vendor (CNA) |
| Linux Linux | 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce | Vendor (CNA) |
| Linux Linux | be387230dc22d870afd0e5d35912b07c2bc323bd | Vendor (CNA) |
| Linux Linux | d9df965284abde27ba6bfbdfc8407697cf6802f1 | Vendor (CNA) |
| Linux Linux | e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3c | Vendor (CNA) |
| debian:linux | 6.12.94-1 · Debian:13 | 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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
- CVSS— → 7.8
- Severity— → high
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.