CVE-2026-89984perf/x86/intel: Fix kernel address leakages in LBR stack
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel: Fix kernel address leakages in LBR stack Before Arch LBR gained CPL filtering support, a user-only branch stack could still contain kernel addresses. As a result, kernel branch records may be exposed to user space even when PERF_SAMPLE_BRANCH_USER is requested. For example, on Intel Tiger Lake, the following command can still report SYSRET/ERET entries with kernel-space from addresses: $ ./perf record -e cycles:p -o - --branch-filter any,save_type,u -- \ ./perf bench syscall basic --loop 1000 | \ ./perf script -i - --fields brstack|tr ' ' '\n'| \ grep -E '0x[89a-f][0-9a-f]{15}' Total time: 0.000 [sec] 0.219000 usecs/op 4,566,210 ops/sec [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.551 MB - ] 0xffffffff93c001c8/0x7f12a2b1d647/P/-/-/16959/SYSRET/- 0xffffffff93c001c8/0x7f12a2b1d5c2/P/-/-/17535/SYSRET/- 0xffffffff93c01928/0x7f12a2861000/P/-/-/6719/ERET/- 0xffffffff93c01928/0x7f12a297a000/P/-/-/8575/ERET/- The problem is that intel_pmu_lbr_filter() does not fully validate the privilege level of sampled entries. It filters some mismatches based on the branch type and the to address, but it does not reject entries whose from address violates the requested branch privilege filter. Fix this by extending software filtering to validate both from and to addresses against br_sel. Any LBR entry contains kernel address does not match the requested user filter is dropped. This prevents kernel addresses from appearing in user-only branch stacks.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 47125db27e47e9d44c878bf8925aa057824bb0d5 before f3705db4e6378cc1b91a38ce0fe2f879055e23ca; from 47125db27e47e9d44c878bf8925aa057824bb0d5 before b589147f54adc62e4172e4acf079ad5fb7b3687f; from 47125db27e47e9d44c878bf8925aa057824bb0d5 before be0628a101ac05b085aaa4f650d48bd3915e80fa; from 47125db27e47e9d44c878bf8925aa057824bb0d5 before ca19a175e89b7de604fab736436cbab74030b47a; 47125db27e47e9d44c878bf8925aa057824bb0d5 builds before 6ac26161db27f7fb9d9e89ae240dbe52795496cc; 47125db27e47e9d44c878bf8925aa057824bb0d5 builds before 3c492c8eba02698ca893a9a13388d2adf6dfb839; 47125db27e47e9d44c878bf8925aa057824bb0d5 builds before 68c4b780b266a435261a1e029bede5ee3c2735cc; from 47125db27e47e9d44c878bf8925aa057824bb0d5 before e2b0575900ff72aa82748af96e7bd564ade5157a | CNA record |
References
- https://git.kernel.org/stable/c/f3705db4e6378cc1b91a38ce0fe2f879055e23ca
- https://git.kernel.org/stable/c/b589147f54adc62e4172e4acf079ad5fb7b3687f
- https://git.kernel.org/stable/c/be0628a101ac05b085aaa4f650d48bd3915e80fa
- https://git.kernel.org/stable/c/ca19a175e89b7de604fab736436cbab74030b47a
- https://git.kernel.org/stable/c/6ac26161db27f7fb9d9e89ae240dbe52795496cc
- https://git.kernel.org/stable/c/3c492c8eba02698ca893a9a13388d2adf6dfb839
- https://git.kernel.org/stable/c/68c4b780b266a435261a1e029bede5ee3c2735cc
- https://git.kernel.org/stable/c/e2b0575900ff72aa82748af96e7bd564ade5157a
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.