Kernel-address disclosure via incomplete branch-origin filtering
Published Aug 28, 2026 · Updated Aug 28, 2026
Information disclosure in the AMD LBR V2 perf path in Linux allows local users to read kernel addresses through user-only branch stacks. The hardware privilege filter checks only each branch target, and amd_pmu_lbr_filter failed to reject kernel-space branch-from addresses when user-only sampling excluded kernel branches. Exploitation requires local perf access and an AMD processor with X86_FEATURE_AMD_LBR_V2; the disclosed consequence is kernel-address exposure, not direct kernel-memory reads.
Summary
What happened
Information disclosure in the AMD LBR V2 perf path in Linux allows local users to read kernel addresses through user-only branch stacks. The hardware privilege filter checks only each branch target, and amd_pmu_lbr_filter failed to reject kernel-space branch-from addresses when user-only sampling excluded kernel branches. Exploitation requires local perf access and an AMD processor with X86_FEATURE_AMD_LBR_V2; the disclosed consequence is kernel-address exposure, not direct kernel-memory reads.
The record
- CVE
- CVE-2026-80602
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=6.1
- Affected versionversion=f4f925dae7419fc7a10af539c073871927ce3a24 <208ecca408b1707ad86ea247d3d3e09d3606fc13
- Affected versionversion=f4f925dae7419fc7a10af539c073871927ce3a24 <2a892294b83f541115c94b0bb637f39bef187657
- Affected versionversion=f4f925dae7419fc7a10af539c073871927ce3a24 <5ab0eba9c8819506bcb72348fd701f8a9006f95e
- Affected versionversion=f4f925dae7419fc7a10af539c073871927ce3a24 <5be478c1e08981ca91b34de310d7e2638171d9d8
- Affected versionversion=f4f925dae7419fc7a10af539c073871927ce3a24 <fb3b76b5ad2ebad63dd76f8b65b624eaf638b73f
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
Public exploit references
- Upstream perf branch-stack reproduction commandproof 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