linux-kernel - Re: [PATCH] zram: fix NULL pointer dereference in zcomp_available

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: <h3fagdwigvveeqkd7zikzv2glcfiarqpowiumna6ngb7ktd4zz@7is5ivhmyvbu>
Date: Wed, 6 Aug 2025 11:59:44 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Seyediman Seyedarab <imandevel@...il.com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, minchan@...nel.org, 
	axboe@...nel.dk, linux-kernel@...r.kernel.org, linux-block@...r.kernel.org, 
	syzbot+1a281a451fd8c0945d07@...kaller.appspotmail.com
Subject: Re: [PATCH] zram: fix NULL pointer dereference in
 zcomp_available_show()

On (25/08/05 18:03), Seyediman Seyedarab wrote:
> I need to correct my previous statement about the use-after-free issue.
> 
> My reproducer was wrong. The garbage output I reported was actually from
> an uninitialized buffer in  my test code, not from reading freed memory! 
> When the device is removed, the kernel correctly returns -ENODEV
> rather than accessing freed memory:

[..]

> The kernel properly protects against use-after-free in this path. I 
> apologize for the confusion.

Great, thanks a lot for the update!