← Back to CVE intelligence
CVE intelligence

CVE-2026-99111

Vulnerability intelligence

Published Oct 28, 2026Sources checked Nov 20, 2026
N/ACVSS not listedScore unavailable
What this means

Review the available evidence

CVE-2026-99111. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Microsoft Security Response Center guidance

Vendor revision: Nov 20, 2026

Release Notes

Vendor-listed releases

  • 0:6.18.62-1.1.azl4

Ubuntu Security Notices guidance

Vendor revision: Nov 19, 2026
Vendor remediation details

This update corrects flaws in the following subsystems: - S390 architecture; - x86 architecture; - Block layer subsystem; - Cryptographic API; - Compute Acceleration Framework; - FireWire subsystem; - GPIO subsystem; - GPU drivers; - Microsoft Hyper-V drivers; - I2C subsystem; - Multiple devices driver; - Network drivers; - STMicroelectronics network drivers; - Power supply drivers; - S/390 drivers; - SCSI subsystem; - SPI subsystem; - TCM subsystem; - UFS subsystem; - File systems infrastructure; - Ext4 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - SMB network file system; - Tracing file system; - XFS file system; - Kernel futex primitives; - Key management; - Key Management; - VMware vSockets driver; - io_uring subsystem; - IPC subsys

CISA KEVNot listedBased on the latest collected catalog
EPSS0.2%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-99111?

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

smb: client: fix data corruption with concurrent writes and O_TRUNC

cifs_do_truncate() flushes dirty pages with filemap_write_and_wait() and truncates the file on the server, but in the old code both operations ran without holding i_rwsem or invalidate_lock.

A concurrent buffered write via netfs_perform_write() -- which only needs i_rwsem shared -- could dirty new pages after the flush but before the local truncation, and those pages would be silently discarded by cifs_setsize() -> truncate_pagecache().

Fix by acquiring inode_lock (exclusive i_rwsem) and filemap_invalidate_lock at the top of cifs_do_truncate(), so the entire flush-truncate-resize sequence is atomic with respect to:

- buffered writes (blocked by exclusive i_rwsem, since netfs_start_io_write takes i_rwsem shared), - read page faults (blocked by exclusive invalidate_lock, since filemap_fault takes it shared), - writeback collection (blocked by netfs_wb_begin/netfs_wb_end around the server truncate and local resize, since netfs_writepages also acquires the wb lock).

Source: NVD