The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Wang Liang <wangliang74@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: <mhiramat@kernel.org>, <mathieu.desnoyers@efficios.com>,
	<tglozar@redhat.com>, <yuehaibing@huawei.com>,
	<zhangchangzhong@huawei.com>,
	<linux-trace-kernel@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] tracing/osnoise: fix null-ptr-deref in bitmap_parselist
Date: Sat, 6 Sep 2025 10:58:25 +0800	[thread overview]
Message-ID: <54df95d3-e8fe-4aa2-966d-bd580cdf2b86@huawei.com> (raw)
In-Reply-To: <20250905184456.084d1ff3@gandalf.local.home>


在 2025/9/6 6:44, Steven Rostedt 写道:
> On Fri, 5 Sep 2025 11:25:44 +0800
> Wang Liang <wangliang74@huawei.com> wrote:
>
> Hi Wang,
>
> FYI, the tracincg subsystem requires capital subject:
>
>    tracing/osnoise: Fix null-ptr-deref in bitmap_parselist()
>
> And parenthesis for function names.


Thanks for your guide, it is clear and helpful!

>> A crash was observed with the following output:
>>
>> BUG: kernel NULL pointer dereference, address: 0000000000000010
>> Oops: Oops: 0000 [#1] SMP NOPTI
>> CPU: 2 UID: 0 PID: 92 Comm: osnoise_cpus Not tainted 6.17.0-rc4-00201-gd69eb204c255 #138 PREEMPT(voluntary)
>> RIP: 0010:bitmap_parselist+0x53/0x3e0
>> Call Trace:
>>   <TASK>
>>   osnoise_cpus_write+0x7a/0x190
>>   vfs_write+0xf8/0x410
>>   ? do_sys_openat2+0x88/0xd0
>>   ksys_write+0x60/0xd0
>>   do_syscall_64+0xa4/0x260
>>   entry_SYSCALL_64_after_hwframe+0x77/0x7f
>>   </TASK>
>>
>> This issue can be reproduced by below code:
>>
>> fd=open("/sys/kernel/debug/tracing/osnoise/cpus", O_WRONLY);
>> write(fd, "0-2", 0);
>>
>> When user pass 'count=0' to osnoise_cpus_write(), kmalloc() will return
>> ZERO_SIZE_PTR (16) and cpulist_parse() treat it as a normal value, which
>> trigger the null pointer dereference. Add check for the parameter 'count'.
>>
>> Fixes: 17f89102fe23 ("tracing/osnoise: Allow arbitrarily long CPU string")
>> Signed-off-by: Wang Liang <wangliang74@huawei.com>
>> ---
>>   kernel/trace/trace_osnoise.c | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/kernel/trace/trace_osnoise.c b/kernel/trace/trace_osnoise.c
>> index fd259da0aa64..edf5178d0317 100644
>> --- a/kernel/trace/trace_osnoise.c
>> +++ b/kernel/trace/trace_osnoise.c
>> @@ -2322,6 +2322,9 @@ osnoise_cpus_write(struct file *filp, const char __user *ubuf, size_t count,
>>   	int running, err;
>>   	char *buf __free(kfree) = NULL;
>>   
>> +	if (count < 1)
>> +		return -EINVAL;
> Sending a count of 0 is not invalid. This should simply return 0;
>
> -- Steve


Ok. I will correct it and send a v2 patch later.

------
Best regards
Wang Liang

>> +
>>   	buf = kmalloc(count, GFP_KERNEL);
>>   	if (!buf)
>>   		return -ENOMEM;
>

      reply	other threads:[~2025-09-06  2:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05  3:25 [PATCH -next] tracing/osnoise: fix null-ptr-deref in bitmap_parselist Wang Liang
2025-09-05 22:44 ` Steven Rostedt
2025-09-06  2:58   ` Wang Liang [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=54df95d3-e8fe-4aa2-966d-bd580cdf2b86@huawei.com \
    --to=wangliang74@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglozar@redhat.com \
    --cc=yuehaibing@huawei.com \
    --cc=zhangchangzhong@huawei.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