← All Advisories
Reported from OT-Advisories.com as of

Linux Linux Kernel Use-After-Free Rated 7.8 CVSS

Last refreshed2026-10-15

Status: UPDATED  |  Advisory ID: CVE-2026-46210

Key Details

CVECVE-2026-46210
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-15
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-416 (Use After Free)
Exploitation prediction (EPSS)
0.17% probability of exploitation in the next 30 days (5% percentile) -- FIRST.org's EPSS model.

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-46210
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-46210
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.