Service interruption via rounded-down EOF validation
Published Jun 19, 2024 · Updated May 11, 2026
Improper EOF validation in Linux kernel branches 6.6, 6.8, and 6.9 allows local users to interrupt service via an unaligned block write. The blkdev_iomap_begin function in block/fops.c rounds the requested position down to the logical block size, then checks the rounded iomap offset against inode size instead of checking the raw position, producing a zero-length mapping for an unaligned position at EOF. Low-privileged local access and the ability to issue the crafted block-device write are required; the reported consequence is availability loss without confidentiality or integrity impact.
Summary
What happened
Improper EOF validation in Linux kernel branches 6.6, 6.8, and 6.9 allows local users to interrupt service via an unaligned block write. The blkdev_iomap_begin function in block/fops.c rounds the requested position down to the logical block size, then checks the rounded iomap offset against inode size instead of checking the raw position, producing a zero-length mapping for an unaligned position at EOF. Low-privileged local access and the ability to issue the crafted block-device write are required; the reported consequence is availability loss without confidentiality or integrity impact.
The record
- CVE
- CVE-2024-38604
- Published
- Jun 19, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=487c607df790d366e67a7d6a30adf785cdd98e55 <0c12028aec837f5a002009bbf68d179d506510e8
- Affected versionversion=487c607df790d366e67a7d6a30adf785cdd98e55 <10b723bcba8986537a484aa94dbfc9093fd776a1
- Affected versionversion=487c607df790d366e67a7d6a30adf785cdd98e55 <72c54e063c32aeb38d43a2bd897821e6e5a1757d
- Affected versionversion=487c607df790d366e67a7d6a30adf785cdd98e55 <910717920c8c3f9386277a44c44d448058a18084
- Affected versionversion=6.6
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