cve.bz

CVE-2026-53120 linux linux kernel: Use After Free

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: PCI: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1]

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-53120 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53120?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53120?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53120 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.160
Linux6.126.12.91
Linux6.186.18.33
Linux7.07.0.10
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linuxno fix listedDEBIAN-CVE-2026-53120
Debian13linux6.12.94-1DEBIAN-CVE-2026-53120
Debian14linux7.0.10-1DEBIAN-CVE-2026-53120
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-53120
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-53120
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-53120
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-53120
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 41 moreno fix listedUBUNTU-CVE-2026-53120
Ubuntu24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-53120 USN-8728-2
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-53120
Ubuntu24.04:LTSlinux-gcp-7.0, linux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-53120 USN-8728-1 USN-8728-3
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-53120 USN-8569-1
Ubuntu24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-53120 USN-8663-1
Ubuntu24.04:LTSlinux-nvidia-tegra6.8.0-1035.38UBUNTU-CVE-2026-53120 USN-8781-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-53120
19 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernelno fix listedAZL-90303
Alpaquita23linux-ltsno fix listedBELL-CVE-2026-53120
Alpaquita25linux-lts6.12.92-r0BELL-CVE-2026-53120
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-53120

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

PCI driver matching could read driver_override without the device lock while another control path updates or frees the same string, creating a race based use-after-free in the kernel. The exposed primitive is an invalid dereference of freed memory during PCI driver matching, so the realistic impact is at least local denial of service via crash and the worst case may include confidentiality or integrity impact if the UAF can be shaped into stronger memory corruption. For the CVSS the PR:L is used for the paranoid score because some deployments delegate PCI device management to a reduced capability root, container root, service account, VFIO manager, or similar local actor rather than a full host administrator. The issue is local control plane reachable and not directly network reachable. Attack complexity is high because reliable triggering depends on a timing window between driver matching and override update or release.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelFix deferred
Red Hat Enterprise Linux 7kernel-rtFix deferred
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-53120.

References

Check your stackJSON