CVE-2026-23369
Race Condition in Linux i2c_i801 Driver Causes Kernel Panic
Publication date: 2026-03-25
Last updated on: 2026-04-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.7 |
| linux | linux_kernel | From 6.19 (inc) to 6.19.7 (exc) |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.17 (exc) |
| linux | linux_kernel | From 6.7.1 (inc) to 6.12.77 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's i2c: i801 driver. It involves a concurrency issue during system boot where multiple udev threads simultaneously collect device information and access the i801_acpi_io_handler. The first thread marks a certain area as reserved by ACPI, which leads to deregistration of that area. However, a second thread may attempt to access this now unregistered area before a proper check is made. Since the i2c_lock_bus function relies on this area containing lock operations to lock the bus, accessing it after deregistration causes a NULL pointer dereference, resulting in a kernel panic during boot.
How can this vulnerability impact me? :
The primary impact of this vulnerability is a kernel panic during system boot, which can cause the system to crash and become unavailable. This can lead to denial of service as the affected system may fail to start properly or become unstable, potentially disrupting operations that depend on the Linux kernel and the i2c: i801 driver.