Linux Kernel up to 6.17.12/6.18.1 accel ivpu_bo_unbind_all_bos_from_context memory corruption

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.17.12/6.18.1. This vulnerability affects the function ivpu_bo_unbind_all_bos_from_context of the component accel. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2025-68730. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.17.12/6.18.1. It has been classified as critical. This affects the function ivpu_bo_unbind_all_bos_from_context of the component accel. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-68730 since 12/24/2025. The exploitability is told to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/25/2025).

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

Upgrading to version 6.17.13, 6.18.2 or 6.19-rc1 eliminates this vulnerability. Applying the patch 8172838a284c27190fa6782c2740a97020434750/c9ef5ccd8bd9bcf598b6d3f77e7eb4dde7149aec/8b694b405a84696f1d964f6da7cf9721e68c4714 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 (279704) and CERT Bund (WID-SEC-2025-2920). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Open Source Linux Kernel

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.17.0
• 6.17.1
• 6.17.2
• 6.17.3
• 6.17.4
• 6.17.5
• 6.17.6
• 6.17.7
• 6.17.8
• 6.17.9
• 6.17.10
• 6.17.11
• 6.17.12
• 6.18.0
• 6.18.1

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion