CVE-2026-31740
Race Condition in Linux Kernel rz-mtu3-cnt Counter Driver
Publication date: 2026-05-01
Last updated on: 2026-05-01
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's handling of the rz-mtu3 counter driver and PWM driver. Both drivers use hardware channels 1 and 2 and assign their own struct device pointer to the same dev member within the shared struct rz_mtu3_channel. Because these assignments race against each other, the dev member may end up pointing to the wrong device instance.
As a result, the counter sub-driver might perform runtime power management (PM) actions on the wrong device, depending on the order in which the drivers are probed. The fix involves using the parent pointer of the counter, which is correctly assigned during probe, instead of the shared dev member.
How can this vulnerability impact me? :
This vulnerability can cause the counter sub-driver to perform runtime power management operations on an incorrect device due to the dev member pointing to the wrong struct device instance. This mismanagement could lead to unexpected device behavior, potential device malfunctions, or instability in the system's power management.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is related to the Linux kernel's rz-mtu3 counter driver and PWM driver sharing and overwriting the dev member in struct rz_mtu3_channel, causing incorrect runtime PM actions.
To mitigate this vulnerability, update your Linux kernel to a version where this issue is fixed. The fix involves using the parent pointer of the counter, assigned during probe, instead of the shared dev member inside struct rz_mtu3_channel.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
There is no information available in the provided context or resources about how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.