CVE-2026-98314: Linux kernel · ALSA: pcm: set timer->private_data before registering the PCM timer
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd, d63f5a9f8121fb43c798056d7dd34c58f47185d7, 686c7a6af1eea8d2a919303e4c6bbec3de79dbdc +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel source code as indicated by multiple fixed commit versions. Users should update their Linux kernel to a version including these fixes to remediate the issue.
Description
A vulnerability in the Linux kernel ALSA PCM timer implementation could cause a NULL-pointer dereference due to a race condition where timer->private_data is accessed before being set. This occurs because the timer is registered in the global timer list before its private_data field is initialized, allowing concurrent access to a NULL pointer.
References
- git.kernel.org/stable/c/27f167e117eca310661fbcbacb352ea08face067 (opens in a new tab)
- git.kernel.org/stable/c/555d168bd98daa46daccc68c908201388c834293 (opens in a new tab)
- git.kernel.org/stable/c/8c869d5cf5affb20994bdbb60e7d46d65c91b55f (opens in a new tab)
- git.kernel.org/stable/c/686c7a6af1eea8d2a919303e4c6bbec3de79dbdc (opens in a new tab)
- git.kernel.org/stable/c/e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd (opens in a new tab)
- git.kernel.org/stable/c/d63f5a9f8121fb43c798056d7dd34c58f47185d7 (opens in a new tab)
- git.kernel.org/stable/c/0b349249d572633d7c8cdeb917623d1676a2b7c3 (opens in a new tab)
- git.kernel.org/stable/c/1e713f9bb2ac583521f06b0eb4e22440b1e3d078 (opens in a new tab)