grub2 - Debian Package Tracker

general

source: grub2 (main)
version: 2.12-7
maintainer: GRUB Maintainers (archive) (DMD)
uploaders: Steve McIntyre [DMD] – Jordi Mallach [DMD] – Julian Andres Klode [DMD] – Felix Zielcke [DMD] [DM] – Mate Kukri [DMD]
arch: any
std-ver: 3.9.6
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.06-3~deb10u1
o-o-sec: 2.06-3~deb10u4
oldstable: 2.06-3~deb11u6
old-sec: 2.06-3~deb11u6
old-upd: 2.06-3~deb11u2
stable: 2.06-13+deb12u1
stable-sec: 2.06-13+deb12u1
stable-bpo: 2.12-1~bpo12+1
testing: 2.12-7
unstable: 2.12-7

versioned links

2.06-3~deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.06-3~deb10u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.06-3~deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.06-3~deb11u6: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.06-13+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.12-1~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.12-7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

grub-common (168 bugs: 1, 120, 47, 0)
grub-coreboot (1 bugs: 0, 0, 1, 0)
grub-coreboot-bin (1 bugs: 0, 1, 0, 0)
grub-coreboot-dbg
grub-efi (12 bugs: 0, 12, 0, 0)
grub-efi-amd64 (56 bugs: 7, 40, 9, 0)
grub-efi-amd64-bin (12 bugs: 0, 12, 0, 0)
grub-efi-amd64-dbg
grub-efi-amd64-signed-template
grub-efi-amd64-unsigned
grub-efi-arm (2 bugs: 0, 2, 0, 0)
grub-efi-arm-bin
grub-efi-arm-dbg
grub-efi-arm-unsigned
grub-efi-arm64 (5 bugs: 1, 4, 0, 0)
grub-efi-arm64-bin (1 bugs: 0, 1, 0, 0)
grub-efi-arm64-dbg
grub-efi-arm64-signed-template
grub-efi-arm64-unsigned
grub-efi-ia32 (5 bugs: 0, 4, 1, 0)
grub-efi-ia32-bin
grub-efi-ia32-dbg
grub-efi-ia32-signed-template
grub-efi-ia32-unsigned
grub-efi-ia64
grub-efi-ia64-bin
grub-efi-ia64-dbg
grub-efi-ia64-unsigned
grub-efi-loong64
grub-efi-loong64-bin
grub-efi-loong64-dbg
grub-efi-loong64-unsigned
grub-efi-riscv64
grub-efi-riscv64-bin
grub-efi-riscv64-dbg
grub-efi-riscv64-unsigned
grub-emu (1 bugs: 1, 0, 0, 0)
grub-emu-dbg
grub-firmware-qemu
grub-ieee1275 (7 bugs: 0, 6, 1, 0)
grub-ieee1275-bin (1 bugs: 0, 1, 0, 0)
grub-ieee1275-dbg
grub-linuxbios
grub-mount-udeb
grub-pc (258 bugs: 2, 204, 52, 0)
grub-pc-bin (7 bugs: 0, 6, 1, 0)
grub-pc-dbg (1 bugs: 1, 0, 0, 0)
grub-rescue-pc (3 bugs: 0, 1, 2, 0)
grub-theme-starfield
grub-uboot (1 bugs: 0, 1, 0, 0)
grub-uboot-bin
grub-uboot-dbg
grub-xen (3 bugs: 0, 2, 1, 0)
grub-xen-bin
grub-xen-dbg
grub-xen-host (4 bugs: 0, 4, 0, 0)
grub-yeeloong
grub-yeeloong-bin
grub-yeeloong-dbg
grub2 (67 bugs: 0, 47, 20, 0)
grub2-common (66 bugs: 2, 41, 23, 0)

action needed

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2025-4382: A flaw was found in systems utilizing LUKS-encrypted disks with GRUB configured for TPM-based auto-decryption. When GRUB is set to automatically decrypt disks using keys stored in the TPM, it reads the decryption key into system memory. If an attacker with physical access can corrupt the underlying filesystem superblock, GRUB will fail to locate a valid filesystem and enter rescue mode. At this point, the disk is already decrypted, and the decryption key remains loaded in system memory. This scenario may allow an attacker with physical access to access the unencrypted data without any further authentication, thereby compromising data confidentiality. Furthermore, the ability to force this state through filesystem corruption also presents a data integrity concern.
CVE-2024-56738: GNU GRUB (aka GRUB2) through 2.12 does not use a constant-time algorithm for grub_crypto_memcmp and thus allows side-channel attacks.

Created: 2024-12-20 Last update: 2025-05-10 10:57

25 security issues in bullseye high

There are 25 open security issues in bullseye.

24 important issues:

CVE-2025-0622: A flaw was found in command/gpg. In some scenarios, hooks created by loaded modules are not removed when the related module is unloaded. This flaw allows an attacker to force grub2 to call the hooks once the module that registered it was unloaded, leading to a use-after-free vulnerability. If correctly exploited, this vulnerability may result in arbitrary code execution, eventually allowing the attacker to bypass secure boot protections.
CVE-2025-0624: A flaw was found in grub2. During the network boot process, when trying to search for the configuration file, grub copies data from a user controlled environment variable into an internal buffer using the grub_strcpy() function. During this step, it fails to consider the environment variable length when allocating the internal buffer, resulting in an out-of-bounds write. If correctly exploited, this issue may result in remote code execution through the same network segment grub is searching for the boot information, which can be used to by-pass secure boot protections.
CVE-2025-0677: A flaw was found in grub2. When performing a symlink lookup, the grub's UFS module checks the inode's data size to allocate the internal buffer to read the file content, however, it fails to check if the symlink data size has overflown. When this occurs, grub_malloc() may be called with a smaller value than needed. When further reading the data from the disk into the buffer, the grub_ufs_lookup_symlink() function will write past the end of the allocated size. An attack can leverage this by crafting a malicious filesystem, and as a result, it will corrupt data stored in the heap, allowing for arbitrary code execution used to by-pass secure boot mechanisms.
CVE-2025-0678: A flaw was found in grub2. When reading data from a squash4 filesystem, grub's squash4 fs module uses user-controlled parameters from the filesystem geometry to determine the internal buffer size, however, it improperly checks for integer overflows. A maliciously crafted filesystem may lead some of those buffer size calculations to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result, the direct_read() will perform a heap based out-of-bounds write during data reading. This flaw may be leveraged to corrupt grub's internal critical data and may result in arbitrary code execution, by-passing secure boot protections.
CVE-2025-0684: A flaw was found in grub2. When performing a symlink lookup from a reiserfs filesystem, grub's reiserfs fs module uses user-controlled parameters from the filesystem geometry to determine the internal buffer size, however, it improperly checks for integer overflows. A maliciouly crafted filesystem may lead some of those buffer size calculations to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result, the grub_reiserfs_read_symlink() will call grub_reiserfs_read_real() with a overflown length parameter, leading to a heap based out-of-bounds write during data reading. This flaw may be leveraged to corrupt grub's internal critical data and can result in arbitrary code execution, by-passing secure boot protections.
CVE-2025-0685: A flaw was found in grub2. When reading data from a jfs filesystem, grub's jfs filesystem module uses user-controlled parameters from the filesystem geometry to determine the internal buffer size, however, it improperly checks for integer overflows. A maliciouly crafted filesystem may lead some of those buffer size calculations to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result, the grub_jfs_lookup_symlink() function will write past the internal buffer length during grub_jfs_read_file(). This issue can be leveraged to corrupt grub's internal critical data and may result in arbitrary code execution, by-passing secure boot protections.
CVE-2025-0686: A flaw was found in grub2. When performing a symlink lookup from a romfs filesystem, grub's romfs filesystem module uses user-controlled parameters from the filesystem geometry to determine the internal buffer size, however, it improperly checks for integer overflows. A maliciously crafted filesystem may lead some of those buffer size calculations to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result, the grub_romfs_read_symlink() may cause out-of-bounds writes when the calling grub_disk_read() function. This issue may be leveraged to corrupt grub's internal critical data and can result in arbitrary code execution by-passing secure boot protections.
CVE-2025-0689: When reading data from disk, the grub's UDF filesystem module utilizes the user controlled data length metadata to allocate its internal buffers. In certain scenarios, while iterating through disk sectors, it assumes the read size from the disk is always smaller than the allocated buffer size which is not guaranteed. A crafted filesystem image may lead to a heap-based buffer overflow resulting in critical data to be corrupted, resulting in the risk of arbitrary code execution by-passing secure boot protections.
CVE-2025-0690: The read command is used to read the keyboard input from the user, while reads it keeps the input length in a 32-bit integer value which is further used to reallocate the line buffer to accept the next character. During this process, with a line big enough it's possible to make this variable to overflow leading to a out-of-bounds write in the heap based buffer. This flaw may be leveraged to corrupt grub's internal critical data and secure boot bypass is not discarded as consequence.
CVE-2025-1118: A flaw was found in grub2. Grub's dump command is not blocked when grub is in lockdown mode, which allows the user to read any memory information, and an attacker may leverage this in order to extract signatures, salts, and other sensitive information from the memory.
CVE-2025-1125: When reading data from a hfs filesystem, grub's hfs filesystem module uses user-controlled parameters from the filesystem metadata to calculate the internal buffers size, however it misses to properly check for integer overflows. A maliciouly crafted filesystem may lead some of those buffer size calculation to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result the hfsplus_open_compressed_real() function will write past of the internal buffer length. This flaw may be leveraged to corrupt grub's internal critical data and may result in arbitrary code execution by-passing secure boot protections.
CVE-2025-4382: A flaw was found in systems utilizing LUKS-encrypted disks with GRUB configured for TPM-based auto-decryption. When GRUB is set to automatically decrypt disks using keys stored in the TPM, it reads the decryption key into system memory. If an attacker with physical access can corrupt the underlying filesystem superblock, GRUB will fail to locate a valid filesystem and enter rescue mode. At this point, the disk is already decrypted, and the decryption key remains loaded in system memory. This scenario may allow an attacker with physical access to access the unencrypted data without any further authentication, thereby compromising data confidentiality. Furthermore, the ability to force this state through filesystem corruption also presents a data integrity concern.
CVE-2024-45774: A flaw was found in grub2. A specially crafted JPEG file can cause the JPEG parser of grub2 to incorrectly check the bounds of its internal buffers, resulting in an out-of-bounds write. The possibility of overwriting sensitive information to bypass secure boot protections is not discarded.
CVE-2024-45775: A flaw was found in grub2 where the grub_extcmd_dispatcher() function calls grub_arg_list_alloc() to allocate memory for the grub's argument list. However, it fails to check in case the memory allocation fails. Once the allocation fails, a NULL point will be processed by the parse_option() function, leading grub to crash or, in some rare scenarios, corrupt the IVT data.
CVE-2024-45776: When reading the language .mo file in grub_mofile_open(), grub2 fails to verify an integer overflow when allocating its internal buffer. A crafted .mo file may lead the buffer size calculation to overflow, leading to out-of-bound reads and writes. This flaw allows an attacker to leak sensitive data or overwrite critical data, possibly circumventing secure boot protections.
CVE-2024-45777: A flaw was found in grub2. The calculation of the translation buffer when reading a language .mo file in grub_gettext_getstr_from_position() may overflow, leading to a Out-of-bound write. This issue can be leveraged by an attacker to overwrite grub2's sensitive heap data, eventually leading to the circumvention of secure boot protections.
CVE-2024-45778: A stack overflow flaw was found when reading a BFS file system. A crafted BFS filesystem may lead to an uncontrolled loop, causing grub2 to crash.
CVE-2024-45779: An integer overflow flaw was found in the BFS file system driver in grub2. When reading a file with an indirect extent map, grub2 fails to validate the number of extent entries to be read. A crafted or corrupted BFS filesystem may cause an integer overflow during the file reading, leading to a heap of bounds read. As a consequence, sensitive data may be leaked, or grub2 will crash.
CVE-2024-45780: A flaw was found in grub2. When reading tar files, grub2 allocates an internal buffer for the file name. However, it fails to properly verify the allocation against possible integer overflows. It's possible to cause the allocation length to overflow with a crafted tar file, leading to a heap out-of-bounds write. This flaw eventually allows an attacker to circumvent secure boot protections.
CVE-2024-45781: A flaw was found in grub2. When reading a symbolic link's name from a UFS filesystem, grub2 fails to validate the string length taken as an input. The lack of validation may lead to a heap out-of-bounds write, causing data integrity issues and eventually allowing an attacker to circumvent secure boot protections.
CVE-2024-45782: A flaw was found in the HFS filesystem. When reading an HFS volume's name at grub_fs_mount(), the HFS filesystem driver performs a strcpy() using the user-provided volume name as input without properly validating the volume name's length. This issue may read to a heap-based out-of-bounds writer, impacting grub's sensitive data integrity and eventually leading to a secure boot protection bypass.
CVE-2024-45783: A flaw was found in grub2. When failing to mount an HFS+ grub, the hfsplus filesystem driver doesn't properly set an ERRNO value. This issue may lead to a NULL pointer access.
CVE-2024-56737: GNU GRUB (aka GRUB2) through 2.12 has a heap-based buffer overflow in fs/hfs.c via crafted sblock data in an HFS filesystem.
CVE-2024-56738: GNU GRUB (aka GRUB2) through 2.12 does not use a constant-time algorithm for grub_crypto_memcmp and thus allows side-channel attacks.

1 issue postponed or untriaged:

CVE-2021-3981: (needs triaging) A flaw in grub2 was found where its configuration file, known as grub.cfg, is being created with the wrong permission set allowing non privileged users to read its content. This represents a low severity confidentiality issue, as those users can eventually read any encrypted passwords present in grub.cfg. This flaw affects grub2 2.06 and previous versions. This issue has been fixed in grub upstream but no version with the fix is currently released.

Created: 2024-12-20 Last update: 2025-05-10 10:57

24 security issues in bookworm high

There are 24 open security issues in bookworm.

1 important issue:

CVE-2025-4382: A flaw was found in systems utilizing LUKS-encrypted disks with GRUB configured for TPM-based auto-decryption. When GRUB is set to automatically decrypt disks using keys stored in the TPM, it reads the decryption key into system memory. If an attacker with physical access can corrupt the underlying filesystem superblock, GRUB will fail to locate a valid filesystem and enter rescue mode. At this point, the disk is already decrypted, and the decryption key remains loaded in system memory. This scenario may allow an attacker with physical access to access the unencrypted data without any further authentication, thereby compromising data confidentiality. Furthermore, the ability to force this state through filesystem corruption also presents a data integrity concern.

23 issues left for the package maintainer to handle:

CVE-2025-0622: (needs triaging) A flaw was found in command/gpg. In some scenarios, hooks created by loaded modules are not removed when the related module is unloaded. This flaw allows an attacker to force grub2 to call the hooks once the module that registered it was unloaded, leading to a use-after-free vulnerability. If correctly exploited, this vulnerability may result in arbitrary code execution, eventually allowing the attacker to bypass secure boot protections.
CVE-2025-0624: (needs triaging) A flaw was found in grub2. During the network boot process, when trying to search for the configuration file, grub copies data from a user controlled environment variable into an internal buffer using the grub_strcpy() function. During this step, it fails to consider the environment variable length when allocating the internal buffer, resulting in an out-of-bounds write. If correctly exploited, this issue may result in remote code execution through the same network segment grub is searching for the boot information, which can be used to by-pass secure boot protections.
CVE-2025-0677: (needs triaging) A flaw was found in grub2. When performing a symlink lookup, the grub's UFS module checks the inode's data size to allocate the internal buffer to read the file content, however, it fails to check if the symlink data size has overflown. When this occurs, grub_malloc() may be called with a smaller value than needed. When further reading the data from the disk into the buffer, the grub_ufs_lookup_symlink() function will write past the end of the allocated size. An attack can leverage this by crafting a malicious filesystem, and as a result, it will corrupt data stored in the heap, allowing for arbitrary code execution used to by-pass secure boot mechanisms.
CVE-2025-0678: (needs triaging) A flaw was found in grub2. When reading data from a squash4 filesystem, grub's squash4 fs module uses user-controlled parameters from the filesystem geometry to determine the internal buffer size, however, it improperly checks for integer overflows. A maliciously crafted filesystem may lead some of those buffer size calculations to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result, the direct_read() will perform a heap based out-of-bounds write during data reading. This flaw may be leveraged to corrupt grub's internal critical data and may result in arbitrary code execution, by-passing secure boot protections.
CVE-2025-0684: (needs triaging) A flaw was found in grub2. When performing a symlink lookup from a reiserfs filesystem, grub's reiserfs fs module uses user-controlled parameters from the filesystem geometry to determine the internal buffer size, however, it improperly checks for integer overflows. A maliciouly crafted filesystem may lead some of those buffer size calculations to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result, the grub_reiserfs_read_symlink() will call grub_reiserfs_read_real() with a overflown length parameter, leading to a heap based out-of-bounds write during data reading. This flaw may be leveraged to corrupt grub's internal critical data and can result in arbitrary code execution, by-passing secure boot protections.
CVE-2025-0685: (needs triaging) A flaw was found in grub2. When reading data from a jfs filesystem, grub's jfs filesystem module uses user-controlled parameters from the filesystem geometry to determine the internal buffer size, however, it improperly checks for integer overflows. A maliciouly crafted filesystem may lead some of those buffer size calculations to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result, the grub_jfs_lookup_symlink() function will write past the internal buffer length during grub_jfs_read_file(). This issue can be leveraged to corrupt grub's internal critical data and may result in arbitrary code execution, by-passing secure boot protections.
CVE-2025-0686: (needs triaging) A flaw was found in grub2. When performing a symlink lookup from a romfs filesystem, grub's romfs filesystem module uses user-controlled parameters from the filesystem geometry to determine the internal buffer size, however, it improperly checks for integer overflows. A maliciously crafted filesystem may lead some of those buffer size calculations to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result, the grub_romfs_read_symlink() may cause out-of-bounds writes when the calling grub_disk_read() function. This issue may be leveraged to corrupt grub's internal critical data and can result in arbitrary code execution by-passing secure boot protections.
CVE-2025-0689: (needs triaging) When reading data from disk, the grub's UDF filesystem module utilizes the user controlled data length metadata to allocate its internal buffers. In certain scenarios, while iterating through disk sectors, it assumes the read size from the disk is always smaller than the allocated buffer size which is not guaranteed. A crafted filesystem image may lead to a heap-based buffer overflow resulting in critical data to be corrupted, resulting in the risk of arbitrary code execution by-passing secure boot protections.
CVE-2025-0690: (needs triaging) The read command is used to read the keyboard input from the user, while reads it keeps the input length in a 32-bit integer value which is further used to reallocate the line buffer to accept the next character. During this process, with a line big enough it's possible to make this variable to overflow leading to a out-of-bounds write in the heap based buffer. This flaw may be leveraged to corrupt grub's internal critical data and secure boot bypass is not discarded as consequence.
CVE-2025-1118: (needs triaging) A flaw was found in grub2. Grub's dump command is not blocked when grub is in lockdown mode, which allows the user to read any memory information, and an attacker may leverage this in order to extract signatures, salts, and other sensitive information from the memory.
CVE-2025-1125: (needs triaging) When reading data from a hfs filesystem, grub's hfs filesystem module uses user-controlled parameters from the filesystem metadata to calculate the internal buffers size, however it misses to properly check for integer overflows. A maliciouly crafted filesystem may lead some of those buffer size calculation to overflow, causing it to perform a grub_malloc() operation with a smaller size than expected. As a result the hfsplus_open_compressed_real() function will write past of the internal buffer length. This flaw may be leveraged to corrupt grub's internal critical data and may result in arbitrary code execution by-passing secure boot protections.
CVE-2024-45774: (needs triaging) A flaw was found in grub2. A specially crafted JPEG file can cause the JPEG parser of grub2 to incorrectly check the bounds of its internal buffers, resulting in an out-of-bounds write. The possibility of overwriting sensitive information to bypass secure boot protections is not discarded.
CVE-2024-45775: (needs triaging) A flaw was found in grub2 where the grub_extcmd_dispatcher() function calls grub_arg_list_alloc() to allocate memory for the grub's argument list. However, it fails to check in case the memory allocation fails. Once the allocation fails, a NULL point will be processed by the parse_option() function, leading grub to crash or, in some rare scenarios, corrupt the IVT data.
CVE-2024-45776: (needs triaging) When reading the language .mo file in grub_mofile_open(), grub2 fails to verify an integer overflow when allocating its internal buffer. A crafted .mo file may lead the buffer size calculation to overflow, leading to out-of-bound reads and writes. This flaw allows an attacker to leak sensitive data or overwrite critical data, possibly circumventing secure boot protections.
CVE-2024-45777: (needs triaging) A flaw was found in grub2. The calculation of the translation buffer when reading a language .mo file in grub_gettext_getstr_from_position() may overflow, leading to a Out-of-bound write. This issue can be leveraged by an attacker to overwrite grub2's sensitive heap data, eventually leading to the circumvention of secure boot protections.
CVE-2024-45778: (needs triaging) A stack overflow flaw was found when reading a BFS file system. A crafted BFS filesystem may lead to an uncontrolled loop, causing grub2 to crash.
CVE-2024-45779: (needs triaging) An integer overflow flaw was found in the BFS file system driver in grub2. When reading a file with an indirect extent map, grub2 fails to validate the number of extent entries to be read. A crafted or corrupted BFS filesystem may cause an integer overflow during the file reading, leading to a heap of bounds read. As a consequence, sensitive data may be leaked, or grub2 will crash.
CVE-2024-45780: (needs triaging) A flaw was found in grub2. When reading tar files, grub2 allocates an internal buffer for the file name. However, it fails to properly verify the allocation against possible integer overflows. It's possible to cause the allocation length to overflow with a crafted tar file, leading to a heap out-of-bounds write. This flaw eventually allows an attacker to circumvent secure boot protections.
CVE-2024-45781: (needs triaging) A flaw was found in grub2. When reading a symbolic link's name from a UFS filesystem, grub2 fails to validate the string length taken as an input. The lack of validation may lead to a heap out-of-bounds write, causing data integrity issues and eventually allowing an attacker to circumvent secure boot protections.
CVE-2024-45782: (needs triaging) A flaw was found in the HFS filesystem. When reading an HFS volume's name at grub_fs_mount(), the HFS filesystem driver performs a strcpy() using the user-provided volume name as input without properly validating the volume name's length. This issue may read to a heap-based out-of-bounds writer, impacting grub's sensitive data integrity and eventually leading to a secure boot protection bypass.
CVE-2024-45783: (needs triaging) A flaw was found in grub2. When failing to mount an HFS+ grub, the hfsplus filesystem driver doesn't properly set an ERRNO value. This issue may lead to a NULL pointer access.
CVE-2024-56737: (needs triaging) GNU GRUB (aka GRUB2) through 2.12 has a heap-based buffer overflow in fs/hfs.c via crafted sblock data in an HFS filesystem.
CVE-2024-56738: (postponed; to be fixed through a stable update) GNU GRUB (aka GRUB2) through 2.12 does not use a constant-time algorithm for grub_crypto_memcmp and thus allows side-channel attacks.

You can find information about how to handle these issues in the security team's documentation.

Created: 2024-12-20 Last update: 2025-05-10 10:57

2 security issues in trixie high

There are 2 open security issues in trixie.

1 important issue:

CVE-2025-4382: A flaw was found in systems utilizing LUKS-encrypted disks with GRUB configured for TPM-based auto-decryption. When GRUB is set to automatically decrypt disks using keys stored in the TPM, it reads the decryption key into system memory. If an attacker with physical access can corrupt the underlying filesystem superblock, GRUB will fail to locate a valid filesystem and enter rescue mode. At this point, the disk is already decrypted, and the decryption key remains loaded in system memory. This scenario may allow an attacker with physical access to access the unencrypted data without any further authentication, thereby compromising data confidentiality. Furthermore, the ability to force this state through filesystem corruption also presents a data integrity concern.

1 issue postponed or untriaged:

CVE-2024-56738: (postponed; to be fixed through a stable update) GNU GRUB (aka GRUB2) through 2.12 does not use a constant-time algorithm for grub_crypto_memcmp and thus allows side-channel attacks.

Created: 2025-05-10 Last update: 2025-05-10 10:57

lintian reports 421 errors and 161 warnings high

Lintian reports 421 errors and 161 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2025-03-16 Last update: 2025-03-16 12:01

debian/patches: 2 patches with invalid metadata, 131 patches to forward upstream high

Among the 146 debian patches available in version 2.12-7 of the package, we noticed the following issues:

2 patches with invalid metadata that ought to be fixed.
131 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2025-03-16 09:31

Standards version of the package is outdated. high

The package is severely out of date with respect to the Debian Policy. The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.2 instead of 3.9.6).

Created: 2016-02-06 Last update: 2025-03-16 00:25

58 bugs tagged patch in the BTS normal

The BTS contains patches fixing 58 bugs (70 if counting merged bugs), consider including or untagging them.

Created: 2025-01-06 Last update: 2025-05-11 10:00

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2022-09-24 Last update: 2025-05-11 09:22

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2020-02-26 Last update: 2025-03-16 03:04

Build log checks report 1 warning low

Build log checks report 1 warning

Created: 2014-07-02 Last update: 2014-07-02 18:05

news

[rss feed]

[2025-03-23] grub2 2.12-7 MIGRATED to testing (Debian testing watch)
[2025-03-15] Accepted grub2 2.12-7 (source) into unstable (Felix Zielcke)
[2025-03-13] Accepted grub2 2.12-6 (source) into unstable (Mate Kukri) (signed by: Julian Andres Klode)
[2024-07-21] grub2 2.12-5 MIGRATED to testing (Debian testing watch)
[2024-07-15] Accepted grub2 2.12-5 (source) into unstable (Felix Zielcke)
[2024-07-10] Accepted grub2 2.12-4 (source) into unstable (Felix Zielcke)
[2024-05-03] grub2 2.12-2 MIGRATED to testing (Debian testing watch)
[2024-04-25] Accepted grub2 2.12-3 (source amd64) into experimental (Debian FTP Masters) (signed by: Julian Andres Klode)
[2024-04-07] grub2 2.12-2~deb13u1 MIGRATED to testing (Debian testing watch)
[2024-04-05] Accepted grub2 2.12-2 (source) into unstable (Julian Andres Klode)
[2024-04-05] Accepted grub2 2.12-2~deb13u1 (source) into testing-proposed-updates (Julian Andres Klode)
[2024-04-03] Accepted grub2 2.12-1.1 (source) into unstable (Bastian Blank)
[2024-03-13] Accepted grub2 2.12-1~bpo12+1 (source amd64) into stable-backports (Debian FTP Masters) (signed by: John Goerzen)
[2024-02-01] grub2 2.12-1 MIGRATED to testing (Debian testing watch)
[2024-01-23] Accepted grub2 2.12-1 (source) into unstable (Mate Kukri) (signed by: Julian Andres Klode)
[2024-01-12] Accepted grub2 2.12~rc1-13 (source) into unstable (Julian Andres Klode)
[2023-11-09] Accepted grub2 2.12~rc1-12 (source) into unstable (Julian Andres Klode)
[2023-10-11] grub2 2.06-13+deb13u1 MIGRATED to testing (Debian testing watch)
[2023-10-10] Accepted grub2 2.06-3~deb11u6 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Julian Andres Klode)
[2023-10-10] Accepted grub2 2.06-13+deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Julian Andres Klode)
[2023-10-09] Accepted grub2 2.06-13+deb13u1 (source) into testing-proposed-updates (Julian Andres Klode)
[2023-10-06] Accepted grub2 2.06-3~deb11u6 (source) into oldstable-security (Debian FTP Masters) (signed by: Julian Andres Klode)
[2023-10-06] Accepted grub2 2.06-13+deb12u1 (source) into stable-security (Debian FTP Masters) (signed by: Julian Andres Klode)
[2023-10-03] Accepted grub2 2.12~rc1-11 (source) into unstable (Julian Andres Klode)
[2023-10-03] Accepted grub2 2.06-3~deb10u4 (source) into oldoldstable (Julian Andres Klode)
[2023-09-18] Accepted grub2 2.12~rc1-10 (source) into unstable (Julian Andres Klode)
[2023-09-05] Accepted grub2 2.12~rc1-9 (source) into unstable (Julian Andres Klode)
[2023-09-05] Accepted grub2 2.12~rc1-8 (source) into unstable (Julian Andres Klode)
[2023-09-04] Accepted grub2 2.12~rc1-7 (source) into unstable (Julian Andres Klode)
[2023-09-04] Accepted grub2 2.12~rc1-6 (source amd64) into experimental (Debian FTP Masters) (signed by: Julian Andres Klode)

bugs [bug history graph]

all: 700 731
RC: 16 17
I&N: 521 542
M&W: 161 170
F&P: 2
patch: 58 70

links

homepage
lintian (421, 161)
buildd: logs, checks, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
l10n (90, 80)
debian patches

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.12-5ubuntu11
267 bugs (19 patches)
patches for 2.12-5ubuntu11