fanotify: Validate the return value of mnt_ns_from_dentry() before dereferencing
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fanotify: Validate the return value of mnt_ns_from_dentry() before dereferencing
The function do_fanotify_mark() does not validate if mnt_ns_from_dentry() returns NULL before dereferencing mntns->user_ns. This causes a NULL pointer dereference in do_fanotify_mark() if the path is not a mount namespace object.
Fix this by checking mnt_ns_from_dentry()'s return value before dereferencing it.
Before the patch
$ gcc fanotify_nullptr.c -o fanotify_nullptr $ mkdir A $ ./fanotify_nullptr Fanotify fd: 3 fanotify_mark: Operation not permitted $ unshare -Urm Fanotify fd: 3 Killed
int main(void){ int ffd; ffd = fanotify_init(FAN_CLASS_NOTIF | FAN_REPORT_MNT, 0); if(ffd < 0){ perror("fanotify_init"); exit(EXIT_FAILURE); }
printf("Fanotify fd: %d\n",ffd);
From the CVE record · Linux
The Linux kernel’s fanotify mark handler can dereference a NULL pointer when a path is not a mount namespace object. A local user can trigger a kernel crash by making a fanotify mark request under the conditions shown in the report, which include entering a user and mount namespace.
Engineers running Linux kernels with the affected fanotify code should check their systems; affected versions are not specified.