Answer in brief
CVE-2026-90116 records a Unknown severity vulnerability in ALSA: mtpav: shut down output timer before card teardown. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <392c985c6b03dfdf4904c0d464f18735ca3c4df8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1e16e82581521a2fe20eda29bdc9e75286f7c950 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c73cb5b7c159246dd572277c668851a56e516019 | 392c985c6b03dfdf4904c0d464f18735ca3c4df8, 1e16e82581521a2fe20eda29bdc9e75286f7c950, c73cb5b7c159246dd572277c668851a56e516019 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.