CVE-2026-80698

Description

A flaw was found in the dmaengine: idxd component of the Linux kernel. This vulnerability is caused by a double free error where memory allocated for work queue (wq), engine, and group structures is freed twice. This occurs because kfree() is explicitly called in error handling and cleanup routines, in addition to being called by the device release callbacks. A local attacker could potentially exploit this to cause a denial of service or have other unspecified impacts due to memory corruption.

Statement

A double free can occur in the dmaengine idxd driver because wq, engine, and group objects are freed by their device release callbacks and were also freed explicitly by setup error paths or cleanup functions after put_device. When put_device drops the reference count to zero, the release callback owns the final free, so a later kfree operates on already freed kernel memory. For the CVSS the PR:L is used in the paranoid score because a local actor with limited but relevant control over driver lifecycle, device management, or resource pressure may be able to reach error or cleanup paths in some deployments. The realistic base case is closer to PR:H because normal idxd load and remove operations are administrator controlled. The issue is not network reachable. Impact is at least local denial of service via kernel memory corruption and in the worst case may allow confidentiality or integrity impact if the double free can be shaped into a usable kernel heap corruption primitive.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.