linux-kernel - Re: CVE-2024-27429: netrom: Fix a data-race around sysctl_netrom_obsolescence_count

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]

Date: Tue, 21 May 2024 16:40:24 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Michal Hocko <mhocko@...e.com>
Cc: cve@...nel.org, linux-kernel@...r.kernel.org,
	Jason Xing <kernelxing@...cent.com>,
	linux-cve-announce@...r.kernel.org
Subject: Re: CVE-2024-27429: netrom: Fix a data-race around
 sysctl_netrom_obsolescence_count_initialiser

On Tue, May 21, 2024 at 10:39:04AM +0200, Michal Hocko wrote:
> This and couple of others are all having the same pattern. Adding
> READ_ONCE for an integer value with a claim that this might race with
> sysctl updates. While the claim about the race is correct I fail to see
> how this could have any security consequences. Even if a partial write
> was observed which sounds _more_ than theoretical these all are merely
> timeouts and delays.
> 
> Is there anything I am missing?

Nope, you are right, our fault, I'll go revoke this now.

Thanks for the review, it's much appreciated!

greg k-h