grsecurity
grsecurity
@grsecurity.bsky.social
Foundational security for the Linux kernel. Solving the most difficult memory unsafety problems. Created by @opensrcsec
247 followers2 following36 posts
We recommend: Apply: git.kernel.org/pub/scm/linu... Ignore the fix for CVE-2026-53166 which introduced the worse DoS and was reverted just recently: git.kernel.org/pub/scm/linu... Apply this fix which addressed the same initial DoS issue without introducing another: git.kernel.org/pub/scm/linu...
KERNSEAL makes the linear page cache overflow in cyberstan.co.uk/fuse-readdir... deterministically unexploitable. Serial log below 👇
We've just published a Knowledge Base article with more information about the vulnerability, current published/unpublished exploits, and current mitigations. We still recommend patching ASAP.
Exploits are now appearing targeting pidfd, which is forced into all Linux kernels since 5.10 (2020), no module or initcall to blacklist this time, must patch ASAP!
Exploits are now appearing targeting pidfd, which is forced into all Linux kernels since 5.10 (2020), no module or initcall to blacklist this time, must patch ASAP!
We've just sent a mail to all customers notifying them of this issue, with split-out fixes available for 5.15, 6.6, and 6.18. We'll share more information on our Knowledge Base as it becomes available.
We've just sent a mail to all customers notifying them of this issue, with split-out fixes available for 5.15, 6.6, and 6.18. We'll share more information on our Knowledge Base as it becomes available.
We've uploaded new patches for 5.15, 6.6, and 6.18 to address an obfuscated upstream Linux logic vulnerability that should exist in all kernel versions: git.kernel.org/pub/scm/linu...
We've uploaded new patches for 5.15, 6.6, and 6.18 to address an obfuscated upstream Linux logic vulnerability that should exist in all kernel versions: git.kernel.org/pub/scm/linu...
The KB article with links to the combined/split-out patches for 5.15 and 6.6 (adapted to grsecurity) are now available.
Updated 5.15 and 6.6 patches are now available. We're now preparing a KB article with more guidance than shared in last night's email with links to combined/split-out patches for both 5.15 and 6.6 for those on older kernels who need CONFIG_CRYPTO_USER_API_AEAD enabled (which shouldn't be anyone)
For it to be effective at all, you would need to have CONFIG_CRYPTO_USER_API_AEAD=m. If it's =y, there is no module and the mitigation is a no-op. oracle.github.io/kconfigs/?co... shows the setting for common distros/versions, but it's most reliable to check your running kernel's config.
For RHEL/RHEL-derived configurations, this approach will work (the function name has been stable since 2015 and initcall_blacklist has been supported since 2014): news.ycombinator.com/item?id=4795...
Preparatory patches: github.com/NVIDIA/open-... Full Kbuild support: github.com/NVIDIA/open-... #grsecurity compatibility: github.com/NVIDIA/open-...
Slides for Pawel's H2HC presentation this month on the TLB are now available on grsecurity.net/papers If you've never heard of "paging-structure caches" before, check it out!
We need to post a correction to yesterday's eBPF performance numbers: Mathias Krause wasn't happy with just a 30x speedup and took a look at one final bottleneck that was bothering him. The speedup over vanilla is now 747x 🤯 (5.27s vs 1h5m40s)
Performance isn't the enemy of security: we care about both. Today's patches finish off a set of security/performance improvements to eBPF. Below we show a ~30x speedup vs vanilla in running the eBPF selftests with every single #grsecurity option enabled!
Testcase fixes were sent upstream by Mathias Krause here: lore.kernel.org/bpf/20241104...
Johannes Wikner has published a detailed walkthrough of the first cross-process Spectre exploit against a real target, an attack he developed in part during his internship with us last year. Check it out here: grsecurity.net/cross_proces...
You are up to date.