CVE-2026-98314

ALSA: pcm: set timer->private_data before registering the PCM timer

Description

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.

Key facts

Published
6 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.184% likely to be exploited in the next 30 days, higher than 8.116% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 27f167e117eca310661fbcbacb352ea08face067 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 555d168bd98daa46daccc68c908201388c834293 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 8c869d5cf5affb20994bdbb60e7d46d65c91b55f (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 686c7a6af1eea8d2a919303e4c6bbec3de79dbdc (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding d63f5a9f8121fb43c798056d7dd34c58f47185d7 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 0b349249d572633d7c8cdeb917623d1676a2b7c3 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 1e713f9bb2ac583521f06b0eb4e22440b1e3d078 (affected)
LinuxLinux
  • Default status: affected
  • 2.6.12 (affected)
  • 0 up to but excluding 2.6.12 (unaffected)
  • 5.10.271 up to and including 5.10.* (unaffected)
  • 5.15.222 up to and including 5.15.* (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.54 up to and including 6.18.* (unaffected)
  • 7.2.8 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 6 Oct 2026 Published

References