From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74627: net: devmem: prevent net-iov / page mixing
Date: Sat, 22 Aug 2026 17:31:51 +0200 [thread overview]
Message-ID: <2026082220-CVE-2026-74627-6aa8@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: devmem: prevent net-iov / page mixing
We should either have net_iov or page backed frags in a single skb,
otherwise it blows up down the stack. Don't allow mixing in
zerocopy_fill_skb_from_devmem().
The Linux kernel CVE team has assigned CVE-2026-74627 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit bd61848900bff597764238f3a8ec67c815cd316e and fixed in 6.18.45 with commit e9bfe12b1d04c34c6fedcba21d9709b65c08aa33
Issue introduced in 6.16 with commit bd61848900bff597764238f3a8ec67c815cd316e and fixed in 7.1.9 with commit ed08011ae0be88f16cceae190535d6c790c83b0c
Issue introduced in 6.16 with commit bd61848900bff597764238f3a8ec67c815cd316e and fixed in 7.2 with commit 53a43508ee332d8bffe40590c3d189c92a551f9f
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-74627
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:
net/core/datagram.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/e9bfe12b1d04c34c6fedcba21d9709b65c08aa33
https://git.kernel.org/stable/c/ed08011ae0be88f16cceae190535d6c790c83b0c
https://git.kernel.org/stable/c/53a43508ee332d8bffe40590c3d189c92a551f9f
reply other threads:[~2026-08-22 15:35 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=2026082220-CVE-2026-74627-6aa8@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.