From: Demi Marie Obenour <demiobenour@gmail.com>
To: oss-security@lists.openwall.com,
Richard Kettlewell <rjk@terraraq.uk>,
Eric Biggers <ebiggers@kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-crypto@vger.kernel.org
Subject: Re: [oss-security] CVE-2026-31431: CopyFail: linux local privilege scalation
Date: Sat, 2 May 2026 18:32:22 -0400 [thread overview]
Message-ID: <3a52a111-e961-4ac6-830c-31465a7d14de@gmail.com> (raw)
In-Reply-To: <cfe5a1f5-f7fe-44a5-8af9-8e4c8d68b3d7@terraraq.uk>
[-- Attachment #1.1.1: Type: text/plain, Size: 1608 bytes --]
On 5/2/26 15:13, Richard Kettlewell wrote:
> On 01/05/2026 16:30, Demi Marie Obenour wrote:
>> On 4/30/26 03:19, Eric Biggers wrote:
>>> But I also hope this finally provides some more impetus for AF_ALG to be
>>> deprecated and removed. It's a massive, largely pointless attack
>>> surface which has been causing problems, including regular CVEs, ever
>>> since it was added to the kernel in 2010. And of course it's gotten
>>> even worse lately, with LLMs now being able to find the bugs.
>>>
>>> Userspace crypto libraries exist. There's no need to escalate to kernel
>>> mode just to do some math.
>>
>> The only reason I can think of to keep it is for embedded systems
>> with weak CPUs and crypto accelerators that are actually worth using.
>> However, those seem to be very rare outside of things like routers,
>> which run specialized distros like OpenWRT. Even when the accelerator
>> exists and is worth using, AF_ALG is certainly not an efficient way
>> to access it.
>
> I have that use case, although fortunately it's in a context where
> splice() is disabled. But the requirement is for access to the SoC's
> accelerator - the interface doesn't need to be via AF_ALG in particular,
> it doesn't have to offer software crypto (and it might be better if it
> didn't), and it needn't be independent of the specific hardware
> (although in the bigger picture it'd be a shame if it wasn't).
>
> ttfn/rjk
Can you provide benchmarks showing that the accelerator is faster
than the CPU on realistic workloads?
--
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 22:32 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 ` [oss-security] CVE-2026-31431: CopyFail: linux local privilege scalation Demi Marie Obenour
[not found] ` <CAM=PXV4q2i13W8Z_AZGDfdxbqWANJ=U4Sw3FTcv5mH_QUrrSfA@mail.gmail.com>
[not found] ` <afcqxCv58YrhbtVr@definition.pseudorandom.co.uk>
2026-05-03 19:20 ` Greg Dahlman
[not found] ` <cfe5a1f5-f7fe-44a5-8af9-8e4c8d68b3d7@terraraq.uk>
2026-05-02 22:32 ` Demi Marie Obenour [this message]
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=3a52a111-e961-4ac6-830c-31465a7d14de@gmail.com \
--to=demiobenour@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oss-security@lists.openwall.com \
--cc=rjk@terraraq.uk \
/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