Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74276: spi: xilinx: use FIFO occupancy register to determine buffer size

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 1c9246a199e19b2fd36e94feed60e55f27103a4f, 1fc6a6c0cc7796b0c1cf4eec3f0720f422f09273, 47f3b5365536e8c38f264824ab15fdb74454e066.

Low priority for now. Upgrade to Linux Linux 1c9246a199e19b2fd36e94feed60e55f27103a4f, 1fc6a6c0cc7796b0c1cf4eec3f0720f422f09273, 47f3b5365536e8c38f264824ab15fdb74454e066 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74276

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.0affected
    • 4c9a761402d780b86b9b068aba4ef8e29ed15e99 and later · before 4ee65558a7fda463222f5edc631b6d7862218725affected · git
    • 4c9a761402d780b86b9b068aba4ef8e29ed15e99 and later · before e98f589d54068dfcc7da42d9b730e47b84e2991aaffected · git
    • 4c9a761402d780b86b9b068aba4ef8e29ed15e99 and later · before 1fc6a6c0cc7796b0c1cf4eec3f0720f422f09273affected · git
    • 4c9a761402d780b86b9b068aba4ef8e29ed15e99 and later · before dfab0d4698a642bab9b895e2e6d240838cfe2cc6affected · git
    • 4c9a761402d780b86b9b068aba4ef8e29ed15e99 and later · before d7ccd8736b67550eca746ed7fa39a36016ff114baffected · git
    • 4c9a761402d780b86b9b068aba4ef8e29ed15e99 and later · before 1c9246a199e19b2fd36e94feed60e55f27103a4faffected · git
    • 4c9a761402d780b86b9b068aba4ef8e29ed15e99 and later · before d1944b71c18e7494756bff1a6f80c25be99eaecbaffected · git
    • 4c9a761402d780b86b9b068aba4ef8e29ed15e99 and later · before 47f3b5365536e8c38f264824ab15fdb74454e066affected · git
    • before 4.0not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74274Aug 15, 2026 · cxl/region: Fill first free targets[] slot during auto-discovery
    0Monitor
  • ← EarlierCVE-2026-74275Aug 15, 2026 · cxl/region: Fix out-of-bounds access in cxl_cancel_auto_attach()
    33Monitor
  • Later →CVE-2026-74280Aug 15, 2026 · crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1c9246a199e19b2fd36e94feed60e55f27103a4fVendor (CNA)
Linux Linux1fc6a6c0cc7796b0c1cf4eec3f0720f422f09273Vendor (CNA)
Linux Linux47f3b5365536e8c38f264824ab15fdb74454e066Vendor (CNA)
Linux Linux4ee65558a7fda463222f5edc631b6d7862218725Vendor (CNA)
Linux Linuxd1944b71c18e7494756bff1a6f80c25be99eaecbVendor (CNA)
Linux Linuxd7ccd8736b67550eca746ed7fa39a36016ff114bVendor (CNA)
Linux Linuxdfab0d4698a642bab9b895e2e6d240838cfe2cc6Vendor (CNA)
Linux Linuxe98f589d54068dfcc7da42d9b730e47b84e2991aVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records