Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99175fsnotify: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 6b3f05d24d355f50f3d9814304650fcab0efb482 – < f7def717c06aea7004905e4d1568c3691ef9825d
    • affected 6b3f05d24d355f50f3d9814304650fcab0efb482 – < da2f9aa89ef1b1fe7a7c6e1a8ddacd9c975e86aa
    • affected 6b3f05d24d355f50f3d9814304650fcab0efb482 – < 587d80966dcce2824f13fd32dab83bf882acf66f
    • affected 6b3f05d24d355f50f3d9814304650fcab0efb482 – < d28a460a2237220d9ccbdd3baac6eaead44e96cb
    • affected 6b3f05d24d355f50f3d9814304650fcab0efb482 – < 61133f15773b907bada651a02d9c6d38eae37c48
    • affected 6b3f05d24d355f50f3d9814304650fcab0efb482 – < 952501bfc6e5e654ac4a17ec9d90c1ec614bd9f1
    • affected 6b3f05d24d355f50f3d9814304650fcab0efb482 – < 472589eacdf10b5f9bd10b333957ed5291b2544b
    • affected 6b3f05d24d355f50f3d9814304650fcab0efb482 – < 36ebddca56b9d8993d6dc984fdecc748ee1f5e06
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99175 badge
[![CVE-2026-99175](https://cveledger.app/badge/CVE-2026-99175.svg)](https://cveledger.app/cve/CVE-2026-99175)

Record last updated .