Bug 2516556 (CVE-2026-72133)

Summary: CVE-2026-72133 kernel: spi: uniphier: Fix completion initialization order before devm_request_irq()
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's spi: uniphier driver. The driver attempts to use an internal synchronization mechanism before it has been properly set up. If an interrupt occurs at a precise moment, the system may try to operate on this uninitialized mechanism, leading to unpredictable system behavior. This could result in system instability or a denial of service.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-15 06:18:43 UTC 
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.
Comment 1 Keith Grant 2026-08-17 23:18:50 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081530-CVE-2026-72133-a965@gregkh/T