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-43275scsi: ufs: core: Flush exception handling work when RPM level is zero

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Flush exception handling work when RPM level is zero Ensure that the exception event handling work is explicitly flushed during suspend when the runtime power management level is set to UFS_PM_LVL_0. When the RPM level is zero, the device power mode and link state both remain active. Previously, the UFS core driver bypassed flushing exception event handling jobs in this configuration. This created a race condition where the driver could attempt to access the host controller to handle an exception after the system had already entered a deep power-down state, resulting in a system crash. Explicitly flush this work and disable auto BKOPs before the suspend callback proceeds. This guarantees that pending exception tasks complete and prevents illegal hardware access during the power-down sequence.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 5 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-43275, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.09% · top 100% of all CVEs (19 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 57d104c153d3d6d7bea60089e80f37501851ed2c – < d5c3a1a13f97355c397f9439d79cb04b182958a3
    • affected 57d104c153d3d6d7bea60089e80f37501851ed2c – < 5d186731bc335cc049d4e57ab9f563cfab95593e
    • affected 57d104c153d3d6d7bea60089e80f37501851ed2c – < aa8d68d97c7f0ef966e51afc17fdbdc372700edf
    • affected 57d104c153d3d6d7bea60089e80f37501851ed2c – < aac2fee7513dd25042a616f86a1469b4858d2c5c
    • affected 57d104c153d3d6d7bea60089e80f37501851ed2c – < 78d8e2d6352e8317686ee3a44811ac14c415a57d
    • affected 57d104c153d3d6d7bea60089e80f37501851ed2c – < ab71c146c135f9af1614ef0fc29a0a3b84f1a373
    • affected 57d104c153d3d6d7bea60089e80f37501851ed2c – < f8ef441811ec413717f188f63d99182f30f0f08e
  • Linux · Linux

    • affected 3.18
    • unaffected < 3.18
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .