CVE-2026-89979: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-r2rw-736q-8cv3
Share
CVSS 7.8
Published
Advisory Summary

CVE-2026-89979 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-89979 at a Glance

CVE Identifier CVE-2026-89979
GHSA Identifier GHSA-r2rw-736q-8cv3
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-89979

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-89979, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-89979 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89979
git.kernel.org/stable/c/50afadf1ea... WEB
https://git.kernel.org/stable/c/50afadf1ea66597116eb14e73c24da7ae99b759f
git.kernel.org/stable/c/5abeb4f9f2... WEB
https://git.kernel.org/stable/c/5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb
git.kernel.org/stable/c/7ad2ea7c10... WEB
https://git.kernel.org/stable/c/7ad2ea7c10044b08ecf7b04376916faf12e17a99
git.kernel.org/stable/c/acac7b5e07... WEB
https://git.kernel.org/stable/c/acac7b5e07349a9d10d78873afb4b93cd1dc721f
git.kernel.org/stable/c/ad29779736... WEB
https://git.kernel.org/stable/c/ad29779736cfd6f5595f0cab300dd7611418e363
git.kernel.org/stable/c/b1d1214455... WEB
https://git.kernel.org/stable/c/b1d12144557fceed5de6e22e2c2e30a40ed37702
git.kernel.org/stable/c/b2edc017f9... WEB
https://git.kernel.org/stable/c/b2edc017f94c08bdd0b046a586e43ac771a2f942
git.kernel.org/stable/c/b599e7f164... WEB
https://git.kernel.org/stable/c/b599e7f16441386754ec083fa62a549bccb02fca

Frequently Asked Questions

What is CVE-2026-89979?
CVE-2026-89979 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-89979?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-89979?
CVE-2026-89979 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89979?
CVE-2026-89979 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89979?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r2rw-736q-8cv3",
  "modified" : "2026-09-16T15:31:04Z",
  "published" : "2026-09-16T12:30:44Z",
  "aliases" : [ "CVE-2026-89979" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89979"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/50afadf1ea66597116eb14e73c24da7ae99b759f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5abeb4f9f2023f001d693b4e5e1ebbf25e25d0eb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7ad2ea7c10044b08ecf7b04376916faf12e17a99"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/acac7b5e07349a9d10d78873afb4b93cd1dc721f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ad29779736cfd6f5595f0cab300dd7611418e363"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b1d12144557fceed5de6e22e2c2e30a40ed37702"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b2edc017f94c08bdd0b046a586e43ac771a2f942"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b599e7f16441386754ec083fa62a549bccb02fca"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:08Z"
  }
}