CVE-2024-1048: Grub2: grub2-set-bootflag can be abused by local (pseudo-)users
A flaw was found in the grub2-set-bootflag utility of grub2. After the fix of CVE-2019-14865, grub2-set-bootflag will create a temporary file with the new grubenv content and rename it to the original grubenv file. If the program is killed before the rename operation, the temporary file will not be removed and may fill the filesystem when invoked multiple times, resulting in a filesystem out of free inodes or blocks.
Other sources
A flaw was found in the grub2-set-bootflag utility of grub2. After the fix of CVE-2019-14865, grub2-set-bootflag will create a temporary file with the new grubenv content and rename it to the original grubenv file. If the program is killed before the rename operation, the temporary file will not be removed and may fill the filesystem when invoked multiple times, resulting in a filesystem out of free inodes or out of free blocks.
Reference: https://www.openwall.com/lists/oss-security/2024/02/06/3
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-1048?
CVE-2024-1048 has been classified as a moderate severity vulnerability.
How do I fix CVE-2024-1048?
To fix CVE-2024-1048, update the grub2 package to the latest version provided by your distribution.
What software is affected by CVE-2024-1048?
CVE-2024-1048 affects the grub2-set-bootflag utility in GNU Grub2, Red Hat Enterprise Linux 8.0 and 9.0, and Fedora 40.
What is the impact of CVE-2024-1048?
The impact of CVE-2024-1048 may allow unauthorized manipulation of the grubenv file if exploited.
Is there a workaround for CVE-2024-1048?
Currently, the recommended approach is to apply the relevant updates to mitigate CVE-2024-1048.