Snapshot data corruption via missing OSD context
Published May 6, 2026 · Updated May 6, 2026
Snapshot integrity failure in affected Linux Kernel releases allows local users to corrupt CephFS snapshot data through hole punching. In fs/ceph/file.c, ceph_zero_partial_object() sends its zeroing OSD write without the inode snapshot context, so a live-file operation also changes data preserved by an existing snapshot. Reachability requires a mounted CephFS client with write and snapshot permissions; the demonstrated consequence is silent snapshot-content modification rather than code execution or a service crash.
Summary
What happened
Snapshot integrity failure in affected Linux Kernel releases allows local users to corrupt CephFS snapshot data through hole punching. In fs/ceph/file.c, ceph_zero_partial_object() sends its zeroing OSD write without the inode snapshot context, so a live-file operation also changes data preserved by an existing snapshot. Reachability requires a mounted CephFS client with write and snapshot permissions; the demonstrated consequence is silent snapshot-content modification rather than code execution or a service crash.
The record
- CVE
- CVE-2026-43273
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.12
- Affected versionversion=ad7a60de882aca31afb58721db166f7e77afcd92 <36673344b41c31fb502dd0d0113cec1aa96f581e
- Affected versionversion=ad7a60de882aca31afb58721db166f7e77afcd92 <4097e70fc543cca72982854108a32f6ae924e727
- Affected versionversion=ad7a60de882aca31afb58721db166f7e77afcd92 <531a76c5a2e44264cee8a70121e63eb28c1ba728
- Affected versionversion=ad7a60de882aca31afb58721db166f7e77afcd92 <5788b742007f53406049bef917833a71ddd43f60
- Affected versionversion=ad7a60de882aca31afb58721db166f7e77afcd92 <69e59a87bab0ea31ab2a584fc65e12dafacf8953
- Affected versionversion=ad7a60de882aca31afb58721db166f7e77afcd92 <757873abfc8ea38592582180aed0f57f0f0cb07a
- Affected versionversion=ad7a60de882aca31afb58721db166f7e77afcd92 <9efa154609cdb658f51c7d76b30a09f7e6485250
- Affected versionversion=ad7a60de882aca31afb58721db166f7e77afcd92 <f16bd3fa74a2084ee7e16a8a2be7e7399b970907
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo