Answer in brief
CVE-2026-89979 records a High severity (CVSS 7.8) vulnerability in ALSA: pcm: Fix race between non-atomic ops and trigger-start. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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.
CVSS is 7.8. 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b1d12144557fceed5de6e22e2c2e30a40ed37702 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b2edc017f94c08bdd0b046a586e43ac771a2f942 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b599e7f16441386754ec083fa62a549bccb02fca || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ad29779736cfd6f5595f0cab300dd7611418e363 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7ad2ea7c10044b08ecf7b04376916faf12e17a99 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50afadf1ea66597116eb14e73c24da7ae99b759f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <acac7b5e07349a9d10d78873afb4b93cd1dc721f | b1d12144557fceed5de6e22e2c2e30a40ed37702, b2edc017f94c08bdd0b046a586e43ac771a2f942, b599e7f16441386754ec083fa62a549bccb02fca, ad29779736cfd6f5595f0cab300dd7611418e363, 5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb, 7ad2ea7c10044b08ecf7b04376916faf12e17a99, 50afadf1ea66597116eb14e73c24da7ae99b759f, acac7b5e07349a9d10d78873afb4b93cd1dc721f |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b1d12144557fceed5de6e22e2c2e30a40ed37702 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b2edc017f94c08bdd0b046a586e43ac771a2f942 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b599e7f16441386754ec083fa62a549bccb02fca || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ad29779736cfd6f5595f0cab300dd7611418e363 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7ad2ea7c10044b08ecf7b04376916faf12e17a99 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50afadf1ea66597116eb14e73c24da7ae99b759f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <acac7b5e07349a9d10d78873afb4b93cd1dc721f || >=0 <5.10.270 || >=0 <5.15.221 || >=0 <6.1.188 || >=0 <6.6.157 || >=0 <6.12.110 || >=0 <6.18.51 || >=0 <7.2.5 | b1d12144557fceed5de6e22e2c2e30a40ed37702, b2edc017f94c08bdd0b046a586e43ac771a2f942, b599e7f16441386754ec083fa62a549bccb02fca, ad29779736cfd6f5595f0cab300dd7611418e363, 5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb, 7ad2ea7c10044b08ecf7b04376916faf12e17a99, 50afadf1ea66597116eb14e73c24da7ae99b759f, acac7b5e07349a9d10d78873afb4b93cd1dc721f, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5 |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.