PT-2026-61376 · Linux · Linux
CVE-2026-64059
·
Published
2026-07-19
·
Updated
2026-07-19
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
netfs: Fix folio->private handling in netfs perform write()
Under some circumstances, netfs perform write() doesn't correctly
manipulate folio->private between NULL, NETFS FOLIO COPY TO CACHE, pointing
to a group and pointing to a netfs folio struct, leading to potential
multiple attachments of private data with associated folio ref leaks and
also leaks of netfs folio structs or netfs group refs.
Fix this by consolidating the place at which a folio is marked uptodate in
one place and having that look at what's attached to folio->private and
decide how to clean it up and then set the new group. Also, the content
shouldn't be flushed if group is NULL, even if a group is specified in the
netfs group parameter, as that would be the case for a new folio. A
filesystem should always specify netfs group or never specify netfs group.
The Sashiko auto-review tool noted that it was theoretically possible that
the fpos >= ctx->zero point section might leak if it modified a streaming
write folio. This is unlikely, but with a network filesystem, third party
changes can happen. It also pointed out that netfs set group() would
leak if called multiple times on the same folio from the "whole folio
modify section".
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux