Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-72133, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.4.

Affected products

  • Linux · Linux

    • affected 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 – < b9fcf0db433d79648ace74bc2b8b88f91e306304
    • affected 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 – < 82a5746c4c9e94f6f816ec7edea6ddc24417c6a5
    • affected 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 – < f4bb0a91f7badd6d15ac8d783a1169d9e1e95c17
    • affected 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 – < 49f6705d80b5e6175d8435d9c72b66bd516a8e89
    • affected 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 – < 8b5798ce0007874c14611b8ee4ce6c749855260e
    • affected 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 – < d44b828eb551bd59ba9f22457825cc3db3a39fc1
    • affected 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 – < 077a7bc1c32d3da9670c5e282ea3e5ac8a94be59
    • affected 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 – < f3ad1c87d8201e54b66bd6072442f0b5d5a308ee
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72133 badge
[![CVE-2026-72133](https://cveledger.app/badge/CVE-2026-72133.svg)](https://cveledger.app/cve/CVE-2026-72133)

Record last updated .