CVE-2024-35977

published 20 May 2024 · updated 11 May 2026

platform/chrome: cros_ec_uart: properly fix race condition

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5e700b384ec13f5bcac9855cb28fcc674f1d3593, Kernel 9e9bb74a93b7daa32313ccaefd0edc529d40daf8 and Kernel cfd758041d8b79aa8c3f811b6bd6105379f2f702.

In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_uart: properly fix race condition The cros_ec_uart_probe() function calls devm_serdev_device_open() before it calls serdev_device_set_client_ops(). This can trigger a NULL pointer dereference: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... Call Trace: <TASK> ... ? ttyport_receive_buf A simplified version of crashing code is as follows: static inline size_t serdev_controller_receive_buf(struct serdev_controller *ctrl, const u8 *data, size_t count) { struct serdev_device *serdev = ctrl->serdev; if (!serdev || !serdev->ops->receive_buf) // CRASH! return 0; return serdev->ops->receive_buf(serdev, data, count); } It assumes that if SERPORT_ACTIVE is set and serdev exists, serdev->ops will also exist. This conflicts with the existing cros_ec_uart_probe() logic, as it first calls devm_serdev_device_open() (which sets SERPORT_ACTIVE), and only later sets serdev->ops via serdev_device_set_client_ops(). Commit 01f95d42b8f4 ("platform/chrome: cros_ec_uart: fix race condition") attempted to fix a similar race condition, but while doing so, made the window of error for this race condition to happen much wider. Attempt to fix the race condition again, making sure we fully setup before calling devm_serdev_device_open().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.3, >=01f95d42b8f4e88f20d68791b0a85dbb9e3d1ac9 <5e700b384ec13f5bcac9855cb28fcc674f1d3593, >=01f95d42b8f4e88f20d68791b0a85dbb9e3d1ac9 <9e9bb74a93b7daa32313ccaefd0edc529d40daf8, >=01f95d42b8f4e88f20d68791b0a85dbb9e3d1ac9 <cfd758041d8b79aa8c3f811b6bd6105379f2f7025e700b384ec13f5bcac9855cb28fcc674f1d3593, 9e9bb74a93b7daa32313ccaefd0edc529d40daf8, cfd758041d8b79aa8c3f811b6bd6105379f2f702

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-35977 severity on Zeptric[![CVE-2024-35977](https://zeptric.io/badge/cve/CVE-2024-35977.svg)](https://zeptric.io/cve/CVE-2024-35977)