Kernel crash via misaligned AMDGPU fence offset
Published Aug 10, 2026 · Updated Aug 10, 2026
Reachable assertions in the Linux kernel's AMDGPU SDMA 6.0 driver allow local users with render-node access to crash the kernel. The sdma_v6_0_ring_emit_fence function applies BUG_ON to an unvalidated, user-controlled fence offset whose low bits survive address construction. A local process with an AMDGPU render-node file descriptor and SDMA 6.0 hardware can submit a misaligned fence address, causing an oops and a machine panic when panic-on-oops handling is enabled.
Summary
What happened
Reachable assertions in the Linux kernel's AMDGPU SDMA 6.0 driver allow local users with render-node access to crash the kernel. The sdma_v6_0_ring_emit_fence function applies BUG_ON to an unvalidated, user-controlled fence offset whose low bits survive address construction. A local process with an AMDGPU render-node file descriptor and SDMA 6.0 hardware can submit a misaligned fence address, causing an oops and a machine panic when panic-on-oops handling is enabled.
The record
- CVE
- CVE-2026-68251
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-248, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.12.101
- Affected versionversion=0 <6.18.42
- Affected versionversion=0 <6.6.148
- Affected versionversion=0 <7.1.6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2eb06c88426b6c8de602c608959f3a56ac51861e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <51fd52087165180967cf7d5ee99badee7e172ea0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9df8a7f09e305249872b536555793b28e77b7de9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e7f31c9a61533062a704f90b9f63064045249693
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ec42c96c322e5cc48099ab5e67b5cbe236cb1949
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo