From: Greg KH <gregkh@linuxfoundation.org>
To: Edward Adam Davis <eadavis@sina.com>
Cc: syzbot+9a321aea9d851b299486@syzkaller.appspotmail.com,
dakr@kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org, rafael@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] sysfs: prevent writing excessively large files
Date: Thu, 17 Sep 2026 08:34:46 +0100 [thread overview]
Message-ID: <2026091700-baritone-clapping-685d@gregkh> (raw)
In-Reply-To: <20260915122018.924041-1-eadavis@sina.com>
On Tue, Sep 15, 2026 at 08:20:17PM +0800, Edward Adam Davis wrote:
> Since atomic_write_len is not configured for sysfs_file_kfops_rw, a large
> file write via sysfs_kf_write() may result in an out-of-bounds read when
> checking for the null terminator of a string element in the kobject_actions
> array within kobject_action_type(), potentially hitting:
>
> BUG: KASAN: global-out-of-bounds in kobject_action_type lib/kobject_uevent.c:86 [inline]
> BUG: KASAN: global-out-of-bounds in kobject_synth_uevent+0x79d/0x7d0 lib/kobject_uevent.c:200
> Read of size 1 at addr ffffffff8d72559f by task syz.0.17/5917
> Call Trace:
> kobject_action_type lib/kobject_uevent.c:86 [inline]
> kobject_synth_uevent+0x79d/0x7d0 lib/kobject_uevent.c:200
> bus_uevent_store+0x3d/0x90 drivers/base/bus.c:917
> bus_attr_store+0x74/0xb0 drivers/base/bus.c:172
> sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145
> kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345
> new_sync_write fs/read_write.c:595 [inline]
> vfs_write+0x6af/0x1050 fs/read_write.c:687
>
> Add atomic_write_len for sysfs_file_kfops_rw and sysfs_file_kfops_wo
> properly.
>
> Fixes: f6acf8bb6a40 ("sysfs, kernfs: introduce kernfs_ops")
> Reported-by: syzbot+9a321aea9d851b299486@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=9a321aea9d851b299486
> Tested-by: syzbot+9a321aea9d851b299486@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@sina.com>
> ---
> fs/sysfs/file.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/sysfs/file.c b/fs/sysfs/file.c
> index cd5bb0f9fee6..a63130d18680 100644
> --- a/fs/sysfs/file.c
> +++ b/fs/sysfs/file.c
> @@ -228,10 +228,12 @@ static const struct kernfs_ops sysfs_file_kfops_ro = {
> };
>
> static const struct kernfs_ops sysfs_file_kfops_wo = {
> + .atomic_write_len = PAGE_SIZE,
> .write = sysfs_kf_write,
> };
>
> static const struct kernfs_ops sysfs_file_kfops_rw = {
> + .atomic_write_len = PAGE_SIZE,
> .seq_show = sysfs_kf_seq_show,
> .write = sysfs_kf_write,
> };
> --
> 2.43.0
>
Are you sure this will not break those sysfs files that want larger page
sizes? Given the age of this "issue" it's really worrying to me to
change it now...
thanks,
greg k-h
next prev parent reply other threads:[~2026-09-17 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 16:38 [syzbot] [kernel?] KASAN: global-out-of-bounds Read in bus_uevent_store syzbot
2026-09-15 11:00 ` Edward Adam Davis
2026-09-15 11:22 ` syzbot
2026-09-15 11:24 ` Edward Adam Davis
2026-09-15 12:06 ` syzbot
2026-09-15 12:20 ` [PATCH] sysfs: prevent writing excessively large files Edward Adam Davis
2026-09-16 7:17 ` Greg KH
2026-09-16 10:19 ` Edward Adam Davis
2026-09-16 17:44 ` Greg KH
2026-09-17 4:24 ` Edward Adam Davis
2026-09-17 7:34 ` Greg KH [this message]
2026-09-17 7:56 ` Edward Adam Davis
2026-09-17 10:00 ` David Laight
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=2026091700-baritone-clapping-685d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=eadavis@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzbot+9a321aea9d851b299486@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®