From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72363: netfs: Fix folio state after ENOMEM whilst under writeback iteration
Date: Sat, 15 Aug 2026 15:07:22 +0900 [thread overview]
Message-ID: <2026081514-CVE-2026-72363-5e8b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
netfs: Fix folio state after ENOMEM whilst under writeback iteration
Fix the state of the current folio when ENOMEM occurs during writeback
iteration. The folio needs to be redirtied and unlocked before the
terminal writeback_iter() is invoked.
The Linux kernel CVE team has assigned CVE-2026-72363 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit 06fa229ceb36898e68022b5654c017d2c6582d7d and fixed in 6.18.40 with commit a9b89752c2726e88ea67994fb97a0316b24d30b7
Issue introduced in 6.14 with commit 06fa229ceb36898e68022b5654c017d2c6582d7d and fixed in 7.1.5 with commit 1a4421c7a5611db554328f721a4f7642440b44bd
Issue introduced in 6.14 with commit 06fa229ceb36898e68022b5654c017d2c6582d7d and fixed in 7.2-rc2 with commit b6a713fd34b9498ee2164d5d3e8460732a392efc
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-72363
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/write_issue.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/a9b89752c2726e88ea67994fb97a0316b24d30b7
https://git.kernel.org/stable/c/1a4421c7a5611db554328f721a4f7642440b44bd
https://git.kernel.org/stable/c/b6a713fd34b9498ee2164d5d3e8460732a392efc
reply other threads:[~2026-08-15 6:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081514-CVE-2026-72363-5e8b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.