{"cve":"CVE-2026-89979","nvd":{"published":"2026-09-16T11:17:08.770","modified":"2026-10-19T09:18:44.710","status":"Received","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: pcm: Fix race between non-atomic ops and trigger-start\n\nWe protect the races of the concurrent state transitions between\natomic PCM ops, but the checks between the non-atomic ops (hw_params,\nhw_free and prepare) and the atomic ops aren't perfect; there is a\ncheck of the conflicting PCM state at the beginning of hw_params & co,\nbut the atomic PCM ops can be still issued during the non-atomic PCM\noperations.  An example such scenario is that a thread A re-issues the\nPREPARE or HW_PARAMS for the already prepared stream, while another\nthread B triggers the PCM start in the middle of the prepare\noperation.  Although this usually doesn't lead to much serious issues,\nit can give some inconsistency as reported by syzkaller (such as\nODEBUG warning).\n\nThere are various atomic PCM ops, and basically the only problem is\nthe PCM start as it operates from the PREPARED state.  Other trigger\ncommands (stop, etc) are for the running or the other special state,\nhence they are filtered as pre-condition.\n\nThis patch is for preventing the PCM trigger-start during the non-\natomic operations in order to address the problems above.\nFortunately, the hw_params, hw_free and prepare operations call\nsnd_pcm_buffer_access_lock(), and this can be used for checking the\nconcurrent operations at the PCM trigger -- which sets the\nruntime->buffer_accessing to a negative (if possible), so the PCM\ntrigger just needs to check the runtime->buffer_accessing value; if\nit's negative, it means the concurrent non-atomic PCM ops is running.","cvss_v4":null,"cvss_v3":{"version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","score":7.8},"cwes":[],"references":["https://git.kernel.org/stable/c/50afadf1ea66597116eb14e73c24da7ae99b759f","https://git.kernel.org/stable/c/5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb","https://git.kernel.org/stable/c/7ad2ea7c10044b08ecf7b04376916faf12e17a99","https://git.kernel.org/stable/c/acac7b5e07349a9d10d78873afb4b93cd1dc721f","https://git.kernel.org/stable/c/ad29779736cfd6f5595f0cab300dd7611418e363"],"products":[],"source":"nvd","synced_at":"2026-10-19T22:54:41.405518556+00:00"},"epss":{"cve":"CVE-2026-89979","score":0.00169,"percentile":0.06188,"date":"2026-10-25"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}