diff --git a/advisories/unreviewed/2024/12/GHSA-rfr4-95g9-6vf3/GHSA-rfr4-95g9-6vf3.json b/advisories/unreviewed/2024/12/GHSA-rfr4-95g9-6vf3/GHSA-rfr4-95g9-6vf3.json new file mode 100644 index 00000000000..96a8873d4f3 --- /dev/null +++ b/advisories/unreviewed/2024/12/GHSA-rfr4-95g9-6vf3/GHSA-rfr4-95g9-6vf3.json @@ -0,0 +1,37 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-rfr4-95g9-6vf3", + "modified": "2024-12-07T09:30:23Z", + "published": "2024-12-07T09:30:23Z", + "aliases": [ + "CVE-2024-53143" + ], + "details": "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.", + "severity": [], + "affected": [], + "references": [ + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53143" + }, + { + "type": "WEB", + "url": "https://git.kernel.org/stable/c/21d1b618b6b9da46c5116c640ac4b1cc8d40d63a" + }, + { + "type": "WEB", + "url": "https://git.kernel.org/stable/c/45a8f8232a495221ed058191629f5c628f21601a" + }, + { + "type": "WEB", + "url": "https://git.kernel.org/stable/c/83af1cfa10d9aafdabd06b3655e07727f373b434" + } + ], + "database_specific": { + "cwe_ids": [], + "severity": null, + "github_reviewed": false, + "github_reviewed_at": null, + "nvd_published_at": "2024-12-07T07:15:03Z" + } +} \ No newline at end of file