CVE-2023-52501

Updated: 2025-01-13 22:52:35.63026

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.


Links NIST CIRCL RHEL Ubuntu

Severity

Severity Score
CVSS Version 2.x 0
CVSS Version 3.x HIGH 7.1000000000000005

Status

OS name Project name Version Score Severity Status Errata Last updated

Statement

AlmaLinux 9.2 ESU kernel 5.14.0 7.1 HIGH Released CLSA-2025:1743193221 2025-02-22 01:18:27
CentOS 6 ELS kernel 2.6.32 7.1 HIGH Not Vulnerable 2025-02-24 06:44:31
CentOS 8.4 ELS kernel 4.18.0 7.1 HIGH Not Vulnerable 2025-01-16 10:39:15
CentOS 8.5 ELS kernel 4.18.0 7.1 HIGH Not Vulnerable 2025-01-17 01:23:26
CloudLinux 6 ELS kernel 2.6.32 7.1 HIGH Not Vulnerable 2025-02-24 06:44:31
Oracle Linux 6 ELS kernel 2.6.32 7.1 HIGH Not Vulnerable 2025-02-24 06:44:31
Ubuntu 16.04 ELS linux-hwe 4.15.0 7.1 HIGH Not Vulnerable 2025-01-15 01:09:29
Ubuntu 16.04 ELS linux 4.4.0 7.1 HIGH Not Vulnerable 2025-01-16 10:39:16
Ubuntu 18.04 ELS linux 4.15.0 7.1 HIGH Not Vulnerable 2025-01-16 04:38:55