CVE-2025-38297: PM: EM: Fix potential division-by-zero error in em_compute_costs()
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.17% (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 14cbdd64f3870cf0a2d94b87919b9056448c59a0, 179c0c7044a378198adb36f2a12410ab68cc730a, 81d72f9241d884ec29524431f74f8009310cfa0c.
Low priority for now. Upgrade to Linux Linux 14cbdd64f3870cf0a2d94b87919b9056448c59a0, 179c0c7044a378198adb36f2a12410ab68cc730a, 81d72f9241d884ec29524431f74f8009310cfa0c 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: PM: EM: Fix potential division-by-zero error in em_compute_costs() When the device is of a non-CPU type, table[i].performance won't be initialized in the previous em_init_performance(), resulting in division by zero when calculating costs in em_compute_costs(). Since the 'cost' algorithm is only used for EAS energy efficiency calculations and is currently not utilized by other device drivers, we should add the _is_cpu_device(dev) check to prevent this division-by-zero issue.
- Published
- Jul 10, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-369
Report tools
Action score
22
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.
Is your version affected? Check itNoroxi 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 |
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
- 6.9affected
- 1b600da510735a0f92c8b4140a7e2cb037a6a6c3 and later · before 81d72f9241d884ec29524431f74f8009310cfa0caffected · git
- 1b600da510735a0f92c8b4140a7e2cb037a6a6c3 and later · before 14cbdd64f3870cf0a2d94b87919b9056448c59a0affected · git
- 1b600da510735a0f92c8b4140a7e2cb037a6a6c3 and later · before 179c0c7044a378198adb36f2a12410ab68cc730aaffected · git
- before 6.9not affected · semver
- 6.12.34 and later · up to and including 6.12.*not affected · semver
- 6.15.3 and later · up to and including 6.15.*not affected · semver
- 6.16 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.9 and later · before 6.12.34
- linux linux kernel6.13 and later · before 6.15.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.35-1 | 6.12.35-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.26.1.160000.2.7 | 6.12.0-160000.26.1.160000.2.7 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.26.1.160000.2.7 | 6.12.0-160000.26.1.160000.2.7 |
| SUSE:Linux Micro 6.2 | kernel-rt | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
| SUSE:Linux Micro 6.2 | kernel-source | before 6.12.0-160000.26.1 | 6.12.0-160000.26.1 |
+2
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-38295Jul 10, 2025 · perf/amlogic: Replace smp_processor_id() with raw_smp_processor_id() in meson_ddr_pmu_create()31Monitor
- ← EarlierCVE-2025-38296Jul 10, 2025 · ACPI: platform_profile: Avoid initializing on non-ACPI platforms22Monitor
- Later →CVE-2025-38298Jul 10, 2025 · EDAC/skx_common: Fix general protection fault31Monitor
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 | 14cbdd64f3870cf0a2d94b87919b9056448c59a0 | Vendor (CNA) |
| Linux Linux | 179c0c7044a378198adb36f2a12410ab68cc730a | Vendor (CNA) |
| Linux Linux | 81d72f9241d884ec29524431f74f8009310cfa0c | Vendor (CNA) |
| debian:linux | 6.12.35-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.26.1.160000.2.7 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.26.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.26.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.26.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.26.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.26.1.160000.2.7 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.26.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.26.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.26.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.26.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.26.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.26.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.26.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.26.1 · SUSE:Linux Enterprise Server 16.0 | 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-26945435 days apartcrypto: iaa - Fix nr_cpus < nr_iaa case33Monitor
- CVE-2025-383120 days apartfbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod()22Monitor
- CVE-2025-382056 days apartdrm/amd/display: Avoid divide by zero by initializing dummy pitch to 122Monitor
- CVE-2025-381267 days apartnet: stmmac: make sure that ptp_rate is not 0 before configuring timestamping22Monitor
- CVE-2022-4997822 days apartfbdev: fb_pm2fb: Avoid potential divide by zero error22Monitor
- CVE-2022-5017822 days apartwifi: rtw89: 8852a: rfk: fix div 0 exception22Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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-369 · Divide By ZeroCVSS 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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.