CVE-2025-38142
What it is
In the Linux kernel, the following vulnerability has been resolved: hwmon: (asus-ec-sensors) check sensor index in read_string() Prevent a potential invalid memory access when the requested sensor is not found. find_ec_sensor_index() may return a negative value (e.g. -ENOENT), but its result was used without checking, which could lead to undefined behavior when passed to get_sensor_info(). Add a proper check to return -EINVAL if sensor_index is negative. Found by Linux Verification Center (linuxtesting.org) with SVACE. [groeck: Return error code returned from find_ec_sensor_index]
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Analyzed
Affected
- Linux Kernel < 6.1.142
- Linux Kernel < 6.6.94
- Linux Kernel < 6.12.34
- Linux Kernel < 6.15.3
- Debian Linux 11.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38142.md and follow it. Check whether this project is affected by CVE-2025-38142. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/19bd9cde38dd4ca1771aed7afba623e7f4247c8e
- https://git.kernel.org/stable/c/25be318324563c63cbd9cb53186203a08d2f83a1
- https://git.kernel.org/stable/c/4e9e45746b861ebd54c03ef301da2cb8fc990536
- https://git.kernel.org/stable/c/6bf529ce84dccc0074dbc704e70aee4aa545057e
- https://git.kernel.org/stable/c/7eeb3df6f07a886bdfd52757ede127a59a8784dc
References
- https://git.kernel.org/stable/c/19bd9cde38dd4ca1771aed7afba623e7f4247c8e
- https://git.kernel.org/stable/c/25be318324563c63cbd9cb53186203a08d2f83a1
- https://git.kernel.org/stable/c/4e9e45746b861ebd54c03ef301da2cb8fc990536
- https://git.kernel.org/stable/c/6bf529ce84dccc0074dbc704e70aee4aa545057e
- https://git.kernel.org/stable/c/7eeb3df6f07a886bdfd52757ede127a59a8784dc
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html