From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Qasim Ijaz <qasdev00@gmail.com>,
zhaomengmeng@kylinos.cn, llfamsec@gmail.com,
gregkh@linuxfoundation.org, ancowi69@gmail.com
Cc: jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
syzbot <syzbot+4e6e7e4279d046613bc5@syzkaller.appspotmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] jfs: fix slab-out-of-bounds read in ea_get()
Date: Wed, 19 Feb 2025 16:23:28 -0600 [thread overview]
Message-ID: <6df15794-4acb-4c24-adc8-a273f0fe1b51@oracle.com> (raw)
In-Reply-To: <20250213210553.28613-1-qasdev00@gmail.com>
On 2/13/25 3:05PM, Qasim Ijaz wrote:
> During the "size_check" label in ea_get(), the code checks if the extended
> attribute list (xattr) size matches ea_size. If not, it logs
> "ea_get: invalid extended attribute" and calls print_hex_dump().
>
> Here, EALIST_SIZE(ea_buf->xattr) returns 4110417968, which exceeds
> INT_MAX (2,147,483,647). Then ea_size is clamped:
>
> int size = clamp_t(int, ea_size, 0, EALIST_SIZE(ea_buf->xattr));
>
> Although clamp_t aims to bound ea_size between 0 and 4110417968, the upper
> limit is treated as an int, causing an overflow above 2^31 - 1. This leads
> "size" to wrap around and become negative (-184549328).
>
> The "size" is then passed to print_hex_dump() (called "len" in
> print_hex_dump()), it is passed as type size_t (an unsigned
> type), this is then stored inside a variable called
> "int remaining", which is then assigned to "int linelen" which
> is then passed to hex_dump_to_buffer(). In print_hex_dump()
> the for loop, iterates through 0 to len-1, where len is
> 18446744073525002176, calling hex_dump_to_buffer()
> on each iteration:
>
> for (i = 0; i < len; i += rowsize) {
> linelen = min(remaining, rowsize);
> remaining -= rowsize;
>
> hex_dump_to_buffer(ptr + i, linelen, rowsize, groupsize,
> linebuf, sizeof(linebuf), ascii);
>
> ...
> }
>
> The expected stopping condition (i < len) is effectively broken
> since len is corrupted and very large. This eventually leads to
> the "ptr+i" being passed to hex_dump_to_buffer() to get closer
> to the end of the actual bounds of "ptr", eventually an out of
> bounds access is done in hex_dump_to_buffer() in the following
> for loop:
>
> for (j = 0; j < len; j++) {
> if (linebuflen < lx + 2)
> goto overflow2;
> ch = ptr[j];
> ...
> }
>
> To fix this we should validate "EALIST_SIZE(ea_buf->xattr)"
> before it is utilised.
Agreed. The patch looks good. I'll add it to jfs-next
Shaggy
>
> Reported-by: syzbot <syzbot+4e6e7e4279d046613bc5@syzkaller.appspotmail.com>
> Tested-by: syzbot <syzbot+4e6e7e4279d046613bc5@syzkaller.appspotmail.com>
> Closes: https://syzkaller.appspot.com/bug?extid=4e6e7e4279d046613bc5
> Fixes: d9f9d96136cb ("jfs: xattr: check invalid xattr size more strictly")
> Cc: stable@vger.kernel.org
> Signed-off-by: Qasim Ijaz <qasdev00@gmail.com>
> ---
> v2:
> - Added Cc stable tag
>
> fs/jfs/xattr.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/fs/jfs/xattr.c b/fs/jfs/xattr.c
> index 24afbae87225..7575c51cce9b 100644
> --- a/fs/jfs/xattr.c
> +++ b/fs/jfs/xattr.c
> @@ -559,11 +555,16 @@ static int ea_get(struct inode *inode, struct ea_buffer *ea_buf, int min_size)
>
> size_check:
> if (EALIST_SIZE(ea_buf->xattr) != ea_size) {
> - int size = clamp_t(int, ea_size, 0, EALIST_SIZE(ea_buf->xattr));
> -
> - printk(KERN_ERR "ea_get: invalid extended attribute\n");
> - print_hex_dump(KERN_ERR, "", DUMP_PREFIX_ADDRESS, 16, 1,
> - ea_buf->xattr, size, 1);
> + if (unlikely(EALIST_SIZE(ea_buf->xattr) > INT_MAX)) {
> + printk(KERN_ERR "ea_get: extended attribute size too large: %u > INT_MAX\n",
> + EALIST_SIZE(ea_buf->xattr));
> + } else {
> + int size = clamp_t(int, ea_size, 0, EALIST_SIZE(ea_buf->xattr));
> +
> + printk(KERN_ERR "ea_get: invalid extended attribute\n");
> + print_hex_dump(KERN_ERR, "", DUMP_PREFIX_ADDRESS, 16, 1,
> + ea_buf->xattr, size, 1);
> + }
> ea_release(inode, ea_buf);
> rc = -EIO;
> goto clean_up;
prev parent reply other threads:[~2025-02-19 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 21:05 Qasim Ijaz
2025-02-19 22:23 ` Dave Kleikamp [this message]
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=6df15794-4acb-4c24-adc8-a273f0fe1b51@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=ancowi69@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=llfamsec@gmail.com \
--cc=qasdev00@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+4e6e7e4279d046613bc5@syzkaller.appspotmail.com \
--cc=zhaomengmeng@kylinos.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®