From: Demi Marie Obenour <demiobenour@gmail.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: oss-security@lists.openwall.com,
Jan Schaumann <jschauma@netmeister.org>,
iwd@lists.linux.dev,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [oss-security] CVE-2026-31431: CopyFail: linux local privilege scalation
Date: Sat, 2 May 2026 02:39:12 -0400 [thread overview]
Message-ID: <378c2ca2-417a-4969-bda5-b7d3f3e8b6fd@gmail.com> (raw)
In-Reply-To: <20260502035402.GB3872267@google.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1012 bytes --]
On 5/1/26 23:54, Eric Biggers wrote:
> On Sat, May 02, 2026 at 03:35:58AM +0000, Eric Biggers wrote:
>> So the idea would be something along the lines of:
>
> And just to make sure no one gets the wrong impression: just because
> there seem to be ways in which the attack surface of AF_ALG could/should
> be reduced doesn't mean that userspace should keep using it (or even
> worse, start to use it). Fixing programs like iwd needs to proceed
> concurrently, so that eventually (some years down the line) the problem
> can finally be fully solved by removing AF_ALG from the kernel source.
>
> - Eric
Can AF_ALG be emulated using LD_PRELOAD? That would allow it to be
eliminated from the kernel much more quickly, as one would not need
to get rid of all of its existing users. It would even work for those
who need AF_ALG because of closed source binaries, who otherwise will
have no alternative other than running an old kernel in a VM.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-02 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <afJorKIje4O6dXbH@netmeister.org>
[not found] ` <d6111caa-db61-498a-92cb-ea7a0aa0a5e2@ehuk.net>
[not found] ` <87se8dgicq.fsf@gentoo.org>
[not found] ` <afL-QhLfEKqHZqka@eldamar.lan>
[not found] ` <20260430071917.GB54208@sol>
[not found] ` <177abb5d-8ba9-4bb9-8b23-9fbc868ed3cd@gmail.com>
[not found] ` <20260501180028.GA2260@sol>
[not found] ` <19837ef5-e5b6-45f4-8336-3ce07423dfb1@gmail.com>
[not found] ` <20260501201841.GA2540@quark>
[not found] ` <c13dd3c5-ddc1-431e-bc7d-2de39c551f8e@gmail.com>
[not found] ` <20260502033556.GA3872267@google.com>
2026-05-02 4:52 ` AF_ALG hardening Demi Marie Obenour
2026-05-02 8:19 ` Simon Richter
2026-05-02 20:42 ` Demi Marie Obenour
2026-05-02 19:16 ` Eric Biggers
2026-05-04 19:01 ` Simon Richter
2026-05-04 19:54 ` Eric Biggers
[not found] ` <20260502035402.GB3872267@google.com>
2026-05-02 6:39 ` Demi Marie Obenour [this message]
[not found] ` <CAM=PXV4q2i13W8Z_AZGDfdxbqWANJ=U4Sw3FTcv5mH_QUrrSfA@mail.gmail.com>
[not found] ` <afcqxCv58YrhbtVr@definition.pseudorandom.co.uk>
2026-05-03 19:20 ` [oss-security] CVE-2026-31431: CopyFail: linux local privilege scalation Greg Dahlman
[not found] ` <cfe5a1f5-f7fe-44a5-8af9-8e4c8d68b3d7@terraraq.uk>
2026-05-02 22:32 ` Demi Marie Obenour
2026-05-03 6:30 ` Peter Gutmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=378c2ca2-417a-4969-bda5-b7d3f3e8b6fd@gmail.com \
--to=demiobenour@gmail.com \
--cc=ebiggers@kernel.org \
--cc=iwd@lists.linux.dev \
--cc=jschauma@netmeister.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oss-security@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox