---
id: CVE-2026-31440
title: 'dmaengine: idxd: Fix leaking event log memory'
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  dmaengine: idxd: Fix leaking event log memory

  During the device remove process, the device is reset, causing the
  configuration registers to go back to their default st…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 <
    695b491dc3f20365fd5821f22e25dbe3c1c20cbc
  - >-
    Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 <
    d94f9b0ba28a205caf95902ee88b42bdb8af83d0
  - >-
    Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 <
    facd0012708e942fc12890708738aebde497564e
  - >-
    Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 <
    9dfa00967e6ef43a9dd0887fe5c3a721a39da92e
  - >-
    Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 <
    ee66bc29578391c9b48523dc9119af67bd5c7c0f
  - Linux 6.4
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T21:33:27.403110Z'
published: '2026-04-22'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T21:33:51.748Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-31440'
references:
  - url: 'https://git.kernel.org/stable/c/695b491dc3f20365fd5821f22e25dbe3c1c20cbc'
  - url: 'https://git.kernel.org/stable/c/d94f9b0ba28a205caf95902ee88b42bdb8af83d0'
  - url: 'https://git.kernel.org/stable/c/facd0012708e942fc12890708738aebde497564e'
  - url: 'https://git.kernel.org/stable/c/9dfa00967e6ef43a9dd0887fe5c3a721a39da92e'
  - url: 'https://git.kernel.org/stable/c/ee66bc29578391c9b48523dc9119af67bd5c7c0f'
tags:
  - cve.org
epss: 0.00122
epssPercentile: 0.01983
ingestedAt: '2026-11-05T22:38:32.137Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

dmaengine: idxd: Fix leaking event log memory

During the device remove process, the device is reset, causing the
configuration registers to go back to their default state, which is
zero. As the driver is checking if the event log support was enabled
before deallocating, it will fail if a reset happened before.

Do not check if the support was enabled, the check for 'idxd->evl'
being valid (only allocated if the HW capability is available) is
enough.

## Affected

- `Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 < 695b491dc3f20365fd5821f22e25dbe3c1c20cbc`
- `Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 < d94f9b0ba28a205caf95902ee88b42bdb8af83d0`
- `Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 < facd0012708e942fc12890708738aebde497564e`
- `Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 < 9dfa00967e6ef43a9dd0887fe5c3a721a39da92e`
- `Linux >= 244da66cda359227d80ccb41dbcb99da40eae186 < ee66bc29578391c9b48523dc9119af67bd5c7c0f`
- `Linux 6.4`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
