Shellfeed logo Shellfeed

CVE-2026-98314 · UNKNOWN

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

EPSS: 0.2% probability of exploitation in the next 30 days (percentile 8.1).

Details

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.

Affected packages

  • GIT git.kernel.org/pub/scm/linux/kernel/git/stable/linux [1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – 27f167e117eca310661fbcbacb352ea08face067]
  • Linux Kernel [2.6.12 – 5.10.271] [5.11.0 – 5.15.222] [5.16.0 – 6.1.189] [6.2.0 – 6.6.158] [6.7.0 – 6.12.112] [6.13.0 – 6.18.54] [6.19.0 – 7.2.8]

References