Is there a public exploit for CVE-2026-99111?

No public exploit for CVE-2026-99111 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix data corruption with concurrent writes and OTRUNC…

CVE-2026-99111

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix data corruption with concurrent writes and OTRUNC cifsdotruncate() flushes dirty pages with filemapwriteandwait() and truncates the file on the server, but in the old code both operations ran without holding irwsem or invalidatelock. A concurrent buffered write via netfsperformwrite() -- which only needs irwsem shared -- could dirty new pages after the flush but before the local truncation, and those pages would be silently discarded by cifssetsize() -> truncatepagecache(). Fix by acquiring inodelock (exclusive irwsem) and filemapinvalidatelock at the top of cifsdotruncate(), so the entire flush-truncate-resize sequence is atomic with respect to: buffered writes (blocked by exclusive irwsem, since netfsstartiowrite takes irwsem shared), read page faults (blocked by exclusive invalidatelock, since filemapfault takes it shared), writeback collection (blocked by netfswbbegin/netfswbend around the server truncate and local resize, since netfswritepages also acquires the wb lock).

Assessment

CVSS: Not yet scored
Severity: Unscored
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 28 October 2026
Last updated: 28 October 2026
Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 7 + 6? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99111