# CVE-2026-72133: spi: uniphier: Fix completion initialization order before devm_request_irq()

> A race condition in the Linux kernel SPI driver allows an interrupt to trigger before completion initialization, potentially causing undefined behavior and system crashes.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72133, DEBIAN-CVE-2026-72133, GHSA-24h9-gmhv-mhpq, UBUNTU-CVE-2026-72133

## What is CVE-2026-72133?

CVE-2026-72133 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

spi: uniphier: Fix completion initialization order before devm_request_irq()

The driver calls devm_request_irq() before initializing the completion
used by the interrupt handler. Because the interrupt may occur immediately
after devm_request_irq(), the handler may execute before init_completion().

This may result in calling complete() on an uninitialized completion,
causing undefined behavior. This has been observed with KASAN.

Fix this by initializing the completion before registering the IRQ.

## Which versions are affected by CVE-2026-72133?


## How do I fix CVE-2026-72133?

Apply the vendor's patch.

## Is CVE-2026-72133 being exploited?

There is no known exploitation of CVE-2026-72133 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72133 and fix it if it is affected.

What it is: CVE-2026-72133 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72133 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72133/ (Markdown: https://insights.sbomify.com/CVE-2026-72133/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72133
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72133
- OSV: https://osv.dev/vulnerability/CVE-2026-72133

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72133/
Summaries are generated and may contain mistakes; the official description above is the record.