FUSE client crash via callback type confusion
Published Feb 21, 2023 · Updated Mar 14, 2025
Out-of-bounds read in GlusterFS 11.0 allows remote attackers to crash a FUSE client through an inode-lock-contention callback. The callback passes a 40-byte gf_upcall structure to notify, which treats it as glusterfs_graph_t and reads graph->id at offset 52. Reachability requires a FUSE client to process that callback; the documented AddressSanitizer run aborts the affected client without reported data disclosure or modification.
Summary
What happened
Out-of-bounds read in GlusterFS 11.0 allows remote attackers to crash a FUSE client through an inode-lock-contention callback. The callback passes a 40-byte gf_upcall structure to notify, which treats it as glusterfs_graph_t and reads graph->id at offset 52. Reachability requires a FUSE client to process that callback; the documented AddressSanitizer run aborts the affected client without reported data disclosure or modification.
The record
- CVE
- CVE-2023-26253
- Published
- Feb 21, 2023
- Updated
- Mar 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 2023CVE publishedPublication date reported by the CVE source.
- Mar 14, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- AddressSanitizer FUSE notify crash reproducerproof of concept · 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