On Tue, Jul 15 2025 12:44:40 +0200 Krzysztof Kozlowski wrote:
>You should disclose that you used some AI tool for that... and that
>other report(s) was really fake finding. People should know you
>generated it with AI, so they could make informed decision whether to
>even allocate time here.
Alt
On 7/15/2025 5:44 AM, Krzysztof Kozlowski wrote:
On 04/07/2025 05:16, jackysliu wrote:
From: jackysliu
A null pointer dereference vulnerability exists in the AMD display driver's
(DC module) cleanup function dc_destruct().
When display control context (dc->ctx) construction fails
(due to
On 04/07/2025 05:16, jackysliu wrote:
> From: jackysliu
>
> A null pointer dereference vulnerability exists in the AMD display driver's
> (DC module) cleanup function dc_destruct().
> When display control context (dc->ctx) construction fails
> (due to memory allocation failure), this pointer r
From: jackysliu
A null pointer dereference vulnerability exists in the AMD display driver's
(DC module) cleanup function dc_destruct().
When display control context (dc->ctx) construction fails
(due to memory allocation failure), this pointer remains NULL.
During subsequent error handling when
