From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21782: orangefs: fix a oob in orangefs_debug_write
Date: Wed, 26 Feb 2025 18:17:38 -0800 [thread overview]
Message-ID: <2025022608-CVE-2025-21782-9d97@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
orangefs: fix a oob in orangefs_debug_write
I got a syzbot report: slab-out-of-bounds Read in
orangefs_debug_write... several people suggested fixes,
I tested Al Viro's suggestion and made this patch.
The Linux kernel CVE team has assigned CVE-2025-21782 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.129 with commit 1da2697307dad281dd690a19441b5ca4af92d786
Fixed in 6.6.79 with commit 2b84a231910cef2e0a16d29294afabfb69112087
Fixed in 6.12.16 with commit 897f496b946fdcfab5983c983e4b513ab6682364
Fixed in 6.13.4 with commit 1c5244299241cf49d8ae7b5054e299cc8faa4e09
Fixed in 6.14-rc1 with commit f7c848431632598ff9bce57a659db6af60d75b39
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-21782
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/orangefs/orangefs-debugfs.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/1da2697307dad281dd690a19441b5ca4af92d786
https://git.kernel.org/stable/c/2b84a231910cef2e0a16d29294afabfb69112087
https://git.kernel.org/stable/c/897f496b946fdcfab5983c983e4b513ab6682364
https://git.kernel.org/stable/c/1c5244299241cf49d8ae7b5054e299cc8faa4e09
https://git.kernel.org/stable/c/f7c848431632598ff9bce57a659db6af60d75b39
reply other threads:[~2025-02-27 2:19 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=2025022608-CVE-2025-21782-9d97@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.