CVE-2026-72133
Linux kernel uniphier SPI driver race can call complete() on uninitialized completion.
Is CVE-2026-72133 being exploited?
Not confirmed. CVE-2026-72133 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-72133?
CVE-2026-72133 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72133?
Yes. A fix has been recorded for CVE-2026-72133. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72133 affect?
CVE-2026-72133 affects Linux kernel (uniphier SPI driver), Socionext UniPhier-based devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72133?
Apply upstream/vendor kernel patch or update affected kernels immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
IRQ may fire before completion is initialized, causing kernel memory corruption/crash; may enable local privilege escalation or denial of service.
Patch when possible
- affected>= 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and < b9fcf0db433d79648ace74bc2b8b88f91e306304
- affected>= 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and < 82a5746c4c9e94f6f816ec7edea6ddc24417c6a5
- affected>= 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and < f4bb0a91f7badd6d15ac8d783a1169d9e1e95c17
- affected>= 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and < 49f6705d80b5e6175d8435d9c72b66bd516a8e89
- affected>= 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and < 8b5798ce0007874c14611b8ee4ce6c749855260e
- affected>= 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and < d44b828eb551bd59ba9f22457825cc3db3a39fc1
- affected>= 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and < 077a7bc1c32d3da9670c5e282ea3e5ac8a94be59
- affected>= 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and < f3ad1c87d8201e54b66bd6072442f0b5d5a308ee
- affected4.19
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.