{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40021 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40021 is a vulnerability in Linux, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40021 and fix it if it is affected.\n\nWhat it is: CVE-2025-40021 is a vulnerability in Linux, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40021 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-40021/ (Markdown: https://insights.sbomify.com/CVE-2025-40021/index.md)","id":"CVE-2025-40021","markdown":"https://insights.sbomify.com/CVE-2025-40021/index.md","name":"CVE-2025-40021","record":{"aliases":["AZL-68811","BELL-CVE-2025-40021","DEBIAN-CVE-2025-40021","GHSA-hmw5-3qc9-5j9m","ROOT-OS-DEBIAN-11-CVE-2025-40021","ROOT-OS-UBUNTU-2404-CVE-2025-40021","UBUNTU-CVE-2025-40021"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"Attackers with high privileges can bypass kernel lockdown restrictions via the dynamic events interface in the Linux kernel.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: dynevent: Add a missing lockdown check on dynevent\n\nSince dynamic_events interface on tracefs is compatible with\nkprobe_events and uprobe_events, it should also check the lockdown\nstatus and reject if it is set.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"tracing: dynevent: Add a missing lockdown check on dynevent","id":"CVE-2025-40021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"crypto: af_alg - Fix incorrect boolean values in af_alg_ctx","id":"CVE-2025-40022"},"packages":[],"prev":{"headline":"can: peak_usb: fix shift-out-of-bounds issue","id":"CVE-2025-40020"},"products":["Linux"],"published":"2025-10-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"Attackers with high privileges can bypass kernel lockdown restrictions via the dynamic events interface in the Linux kernel.","url":"https://insights.sbomify.com/CVE-2025-40021/"}