CVE-2025-22084: w1: fix NULL pointer dereference in probe
In the Linux kernel, the following vulnerability has been resolved:
w1: fix NULL pointer dereference in probe
The w1uartprobe() function calls w1uartserdevopen() (which includes devmserdevdeviceopen()) before setting the client ops via serdevdevicesetclientops(). This ordering can trigger a NULL pointer dereference in the serdev controller's receivebuf handler, as it assumes serdev->ops is valid when SERPORTACTIVE is set.
This is similar to the issue fixed in commit 5e700b384ec1 ("platform/chrome: crosecuart: properly fix race condition") where devmserdevdeviceopen() was called before fully initializing the device.
Fix the race by ensuring client ops are set before enabling the port via w1uartserdevopen().
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-22084?
CVE-2025-22084 is classified with a severity rating that indicates a potential for denial-of-service due to NULL pointer dereference.
How do I fix CVE-2025-22084?
To fix CVE-2025-22084, update your Linux kernel to the patched version that addresses the NULL pointer dereference issue.
Which versions of the Linux kernel are affected by CVE-2025-22084?
CVE-2025-22084 affects specific versions of the Linux kernel prior to the release of the security update that resolves this issue.
What are the implications of CVE-2025-22084 for Linux users?
The implications of CVE-2025-22084 for Linux users include potential system crashes and instability if the vulnerability is exploited.
Can CVE-2025-22084 be exploited remotely?
CVE-2025-22084 does not appear to be directly exploitable remotely but could lead to local denial-of-service conditions.