CVE-2022-49914: btrfs: fix inode list leak during backref walking at resolve_indirect_refs()

Published May 1, 2025
·
Updated

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

btrfs: fix inode list leak during backref walking at resolveindirectrefs()

During backref walking, at resolveindirectrefs(), if we get an error we jump to the 'out' label and call ulistfree() on the 'parents' ulist, which frees all the elements in the ulist - however that does not free any inode lists that may be attached to elements, through the 'aux' field of a ulist node, so we end up leaking lists if we have any attached to the unodes.

Fix this by calling freeleaflist() instead of ulistfree() when we exit from resolveindirectrefs(). The static function freeleaflist() is moved up for this to be possible and it's slightly simplified by removing unnecessary code.

Affected Software

10 affected components
Linux Linux kernel
Linux Linux kernel>=3.5<4.14.299
Linux Linux kernel>=4.15<4.19.265
Linux Linux kernel>=4.20<5.4.224
Linux Linux kernel>=5.5<5.10.154
Linux Linux kernel>=5.11<5.15.78
Linux Linux kernel>=5.16<6.0.8
Linux Linux kernel=6.1-rc1
Linux Linux kernel=6.1-rc2
Linux Linux kernel=6.1-rc3

Event History

May 1, 2025
CVE Published
via MITRE·02:10 PM
Data Sourced
via MITRE·02:10 PM
Description
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2022-49914?

CVE-2022-49914 is categorized as a medium severity vulnerability in the Linux kernel.

2

How do I fix CVE-2022-49914?

To fix CVE-2022-49914, you should update your Linux kernel to the latest stable version provided by your distribution.

3

What are the potential impacts of exploiting CVE-2022-49914?

Exploiting CVE-2022-49914 may lead to memory leaks and potential denial of service conditions.

4

Which versions of the Linux kernel are affected by CVE-2022-49914?

CVE-2022-49914 affects multiple versions of the Linux kernel prior to the resolution in the latest releases.

5

Is there a workaround for CVE-2022-49914?

There are no specific workarounds for CVE-2022-49914; updating the kernel is the recommended action.

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