{"vulnerability": "CVE-2024-53143", "sightings": [{"uuid": "58100c39-9bf2-4fda-b43e-d0e484ded62f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-53143", "type": "seen", "source": "https://t.me/cvedetector/12314", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-53143 - \"Linux Kernel fsnotify UAF\"\", \n  \"Content\": \"CVE ID : CVE-2024-53143 \nPublished : Dec. 7, 2024, 7:15 a.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfsnotify: Fix ordering of iput() and watched_objects decrement  \n  \nEnsure the superblock is kept alive until we're done with iput().  \nHolding a reference to an inode is not allowed unless we ensure the  \nsuperblock stays alive, which fsnotify does by keeping the  \nwatched_objects count elevated, so iput() must happen before the  \nwatched_objects decrement.  \nThis can lead to a UAF of something like sb->s_fs_info in tmpfs, but the  \nUAF is hard to hit because race orderings that oops are more likely, thanks  \nto the CHECK_DATA_CORRUPTION() block in generic_shutdown_super().  \n  \nAlso, ensure that fsnotify_put_sb_watched_objects() doesn't call  \nfsnotify_sb_watched_objects() on a superblock that may have already been  \nfreed, which would cause a UAF read of sb->s_fsnotify_info. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-07T09:11:34.000000Z"}]}