From: Christian Brauner <brauner@kernel.org>
To: Wang Haoran <haoranwangsec@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
akpm@linux-foundation.org
Subject: Re: [PATCH] iov_iter: use kmemdup_array for dup_iter to harden against overflow
Date: Tue, 14 Apr 2026 11:46:43 +0200 [thread overview]
Message-ID: <20260414-lockruf-frequentieren-a87539acb6ec@brauner> (raw)
In-Reply-To: <20260413060655.1139141-1-haoranwangsec@gmail.com>
On Mon, 13 Apr 2026 14:06:55 +0800, Wang Haoran wrote:
> While auditing the Linux 7.0-rc2 kernel, I identified a potential security
> vulnerability in the iov_iter framework's memory allocation logic.
>
> The dup_iter() function, which is exported via EXPORT_SYMBOL, currently
> uses kmemdup() with a raw multiplication to allocate the duplicate iovec array:
>
> new->iov = kmemdup(from->iov, nr_segs * sizeof(struct iovec), gfp);
>
> [...]
Applied to the vfs-7.2.misc branch of the vfs/vfs.git tree.
Patches in the vfs-7.2.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-7.2.misc
[1/1] iov_iter: use kmemdup_array for dup_iter to harden against overflow
https://git.kernel.org/vfs/vfs/c/ea5efcc5c589
prev parent reply other threads:[~2026-04-14 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 6:06 [PATCH] iov_iter: use kmemdup_array for dup_iter to harden against overflow Wang Haoran
2026-04-14 8:18 ` Christoph Hellwig
2026-04-14 9:46 ` Christian Brauner [this message]
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=20260414-lockruf-frequentieren-a87539acb6ec@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=haoranwangsec@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox