CVE-2026-98313: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-hmwj-x5pc-fh88
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98313
GHSA Identifier GHSA-hmwj-x5pc-fh88
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-98313

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-98313, 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: drm/msm/dp: skip PUSH_IDLE when the link was never enabled msm_dp_display_atomic_enable() returns early when link training fails, leaving ->power_on false and the main link down. msm_dp_display_atomic_disable() nevertheless writes DP_STATE_CTRL_PUSH_IDLE and waits for an idle-pattern completion that cannot arrive, so every failed enable is followed by "PUSH_IDLE pattern timedout". Every other step of the teardown is already gated on that flag: msm_dp_display_disable(), called from .atomic_post_disable(), returns early on !power_on. The PUSH_IDLE write is the only one that is not, so the controller's runtime-PM reference is then dropped without the link having been taken down. On glymur (Snapdragon X2 Elite) the consequence is not a warning. The SoC does not survive it: TrustZone force-stops the SOCCP and ADSP remote processors and the machine resets silently about 50 ms later, with no oops and no panic. On an ASUS Zenbook A16 (UX3607OA), whose eDP panel does not currently train, this reproduces without any compositor or GPU involvement: # eDP enable has already failed with "Failed link training (rc=-104)" echo 1 > /sys/class/graphics/fb0/blank [535.645455] === marker === [535.694833] qcom_q6v5_pas d00000.remoteproc: fatal error received: \ sys_m_smsm.c:512:TZ force stop [535.694875] remoteproc remoteproc0: crash detected in soccp: type fatal error [535.728857] qcom_q6v5_pas 6800000.remoteproc: fatal error received: \ sys_m_smsm.c:783:err fatal notification received from TZ <SoC reset> Gate the PUSH_IDLE write on ->power_on so the disable path is consistent with the rest of the teardown. With this applied the same sequence is harmless and the machine stays up; without it, it resets every time. The unconditional write dates back to the original DP driver (c943b4948b58 ("drm/msm/dp: add displayPort driver support")), but the surrounding code has been restructured several times since, so no Fixes: tag is offered. Note that the eDP link-training failure that exposes this on the A16 is a separate problem in the glymur eDP PHY and is reported separately; this change is about not damaging the machine when training fails, for whatever reason. Tested on ASUS Zenbook A16 (UX3607OA), Snapdragon X2 Elite Extreme, on linux-next next-20260803 and next-20260807. The machine has since been running next-20260807 with this patch as its daily driver. Patchwork: https://patchwork.freedesktop.org/patch/745167/

References

NVD — CVE-2026-98313 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98313
git.kernel.org/stable/c/5e97d117b7... WEB
https://git.kernel.org/stable/c/5e97d117b79c3ce89542369ef697be64850de8ad
git.kernel.org/stable/c/dc57147549... WEB
https://git.kernel.org/stable/c/dc57147549a10c99766144cde265645287718ff7
git.kernel.org/stable/c/e249a6e2a1... WEB
https://git.kernel.org/stable/c/e249a6e2a130c08bb4d8b0a55cbe29754307e5c9

Frequently Asked Questions

What is CVE-2026-98313?
CVE-2026-98313 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-98313?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98313?
CVE-2026-98313 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98313?
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-hmwj-x5pc-fh88",
  "modified" : "2026-10-06T09:31:34Z",
  "published" : "2026-10-06T09:31:34Z",
  "aliases" : [ "CVE-2026-98313" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dp: skip PUSH_IDLE when the link was never enabled\n\nmsm_dp_display_atomic_enable() returns early when link training fails,\nleaving ->power_on false and the main link down.\nmsm_dp_display_atomic_disable() nevertheless writes DP_STATE_CTRL_PUSH_IDLE\nand waits for an idle-pattern completion that cannot arrive, so every failed\nenable is followed by \"PUSH_IDLE pattern timedout\".\n\nEvery other step of the teardown is already gated on that flag:\nmsm_dp_display_disable(), called from .atomic_post_disable(), returns early\non !power_on. The PUSH_IDLE write is the only one that is not, so the\ncontroller's runtime-PM reference is then dropped without the link having\nbeen taken down.\n\nOn glymur (Snapdragon X2 Elite) the consequence is not a warning. The SoC\ndoes not survive it: TrustZone force-stops the SOCCP and ADSP remote\nprocessors and the machine resets silently about 50 ms later, with no oops\nand no panic. On an ASUS Zenbook A16 (UX3607OA), whose eDP panel does not\ncurrently train, this reproduces without any compositor or GPU involvement:\n\n  # eDP enable has already failed with \"Failed link training (rc=-104)\"\n  echo 1 > /sys/class/graphics/fb0/blank\n\n  [535.645455] === marker ===\n  [535.694833] qcom_q6v5_pas d00000.remoteproc: fatal error received: \\\n                 sys_m_smsm.c:512:TZ force stop\n  [535.694875] remoteproc remoteproc0: crash detected in soccp: type fatal error\n  [535.728857] qcom_q6v5_pas 6800000.remoteproc: fatal error received: \\\n                 sys_m_smsm.c:783:err fatal notification received from TZ\n  <SoC reset>\n\nGate the PUSH_IDLE write on ->power_on so the disable path is consistent\nwith the rest of the teardown. With this applied the same sequence is\nharmless and the machine stays up; without it, it resets every time.\n\nThe unconditional write dates back to the original DP driver\n(c943b4948b58 (\"drm/msm/dp: add displayPort driver support\")), but the\nsurrounding code has been restructured several times since, so no Fixes:\ntag is offered.\n\nNote that the eDP link-training failure that exposes this on the A16 is a\nseparate problem in the glymur eDP PHY and is reported separately; this\nchange is about not damaging the machine when training fails, for whatever\nreason.\n\nTested on ASUS Zenbook A16 (UX3607OA), Snapdragon X2 Elite Extreme, on\nlinux-next next-20260803 and next-20260807. The machine has since been\nrunning next-20260807 with this patch as its daily driver.\n\nPatchwork: https://patchwork.freedesktop.org/patch/745167/",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98313"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5e97d117b79c3ce89542369ef697be64850de8ad"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dc57147549a10c99766144cde265645287718ff7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e249a6e2a130c08bb4d8b0a55cbe29754307e5c9"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-06T09:18:22Z"
  }
}