CVE-2026-89595

CVE CVE-2026-89595EUVD EUVD-2026-76507Veröffentlicht 2026-09-11T19:44:58.000ZZuletzt geändert 2026-09-14T12:01:18.000Z

Was das Advisory beschreibt

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.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux 63c882a05416e18de6fb59f7dd6da48f3bbe8273 <947400af98b9e63841929d079a2c3ea0a8ba227b; patch: 6.1.188; 2.6.31; 63c882a05416e18de6fb59f7dd6da48f3bbe8273 <ac8d8b599d466a129122bded77db3d0f8b96b461; patch: 6.18.51; 63c882a05416e18de6fb59f7dd6da48f3bbe8273 <e422777fdd4746de1109575c51e65038d4c5c1be; patch: 0; 63c882a05416e18de6fb59f7dd6da48f3bbe8273 <de75382d6e354b2b055df4896d12a91969f12090; 63c882a05416e18de6fb59f7dd6da48f3bbe8273 <2f09f08d602647fc4e328fc27ecb4c3008d10338; patch: 7.2.4; 63c882a05416e18de6fb59f7dd6da48f3bbe8273 <92289e66639f62abc754c6f3bce5ead7e98e4ee2; patch: 7.3-rc1; patch: 6.12.110; 63c882a05416e18de6fb59f7dd6da48f3bbe8273 <27d172b60eeca5c8fd51b246f9fb959067cf102b; patch: 6.6.157; patch: 5.10.270; 63c882a05416e18de6fb59f7dd6da48f3bbe8273 <343ae18e960f6c5f1d34d58a69750c62cd463228; patch: 5.15.221

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.