Bug 2576898 (CVE-2026-99417) - CVE-2026-99417 kernel: kernel: Information disclosure in OverlayFS via race condition during hard link creation
Summary: CVE-2026-99417 kernel: kernel: Information disclosure in OverlayFS via race c...
Keywords:
Status: NEW
Alias: CVE-2026-99417
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-19 15:39 UTC by OSIDB Bzimport
Modified: 2026-11-19 19:40 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-19 15:39:07 UTC
In the Linux kernel, the following vulnerability has been resolved:

ovl: fix a torn path in ovl_get_redirect()

A hard link of a metacopy file that races with a rename of an ancestor
stores a redirect to the wrong lower file.

Each component of an absolute redirect must be the name that a dentry
has in the parent that the walk continues with. ovl_get_redirect()
copies the name under d_lock and calls dget_parent() after the unlock,
and the callers for a hard link hold no lock that stops a rename across
directories. A rename between the two steps combines the old name with
the new parent.

With delays in ovl_get_redirect(), an unprivileged user hard-linked a
metacopy file while renaming its ancestor to another directory, the
stored redirect named another lower path, and after a remount the file
showed the data of a root-only file.

Fix this by taking the parent first and checking it again under d_lock.


Note You need to log in before you can comment on or make changes to this bug.