CVE-2026-53099
Received Received - Intake
BaseFortify

Publication date: 2026-06-24

Last updated on: 2026-06-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Switch CONFIG_CFI_CLANG to CONFIG_CFI This was renamed in commit 23ef9d439769 ("kcfi: Rename CONFIG_CFI_CLANG to CONFIG_CFI") as it is now a compiler-agnostic option. Using the wrong name results in the code getting compiled out. Meaning the CFI failures for btf_dtor_kfunc_t would still trigger.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-24
Last Modified
2026-06-24
Generated
2026-06-25
AI Q&A
2026-06-24
EPSS Evaluated
N/A
NVD
CVE-2026-53099
EUVD
EUVD-2026-38967
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability relates to the Linux kernel's configuration for Control Flow Integrity (CFI). Specifically, the configuration option named CONFIG_CFI_CLANG was renamed to CONFIG_CFI to make it compiler-agnostic. If the old name is used, the relevant code is compiled out, which means that CFI failures related to btf_dtor_kfunc_t would still occur and not be properly handled.

Impact Analysis

If the Linux kernel is compiled with the incorrect configuration name (CONFIG_CFI_CLANG instead of CONFIG_CFI), the Control Flow Integrity protections for certain kernel functions (btf_dtor_kfunc_t) will not be active. This could allow CFI failures to go undetected, potentially leading to security issues such as exploitation of kernel code execution or bypassing security mechanisms.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53099. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart