CVE-2026-72237perf/x86/amd/brs: Fix kernel address leakage
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd/brs: Fix kernel address leakage A user-only branch stack can contain branches that originate from the kernel. As a result, kernel addresses are exposed to user space even when PERF_SAMPLE_BRANCH_USER is requested. On AMD processors supporting X86_FEATURE_BRS (Zen 3 only), perf can still report entries such as SYSRET/interrupt returns for which the branch-from addresses are in the kernel. E.g. $ perf record -j any,u -c 4000 -e branch-brs -o - -- \ perf bench syscall basic --loop 1000 | \ perf script -i - -F brstack|tr ' ' '\n'| \ grep -E '0x[89a-f][0-9a-f]{15}' ... 0xffffffff810001c4/0x72e2e32955eb/-/-/-/0//- 0xffffffff810001c4/0x72e2d94a9821/-/-/-/0//- 0xffffffff810001c4/0x72e2d94ffa1b/-/-/-/0//- ... BRS provides no hardware branch filtering, so privilege level filtering is performed entirely in software. However, amd_brs_match_plm() only validates the branch-to address against the requested privilege levels. For branches from the kernel to user space, the branch-from address is left unchecked and is leaked. Extend the software filter to also validate the branch-from address, so that any branch record whose branch-from address is in the kernel is dropped when PERF_SAMPLE_BRANCH_USER is requested.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 4 days later
· 4 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 – < 4f949bc3913a6e3ce3b8574ac6ed1da8ec7a5ad1
- affected 8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 – < ac44b4a3d6137489f8fa2e794b12e849c6b22eaa
- affected 8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 – < 90843d00dbc61220b66408ea0d8775cae9e51f70
- affected 8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 – < 046f6244da9b68e463a849b21446b9424e531491
- affected 8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 – < 2e706be56f418718bb3ae66c0aa94f9b61150e6d
- affected 8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 – < 47915e855fb38b42133e31ba917d99565f862154
- affected 5.19
- unaffected < 5.19
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/4f949bc3913a6e3ce3b8574ac6ed1da8ec7a5ad1 (opens in a new tab)
- https://git.kernel.org/stable/c/ac44b4a3d6137489f8fa2e794b12e849c6b22eaa (opens in a new tab)
- https://git.kernel.org/stable/c/90843d00dbc61220b66408ea0d8775cae9e51f70 (opens in a new tab)
- https://git.kernel.org/stable/c/046f6244da9b68e463a849b21446b9424e531491 (opens in a new tab)
- https://git.kernel.org/stable/c/2e706be56f418718bb3ae66c0aa94f9b61150e6d (opens in a new tab)
- https://git.kernel.org/stable/c/47915e855fb38b42133e31ba917d99565f862154 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59136 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72237)Record last updated .