CVE-2025-40021
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.
Affected versions
Linux kernel versions
5.4
and later are affected. Fixed in
5.10.245,
5.15.194,
6.1.155,
6.6.109,
6.12.50,
6.16.10,
6.17
and their respective stable series.
References
The following references provide additional information about CVE-2025-40021 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/07b1f63b5f86765793fab44d3d4c2be681cddafb
-
PatchKernel patch commithttps://git.kernel.org/stable/c/0d41604d2d53c1abe27fefb54b37a8f6642a4d74
-
PatchKernel patch commithttps://git.kernel.org/stable/c/3887f3814c0e770e6b73567fe0f83a2c01a6470c
Frequently asked questions
-
What is CVE-2025-40021?
CVE-2025-40021 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.4 onward and has been patched in 5.10.245, 5.15.194, 6.1.155 and others. CVE-2025-40021 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2025-40021?
Yes — CVE-2025-40021 has been patched. Fixed versions include 5.10.245, 5.15.194, 6.1.155 and others. If you are running Linux kernel 5.4 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-40021 actively exploited?
No — CVE-2025-40021 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.