CVE-2024-50013: exfat: fix memory leak in exfat_load_bitmap()

Published Oct 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

exfat: fix memory leak in exfatloadbitmap()

If the first directory entry in the root directory is not a bitmap directory entry, 'bh' will not be released and reassigned, which will cause a memory leak.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

8 affected componentsFixes available
Linux Linux kernel>=5.7<5.10.227
Linux Linux kernel>=5.11<5.15.168
Linux Linux kernel>=5.16<6.1.113
Linux Linux kernel>=6.2<6.6.55
Linux Linux kernel>=6.7<6.10.14
Linux Linux kernel>=6.11<6.11.3
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1

Event History

Oct 21, 2024
CVE Published
via MITRE·06:54 PM
Data Sourced
via MITRE·06:54 PM
Description
Data Sourced
via Red Hat·07:03 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 12, 2025
Data Sourced
via Launchpad·05:17 AM
Description
Apr 29, 2025
Data Sourced
via Ubuntu·06:30 AM
RemedyDescriptionSeverityAffected Software
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-2024-50013?

The severity of CVE-2024-50013 is classified as moderate due to the memory leak vulnerability in the Linux kernel.

2

How do I fix CVE-2024-50013?

To fix CVE-2024-50013, update the Linux kernel to a version that includes the patch for this vulnerability.

3

Which versions of the Linux kernel are affected by CVE-2024-50013?

CVE-2024-50013 affects Linux kernel versions between 5.7 and 6.11.3.

4

Is a workaround available for CVE-2024-50013?

There is no specific workaround for CVE-2024-50013; upgrading the kernel is recommended instead.

5

What can happen if CVE-2024-50013 is exploited?

If CVE-2024-50013 is exploited, it may lead to a denial of service due to excessive memory usage.

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