Skip to main content
Vulnerability Database/CVE-2026-31440

CVE-2026-31440: Linux Kernel Information Disclosure Flaw

CVE-2026-31440 is an information disclosure vulnerability in the Linux Kernel dmaengine idxd driver that causes event log memory leaks during device removal. This article covers technical details, affected versions, and mitigation.

Updated:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-31440 Overview

CVE-2026-31440 is a memory leak vulnerability in the Linux kernel's Intel Data Streaming Accelerator (idxd) DMA engine driver. The flaw resides in the device removal path, where the driver fails to release event log memory after a device reset. During removal, the device is reset and configuration registers return to their default zero state. Because the driver checks whether event log support was enabled before deallocating, the deallocation is skipped when a reset has already cleared that capability bit, leaking the allocated buffer. The issue is tracked under [CWE-401: Missing Release of Memory after Effective Lifetime].

Critical Impact

A local authenticated user with the ability to repeatedly bind and unbind idxd devices can exhaust kernel memory, leading to denial of service on affected Linux systems.

Affected Products

  • Linux Kernel (mainline) prior to fixed commits
  • Linux Kernel 7.0-rc1 through 7.0-rc5
  • Systems using Intel Data Streaming Accelerator (idxd) DMA engine driver

Discovery Timeline

  • 2026-04-22 - CVE-2026-31440 published to NVD
  • 2026-05-07 - Last updated in NVD database

Technical Details for CVE-2026-31440

Vulnerability Analysis

The vulnerability exists in the idxd DMA engine driver, which provides kernel support for Intel Data Streaming Accelerator hardware. The driver allocates an event log buffer (idxd->evl) when the hardware advertises event log capability. This buffer must be released when the device is removed.

During device removal, the driver issues a reset that clears the device configuration registers. After this reset, the capability bit indicating event log support reads as zero. The cleanup code conditionally frees the event log memory based on this capability bit rather than on the presence of a valid idxd->evl allocation. The conditional check evaluates false after a reset, and the allocated memory is never freed.

Repeated device bind and unbind operations accumulate leaked allocations in kernel memory. Over time this exhausts kernel memory available for other allocations, producing a denial of service condition.

Root Cause

The root cause is an incorrect predicate guarding deallocation in the device removal path. The driver consults runtime hardware state to decide whether to release a software-managed allocation. Because the reset performed during removal clears that hardware state, the predicate becomes unreliable and the deallocation is skipped.

The upstream fix removes the hardware capability check and relies solely on whether idxd->evl points to a valid allocation, since the pointer is only set when the capability was present at allocation time.

Attack Vector

Exploitation requires local access with sufficient privileges to trigger idxd device removal or to repeatedly bind and unbind the driver through sysfs. No user interaction or network access is required. The attacker cannot directly read or modify memory through this flaw. The impact is limited to availability through kernel memory exhaustion.

The vulnerability is not known to be exploited in the wild and is not listed in the CISA Known Exploited Vulnerabilities catalog. No public proof-of-concept exploit is available.

Detection Methods for CVE-2026-31440

Indicators of Compromise

  • Steadily increasing kernel slab memory consumption visible in /proc/meminfo and /proc/slabinfo correlated with idxd driver activity.
  • Repeated idxd device bind and unbind events recorded in kernel logs (dmesg) without corresponding memory recovery.
  • Out-of-memory events on systems with Intel Data Streaming Accelerator hardware and the idxd driver loaded.

Detection Strategies

  • Inventory Linux hosts running affected kernel versions and verify whether the idxd driver is loaded using lsmod | grep idxd.
  • Monitor kernel memory growth over time on systems with idxd hardware, alerting on sustained slab growth without workload justification.
  • Audit sysfs writes to /sys/bus/dsa/drivers/idxd/bind and unbind paths to identify unusual device lifecycle activity.

Monitoring Recommendations

  • Collect kernel telemetry including dmesg output, slabinfo, and OOM killer events into a centralized log platform for trend analysis.
  • Establish baselines for kernel memory utilization on servers hosting Intel DSA-enabled workloads.
  • Alert on local privilege actions that interact with DMA engine driver sysfs interfaces from non-administrative accounts.

How to Mitigate CVE-2026-31440

Immediate Actions Required

  • Apply the upstream Linux kernel patches referenced in the kernel.org commits and rebuild or update to a kernel release that includes the fix.
  • Restrict local access to systems running affected kernels and limit which accounts can manipulate DMA engine driver bindings.
  • Where patching is delayed, avoid repeated bind and unbind cycles of idxd devices on production systems.

Patch Information

The fix is available in upstream Linux kernel commits 9dfa009, d94f9b0, ee66bc2, and facd001. The patch removes the capability-bit check in the event log teardown path and validates only the idxd->evl pointer before deallocation. Distribution maintainers have backported the change to supported stable kernel branches.

Workarounds

  • Unload the idxd driver with modprobe -r idxd on systems that do not require Intel Data Streaming Accelerator functionality.
  • Restrict permissions on /sys/bus/dsa/drivers/idxd/ sysfs entries to root-only access to prevent unprivileged users from triggering bind cycles.
  • Schedule reboots to reclaim leaked kernel memory on systems where patching cannot be applied immediately.
bash
# Verify kernel version and idxd driver status
uname -r
lsmod | grep idxd

# Unload idxd driver if Intel DSA is not required
sudo modprobe -r idxd

# Monitor kernel slab memory for leak indicators
watch -n 5 'grep -E "Slab|SReclaimable|SUnreclaim" /proc/meminfo'

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.