fs/fhandle.c: fix a race in call of has_locked_children()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.466.15.36.16In the Linux kernel, the following vulnerability has been resolved:
fs/fhandle.c: fix a race in call of has_locked_children()
may_decode_fh() is calling has_locked_children() while holding no locks. That's an oopsable race...
The rest of the callers are safe since they are holding namespace_sem and are guaranteed a positive refcount on the mount in question.
Rename the current has_locked_children() to __has_locked_children(), make it static and switch the fs/namespace.c users to it.
Make has_locked_children() a wrapper for __has_locked_children(), calling the latter under read_seqlock_excl(&mount_lock).
From the CVE record · Linux
The Linux kernel's may_decode_fh() can call has_locked_children() without holding a lock, creating a race that can cause a kernel oops. The input does not specify how an attacker could trigger the race or whether access or user interaction is required.
Engineers running Linux kernels should check whether their kernel includes the fs/fhandle.c fix; affected versions were not specified.