From: Greg KH <gregkh@linuxfoundation.org>
To: 이상호 <kudo3228@gmail.com>
Cc: kees@kernel.org, linux-kernel@vger.kernel.org, security@kernel.org
Subject: Re: [BUG] ufs: crafted writable mount can overflow cylinder summary buffer
Date: Wed, 17 Jun 2026 20:29:59 +0530 [thread overview]
Message-ID: <2026061713-extortion-shower-f4f4@gregkh> (raw)
In-Reply-To: <CAFvCSAZAQFDo9tJdRCqkstYuyQQ9V5p==S_1z1haOBwcSKMWQg@mail.gmail.com>
On Wed, Jun 17, 2026 at 11:42:40PM +0900, 이상호 wrote:
> Hello,
>
> I am reporting a UFS/FFS mount-time memory corruption issue in
> ufs_read_cylinder_structures().
>
> A crafted UFS/FFS filesystem image can set inconsistent cylinder-summary
> geometry so that the kernel allocates kmalloc(s_cssize) but copies more than
> that allocation while reading cylinder summary blocks during a writable UFS
> mount.
No need to cc: the security list for this, it's just a "normal" bug to
fix. Please submit a patch to resolve it if you wish to see it fixed in
the kernel or even better, in the userspace fsck tool.
thanks,
greg k-h
prev parent reply other threads:[~2026-06-17 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 14:42 이상호
2026-06-17 14:59 ` Greg KH [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=2026061713-extortion-shower-f4f4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=kudo3228@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=security@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 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®