linux-kernel - Re: [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221102120338.254741f7@rorschach.local.home>
Date:   Wed, 2 Nov 2022 12:03:38 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     postix@...teo.eu
Cc:     20221031144850.5522b036@...schach.local.home,
        linux-kernel@...r.kernel.org, regressions@...ts.linux.dev,
        tiwai@...e.de
Subject: Re: [REGRESSION 6.0.x / 6.1.x] NULL dereferencing at tracing

On Wed,  2 Nov 2022 15:57:56 +0000
postix@...teo.eu wrote:

> Hello everyone,
> 
> I have added lot's of debug printk's to see what's happening and I found 
> that the "cpu" counter, which is used to access the buffer's array 
> elements (cpu_buffer = buffer->buffers[cpu]) in the ring_buffer_wake_waiters
> function, exceeds the maximum number of total of total cores, namely in 
> my case 24, which means, it should only run from 0..23. However, upon 
> debugging, it runs up to 31, and thus causing a NULL pointer dereference 
> (&cpu_buffer->irq_work).
> 

Could you add this patch.

 https://lore.kernel.org/all/20221101191009.1e7378c8@rorschach.local.home/

Thanks,

-- Steve