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.
Published: 2026-10-28
Score: n/a
EPSS: n/a
KEV: No
Impact: Denial of Service via kernel crash
Action: Patch Kernel
AI Analysis

Impact

A race condition in the Linux kernel fsnotify subsystem allows a new mark to be inserted while a connector is being torn down, causing the kernel to dereference a null pointer during a final detach operation. When an unprivileged process performs an fdinfo read concurrently with the detachment, the call to igrab(NULL) triggers a KASAN null‑pointer dereference and can lead to a kernel panic. The bug is a classic example of a synchronization flaw resulting in a use‑after‑free or null‑pointer dereference and manifests as a denial‑of‑service when the system experiences a crash or restart.

Affected Systems

The vulnerability affects all versions of the Linux kernel that lack the fsnotify DESTROYING flag patch. No specific release revisions are listed, so any kernel prior to the inclusion of the referenced commit sequence is potentially exposed. The flaw resides in the core kernel and therefore applies to all distributions that ship an unpatched kernel.

Risk and Exploitability

Because the EPSS score is not available and the vulnerability is not listed in CISA KEV, the exact likelihood of exploitation is uncertain, but the potential impact is high: a crash of the kernel causes service interruption and may allow an attacker to force a reboot. The race condition can be triggered by any user interacting with inotify watches, so unprivileged users can potentially induce the fault. The lack of a public exploit does not diminish the risk, as the vulnerability requires only normal operation of the inotify subsystem, which is commonly used by many applications.

Generated by OpenCVE AI on October 28, 2026 at 11:57 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch that implements the DESTROYING flag for fsnotify as referenced in the listed commit logs and rebuild or update your kernel image.
  • If a kernel upgrade cannot be performed immediately, consider disabling inotify or removing its usage from critical services to reduce the chance of a race during teardown.
  • After the patch has been applied or the kernel has been updated, monitor system logs for KASAN null‑ptr‑deref messages or kernel panic events and confirm that the fault no longer occurs.

Generated by OpenCVE AI on October 28, 2026 at 11:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 28 Oct 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-476
CWE-758

Wed, 28 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
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.
Title fsnotify: prevent mark additions during connector teardown
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-28T10:35:29.760Z

Reserved: 2026-09-25T10:25:14.399Z

Link: CVE-2026-99175

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-28T11:17:38.150

Modified: 2026-10-28T11:17:38.150

Link: CVE-2026-99175

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-28T12:00:22Z

Weaknesses
  • CWE-416

    Use After Free

  • CWE-476

    NULL Pointer Dereference

  • CWE-758

    Reliance on Undefined, Unspecified, or Implementation-Defined Behavior