Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90116ALSA: mtpav: shut down output timer before card teardown

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a9435a1f14a6f9520452617343ea59bb35ba9e79
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 793163e134028e7136c9dd9e30f7f656de1eabba
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < de75857ce374671712e1d9528844e3c0543dcef6
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 392c985c6b03dfdf4904c0d464f18735ca3c4df8
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1e16e82581521a2fe20eda29bdc9e75286f7c950
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c73cb5b7c159246dd572277c668851a56e516019
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90116 badge
[![CVE-2026-90116](https://cveledger.app/badge/CVE-2026-90116.svg)](https://cveledger.app/cve/CVE-2026-90116)

Record last updated .