From: Leo Stone <leocstone@gmail.com>
To: syzbot+7536f77535e5210a5c76@syzkaller.appspotmail.com
Cc: Leo Stone <leocstone@gmail.com>,
jmorris@namei.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
penguin-kernel@I-love.SAKURA.ne.jp, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, takedakn@nttdata.co.jp,
tomoyo-dev-en@lists.osdn.me
Subject: [PATCH] tomoyo: Reject excessively long lines
Date: Sun, 15 Dec 2024 18:14:58 -0800 [thread overview]
Message-ID: <20241216021459.178759-2-leocstone@gmail.com> (raw)
In-Reply-To: <675f4ea7.050a0220.37aaf.0105.GAE@google.com>
syzbot creates an anonymous memory region, and then issues a
write syscall from the new memory region to a sysfs entry controlled by
tomoyo, specifying a buffer size of just under 2 GB (the actual size of
the buffer is ~32 MB). Because tomoyo_write_control will double the
size of head->write_buf every time it runs out of space for the current
line, and everything in the zero-initialized buffer is on the same line,
the function will eventually issue a kzalloc with a size that is too large,
triggering the warning.
Reject writes with excessively long lines.
Reported-by: syzbot+7536f77535e5210a5c76@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=7536f77535e5210a5c76
Signed-off-by: Leo Stone <leocstone@gmail.com>
---
security/tomoyo/common.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/security/tomoyo/common.c b/security/tomoyo/common.c
index 5c7b059a332a..0c75be949c9d 100644
--- a/security/tomoyo/common.c
+++ b/security/tomoyo/common.c
@@ -2665,6 +2665,10 @@ ssize_t tomoyo_write_control(struct tomoyo_io_buffer *head,
if (head->w.avail >= head->writebuf_size - 1) {
const int len = head->writebuf_size * 2;
+ if (len > KMALLOC_MAX_SIZE) {
+ error = -EINVAL;
+ break;
+ }
char *cp = kzalloc(len, GFP_NOFS);
if (!cp) {
--
2.43.0
next prev parent reply other threads:[~2024-12-16 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 21:48 [syzbot] [tomoyo?] WARNING in tomoyo_write_control syzbot
2024-12-16 2:14 ` Leo Stone [this message]
2024-12-16 7:19 ` [syzbot] " syzbot
2024-12-16 7:20 ` syzbot
2024-12-16 8:19 ` [PATCH] tomoyo: prevent bad buffer size in tracing_cpumask_write Lizhi Xu
2024-12-16 10:06 ` Tetsuo Handa
2024-12-16 10:45 ` [PATCH] tomoyo: don't emit warning in tomoyo_write_control() Tetsuo Handa
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=20241216021459.178759-2-leocstone@gmail.com \
--to=leocstone@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=serge@hallyn.com \
--cc=syzbot+7536f77535e5210a5c76@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takedakn@nttdata.co.jp \
--cc=tomoyo-dev-en@lists.osdn.me \
/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.