Look up another CVE · open CVE-2025-68730 in the interactive tracker
CVE-2025-68730
accel/ivpu: Fix page fault in ivpu_bo_unbind_all_bos_from_context()
Published 2025-12-24 (10 months ago) by the Linux kernel CNA. Subsystem drivers/accel. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2025-68730 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 6.17.13-1 | Update the kernel and reboot. Fixed in 6.17.13-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.17.13-1 | Update the kernel and reboot. Fixed in 6.17.13-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/accel/ivpu/ivpu_gem.c
- What this is
- DRM ACCEL DRIVERS FOR INTEL VPUMAINTAINERS section matched on drivers/accel/ivpu/ · dri-devel@lists.freedesktop.org · Supported
- Kernel module
- intel_vpu
Check it on the machine
grep -wE 'CONFIG_DRM_ACCEL|CONFIG_DRM_ACCEL_IVPU' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w intel_vpuPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixieMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_DRM_ACCEL, CONFIG_DRM_ACCEL_IVPU
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2025-12-24 (10 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.14%, higher than 3.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/accel
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.8 | 6.17.13 | 8172838a284c |
| 6.8 | 6.18.2 | c9ef5ccd8bd9 |
| 6.8 | 6.19 | 8b694b405a84 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The attacker reaches the flaw through DRM_IOCTL_IVPU_BO_CREATE on a local /dev/accel/accel* device, followed by closing the descriptor to invoke vulnerable context teardown.
- AC:LAttack complexity, low
- A page-aligned size of 0x8000000000000000 deterministically becomes a negative loff_t in shmem_file_setup(), forcing failure after the BO was linked; the attacker then directly triggers the UAF by closing the descriptor.
- PR:LPrivileges required, low
- The ioctl has no DRM authentication, master, root-only, or capability requirement and is available to an ordinary user granted normal accelerator-device access.
- UI:NUser interaction, none
- The attacker independently issues the allocation ioctl and closes the descriptor; no action by another user is required.
- S:UScope, unchanged
- The dangling BO corrupts or exposes resources within the same host-kernel security authority and does not itself cross a VM or IOMMU isolation boundary.
- C:HConfidentiality impact, high
- The freed BO can be reclaimed and sprayed before list traversal, making its reservation and other pointer fields attacker-influenced; this kernel-heap UAF can support arbitrary kernel-memory disclosure.
- I:HIntegrity impact, high
- Traversal performs locking and possible unbinding through attacker-influenced freed-object pointers, making arbitrary kernel writes or control-flow hijacking defensible.
- A:HAvailability impact, high
- The stale BO is dereferenced during context teardown, producing the documented kernel page fault; controlled reallocation can also corrupt the list and cause an unbounded teardown loop.