---
title: "CVE-2026-93782: Linux Kernel vhost-scsi - Broken Access Control"
description: "Linux kernel vhost-scsi contains a data tampering vulnerability caused by reuse of old memory mappings after VHOST_SET_MEM_TABLE ioctl, letting attackers cause response data to be written to unrelated userspace objects, exploit requires device ioctl usage."
url: https://panop.io/threat-heartbeat/CVE-2026-93782/
---

# CVE-2026-93782 Linux Kernel vhost-scsi - Broken Access Control

Linux kernel vhost-scsi contains a data tampering vulnerability caused by reuse of old memory mappings after VHOST\_SET\_MEM\_TABLE ioctl, letting attackers cause response data to be written to unrelated userspace objects, exploit requires device ioctl usage.

CVSS base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.12% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-93782)

## Details

Type

Broken Access Control

Impact

Data Tampering

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Published

24 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version with the vhost-scsi backend flush fix.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-93782](https://nvd.nist.gov/vuln/detail/CVE-2026-93782)
- [https://git.kernel.org/stable/c/6436411203d8c702ffc055700f1a6bde488ff681](https://git.kernel.org/stable/c/6436411203d8c702ffc055700f1a6bde488ff681)
- [https://git.kernel.org/stable/c/be2636e1b21fe860db918152abf2932638d06ed7](https://git.kernel.org/stable/c/be2636e1b21fe860db918152abf2932638d06ed7)
- [https://git.kernel.org/stable/c/cec088285adcc7ae23c119b6bbdb22270dc2de8f](https://git.kernel.org/stable/c/cec088285adcc7ae23c119b6bbdb22270dc2de8f)
- [https://git.kernel.org/stable/c/e0bf6bed528693a6b32439ab122b34a34b66d96f](https://git.kernel.org/stable/c/e0bf6bed528693a6b32439ab122b34a34b66d96f)
- [https://git.kernel.org/stable/c/22598f55a4c2b510b3df5e69e563387a963222ae](https://git.kernel.org/stable/c/22598f55a4c2b510b3df5e69e563387a963222ae)
- [https://git.kernel.org/stable/c/6c1b802e36b05ebd9d41686c4dce6f06966af469](https://git.kernel.org/stable/c/6c1b802e36b05ebd9d41686c4dce6f06966af469)
- [https://git.kernel.org/stable/c/981c97d09c6b9560bb12dcc41f11ce59b1a48e97](https://git.kernel.org/stable/c/981c97d09c6b9560bb12dcc41f11ce59b1a48e97)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)