CVE-2023-53612

In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Simplify platform device handling Coretemp's platform driver is unconventional. All the real work is done globally by the initcall and CPU hotplug notifiers, while the "driver" effectively just wraps an allocation and the registration of the hwmon interface in a long-winded round-trip through the driver core. The whole logic of dynamically creating and destroying platform devices to bring the interfaces up and down is error prone, since it assumes platform_device_add() will synchronously bind the driver and set drvdata before it returns, thus results in a NULL dereference if drivers_autoprobe is turned off for the platform bus. Furthermore, the unusual approach of doing that from within a CPU hotplug notifier, already commented in the code that it deadlocks suspend, also causes lockdep issues for other drivers or subsystems which may want to legitimately register a CPU hotplug notifier from a platform bus notifier. All of these issues can be solved by ripping this unusual behaviour out completely, simply tying the platform devices to the lifetime of the module itself, and directly managing the hwmon interfaces from the hotplug notifiers. There is a slight user-visible change in that /sys/bus/platform/drivers/coretemp will no longer appear, and /sys/devices/platform/coretemp.n will remain present if package n is hotplugged off, but hwmon users should really only be looking for the presence of the hwmon interfaces, whose behaviour remains unchanged.

• CWE-476

• https://git.kernel.org/stable/c/4000384684f612b3645a944f6acde0e65ac370b8Patch
• https://git.kernel.org/stable/c/52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03fePatch
• https://git.kernel.org/stable/c/5735878a7b7db7e9ce731cb36cec298a9de67549Patch
• https://git.kernel.org/stable/c/6d03bbff456befeccdd4d663177c4d6c75d0c4ffPatch
• https://git.kernel.org/stable/c/8fcdbc4bc01365f4b10fed7db544a3149e3054fdPatch
• https://git.kernel.org/stable/c/c57a8d14d7880521150ee801d53a0a64fdffd9c8Patch

Published

Oct 4, 2025

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2023-53607In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53608In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2023-53609In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-5361Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2023-53610In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53611In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53613In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2023-53614In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2023-53615In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2023-53616In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2023-53617In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2023-53618In the Linux kernel, the following vulnerability has been re…5.5