CVE-2023-54119

inotify: Avoid reporting event with invalid wd

N/A

Published: December 24, 2025 at 01:06 PM UTC

Updated: June 17, 2026 at 06:46 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: inotify: Avoid reporting event with invalid wd When inotify_freeing_mark() races with inotify_handle_inode_event() it can happen that inotify_handle_inode_event() sees that i_mark->wd got already reset to -1 and reports this value to userspace which can confuse the inotify listener. Avoid the problem by validating that wd is sensible (and pretend the mark got removed before the event got generated otherwise).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.31 ≤ v < 5.10.1802.6.31 ≤ v < 5.15.1122.6.31 ≤ v < 5.4.2432.6.31 ≤ v < 6.1.292.6.31 ≤ v < 6.2.162.6.31 ≤ v < 6.3.32.6.31 ≤ v < 6.42.6.317e790dd5fc937bc8d2400c30a05e32a9e9eef276

Vendor states this is fixed in 145f54ea336b06cf4f92eeee996f2ffca939ea43 (fixed)

Vendor states this is fixed in 17ad86d8c12220de97e80d88b5b4c934a40e1812 (fixed)

Vendor states this is fixed in 2d65c97777e5b4a845637800d5d7b648f5772106 (fixed)

Vendor states this is fixed in 8fb33166aed888769ea63d6af49515893f8a1f14 (fixed)

Vendor states this is fixed in a48bacee05860c6089c3482bcdc80720b0ee5732 (fixed)

Vendor states this is fixed in c915d8f5918bea7c3962b09b8884ca128bfd9b0c (fixed)

Vendor states this is fixed in fb3294998489d39835006240e9c6e6b2ac62022e (fixed)

Vendor states this is fixed in 2.6.31 (unaffected)

Vendor states this is fixed in 5.10.180 (unaffected)

Vendor states this is fixed in 5.15.112 (unaffected)

Vendor states this is fixed in 5.4.243 (unaffected)

Vendor states this is fixed in 6.1.29 (unaffected)