CVE-2025-38466: perf: Revert to requiring CAP_SYS_ADMIN for uprobes
In the Linux kernel, the following vulnerability has been resolved:
perf: Revert to requiring CAP_SYS_ADMIN for uprobes
Jann reports that uprobes can be used destructively when used in the
middle of an instruction. The kernel only verifies there is a valid
instruction at the requested offset, but due to variable instruction
length cannot determine if this is an instruction as seen by the
intended execution stream.
Additionally, Mark Rutland notes that on architectures that mix data
in the text segment (like arm64), a similar things can be done if the
data word is 'mistaken' for an instruction.
As such, require CAP_SYS_ADMIN for uprobes.
Security readout for executives and security teams
Plain-English summary
A locally authenticated user could misuse Linux uprobes to disrupt or manipulate another execution path, potentially compromising confidentiality, integrity, and availability. The kernel fix restores a strong administrative privilege requirement, limiting uprobe creation to processes with CAP_SYS_ADMIN.
Executive priority
Treat as a high-priority local privilege-boundary issue. Accelerate patching on shared, multi-user, development, and other systems running untrusted local workloads. Remote-only servers with tightly controlled local access may be sequenced behind demonstrably exposed hosts.
Technical view
The kernel accepted uprobes at offsets containing valid instructions without proving the offset aligned with the intended variable-length instruction stream. On architectures such as arm64, text segments may also contain data mistaken for instructions. The resolution requires CAP_SYS_ADMIN for uprobes.
Likely exposure
Exposure applies to affected Linux kernels where a low-privileged local process can create uprobes without CAP_SYS_ADMIN. Internet reachability alone does not create exposure. The supplied version data is ambiguous, so confirm status using the running kernel build and vendor guidance.
Exploitation context
The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with potentially high confidentiality, integrity, and availability impact. The bundle marks KEV false and provides no evidence of active exploitation.
Researcher notes
The core weakness is unsafe uprobe placement relative to the intended instruction stream, plus instruction-versus-data ambiguity on mixed text segments. The fix is authorization hardening rather than complete instruction-stream validation. No CWE is assigned, and the supplied evidence does not establish public exploitation.
Mitigation direction
Install a vendor-supported kernel update containing the uprobe privilege fix.
Prioritize multi-user systems where untrusted local users can access performance tracing facilities.
Until updated, restrict untrusted local access and review vendor-recommended temporary mitigations.
Validation and detection
Record each system's running kernel version, build, architecture, and distribution package release.
Confirm through vendor advisories that the installed kernel includes the relevant stable fix.
Verify unprivileged processes cannot create uprobes without CAP_SYS_ADMIN after remediation.
Review monitoring data for unexpected uprobe or performance-tracing activity by non-administrative users.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38466 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.