Kernel: secure boot does not automatically enable kernel lockdown
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.15-100.fc40, 6.12.15-200.fc41
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The Linux Kernel lockdown mode for kernel versions starting on 6.12 and above for Fedora Linux has the lockdown mode disabled without any warning. This may allow an attacker to gain access to sensitive information such kernel memory mappings, I/O ports, BPF and kprobes. Additionally unsigned modules can be loaded, leading to execution of untrusted code breaking breaking any Secure Boot protection. This vulnerability affects only Fedora Linux.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- kernel
From 6.12.4-100.fc40 · fixed in 6.12.15-100.fc40; From 6.12.1-200.fc41 · fixed in 6.12.15-200.fc41
- kernel
Version range not reported
- kernel
Version range not reported
- kernel
Version range not reported
- kernel
Version range not reported
- kernel
Version range not reported
- kernel-rt
Version range not reported
- kernel
Version range not reported
- kernel-rt
Version range not reported
- kernel-rt
Version range not reported
- rhcos
Version range not reported