CVE-2026-99175

fsnotify: prevent mark additions during connector teardown

Description

In the Linux kernel, the following vulnerability has been resolved: fsnotify: prevent mark additions during connector teardown fsnotify_destroy_marks() keeps a reference to its current mark while it drops conn->lock to destroy the mark. This stabilizes the forward-walk cursor, but does not prevent a new mark from being inserted before it. For example, an inotify watch re-added after IN_IGNORED sorts before the old, detached mark for the same group. The walk can miss the replacement and then detach the entire connector from the object. The replacement is still on its group's marks_list and, for inotify, in the watch IDR. The group mutex no longer protects the connector's object from disappearing. An unprivileged fdinfo read racing the final detach can consequently call igrab(NULL): BUG: KASAN: null-ptr-deref in igrab+0x24/0x100 Write of size 4 at addr 0000000000000148 Call Trace: igrab+0x24/0x100 inotify_show_fdinfo+0x1dc/0x5e0 seq_show+0x397/0x690 Set a DESTROYING flag under conn->lock before starting the walk, and reject new marks on that connector with -ENOENT. The existing add-mark error paths undo the temporary group-list entry and the backend's watch allocation. Do not wait for teardown while holding the group mutex, which the destroyer needs. Once the old connector is detached, an add can install a fresh connector as before. This closes the insertion race for all object types using the common connector teardown, without changing the mark reference or SRCU lifetime rules.

Key facts

Published
28 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.177% likely to be exploited in the next 30 days, higher than 7.364% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 6b3f05d24d355f50f3d9814304650fcab0efb482 up to but excluding f7def717c06aea7004905e4d1568c3691ef9825d (affected)
  • 6b3f05d24d355f50f3d9814304650fcab0efb482 up to but excluding da2f9aa89ef1b1fe7a7c6e1a8ddacd9c975e86aa (affected)
  • 6b3f05d24d355f50f3d9814304650fcab0efb482 up to but excluding 587d80966dcce2824f13fd32dab83bf882acf66f (affected)
  • 6b3f05d24d355f50f3d9814304650fcab0efb482 up to but excluding d28a460a2237220d9ccbdd3baac6eaead44e96cb (affected)
  • 6b3f05d24d355f50f3d9814304650fcab0efb482 up to but excluding 61133f15773b907bada651a02d9c6d38eae37c48 (affected)
  • 6b3f05d24d355f50f3d9814304650fcab0efb482 up to but excluding 952501bfc6e5e654ac4a17ec9d90c1ec614bd9f1 (affected)
  • 6b3f05d24d355f50f3d9814304650fcab0efb482 up to but excluding 472589eacdf10b5f9bd10b333957ed5291b2544b (affected)
  • 6b3f05d24d355f50f3d9814304650fcab0efb482 up to but excluding 36ebddca56b9d8993d6dc984fdecc748ee1f5e06 (affected)
LinuxLinux
  • Default status: affected
  • 4.12 (affected)
  • 0 up to but excluding 4.12 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References