fsnotify: Fix ordering of iput() and watched_objects decrement
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.11.11, 6.12.2
- CVEs
- CVE-2024-53143
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 21:41 UTC · Revision 1
Source evidence
fsnotify: Fix ordering of iput() and watched_objects decrement
core-osv · Original sourcePublished 7 Dec 2024, 06:40 UTC
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.
osv:CVE-2024-53143
Kernel
Fixed versions: 6.11.11, 6.12.2
Complete source record
{
"id": "c800f0367f1d510a5672cc7190653004726ef01b66b8e205daff425c35d590b0",
"url": "https://osv.dev/vulnerability/CVE-2024-53143",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "fsnotify: Fix ordering of iput() and watched_objects decrement",
"summary": "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.",
"evidence": "osv:CVE-2024-53143",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.11.11",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-53143",
"aliases": [
"CVE-2024-53143"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d2f277e26f521ccf6fb438463b41dba6123caabe"
},
{
"fixed": "45a8f8232a495221ed058191629f5c628f21601a"
},
{
"fixed": "83af1cfa10d9aafdabd06b3655e07727f373b434"
},
{
"fixed": "21d1b618b6b9da46c5116c640ac4b1cc8d40d63a"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-53143.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.10.0"
},
{
"fixed": "6.11.11"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.12.0"
},
{
"fixed": "6.12.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-53143.json"
}
}
],
"modified": "2026-10-28T02:30:24.203408734Z",
"provider": "osv",
"references": [
"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://github.com/CVEProject/cvelistV5/tree/main/cves/2024/53xxx/CVE-2024-53143.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-53143",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/53xxx/CVE-2024-53143.json"
}
},
"related_cves": [
{
"value": "CVE-2024-53143",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 490317,
"published_at": "2024-12-07T06:40:43.522+00:00"
}