Skip to content
Fencer Vulns
medium 5.5

CVE-2025-21770 json

iommu: Fix potential memory leak in iopf_queue_remove_device()

published 2025-02-27 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-5165

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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

iommu: Fix potential memory leak in iopf_queue_remove_device()

The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf's with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue.

However, it fails to release the group structure that represents a group of iopf's awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf's.

Fix it by calling iopf_free_group() after the iopf group is responded.

Patch / fix

  • Linux Linux 6.12.16, 6.13.4, 6.14
  • linux Debian 14, Debian 13 6.12.16-1

debian advisories DEBIAN-CVE-2025-21770

  • linux-gcp-6.11 Ubuntu 24.04 LTS 6.11.0-1015.15~24.04.1
  • linux-hwe-6.11 Ubuntu 24.04 LTS 6.11.0-26.26~24.04.1
  • linux-oem-6.11 Ubuntu 24.04 LTS 6.11.0-1022.22
  • linux-azure-6.11 Ubuntu 24.04 LTS 6.11.0-1015.15~24.04.1
  • linux-nvidia-6.11 Ubuntu 24.04 LTS 6.11.0-1010.10
  • linux-lowlatency-hwe-6.11 Ubuntu 24.04 LTS 6.11.0-1014.15~24.04.1

ubuntu advisories UBUNTU-CVE-2025-21770

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.8.1
  • kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.8.1
  • kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.8.1
  • kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.6.1
  • kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.6.1
  • kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.6.1
  • kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.6.1
  • kernel-zfcpdump SLE Module for Basesystem 15 SP7 6.4.0-150700.53.6.1

suse advisories SUSE-SU-2025:02333-1SUSE-SU-2025:02307-1SUSE-SU-2025:02254-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-21770 updated cvss 5.5

kernel: iommu: Fix potential memory leak in iopf_queue_remove_device()

  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
13 mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.