Kernel memory corruption via unaligned MHI ring pointer
Published Feb 29, 2024 · Updated Jul 24, 2026
Out-of-bounds write in affected Linux kernel releases allows attackers to corrupt kernel memory or interrupt service via an MHI event-ring pointer. The is_valid_ring_ptr function in drivers/bus/mhi/host/main.c checks only whether the device-supplied address falls inside the ring buffer, then accepts it without verifying 128-bit struct mhi_ring_element alignment. Exploitation requires an active MHI controller and control of its event-ring read pointer; published outcomes are a service interruption or ring-buffer corruption, not demonstrated code execution.
Summary
What happened
Out-of-bounds write in affected Linux kernel releases allows attackers to corrupt kernel memory or interrupt service via an MHI event-ring pointer. The is_valid_ring_ptr function in drivers/bus/mhi/host/main.c checks only whether the device-supplied address falls inside the ring buffer, then accepts it without verifying 128-bit struct mhi_ring_element alignment. Exploitation requires an active MHI controller and control of its event-ring read pointer; published outcomes are a service interruption or ring-buffer corruption, not demonstrated code execution.
The record
- CVE
- CVE-2023-52494
- Published
- Feb 29, 2024
- Updated
- Jul 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- Jul 24, 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.10.36 <5.10.261
- Affected versionversion=5.11.20 <5.12
- Affected versionversion=5.12.3 <5.13
- Affected versionversion=5.13
- Affected versionversion=76879a980cd5ede4cb9a638999fb80d37bc09db5
- Affected versionversion=a1d2bd164c1c78f87968b7883964175ec41c32ae <76ed0c6f6418cec6efe6f65a0b91f84be80b72eb
- Affected versionversion=ec32332df7645e0ba463a08d483fe97665167071 <2df39ac8f813860f79782807c3f7acff40b3c551
- Affected versionversion=ec32332df7645e0ba463a08d483fe97665167071 <94991728c84f8df54fd9eec9b85855ef9057ea08
- Affected versionversion=ec32332df7645e0ba463a08d483fe97665167071 <a9ebfc405fe1be145f414eafadcbf09506082010
- Affected versionversion=ec32332df7645e0ba463a08d483fe97665167071 <ecf8320111822a1ae5d5fc512953eab46d543d0b
- Affected versionversion=ec32332df7645e0ba463a08d483fe97665167071 <eff9704f5332a13b08fbdbe0f84059c9e7051d5f
- Affected versionversion=fd5f40fc887485a8b9a6806a640a0d8e0ef1afb6
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.
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