Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-52494, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected a1d2bd164c1c78f87968b7883964175ec41c32ae – < 76ed0c6f6418cec6efe6f65a0b91f84be80b72eb
    • affected ec32332df7645e0ba463a08d483fe97665167071 – < 94991728c84f8df54fd9eec9b85855ef9057ea08
    • affected ec32332df7645e0ba463a08d483fe97665167071 – < 2df39ac8f813860f79782807c3f7acff40b3c551
    • affected ec32332df7645e0ba463a08d483fe97665167071 – < a9ebfc405fe1be145f414eafadcbf09506082010
    • affected ec32332df7645e0ba463a08d483fe97665167071 – < ecf8320111822a1ae5d5fc512953eab46d543d0b
    • affected ec32332df7645e0ba463a08d483fe97665167071 – < eff9704f5332a13b08fbdbe0f84059c9e7051d5f
    • affected fd5f40fc887485a8b9a6806a640a0d8e0ef1afb6
    • affected 76879a980cd5ede4cb9a638999fb80d37bc09db5
    • affected 5.10.36 – < 5.10.261
    • affected 5.11.20 – < 5.12
    • affected 5.12.3 – < 5.13
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.149 – ≤ 5.15.*
    • unaffected 6.1.76 – ≤ 6.1.*
    • unaffected 6.6.15 – ≤ 6.6.*
    • unaffected 6.7.3 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52494 badge
[![CVE-2023-52494](https://cveledger.app/badge/CVE-2023-52494.svg)](https://cveledger.app/cve/CVE-2023-52494)

Record last updated .