CVE-2026-98314
ALSA: pcm: set timer->private_data before registering the PCM timer
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 27f167e117eca310661fbcbacb352ea08face067Upgrade to: 27f167e117eca310661fbcbacb352ea08face067Affected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 555d168bd98daa46daccc68c908201388c834293Upgrade to: 555d168bd98daa46daccc68c908201388c834293Affected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8c869d5cf5affb20994bdbb60e7d46d65c91b55fUpgrade to: 8c869d5cf5affb20994bdbb60e7d46d65c91b55fAffected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 686c7a6af1eea8d2a919303e4c6bbec3de79dbdcUpgrade to: 686c7a6af1eea8d2a919303e4c6bbec3de79dbdc + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: set timer->private_data before registering the PCM timer snd_pcm_timer_init() calls snd_device_register() to link the new struct snd_timer into the global timer list while it still carries hw.c_resolution = snd_pcm_timer_resolution (and hw.start/hw.stop), and only afterwards sets timer->private_data = substream. Once the timer is on the list under register_mutex, a concurrent reader can already reach it through the same mutex and invoke these callbacks. /proc/asound/timers does this via c_resolution(), and snd_timer_open()+snd_timer_start() reach start()/stop() the same way. All three dereference timer->private_data, which for this brief window is NULL, giving a NULL-pointer dereference: substream = timer->private_data; return substream->runtime ? ... // substream is NULL Move the private_data/private_free assignment before snd_device_register() so the timer is never visible on the list without its private_data set. On the snd_device_register() failure path, private_free() (snd_pcm_timer_free()) can now run, but it only does substream->timer = NULL, which is already NULL at that point since substream->timer is set to the new timer just once, after a successful registration -- so the failure path stays safe.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/27f167e117eca310661fbcbacb352ea08face067
- git.kernel.org/stable/c/555d168bd98daa46daccc68c908201388c834293
- git.kernel.org/stable/c/8c869d5cf5affb20994bdbb60e7d46d65c91b55f
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI