CVE-2026-93168: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-r3mw-x3xp-fjpr
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-93168
GHSA Identifier GHSA-r3mw-x3xp-fjpr
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-93168

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-93168, 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: dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout Currently when calling xilinx_dma_poll_timeout with delay_us=0 and a condition that is never fulfilled, the CPU busy-waits for prolonged time and the timeout triggers only with a massive delay causing a CPU stall. This happens due to a huge underestimation of wall clock time in poll_timeout_us_atomic. Commit 7349a69cf312 ("iopoll: Do not use timekeeping in read_poll_timeout_atomic()") changed the behavior to no longer use ktime_get at the expense of underestimation of wall clock time which appears to be very large for delay_us=0. Instead of timing out after approximately XILINX_DMA_LOOP_COUNT microseconds, the timeout takes XILINX_DMA_LOOP_COUNT * 1000 * (time that the overhead of the for loop in poll_timeout_us_atomic takes) which is in the range of several minutes for XILINX_DMA_LOOP_COUNT=1000000. Fix this by using a non-zero value for delay_us. Use delay_us=10 to keep the delay in the hot path of starting DMA transfers minimal but still avoid CPU stalls in case of unexpected hardware failures. One-off measurement with delay_us=0 causes the cpu to busy wait around 7 minutes in the timeout case. After applying this patch with delay_us=10 the measured timeout was 1053428 microseconds which is roughly equivalent to the expected 1000000 microseconds specified in XILINX_DMA_LOOP_COUNT. Add a constant XILINX_DMA_POLL_DELAY_US for delay_us value.

References

NVD — CVE-2026-93168 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93168
git.kernel.org/stable/c/8b5654d317... WEB
https://git.kernel.org/stable/c/8b5654d317277e6e505c23f8fa7e415237fefc7f
git.kernel.org/stable/c/aa99c4d1d6... WEB
https://git.kernel.org/stable/c/aa99c4d1d63bbc26a5fc4c667d89b2595743c19d
git.kernel.org/stable/c/f786e7b3ad... WEB
https://git.kernel.org/stable/c/f786e7b3adbf3bd14964a1cedf9d55b6ad91dcd7

Frequently Asked Questions

What is CVE-2026-93168?
CVE-2026-93168 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-93168?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93168?
CVE-2026-93168 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93168?
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-r3mw-x3xp-fjpr",
  "modified" : "2026-10-15T12:30:52Z",
  "published" : "2026-09-17T18:32:12Z",
  "aliases" : [ "CVE-2026-93168" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout\n\nCurrently when calling xilinx_dma_poll_timeout with delay_us=0 and a\ncondition that is never fulfilled, the CPU busy-waits for prolonged time\nand the timeout triggers only with a massive delay causing a CPU stall.\n\nThis happens due to a huge underestimation of wall clock time in\npoll_timeout_us_atomic. Commit 7349a69cf312 (\"iopoll: Do not use\ntimekeeping in read_poll_timeout_atomic()\") changed the behavior to no\nlonger use ktime_get at the expense of underestimation of wall clock\ntime which appears to be very large for delay_us=0. Instead of timing\nout after approximately XILINX_DMA_LOOP_COUNT microseconds, the timeout\ntakes XILINX_DMA_LOOP_COUNT * 1000 * (time that the overhead of the for\nloop in poll_timeout_us_atomic takes) which is in the range of several\nminutes for XILINX_DMA_LOOP_COUNT=1000000. Fix this by using a non-zero\nvalue for delay_us. Use delay_us=10 to keep the delay in the hot path of\nstarting DMA transfers minimal but still avoid CPU stalls in case of\nunexpected hardware failures.\n\nOne-off measurement with delay_us=0 causes the cpu to busy wait around 7\nminutes in the timeout case. After applying this patch with delay_us=10\nthe measured timeout was 1053428 microseconds which is roughly\nequivalent to the expected 1000000 microseconds specified in\nXILINX_DMA_LOOP_COUNT.\n\nAdd a constant XILINX_DMA_POLL_DELAY_US for delay_us value.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93168"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8b5654d317277e6e505c23f8fa7e415237fefc7f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aa99c4d1d63bbc26a5fc4c667d89b2595743c19d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f786e7b3adbf3bd14964a1cedf9d55b6ad91dcd7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:18:12Z"
  }
}