perf/core: Check kernel access when kernel callchains are requested
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.113, 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: perf/core: Check kernel access when kernel callchains are requested perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel. However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it. Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested. This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Linux Linux
From 0764771dab80d7b84b9a271bee7f1b21a04a3f0c · fixed in 132bee76097be421ab3012130b5b506324cf2be1; From 0764771dab80d7b84b9a271bee7f1b21a04a3f0c · fixed in 2581b43e162cfc43e6f5d8dd8d2b38f3441550de; From 0764771dab80d7b84b9a271bee7f1b21a04a3f0c · fixed in 6e187281f978a2bff98ead6aa40f8ddc9a2c9afb; From 0764771dab80d7b84b9a271bee7f1b21a04a3f0c · fixed in a4573a3838ae4fc73b70019cfa1dac9aaea7cc2f
- Linux Linux
2.6.31
- KernelLinux
fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10