CVE-2026-72422: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-2r52-5q5c-m3mp
Share
CVSS 9.8
Published
Advisory Summary

CVE-2026-72422 is a CRITICAL (CVSS 9.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-72422 at a Glance

CVE Identifier CVE-2026-72422
GHSA Identifier GHSA-2r52-5q5c-m3mp
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.8

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

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
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-72422

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-72422, 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: ksmbd: fix use-after-free of conn->preauth_info in concurrent SMB2 NEGOTIATE conn->preauth_info is shared connection state (struct preauth_integrity_info, kmalloc-96) that is allocated and freed by the SMB2 NEGOTIATE handler and read by the response send path. smb2_handle_negotiate() allocates conn->preauth_info, and on a deassemble_neg_contexts() failure kfrees it and sets it to NULL. Both the allocation and the free/NULL happen under ksmbd_conn_lock(conn) (the connection srv_mutex), which is held across the whole handler body. The response send path smb3_preauth_hash_rsp(), called from the send: block of __handle_ksmbd_work(), reads conn->preauth_info and dereferences conn->preauth_info->Preauth_HashValue (via ksmbd_gen_preauth_integrity_hash()) without taking conn_lock. When a client drives two SMB2 NEGOTIATE requests on the same connection, one worker can free conn->preauth_info on the failing-negotiate path while a concurrent send-path worker is reading it, producing a slab use-after-free read (KASAN-confirmed). The send-path read tested conn->preauth_info for NULL but raced with the free that occurs between the NULL check and the dereference, so the NULL guard alone does not close the window. Serialize the NEGOTIATE-branch read in smb3_preauth_hash_rsp() under ksmbd_conn_lock(conn) and re-check conn->preauth_info inside the lock. Because the negotiate handler holds conn_lock across its kfree + NULL assignment, a reader that also takes conn_lock either runs fully before the allocation or fully after the NULL store, and can never observe the freed-but-not-yet-NULLed pointer. ksmbd_gen_preauth_integrity_hash() takes no locks itself (it only computes a SHA-512 over the buffer), so no lock-ordering inversion is introduced, and conn_lock is a sleepable mutex which is safe on this send path (it already performs network I/O).

References

NVD — CVE-2026-72422 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72422
git.kernel.org/stable/c/0c05422747... WEB
https://git.kernel.org/stable/c/0c054227479ed7e36ebccb3a558bc0ef698264f6
git.kernel.org/stable/c/16a1ecf39c... WEB
https://git.kernel.org/stable/c/16a1ecf39c217e3d164bd32ef2a4f650abc067fa
git.kernel.org/stable/c/1c89da3baa... WEB
https://git.kernel.org/stable/c/1c89da3baa2b1f269178afa87dc30479b8535776
git.kernel.org/stable/c/7470511d08... WEB
https://git.kernel.org/stable/c/7470511d085af1c7a043a60e53d52b512d5a10b1
git.kernel.org/stable/c/77bb0bbfcc... WEB
https://git.kernel.org/stable/c/77bb0bbfcc4e777ca653174689e5e363f8ee63d1
git.kernel.org/stable/c/c7bef84740... WEB
https://git.kernel.org/stable/c/c7bef84740d1d57848c74f6f5b996606e43ea4fe
git.kernel.org/stable/c/d0a469122e... WEB
https://git.kernel.org/stable/c/d0a469122e7bf8338fec1949fb1e8e1290ed8caa

Frequently Asked Questions

What is CVE-2026-72422?
CVE-2026-72422 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-72422?
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-72422?
CVE-2026-72422 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72422?
CVE-2026-72422 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72422?
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-2r52-5q5c-m3mp",
  "modified" : "2026-08-17T06:33:29Z",
  "published" : "2026-08-15T06:32:24Z",
  "aliases" : [ "CVE-2026-72422" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free of conn->preauth_info in concurrent SMB2 NEGOTIATE\n\nconn->preauth_info is shared connection state (struct\npreauth_integrity_info, kmalloc-96) that is allocated and freed by the\nSMB2 NEGOTIATE handler and read by the response send path.\n\nsmb2_handle_negotiate() allocates conn->preauth_info, and on a\ndeassemble_neg_contexts() failure kfrees it and sets it to NULL. Both the\nallocation and the free/NULL happen under ksmbd_conn_lock(conn) (the\nconnection srv_mutex), which is held across the whole handler body.\n\nThe response send path smb3_preauth_hash_rsp(), called from the send:\nblock of __handle_ksmbd_work(), reads conn->preauth_info and dereferences\nconn->preauth_info->Preauth_HashValue (via\nksmbd_gen_preauth_integrity_hash()) without taking conn_lock. When a\nclient drives two SMB2 NEGOTIATE requests on the same connection, one\nworker can free conn->preauth_info on the failing-negotiate path while a\nconcurrent send-path worker is reading it, producing a slab\nuse-after-free read (KASAN-confirmed).\n\nThe send-path read tested conn->preauth_info for NULL but raced with the\nfree that occurs between the NULL check and the dereference, so the NULL\nguard alone does not close the window.\n\nSerialize the NEGOTIATE-branch read in smb3_preauth_hash_rsp() under\nksmbd_conn_lock(conn) and re-check conn->preauth_info inside the lock.\nBecause the negotiate handler holds conn_lock across its kfree + NULL\nassignment, a reader that also takes conn_lock either runs fully before\nthe allocation or fully after the NULL store, and can never observe the\nfreed-but-not-yet-NULLed pointer. ksmbd_gen_preauth_integrity_hash()\ntakes no locks itself (it only computes a SHA-512 over the buffer), so\nno lock-ordering inversion is introduced, and conn_lock is a sleepable\nmutex which is safe on this send path (it already performs network I/O).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72422"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0c054227479ed7e36ebccb3a558bc0ef698264f6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/16a1ecf39c217e3d164bd32ef2a4f650abc067fa"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1c89da3baa2b1f269178afa87dc30479b8535776"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7470511d085af1c7a043a60e53d52b512d5a10b1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/77bb0bbfcc4e777ca653174689e5e363f8ee63d1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c7bef84740d1d57848c74f6f5b996606e43ea4fe"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d0a469122e7bf8338fec1949fb1e8e1290ed8caa"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:15Z"
  }
}