Is there a patch available for CVE-2026-99111?

Yes, a patch is available for CVE-2026-99111. Update the affected software to the latest version immediately.

Linux CVE-2026-99111

EUVD-2026-112011

2026-10-28 Linux

GHSA-2cjv-j4m8-25m8

Information Disclosure Linux

View

Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.

Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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).

Affected VersionsENISA

Linux 110fee6b9bb58a5c50047fc2594d415f741b591e <a8603b52b39f520ea8a34def74c23fba87396d3e

Linux patch: 7.3

Linux patch: 0

Linux 110fee6b9bb58a5c50047fc2594d415f741b591e <4d143608a0445443a85c9b29f4c9f8e63d5dbfc9

Linux patch: 7.2.13

Linux 110fee6b9bb58a5c50047fc2594d415f741b591e <ffa66fdc7d35b890606767c4d2c7ac26b4d90a99

Linux patch: 6.18.59

Linux 6.18

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Lifecycle Timeline

Patch available

Oct 28, 2026 - 11:02 EUVD

CVE Published

Oct 28, 2026 - 10:34 cve.org

UNKNOWN (no severity yet)

Threat Intelligence Overview

Data Quality

2 sources

Confidence: Low

EUVD

CVE.org

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity Not scored yet

CISA KEV No

Public POC No

EPSS N/A

Patch available Yes

Active threat No

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.