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-2023-52515RDMA/srp: Do not call scsi_done() from srp_abort()

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/srp: Do not call scsi_done() from srp_abort() After scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler callback, it performs one of the following actions: * Call scsi_queue_insert(). * Call scsi_finish_command(). * Call scsi_eh_scmd_add(). Hence, SCSI abort handlers must not call scsi_done(). Otherwise all the above actions would trigger a use-after-free. Hence remove the scsi_done() call from srp_abort(). Keep the srp_free_req() call before returning SUCCESS because we may not see the command again if SUCCESS is returned.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 years 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-2023-52515, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.69% · top 46% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected d8536670916a685df116b5c2cb256573fd25e4e3 – < 26788a5b48d9d5cd3283d777d238631c8cd7495a
    • affected d8536670916a685df116b5c2cb256573fd25e4e3 – < b9bdffb3f9aaeff8379c83f5449c6b42cb71c2b5
    • affected d8536670916a685df116b5c2cb256573fd25e4e3 – < 2b298f9181582270d5e95774e5a6c7a7fb5b1206
    • affected d8536670916a685df116b5c2cb256573fd25e4e3 – < 05a10b316adaac1f322007ca9a0383b410d759cc
    • affected d8536670916a685df116b5c2cb256573fd25e4e3 – < e193b7955dfad68035b983a0011f4ef3590c85eb
    • affected 738589592a04180e39b6fb5fe8205d85b7dc69f6
    • affected 0575df129e2eb4a801beae0e6e041787480f42b9
    • affected 22fb582405002812d8fb89d0ed1264e97d3d25ad
    • affected 39d6594c457c4728794cb4c3c7be53f93f1ef3ae
    • affected b3f3b814add77a464911df0080d812b18f61ff38
    • affected 3.0.45 – < 3.1
    • affected 3.2.32 – < 3.3
    • affected 3.4.13 – < 3.5
    • affected 3.5.6 – < 3.6
    • affected 3.6.1 – < 3.7
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 5.10.199 – ≤ 5.10.*
    • unaffected 5.15.136 – ≤ 5.15.*
    • unaffected 6.1.57 – ≤ 6.1.*
    • unaffected 6.5.7 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .