CVE-2026-72215: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-cpm2-25vc-f276
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-72215
GHSA Identifier GHSA-cpm2-25vc-f276
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-72215

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-72215, 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: MIPS: DEC: Ensure 32-bit stack location for o32 prom_printf() In 64-bit configurations calling any firmware entry points from a kernel thread other than the initial one will result in a situation where the stack has been placed in the XKPHYS 64-bit memory segment. Consequently the stack pointer is no longer a 32-bit value and when the 32-bit firmware code called uses 32-bit ALU operations to manipulate the stack pointer, the calculated result is incorrect (in fact in the 64-bit MIPS ISA almost all 32-bit ALU operations will produce an unpredictable result when executed on 64-bit data) and control goes astray. This may happen when no final console driver has been enabled in the configuration and consequently the initial console continues being used late into bootstrap, or with an upcoming change that will switch the zs driver to use a platform device, which in turn will make the console handover happen only after other kernel threads have already been started, and the kernel will hang at: pid_max: default: 32768 minimum: 301 or somewhat later, but always before: cblist_init_generic: Setting adjustable number of callback queues. has been printed. It seems that only the prom_printf() entry point is affected. Of all the other entry points wired only rex_slot_address() and rex_gettcinfo() are called from a kernel thread other than the initial one, specifically kernel_init(), and they are leaf functions that do no business with the stack, having worked with no issue ever since 64-bit support was added for the platform back in 2002. To address this issue then, arrange for the stack to be switched in the o32 wrapper as required for prom_printf() only, by supplying call_o32() with a pointer to a chunk of initdata space, which is placed in the CKSEG0 32-bit compatibility segment, observing that prom_printf() is only called from console output handler and therefore with the console lock held, implying no need for this code to be reentrant. Other firmware entry points may be called with interrupts enabled and no lock held, and may therefore require that call_o32() be reentrant. They trigger no issue at this point and "if it ain't broke, don't fix it," so just leave them alone.

References

NVD — CVE-2026-72215 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72215
git.kernel.org/stable/c/1ed18b5c3b... WEB
https://git.kernel.org/stable/c/1ed18b5c3be9657fe288fa4dae0bef2470598683
git.kernel.org/stable/c/27857db30c... WEB
https://git.kernel.org/stable/c/27857db30c98583e12dd8d939ba2370bce08a5be
git.kernel.org/stable/c/3394757c5d... WEB
https://git.kernel.org/stable/c/3394757c5d3970ab36d2aafa6dd40952b43f0d16
git.kernel.org/stable/c/3ae86630b9... WEB
https://git.kernel.org/stable/c/3ae86630b94f72bf4012c6322f81f622dc4fdf24
git.kernel.org/stable/c/5ff79e8bdc... WEB
https://git.kernel.org/stable/c/5ff79e8bdc75db51e30298a75939e2308e7658e0
git.kernel.org/stable/c/9cd4a8ed12... WEB
https://git.kernel.org/stable/c/9cd4a8ed12d2a6313592e43c14cca5eca6717bee
git.kernel.org/stable/c/d3fd2d358d... WEB
https://git.kernel.org/stable/c/d3fd2d358df0ca712183509cbbed6a16bde1d17e
git.kernel.org/stable/c/d828bca843... WEB
https://git.kernel.org/stable/c/d828bca84311e278093e60b2864a54f4bbb0c2ad

Frequently Asked Questions

What is CVE-2026-72215?
CVE-2026-72215 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-72215?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-72215?
CVE-2026-72215 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72215?
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-cpm2-25vc-f276",
  "modified" : "2026-08-15T06:32:16Z",
  "published" : "2026-08-15T06:32:16Z",
  "aliases" : [ "CVE-2026-72215" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nMIPS: DEC: Ensure 32-bit stack location for o32 prom_printf()\n\nIn 64-bit configurations calling any firmware entry points from a kernel\nthread other than the initial one will result in a situation where the\nstack has been placed in the XKPHYS 64-bit memory segment.\n\nConsequently the stack pointer is no longer a 32-bit value and when the\n32-bit firmware code called uses 32-bit ALU operations to manipulate the\nstack pointer, the calculated result is incorrect (in fact in the 64-bit\nMIPS ISA almost all 32-bit ALU operations will produce an unpredictable\nresult when executed on 64-bit data) and control goes astray.\n\nThis may happen when no final console driver has been enabled in the\nconfiguration and consequently the initial console continues being used\nlate into bootstrap, or with an upcoming change that will switch the zs\ndriver to use a platform device, which in turn will make the console\nhandover happen only after other kernel threads have already been\nstarted, and the kernel will hang at:\n\n  pid_max: default: 32768 minimum: 301\n\nor somewhat later, but always before:\n\n  cblist_init_generic: Setting adjustable number of callback queues.\n\nhas been printed.\n\nIt seems that only the prom_printf() entry point is affected.  Of all\nthe other entry points wired only rex_slot_address() and rex_gettcinfo()\nare called from a kernel thread other than the initial one, specifically\nkernel_init(), and they are leaf functions that do no business with the\nstack, having worked with no issue ever since 64-bit support was added\nfor the platform back in 2002.\n\nTo address this issue then, arrange for the stack to be switched in the\no32 wrapper as required for prom_printf() only, by supplying call_o32()\nwith a pointer to a chunk of initdata space, which is placed in the\nCKSEG0 32-bit compatibility segment, observing that prom_printf() is\nonly called from console output handler and therefore with the console\nlock held, implying no need for this code to be reentrant.\n\nOther firmware entry points may be called with interrupts enabled and no\nlock held, and may therefore require that call_o32() be reentrant.  They\ntrigger no issue at this point and \"if it ain't broke, don't fix it,\" so\njust leave them alone.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72215"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1ed18b5c3be9657fe288fa4dae0bef2470598683"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/27857db30c98583e12dd8d939ba2370bce08a5be"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3394757c5d3970ab36d2aafa6dd40952b43f0d16"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3ae86630b94f72bf4012c6322f81f622dc4fdf24"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5ff79e8bdc75db51e30298a75939e2308e7658e0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9cd4a8ed12d2a6313592e43c14cca5eca6717bee"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d3fd2d358df0ca712183509cbbed6a16bde1d17e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d828bca84311e278093e60b2864a54f4bbb0c2ad"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:40Z"
  }
}