From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
outbounddisclosures@openai.com, Kyle Zeng <kylebot@openai.com>
Subject: Re: [PATCH 6.12.y] reiserfs: validate tail item bounds before conversion
Date: Fri, 12 Jun 2026 10:41:19 -0400 [thread overview]
Message-ID: <20260612-stable-reply-reiserfs-tail-0006@kernel.org> (raw)
In-Reply-To: <20260611224027.74281-1-kylebot@openai.com>
On Thu, Jun 11, 2026 at 03:40:27PM -0700, Kyle Zeng wrote:
> Validate the per-item page copy and aggregate tail length before calling
> reiserfs_delete_item(), and reject corrupt metadata with -EIO after
> reporting a filesystem error.
Thanks for the fix. Same as your other reiserfs patch: no upstream
commit (reiserfs was removed in 6.13) and no maintainer ack, so I can't
queue a stable-only change for a removed subsystem on my own.
If you can get subsystem review/ack, I'll reconsider. As before,
exploitation requires mounting a crafted image.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-12 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 22:40 [PATCH 6.12.y] reiserfs: validate tail item bounds before conversion Kyle Zeng
2026-06-12 14:41 ` Sasha Levin [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=20260612-stable-reply-reiserfs-tail-0006@kernel.org \
--to=sashal@kernel.org \
--cc=kylebot@openai.com \
--cc=outbounddisclosures@openai.com \
--cc=stable@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.