# perf/x86/amd/lbr: Fix kernel address leakage

CVE record · `CVE-2026-80602`

- **Identifiers:** `CVE-2026-80602`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 28 Aug 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 28 Aug 2026, 06:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `f4f925dae7419fc7a10af539c073871927ce3a24 to before 5adfec05e804ce4bd3368b75df5e5b7b40ee960b` (git)
  - affected: `f4f925dae7419fc7a10af539c073871927ce3a24 to before 5be478c1e08981ca91b34de310d7e2638171d9d8` (git)
  - affected: `f4f925dae7419fc7a10af539c073871927ce3a24 to before 208ecca408b1707ad86ea247d3d3e09d3606fc13` (git)
  - affected: `f4f925dae7419fc7a10af539c073871927ce3a24 to before 5ab0eba9c8819506bcb72348fd701f8a9006f95e` (git)
  - affected: `f4f925dae7419fc7a10af539c073871927ce3a24 to before fb3b76b5ad2ebad63dd76f8b65b624eaf638b73f` (git)
  - affected: `f4f925dae7419fc7a10af539c073871927ce3a24 to before 2a892294b83f541115c94b0bb637f39bef187657` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.1`
  - unaffected: `before 6.1` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.145 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.97 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.40 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.5 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel perf subsystem on AMD processors with LBR v2 (affected from f4f925dae7419fc7a10af539c073871927ce3a24 until fixed in the listed stable releases, including 6.1 series fixes from 6.1.191, 6.6.145, 6.12.97 and 6.18.40) can include kernel addresses in user-only branch stack records. A local user who records branch stacks with perf can therefore see kernel addresses that should be hidden. Upgrade to a fixed kernel version: 6.1.191 or later in the 6.1 series, 6.6.145 or later, 6.12.97 or later, or 6.18.40 or later. The source gives no workaround.

Written 12 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 11th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 28 Aug 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-80602](https://www.cve.org/CVERecord?id=CVE-2026-80602)
- [NVD: CVE-2026-80602](https://nvd.nist.gov/vuln/detail/CVE-2026-80602)

### References from the CNA

- <https://git.kernel.org/stable/c/5adfec05e804ce4bd3368b75df5e5b7b40ee960b>
- <https://git.kernel.org/stable/c/5be478c1e08981ca91b34de310d7e2638171d9d8>
- <https://git.kernel.org/stable/c/208ecca408b1707ad86ea247d3d3e09d3606fc13>
- <https://git.kernel.org/stable/c/5ab0eba9c8819506bcb72348fd701f8a9006f95e>
- <https://git.kernel.org/stable/c/fb3b76b5ad2ebad63dd76f8b65b624eaf638b73f>
- <https://git.kernel.org/stable/c/2a892294b83f541115c94b0bb637f39bef187657>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-80602>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-80602/>. Everything for agents: <https://agentprime.io/llms.txt>.
