CVE-2025-68201: drm/amdgpu: remove two invalid BUG_ON()s
Noroxi assessment
Priority: Monitor (action score 0/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.22% (FIRST EPSS).
- Fixed version: Linux Linux 5d55ed19d4190d2c210ac05ac7a53f800a8c6fe5, 7281d5b698d60fa46d17cd36ee8c5192fea9428d, a41bdba05899c7f455cd960ef0713acc335370dc; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 5d55ed19d4190d2c210ac05ac7a53f800a8c6fe5, 7281d5b698d60fa46d17cd36ee8c5192fea9428d, a41bdba05899c7f455cd960ef0713acc335370dc; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: remove two invalid BUG_ON()s Those can be triggered trivially by userspace.
- Published
- Dec 16, 2025
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
—
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.19affected
- 3d879e81f0f9ed5d33b5eda0fe5226c884bb8073 and later · before 7281d5b698d60fa46d17cd36ee8c5192fea9428daffected · git
- 3d879e81f0f9ed5d33b5eda0fe5226c884bb8073 and later · before b68d1f321119b83ca58edd1365c44453b4047c91affected · git
- 3d879e81f0f9ed5d33b5eda0fe5226c884bb8073 and later · before eaf12bffd7f79f4d46ec028706f9d1a2d90f46fdaffected · git
- 3d879e81f0f9ed5d33b5eda0fe5226c884bb8073 and later · before a41bdba05899c7f455cd960ef0713acc335370dcaffected · git
- 3d879e81f0f9ed5d33b5eda0fe5226c884bb8073 and later · before 5d55ed19d4190d2c210ac05ac7a53f800a8c6fe5affected · git
- before 5.19not affected · semver
- 6.1.175 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.59 and later · up to and including 6.12.*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.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.9-1 | 6.17.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68199Dec 16, 2025 · codetag: debug: handle existing CODETAG_EMPTY in mark_objexts_empty for slabobj_ext0Monitor
- ← EarlierCVE-2025-68200Dec 16, 2025 · bpf: Add bpf_prog_run_data_pointers()0Monitor
- Later →CVE-2025-68202Dec 16, 2025 · sched_ext: Fix unsafe locking in the scx_dump_state()0Monitor
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 | 5d55ed19d4190d2c210ac05ac7a53f800a8c6fe5 | Vendor (CNA) |
| Linux Linux | 7281d5b698d60fa46d17cd36ee8c5192fea9428d | Vendor (CNA) |
| Linux Linux | a41bdba05899c7f455cd960ef0713acc335370dc | Vendor (CNA) |
| Linux Linux | b68d1f321119b83ca58edd1365c44453b4047c91 | Vendor (CNA) |
| Linux Linux | eaf12bffd7f79f4d46ec028706f9d1a2d90f46fd | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.176-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.