CVE-2024-56581: btrfs: ref-verify: fix use-after-free after invalid ref action

Published Dec 27, 2024
·
Updated

btrfs: ref-verify: fix use-after-free after invalid ref action

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

13 affected componentsFixes available
Linux Linux kernel>=4.15<5.4.287
Linux Linux kernel>=5.5<5.10.231
Linux Linux kernel>=5.11<5.15.174
Linux Linux kernel>=5.16<6.1.120
Linux Linux kernel>=6.2<6.6.64
Linux Linux kernel>=6.7<6.12.4
Linux Linux kernel=6.13-rc1
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.176.3-1
Microsoft azl3 kernel 6.6.57.1-7
Microsoft azl3 kernel 6.6.64.2-1
Microsoft cbl2 kernel 5.15.173.1-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Compensating control

    For Btrfs systems affected by the btrfs: ref-verify: fix use-after-free after invalid ref action issue, ensure the kernel change that removes the newly inserted ref entry from the respective block entry's rbtree on the error path in btrfs_ref_tree_mod() (when encountering an unexpected BTRFS_DROP_DELAYED_REF action) is applied, so the freed ref entry is not left referenced in the rbtree during btrfs_free_ref_cache()/free_block_entry().

Event History

Dec 27, 2024
CVE Published
via MITRE·02:23 PM
Data Sourced
via MITRE·02:23 PM
DescriptionSeverity
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 29, 2025
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
DescriptionSeverity
Mar 27, 2025
Data Sourced
via Launchpad·06:44 PM
Description
May 2, 2025
Data Sourced
via Ubuntu·06:52 PM
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-56581?

The severity of CVE-2024-56581 is classified as high due to its potential for exploitation leading to use-after-free vulnerabilities.

2

How do I fix CVE-2024-56581?

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

3

Which Linux kernel versions are affected by CVE-2024-56581?

CVE-2024-56581 affects various versions of the Linux kernel from 4.15 to 6.13-rc1.

4

What is the impact of CVE-2024-56581?

The impact of CVE-2024-56581 includes the potential for a remote attacker to execute arbitrary code or crash the system.

5

Is CVE-2024-56581 exploitable remotely?

Yes, CVE-2024-56581 may be exploitable remotely, depending on the specific configuration and environment.

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