CVE-2026-80592: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-m63c-95f6-2rwg
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-80592
GHSA Identifier GHSA-m63c-95f6-2rwg
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-80592

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-80592, 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: samples/damon/mtier: fail early if address range parameters are invalid The comment on top of `struct damon_region` clearly says that For any use case, @ar should be non-zero positive size. which is now verified in damon_verify_new_region() if the kernel is built with DAMON_DEBUG_SANITY. The WARN_ONCE() can be triggered if the mtier sample module is enabled before node{0,1}_{start,end}_addr have been properly initialized, which is obviously not good. ------------[ cut here ]------------ start 0 >= end 0 WARNING: mm/damon/core.c:217 at damon_new_region+0xf4/0x118, CPU#59: bash/341468 Call trace: damon_new_region+0xf4/0x118 (P) damon_set_regions+0xfc/0x3c0 damon_sample_mtier_build_ctx+0xe8/0x3a8 damon_sample_mtier_start+0x1c/0x90 damon_sample_mtier_enable_store+0x98/0xb0 param_attr_store+0xb4/0x128 module_attr_store+0x2c/0x50 sysfs_kf_write+0x58/0x90 kernfs_fop_write_iter+0x16c/0x238 vfs_write+0x2c0/0x370 ksys_write+0x74/0x118 __arm64_sys_write+0x24/0x38 invoke_syscall+0xa8/0x118 el0_svc_common.constprop.0+0x48/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x54/0x370 el0t_64_sync_handler+0xa0/0xe8 el0t_64_sync+0x1ac/0x1b0 ---[ end trace 0000000000000000 ]--- Note that the same issue can happen if detect_node_addresses is true, and node 0 or 1 is memoryless. Fix it together by checking the validity of parameters right before damon_new_region() and fail early if they're invalid.

References

NVD — CVE-2026-80592 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80592
git.kernel.org/stable/c/7746d72c64... WEB
https://git.kernel.org/stable/c/7746d72c64054976887928d64d2caf25c5a6dcc0
git.kernel.org/stable/c/9d360fb820... WEB
https://git.kernel.org/stable/c/9d360fb820a3b9576d155e720ec44fef54d2efb5
git.kernel.org/stable/c/db20589d7b... WEB
https://git.kernel.org/stable/c/db20589d7b248211f63f4a7f642a49c0832b13ae

Frequently Asked Questions

What is CVE-2026-80592?
CVE-2026-80592 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-80592?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80592?
CVE-2026-80592 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80592?
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-m63c-95f6-2rwg",
  "modified" : "2026-08-28T09:31:45Z",
  "published" : "2026-08-28T09:31:45Z",
  "aliases" : [ "CVE-2026-80592" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsamples/damon/mtier: fail early if address range parameters are invalid\n\nThe comment on top of `struct damon_region` clearly says that\n\n    For any use case, @ar should be non-zero positive size.\n\nwhich is now verified in damon_verify_new_region() if the kernel is built\nwith DAMON_DEBUG_SANITY.\n\nThe WARN_ONCE() can be triggered if the mtier sample module is enabled\nbefore node{0,1}_{start,end}_addr have been properly initialized, which is\nobviously not good.\n\n ------------[ cut here ]------------\n start 0 >= end 0\n WARNING: mm/damon/core.c:217 at damon_new_region+0xf4/0x118, CPU#59: bash/341468\n Call trace:\n  damon_new_region+0xf4/0x118 (P)\n  damon_set_regions+0xfc/0x3c0\n  damon_sample_mtier_build_ctx+0xe8/0x3a8\n  damon_sample_mtier_start+0x1c/0x90\n  damon_sample_mtier_enable_store+0x98/0xb0\n  param_attr_store+0xb4/0x128\n  module_attr_store+0x2c/0x50\n  sysfs_kf_write+0x58/0x90\n  kernfs_fop_write_iter+0x16c/0x238\n  vfs_write+0x2c0/0x370\n  ksys_write+0x74/0x118\n  __arm64_sys_write+0x24/0x38\n  invoke_syscall+0xa8/0x118\n  el0_svc_common.constprop.0+0x48/0xf0\n  do_el0_svc+0x24/0x38\n  el0_svc+0x54/0x370\n  el0t_64_sync_handler+0xa0/0xe8\n  el0t_64_sync+0x1ac/0x1b0\n ---[ end trace 0000000000000000 ]---\n\nNote that the same issue can happen if detect_node_addresses is true, and\nnode 0 or 1 is memoryless.  Fix it together by checking the validity of\nparameters right before damon_new_region() and fail early if they're\ninvalid.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80592"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7746d72c64054976887928d64d2caf25c5a6dcc0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9d360fb820a3b9576d155e720ec44fef54d2efb5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/db20589d7b248211f63f4a7f642a49c0832b13ae"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-28T08:16:42Z"
  }
}