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-2025-68371scsi: smartpqi: Fix device resources accessed after device removal

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix device resources accessed after device removal Correct possible race conditions during device removal. Previously, a scheduled work item to reset a LUN could still execute after the device was removed, leading to use-after-free and other resource access issues. This race condition occurs because the abort handler may schedule a LUN reset concurrently with device removal via sdev_destroy(), leading to use-after-free and improper access to freed resources. - Check in the device reset handler if the device is still present in the controller's SCSI device list before running; if not, the reset is skipped. - Cancel any pending TMF work that has not started in sdev_destroy(). - Ensure device freeing in sdev_destroy() is done while holding the LUN reset mutex to avoid races with ongoing resets.

Timeline

  1. ID reserved

    By Linux

  2. · 8 days later

    Published

  3. · 11 months 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 2d80f4054f7f901b8ad97358a9069616ac8524c7 – < 7dfa5a5516ec3c6b9b6c22ee18f0eb2df3f38ef2
    • affected 2d80f4054f7f901b8ad97358a9069616ac8524c7 – < 6d2390653d82cad0e1ba2676e536dd99678f6ef1
    • affected 2d80f4054f7f901b8ad97358a9069616ac8524c7 – < eccc02ba1747501d92bb2049e3ce378ba372f641
    • affected 2d80f4054f7f901b8ad97358a9069616ac8524c7 – < 4e1acf1b6dd6dd0495bda139daafd7a403ae2dc1
    • affected 2d80f4054f7f901b8ad97358a9069616ac8524c7 – < 1a5c5a2f88e839af5320216a02ffb075b668596a
    • affected 2d80f4054f7f901b8ad97358a9069616ac8524c7 – < b518e86d1a70a88f6592a7c396cf1b93493d1aab
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.63 – ≤ 6.12.*
    • unaffected 6.17.13 – ≤ 6.17.*
    • unaffected 6.18.2 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .