CVE-2026-90116: Linux kernel · ALSA: mtpav: shut down output timer before card teardown
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in de75857ce374671712e1d9528844e3c0543dcef6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in de75857ce374671712e1d9528844e3c0543dcef6, c73cb5b7c159246dd572277c668851a56e516019, 793163e134028e7136c9dd9e30f7f656de1eabba +2
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: mtpav: shut down output timer before card teardown snd_mtpav_output_timer() rearms chip->timer while holding chip->spinlock and accesses the card-private mtpav state. snd_mtpav_free() currently takes the same lock and calls timer_delete() when the timer is active. This only removes a pending timer; it does not wait for a callback that is already running and does not prevent the callback from rearming the timer. A callback running on another CPU can therefore continue after snd_mtpav_free() releases the lock and access the card-private state while the card is being torn down. It can also rearm the timer after timer_delete() has returned. Call timer_shutdown_sync() without holding chip->spinlock. This waits for any running callback to finish and prevents further rearming before the card-private mtpav state is released.
References
- git.kernel.org/stable/c/793163e134028e7136c9dd9e30f7f656de1eabba (opens in a new tab)
- git.kernel.org/stable/c/de75857ce374671712e1d9528844e3c0543dcef6 (opens in a new tab)
- git.kernel.org/stable/c/392c985c6b03dfdf4904c0d464f18735ca3c4df8 (opens in a new tab)
- git.kernel.org/stable/c/1e16e82581521a2fe20eda29bdc9e75286f7c950 (opens in a new tab)
- git.kernel.org/stable/c/c73cb5b7c159246dd572277c668851a56e516019 (opens in a new tab)