Tracefs lockdown bypass via unchecked dynamic_events open
Published Oct 24, 2025 · Updated Oct 24, 2025
Improper access control in affected Linux kernel branches beginning with 5.4 allows local privileged users to bypass tracefs lockdown. The dyn_event_open function opens tracefs dynamic_events without calling security_locked_down for LOCKDOWN_TRACEFS. Exploitation requires local privileged tracefs access and enabled kernel lockdown, after which probe events can be added despite that restriction.
Summary
What happened
Improper access control in affected Linux kernel branches beginning with 5.4 allows local privileged users to bypass tracefs lockdown. The dyn_event_open function opens tracefs dynamic_events without calling security_locked_down for LOCKDOWN_TRACEFS. Exploitation requires local privileged tracefs access and enabled kernel lockdown, after which probe events can be added despite that restriction.
The record
- CVE
- CVE-2025-40021
- Published
- Oct 24, 2025
- Updated
- Oct 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1562.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 24, 2025CVE publishedPublication date reported by the CVE source.
- Oct 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 <07b1f63b5f86765793fab44d3d4c2be681cddafb
- Affected versionversion=17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 <0d41604d2d53c1abe27fefb54b37a8f6642a4d74
- Affected versionversion=17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 <3887f3814c0e770e6b73567fe0f83a2c01a6470c
- Affected versionversion=17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 <456c32e3c4316654f95f9d49c12cbecfb77d5660
- Affected versionversion=17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 <573b1e39edfcb7b4eecde0f1664455a1f4462eee
- Affected versionversion=17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 <b47c4e06687a5a7b6c6ef4bd303fcfe4430b26bb
- Affected versionversion=17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 <f3ac1f4eaba58e57943efa3e8b8d71fa7aab0abf
- Affected versionversion=5.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo