LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53598: bus: mhi: host: Range check CHDBOFF and ERDBOFF

In the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: Range check CHDBOFF and ERDBOFF If the value read from the CHDBOFF and ERDBOFF registers is outside the range of the MHI register space then an invalid address might be computed which later causes a kernel panic. Range check the read value to prevent a crash due to bad data from the device.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can let bad data from an MHI device trigger a kernel panic. The practical business impact is system availability: affected hosts may crash if they use vulnerable MHI host code and receive out-of-range register values.

Executive priority

Treat as a targeted availability risk, not a confirmed active exploitation emergency. Patch during normal kernel maintenance, with higher priority for fleets using MHI hardware in operationally critical systems.

Technical view

The MHI host bus code read CHDBOFF and ERDBOFF register values without verifying they stayed within MHI register space. Out-of-range values could produce an invalid computed address and later panic the kernel. Stable kernel commits add range checks.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with MHI-capable hardware or drivers. The source bundle does not identify specific distributions, devices, or cloud images.

Exploitation context

The bundle does not show CISA KEV listing, public exploitation, CVSS, or exploit availability. Evidence supports a denial-of-service style kernel panic caused by bad device-provided register data.

Researcher notes

Focus analysis on MHI host register handling for CHDBOFF and ERDBOFF. The root issue is missing bounds validation before address computation. The source bundle does not provide exploit details, affected device models, CVSS, or CWE classification.

Mitigation direction

  • Apply a Linux kernel update containing the referenced stable fixes.
  • Check distribution or device vendor advisories for affected kernel package status.
  • Prioritize systems using MHI-connected modems or similar hardware.
  • If patching is delayed, reduce exposure to untrusted or unstable MHI devices.

Validation and detection

  • Inventory Linux kernel versions against vendor fixed packages or referenced stable commits.
  • Confirm whether deployed systems load or depend on MHI host drivers.
  • Review kernel logs for MHI-related panics or device initialization failures.
  • Track vendor advisories because no CVSS or product-specific matrix is provided.
Prepared
Confidence
medium
Sources
8

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-53598 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
7Source 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
LinuxLinux6cd330ae76ffd5c8f6294c423cabde7eeef1b40c, 6cd330ae76ffd5c8f6294c423cabde7eeef1b40c, 6cd330ae76ffd5c8f6294c423cabde7eeef1b40c, 6cd330ae76ffd5c8f6294c423cabde7eeef1b40c, 6cd330ae76ffd5c8f6294c423cabde7eeef1b40c, 6cd330ae76ffd5c8f6294c423cabde7eeef1b40cunaffected
LinuxLinux5.7, 0, 5.10.192, 5.15.112, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

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