Answer in brief
CVE-2024-53143 records a High severity (CVSS 7.8) vulnerability in fsnotify: Fix ordering of iput() and watched_objects decrement. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d2f277e26f521ccf6fb438463b41dba6123caabe <45a8f8232a495221ed058191629f5c628f21601a || >=d2f277e26f521ccf6fb438463b41dba6123caabe <83af1cfa10d9aafdabd06b3655e07727f373b434 || >=d2f277e26f521ccf6fb438463b41dba6123caabe <21d1b618b6b9da46c5116c640ac4b1cc8d40d63a | 45a8f8232a495221ed058191629f5c628f21601a, 83af1cfa10d9aafdabd06b3655e07727f373b434, 21d1b618b6b9da46c5116c640ac4b1cc8d40d63a |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Dec 7, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.