CVE-2026-72133: spi: uniphier: Fix completion initialization order before devm_request_irq()
Noroxi assessment
Priority: Monitor (action score 33/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 077a7bc1c32d3da9670c5e282ea3e5ac8a94be59, 49f6705d80b5e6175d8435d9c72b66bd516a8e89, 82a5746c4c9e94f6f816ec7edea6ddc24417c6a5.
Low priority for now. Upgrade to Linux Linux 077a7bc1c32d3da9670c5e282ea3e5ac8a94be59, 49f6705d80b5e6175d8435d9c72b66bd516a8e89, 82a5746c4c9e94f6f816ec7edea6ddc24417c6a5 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: 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.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.19affected
- 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and later · before b9fcf0db433d79648ace74bc2b8b88f91e306304affected · git
- 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and later · before 82a5746c4c9e94f6f816ec7edea6ddc24417c6a5affected · git
- 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and later · before f4bb0a91f7badd6d15ac8d783a1169d9e1e95c17affected · git
- 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and later · before 49f6705d80b5e6175d8435d9c72b66bd516a8e89affected · git
- 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and later · before 8b5798ce0007874c14611b8ee4ce6c749855260eaffected · git
- 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and later · before d44b828eb551bd59ba9f22457825cc3db3a39fc1affected · git
- 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and later · before 077a7bc1c32d3da9670c5e282ea3e5ac8a94be59affected · git
- 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and later · before f3ad1c87d8201e54b66bd6072442f0b5d5a308eeaffected · git
- before 4.19not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72128Aug 15, 2026 · nvmet: fix refcount leak in nvmet_sq_create()0Monitor
- ← EarlierCVE-2026-72132Aug 15, 2026 · NFS: Charge unstable writes by request size, not folio size0Monitor
- Later →CVE-2026-72134Aug 15, 2026 · spi: imx: reconfigure for PIO when DMA cannot be started31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 077a7bc1c32d3da9670c5e282ea3e5ac8a94be59 | Vendor (CNA) |
| Linux Linux | 49f6705d80b5e6175d8435d9c72b66bd516a8e89 | Vendor (CNA) |
| Linux Linux | 82a5746c4c9e94f6f816ec7edea6ddc24417c6a5 | Vendor (CNA) |
| Linux Linux | 8b5798ce0007874c14611b8ee4ce6c749855260e | Vendor (CNA) |
| Linux Linux | b9fcf0db433d79648ace74bc2b8b88f91e306304 | Vendor (CNA) |
| Linux Linux | d44b828eb551bd59ba9f22457825cc3db3a39fc1 | Vendor (CNA) |
| Linux Linux | f3ad1c87d8201e54b66bd6072442f0b5d5a308ee | Vendor (CNA) |
| Linux Linux | f4bb0a91f7badd6d15ac8d783a1169d9e1e95c17 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package 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.
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 researchersFinders, 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
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/49f6705d80b5e6175d8435d9c72b66bd516a8e89
- git.kernel.org/stable/c/82a5746c4c9e94f6f816ec7edea6ddc24417c6a5
- git.kernel.org/stable/c/8b5798ce0007874c14611b8ee4ce6c749855260e
- git.kernel.org/stable/c/b9fcf0db433d79648ace74bc2b8b88f91e306304
- git.kernel.org/stable/c/d44b828eb551bd59ba9f22457825cc3db3a39fc1
- git.kernel.org/stable/c/f3ad1c87d8201e54b66bd6072442f0b5d5a308ee
- git.kernel.org/stable/c/f4bb0a91f7badd6d15ac8d783a1169d9e1e95c17
Vendor advisories and official records. Exploit/PoC links are deliberately left out.