VulnerabilityPublished 15 Aug 2026Updated 21 Oct 2026

CVE-2026-72325: Linux kernel · perf/x86/amd/core: Avoid enabling BRS from the SVM reload path

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in e9b1a7411a667539c2f55e720bbb5f623b526a32 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in e9b1a7411a667539c2f55e720bbb5f623b526a32, 46d0fd8535edce31f15e48d2de1bdee39a4850e5, 7cc438c99bba324a0562b1bafa747b10f7e251df +2

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bae19fdd7e9e759580ac4693d2df3bc23ab415d7, < e9b1a7411a667539c2f55e720bbb5f623b526a32	Fixed in e9b1a7411a667539c2f55e720bbb5f623b526a32
LinuxLinux	Affected ≥ bae19fdd7e9e759580ac4693d2df3bc23ab415d7, < 46d0fd8535edce31f15e48d2de1bdee39a4850e5	Fixed in 46d0fd8535edce31f15e48d2de1bdee39a4850e5
LinuxLinux	Affected ≥ bae19fdd7e9e759580ac4693d2df3bc23ab415d7, < 7cc438c99bba324a0562b1bafa747b10f7e251df	Fixed in 7cc438c99bba324a0562b1bafa747b10f7e251df
LinuxLinux	Affected ≥ bae19fdd7e9e759580ac4693d2df3bc23ab415d7, < 07c60dda9c059c09f83d42a3ebda2e7cc1cf3bc2	Fixed in 07c60dda9c059c09f83d42a3ebda2e7cc1cf3bc2
LinuxLinux	Affected ≥ bae19fdd7e9e759580ac4693d2df3bc23ab415d7, < 3b0aa139ba09a5b73c0f300e652076232f869f68	Fixed in 3b0aa139ba09a5b73c0f300e652076232f869f68
LinuxLinux	Affected =5.19	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path Branch Sampling (BRS) and Last Branch Record (LBR) are mutually exclusive hardware features, and users of both are tracked via cpuc->lbr_users. When SVM is toggled on a CPU, the host perf events are reprogrammed to update the HostOnly filter bit (set when virtualization is enabled, cleared when it is disabled). On PerfMonV2-capable processors, this reprogramming is performed by calling amd_pmu_enable_all() to rewrite the event selectors. However, amd_pmu_enable_all() also calls amd_brs_enable_all(), which enables BRS whenever cpuc->lbr_users > 0. Having active LBR events satisfies this gating on processors that have LBR but not BRS. The kernel then tries to set the BRS enable bit in DebugExtnCfg (MSR 0xc000010f). Since that bit is deprecated on such hardware, the write results in a #GP: Call Trace: <IRQ> amd_pmu_enable_all+0x1d/0x90 amd_pmu_disable_virt+0x62/0xb0 kvm_arch_disable_virtualization_cpu+0xa/0x40 [kvm] hardware_disable_nolock+0x1a/0x30 [kvm] __flush_smp_call_function_queue+0x9b/0x410 __sysvec_call_function+0x18/0xc0 sysvec_call_function+0x69/0x90 </IRQ> <TASK> asm_sysvec_call_function+0x16/0x20 RIP: 0010:cpuidle_enter_state+0xc4/0x450 ? cpuidle_enter_state+0xb7/0x450 cpuidle_enter+0x29/0x40 cpuidle_idle_call+0xf5/0x160 do_idle+0x7b/0xe0 cpu_startup_entry+0x26/0x30 start_secondary+0x115/0x140 secondary_startup_64_no_verify+0x194/0x19b </TASK> Fix this by ensuring that BRS is not enabled from the event selector reprogramming path even when cpuc->lbr_users > 0.

References

Community reviews

Loading reviews…