Re:Copy Fail – CVE-2026-31431
by angry_octet on Thursday April 30, 2026 @05:35AM
(#47960140)
All the uses of vmsplice etc are a bit tricky, and that points to the need for a better interface. But given you're using splice, why not do the crypto in user space? A belief that it is better to be fast and buggy than safe and slower?
[ Parent
| on HN ]
If neither a hardware component nor kernel key management is involved, crypto should be done in userspace, end of sentence.
The more I think about it, the more I think it should be behind CAP_SYS_ADMIN, or a new CAP_KCRYPT (better name TBD. CAP_CRYPT_OFFLOAD?)
Re:Copy Fail – CVE-2026-31431
by angry_octet on Thursday April 30, 2026 @08:24AM
(#47961371)
Yes it should definitely require a capability.
Still a risk that some admin-enabled method (like enabling an IPsec VPN) provides a path to it, but would reduce the potential for crafting weird inputs.
Re:Copy Fail – CVE-2026-31431
by angry_octet on Thursday April 30, 2026 @08:25AM
(#47961387)
I'm also wondering if it couldn't be rewritten to use io_uring interfaces.
That's really orthogonal (and you can already do io_uring with AF_ALG, at the end of the day AF_ALG is just recvmsg() and sendmsg(), which work just fine in io_uring...)
Re:Copy Fail – CVE-2026-31431
by angry_octet on Sunday May 03, 2026 @11:00AM
(#47997610)
I mean for more efficient and easier to verify out-of-kernel implementations of crypto with kernel like speeds.