fuse: Initialize beyond-EOF page contents before setting uptodate
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a1d75f258230b75d46aecdf28b2e732413028863 · < ac42e0f0eb66af966015ee33fd355bc6f5d80cd6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fuse: Initialize beyond-EOF page contents before setting uptodate
fuse_notify_store(), unlike fuse_do_readpage(), does not enable page zeroing (because it can be used to change partial page contents).
So fuse_notify_store() must be more careful to fully initialize page contents (including parts of the page that are beyond end-of-file) before marking the page uptodate.
The current code can leave beyond-EOF page contents uninitialized, which makes these uninitialized page contents visible to userspace via mmap().
This is an information leak, but only affects systems which do not enable init-on-alloc (via CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y or the corresponding kernel command line parameter).
From the CVE record · Linux
The Linux kernel's FUSE notification path can mark a page uptodate without initializing its contents beyond end-of-file. On systems without init-on-alloc enabled, those uninitialized contents can become visible to userspace through mmap(). The input does not specify authentication requirements or user interaction.
Engineers running Linux kernels without init-on-alloc enabled should check their systems; affected versions are not specified.