Local denial of service via orphaned temporary files
Published Feb 6, 2024 · Updated Nov 20, 2025
Temporary-file cleanup failure in Red Hat Enterprise Linux 8 and 9 allows local users to exhaust /boot filesystem inodes. The SUID grub2-set-bootflag utility writes new grubenv content to a temporary file but does not remove it when termination occurs before rename. A low-privilege local account can repeatedly trigger reliable SIGXFSZ termination until the affected filesystem cannot create new files.
Summary
What happened
Temporary-file cleanup failure in Red Hat Enterprise Linux 8 and 9 allows local users to exhaust /boot filesystem inodes. The SUID grub2-set-bootflag utility writes new grubenv content to a temporary file but does not remove it when termination occurs before rename. A low-privilege local account can repeatedly trigger reliable SIGXFSZ termination until the affected filesystem cannot create new files.
The record
- CVE
- CVE-2024-1048
- Published
- Feb 6, 2024
- Updated
- Nov 20, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-459, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
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