CVE-2026-89979Hinoki check available

PCM state inconsistency via concurrent trigger-start

Published Sep 16, 2026 · Updated Sep 16, 2026

Race condition in the ALSA PCM core allows local users to cause inconsistent stream state by concurrently starting a prepared stream. The snd_pcm_pre_start function checks only that the runtime is PREPARED and fails to reject trigger-start while hw_params, hw_free, or prepare holds buffer access. Reaching the flaw requires PCM device access and overlapping setup with trigger-start; reported consequences are limited to state inconsistency and kernel debug warnings.

CVSS severityUnavailable
Unscored
EPSS probabilityUnavailable
No score available in this record
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in the ALSA PCM core allows local users to cause inconsistent stream state by concurrently starting a prepared stream. The snd_pcm_pre_start function checks only that the runtime is PREPARED and fails to reject trigger-start while hw_params, hw_free, or prepare holds buffer access. Reaching the flaw requires PCM device access and overlapping setup with trigger-start; reported consequences are limited to state inconsistency and kernel debug warnings.

The record

CVE
CVE-2026-89979
Published
Sep 16, 2026
Updated
Sep 16, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 16, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 16, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <5.10.270
  2. Affected versionversion=0 <5.15.221
  3. Affected versionversion=0 <6.1.188
  4. Affected versionversion=0 <6.12.110
  5. Affected versionversion=0 <6.18.51
  6. Affected versionversion=0 <6.6.157
  7. Affected versionversion=0 <7.2.5
  8. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50afadf1ea66597116eb14e73c24da7ae99b759f
  9. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb
  10. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7ad2ea7c10044b08ecf7b04376916faf12e17a99
  11. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <acac7b5e07349a9d10d78873afb4b93cd1dc721f
  12. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ad29779736cfd6f5595f0cab300dd7611418e363
  13. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b1d12144557fceed5de6e22e2c2e30a40ed37702
  14. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b2edc017f94c08bdd0b046a586e43ac771a2f942
  15. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b599e7f16441386754ec083fa62a549bccb02fca

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=0 <5.10.270; version=0 <5.15.221; version=0 <6.1.188; version=0 <6.12.110; version=0 <6.18.51; version=0 <6.6.157; version=0 <7.2.5; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50afadf1ea66597116eb14e73c24da7ae99b759f; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7ad2ea7c10044b08ecf7b04376916faf12e17a99; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <acac7b5e07349a9d10d78873afb4b93cd1dc721f; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ad29779736cfd6f5595f0cab300dd7611418e363; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b1d12144557fceed5de6e22e2c2e30a40ed37702; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b2edc017f94c08bdd0b046a586e43ac771a2f942; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b599e7f16441386754ec083fa62a549bccb02fca

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo