BaseFortify

Publication date: 2025-10-24

Last updated on: 2025-10-27

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: dynevent: Add a missing lockdown check on dynevent Since dynamic_events interface on tracefs is compatible with kprobe_events and uprobe_events, it should also check the lockdown status and reject if it is set.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-24

Last Modified

2025-10-27

Generated

2026-07-06

AI Q&A

2025-10-24

EPSS Evaluated

2026-07-05

NVD

CVE-2025-40021

EUVD

EUVD-2025-35838

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves the dynamic_events interface on tracefs, which is compatible with kprobe_events and uprobe_events. The issue was that it lacked a lockdown check, meaning it did not verify if the system was in lockdown mode before allowing certain operations. This missing check could allow unauthorized actions when lockdown is enabled. The vulnerability was resolved by adding the missing lockdown check to the dynevent interface.

Impact Analysis

If exploited, this vulnerability could allow unauthorized users or processes to perform tracing operations via the dynamic_events interface even when the system lockdown is enabled. This could potentially lead to information disclosure or unauthorized system behavior by bypassing security restrictions intended to protect the system during lockdown.

Hi! I’m here to help you understand CVE-2025-40021. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70