Kernel-address disclosure via incomplete LBR privilege filtering
Published Sep 16, 2026 · Updated Sep 16, 2026
Information disclosure in Linux allows local users to read kernel addresses through user-only Intel LBR branch stacks. The intel_pmu_lbr_filter() function validates a sampled branch's target privilege but fails to reject a kernel-space source address that violates the user-only filter. Reachability requires local perf branch sampling and affected Intel LBR hardware; the demonstrated consequence is address disclosure rather than kernel-memory access.
Summary
What happened
Information disclosure in Linux allows local users to read kernel addresses through user-only Intel LBR branch stacks. The intel_pmu_lbr_filter() function validates a sampled branch's target privilege but fails to reject a kernel-space source address that violates the user-only filter. Reachability requires local perf branch sampling and affected Intel LBR hardware; the demonstrated consequence is address disclosure rather than kernel-memory access.
The record
- CVE
- CVE-2026-89984
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=47125db27e47e9d44c878bf8925aa057824bb0d5 <3c492c8eba02698ca893a9a13388d2adf6dfb839
- Affected versionversion=47125db27e47e9d44c878bf8925aa057824bb0d5 <68c4b780b266a435261a1e029bede5ee3c2735cc
- Affected versionversion=47125db27e47e9d44c878bf8925aa057824bb0d5 <6ac26161db27f7fb9d9e89ae240dbe52795496cc
- Affected versionversion=47125db27e47e9d44c878bf8925aa057824bb0d5 <b589147f54adc62e4172e4acf079ad5fb7b3687f
- Affected versionversion=47125db27e47e9d44c878bf8925aa057824bb0d5 <be0628a101ac05b085aaa4f650d48bd3915e80fa
- Affected versionversion=47125db27e47e9d44c878bf8925aa057824bb0d5 <ca19a175e89b7de604fab736436cbab74030b47a
- Affected versionversion=47125db27e47e9d44c878bf8925aa057824bb0d5 <e2b0575900ff72aa82748af96e7bd564ade5157a
- Affected versionversion=47125db27e47e9d44c878bf8925aa057824bb0d5 <f3705db4e6378cc1b91a38ce0fe2f879055e23ca
- Affected versionversion=5.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Intel LBR kernel-address leak perf reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo