Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97991 Overview
CVE-2026-97991 is a Linux kernel vulnerability in the vdpa_sim_blk virtio block simulator driver. The function vdpasim_blk_check_range() logs invalid start sectors but continues validating the request. An unsigned capacity subtraction can underflow, allowing an out-of-range buffer offset to reach the data path. The flaw leads to out-of-bounds reads and writes in three virtio block request handlers: VIRTIO_BLK_T_OUT, VIRTIO_BLK_T_IN, and VIRTIO_BLK_T_WRITE_ZEROES.
Critical Impact
A local attacker with access to the vDPA block simulator can trigger out-of-bounds memory reads and writes in kernel space, enabling potential privilege escalation, kernel information disclosure, or denial of service.
Affected Products
- Linux kernel versions containing the vdpa_sim_blk driver prior to the fixing commits
- Linux stable kernel branches referenced by commits 0a8693f, 14acb0d, a8a1413, and d6dac17
- Systems with the vDPA block simulator module (vdpa_sim_blk) loaded
Discovery Timeline
- 2026-09-25 - CVE-2026-97991 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-97991
Vulnerability Analysis
The vulnerability resides in the vdpa_sim_blk driver, which simulates a virtio block device for Virtual Data Path Acceleration (vDPA) testing. The vdpasim_blk_check_range() helper validates incoming block requests against the backing buffer capacity. When a request specifies a start sector at or beyond capacity, the function logs the condition but does not reject the request. Execution continues into an unsigned subtraction that underflows, producing a very large offset value.
This invalid offset then flows into three request paths. VIRTIO_BLK_T_OUT passes blk->buffer + offset to vringh_iov_pull_iotlb(), triggering an out-of-bounds write inside _copy_from_iter() or memcpy(). VIRTIO_BLK_T_IN passes the same corrupted pointer to vringh_iov_push_iotlb(), triggering an out-of-bounds read in _copy_to_iter(). VIRTIO_BLK_T_WRITE_ZEROES passes the pointer to memset(), producing an out-of-bounds write.
Root Cause
The root cause is incomplete input validation combined with an integer underflow [CWE-191]. The validator continued processing after detecting an invalid start sector. The subsequent unsigned subtraction of the capacity produced an attacker-influenced buffer offset. The IN and OUT paths further round byte counts down to sectors during validation, but copy the original byte counts, so a sub-sector request at the capacity boundary can still read or write past the end of the buffer.
Attack Vector
Exploitation requires local access and the ability to submit virtio block requests to a vdpa_sim_blk device. An attacker crafts a virtio block descriptor with a start sector equal to or greater than the simulated device capacity. The resulting underflow steers memory accesses outside the allocated blk->buffer region. Depending on the request type, the attacker achieves kernel memory disclosure or kernel heap corruption, both of which can be chained toward privilege escalation.
Technical details are available in the upstream fixes: Linux Kernel Commit 0a8693f, Linux Kernel Commit 14acb0d, Linux Kernel Commit a8a1413, and Linux Kernel Commit d6dac17.
Detection Methods for CVE-2026-97991
Indicators of Compromise
- Kernel log entries from vdpasim_blk_check_range() reporting invalid start sectors on an unpatched system.
- KASAN (Kernel Address Sanitizer) reports flagging out-of-bounds reads or writes in _copy_from_iter, _copy_to_iter, or memset originating from vdpa_sim_blk request handlers.
- Unexpected kernel oops or panic traces referencing vdpasim_blk_work or vringh_iov_pull_iotlb.
Detection Strategies
- Audit loaded kernel modules for vdpa_sim_blk presence on production hosts where it should not be enabled.
- Monitor dmesg and journald for warnings generated by the vDPA block simulator describing out-of-range sector requests.
- Enable KASAN in test and staging kernels to surface boundary violations during fuzzing of virtio block interfaces.
Monitoring Recommendations
- Forward kernel ring buffer logs to a central analytics platform and alert on vdpa_sim_blk warnings.
- Track module load events for vdpa_sim_blk using auditd rules on hosts running virtualization or vDPA workloads.
- Correlate guest-initiated virtio block activity with host kernel errors to identify abusive request patterns.
How to Mitigate CVE-2026-97991
Immediate Actions Required
- Apply the upstream Linux kernel patches referenced in the stable commits 0a8693f, 14acb0d, a8a1413, and d6dac17.
- If patching is not immediately possible, unload the vdpa_sim_blk module on hosts where it is not required.
- Restrict access to vDPA control interfaces to trusted administrators only.
Patch Information
The fix rejects any request with a start sector at or beyond the backing buffer capacity before performing the unsigned subtraction. Treating the capacity boundary itself as invalid prevents sub-sector requests from escaping validation. Distribution kernels should be updated to builds that include the referenced commits. Verify your running kernel contains the fix by reviewing the vendor changelog for vdpa_sim_blk.
Workarounds
- Blacklist the vdpa_sim_blk module on systems that do not require vDPA block simulation by adding blacklist vdpa_sim_blk to a file under /etc/modprobe.d/.
- Limit which users can access /dev/vhost-vdpa-* and vDPA management netlink interfaces through strict file permissions and namespace isolation.
- Disable or avoid loading vDPA simulator drivers in production kernels; retain them only in development and test environments.
# Prevent the vulnerable module from loading at boot
echo 'blacklist vdpa_sim_blk' | sudo tee /etc/modprobe.d/disable-vdpa-sim-blk.conf
# Unload the module from the running kernel if present
sudo modprobe -r vdpa_sim_blk
# Verify the module is no longer loaded
lsmod | grep vdpa_sim_blk
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

