Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-64516— drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets

CVSS 8.8 · High EPSS 0.14% · P4

Possible ATT&CK Techniques 1AI

T1203 · Exploitation for Client Execution

Affected Version Matrix 6

VendorProductVersion RangeStatus
LinuxLinuxd4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f< ce0de178ef08408f6ba8f2e9a13bf52fbe5852f4affected
d4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f< 3e5a1d5bb2ff061e64c7992f8e5404dfd4c2d0f3affected
6.19affected
< 6.19unaffected
7.0.11≤ 7.0.*unaffected
7.1≤ *unaffected
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-64516

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access. Make sure the stack and data offsets are aligned to the 32K TLB size. Check that the FW microcode actually fits in the space that is reserved for it. (cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux d4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f ~ ce0de178ef08408f6ba8f2e9a13bf52fbe5852f4 -
LinuxLinux 6.19 -

II. Public POCs for CVE-2026-64516

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-64516

登录查看更多情报信息。

Patches & Fixes for CVE-2026-64516 (2)

Same Patch Batch · Linux · 2026-07-25 · 274 CVEs total

CVE-2026-643919.8 CRITICALksmbd: use opener credentials for ADS I/O
CVE-2026-642689.8 CRITICALRDMA/siw: bound Read Response placement to the RREAD length
CVE-2026-643849.8 CRITICALsmb: client: fix change notify replay double-free
CVE-2026-643839.8 CRITICALsmb: client: fix double-free in SMB2_flush() replay
CVE-2026-643859.8 CRITICALsmb: client: fix double-free in SMB2_ioctl() replay
CVE-2026-643869.8 CRITICALsmb: client: fix query_info() replay double-free
CVE-2026-643879.8 CRITICALsmb: client: fix query directory replay double-free
CVE-2026-644399.8 CRITICALcrypto: krb5 - filter out async aead implementations at alloc
CVE-2026-643039.8 CRITICALspi: fsl-lpspi: terminate the RX channel on TX prepare failure path
CVE-2026-643559.8 CRITICALbpf: Reject fragmented frames in devmap
CVE-2026-644599.8 CRITICALtcp: restore RCU grace period in tcp_ao_destroy_sock
CVE-2026-644109.8 CRITICALnetfilter: flowtable: IPIP tunnel hardware offload is not yet support
CVE-2026-643999.8 CRITICALksmbd: add permission checks for FSCTL_DUPLICATE_EXTENTS_TO_FILE
CVE-2026-643979.8 CRITICALksmbd: serialize QUERY_DIRECTORY requests per file
CVE-2026-645239.8 CRITICALnet/handshake: Take a long-lived file reference at submit
CVE-2026-643209.1 CRITICALnvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page
CVE-2026-643929.1 CRITICALksmbd: use opener credentials for delete-on-close
CVE-2026-642699.1 CRITICALRDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg
CVE-2026-643939.1 CRITICALksmbd: run set info with opener credentials
CVE-2026-643199.1 CRITICALnvmet-auth: validate reply message payload bounds against transfer length

Showing top 20 of 274 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-64516

No comments yet


Leave a comment