ALSA: timer: Forcibly close timer instances at closing
Summary
| CVE | CVE-2026-53193 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-25 09:16:36 UTC |
| Updated | 2026-06-25 09:16:36 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
ALSA: timer: Forcibly close timer instances at closing
When snd_timer object is freed via snd_timer_free() and still pending
snd_timer_instance objects are assigned to the timer object, it tries
to unlink all instances and just set NULL to each ti->timer, then
releases the resources immediately. The problem is, however, when
there are slave timer instances that are associated with a master
instance linked to this timer: namely, those slave instances still
point to the freed timer object although the master instance is
unlinked, which may lead to user-after-free. The bug can be easily
triggered particularly when a new userspace-driven timers
(CONFIG_SND_UTIMER) is involved, since it can create and delete the
timer object via a simple file open/close, while the other
applications may keep accessing to that timer.
This patch is an attempt to paper over the problem above: now instead
of just unlinking, call snd_timer_close[_locked]() forcibly for each
pending timer instance, so that all assigned slave timer instances are
properly detached, too. Since snd_timer_close() might be called later
by the driver that created that instance, the check of
SNDRV_TIMER_IFLG_DEAD is added at the beginning, too. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 37745918e0e7575bc40f38da93a99b9fa6406224 586b219a22b1032b28b8bd356b963276c5e5bf53 git |
Not specified |
| CNA |
Linux |
Linux |
affected 37745918e0e7575bc40f38da93a99b9fa6406224 f46093dd22969037beb1fce2e043f3236be41c92 git |
Not specified |
| CNA |
Linux |
Linux |
affected 37745918e0e7575bc40f38da93a99b9fa6406224 60e73ab87b84bbd6bd7ddd1d16019a3a3705ab8f git |
Not specified |
| CNA |
Linux |
Linux |
affected 37745918e0e7575bc40f38da93a99b9fa6406224 da3039e91d1f835874ed6e9a33ea19ee80c2cb92 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.12 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.94 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.36 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.13 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/60e73ab87b84bbd6bd7ddd1d16019a3a3705ab8f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/f46093dd22969037beb1fce2e043f3236be41c92 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/586b219a22b1032b28b8bd356b963276c5e5bf53 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/da3039e91d1f835874ed6e9a33ea19ee80c2cb92 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.