CVE-2026-53193
Last modified
CVE-2026-53193 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.12, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53193?
How severe is CVE-2026-53193?
How do I fix CVE-2026-53193?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53188In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53189In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5319A security vulnerability has been detected in itsourcecode P…4.3
- CVE-2026-53190In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53191In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53192In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53194In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53195In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53196In the Linux kernel, the following vulnerability has been re…6.8
- CVE-2026-53197In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53198In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53199In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2026-53193?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
