Microsoft Security Response Center guidance
Vendor revision: Nov 20, 2026Release Notes
Vendor-listed releases
- 0:6.18.62-1.1.azl4
Vulnerability intelligence
CVE-2026-99158. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.
Release Notes
Vendor-listed releases
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
In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Fix false warning in ring_buffer_map_get_reader()
The mmap reader can warn when it catches up with a writer that is still committing events. rb_get_reader_page() returns NULL in this case, but ring_buffer_map_get_reader() treats that result as an error.
The initial rb_per_cpu_empty() check filters out an empty buffer, but it does not guarantee that the next reader page has committed data. Writers do not take reader_lock and can advance commit_page before publishing the committed length on the new page. rb_get_reader_page() can swap to that page, catch up with the writer and return NULL.
Handle NULL through the existing no-data exit without warning. Remove the caller's reader_page == commit_page check as well, since the reader-page helper already handles that case.
The existing metadata update and return path remain in place.
Source: NVD