perf/x86/amd/brs: Fix kernel address leakage
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ac44b4a3d6137489f8fa2e794b12e849c6b22eaa, Kernel 046f6244da9b68e463a849b21446b9424e531491, Kernel 2e706be56f418718bb3ae66c0aa94f9b61150e6d and 8 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 <ac44b4a3d6137489f8fa2e794b12e849c6b22eaa, >=8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 <046f6244da9b68e463a849b21446b9424e531491, >=8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 <2e706be56f418718bb3ae66c0aa94f9b61150e6d, >=8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 <47915e855fb38b42133e31ba917d99565f862154, >=8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 <4f949bc3913a6e3ce3b8574ac6ed1da8ec7a5ad1, >=8910075d61a37e5b0d82e6c83ed9a0a31fe9ea08 <90843d00dbc61220b66408ea0d8775cae9e51f70, =5.19 | ac44b4a3d6137489f8fa2e794b12e849c6b22eaa, 046f6244da9b68e463a849b21446b9424e531491, 2e706be56f418718bb3ae66c0aa94f9b61150e6d, 47915e855fb38b42133e31ba917d99565f862154, 4f949bc3913a6e3ce3b8574ac6ed1da8ec7a5ad1, 90843d00dbc61220b66408ea0d8775cae9e51f70 |
| linux-kernel: Kernel | >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=5.19.0 <6.1.183 | 6.18.40, 7.1.5, 6.6.145, 6.12.97, 6.1.183 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket