CVE-2025-21956: drm/amd/display: Assign normalized_pix_clk when color depth = 14
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.23% (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 0174a2e5770efee9dbd4b58963ed4d939298ff5e, 04f90b505ad3a6eed474bbaa03167095fef5203a, 0c0016712e5dc23ce4a7e673cbebc24a535d8c8a.
Low priority for now. Upgrade to Linux Linux 0174a2e5770efee9dbd4b58963ed4d939298ff5e, 04f90b505ad3a6eed474bbaa03167095fef5203a, 0c0016712e5dc23ce4a7e673cbebc24a535d8c8a 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: Assign normalized_pix_clk when color depth = 14 [WHY & HOW] A warning message "WARNING: CPU: 4 PID: 459 at ... /dc_resource.c:3397 calculate_phy_pix_clks+0xef/0x100 [amdgpu]" occurs because the display_color_depth == COLOR_DEPTH_141414 is not handled. This is observed in Radeon RX 6600 XT. It is fixed by assigning pix_clk * (14 * 3) / 24 - same as the rests. Also fixes the indentation in get_norm_pix_clk. (cherry picked from commit 274a87eb389f58eddcbc5659ab0b180b37e92775)
- Published
- Apr 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th 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.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.15 and later · before 5.4.292
- linux linux kernel5.5 and later · before 5.10.236
- linux linux kernel5.11 and later · before 5.15.180
- linux linux kernel5.16 and later · before 6.1.132
- linux linux kernel6.2 and later · before 6.6.84
- linux linux kernel6.7 and later · before 6.12.20
- linux linux kernel6.13 and later · before 6.13.8
- 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
- 4.15affected
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before cca3ab74f90176099b6392e8e894b52b27b3d080affected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 0174a2e5770efee9dbd4b58963ed4d939298ff5eaffected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 0c0016712e5dc23ce4a7e673cbebc24a535d8c8aaffected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before dc831b38680c47d07e425871a9852109183895cfaffected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before a8f77e1658d78e4a8bb227a83bcee67de97f7634affected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 04f90b505ad3a6eed474bbaa03167095fef5203aaffected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 27df30106690969f7d63604f0d49ed8e9bffa2cbaffected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 79e31396fdd7037c503e6add15af7cb00633ea92affected · git
- before 4.15not 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.133-1 | 6.1.133-1 |
| Debian:13 | linux | before 6.12.20-1 | 6.12.20-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-21953Apr 1, 2025 · net: mana: cleanup mana struct after debugfs_remove()22Monitor
- ← EarlierCVE-2025-21954Apr 1, 2025 · netmem: prevent TX of unreadable skbs22Monitor
- Later →CVE-2025-21957Apr 1, 2025 · scsi: qla1280: Fix kernel oops when debug level > 222Monitor
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 | 0174a2e5770efee9dbd4b58963ed4d939298ff5e | Vendor (CNA) |
| Linux Linux | 04f90b505ad3a6eed474bbaa03167095fef5203a | Vendor (CNA) |
| Linux Linux | 0c0016712e5dc23ce4a7e673cbebc24a535d8c8a | Vendor (CNA) |
| Linux Linux | 27df30106690969f7d63604f0d49ed8e9bffa2cb | Vendor (CNA) |
| Linux Linux | 79e31396fdd7037c503e6add15af7cb00633ea92 | Vendor (CNA) |
| Linux Linux | a8f77e1658d78e4a8bb227a83bcee67de97f7634 | Vendor (CNA) |
| Linux Linux | cca3ab74f90176099b6392e8e894b52b27b3d080 | Vendor (CNA) |
| Linux Linux | dc831b38680c47d07e425871a9852109183895cf | Vendor (CNA) |
| debian:linux | 6.1.133-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.
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 (9 more)Show less
- git.kernel.org/stable/c/04f90b505ad3a6eed474bbaa03167095fef5203a
- git.kernel.org/stable/c/0c0016712e5dc23ce4a7e673cbebc24a535d8c8a
- git.kernel.org/stable/c/27df30106690969f7d63604f0d49ed8e9bffa2cb
- git.kernel.org/stable/c/79e31396fdd7037c503e6add15af7cb00633ea92
- git.kernel.org/stable/c/a8f77e1658d78e4a8bb227a83bcee67de97f7634
- git.kernel.org/stable/c/cca3ab74f90176099b6392e8e894b52b27b3d080
- git.kernel.org/stable/c/dc831b38680c47d07e425871a9852109183895cf
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.