CVE-2023-53242: thermal/drivers/hisi: Drop second sensor hi3660
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.16% (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 15cc25829a97c3957e520e971868aacc84341317, 3cf2181e438f43ed24e12424fe36d156cca233b9, 68e675a9b69cfc34dd915d91a4650e3ee53421f4.
Low priority for now. Upgrade to Linux Linux 15cc25829a97c3957e520e971868aacc84341317, 3cf2181e438f43ed24e12424fe36d156cca233b9, 68e675a9b69cfc34dd915d91a4650e3ee53421f4 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: thermal/drivers/hisi: Drop second sensor hi3660 The commit 74c8e6bffbe1 ("driver core: Add __alloc_size hint to devm allocators") exposes a panic "BRK handler: Fatal exception" on the hi3660_thermal_probe funciton. This is because the function allocates memory for only one sensors array entry, but tries to fill up a second one. Fix this by removing the unneeded second access.
- Published
- Sep 15, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
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.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.1
- 1.6 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.20.1 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
- linux linux kernel4.20
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.20affected
- 7d3a2a2bbadb4bf5856ed394ba09b8fbb7a80460 and later · before 3cf2181e438f43ed24e12424fe36d156cca233b9affected · git
- 7d3a2a2bbadb4bf5856ed394ba09b8fbb7a80460 and later · before e02bc492883abf751fd1a8d89fc025fbce6744c6affected · git
- 7d3a2a2bbadb4bf5856ed394ba09b8fbb7a80460 and later · before f5aaf140ab1c02889c088e1b1098adad600541afaffected · git
- 7d3a2a2bbadb4bf5856ed394ba09b8fbb7a80460 and later · before 9f6756cd09889c7201ee31e6f76fbd914fb0b80daffected · git
- 7d3a2a2bbadb4bf5856ed394ba09b8fbb7a80460 and later · before 68e675a9b69cfc34dd915d91a4650e3ee53421f4affected · git
- 7d3a2a2bbadb4bf5856ed394ba09b8fbb7a80460 and later · before 15cc25829a97c3957e520e971868aacc84341317affected · git
- before 4.20not 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-53240Sep 15, 2025 · xsk: check IFF_UP earlier in Tx path22Monitor
- ← EarlierCVE-2023-53241Sep 15, 2025 · nfsd: call op_release, even when op_func returns an error22Monitor
- Later →CVE-2023-53243Sep 15, 2025 · btrfs: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile22Monitor
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 | 15cc25829a97c3957e520e971868aacc84341317 | Vendor (CNA) |
| Linux Linux | 3cf2181e438f43ed24e12424fe36d156cca233b9 | Vendor (CNA) |
| Linux Linux | 68e675a9b69cfc34dd915d91a4650e3ee53421f4 | Vendor (CNA) |
| Linux Linux | 9f6756cd09889c7201ee31e6f76fbd914fb0b80d | Vendor (CNA) |
| Linux Linux | e02bc492883abf751fd1a8d89fc025fbce6744c6 | Vendor (CNA) |
| Linux Linux | f5aaf140ab1c02889c088e1b1098adad600541af | 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)
—
CVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3cf2181e438f43ed24e12424fe36d156cca233b9
- git.kernel.org/stable/c/68e675a9b69cfc34dd915d91a4650e3ee53421f4
- git.kernel.org/stable/c/9f6756cd09889c7201ee31e6f76fbd914fb0b80d
- git.kernel.org/stable/c/e02bc492883abf751fd1a8d89fc025fbce6744c6
- git.kernel.org/stable/c/f5aaf140ab1c02889c088e1b1098adad600541af
Vendor advisories and official records. Exploit/PoC links are deliberately left out.