CVE-2026-68201: ALSA: timer: drain a slave's callback before its master detaches it
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.17% (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 2b298997786876b225cff2446e11a0fa6f602f6d, 426c0ff1c433d6030610ad4f9375746dfe931caa, bdefe1346a8e6b8dc8593406dc2617e985fcbcab.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2b298997786876b225cff2446e11a0fa6f602f6d, 426c0ff1c433d6030610ad4f9375746dfe931caa, bdefe1346a8e6b8dc8593406dc2617e985fcbcab 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: timer: drain a slave's callback before its master detaches it snd_timer_close_locked() drains the closing instance's own in-flight callback (IFLG_CALLBACK) before freeing it, but not its slaves'. When a master instance is closed, remove_slave_links() clears each slave's ->timer; the slave's own close then reads timer == NULL and takes the branch that skips the drain entirely (snd_timer_stop_slave() also no-ops on a NULL timer). So a slave whose callback is still running when the master is closed is freed underneath the live callback, leading to use-after-free. Drain the slaves too before remove_slave_links() severs them. snd_timer_stop() has already taken this instance off the active list, so no new slave callback can be queued. Take the slaves off the ack list so a pending one can't fire either, then wait for any that is already in flight.
- Published
- Aug 10, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th 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%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
—
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
- 6.12affected
- 37745918e0e7575bc40f38da93a99b9fa6406224 and later · before cd461bcfcdf8d6b6b5365941c1d3859f8bc77aa0affected · git
- 37745918e0e7575bc40f38da93a99b9fa6406224 and later · before 426c0ff1c433d6030610ad4f9375746dfe931caaaffected · git
- 37745918e0e7575bc40f38da93a99b9fa6406224 and later · before 2b298997786876b225cff2446e11a0fa6f602f6daffected · git
- 37745918e0e7575bc40f38da93a99b9fa6406224 and later · before bdefe1346a8e6b8dc8593406dc2617e985fcbcabaffected · git
- before 6.12not affected · semver
- 6.12.101 and later · up to and including 6.12.*not affected · semver
- 6.18.42 and later · up to and including 6.18.*not affected · semver
- 7.1.6 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-devel | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-devel-matched | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-headers | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-zfcpdump-devel | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | kernel-zfcpdump-devel-matched | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | perf | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:10 | python3-perf | before 6.12.0-211.59.1.el10_2 | 6.12.0-211.59.1.el10_2 |
| AlmaLinux:9 | kernel | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 |
+96
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-68199Aug 10, 2026 · wifi: ath6kl: fix OOB access from firmware ADDBA window size35Monitor
- ← EarlierCVE-2026-68200Aug 10, 2026 · ALSA: timer: don't re-enter an instance callback that is still running31Monitor
- Later →CVE-2026-68202Aug 10, 2026 · ALSA: seq: close a re-opened queue timer in the destructor31Monitor
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 | 2b298997786876b225cff2446e11a0fa6f602f6d | Vendor (CNA) |
| Linux Linux | 426c0ff1c433d6030610ad4f9375746dfe931caa | Vendor (CNA) |
| Linux Linux | bdefe1346a8e6b8dc8593406dc2617e985fcbcab | Vendor (CNA) |
| Linux Linux | cd461bcfcdf8d6b6b5365941c1d3859f8bc77aa0 | Vendor (CNA) |
| almalinux:kernel | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules-core | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules-extra | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 5.14.0-687.51.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.101-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+1
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).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()39Monitor
- CVE-2026-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust39Monitor
- CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()39Monitor
- CVE-2026-681560 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update39Monitor
- CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification39Monitor
- CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment39Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · 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-secondary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.