CVE-2026-72323: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-ghfh-7xfw-63jp
Share
CVSS 9.8
Published
Advisory Summary

CVE-2026-72323 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-72323 at a Glance

CVE Identifier CVE-2026-72323
GHSA Identifier GHSA-ghfh-7xfw-63jp
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-72323

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-72323, 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: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() A race condition exists between device teardown (inetdev_destroy) and incoming IGMP query processing (igmp_rcv), leading to a Use-After-Free in the IGMP timer callback. During device destruction, inetdev_destroy() drops the primary reference to in_device, which can drop its refcount to 0. The actual freeing of in_device memory is deferred via RCU (using call_rcu()). Concurrently, igmp_rcv() runs under RCU read lock and obtains the in_device pointer. Because the memory is RCU-protected, CPU-0 can safely dereference in_device even if its refcount has hit 0. However, if CPU-0 calls igmp_gq_start_timer() and re-arms the timer, it attempts to acquire a reference using in_dev_hold(). This increments the refcount from 0 to 1, triggering a "refcount_t: addition on 0" warning. Since the in_device memory is still scheduled to be freed after the RCU grace period (as the free callback does not check the refcount again), the device is freed while the timer is still armed. When the timer expires, it accesses the freed memory, causing a kernel panic. Fix this by using refcount_inc_not_zero() (via a new helper in_dev_hold_safe()) to prevent acquiring a reference if the device is already being destroyed. If the refcount is 0, we do not arm the timer. A similar issue in IPv6 MLD is fixed in a subsequent patch.

References

NVD — CVE-2026-72323 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72323
git.kernel.org/stable/c/1652583033... WEB
https://git.kernel.org/stable/c/165258303357e54b75fc19b341ae2a2b7c9e3910
git.kernel.org/stable/c/40a1e998cb... WEB
https://git.kernel.org/stable/c/40a1e998cb266ed4cb529a0bb4fee2b0ba732702
git.kernel.org/stable/c/7265c747ee... WEB
https://git.kernel.org/stable/c/7265c747eec415ca3109a6a14a419f7ae433b780
git.kernel.org/stable/c/74b301f7f1... WEB
https://git.kernel.org/stable/c/74b301f7f197517016befb5f5dfab01f7bc64be5
git.kernel.org/stable/c/75e984fe0c... WEB
https://git.kernel.org/stable/c/75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea3
git.kernel.org/stable/c/7b19c0f81e... WEB
https://git.kernel.org/stable/c/7b19c0f81ed1fdaec6bc522569be367199a9edf3
git.kernel.org/stable/c/8d4394ffa4... WEB
https://git.kernel.org/stable/c/8d4394ffa40508e0de72f464af351f6ca6a6cdc3
git.kernel.org/stable/c/d107b4c4f8... WEB
https://git.kernel.org/stable/c/d107b4c4f8274763b7ea5ab05d45cef78e4b81ba

Frequently Asked Questions

What is CVE-2026-72323?
CVE-2026-72323 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-72323?
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-72323?
CVE-2026-72323 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-72323?
CVE-2026-72323 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72323?
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-ghfh-7xfw-63jp",
  "modified" : "2026-09-02T15:34:25Z",
  "published" : "2026-08-15T06:32:20Z",
  "aliases" : [ "CVE-2026-72323" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: igmp: Fix potential UAF in igmp_gq_start_timer()\n\nA race condition exists between device teardown (inetdev_destroy) and\nincoming IGMP query processing (igmp_rcv), leading to a Use-After-Free\nin the IGMP timer callback.\n\nDuring device destruction, inetdev_destroy() drops the primary reference\nto in_device, which can drop its refcount to 0. The actual freeing of\nin_device memory is deferred via RCU (using call_rcu()).\n\nConcurrently, igmp_rcv() runs under RCU read lock and obtains the\nin_device pointer. Because the memory is RCU-protected, CPU-0 can safely\ndereference in_device even if its refcount has hit 0.\n\nHowever, if CPU-0 calls igmp_gq_start_timer() and re-arms the timer, it\nattempts to acquire a reference using in_dev_hold(). This increments the\nrefcount from 0 to 1, triggering a \"refcount_t: addition on 0\" warning.\nSince the in_device memory is still scheduled to be freed after the RCU\ngrace period (as the free callback does not check the refcount again),\nthe device is freed while the timer is still armed. When the timer\nexpires, it accesses the freed memory, causing a kernel panic.\n\nFix this by using refcount_inc_not_zero() (via a new helper\nin_dev_hold_safe()) to prevent acquiring a reference if the device is\nalready being destroyed. If the refcount is 0, we do not arm the timer.\n\nA similar issue in IPv6 MLD is fixed in a subsequent patch.",
  "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-72323"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/165258303357e54b75fc19b341ae2a2b7c9e3910"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/40a1e998cb266ed4cb529a0bb4fee2b0ba732702"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7265c747eec415ca3109a6a14a419f7ae433b780"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/74b301f7f197517016befb5f5dfab01f7bc64be5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/75e984fe0cb9e7fbde0c8ee838c61ce8573d3ea3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7b19c0f81ed1fdaec6bc522569be367199a9edf3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8d4394ffa40508e0de72f464af351f6ca6a6cdc3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d107b4c4f8274763b7ea5ab05d45cef78e4b81ba"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:05Z"
  }
}