CVE-2026-53342: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-w39q-f6gf-xv3r
Share
CVSS 5.5
Published
Advisory Summary

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

CVE-2026-53342 at a Glance

CVE Identifier CVE-2026-53342
GHSA Identifier GHSA-w39q-f6gf-xv3r
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

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

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-53342

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-53342, 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: arm64: mm: call pagetable dtor when freeing hot-removed page tables Since 5e8eb9aeeda3 ("arm64: mm: always call PTE/PMD ctor in __create_pgd_mapping()") page-table allocation on ARM64 always calls pagetable_{pte,pmd,pud,p4d}_ctor(). This sets the page_type to PGTY_table, increments NR_PAGETABLE and possible allocates a PTL. However the matching pagetable_dtor() calls were never added. With DEBUG_VM enabled on kernel versions prior to v6.17 without 2dfcd1608f3a9 ("mm/page_alloc: let page freeing clear any set page type") this leads to the following warning when freeing these pages due to page->page_type sharing page->_mapcount: BUG: Bad page state in process ... pfn:284fbb page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x284fbb flags: 0x17fffc000000000(node=0|zone=2|lastcpupid=0x1ffff) page_type: f2(table) page dumped because: nonzero mapcount Call trace: bad_page+0x13c/0x160 __free_frozen_pages+0x6cc/0x860 ___free_pages+0xf4/0x180 free_pages+0x54/0x80 free_hotplug_page_range.part.0+0x58/0x90 free_empty_tables+0x438/0x500 __remove_pgd_mapping.constprop.0+0x60/0xa8 arch_remove_memory+0x48/0x80 try_remove_memory+0x158/0x1d8 offline_and_remove_memory+0x138/0x180 It can also lead to leaking the ptl allocation if ALLOC_SPLIT_PTLOCKS is defined and incorrect NR_PAGETABLE stats. Fix this by calling pagetable_dtor() in free_hotplug_pgtable_page() prior to freeing the page to undo the effects of calling pagetable_*_ctor().

References

NVD — CVE-2026-53342 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-53342
git.kernel.org/stable/c/95f27fcda6... WEB
https://git.kernel.org/stable/c/95f27fcda681021ed3906d3cae7e68b6a57a1d8e
git.kernel.org/stable/c/aaa688ac9f... WEB
https://git.kernel.org/stable/c/aaa688ac9f18207f7452c6472e647c1febaea6a3
git.kernel.org/stable/c/c594b83457... WEB
https://git.kernel.org/stable/c/c594b83457ccdee76d458416fb3bc9348a37592f

Frequently Asked Questions

What is CVE-2026-53342?
CVE-2026-53342 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-53342?
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-53342?
CVE-2026-53342 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-53342?
CVE-2026-53342 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-53342?
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-w39q-f6gf-xv3r",
  "modified" : "2026-07-24T00:32:32Z",
  "published" : "2026-07-01T15:35:19Z",
  "aliases" : [ "CVE-2026-53342" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: mm: call pagetable dtor when freeing hot-removed page tables\n\nSince 5e8eb9aeeda3 (\"arm64: mm: always call PTE/PMD ctor in\n__create_pgd_mapping()\") page-table allocation on ARM64 always calls\npagetable_{pte,pmd,pud,p4d}_ctor().  This sets the page_type to\nPGTY_table, increments NR_PAGETABLE and possible allocates a PTL.  However\nthe matching pagetable_dtor() calls were never added.\n\nWith DEBUG_VM enabled on kernel versions prior to v6.17 without\n2dfcd1608f3a9 (\"mm/page_alloc: let page freeing clear any set page type\")\nthis leads to the following warning when freeing these pages due to\npage->page_type sharing page->_mapcount:\n\n  BUG: Bad page state in process ... pfn:284fbb\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x284fbb\n  flags: 0x17fffc000000000(node=0|zone=2|lastcpupid=0x1ffff)\n  page_type: f2(table)\n  page dumped because: nonzero mapcount\n  Call trace:\n   bad_page+0x13c/0x160\n   __free_frozen_pages+0x6cc/0x860\n   ___free_pages+0xf4/0x180\n   free_pages+0x54/0x80\n   free_hotplug_page_range.part.0+0x58/0x90\n   free_empty_tables+0x438/0x500\n   __remove_pgd_mapping.constprop.0+0x60/0xa8\n   arch_remove_memory+0x48/0x80\n   try_remove_memory+0x158/0x1d8\n   offline_and_remove_memory+0x138/0x180\n\nIt can also lead to leaking the ptl allocation if ALLOC_SPLIT_PTLOCKS is\ndefined and incorrect NR_PAGETABLE stats.  Fix this by calling\npagetable_dtor() in free_hotplug_pgtable_page() prior to freeing the page\nto undo the effects of calling pagetable_*_ctor().",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-53342"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/95f27fcda681021ed3906d3cae7e68b6a57a1d8e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aaa688ac9f18207f7452c6472e647c1febaea6a3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c594b83457ccdee76d458416fb3bc9348a37592f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-01T14:16:42Z"
  }
}