From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21741: usbnet: ipheth: fix DPE OoB read
Date: Wed, 26 Feb 2025 18:11:23 -0800 [thread overview]
Message-ID: <2025022600-CVE-2025-21741-cbfd@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usbnet: ipheth: fix DPE OoB read
Fix an out-of-bounds DPE read, limit the number of processed DPEs to
the amount that fits into the fixed-size NDP16 header.
The Linux kernel CVE team has assigned CVE-2025-21741 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.5 with commit a2d274c62e44b1995c170595db3865c6fe701226 and fixed in 6.6.78 with commit 22475242ddb70e35c9148234be9a3aa9fb8efff9
Issue introduced in 6.5 with commit a2d274c62e44b1995c170595db3865c6fe701226 and fixed in 6.12.14 with commit 5835bf66c50ac2b85ed28b282c2456c3516ef0a6
Issue introduced in 6.5 with commit a2d274c62e44b1995c170595db3865c6fe701226 and fixed in 6.13.3 with commit 971b8c572559e52d32a2b82f2d9e0685439a0117
Issue introduced in 6.5 with commit a2d274c62e44b1995c170595db3865c6fe701226 and fixed in 6.14-rc1 with commit ee591f2b281721171896117f9946fced31441418
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-2025-21741
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:
drivers/net/usb/ipheth.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/22475242ddb70e35c9148234be9a3aa9fb8efff9
https://git.kernel.org/stable/c/5835bf66c50ac2b85ed28b282c2456c3516ef0a6
https://git.kernel.org/stable/c/971b8c572559e52d32a2b82f2d9e0685439a0117
https://git.kernel.org/stable/c/ee591f2b281721171896117f9946fced31441418
reply other threads:[~2025-02-27 2:13 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=2025022600-CVE-2025-21741-cbfd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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.