CVE-2026-52923: Software Security Vulnerability Vulnerability

HIGH

Advisory Identifier: GHSA-m237-4jxg-w5jh

CVSS 7.8

Published 2026-06-24

Advisory Summary

CVE-2026-52923 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-20: Improper Input Validation) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-52923 at a Glance

CVE Identifier CVE-2026-52923

GHSA Identifier GHSA-m237-4jxg-w5jh

Severity HIGH

CVSS v3.1 Base Score 7.8

CWE Classification CWE-20: Improper Input Validation

Affected Product Software

Package Ecosystem Maven

Published Date 2026-06-24

Last Updated 2026-10-15

Security Impact

CVSS: 7.8

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:H/I:H/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 High (C:H)

Integrity High (I:H)

Availability High (A:H)

How to Fix CVE-2026-52923

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-52923, 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 CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. 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: ipc: limit next_id allocation to the valid ID range The checkpoint/restore sysctl path can request the next SysV IPC id through ids->next_id. ipc_idr_alloc() currently forwards that request to idr_alloc() with an open-ended upper bound. If the valid tail of the SysV IPC id space is full, the allocation can spill beyond ipc_mni. The returned SysV IPC id still uses the normal index encoding, so later lookup and removal can target the wrong slot. This leaves the real IDR entry behind and breaks the IDR state for the object. The bug is in ipc_idr_alloc() in the checkpoint/restore path. 1. ids->next_id is passed to: idr_alloc(&ids->ipcs_idr, new, ipcid_to_idx(next_id), 0, ...) 2. The zero upper bound makes the allocation effectively open-ended. Once the valid SysV IPC tail is occupied, idr_alloc() can spill past ipc_mni and allocate an entry beyond the valid IPC id range. 3. The new object id is still encoded with the narrower SysV IPC index width: new->id = (new->seq << ipcmni_seq_shift()) + idx 4. Later removal goes through ipc_rmid(), which uses: ipcid_to_idx(ipcp->id) That truncates the real IDR index. An object actually stored at a high index can then be removed as if it lived at a low in-range index. 5. For shared memory, shm_destroy() frees the current object anyway, but the real high IDR slot is left behind as a dangling pointer. 6. A subsequent walk of /proc/sysvipc/shm reaches the stale IDR entry and dereferences freed memory. Prevent this by bounding the requested allocation to ipc_mni so the checkpoint/restore path fails once the valid range is exhausted.

References

NVD — CVE-2026-52923 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-52923

Software Security Information SECURITY

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52923.json

git.kernel.org/stable/c/fa0b9b2b7a... WEB

https://git.kernel.org/stable/c/fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139

git.kernel.org/stable/c/bd4be70669... WEB

https://git.kernel.org/stable/c/bd4be70669af55b974860d13680348cfdf50bbed

git.kernel.org/stable/c/af24e202b5... WEB

https://git.kernel.org/stable/c/af24e202b543ded8a34f1d5d3db54eb916173f04

git.kernel.org/stable/c/a3cc795129... WEB

https://git.kernel.org/stable/c/a3cc795129e5ec0f8948653a3bf471e7d8852f5e

git.kernel.org/stable/c/8c58a92849... WEB

https://git.kernel.org/stable/c/8c58a92849175f5e2ab7bc2734b3b89afe79f6ef

git.kernel.org/stable/c/41058d4c3f... WEB

https://git.kernel.org/stable/c/41058d4c3f63ab64901560a704882e0565f4e456

git.kernel.org/stable/c/3bbe2bb911... WEB

https://git.kernel.org/stable/c/3bbe2bb9111ce6967a951bfac79af142d816fae5

git.kernel.org/stable/c/157ce2c683... WEB

https://git.kernel.org/stable/c/157ce2c6836ce0ff19108a819f38df061345425f

cert-portal.siemens.com/productcert/html/ss... WEB

https://cert-portal.siemens.com/productcert/html/ssa-784472.html

bugzilla.redhat.com/show_bug.cgi WEB

https://bugzilla.redhat.com/show_bug.cgi?id=2492094

Software Security Information SECURITY

https://access.redhat.com/security/cve/CVE-2026-52923

access.redhat.com/errata/rhsa-2026:63... WEB

https://access.redhat.com/errata/RHSA-2026:63189

access.redhat.com/errata/rhsa-2026:61... WEB

https://access.redhat.com/errata/RHSA-2026:61692

access.redhat.com/errata/rhsa-2026:53... WEB

https://access.redhat.com/errata/RHSA-2026:53330

access.redhat.com/errata/rhsa-2026:52... WEB

https://access.redhat.com/errata/RHSA-2026:52764

access.redhat.com/errata/rhsa-2026:52... WEB

https://access.redhat.com/errata/RHSA-2026:52649

access.redhat.com/errata/rhsa-2026:51... WEB

https://access.redhat.com/errata/RHSA-2026:51604

access.redhat.com/errata/rhsa-2026:51... WEB

https://access.redhat.com/errata/RHSA-2026:51603

access.redhat.com/errata/rhsa-2026:49... WEB

https://access.redhat.com/errata/RHSA-2026:49857

access.redhat.com/errata/rhsa-2026:49... WEB

https://access.redhat.com/errata/RHSA-2026:49851

access.redhat.com/errata/rhsa-2026:49... WEB

https://access.redhat.com/errata/RHSA-2026:49212

access.redhat.com/errata/rhsa-2026:49... WEB

https://access.redhat.com/errata/RHSA-2026:49031

access.redhat.com/errata/rhsa-2026:48... WEB

https://access.redhat.com/errata/RHSA-2026:48386

access.redhat.com/errata/rhsa-2026:47... WEB

https://access.redhat.com/errata/RHSA-2026:47248

Frequently Asked Questions

What is CVE-2026-52923?

CVE-2026-52923 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-20: Improper Input Validation.

Which Software versions are affected?

Affected versions include releases prior to current release patches.

What version fixes CVE-2026-52923?

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-52923?

CVE-2026-52923 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

What CWE is associated with CVE-2026-52923?

CVE-2026-52923 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).

How can I check Maven dependencies for CVE-2026-52923?

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-m237-4jxg-w5jh",
  "modified" : "2026-10-15T03:36:10Z",
  "published" : "2026-06-24T09:30:48Z",
  "aliases" : [ "CVE-2026-52923" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nipc: limit next_id allocation to the valid ID range\n\nThe checkpoint/restore sysctl path can request the next SysV IPC id\nthrough ids->next_id.  ipc_idr_alloc() currently forwards that request to\nidr_alloc() with an open-ended upper bound.\n\nIf the valid tail of the SysV IPC id space is full, the allocation can\nspill beyond ipc_mni.  The returned SysV IPC id still uses the normal\nindex encoding, so later lookup and removal can target the wrong slot. \nThis leaves the real IDR entry behind and breaks the IDR state for the\nobject.\n\nThe bug is in ipc_idr_alloc() in the checkpoint/restore path.\n\n1. ids->next_id is passed to:\n\n       idr_alloc(&ids->ipcs_idr, new, ipcid_to_idx(next_id), 0, ...)\n\n2. The zero upper bound makes the allocation effectively open-ended.\n   Once the valid SysV IPC tail is occupied, idr_alloc() can spill past\n   ipc_mni and allocate an entry beyond the valid IPC id range.\n\n3. The new object id is still encoded with the narrower SysV IPC index\n   width:\n\n       new->id = (new->seq << ipcmni_seq_shift()) + idx\n\n4. Later removal goes through ipc_rmid(), which uses:\n\n       ipcid_to_idx(ipcp->id)\n\n   That truncates the real IDR index. An object actually stored at a\n   high index can then be removed as if it lived at a low in-range\n   index.\n\n5. For shared memory, shm_destroy() frees the current object anyway, but\n   the real high IDR slot is left behind as a dangling pointer.\n\n6. A subsequent walk of /proc/sysvipc/shm reaches the stale IDR entry\n   and dereferences freed memory.\n\nPrevent this by bounding the requested allocation to ipc_mni so the\ncheckpoint/restore path fails once the valid range is exhausted.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-52923"
  }, {
    "type" : "WEB",
    "url" : "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52923.json"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bd4be70669af55b974860d13680348cfdf50bbed"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/af24e202b543ded8a34f1d5d3db54eb916173f04"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a3cc795129e5ec0f8948653a3bf471e7d8852f5e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8c58a92849175f5e2ab7bc2734b3b89afe79f6ef"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/41058d4c3f63ab64901560a704882e0565f4e456"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3bbe2bb9111ce6967a951bfac79af142d816fae5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/157ce2c6836ce0ff19108a819f38df061345425f"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-784472.html"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2492094"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-52923"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:63189"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:61692"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:53330"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:52764"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:52649"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:51604"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:51603"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:49857"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:49851"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:49212"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:49031"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:48386"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:47248"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-401", "CWE-825" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-06-24T08:16:22Z"
  }
}

CVSS V3

7.8 HIGH

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 High (C:H)

Integrity High (I:H)

Availability High (A:H)

Vector String

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Advisory Metadata

Source ID: GHSA-m237-4jxg-w5jh
Schema Version: 1.4.0
Published: 2026-06-24 09:30
Last Modified: 2026-10-15 03:36
Database Record File: advisories/unreviewed/2026/06/GHSA-m237-4jxg-w5jh/GHSA-m237-4jxg-w5jh.json