CVE-2026-74276: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-h2g9-c4gr-qg58
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-74276
GHSA Identifier GHSA-h2g9-c4gr-qg58
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-74276

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-74276, 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: spi: xilinx: use FIFO occupancy register to determine buffer size The method the driver uses to determine the size of the FIFO has a problem. What it currently does is this: It stops the SPI hardware and writes to the TX FIFO register until TX FIFO FULL asserts in the status register. But the hardware does not only have the FIFO, it also has a shift register which can hold a byte. This can be seen, when writing a byte to the FIFO (while the SPI hardware is stopped,) the TX FIFO EMPTY is still empty. So, if we have a FIFO size of 16 for example, the current method returns a 17. This is a problem, at least when using the driver in irq mode. The same size determined for the TX FIFO is also assumed for the RX FIFO. When a SPI transaction wants to write the amount of the FIFO size or more bytes, the following happens, for example with 16 bytes FIFO size: The driver stops the SPI hardware and writes 17 bytes to the TX FIFO and starts the SPI hardware and goes sleep. The hardware then shifts out 17 bytes (FIFO + shift register) and simultaneously reads bytes into the RX FIFO, but it only has 16 places, so it looses one byte. Then TX FIFO empty asserts, wakes the driver again, which has a fast path and reads 16 bytes from the RX FIFO, but before reading the last 17th byte (which is lost) it does this: sr = xspi->read_fn(xspi->regs + XSPI_SR_OFFSET); if (!(sr & XSPI_SR_RX_EMPTY_MASK)) { xilinx_spi_rx(xspi); rx_words--; } It reads the status register and checks if the RX FIFO is not empty. But it is empty in our case. So this check spins in a while loop forever locking the driver. This patch fixes the logic to determine the FIFO size.

References

NVD — CVE-2026-74276 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74276
git.kernel.org/stable/c/1c9246a199... WEB
https://git.kernel.org/stable/c/1c9246a199e19b2fd36e94feed60e55f27103a4f
git.kernel.org/stable/c/1fc6a6c0cc... WEB
https://git.kernel.org/stable/c/1fc6a6c0cc7796b0c1cf4eec3f0720f422f09273
git.kernel.org/stable/c/47f3b53655... WEB
https://git.kernel.org/stable/c/47f3b5365536e8c38f264824ab15fdb74454e066
git.kernel.org/stable/c/4ee65558a7... WEB
https://git.kernel.org/stable/c/4ee65558a7fda463222f5edc631b6d7862218725
git.kernel.org/stable/c/d1944b71c1... WEB
https://git.kernel.org/stable/c/d1944b71c18e7494756bff1a6f80c25be99eaecb
git.kernel.org/stable/c/d7ccd8736b... WEB
https://git.kernel.org/stable/c/d7ccd8736b67550eca746ed7fa39a36016ff114b
git.kernel.org/stable/c/dfab0d4698... WEB
https://git.kernel.org/stable/c/dfab0d4698a642bab9b895e2e6d240838cfe2cc6
git.kernel.org/stable/c/e98f589d54... WEB
https://git.kernel.org/stable/c/e98f589d54068dfcc7da42d9b730e47b84e2991a

Frequently Asked Questions

What is CVE-2026-74276?
CVE-2026-74276 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-74276?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-74276?
CVE-2026-74276 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74276?
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-h2g9-c4gr-qg58",
  "modified" : "2026-08-15T06:32:27Z",
  "published" : "2026-08-15T06:32:27Z",
  "aliases" : [ "CVE-2026-74276" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: xilinx: use FIFO occupancy register to determine buffer size\n\nThe method the driver uses to determine the size of the FIFO has a\nproblem. What it currently does is this:\nIt stops the SPI hardware and writes to the TX FIFO register until TX\nFIFO FULL asserts in the status register. But the hardware does not only\nhave the FIFO, it also has a shift register which can hold a byte. This\ncan be seen, when writing a byte to the FIFO (while the SPI hardware is\nstopped,) the TX FIFO EMPTY is still empty. So, if we have a FIFO size\nof 16 for example, the current method returns a 17.\nThis is a problem, at least when using the driver in irq mode. The same\nsize determined for the TX FIFO is also assumed for the RX FIFO. When a\nSPI transaction wants to write the amount of the FIFO size or more\nbytes, the following happens, for example with 16 bytes FIFO size:\nThe driver stops the SPI hardware and writes 17 bytes to the TX FIFO and\nstarts the SPI hardware and goes sleep.\nThe hardware then shifts out 17 bytes (FIFO + shift register) and\nsimultaneously reads bytes into the RX FIFO, but it only has 16 places,\nso it looses one byte. Then TX FIFO empty asserts, wakes the driver\nagain, which has a fast path and reads 16 bytes from the RX FIFO, but\nbefore reading the last 17th byte (which is lost) it does this:\n\n\tsr = xspi->read_fn(xspi->regs + XSPI_SR_OFFSET);\n\tif (!(sr & XSPI_SR_RX_EMPTY_MASK)) {\n\t\txilinx_spi_rx(xspi);\n\t\trx_words--;\n\t}\n\nIt reads the status register and checks if the RX FIFO is not empty.\nBut it is empty in our case. So this check spins in a while loop\nforever locking the driver.\n\nThis patch fixes the logic to determine the FIFO size.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74276"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1c9246a199e19b2fd36e94feed60e55f27103a4f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1fc6a6c0cc7796b0c1cf4eec3f0720f422f09273"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/47f3b5365536e8c38f264824ab15fdb74454e066"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4ee65558a7fda463222f5edc631b6d7862218725"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d1944b71c18e7494756bff1a6f80c25be99eaecb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d7ccd8736b67550eca746ed7fa39a36016ff114b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dfab0d4698a642bab9b895e2e6d240838cfe2cc6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e98f589d54068dfcc7da42d9b730e47b84e2991a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:26Z"
  }
}