Vulnerability · Published May 28, 2026 · Assigned by Linux

CVE-2026-46210media: iris: fix use-after-free of fmt_src during MBPF check

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.1%top 97.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: media: iris: fix use-after-free of fmt_src during MBPF check During concurrency testing, multiple instances can run in parallel, and each instance uses its own inst->lock while the core->lock protects the list of active instances. The race happens because these locks cover different scopes, inst->lock protects only the internals of a single instance, while the Macro Blocks Per Frame (MBPF) checker walks the core list under core->lock and reads fields like fmt_src->width and fmt_src->height. At the same time, iris_close() may free fmt_src and fmt_dst under inst->lock while the instance is still present in the core list. This allows a situation where the MBPF checker, still iterating through the core list, reaches an instance whose fmt_src was already freed by another thread and ends up dereferencing a dangling pointer, resulting in a use-after-free. This happens because the MBPF checker assumes that any instance in the core list is fully valid, but the freeing of fmt_src and fmt_dst without removing the instance from the core list is not correct. The correct ordering is to defer freeing fmt_src and fmt_dst until after the instance has been removed from the core list and all teardown under the core lock has completed, ensuring that no dangling pointers are ever exposed during MBPF checks.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.0.9-1DEBIAN-CVE-2026-46210
Ubuntu:26.04:LTSlinux7.0.0-28.28UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-aws7.0.0-1009.9UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-gcp7.0.0-1008.8UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-gke7.0.0-1003.4UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-ibm7.0.0-1010.10UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1016.16UBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2016.16UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1009.9UBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-oracle7.0.0-1008.8UBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-raspi7.0.0-1015.15UBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-realtime7.0.0-28.28.1UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46210
Ubuntu:26.04:LTSlinux-riscv7.0.0-28.28.1UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-46210
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-46210
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-46210

Affected products (as reported)

VendorProductVersions
Linux Linux 5ad964ad5656668399f00c76707f0d063b64a4b1 – before 96889fcdb0988108a19a29b0467717a503651a735ad964ad5656668399f00c76707f0d063b64a4b1 – before 494ffd1712a588e590e6b1e9f876a8c8b24a91805ad964ad5656668399f00c76707f0d063b64a4b1 – before 3d9593ad1a58c5acc3e5fa2a48222bb7632e6812
Linux Linux 6.18

References