Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-89595

fsnotify: Fix stale object mask after concurrent mark updates

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
None on Exploit-DB, Metasploit or GitHub

Summary

In the Linux kernel, the following vulnerability has been resolved: fsnotify: Fix stale object mask after concurrent mark updates When a mark gets a new event bit, fanotify and inotify may avoid recalculating the object mask if the cached aggregate already contains that bit. This is racy with a recalculation triggered by a concurrent update to another mark on the same connector. The concurrent scan can read the mark before the new bit is added, while the updater reads the old aggregate before that scan publishes its result. The updater then skips recalculation and the scan publishes a mask without the bit, leaving the object mask stale after both updates complete. This can be reproduced with two fanotify groups watching the same inode: one thread removes FAN_MODIFY from one existing mark while another thread adds FAN_MODIFY to the other mark. After both fanotify_mark() calls return, writes can fail to produce FAN_MODIFY for the group whose mark now contains the bit. This was reproduced on an unmodified v6.12.95 kernel. The equivalent inotify interleaving loses IN_MODIFY events. For normal fanotify additions, recalculate whenever the raw mark mask changes. The normal mask is not cleared asynchronously, so an unchanged addition cannot introduce missing interest. Always recalculate ignore-mask updates because FS_MODIFY handling may clear the ignore mask without taking mark->lock, making snapshot comparisons unreliable. Always recalculate after updating an existing inotify watch. Its replace path temporarily sets mark->mask to zero, so a concurrent scan can observe zero even when the old and final masks are equal. Assigning the replacement mask directly would avoid the transient zero, but existing-watch updates are infrequent, so unconditional recalculation is simpler.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 63c882a05416e18de6fb59f7dd6da48f3bbe8273 · fixed in 27d172b60eeca5c8fd51b246f9fb959067cf102b; From 63c882a05416e18de6fb59f7dd6da48f3bbe8273 · fixed in 2f09f08d602647fc4e328fc27ecb4c3008d10338; From 63c882a05416e18de6fb59f7dd6da48f3bbe8273 · fixed in de75382d6e354b2b055df4896d12a91969f12090; From 63c882a05416e18de6fb59f7dd6da48f3bbe8273 · fixed in 343ae18e960f6c5f1d34d58a69750c62cd463228; From 63c882a05416e18de6fb59f7dd6da48f3bbe8273 · fixed in 92289e66639f62abc754c6f3bce5ead7e98e4ee2; From 63c882a05416e18de6fb59f7dd6da48f3bbe8273 · fixed in 947400af98b9e63841929d079a2c3ea0a8ba227b; From 63c882a05416e18de6fb59f7dd6da48f3bbe8273 · fixed in ac8d8b599d466a129122bded77db3d0f8b96b461; From 63c882a05416e18de6fb59f7dd6da48f3bbe8273 · fixed in e422777fdd4746de1109575c51e65038d4c5c1be

  • Linux Linux

    2.6.31

  • KernelLinux

    From 2.6.31 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.4

References 8

git.kernel.org