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-52501ring-buffer: Do not attempt to read past "commit"

Description

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Do not attempt to read past "commit" When iterating over the ring buffer while the ring buffer is active, the writer can corrupt the reader. There's barriers to help detect this and handle it, but that code missed the case where the last event was at the very end of the page and has only 4 bytes left. The checks to detect the corruption by the writer to reads needs to see the length of the event. If the length in the first 4 bytes is zero then the length is stored in the second 4 bytes. But if the writer is in the process of updating that code, there's a small window where the length in the first 4 bytes could be zero even though the length is only 4 bytes. That will cause rb_event_length() to read the next 4 bytes which could happen to be off the allocated page. To protect against this, fail immediately if the next event pointer is less than 8 bytes from the end of the commit (last byte of data), as all events must be a minimum of 8 bytes anyway.

Timeline

  1. ID reserved

    By Linux

  2. · 11 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-52501, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (17 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.1.

Affected products

  • Linux · Linux

    • affected 785888c544e0433f601df18ff98a3215b380b9c3 – < cee5151c5410e868826b8afecfb356f3799ebea3
    • affected 785888c544e0433f601df18ff98a3215b380b9c3 – < 344f2f3e61a90f0150c754796ec9a17fcaeec03d
    • affected 785888c544e0433f601df18ff98a3215b380b9c3 – < b08a4938229dbb530a35c41b83002a1457c6ff49
    • affected 785888c544e0433f601df18ff98a3215b380b9c3 – < 75fc9e99b3a71006720ad1e029db11a4b5c32d4a
    • affected 785888c544e0433f601df18ff98a3215b380b9c3 – < 95a404bd60af6c4d9d8db01ad14fe8957ece31ca
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.198 – ≤ 5.10.*
    • unaffected 5.15.134 – ≤ 5.15.*
    • unaffected 6.1.56 – ≤ 6.1.*
    • unaffected 6.5.6 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .