LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52494: bus: mhi: host: Add alignment check for event ring read pointer

In the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: Add alignment check for event ring read pointer Though we do check the event ring read pointer by "is_valid_ring_ptr" to make sure it is in the buffer range, but there is another risk the pointer may be not aligned. Since we are expecting event ring elements are 128 bits(struct mhi_ring_element) aligned, an unaligned read pointer could lead to multiple issues like DoS or ring buffer memory corruption. So add a alignment check for event ring read pointer.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux MHI host driver could let an improperly aligned event-ring pointer cause a system crash or corrupt kernel memory. Exposure depends on whether the system uses the MHI host driver and runs an affected kernel. The supplied sources do not establish severity or real-world exploitation.

Executive priority

Treat as a targeted kernel-maintenance issue rather than an enterprise-wide emergency based on current evidence. Promptly identify MHI-dependent systems and patch them through supported vendor channels. Escalate priority for operationally critical devices where a kernel crash or memory corruption would materially disrupt service.

Technical view

The MHI host driver validated that an event-ring read pointer was within the ring buffer but did not verify 128-bit alignment required by struct mhi_ring_element. Processing an unaligned pointer could cause denial of service or ring-buffer memory corruption. Linux stable fixes add the missing alignment check.

Likely exposure

Potential exposure is limited to Linux systems using the MHI host driver on affected builds. The supplied record lists affected versions including 5.13, 5.10.261, 5.15.149, 6.1.76, 6.6.15, 6.7.3, and 6.8, but organizations should obtain distribution-specific version mappings because kernel backports can differ.

Exploitation context

The record is not in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. They identify possible denial of service and ring-buffer memory corruption, but do not establish attacker prerequisites, reachability, or demonstrated impact.

Researcher notes

The source bundle does not provide CVSS, CWE classification, exploit prerequisites, or proof of code execution. The described outcomes are denial of service or ring-buffer memory corruption. Version data contains branch-specific commits and unusual entries, so exposure decisions should rely on vendor backport confirmation rather than numeric version comparison alone.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable Linux stable fix.
  • Consult the Linux distribution or device vendor for backport and package-version guidance.
  • Prioritize systems that actively use MHI-connected hardware or the MHI host driver.
  • Apply normal kernel-update restart procedures required by the relevant platform vendor.

Validation and detection

  • Inventory running kernel versions and distribution package revisions.
  • Determine whether the MHI host driver is present and used on each system.
  • Verify the installed kernel includes the applicable cited stable commit or vendor backport.
  • Review vendor advisories for corrected package versions and remaining affected branches.
  • After updating, confirm the corrected kernel is running.
Prepared
Confidence
medium
Sources
8

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-52494 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
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa1d2bd164c1c78f87968b7883964175ec41c32ae, ec32332df7645e0ba463a08d483fe97665167071, ec32332df7645e0ba463a08d483fe97665167071, ec32332df7645e0ba463a08d483fe97665167071, ec32332df7645e0ba463a08d483fe97665167071, ec32332df7645e0ba463a08d483fe97665167071, fd5f40fc887485a8b9a6806a640a0d8e0ef1afb6, 76879a980cd5ede4cb9a638999fb80d37bc09db5, 5.10.36, 5.11.20, 5.12.3unaffected
LinuxLinux5.13, 0, 5.10.261, 5.15.149, 6.1.76, 6.6.15, 6.7.3, 6.8affected
Weakness

CWE details

No CWE listed

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