fs/notify: call exportfs_encode_fid with s_umount
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fs/notify: call exportfs_encode_fid with s_umount
Calling intotify_show_fdinfo() on fd watching an overlayfs inode, while the overlayfs is being unmounted, can lead to dereferencing NULL ptr.
This issue was found by syzkaller.
Race Condition Diagram:
Thread 1 Thread 2 -------- --------
generic_shutdown_super() shrink_dcache_for_umount sb->s_root = NULL
| | vfs_read() | inotify_fdinfo() | * inode get from mark * | show_mark_fhandle(m, inode) | exportfs_encode_fid(inode, ..) | ovl_encode_fh(inode, ..) | ovl_check_encode_origin(inode) | * deref i_sb->s_root * | | v fsnotify_sb_delete(sb)
From the CVE record · Linux
A race in the Linux kernel's fs/notify code can cause a null-pointer dereference when an inotify file descriptor watching an overlayfs inode is read while the overlayfs is being unmounted. A local process reading the descriptor's fdinfo during that race can trigger a kernel crash; no remote access or user interaction is described.
Engineers running Linux kernels that use inotify with overlayfs should check their kernel version; affected versions are not specified.