nday
CVE-2026-52990

fsnotify: fix inode reference leak in fsnotify_recalc_mask()

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
06-24T16:29Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 11171,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-52990",
  "occurred_at": "2026-06-24T16:29:04.148Z",
  "observed_at": "2026-11-12T14:10:31.286634Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2026-11-06T16:15:48.666965Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-06-24T16:29:04.148Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.