From: Greg KH <gregkh@linuxfoundation.org>
To: Edward Adam Davis <eadavis@sina.com>
Cc: dakr@kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org, rafael@kernel.org,
syzbot+9a321aea9d851b299486@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] sysfs: prevent writing excessively large files
Date: Wed, 16 Sep 2026 18:44:06 +0100 [thread overview]
Message-ID: <2026091641-tanned-bust-37f2@gregkh> (raw)
In-Reply-To: <20260916101930.962961-1-eadavis@sina.com>
On Wed, Sep 16, 2026 at 06:19:30PM +0800, Edward Adam Davis wrote:
> From: Edward Aadm Davis <eadavis@sina.com>
>
> On Wed, 16 Sep 2026 09:17:56 +0200, Greg KH 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:
> >
> > What sysfs file are you hitting this on?
> Regular sysfs files.
Which one, all?
> > > 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")
> >
> > What changed to suddenly cause this to show up now if this has been
> > present for decades?
> This issue has always existed. It remained undetected simply because the
> buffer lengths typically passed when writing to `/sys/bus/acpi/uevent`
> happened to be reasonably appropriate.
So what changed to cause this to show up now?
thanks,
greg k-h
next prev parent reply other threads:[~2026-09-16 17:47 UTC|newest]
Thread overview: 11+ 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 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 [this message]
2026-09-17 4:24 ` Edward Adam Davis
2026-09-17 7:34 ` Greg KH
2026-09-17 7:56 ` Edward Adam Davis
2026-09-23 10:55 ` [PATCH v2] kobject: optimize count first value Edward Adam Davis
2026-09-23 12:05 ` Greg KH
2026-09-17 10:00 ` [PATCH] sysfs: prevent writing excessively large files 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=2026091641-tanned-bust-37f2@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 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.