diff options
| author | Aldo Ariel Panzardo <qwe.aldo@gmail.com> | 2026-09-23 08:58:22 -0300 |
|---|---|---|
| committer | Carlos Maiolino <cem@kernel.org> | 2026-10-08 19:25:49 +0200 |
| commit | 0643549ffecaeb716c0b75590a9b76dfa5eb35b3 (patch) | |
| tree | 2d260b434d5c4f818f07cadacc6dfe3bf2d72ffb /tools/lib/python | |
| parent | 3df5e5aaa3bc0913236c48ab29b7df3a785aa29f (diff) | |
| download | linux-next-0643549ffecaeb716c0b75590a9b76dfa5eb35b3.tar.gz linux-next-0643549ffecaeb716c0b75590a9b76dfa5eb35b3.zip | |
xfs: reject out-of-range attribute value lengths in xfs_attr_copy_value
xfs_attr_copy_value() takes the value length as a signed int and, for a
remote xattr, is handed args->rmtvaluelen. That field is filled from the
on-disk __be32 xfs_attr_leaf_name_remote.valuelen in
xfs_attr3_leaf_getvalue(), so a crafted length such as 0x80000000 is
stored into the signed rmtvaluelen as a negative number.
The "buffer too small" guard in xfs_attr_copy_value() is a signed
comparison:
if (args->valuelen < valuelen)
return -ERANGE;
A negative valuelen therefore compares as smaller than the caller's
buffer size, skips the -ERANGE path, and is then used as a copy length,
leading to an out-of-bounds copy of a full remote block into a small
getxattr(2) buffer on a mounted crafted image.
Reject a value length that is negative or larger than the maximum xattr
size before it is used, so a bogus on-disk length can no longer slip
through the value copier.
Fixes: 9df243a1a9e6 ("xfs: consolidate attribute value copying")
Cc: stable@vger.kernel.org
Signed-off-by: Aldo Ariel Panzardo <qwe.aldo@gmail.com>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
