fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a · < 56763afa013444a9d84ca1b74e4b7130942177ba| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios
FUSE_NOTIFY_RETRIEVE must be limited to uptodate folios; !uptodate folios can contain uninitialized data. Since FUSE_NOTIFY_RETRIEVE is intended to only return data that is already in the page cache and not wait for data from the FUSE daemon, treat !uptodate folios as if they weren't present.
This only has security impact on systems that don't enable automatic zero-initialization of all page allocations via CONFIG_INIT_ON_ALLOC_DEFAULT_ON or init_on_alloc=1.
From the CVE record · Linux
The Linux kernel’s FUSE_NOTIFY_RETRIEVE can return page-cache folios that are not up to date and may contain uninitialized data. This has security impact only on systems without automatic zero-initialization of all page allocations enabled via CONFIG_INIT_ON_ALLOC_DEFAULT_ON or init_on_alloc=1. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with FUSE should check affected versions, which are not specified in the input.