CVE-2026-53192: Linux kernel · ALSA: timer: Fix UAF at snd_timer_user_params()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.8 High · fixed in 306427adf9b97e29e5958cb9cf3096c6151fc9ff : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in 306427adf9b97e29e5958cb9cf3096c6151fc9ff, 38034d04d4a75bbca01df2b313ced0bcd0fa3242, 053a401b592be424fea9d57c789f66cd5d8cec11 +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 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 Linux kernel to 306427adf9b97e29e5958cb9cf3096c6151fc9ff, 38034d04d4a75bbca01df2b313ced0bcd0fa3242, 053a401b592be424fea9d57c789f66cd5d8cec11 or 3d39da65b5c422c5e5afb7d5651b0698d060a827.
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– |
Description
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.
References
- git.kernel.org/stable/c/38034d04d4a75bbca01df2b313ced0bcd0fa3242 (opens in a new tab)
- git.kernel.org/stable/c/3d39da65b5c422c5e5afb7d5651b0698d060a827 (opens in a new tab)
- git.kernel.org/stable/c/306427adf9b97e29e5958cb9cf3096c6151fc9ff (opens in a new tab)
- git.kernel.org/stable/c/053a401b592be424fea9d57c789f66cd5d8cec11 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)