cve.bz

CVE-2026-99156 linux linux

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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().

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.273
  • Linux Linux: fixed in 5.15.224
  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.161
  • Linux Linux: fixed in 6.12.115
  • Linux Linux: fixed in 6.18.59
  • Linux Linux: fixed in 7.2.13
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Red Hat, AlmaLinux, Rocky Linux, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-99156 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99156?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99156?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99156 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.7 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.273
Linux5.155.15.224
Linux6.16.1.191
Linux6.66.6.161
Linux6.126.12.115
Linux6.186.18.59
Linux7.27.2.13
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-99156
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99156
Debian13linux6.12.115-2DEBIAN-CVE-2026-99156
Debian14linux7.2.13-1DEBIAN-CVE-2026-99156
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99156
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99156
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99156
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-99156
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 50 moreno fix listedUBUNTU-CVE-2026-99156
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99156
Ubuntu26.10linux7.3.0-10.10UBUNTU-CVE-2026-99156
Ubuntu26.10linux-aws, linux-gcp, linux-azure and 2 more7.3.0-1004.4UBUNTU-CVE-2026-99156
Ubuntu26.10linux-azure-fde7.3.0-1004.5UBUNTU-CVE-2026-99156
Ubuntu26.10linux-riscv, linux-realtime7.3.0-10.10.1UBUNTU-CVE-2026-99156
UbuntuNvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99156
UbuntuPro:14.04:LTSlinux, linux-aws, linux-azure and 1 moreno fix listedUBUNTU-CVE-2026-99156
7 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:8::baseosperf, kernel, bpftool and 30 more0:4.18.0-553.186.1.el8_10RHSA-2026:99015
Red Hatenterprise_linux:8::crbperf-debuginfo, kernel-debuginfo, bpftool-debuginfo and 7 more0:4.18.0-553.186.1.el8_10RHSA-2026:99015
Red Hatenterprise_linux:8::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 12 more0:4.18.0-553.186.1.rt7.527.el8_10RHSA-2026:99031
Red Hatenterprise_linux:8::realtimekernel-rt, kernel-rt-core, kernel-rt-debug and 10 more0:4.18.0-553.186.1.rt7.527.el8_10RHSA-2026:99031
AlmaLinux8kernel-rt, kernel-rt-core, kernel-rt-debug and 7 more4.18.0-553.186.1.rt7.527.el8_10ALSA-2026:99031
AlmaLinux8perf, kernel, bpftool and 22 more4.18.0-553.186.1.el8_10ALSA-2026:99015
Rocky Linux8kernel-rt, kernel-rt-kvm, kernel-rt-core and 12 more0:4.18.0-553.186.1.rt7.527.el8_10RLSA-2026:99031
Rocky Linux8perf, kernel, bpftool and 23 more0:4.18.0-553.186.1.el8_10RLSA-2026:99015
Azure Linux3kernel6.6.161.1-1AZL-111296
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-99156
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99156
Alpaquitastreamlinux-lts6.18.62-r0BELL-CVE-2026-99156

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A race between st_remove and st_open can leave a scsi_tape pointer published in st_index_idr after its final reference is dropped and the object is freed. A concurrent st_open can then find the stale pointer and execute kref_get on freed slab memory, producing a confirmed use after free write of size 4. For the CVSS the PR:L value reflects that the attacker needs local permission to open the SCSI tape device. Reliable triggering also depends on concurrent device removal and winning a timing window, so AC:H is appropriate. Kernel memory corruption and a crash are supported by the KASAN report. The constrained reference count increment does not prove privilege escalation, but slab reuse creates a plausible path to broader confidentiality and integrity impact in the paranoid assessment.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelAffected
Red Hat Enterprise Linux 7kernel-rtAffected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-99156.

References

Check your stackJSON