[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87qzntmqqr.fsf@linuxpenguins.xyz>
Date: Sun, 03 May 2026 07:43:56 +1000
From: Brian May <brian@...uxpenguins.xyz>
To: oss-security@...ts.openwall.com
Subject: Re: Re: CVE-2026-31431: CopyFail: linux local
privilege scalation
Reid Sutherland <reid@...rddimension.net> writes:
> I'm assuming any thoroughly qualified platform engineer compiles the
> host kernel without module support. At least, that needs to make a
> comeback, bring back applying grsec patches and make menuconfig..
Kernel modules here are good, not bad. If everything was compiled into
the kernel it would be harder to solve this sort of security issue.
In this case, it often just meant disabling the module that often wasn't
even loaded. The only exception was if I tested the vulnerabilty before
hand :-). Even then, easy to unload the module and disable it.
But I heard some enterprise kernels came with the code compiled into the
kernel, and these required a kernel command line option and a reboot to
fix.
Of course, maybe there is the argument that only the things you need
should be enabled; but this would be a lot harder for distros to keep
everyone happy. Maybe an argument for building your own custom kernels
not relying on distro kernels.
--
Brian May @ Linux Penguins
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
