CVE-2025-40021Disclosure

LOW

Signal is active with 1 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

1 mentions across 1 observed day

What's happening

Disclosure: 1 classified signal
1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Signal classification1 categories

Disclosure

1100.0%

Referenced assets1 URL

By indicator

https://lore.kernel.org/linux-cve-announce/2025102403-CVE-2025-40021-fbe1@gregkh/

Full discourse1 post

Brad Spengler@spendergrsec200d
Disclosure
Yet we have a CVE for: https://lore.kernel.org/linux-cve-announce/2025102403-CVE-2025-40021-fbe1@gregkh/ Would love to hear the made-up excuse they used for the Xen case
Post summary
The post simply links to a CVE announcement without additional details, indicating an awareness of the vulnerability but no further information about exploitation, mitigation, or technical characteristics.
10021384
4.4K followersView on X

Explore more

Back to dashboard