CVE-2023-52501
Linux Kernel Ring Buffer Off-by-Four Read Corruption
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.
INFO
Published Date :
March 2, 2024, 10:15 p.m.
Last Modified :
Jan. 13, 2025, 6:45 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
5.2
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-52501.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-52501 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-52501 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jan. 13, 2025
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Added CWE NIST CWE-125 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 5.10.198 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.134 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (including) 6.1.56 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (including) 6.5.6 *cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* Changed Reference Type https://git.kernel.org/stable/c/344f2f3e61a90f0150c754796ec9a17fcaeec03d No Types Assigned https://git.kernel.org/stable/c/344f2f3e61a90f0150c754796ec9a17fcaeec03d Patch Changed Reference Type https://git.kernel.org/stable/c/344f2f3e61a90f0150c754796ec9a17fcaeec03d No Types Assigned https://git.kernel.org/stable/c/344f2f3e61a90f0150c754796ec9a17fcaeec03d Patch Changed Reference Type https://git.kernel.org/stable/c/75fc9e99b3a71006720ad1e029db11a4b5c32d4a No Types Assigned https://git.kernel.org/stable/c/75fc9e99b3a71006720ad1e029db11a4b5c32d4a Patch Changed Reference Type https://git.kernel.org/stable/c/75fc9e99b3a71006720ad1e029db11a4b5c32d4a No Types Assigned https://git.kernel.org/stable/c/75fc9e99b3a71006720ad1e029db11a4b5c32d4a Patch Changed Reference Type https://git.kernel.org/stable/c/95a404bd60af6c4d9d8db01ad14fe8957ece31ca No Types Assigned https://git.kernel.org/stable/c/95a404bd60af6c4d9d8db01ad14fe8957ece31ca Patch Changed Reference Type https://git.kernel.org/stable/c/95a404bd60af6c4d9d8db01ad14fe8957ece31ca No Types Assigned https://git.kernel.org/stable/c/95a404bd60af6c4d9d8db01ad14fe8957ece31ca Patch Changed Reference Type https://git.kernel.org/stable/c/b08a4938229dbb530a35c41b83002a1457c6ff49 No Types Assigned https://git.kernel.org/stable/c/b08a4938229dbb530a35c41b83002a1457c6ff49 Patch Changed Reference Type https://git.kernel.org/stable/c/b08a4938229dbb530a35c41b83002a1457c6ff49 No Types Assigned https://git.kernel.org/stable/c/b08a4938229dbb530a35c41b83002a1457c6ff49 Patch Changed Reference Type https://git.kernel.org/stable/c/cee5151c5410e868826b8afecfb356f3799ebea3 No Types Assigned https://git.kernel.org/stable/c/cee5151c5410e868826b8afecfb356f3799ebea3 Patch Changed Reference Type https://git.kernel.org/stable/c/cee5151c5410e868826b8afecfb356f3799ebea3 No Types Assigned https://git.kernel.org/stable/c/cee5151c5410e868826b8afecfb356f3799ebea3 Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/344f2f3e61a90f0150c754796ec9a17fcaeec03d Added Reference https://git.kernel.org/stable/c/75fc9e99b3a71006720ad1e029db11a4b5c32d4a Added Reference https://git.kernel.org/stable/c/95a404bd60af6c4d9d8db01ad14fe8957ece31ca Added Reference https://git.kernel.org/stable/c/b08a4938229dbb530a35c41b83002a1457c6ff49 Added Reference https://git.kernel.org/stable/c/cee5151c5410e868826b8afecfb356f3799ebea3 -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 28, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 14, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Mar. 02, 2024
Action Type Old Value New Value Added 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. Added Reference Linux https://git.kernel.org/stable/c/cee5151c5410e868826b8afecfb356f3799ebea3 [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/344f2f3e61a90f0150c754796ec9a17fcaeec03d [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/b08a4938229dbb530a35c41b83002a1457c6ff49 [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/75fc9e99b3a71006720ad1e029db11a4b5c32d4a [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/95a404bd60af6c4d9d8db01ad14fe8957ece31ca [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-52501 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-52501
weaknesses.