From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72033: orangefs: keep the readdir entry size 64-bit in fill_from_part()
Date: Sat, 15 Aug 2026 15:01:52 +0900 [thread overview]
Message-ID: <2026081512-CVE-2026-72033-9998@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
orangefs: keep the readdir entry size 64-bit in fill_from_part()
fill_from_part() computes the size of a directory entry in size_t but
stores it in a __u32. An entry length near U32_MAX wraps it to a small
value, bypasses the bounds check, and is then used to index the entry,
reading far past the directory part -- an out-of-bounds read that oopses
the kernel.
Compute the size as a u64 so it cannot truncate; the bounds check then
rejects the entry. The trailer is supplied by the userspace client.
The Linux kernel CVE team has assigned CVE-2026-72033 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.12 with commit 480e3e532e31666a18520a7964bb4095d7a16b9a and fixed in 5.10.261 with commit 1679780f482feeb82acb5995587d4fb1d1fe82fd
Issue introduced in 4.12 with commit 480e3e532e31666a18520a7964bb4095d7a16b9a and fixed in 5.15.212 with commit a72bbb43689591c9d36e3bb45c2d4e688cf92682
Issue introduced in 4.12 with commit 480e3e532e31666a18520a7964bb4095d7a16b9a and fixed in 6.1.178 with commit 36723b28e3293047f087f4501f1ef4ead418dd84
Issue introduced in 4.12 with commit 480e3e532e31666a18520a7964bb4095d7a16b9a and fixed in 6.6.145 with commit 07c05601a9a8e5d4481b2a4a16dc0e3c5bc63ad9
Issue introduced in 4.12 with commit 480e3e532e31666a18520a7964bb4095d7a16b9a and fixed in 6.12.97 with commit fdf06a1b66ff39664b01c6bb6a2aa98d81e8ebe1
Issue introduced in 4.12 with commit 480e3e532e31666a18520a7964bb4095d7a16b9a and fixed in 6.18.40 with commit 82fc886e244c76fadf05ef1958aaf8815478ccde
Issue introduced in 4.12 with commit 480e3e532e31666a18520a7964bb4095d7a16b9a and fixed in 7.1.5 with commit e3d325c0bdb7bc5d1b4cc8d8441d79794cd03729
Issue introduced in 4.12 with commit 480e3e532e31666a18520a7964bb4095d7a16b9a and fixed in 7.2-rc2 with commit 18227a6bc98bd0ba96ed3ce9d5b28776a5a28dfc
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-72033
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/dir.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/1679780f482feeb82acb5995587d4fb1d1fe82fd
https://git.kernel.org/stable/c/a72bbb43689591c9d36e3bb45c2d4e688cf92682
https://git.kernel.org/stable/c/36723b28e3293047f087f4501f1ef4ead418dd84
https://git.kernel.org/stable/c/07c05601a9a8e5d4481b2a4a16dc0e3c5bc63ad9
https://git.kernel.org/stable/c/fdf06a1b66ff39664b01c6bb6a2aa98d81e8ebe1
https://git.kernel.org/stable/c/82fc886e244c76fadf05ef1958aaf8815478ccde
https://git.kernel.org/stable/c/e3d325c0bdb7bc5d1b4cc8d8441d79794cd03729
https://git.kernel.org/stable/c/18227a6bc98bd0ba96ed3ce9d5b28776a5a28dfc
reply other threads:[~2026-08-15 6:08 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=2026081512-CVE-2026-72033-9998@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.