CVE-2026-64060: netfs: Fix leak of request in netfs_write_begin() error handling
Greg Kroah-Hartman <[email protected]>
| Newsgroups | org.kernel.vger.linux-cve-announce |
|---|---|
| Message-ID | <2026071910-CVE-2026-64060-4633@gregkh> |
From: Greg Kroah-Hartman <[email protected]> Description =========== In the Linux kernel, the following vulnerability has been resolved: netfs: Fix leak of request in netfs_write_begin() error handling Fix netfs_write_begin() to not leak our ref on the request in the event that we get an error from netfs_wait_for_read(). The Linux kernel CVE team has assigned CVE-2026-64060 to this issue. Affected and fixed versions =========================== Issue introduced in 5.18 with commit 4090b31422a6f24dfe701e31ffec7ba5804a7e2f and fixed in 6.18.34 with commit 22ae28aae43623be235ff455558cdd13fbe2daeb Issue introduced in 5.18 with commit 4090b31422a6f24dfe701e31ffec7ba5804a7e2f and fixed in 7.0.11 with commit 28686d6d8b60dc5bbae9ef6023ab2051d6c66cdf Issue introduced in 5.18 with commit 4090b31422a6f24dfe701e31ffec7ba5804a7e2f and fixed in 7.1 with commit 5046a34f0643441f05b0253ea64e1a3af87efe14 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-64060 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: fs/netfs/buffered_read.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/22ae28aae43623be235ff455558cdd13fbe2daeb https://git.kernel.org/stable/c/28686d6d8b60dc5bbae9ef6023ab2051d6c66cdf https://git.kernel.org/stable/c/5046a34f0643441f05b0253ea64e1a3af87efe14