Local denial of service via uncleared overflow status
Published May 2, 2025 · Updated May 11, 2026
Improper status handling in the AMD PMU code in affected Linux kernels allows local users to interrupt service via performance events. In amd_pmu_v2_handle_irq(), a zero return from x86_perf_event_set_period() continues the loop after incrementing handled but before clearing the corresponding unhandled-overflow bit. Low-privileged local access and AMD PMU v2 overflow handling are required; repeated stale status processing can destabilize the kernel and deny availability.
Summary
What happened
Improper status handling in the AMD PMU code in affected Linux kernels allows local users to interrupt service via performance events. In amd_pmu_v2_handle_irq(), a zero return from x86_perf_event_set_period() continues the loop after incrementing handled but before clearing the corresponding unhandled-overflow bit. Low-privileged local access and AMD PMU v2 overflow handling are required; repeated stale status processing can destabilize the kernel and deny availability.
The record
- CVE
- CVE-2023-53073
- Published
- May 2, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.19
- Affected versionversion=7685665c390dc68c2d9a74e8445f41494cc8f6cf <263f5ecaf7080513efc248ec739b6d9e00f4129f
- Affected versionversion=7685665c390dc68c2d9a74e8445f41494cc8f6cf <9d4c7b1f12e101d6d6253092588b127416ddfb6c
- Affected versionversion=7685665c390dc68c2d9a74e8445f41494cc8f6cf <ab33a8f7649b0324639a336e1081aaea51a4523e
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
No public exploit references are available in this record.
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