CVE-2026-99637: ovl: inherit FMODE_NONOTIFY when opening directory realfiles

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ovl: inherit FMODENONOTIFY when opening directory realfiles

When fanotify hands a listener an fd for a permission event on an overlay directory, ovldiropenrealfile() opens the real directory via dentryopen(), not backingfileopen(), so the lower open could still raise FSOPENPERM and deadlock a listener that also marks the backing filesystem.

Export dentryopennonotify() and call it from ovlpathopenrealfile() when the overlay user file must not generate events. Ordinary ovlpathopen() callers are unchanged.

Affected Software

1 affected componentFixes available
linux/kernel>=5.8.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  2. Compensating control

    Export dentry_open_nonotify() and use it to open overlay directory realfiles instead of dentry_open(), so FMODE_NONOTIFY is inherited and the lower open does not raise FS_OPEN_PERM.

Frequently Asked Questions

1

Which systems are realistically exposed to this deadlock?

Systems using OverlayFS directories with fanotify permission-event listeners are exposed when a listener also marks the backing filesystem. The problematic path occurs when fanotify hands the listener a file descriptor for a permission event on an overlay directory.

2

What conditions are required to trigger the issue?

An attacker or triggering workload needs to cause an OverlayFS directory permission event that results in fanotify providing an fd to a listener. The listener must also monitor the backing filesystem, allowing the lower-directory open to generate another FS_OPEN_PERM event and deadlock.

3

Are ordinary OverlayFS file-open operations affected?

The change applies to opening directory realfiles when the overlay user file must not generate events. Ordinary ovl_path_open() callers are explicitly unchanged.

4

What is the relevant remediation?

Apply a kernel version containing the change that exports dentry_open_nonotify() and uses it from ovl_path_open_realfile() for this non-notifying open path. The provided references identify stable kernel commits containing the fix.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203