Linux Kernel up to 6.19.10 amdgpu_amdkfd_submit_ib use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in Linux Kernel up to 6.1.167/6.6.130/6.12.79/6.18.20/6.19.10. This affects the function amdgpu_amdkfd_submit_ib. Such manipulation leads to use after free. This vulnerability is listed as CVE-2026-31566. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.1.167/6.6.130/6.12.79/6.18.20/6.19.10. It has been rated as critical. Affected by this issue is the function amdgpu_amdkfd_submit_ib. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib amdgpu_amdkfd_submit_ib() submits a GPU job and gets a fence from amdgpu_ib_schedule(). This fence is used to wait for job completion. Currently, the code drops the fence reference using dma_fence_put() before calling dma_fence_wait(). If dma_fence_put() releases the last reference, the fence may be freed before dma_fence_wait() is called. This can lead to a use-after-free. Fix this by waiting on the fence first and releasing the reference only after dma_fence_wait() completes. Fixes the below: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:697 amdgpu_amdkfd_submit_ib() warn: passing freed memory 'f' (line 696) (cherry picked from commit 8b9e5259adc385b61a6590a13b82ae0ac2bd3482)

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-31566 since 03/09/2026. The exploitation is known to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 05/26/2026).

The vulnerability scanner Nessus provides a plugin with the ID 310321 (Linux Distros Unpatched Vulnerability : CVE-2026-31566), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.168, 6.6.131, 6.12.80, 6.18.21 or 6.19.11 eliminates this vulnerability. Applying the patch bc7760c107dc08ef3e231d72c492e67b0a86848b/e23602eb0779760544314ed3905fa6a89a4e4070/138e42be35ff2ce6572ae744de851ea286cf3c69/39820864eacd886f1a6f817414fb8f9ea3e9a2b4/42d248726a0837640452b71c5a202ca3d35239ec/7150850146ebfa4ca998f653f264b8df6f7f85be is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (310321) and CERT Bund (WID-SEC-2026-1279). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Red Hat Enterprise Linux
  • Oracle Linux
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 310321
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-31566

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.168/6.6.131/6.12.80/6.18.21/6.19.11
Patch: bc7760c107dc08ef3e231d72c492e67b0a86848b/e23602eb0779760544314ed3905fa6a89a4e4070/138e42be35ff2ce6572ae744de851ea286cf3c69/39820864eacd886f1a6f817414fb8f9ea3e9a2b4/42d248726a0837640452b71c5a202ca3d35239ec/7150850146ebfa4ca998f653f264b8df6f7f85be

Timelineinfo

03/09/2026 CVE reserved
04/24/2026 +45 days Advisory disclosed
04/24/2026 +0 days VulDB entry created
05/26/2026 +31 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-31566 (🔒)
GCVE (CVE): GCVE-0-2026-31566
GCVE (VulDB): GCVE-100-359378
CERT Bund: WID-SEC-2026-1279 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 04/24/2026 17:43
Updated: 05/26/2026 00:54
Changes: 04/24/2026 17:43 (58), 04/26/2026 12:59 (2), 05/26/2026 00:54 (7)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!