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

Published Aug 15, 2026
·
Updated

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

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

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

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.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Fix the driver logic so that the completion object used by the interrupt handler is initialized (init_completion()) before registering the IRQ with devm_request_irq().

    Linux kernel SPI driver: spi/uniphier completion initialization order (init_completion before devm_request_irq) = Initialize completion before calling devm_request_irq()

Event History

Aug 15, 2026
CVE Published
via MITRE·05:53 AM
Data Sourced
via MITRE·05:53 AM
Description
Data Sourced
via NVD·06:21 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-72133?

CVE-2026-72133 has a risk score of 37, indicating a low to moderate severity level.

2

How do I fix CVE-2026-72133?

To fix CVE-2026-72133, ensure that completion initialization occurs before the call to devm_request_irq() in the driver.

3

What systems are affected by CVE-2026-72133?

CVE-2026-72133 affects the Linux kernel's spi: uniphier driver.

4

What is the impact of CVE-2026-72133 if left unpatched?

If left unpatched, CVE-2026-72133 may lead to unexpected behavior due to interrupts occurring before proper initialization.

5

When was CVE-2026-72133 published?

CVE-2026-72133 was published on August 15, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203