NVD / CVE Program· CNA Linux

CVE-2023-52501: ring-buffer: Do not attempt to read past "commit"

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 344f2f3e61a90f0150c754796ec9a17fcaeec03d, 75fc9e99b3a71006720ad1e029db11a4b5c32d4a, 95a404bd60af6c4d9d8db01ad14fe8957ece31ca.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 344f2f3e61a90f0150c754796ec9a17fcaeec03d, 75fc9e99b3a71006720ad1e029db11a4b5c32d4a, 95a404bd60af6c4d9d8db01ad14fe8957ece31ca or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.1 · v3.1—No exploit Fix available

Memory safety

BDU:2024-07836

Published: Mar 2, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 16th percentile
CWE: CWE-125

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernelbefore 5.10.198
linux linux kernel5.11 and later · before 5.15.134
linux linux kernel5.16 and later · up to 6.1.56 inclusive
linux linux kernel6.2 and later · up to 6.5.6 inclusive
linux linux kernel6.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5.7affected
- 785888c544e0433f601df18ff98a3215b380b9c3 and later · before cee5151c5410e868826b8afecfb356f3799ebea3affected · git
- 785888c544e0433f601df18ff98a3215b380b9c3 and later · before 344f2f3e61a90f0150c754796ec9a17fcaeec03daffected · git
- 785888c544e0433f601df18ff98a3215b380b9c3 and later · before b08a4938229dbb530a35c41b83002a1457c6ff49affected · git
- 785888c544e0433f601df18ff98a3215b380b9c3 and later · before 75fc9e99b3a71006720ad1e029db11a4b5c32d4aaffected · git
- 785888c544e0433f601df18ff98a3215b380b9c3 and later · before 95a404bd60af6c4d9d8db01ad14fe8957ece31caaffected · git
- before 5.7not affected · semver
- 5.10.198 and later · up to and including 5.10.*not affected · semver
- 5.15.134 and later · up to and including 5.15.*not affected · semver
- 6.1.56 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.64-1	6.1.64-1
Debian:13	linux	before 6.5.6-1	6.5.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2023-52499Mar 2, 2024 · powerpc/47x: Fix 47x syscall return crash
22Monitor
← EarlierCVE-2023-52500Mar 2, 2024 · scsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command
22Monitor
Later →CVE-2023-52502Mar 2, 2024 · net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()
35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	344f2f3e61a90f0150c754796ec9a17fcaeec03d	Vendor (CNA)
Linux Linux	75fc9e99b3a71006720ad1e029db11a4b5c32d4a	Vendor (CNA)
Linux Linux	95a404bd60af6c4d9d8db01ad14fe8957ece31ca	Vendor (CNA)
Linux Linux	b08a4938229dbb530a35c41b83002a1457c6ff49	Vendor (CNA)
Linux Linux	cee5151c5410e868826b8afecfb356f3799ebea3	Vendor (CNA)
debian:linux	6.1.64-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).