Bug 2492792 (CVE-2026-53192) - CVE-2026-53192 kernel: ALSA: timer: Fix UAF at snd_timer_user_params()
Summary: CVE-2026-53192 kernel: ALSA: timer: Fix UAF at snd_timer_user_params()
Keywords:
Status: NEW
Alias: CVE-2026-53192
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-25 10:05 UTC by OSIDB Bzimport
Modified: 2026-09-17 12:15 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:68507 0 None None None 2026-09-17 05:45:11 UTC
Red Hat Product Errata RHSA-2026:68531 0 None None None 2026-09-17 07:20:51 UTC
Red Hat Product Errata RHSA-2026:68532 0 None None None 2026-09-17 06:56:56 UTC
Red Hat Product Errata RHSA-2026:68570 0 None None None 2026-09-17 12:15:55 UTC

Description OSIDB Bzimport 2026-06-25 10:05:59 UTC
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.

Comment 3 Jon Orris 2026-09-17 05:45:10 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:68507 https://access.redhat.com/errata/RHSA-2026:68507

Comment 4 Jon Orris 2026-09-17 06:56:55 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:68532 https://access.redhat.com/errata/RHSA-2026:68532

Comment 5 Jon Orris 2026-09-17 07:20:50 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:68531 https://access.redhat.com/errata/RHSA-2026:68531

Comment 6 Jon Orris 2026-09-17 12:15:54 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:68570 https://access.redhat.com/errata/RHSA-2026:68570


Note You need to log in before you can comment on or make changes to this bug.