public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vasiliy Kovalev <kovalev@altlinux.org>
Cc: Christian Brauner <brauner@kernel.org>,
	lvc-patches@linuxtesting.org, dutyrok@altlinux.org,
	gerben@altlinux.org,
	syzbot+5f3a973ed3dfb85a6683@syzkaller.appspotmail.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key
Date: Mon,  7 Apr 2025 19:25:03 +0200	[thread overview]
Message-ID: <20250407-chorkonzert-ankam-80ebcdbffd20@brauner> (raw)
In-Reply-To: <20241019191303.24048-1-kovalev@altlinux.org>

On Sat, 19 Oct 2024 22:13:03 +0300, Vasiliy Kovalev wrote:
> Syzbot reported an issue in hfs subsystem:
> 
> BUG: KASAN: slab-out-of-bounds in memcpy_from_page include/linux/highmem.h:423 [inline]
> BUG: KASAN: slab-out-of-bounds in hfs_bnode_read fs/hfs/bnode.c:35 [inline]
> BUG: KASAN: slab-out-of-bounds in hfs_bnode_read_key+0x314/0x450 fs/hfs/bnode.c:70
> Write of size 94 at addr ffff8880123cd100 by task syz-executor237/5102
> 
> [...]

Stop-gap measure at best. I expect there to be plenty of other ways for
syzbot to trigger issues in hpfsplus.

---

Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes

[1/1] hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key
      https://git.kernel.org/vfs/vfs/c/bb5e07cb9277

      parent reply	other threads:[~2025-04-07 17:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 19:13 [PATCH] hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key Vasiliy Kovalev
2025-03-20 19:30 ` Salvatore Bonaccorso
2025-03-24 16:14   ` Cengiz Can
2025-03-24 16:17     ` Greg KH
2025-03-24 18:43       ` Cengiz Can
2025-03-24 18:53         ` Greg KH
2025-04-06 16:07           ` Cengiz Can
2025-04-06 16:28             ` Greg KH
2025-04-07 10:59             ` Christian Brauner
2025-04-07 17:15               ` Christian Brauner
2025-04-07 17:29                 ` Attila Szasz
2025-04-07 19:08               ` Darrick J. Wong
2025-04-08 10:11                 ` Richard Weinberger
2025-04-08 14:50                   ` Darrick J. Wong
2025-04-08 15:58                     ` Richard Weinberger
2025-04-16 15:10                   ` Eric Sandeen
2025-04-08  8:03               ` Greg KH
2025-04-08 12:00                 ` Attila Szasz
2025-03-27 19:15       ` Attila Szasz
2025-04-07 17:25 ` Christian Brauner [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=20250407-chorkonzert-ankam-80ebcdbffd20@brauner \
    --to=brauner@kernel.org \
    --cc=dutyrok@altlinux.org \
    --cc=gerben@altlinux.org \
    --cc=kovalev@altlinux.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-patches@linuxtesting.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+5f3a973ed3dfb85a6683@syzkaller.appspotmail.com \
    /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