CVE-2025-37767: drm/amd/pm: Prevent division by zero
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.20% (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 327107bd7f052f4ee2d0c966c7ae879822f1814f, 8f7b5987e21e003cafac28f0e4d323e6496f83ba, c3ff73e3bddf1a6c30d7effe4018d12ba0cadd2e; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
Low priority for now. Upgrade to Linux Linux 327107bd7f052f4ee2d0c966c7ae879822f1814f, 8f7b5987e21e003cafac28f0e4d323e6496f83ba, c3ff73e3bddf1a6c30d7effe4018d12ba0cadd2e; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-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: drm/amd/pm: Prevent division by zero The user can set any speed value. If speed is greater than UINT_MAX/8, division by zero is possible. Found by Linux Verification Center (linuxtesting.org) with SVACE.
- Published
- May 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-369
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.2%
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.13 and later · before 5.15.181
- linux linux kernel5.16 and later · before 6.1.135
- linux linux kernel6.2 and later · before 6.6.88
- linux linux kernel6.7 and later · before 6.12.25
- linux linux kernel6.13 and later · before 6.14.4
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.13affected
- c05d1c401572ac63d704183b19db2ce746961412 and later · before f2904fa2b9da943db6bef7c0f8b3fb4fc14acbc4affected · git
- c05d1c401572ac63d704183b19db2ce746961412 and later · before 8f7b5987e21e003cafac28f0e4d323e6496f83baaffected · git
- c05d1c401572ac63d704183b19db2ce746961412 and later · before c3ff73e3bddf1a6c30d7effe4018d12ba0cadd2eaffected · git
- c05d1c401572ac63d704183b19db2ce746961412 and later · before fb803d4bb9ea0a61c21c4987505e4d4ae18f9fdcaffected · git
- c05d1c401572ac63d704183b19db2ce746961412 and later · before 327107bd7f052f4ee2d0c966c7ae879822f1814faffected · git
- c05d1c401572ac63d704183b19db2ce746961412 and later · before f23e9116ebb71b63fe9cec0dcac792aa9af30b0caffected · git
- before 5.13not affected · semver
- 5.15.181 and later · up to and including 5.15.*not affected · semver
- 6.1.135 and later · up to and including 6.1.*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.135-1 | 6.1.135-1 |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-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-37765May 1, 2025 · drm/nouveau: prime: fix ttm_bo_delayed_delete oops22Monitor
- ← EarlierCVE-2025-37766May 1, 2025 · drm/amd/pm: Prevent division by zero22Monitor
- Later →CVE-2025-37768May 1, 2025 · drm/amd/pm: Prevent division by zero22Monitor
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 | 327107bd7f052f4ee2d0c966c7ae879822f1814f | Vendor (CNA) |
| Linux Linux | 8f7b5987e21e003cafac28f0e4d323e6496f83ba | Vendor (CNA) |
| Linux Linux | c3ff73e3bddf1a6c30d7effe4018d12ba0cadd2e | Vendor (CNA) |
| Linux Linux | f23e9116ebb71b63fe9cec0dcac792aa9af30b0c | Vendor (CNA) |
| Linux Linux | f2904fa2b9da943db6bef7c0f8b3fb4fc14acbc4 | Vendor (CNA) |
| Linux Linux | fb803d4bb9ea0a61c21c4987505e4d4ae18f9fdc | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.135-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.
- CVE-2024-26945365 days apartcrypto: iaa - Fix nr_cpus < nr_iaa case33Monitor
- CVE-2025-377400 days apartjfs: add sanity check for agwidth in dbMount22Monitor
- CVE-2025-377660 days apartdrm/amd/pm: Prevent division by zero22Monitor
- CVE-2025-377680 days apartdrm/amd/pm: Prevent division by zero22Monitor
- CVE-2025-377690 days apartdrm/amd/pm/smu11: Prevent division by zero22Monitor
- CVE-2025-377700 days apartdrm/amd/pm: Prevent division by zero22Monitor
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-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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/8f7b5987e21e003cafac28f0e4d323e6496f83ba
- git.kernel.org/stable/c/c3ff73e3bddf1a6c30d7effe4018d12ba0cadd2e
- git.kernel.org/stable/c/f23e9116ebb71b63fe9cec0dcac792aa9af30b0c
- git.kernel.org/stable/c/f2904fa2b9da943db6bef7c0f8b3fb4fc14acbc4
- git.kernel.org/stable/c/fb803d4bb9ea0a61c21c4987505e4d4ae18f9fdc
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.