Linux kernel denial of service in amdgpu dma-buf move notify
- Exploited
- No known exploitation
- Fix
- Fixed in 6.17
- Who is exposed
- Not reported
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: check amdgpu_vm_ready() in dma-buf move notify
amdgpu_dma_buf_move_notify() touches the page tables without first calling amdgpu_vm_ready(). When a process is SIGKILLed, its VM entities are stopped. Teardown of an imported dma-buf then tries to clear PTEs by submitting to one of those stopped entities. That eventually hangs the task.
Commit aa5fc4362fac ("drm/amdgpu: fix task hang from failed job submission during process kill") added the stopped entity check in amdgpu_vm_ready() and used it in amdgpu_cs_vm_handling(). That did not cover a call in amdgpu_dma_buf_move_notify(), what was already mentioned in: lists.freedesktop.org/
Tested by SIGKILLing a GPU workload holding imported dma-bufs. Without the patch "Trying to push to a killed entity" errors are logged, then a task hangs. With the patch there are no hung tasks. This was tested on a 6.18 kernel.
(cherry picked from commit bee5c9d7a34cb1b510ad3b4c18c30f9d38b0ab7d)
What to do
Upgrade to a fixed version: 6.17.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99631 (drm/amdgpu: check amdgpu_vm_ready() in dma-buf move notify), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99631 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 6.16.4, fixed in 6.17
- Linux Linux: versions 6.17
Fixed versions: 6.17.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99631 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99631 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/357f2a753287d878ba13d49248c55343bb5e0090
- https://git.kernel.org/stable/c/d534c4d5d99c079e760b5d38b1f1813ea81292ea
- https://git.kernel.org/stable/c/920ca822f527e45ce084b36f3c420b625eb7c62a
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99631
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99631"}.Affected versions
- Linux LinuxFrom 6.16.4 · fixed in 6.17
- Linux Linux6.17
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99631 |
| Record | NVD · CVE-2026-99631 |
| Other links 3 | |
| Link | git.kernel.org · stable/c/357f2a753287d878ba13d49248c55343bb5e0090 |
| Link | git.kernel.org · stable/c/d534c4d5d99c079e760b5d38b1f1813ea81292ea |
| Link | git.kernel.org · stable/c/920ca822f527e45ce084b36f3c420b625eb7c62a |
Questions about CVE-2026-99631
Is CVE-2026-99631 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99631?
Linux: from 6.16.4 before 6.17. Linux: version 6.17.
Source: cve.now feed data
How do I fix CVE-2026-99631?
Upgrade to a fixed version: 6.17.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.