CVE-2026-80698

dmaengine: idxd: fix double free of wq, engine, and group structs

N/A
Published: August 28, 2026 at 06:53 AM UTC
Updated: October 21, 2026 at 01:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix double free of wq, engine, and group structs The release callbacks for wq, engine, and group devices (idxd_conf_wq_release, idxd_conf_engine_release, idxd_conf_group_release) each call kfree() on the enclosing struct. The setup error paths and cleanup functions also call kfree() explicitly after put_device(), producing a double free whenever put_device() drops the reference count to zero and fires the release. In the setup functions, device_initialize() is called before device_add(), so the reference count is exactly 1 at the error sites. put_device() unconditionally fires the release, which frees the struct; the subsequent explicit kfree() then operates on freed memory. For idxd_setup_wqs(), the wq release callback also owns opcap_bmap and wqcfg. The error unwind additionally freed those fields explicitly before calling put_device(), causing further double frees on both. Remove the redundant explicit kfree() calls from all setup error paths and cleanup functions for wq, engine, and group structs, delegating sole ownership of those allocations to the release callbacks.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1c28fd5f94d8996f7dd3805bd6a16ed46a5d088626c219e7522c494f7865a928c81ced84cc7db3ae35ea8721d9e6e74c6847cf4d6c27e883b00b0331394e179f51fce06d6bb8ca5af8fa53f33c718cf45.11.225.12.55.137c5dd23e57c14cf7177b8a5e0fd08916e0c60005b09ad63775f58a8de3e228f59fb9543bfd964c9ce6f86fe368cdc14764833a6e8bb59f7a85a40e06
Vendor states this is fixed in c93a9f652b7373ac8ee5bfcc18a9af76959b6c6c (fixed)
Vendor states this is fixed in ec2d428b2e32dd157de8f86a86dd85c5b2c8f45c (fixed)
Affected range stops below 5.12, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 6.12.114 (unaffected)
Vendor states this is fixed in 6.18.57 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card