CVE-2025-38142: hwmon: (asus-ec-sensors) check sensor index in read_string()
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.18% (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 19bd9cde38dd4ca1771aed7afba623e7f4247c8e, 25be318324563c63cbd9cb53186203a08d2f83a1, 4e9e45746b861ebd54c03ef301da2cb8fc990536; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1.
Low priority for now. Upgrade to Linux Linux 19bd9cde38dd4ca1771aed7afba623e7f4247c8e, 25be318324563c63cbd9cb53186203a08d2f83a1, 4e9e45746b861ebd54c03ef301da2cb8fc990536; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1 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: (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]
- Published
- Jul 3, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th 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%
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.18 and later · before 6.1.142
- linux linux kernel6.2 and later · before 6.6.94
- linux linux kernel6.7 and later · before 6.12.34
- linux linux kernel6.13 and later · before 6.15.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
- 5.18affected
- d0ddfd241e5719d696bc0b081e260db69d368668 and later · before 6bf529ce84dccc0074dbc704e70aee4aa545057eaffected · git
- d0ddfd241e5719d696bc0b081e260db69d368668 and later · before 4e9e45746b861ebd54c03ef301da2cb8fc990536affected · git
- d0ddfd241e5719d696bc0b081e260db69d368668 and later · before 19bd9cde38dd4ca1771aed7afba623e7f4247c8eaffected · git
- d0ddfd241e5719d696bc0b081e260db69d368668 and later · before 7eeb3df6f07a886bdfd52757ede127a59a8784dcaffected · git
- d0ddfd241e5719d696bc0b081e260db69d368668 and later · before 25be318324563c63cbd9cb53186203a08d2f83a1affected · git
- before 5.18not affected · semver
- 6.1.142 and later · up to and including 6.1.*not affected · semver
- 6.6.94 and later · up to and including 6.6.*not affected · semver
- 6.12.34 and later · up to and including 6.12.*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.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.35-1 | 6.12.35-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-2025-38139Jul 3, 2025 · netfs: Fix oops in write-retry from mis-resetting the subreq iterator28Monitor
- ← EarlierCVE-2025-38141Jul 3, 2025 · dm: fix dm_blk_report_zones31Monitor
- Later →CVE-2025-38143Jul 3, 2025 · backlight: pm8941: Add NULL check in wled_configure()22Monitor
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 | 19bd9cde38dd4ca1771aed7afba623e7f4247c8e | Vendor (CNA) |
| Linux Linux | 25be318324563c63cbd9cb53186203a08d2f83a1 | Vendor (CNA) |
| Linux Linux | 4e9e45746b861ebd54c03ef301da2cb8fc990536 | Vendor (CNA) |
| Linux Linux | 6bf529ce84dccc0074dbc704e70aee4aa545057e | Vendor (CNA) |
| Linux Linux | 7eeb3df6f07a886bdfd52757ede127a59a8784dc | Vendor (CNA) |
| azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.147-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/25be318324563c63cbd9cb53186203a08d2f83a1
- git.kernel.org/stable/c/4e9e45746b861ebd54c03ef301da2cb8fc990536
- git.kernel.org/stable/c/6bf529ce84dccc0074dbc704e70aee4aa545057e
- git.kernel.org/stable/c/7eeb3df6f07a886bdfd52757ede127a59a8784dc
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.