dmaengine: idxd: fix double free of wq, engine, and group structs
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.12, 5.13, 6.6.160, 6.12.114, 6.18.57, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 7c5dd23e57c14cf7177b8a5e0fd08916e0c60005 · fixed in 84cf00b1376c717e55d704dc259483e822ae1b34; From 7c5dd23e57c14cf7177b8a5e0fd08916e0c60005 · fixed in 38208445c41a6164e26748c600f954296991364d; From 7c5dd23e57c14cf7177b8a5e0fd08916e0c60005 · fixed in 63844dc03960b09b36746eda636c08f1479407ce; From 7c5dd23e57c14cf7177b8a5e0fd08916e0c60005 · fixed in c93a9f652b7373ac8ee5bfcc18a9af76959b6c6c; From 7c5dd23e57c14cf7177b8a5e0fd08916e0c60005 · fixed in ec2d428b2e32dd157de8f86a86dd85c5b2c8f45c; From 5.11.22 · fixed in 5.12; From 5.12.5 · fixed in 5.13
- Linux Linux
5.13
- KernelLinux
From 5.13.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.1.8