← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-53193

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-53193

Key Details

CVECVE-2026-53193
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-416 (Use After Free)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-53193
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-53193
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.