LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53073: perf/x86/amd/core: Always clear status for idx

In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd/core: Always clear status for idx The variable 'status' (which contains the unhandled overflow bits) is not being properly masked in some cases, displaying the following warning: WARNING: CPU: 156 PID: 475601 at arch/x86/events/amd/core.c:972 amd_pmu_v2_handle_irq+0x216/0x270 This seems to be happening because the loop is being continued before the status bit being unset, in case x86_perf_event_set_period() returns 0. This is also causing an inconsistency because the "handled" counter is incremented, but the status bit is not cleaned. Move the bit cleaning together above, together when the "handled" counter is incremented.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in AMD performance monitoring code. A status bit may not be cleared correctly, producing kernel warnings and inconsistent handling of performance counter overflows. The public record does not provide a CVSS score or evidence of exploitation.

Executive priority

Treat this as a normal kernel maintenance item unless affected AMD Linux systems are business-critical or showing kernel warnings. Prioritize verified affected systems, but current public evidence does not support emergency response.

Technical view

In arch/x86/events/amd/core.c, amd_pmu_v2_handle_irq can continue before clearing an overflow status bit when x86_perf_event_set_period() returns 0. The fix moves status-bit clearing alongside the handled counter increment. The issue is tied to Linux perf on x86 AMD PMU paths.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions in the AMD x86 perf subsystem path. The CVE record lists Linux 5.19, 6.1.22, 6.2.9, and 6.3 as affected, with stable kernel commits referenced as fixes.

Exploitation context

No active exploitation is indicated. The source bundle marks KEV as false, and the public description describes a kernel warning and accounting inconsistency rather than an exploitation technique.

Researcher notes

The record lacks CVSS, CWE, and exploitability detail. Analysis should stay close to the kernel commit behavior: improper clearing of unhandled overflow status bits in the AMD perf interrupt handler. Avoid assuming privilege escalation or remote attack exposure without additional vendor evidence.

Mitigation direction

  • Check whether deployed kernels match the affected Linux versions or unfixed source commit lineage.
  • Apply vendor or distribution kernel updates that include the referenced stable fixes.
  • If using custom kernels, confirm the relevant stable commits are backported.
  • Monitor vendor advisories for product-specific affected ranges and update instructions.

Validation and detection

  • Confirm kernel package version and changelog include the referenced stable fix commits.
  • For source builds, compare arch/x86/events/amd/core.c with the fixed stable commits.
  • Review kernel logs for the cited amd_pmu_v2_handle_irq warning.
  • Document AMD x86 systems using perf or PMU monitoring for prioritization.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53073 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7685665c390dc68c2d9a74e8445f41494cc8f6cf, 7685665c390dc68c2d9a74e8445f41494cc8f6cf, 7685665c390dc68c2d9a74e8445f41494cc8f6cfunaffected
LinuxLinux5.19, 0, 6.1.22, 6.2.9, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.