CVE-2026-22986
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-04-22
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.9 (inc) to 6.18.6 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for kernel crash messages related to the race condition in gpiolib, such as 'Unable to handle kernel paging request' and 'Internal error: Oops' with call traces involving __srcu_read_lock, gpio_name_to_desc, and gpiochip_add_data_with_key. You can check the kernel logs using commands like 'dmesg | grep -i gpio' or 'journalctl -k | grep -i gpio' to look for these error patterns.
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's GPIO library (gpiolib). It occurs when two drivers call gpiochip_add_data_with_key() simultaneously. One driver may be traversing a srcu-protected list while the other is adding a device to that list without proper synchronization. This creates a window where one instance accesses uninitialized data, specifically the gdev->srcu field, leading to a kernel crash due to invalid memory access.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a race condition when handling GPIO devices. Such crashes can lead to system instability, denial of service, or unexpected reboots, impacting the reliability and availability of systems running affected Linux kernels.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this race condition in gpiolib has been fixed. The fix moves the initialization code for gdev fields before adding it to gpio_devices, preventing the race condition. Until an update is applied, avoid running multiple drivers that call gpiochip_add_data_with_key() concurrently if possible.