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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ce50a353-e501-4a22-9742-188edfa2a7b2@roeck-us.net>
Date: Thu, 22 May 2025 11:53:15 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Kees Cook <kees@...nel.org>
Cc: Joel Granados <joel.granados@...nel.org>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, Wen Yang <wen.yang@...ux.dev>
Subject: Re: [PATCH] kernel/sysctl-test: Unregister sysctl table after test
 completion

On Wed, May 21, 2025 at 06:32:11PM -0700, Guenter Roeck wrote:
> One of the sysctl tests registers a valid sysctl table. This operation
> is expected to succeed. However, it does not unregister the table after
> executing the test. If the code is built as module and the module is
> unloaded after the test, the next operation trying to access the table
> (such as 'sysctl -a') will trigger a crash.
> 
> Unregister the registered table after test completiion to solve the
> problem.
> 

Never mind, I just learned that a very similar patch has been submitted
last December or so but was rejected, and that the acceptable (?) fix seems
to be stalled.

Sorry for the noise.

Guenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ