CVE-2025-40021tracing: dynevent: Add a missing lockdown check on dynevent
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 months later
· 6 months later
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 – < f3ac1f4eaba58e57943efa3e8b8d71fa7aab0abf
- affected 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 – < 0d41604d2d53c1abe27fefb54b37a8f6642a4d74
- affected 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 – < 07b1f63b5f86765793fab44d3d4c2be681cddafb
- affected 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 – < 3887f3814c0e770e6b73567fe0f83a2c01a6470c
- affected 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 – < 573b1e39edfcb7b4eecde0f1664455a1f4462eee
- affected 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 – < b47c4e06687a5a7b6c6ef4bd303fcfe4430b26bb
- affected 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 – < 456c32e3c4316654f95f9d49c12cbecfb77d5660
- affected 5.4
- unaffected < 5.4
- unaffected 5.10.245 – ≤ 5.10.*
- unaffected 5.15.194 – ≤ 5.15.*
- unaffected 6.1.155 – ≤ 6.1.*
- unaffected 6.6.109 – ≤ 6.6.*
- unaffected 6.12.50 – ≤ 6.12.*
- unaffected 6.16.10 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References7
- https://git.kernel.org/stable/c/f3ac1f4eaba58e57943efa3e8b8d71fa7aab0abf (opens in a new tab)
- https://git.kernel.org/stable/c/0d41604d2d53c1abe27fefb54b37a8f6642a4d74 (opens in a new tab)
- https://git.kernel.org/stable/c/07b1f63b5f86765793fab44d3d4c2be681cddafb (opens in a new tab)
- https://git.kernel.org/stable/c/3887f3814c0e770e6b73567fe0f83a2c01a6470c (opens in a new tab)
- https://git.kernel.org/stable/c/573b1e39edfcb7b4eecde0f1664455a1f4462eee (opens in a new tab)
- https://git.kernel.org/stable/c/b47c4e06687a5a7b6c6ef4bd303fcfe4430b26bb (opens in a new tab)
- https://git.kernel.org/stable/c/456c32e3c4316654f95f9d49c12cbecfb77d5660 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-35838 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-40021)Record last updated .