CVE-2025-0685: Grub2: jfs: integer overflow when handling symlinks may lead to heap based out-of-bounds write when reading data

Published Feb 17, 2025
·
Updated

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 grubmalloc() operation with a smaller size than expected. As a result, the grubjfslookupsymlink() function will write past the internal buffer length during grubjfsreadfile(). This issue can be leveraged to corrupt grub's internal critical data and may result in arbitrary code execution, by-passing secure boot protections.

Other sources

Grub2: jfs: integer overflow when handling symlinks may lead to heap based out-of-bounds write when reading data

Microsoft

When reading data from a jfs filesystem, grub's jfs filesystem module uses user-controlled parameters from the filesystem geometry to determine 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 grubmalloc() operation with a smaller size than expected. As a result the grubjfslookupsymlink() function will write past of the internal buffer length during grubjfsreadfile(). This flaw may be leveraged to corrupt grub's internal critical data and may result in arbitrary code execution by-passing secure boot protections.

Red Hat

Affected Software

6 affected componentsFixes available
GNU GRUB2
GNU GRUB2<=2.12
Microsoft azl3 grub2 2.06-25<2.06-25
2.06-25
Microsoft cbl2 grub2 2.06-14<2.06-15
2.06-15
Microsoft cbl2 grub2 2.06-15<2.06-15
2.06-15
Microsoft azl3 grub2 2.06-24<2.06-25
2.06-25

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.06-25
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.06-15

Event History

Feb 17, 2025
Data Sourced
via Red Hat·03:28 PM
DescriptionSeverityAffected Software
Mar 3, 2025
CVE Published
via MITRE·05:14 PM
Data Sourced
via MITRE·05:14 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·03:05 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·03:05 PM
Affected Software
Updated
via Microsoft·03:05 PM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-0685?

CVE-2025-0685 has been rated as critical due to the potential for arbitrary code execution from a malicious JFS filesystem.

2

How do I fix CVE-2025-0685?

To mitigate CVE-2025-0685, update to the latest version of GRUB2 that has patched this vulnerability.

3

Who is affected by CVE-2025-0685?

CVE-2025-0685 affects systems running GNU GRUB2 that utilize JFS filesystems, particularly those without the latest security updates.

4

What impact does CVE-2025-0685 have on system security?

CVE-2025-0685 can lead to significant security risks, including the possibility of an attacker gaining unauthorized access to system resources.

5

Is CVE-2025-0685 related to filesystem vulnerabilities?

Yes, CVE-2025-0685 specifically involves vulnerabilities in the GRUB2 filesystem module when handling JFS filesystems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203