Answer in brief
CVE-2026-52990 records a Unknown severity vulnerability in fsnotify: fix inode reference leak in fsnotify_recalc_mask(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c3638b5b13740fa31762d414bbce8b7a694e582a <926ec3937b28d30c08427053c8d8af7f9e086d82 || >=c3638b5b13740fa31762d414bbce8b7a694e582a <8c8afa6444e6bdc145d2bf2f3aeeca6da3e36b42 || >=c3638b5b13740fa31762d414bbce8b7a694e582a <b740cc86816bbc87902ae9db74cd21abde3c8d63 || >=c3638b5b13740fa31762d414bbce8b7a694e582a <5c80289503da3658e3df80280598c68d181eadbd || >=c3638b5b13740fa31762d414bbce8b7a694e582a <4aca914ac152f5d055ddcb36704d1e539ac08977 || ff34ebaa6f6dc1eebce6a8d6f12a1566f33d00fe || 4f145b67c075324b13d6ae7d5abb6e7a1dbac26d || >=5.10.220 <5.11 || >=5.15.154 <5.16 | 926ec3937b28d30c08427053c8d8af7f9e086d82, 8c8afa6444e6bdc145d2bf2f3aeeca6da3e36b42, b740cc86816bbc87902ae9db74cd21abde3c8d63, 5c80289503da3658e3df80280598c68d181eadbd, 4aca914ac152f5d055ddcb36704d1e539ac08977, 5.11, 5.16 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: fsnotify: fix inode reference leak in fsnotify_recalc_mask() fsnotify_recalc_mask() fails to handle the return value of __fsnotify_recalc_mask(), which may return an inode pointer that needs to be released via fsnotify_drop_object() when the connector's HAS_IREF flag transitions from set to cleared. This manifests as a hung task with the following call trace: INFO: task umount:1234 blocked for more than 120 seconds. Call Trace: __schedule schedule fsnotify_sb_delete generic_shutdown_super kill_anon_super cleanup_mnt task_work_run do_exit do_group_exit The race window that triggers the iref leak: Thread A (adding mark) Thread B (removing mark) ────────────────────── ──────────────────────── fsnotify_add_mark_locked(): fsnotify_add_mark_list(): spin_lock(conn->lock) add mark_B(evictable) to list spin_unlock(conn->lock) return /* ---- gap: no lock held ---- */ fsnotify_detach_mark(mark_A): spin_lock(mark_A->lock) clear ATTACHED flag on mark_A spin_unlock(mark_A->lock) fsnotify_put_mark(mark_A) fsnotify_recalc_mask(): spin_lock(conn->lock) __fsnotify_recalc_mask(): /* mark_A skipped: ATTACHED cleared */ /* only mark_B(evictable) remains */ want_iref = false has_iref = true /* not yet cleared */ -> HAS_IREF transitions true -> false -> returns inode pointer spin_unlock(conn->lock) /* BUG: return value discarded! * iput() and fsnotify_put_sb_watched_objects() * are never called */ Fix this by deferring the transition true -> false of HAS_IREF flag from fsnotify_recalc_mask() (Thread A) to fsnotify_put_mark() (thread B).
Quoted source text, attributed separately from HOL analysis.