drm/amdgpu: Reject UVD message with invalid number of h265 refs
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Reject UVD message with invalid number of h265 refs Same change as for h264, avoids overflow later when calculating min dpb size. (cherry picked from commit a4b0720e4f1601f97f59a2be9c1b4b94fa6527d5)
- Published
- Sep 4, 2026
- Updated
- Sep 7, 2026
- EPSS
- 0.2% · 5th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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.2affected
- 86fa0bdc6fd7b2debc07ce86f1bcd5fb254822e3 and later · before 1facad2a78c1a8aeecc36eb4d560c7f1e10ce198affected · git
- 86fa0bdc6fd7b2debc07ce86f1bcd5fb254822e3 and later · before 499907e5d46e575e96967c0230a0a6af980a17abaffected · git
- 86fa0bdc6fd7b2debc07ce86f1bcd5fb254822e3 and later · before cbf1c84bf5cac2b3742ea3d2085fa713424465ccaffected · git
- 86fa0bdc6fd7b2debc07ce86f1bcd5fb254822e3 and later · before a930c54cb67200de8bc0de87480d09ece7dcd85daffected · git
- 86fa0bdc6fd7b2debc07ce86f1bcd5fb254822e3 and later · before 2abcdc5f738574e7fcdd9417575dffb877fdc26faffected · git
- 86fa0bdc6fd7b2debc07ce86f1bcd5fb254822e3 and later · before e304c3e0d9ce251887be1f274aa0ed52219d5fd7affected · git
- 86fa0bdc6fd7b2debc07ce86f1bcd5fb254822e3 and later · before 0acdf1a575f59bd46717d5c487d84575af5bee8faffected · git
- 86fa0bdc6fd7b2debc07ce86f1bcd5fb254822e3 and later · before 9fca434208f1f9ab977feac62df8ebb1cc7ce893affected · git
- before 4.2not 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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.10-1 | 7.1.10-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 0acdf1a575f59bd46717d5c487d84575af5bee8f | Vendor (CNA) |
| Linux Linux | 1facad2a78c1a8aeecc36eb4d560c7f1e10ce198 | Vendor (CNA) |
| Linux Linux | 2abcdc5f738574e7fcdd9417575dffb877fdc26f | Vendor (CNA) |
| Linux Linux | 499907e5d46e575e96967c0230a0a6af980a17ab | Vendor (CNA) |
| Linux Linux | 9fca434208f1f9ab977feac62df8ebb1cc7ce893 | Vendor (CNA) |
| Linux Linux | a930c54cb67200de8bc0de87480d09ece7dcd85d | Vendor (CNA) |
| Linux Linux | cbf1c84bf5cac2b3742ea3d2085fa713424465cc | Vendor (CNA) |
| Linux Linux | e304c3e0d9ce251887be1f274aa0ed52219d5fd7 | 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 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1015 · Sep 7, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0acdf1a575f59bd46717d5c487d84575af5bee8f
- git.kernel.org/stable/c/1facad2a78c1a8aeecc36eb4d560c7f1e10ce198
- git.kernel.org/stable/c/2abcdc5f738574e7fcdd9417575dffb877fdc26f
- git.kernel.org/stable/c/499907e5d46e575e96967c0230a0a6af980a17ab
- git.kernel.org/stable/c/9fca434208f1f9ab977feac62df8ebb1cc7ce893
- git.kernel.org/stable/c/a930c54cb67200de8bc0de87480d09ece7dcd85d
- git.kernel.org/stable/c/cbf1c84bf5cac2b3742ea3d2085fa713424465cc
- git.kernel.org/stable/c/e304c3e0d9ce251887be1f274aa0ed52219d5fd7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.