Skip to main content
VulnerabilityPublished Updated

CVE-2026-53192: Linux kernel · ALSA: timer: Fix UAF at snd_timer_user_params()

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 37745918e0e7575bc40f38da93a99b9fa6406224, < 306427adf9b97e29e5958cb9cf3096c6151fc9ff
Fixed in
  • 306427adf9b97e29e5958cb9cf3096c6151fc9ff
LinuxLinuxAffected
  • ≥ 37745918e0e7575bc40f38da93a99b9fa6406224, < 38034d04d4a75bbca01df2b313ced0bcd0fa3242
Fixed in
  • 38034d04d4a75bbca01df2b313ced0bcd0fa3242
LinuxLinuxAffected
  • ≥ 37745918e0e7575bc40f38da93a99b9fa6406224, < 053a401b592be424fea9d57c789f66cd5d8cec11
Fixed in
  • 053a401b592be424fea9d57c789f66cd5d8cec11
LinuxLinuxAffected
  • ≥ 37745918e0e7575bc40f38da93a99b9fa6406224, < 3d39da65b5c422c5e5afb7d5651b0698d060a827
Fixed in
  • 3d39da65b5c422c5e5afb7d5651b0698d060a827
LinuxLinuxAffected
  • =6.12
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

Community reviews

Loading reviews…