In the Linux kernel, the following vulnerability has been resolved:
bpf: crypto: Use the correct destructor kfunc type
With CONFIG_CFI enabled, the kernel strictly enforces that indirect function calls use a function pointer type that matches the target function. I ran into the following type mismatch when running BPF self-tests:
CFI failure at bpf_obj_free_fields+0x190/0x238 (target: bpf_crypto_ctx_release+0x0/0x94; expected type: 0xa488ebfc) Internal error: Oops - CFI: 00000000f2008228 [#1] SMP ...
As bpf_crypto_ctx_release() is also used in BPF programs and using a void pointer as the argument would make the verifier unhappy, add a simple stub function with the correct type and register it as the destructor kfunc instead.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade kernel6.18-develUpgrade kernel6.18-debuginfoUpgrade kernel6.18-tools-develUpgrade kernel6.18Upgrade bpftool6.18-debuginfoUpgrade kernel6.18-libbpf-staticUpgrade kernel6.18-headersUpgrade kernel6.18-toolsUpgrade kernel6.18-libbpfUpgrade kernel-livepatch-6.18.16-18.222Upgrade kernel6.18-modules-extraUpgrade kernel6.18-libbpf-debuginfoUpgrade kernel6.18-debuginfo-common-x86_64Upgrade perf6.18-debuginfoUpgrade kernel6.18-modules-extra-commonUpgrade python3-perf6.18-debuginfoUpgrade bpftool6.18Upgrade kernel6.18-libbpf-develUpgrade perf6.18Upgrade kernel6.18-debuginfo-common-aarch64Upgrade python3-perf6.18Upgrade kernel6.18-tools-debuginfo | May 19, 2026 | May 8, 2026 |
| Debian | — | Upgrade linux | Jul 23, 2026 | Jul 23, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub