CVE-2025-37870: drm/amd/display: prevent hang on link training fail
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.30% (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 0363c03672cd3191f037905bf981eb523a3b71b1, 04bf4f2a497e9877c425c5124652e61fb8a1a0aa, 52cdc47cf6519e2912a34d29b7eeb3f10ca85efa.
Low priority for now. Upgrade to Linux Linux 0363c03672cd3191f037905bf981eb523a3b71b1, 04bf4f2a497e9877c425c5124652e61fb8a1a0aa, 52cdc47cf6519e2912a34d29b7eeb3f10ca85efa 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/display: prevent hang on link training fail [Why] When link training fails, the phy clock will be disabled. However, in enable_streams, it is assumed that link training succeeded and the mux selects the phy clock, causing a hang when a register write is made. [How] When enable_stream is hit, check if link training failed. If it did, fall back to the ref clock to avoid a hang and keep the system in a recoverable state.
- Published
- May 9, 2025
- Updated
- Oct 21, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- —
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.3%
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.3affected
- 7462475e3a06fbb0b36243b391296f9f411e9041 and later · before 52cdc47cf6519e2912a34d29b7eeb3f10ca85efaaffected · git
- 7462475e3a06fbb0b36243b391296f9f411e9041 and later · before 0363c03672cd3191f037905bf981eb523a3b71b1affected · git
- 7462475e3a06fbb0b36243b391296f9f411e9041 and later · before 04bf4f2a497e9877c425c5124652e61fb8a1a0aaaffected · git
- 7462475e3a06fbb0b36243b391296f9f411e9041 and later · before 8058061ed9d6bc259d1e678607b07d259342c08faffected · git
- before 6.3not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.25 and later · up to and including 6.12.*not affected · semver
- 6.14.4 and later · up to and including 6.14.*not affected · semver
- 6.15 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.3 and later · before 6.12.25
- linux linux kernel6.13 and later · before 6.14.4
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.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-37867May 9, 2025 · RDMA/core: Silence oversized kvmalloc() warning22Monitor
- ← EarlierCVE-2025-37869May 9, 2025 · drm/xe: Use local fence in error path of xe_migrate_clear31Monitor
- Later →CVE-2025-37873May 9, 2025 · eth: bnxt: fix missing ring index trim on error path22Monitor
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 | 0363c03672cd3191f037905bf981eb523a3b71b1 | Vendor (CNA) |
| Linux Linux | 04bf4f2a497e9877c425c5124652e61fb8a1a0aa | Vendor (CNA) |
| Linux Linux | 52cdc47cf6519e2912a34d29b7eeb3f10ca85efa | Vendor (CNA) |
| Linux Linux | 8058061ed9d6bc259d1e678607b07d259342c08f | Vendor (CNA) |
| debian:linux | 6.12.25-1 · Debian:13 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · 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)
—
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.