# CVE-2025-1272: Kernel: secure boot does not automatically enable kernel lockdown

> Attackers can bypass Secure Boot protections to load unsigned modules and access sensitive kernel memory due to disabled lockdown mode.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-xj75-gfvf-4g86, ROOT-OS-UBUNTU-2204-CVE-2025-1272, UBUNTU-CVE-2025-1272

## What is CVE-2025-1272?

CVE-2025-1272 is a high-severity vulnerability in Fedora Linux, published on 18 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-1272?


## How do I fix CVE-2025-1272?

Apply the vendor's patch.

## Is CVE-2025-1272 being exploited?

There is no known exploitation of CVE-2025-1272 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1272 and fix it if it is affected.

What it is: CVE-2025-1272 is a high-severity vulnerability in Fedora Linux, published on 18 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-1272 in the wild and no public exploit code.

Affected product: Fedora Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1272/ (Markdown: https://insights.sbomify.com/CVE-2025-1272/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1272
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1272
- OSV: https://osv.dev/vulnerability/CVE-2025-1272

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1272/
Summaries are generated and may contain mistakes; the official description above is the record.