CVE-2023-53646: drm/i915/perf: add sentinel to xehp_oa_b_counters
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/perf: add sentinel to xehp_oa_b_counters
Arrays passed to reg_in_range_table should end with empty record.
The patch solves KASAN detected bug with signature:
BUG: KASAN: global-out-of-bounds in xehp_is_valid_b_counter_addr+0x2c7/0x350 [i915]
Read of size 4 at addr ffffffffa1555d90 by task perf/1518
CPU: 4 PID: 1518 Comm: perf Tainted: G U 6.4.0-kasan_438-g3303d06107f3+ #1
Hardware name: Intel Corporation Meteor Lake Client Platform/MTL-P DDR5 SODIMM SBS RVP, BIOS MTLPFWI1.R00.3223.D80.2305311348 05/31/2023
Call Trace:
<TASK>
...
xehp_is_valid_b_counter_addr+0x2c7/0x350 [i915]
(cherry picked from commit 2f42c5afb34b5696cf5fe79e744f99be9b218798)
Security readout for executives and security teams
Plain-English summary
CVE-2023-53646 is a Linux kernel i915 graphics/performance bug where a kernel table lacked an ending marker, causing code to read past a global array. The public record shows a KASAN out-of-bounds read report, not active attacks. Business urgency depends on whether affected Linux kernels and Intel i915 graphics paths exist in your estate.
Executive priority
Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize affected Linux endpoints or specialized systems using Intel graphics/perf paths, and roll fixes into the next supported kernel update cycle unless vendor advisories raise severity.
Technical view
The issue is in drm/i915/perf: arrays passed to reg_in_range_table should terminate with an empty record. Without that sentinel, xehp_is_valid_b_counter_addr can perform a global out-of-bounds read. The source cites KASAN on a 6.4.0 KASAN build and links stable kernel fixes.
Likely exposure
Potential exposure is Linux systems running affected kernel versions identified in the CVE data, especially where the i915 driver and related perf functionality are present. The source bundle does not define distribution package names, exact hardware scope, or cloud image exposure.
Exploitation context
No KEV listing is present, and the provided sources do not claim active exploitation, public exploit availability, or remote exploitability. Evidence is limited to a kernel KASAN report and stable commits resolving the defect.
Researcher notes
The CVE record has no CVSS, CWE, or exploitability detail. The affected-version data appears kernel-focused and should be mapped carefully to distribution backports. Avoid assuming impact beyond the documented global out-of-bounds read in i915 perf handling.
Mitigation direction
Identify systems running affected Linux kernel versions from the CVE record.
Check Linux distribution and kernel vendor advisories for packaged fixed kernels.
Prioritize kernels containing stable commits 21d92025e806 or 785b3f667b4b.
Update affected kernels through normal vendor-supported channels.
If patch timing is constrained, review vendor guidance for temporary mitigations.
Validation and detection
Inventory kernel versions across servers, workstations, and images.
Check whether Intel i915 driver usage exists on in-scope systems.
Confirm deployed kernels include the referenced stable commits or vendor backports.
Review kernel and KASAN logs for matching i915 perf out-of-bounds reports.
Track remediation evidence through package versions, reboot status, and asset records.
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-53646 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 7, 2025, 15:19 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.