CVE-2024-53143: fsnotify: Fix ordering of iput() and watched_objects decrement
First published: Sat Dec 07 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: fsnotify: Fix ordering of iput() and watched_objects 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 watched_objects count elevated, so iput() must happen before the watched_objects decrement. This can lead to a UAF of something like sb->s_fs_info in tmpfs, but the UAF is hard to hit because race orderings that oops are more likely, thanks to the CHECK_DATA_CORRUPTION() block in generic_shutdown_super(). Also, ensure that fsnotify_put_sb_watched_objects() doesn't call fsnotify_sb_watched_objects() on a superblock that may have already been freed, which would cause a UAF read of sb->s_fsnotify_info.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/21d1b618b6b9da46c5116c640ac4b1cc8d40d63a
- https://git.kernel.org/stable/c/45a8f8232a495221ed058191629f5c628f21601a
- https://git.kernel.org/stable/c/83af1cfa10d9aafdabd06b3655e07727f373b434
- https://project-zero.issues.chromium.org/issues/379667898
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53143
- https://nvd.nist.gov/vuln/detail/CVE-2024-53143
- https://launchpad.net/bugs/cve/CVE-2024-53143
- https://security-tracker.debian.org/tracker/CVE-2024-53143
- https://ubuntu.com/security/CVE-2024-53143
- https://git.kernel.org/linus/21d1b618b6b9da46c5116c640ac4b1cc8d40d63a
Frequently Asked Questions
What is the severity of CVE-2024-53143?
CVE-2024-53143 has a medium severity rating due to its potential impact on system stability.
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.
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.
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.
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.
- agent/title
- agent/type
- agent/first-publish-date
- agent/author
- agent/weakness
- agent/severity
- collector/nvd-api
- source/NVD
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- collector/nvd-cve
- agent/source
- agent/references
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian