Copied-file corruption via incomplete dirty-dnode check
Published Nov 24, 2023 · Updated Nov 3, 2025
File corruption in OpenZFS 2.1.13 and earlier and 2.2.0 through 2.2.1 allows attackers to replace copied file data with zeros. The dnode_is_dirty check can ignore dirty data records, causing lseek with SEEK_DATA to report no data and cp to punch a full-file hole. Reachability requires a concurrent append to a newly created ZFS file while sparse-copy logic scans it; zeroed access-control files can disable protections.
Summary
What happened
File corruption in OpenZFS 2.1.13 and earlier and 2.2.0 through 2.2.1 allows attackers to replace copied file data with zeros. The dnode_is_dirty check can ignore dirty data records, causing lseek with SEEK_DATA to report no data and cp to punch a full-file hole. Reachability requires a concurrent append to a newly created ZFS file while sparse-copy logic scans it; zeroed access-control files can disable protections.
The record
- CVE
- CVE-2023-49298
- Published
- Nov 24, 2023
- Updated
- Nov 3, 2025
- Vendor
- OpenZFS
- Product
- OpenZFS
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 24, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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=0 <=2.1.13
- Affected versionversion=2.2.0 <=2.2.1
What conditions does exploitation require?
What is affected?
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
- OpenZFS issue 15526 reproduction procedurefunctional · demonstrated
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