fuse: reject fuse_notify() pagecache ops on directories
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5d7bc7e8680c7ca4c8a4f139ce2a54ccb8131ef0 · < 12df4cfa738aefff21756728e91056d7defb0fe6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fuse: reject fuse_notify() pagecache ops on directories
The operations FUSE_NOTIFY_STORE and FUSE_NOTIFY_RETRIEVE allow the FUSE daemon to actively write/read pagecache contents.
For directories with FOPEN_CACHE_DIR, the pagecache is used as kernel-internal cache storage, and userspace is not supposed to have direct access to this cache - in particular, fuse_parse_cache() will hit WARN_ON() if the cache contains bogus data.
Reject FUSE_NOTIFY_STORE and FUSE_NOTIFY_RETRIEVE on anything other than regular files with -EINVAL.
From the CVE record · Linux
The Linux kernel allowed a FUSE daemon to read or write pagecache contents for directories using FOPEN_CACHE_DIR, even though that cache is reserved for internal use. A daemon able to place bogus data in the cache could trigger a kernel warning when fuse_parse_cache() processes it. This requires control of the FUSE daemon; no separate user interaction is described.
Engineers running Linux kernels with FUSE should check their kernel vendor’s advisory to determine which versions are affected.