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-99156scsi: st: Fix use-after-free race between st_remove() and st_open()

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: st: Fix use-after-free race between st_remove() and st_open() st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its index from st_index_idr. If that was the last reference, scsi_tape_release() frees the structure while it is still published in the idr. scsi_tape_get(), called from st_open(), looks up the tape in st_index_idr and takes a reference under st_ref_mutex and st_index_lock. remove_cdevs() does not wait for opens that are already past chrdev_open(), so an open that is blocked on st_ref_mutex while st_remove() holds it can take the mutex as soon as st_remove() drops it, find the freed tpnt in the idr and call kref_get() on it: BUG: KASAN: slab-use-after-free in st_open Write of size 4 ... st_open (drivers/scsi/st.c:254 drivers/scsi/st.c:1291) chrdev_open ... Freed by task ...: kfree st_remove (drivers/scsi/st.c:4512) Remove the index from the idr before dropping the reference, all under st_ref_mutex. A concurrent scsi_tape_get() now either runs first and holds a valid reference that keeps the tape alive, or runs afterwards and finds nothing, so st_open() fails with -ENXIO. This restores the ordering st_remove() had before the conversion to st_index_idr, where the tape was unpublished from scsi_tapes[] before the final kref_put().

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 3 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-99156, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.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.13% · top 97% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 6c648d95a6af4a79241a916871df17c84c68ea20 – < 7d7f9d2ee4b0841f3eba9fa3627044ad329428de
    • affected 6c648d95a6af4a79241a916871df17c84c68ea20 – < d9517fc39ec3ee13eadefdc17f45300f7d23ed8c
    • affected 6c648d95a6af4a79241a916871df17c84c68ea20 – < e7a5da4a4820210aa7d7cd8e6eb25aabe9e5b5a7
    • affected 6c648d95a6af4a79241a916871df17c84c68ea20 – < 00ff1128123d4bdfacd28d68fb4b6e6f657a3648
    • affected 6c648d95a6af4a79241a916871df17c84c68ea20 – < 5ef230f734e0d23db007c8405f38b7e226740084
    • affected 6c648d95a6af4a79241a916871df17c84c68ea20 – < a1647b653549ff29f0422a63eabf329b842f3822
    • affected 6c648d95a6af4a79241a916871df17c84c68ea20 – < 18a0e3733ce38718688e813e5e2d1106bd4830e5
    • affected 6c648d95a6af4a79241a916871df17c84c68ea20 – < 71caf7f84bd62a4bf91cc95abd2de690afb8d15f
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .