Cloudanix VulnDB

CVE-2025-68730

None

CVSS

—

EPSS

0.2%

Published

Dec 24, 2025

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A bug in Linux kernel code for certain graphics hardware could let a local attacker crash the computer or gain elevated access by exploiting incomplete memory cleanup.

Exploitation
Local Privilege
Attacker needs
Local User
Complexity
Moderate
Impact
Denial Of Service
Component
OS kernel
Class
Use After Free
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

A use-after-free occurs when a buffer object is added to vdev->bo_list in ivpu_gem_create_object but a subsequent failure in drm_gem_shmem_create prevents ivpu_gem_bo_free from being invoked, leaving a deleted BO on the list that is later dereferenced in ivpu_bo_unbind_all_bos_from_context.

Why it matters to the business

Linux systems using the ivpu driver may experience kernel crashes or potential local privilege escalation, impacting stability of AI accelerator workloads with low urgency given absence of known exploitation or ransomware use.

How an attack unfolds

An attacker with local access crafts conditions to induce a drm_gem_shmem_create failure during BO creation, leaving a dangling reference; subsequent unbind operations then trigger invalid memory access that can be leveraged for code execution or denial of service.

How to fix it

Apply the kernel fix from commit 8172838a284c27190fa6782c2740a97020434750 or upgrade affected packages to beats-fips-8 8.17.3-r5, metricbeat-fips-8 8.17.3-r5, filebeat-fips-8 8.17.3-r5, auditbeat-fips-8 8.17.3-r5, or heartbeat-fips-8 8.17.3-r5.

How to confirm the fix worked

Confirm the source change that prevents adding BOs to vdev->bo_list prior to successful drm_gem_shmem_create completion, and verify no dangling references remain after creation failures.

Typical attack path

  1. Trigger ivpu_gem_create_object under failure conditions in drm_gem_shmem_create
  2. Allow incomplete BO initialization to bypass ivpu_gem_bo_free cleanup
  3. Invoke ivpu_bo_unbind_all_bos_from_context to dereference the stale list entry
  4. Exploit resulting page fault or UAF for kernel-level access

How to detect it

Inspect kernel logs and panic traces for references to ivpu_bo_unbind_all_bos_from_context or page faults involving buffer objects on vdev lists; correlate with failed GEM creation attempts.

What your security team should do

  • Apply kernel and package updates to the listed fixed versions immediately on systems exposing ivpu
  • Review stable Linux git repositories for backports to distribution kernels
  • Monitor kernel logs for ivpu-related page faults until patches are deployed

The record

In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix page fault in ivpu_bo_unbind_all_bos_from_context() Don't add BO to the vdev->bo_list in ivpu_gem_create_object(). When failure happens inside drm_gem_shmem_create(), the BO is not fully created and ivpu_gem_bo_free() callback will not be called causing a deleted BO to be left on the list.

Affected packages

Ecosystem Package Introduced Fixed
Linux Kernel 6.8.0 6.17.13
openSUSE:Tumbleweed kernel-source 0 6.18.5-1.1
openSUSE:Tumbleweed kernel-source-longterm 0 6.18.16-1.1

Related vulnerabilities