CVE-2026-74658: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-m8rg-mx7q-fp2c
Share
Published
Advisory Summary

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

CVE-2026-74658 at a Glance

CVE Identifier CVE-2026-74658
GHSA Identifier GHSA-m8rg-mx7q-fp2c
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-74658

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-74658, 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: futex: Prevent robust futex exit race some more A robust futex unlock stores 0 over the whole futex value - wiping FUTEX_WAITERS - and wakes a single waiter. That wakeup is a one-shot notification: the protocol relies on its recipient to either acquire the futex (and eventually unlock while aware of the remaining contention) or re-arm FUTEX_WAITERS before sleeping again. If the woken waiter is killed before it can do either, the kernel must jump in and wake the next task down the line. This is a known complication of the futex protocol with a previous partial fix in commit ca16d5bee598 ("futex: Prevent robust futex exit race"). Unfortunately, that fix is insufficient. If a third task re-acquired the futex through the uncontended fast path in the meantime, the notification is lost: robust exit processing sees that it is owned by another task and does nothing, while the new owner sees no FUTEX_WAITERS when it unlocks and wakes nobody. The remaining waiters sleep forever behind a free futex: A owns the futex, B and C sleep in FUTEX_WAIT uval == A | FUTEX_WAITERS A robust unlock: store 0, FUTEX_WAKE(1) wakes B uval == 0 D fast path acquire: cmpxchg(0 -> D) uval == D, no FUTEX_WAITERS B killed before acting on the wakeup B exit walk, pending op: owner D != B -> no action D unlock: no FUTEX_WAITERS -> no wake C sleeps forever This is clearly a shortcoming in the implementation, which fails to keep the FUTEX_WAITERS bit consistent. Work around this by augmenting the robust list exit processing to also perform the extra wakeup if the futex word is owned by another thread but FUTEX_WAITERS is not set. This does not fix the problem of a non-contended take over/release and free sequence, which has been discussed for years and has been addressed by commit 3ca9595d9fb6 ("futex: Add support for unlocking robust futexes") and subsequent changes, but failed to take the problem described above into account. A more complete solution which is based on the in kernel unlock of contended robust futexes has been discussed in the context of this change and should show up in mainline sooner than later. [ tglx: Amend change log slightly and fixup coding style ]

References

NVD — CVE-2026-74658 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74658
git.kernel.org/stable/c/33bfa85458... WEB
https://git.kernel.org/stable/c/33bfa85458105d6169ebdb697f692b8bb8025bae
git.kernel.org/stable/c/6d4514ca9c... WEB
https://git.kernel.org/stable/c/6d4514ca9cdf61fec4ec634cf50386f6f7e69748
git.kernel.org/stable/c/7b8c53263f... WEB
https://git.kernel.org/stable/c/7b8c53263f8878bdd12c87e147ac6feca5c05211
git.kernel.org/stable/c/7cf710e70f... WEB
https://git.kernel.org/stable/c/7cf710e70f9bb8ea75f759ebed09871801315992
git.kernel.org/stable/c/83b0f71d5a... WEB
https://git.kernel.org/stable/c/83b0f71d5a313a765754acab51d2ecc5de76e0b9
git.kernel.org/stable/c/925628656b... WEB
https://git.kernel.org/stable/c/925628656b73b70930972ccde421de4f758d8650
git.kernel.org/stable/c/a1c2b7b86a... WEB
https://git.kernel.org/stable/c/a1c2b7b86a946b6b172bce44d74553da2323a36c
git.kernel.org/stable/c/aa5c571901... WEB
https://git.kernel.org/stable/c/aa5c571901c6b22b58373693a4bf889ecab11ff5

Frequently Asked Questions

What is CVE-2026-74658?
CVE-2026-74658 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-74658?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-74658?
CVE-2026-74658 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74658?
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-m8rg-mx7q-fp2c",
  "modified" : "2026-08-22T18:30:28Z",
  "published" : "2026-08-22T18:30:28Z",
  "aliases" : [ "CVE-2026-74658" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Prevent robust futex exit race some more\n\nA robust futex unlock stores 0 over the whole futex value - wiping\nFUTEX_WAITERS - and wakes a single waiter. That wakeup is a one-shot\nnotification: the protocol relies on its recipient to either acquire the\nfutex (and eventually unlock while aware of the remaining contention) or\nre-arm FUTEX_WAITERS before sleeping again.  If the woken waiter is killed\nbefore it can do either, the kernel must jump in and wake the next task\ndown the line.\n\nThis is a known complication of the futex protocol with a previous\npartial fix in commit ca16d5bee598 (\"futex: Prevent robust futex exit\nrace\"). Unfortunately, that fix is insufficient.\n\nIf a third task re-acquired the futex through the uncontended fast\npath in the meantime, the notification is lost: robust exit processing\nsees that it is owned by another task and does nothing, while the new\nowner sees no FUTEX_WAITERS when it unlocks and wakes nobody.\nThe remaining waiters sleep forever behind a free futex:\n\n  A owns the futex, B and C sleep in FUTEX_WAIT\n                                        uval == A | FUTEX_WAITERS\n  A robust unlock: store 0, FUTEX_WAKE(1) wakes B\n                                        uval == 0\n  D fast path acquire: cmpxchg(0 -> D)\n                                        uval == D, no FUTEX_WAITERS\n  B killed before acting on the wakeup\n  B exit walk, pending op: owner D != B -> no action\n  D unlock: no FUTEX_WAITERS -> no wake\n                                        C sleeps forever\n\nThis is clearly a shortcoming in the implementation, which fails to keep\nthe FUTEX_WAITERS bit consistent.\n\nWork around this by augmenting the robust list exit processing to also\nperform the extra wakeup if the futex word is owned by another thread but\nFUTEX_WAITERS is not set.\n\nThis does not fix the problem of a non-contended take over/release and free\nsequence, which has been discussed for years and has been addressed by\ncommit 3ca9595d9fb6 (\"futex: Add support for unlocking robust futexes\") and\nsubsequent changes, but failed to take the problem described above into\naccount.\n\nA more complete solution which is based on the in kernel unlock of\ncontended robust futexes has been discussed in the context of this change\nand should show up in mainline sooner than later.\n\n[ tglx: Amend change log slightly and fixup coding style ]",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74658"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/33bfa85458105d6169ebdb697f692b8bb8025bae"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6d4514ca9cdf61fec4ec634cf50386f6f7e69748"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7b8c53263f8878bdd12c87e147ac6feca5c05211"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7cf710e70f9bb8ea75f759ebed09871801315992"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/83b0f71d5a313a765754acab51d2ecc5de76e0b9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/925628656b73b70930972ccde421de4f758d8650"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a1c2b7b86a946b6b172bce44d74553da2323a36c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aa5c571901c6b22b58373693a4bf889ecab11ff5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-22T16:16:39Z"
  }
}