CVE-2024-53143: fsnotify: Fix ordering of iput() and watched_objects decrement

Published Dec 7, 2024
·
Updated

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

fsnotify: Fix ordering of iput() and watchedobjects decrement

Ensure the superblock is kept alive until we're done with iput(). Holding a reference to an inode is not allowed unless we ensure the superblock stays alive, which fsnotify does by keeping the watchedobjects count elevated, so iput() must happen before the watchedobjects decrement. This can lead to a UAF of something like sb->sfsinfo in tmpfs, but the UAF is hard to hit because race orderings that oops are more likely, thanks to the CHECKDATACORRUPTION() block in genericshutdownsuper().

Also, ensure that fsnotifyputsbwatchedobjects() doesn't call fsnotifysbwatchedobjects() on a superblock that may have already been freed, which would cause a UAF read of sb->sfsnotifyinfo.

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

4 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=6.10<6.11.11
Linux Linux kernel>=6.12<6.12.2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1

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.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1

Event History

Dec 7, 2024
CVE Published
via MITRE·06:40 AM
Data Sourced
via MITRE·06:40 AM
DescriptionSeverity
Data Sourced
via Red Hat·07:01 AM
DescriptionSeverityAffected Software
Feb 20, 2025
Data Sourced
via Launchpad·12:52 AM
Description
Mar 28, 2025
Data Sourced
via Ubuntu·01:00 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-53143?

CVE-2024-53143 has a medium severity rating due to its potential impact on system stability.

2

How do I fix CVE-2024-53143?

To fix CVE-2024-53143, update your Linux kernel to versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.15-1.

3

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

CVE-2024-53143 affects various versions of the Linux kernel prior to the fixed updates mentioned in the remedy.

4

What does CVE-2024-53143 imply for system stability?

CVE-2024-53143 could lead to instability in systems by improperly managing inode references related to the superblock.

5

Is CVE-2024-53143 a remote exploitation risk?

CVE-2024-53143 is not classified as a remote exploitation risk but can affect local system operations.

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