CVE-2025-21784: drm/amdgpu: bail out when failed to load fw in psp_init_cap_microcode()
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 3f40a7ff39d9f1d283d5aa9b13e2fb16200aff5f, a0a455b4bc7483ad60e8b8a50330c1e05bb7bfcf, d1d10bd595539ed82ab59b60249f9bdf0994f678.
Low priority for now. Upgrade to Linux Linux 3f40a7ff39d9f1d283d5aa9b13e2fb16200aff5f, a0a455b4bc7483ad60e8b8a50330c1e05bb7bfcf, d1d10bd595539ed82ab59b60249f9bdf0994f678 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/amdgpu: bail out when failed to load fw in psp_init_cap_microcode() In function psp_init_cap_microcode(), it should bail out when failed to load firmware, otherwise it may cause invalid memory access.
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th 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.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 |
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.6.79
- linux linux kernel6.7 and later · before 6.12.16
- linux linux kernel6.13 and later · before 6.13.4
- linux linux kernel6.14
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
- 07dbfc6b102e25087ec345ef2c2eae21c9856f17 and later · before 3f40a7ff39d9f1d283d5aa9b13e2fb16200aff5faffected · git
- 07dbfc6b102e25087ec345ef2c2eae21c9856f17 and later · before d1d10bd595539ed82ab59b60249f9bdf0994f678affected · git
- 07dbfc6b102e25087ec345ef2c2eae21c9856f17 and later · before e7eb84384335e2abf960c94ec0f8c5b835283777affected · git
- 07dbfc6b102e25087ec345ef2c2eae21c9856f17 and later · before a0a455b4bc7483ad60e8b8a50330c1e05bb7bfcfaffected · git
- before 6.3not affected · semver
- 6.6.79 and later · up to and including 6.6.*not affected · semver
- 6.12.16 and later · up to and including 6.12.*not affected · semver
- 6.13.4 and later · up to and including 6.13.*not affected · semver
- 6.14 and laternot affected · original_commit_for_fix
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.16-1 | 6.12.16-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-21782Feb 26, 2025 · orangefs: fix a oob in orangefs_debug_write28Monitor
- ← EarlierCVE-2025-21783Feb 26, 2025 · gpiolib: Fix crash on error in gpiochip_get_ngpios()22Monitor
- Later →CVE-2025-21786Feb 26, 2025 · workqueue: Put the pwq after detaching the rescuer from the pool31Monitor
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 | 3f40a7ff39d9f1d283d5aa9b13e2fb16200aff5f | Vendor (CNA) |
| Linux Linux | a0a455b4bc7483ad60e8b8a50330c1e05bb7bfcf | Vendor (CNA) |
| Linux Linux | d1d10bd595539ed82ab59b60249f9bdf0994f678 | Vendor (CNA) |
| Linux Linux | e7eb84384335e2abf960c94ec0f8c5b835283777 | Vendor (CNA) |
| debian:linux | 6.12.16-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.
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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.