Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
ALSA: timer: Fix UAF at snd_timer_user_params()

In the Linux kernel, the following vulnerability has been resolved: ALSA: timer: Fix UAF at snd_timer_user_params() At releasing a timer object, e.g. when a userspace timer (CONFIG_SND_UTIMER) gets closed and snd_timer_free() is called, it tries to detach the timer instances and release the resources. However, it's still possible that other in-flight tasks are holding the timer instance where the to-be-deleted timer object is associated, and this may lead to racy accesses. Fortunately, most of ioctls dealing with the timer instance list already have the protection with register_mutex, and this also avoids such races. But, SNDRV_TIMER_IOCTL_PARAMS isn't protected, hence the concurrent ioctl may lead to use-after-free. This patch just adds the guard with register_mutex to protect snd_timer_user_params() for covering the code path as a quick workaround. It's no hot-path but rather a rarely issued ioctl, so the performance penalty doesn't matter.

Affected products

Linux
  • <6.1.176
  • =<6.6.*
  • <5.10.259
  • <306427adf9b97e29e5958cb9cf3096c6151fc9ff
  • <5.15.210
  • =<6.18.*
  • <e2331730175f74169046d2af8db1b47243df7c7a
  • <b2214914e461d0466548a52dfe4f4ee8ce362276
  • =<5.10.*
  • =<*
  • <6.12.94
  • =<6.1.*
  • <38034d04d4a75bbca01df2b313ced0bcd0fa3242
  • <6.6.143
  • <117743d62e1225e208568a3ffc2c07214f1347cb
  • <92ad2d7f80cad43b046f093e808e11fe919d304a
  • <3d39da65b5c422c5e5afb7d5651b0698d060a827
  • =<5.15.*
  • =<6.12.*
  • =<7.0.*
  • <053a401b592be424fea9d57c789f66cd5d8cec11
  • <7.0.13
  • <6.18.36