CVE-2026-46314: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-24m2-rchh-h2mx
Share
CVSS 5.5
CWE-835
Published
Advisory Summary

CVE-2026-46314 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-46314 at a Glance

CVE Identifier CVE-2026-46314
GHSA Identifier GHSA-24m2-rchh-h2mx
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
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-46314

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-46314, 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-835: Loop with Unreachable Exit Condition ('Infinite Loop'), where the product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. 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: drm/v3d: Reject empty multisync extension to prevent infinite loop v3d_get_extensions() walks a userspace-provided singly-linked list of ioctl extensions without any bound on the chain length. A local user can craft a self-referential extension (ext->next == &ext) with zero in_sync_count and out_sync_count, which bypasses the existing duplicate- extension guard: if (se->in_sync_count || se->out_sync_count) return -EINVAL; The guard never fires because v3d_get_multisync_post_deps() returns immediately when count is zero, leaving both fields at zero on every iteration. The result is an infinite loop in kernel context, blocking the calling thread and pegging a CPU core indefinitely. Fix this by rejecting a multisync extension where both in_sync_count and out_sync_count are zero in v3d_get_multisync_submit_deps(). An empty multisync carries no synchronization information and serves no useful purpose, so returning -EINVAL for such an extension is the correct defense against this attack vector.

References

NVD — CVE-2026-46314 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-46314
git.kernel.org/stable/c/309abbddec... WEB
https://git.kernel.org/stable/c/309abbddeca0c12714721928a819ef45e5710998
git.kernel.org/stable/c/4fa42a249e... WEB
https://git.kernel.org/stable/c/4fa42a249e8cd6ed17aea04e5695b6e9001f2433
git.kernel.org/stable/c/9c5164781c... WEB
https://git.kernel.org/stable/c/9c5164781cb388d219d8f49fa0f0b04cf86ad544
git.kernel.org/stable/c/fb44d589bf... WEB
https://git.kernel.org/stable/c/fb44d589bf3148e13452185a6e772a7efbf2d684

Frequently Asked Questions

What is CVE-2026-46314?
CVE-2026-46314 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop').
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-46314?
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-46314?
CVE-2026-46314 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-46314?
CVE-2026-46314 is classified under CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') (The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.).
How can I check Maven dependencies for CVE-2026-46314?
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-24m2-rchh-h2mx",
  "modified" : "2026-07-08T15:31:37Z",
  "published" : "2026-06-08T18:31:53Z",
  "aliases" : [ "CVE-2026-46314" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/v3d: Reject empty multisync extension to prevent infinite loop\n\nv3d_get_extensions() walks a userspace-provided singly-linked list of\nioctl extensions without any bound on the chain length. A local user\ncan craft a self-referential extension (ext->next == &ext) with zero\nin_sync_count and out_sync_count, which bypasses the existing duplicate-\nextension guard:\n\n    if (se->in_sync_count || se->out_sync_count)\n            return -EINVAL;\n\nThe guard never fires because v3d_get_multisync_post_deps() returns\nimmediately when count is zero, leaving both fields at zero on every\niteration. The result is an infinite loop in kernel context, blocking\nthe calling thread and pegging a CPU core indefinitely.\n\nFix this by rejecting a multisync extension where both in_sync_count\nand out_sync_count are zero in v3d_get_multisync_submit_deps(). An\nempty multisync carries no synchronization information and serves no\nuseful purpose, so returning -EINVAL for such an extension is the\ncorrect defense against this attack vector.",
  "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-46314"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/309abbddeca0c12714721928a819ef45e5710998"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4fa42a249e8cd6ed17aea04e5695b6e9001f2433"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9c5164781cb388d219d8f49fa0f0b04cf86ad544"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fb44d589bf3148e13452185a6e772a7efbf2d684"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-835" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-06-08T17:16:50Z"
  }
}