CVE-2025-40021 json
tracing: dynevent: Add a missing lockdown check on dynevent
published last yr. modified 21d ago also EUVD-2025-35838
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.245, 5.15.194, 6.1.155, 6.6.109, 6.12.50, 6.16.10, 6.17
- linux Debian 12 6.1.158-1
- linux Debian 13 6.12.57-1
- linux Debian 14 6.16.10-1
debian advisories DEBIAN-CVE-2025-40021
- linux Ubuntu 22.04 LTS 5.15.0-170.180
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux Ubuntu 25.10 6.17.0-6.6
- linux-aws Ubuntu 22.04 LTS 5.15.0-1100.107
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-aws Ubuntu 25.10 6.17.0-1003.3
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1100.109
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
ubuntu advisories UBUNTU-CVE-2025-40021
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1.21.15
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.61.1
- kernel-syms-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.61.1
suse advisories SUSE-SU-2026:20473-1SUSE-SU-2026:20496-1SUSE-SU-2026:20039-1SUSE-SU-2026:20059-1SUSE-SU-2025:4521-1SUSE-SU-2025:4517-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.8.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-kvmsmall openSUSE Leap 16.0 6.12.0-160000.8.1
opensuse advisories openSUSE-SU-2025:20172-1
- git.kernel.org/stable/c/f3ac1f4eaba58e57943efa3e8b8d71fa7aab0abf commit
- git.kernel.org/stable/c/0d41604d2d53c1abe27fefb54b37a8f6642a4d74 commit
- git.kernel.org/stable/c/07b1f63b5f86765793fab44d3d4c2be681cddafb commit
- git.kernel.org/stable/c/3887f3814c0e770e6b73567fe0f83a2c01a6470c commit
- git.kernel.org/stable/c/573b1e39edfcb7b4eecde0f1664455a1f4462eee commit
- git.kernel.org/stable/c/b47c4e06687a5a7b6c6ef4bd303fcfe4430b26bb commit
- git.kernel.org/stable/c/456c32e3c4316654f95f9d49c12cbecfb77d5660 commit
Is CVE-2025-40021 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-40021 updated cvss 4.4
kernel: tracing: dynevent: Add a missing lockdown check on dynevent
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/f3ac1f4eaba58e57943efa3e8b8d71fa7aab0abf
- git.kernel.org /stable/c/0d41604d2d53c1abe27fefb54b37a8f6642a4d74
- git.kernel.org /stable/c/07b1f63b5f86765793fab44d3d4c2be681cddafb
- git.kernel.org /stable/c/3887f3814c0e770e6b73567fe0f83a2c01a6470c
- git.kernel.org /stable/c/573b1e39edfcb7b4eecde0f1664455a1f4462eee
- git.kernel.org /stable/c/b47c4e06687a5a7b6c6ef4bd303fcfe4430b26bb
- git.kernel.org /stable/c/456c32e3c4316654f95f9d49c12cbecfb77d5660
Sources
- CVE List CVE-2025-40021
- NVD CVE-2025-40021
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.