CVE-2026-99687: vhost-scsi: zero misaligned I/O bounce pages

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

vhost-scsi: zero misaligned I/O bounce pages

The misaligned I/O fallback copies the full bounce scatterlist to the request buffer during completion. If a data-in command transfers less than requested, part of a newly allocated bounce page can remain unwritten.

Allocate bounce pages with GFPZERO so all bytes copied during completion have a defined value. This path is already the slow fallback for misaligned I/O, so the added initialization cost is acceptable.

Found during an LLM-assisted source audit and validated with a QEMU/KVM vhost-scsi target using misaligned data-in commands.

Affected Software

3 affected componentsFixes available
linux/kernel>=6.4.16<6.5
6.5
linux/kernel>=6.5.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.5
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Compensating control

    Allocate vhost-scsi misaligned I/O bounce pages with __GFP_ZERO so bytes left unwritten by a short data-in transfer are zeroed before the full bounce scatterlist is copied to the request buffer during completion.

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel vhost-scsi target and exercising the misaligned I/O fallback path are exposed. The issue was validated with a QEMU/KVM vhost-scsi target using misaligned data-in commands.

2

What is required to trigger the affected path?

A data-in command must use misaligned I/O and transfer less data than originally requested. In that case, completion copies the full bounce scatterlist even though part of a newly allocated bounce page may not have been written.

3

What data may be exposed?

Bytes in the unwritten portion of a newly allocated bounce page may be copied into the request buffer. The provided information does not specify the source or sensitivity of those residual bytes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203