CVE-2023-53612: hwmon: (coretemp) Simplify platform device handling
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4000384684f612b3645a944f6acde0e65ac370b8, 52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03fe, 5735878a7b7db7e9ce731cb36cec298a9de67549.
Low priority for now. Upgrade to Linux Linux 4000384684f612b3645a944f6acde0e65ac370b8, 52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03fe, 5735878a7b7db7e9ce731cb36cec298a9de67549 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 4, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.10 and later · before 5.4.235
- linux linux kernel5.5 and later · before 5.10.173
- linux linux kernel5.11 and later · before 5.15.99
- linux linux kernel5.16 and later · before 6.1.16
- linux linux kernel6.2 and later · before 6.2.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.10affected
- e1b370b64031a01bb0c4158ce250073a88921fe1 and later · before 4000384684f612b3645a944f6acde0e65ac370b8affected · git
- e1b370b64031a01bb0c4158ce250073a88921fe1 and later · before 5735878a7b7db7e9ce731cb36cec298a9de67549affected · git
- e1b370b64031a01bb0c4158ce250073a88921fe1 and later · before 52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03feaffected · git
- e1b370b64031a01bb0c4158ce250073a88921fe1 and later · before 8fcdbc4bc01365f4b10fed7db544a3149e3054fdaffected · git
- e1b370b64031a01bb0c4158ce250073a88921fe1 and later · before c57a8d14d7880521150ee801d53a0a64fdffd9c8affected · git
- e1b370b64031a01bb0c4158ce250073a88921fe1 and later · before 6d03bbff456befeccdd4d663177c4d6c75d0c4ffaffected · git
- before 4.10not affected · semver
- 5.4.235 and later · up to and including 5.4.*not affected · semver
- 5.10.173 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.20-1 | 6.1.20-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53609Oct 4, 2025 · scsi: Revert "scsi: core: Do not increase scsi_device's iorequest_cnt if dispatch failed"22Monitor
- ← EarlierCVE-2023-53610Oct 4, 2025 · irqchip: Fix refcount leak in platform_irqchip_probe22Monitor
- Later →CVE-2022-50509Oct 7, 2025 · media: coda: Add check for kmalloc22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4000384684f612b3645a944f6acde0e65ac370b8 | Vendor (CNA) |
| Linux Linux | 52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03fe | Vendor (CNA) |
| Linux Linux | 5735878a7b7db7e9ce731cb36cec298a9de67549 | Vendor (CNA) |
| Linux Linux | 6d03bbff456befeccdd4d663177c4d6c75d0c4ff | Vendor (CNA) |
| Linux Linux | 8fcdbc4bc01365f4b10fed7db544a3149e3054fd | Vendor (CNA) |
| Linux Linux | c57a8d14d7880521150ee801d53a0a64fdffd9c8 | Vendor (CNA) |
| debian:linux | 6.1.20-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/52ea47a0ddfbc5fe05e873d3f5a59db4ba3e03fe
- git.kernel.org/stable/c/5735878a7b7db7e9ce731cb36cec298a9de67549
- git.kernel.org/stable/c/6d03bbff456befeccdd4d663177c4d6c75d0c4ff
- git.kernel.org/stable/c/8fcdbc4bc01365f4b10fed7db544a3149e3054fd
- git.kernel.org/stable/c/c57a8d14d7880521150ee801d53a0a64fdffd9c8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.