[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <675f88d0.050a0220.37aaf.010e.GAE@google.com>
Date: Sun, 15 Dec 2024 17:56:32 -0800
From: syzbot <syzbot+0aecfd34fb878546f3fd@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [trace?] WARNING in bitmap_parse_user
For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org.
***
Subject: Re: [syzbot] [trace?] WARNING in bitmap_parse_user
Author: lizhi.xu@...driver.com
User input a too large count 0x40fdef, it will triger a warning in bitmap_parse_user.
#syz test
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index be62f0ea1814..9e989d97bb78 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -5224,6 +5224,8 @@ tracing_cpumask_write(struct file *filp, const char __user *ubuf,
struct trace_array *tr = file_inode(filp)->i_private;
cpumask_var_t tracing_cpumask_new;
int err;
+ if (count == 0 || count << PAGE_SHIFT > MAX_PAGE_ORDER)
+ return -EINVAL;
if (!zalloc_cpumask_var(&tracing_cpumask_new, GFP_KERNEL))
return -ENOMEM;
Powered by blists - more mailing lists