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-89979

ALSA: pcm: Fix race between non-atomic ops and trigger-start

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix race between non-atomic ops and trigger-start We protect the races of the concurrent state transitions between atomic PCM ops, but the checks between the non-atomic ops (hw_params, hw_free and prepare) and the atomic ops aren't perfect; there is a check of the conflicting PCM state at the beginning of hw_params & co, but the atomic PCM ops can be still issued during the non-atomic PCM operations. An example such scenario is that a thread A re-issues the PREPARE or HW_PARAMS for the already prepared stream, while another thread B triggers the PCM start in the middle of the prepare operation. Although this usually doesn't lead to much serious issues, it can give some inconsistency as reported by syzkaller (such as ODEBUG warning). There are various atomic PCM ops, and basically the only problem is the PCM start as it operates from the PREPARED state. Other trigger commands (stop, etc) are for the running or the other special state, hence they are filtered as pre-condition. This patch is for preventing the PCM trigger-start during the non- atomic operations in order to address the problems above. Fortunately, the hw_params, hw_free and prepare operations call snd_pcm_buffer_access_lock(), and this can be used for checking the concurrent operations at the PCM trigger -- which sets the runtime->buffer_accessing to a negative (if possible), so the PCM trigger just needs to check the runtime->buffer_accessing value; if it's negative, it means the concurrent non-atomic PCM ops is running.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 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

CVSS scores of CVE-2026-89979, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b1d12144557fceed5de6e22e2c2e30a40ed37702
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b2edc017f94c08bdd0b046a586e43ac771a2f942
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b599e7f16441386754ec083fa62a549bccb02fca
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ad29779736cfd6f5595f0cab300dd7611418e363
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7ad2ea7c10044b08ecf7b04376916faf12e17a99
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 50afadf1ea66597116eb14e73c24da7ae99b759f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < acac7b5e07349a9d10d78873afb4b93cd1dc721f
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .