[CVE-2026-53120][MODERATE 7.0] PCI: use generic driver_override infrastructure [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-53120
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: PCI: use generic driver_override infrastructure [ Upstream
Commit: dfe950d9464cad609f3b118c6203e2708055bc61
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dfe950d9464cad609f3b118c6203e2708055bc61
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53120
Analysis date: Wed, 24 Jun 2026 15:56:52 -0400
ActionableScore: 5
ActionableScore lower bound: 2
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
PCI driver matching could race with driver_override update or release, causing a kernel use-after-free in a local device-management path that is usually privileged but may be reachable by delegated VFIO or container device managers.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53120 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53120

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-53120	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-362;CWE-667;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7';DESCR '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.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 4)	YES	OOB LOCK UAF HARDWARE LINUS  DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN7 DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=5
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 5
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Paranoid score signals:

* Memory corruption, weak primitive: +1
  The patch explicitly describes a UAF caused by unlocked access to `driver_override` during PCI driver matching. The primitive is a stale string pointer dereference in `strcmp()`, not a demonstrated write or controlled object replacement.

* Real lifetime corruption: +1
  The bug is a real lifetime issue: `driver_override` can be updated or freed while another path reads it without the required locking.

* Reliable kernel crash / strong DoS: +1
  A stale pointer dereference in PCI matching can plausibly crash the kernel, especially if freed memory is reused or unmapped.

* Local trigger under delegated device management: +1
  In normal deployments the trigger is privileged, but in VFIO, container root, service-account, or device-management setups, PCI binding controls may be delegated to a less-than-full-root actor.

* Privileged kernel/device-management memory corruption path: +1
  The race occurs in PCI driver binding and matching, a trusted kernel device-management path.

* Broad/default/common subsystem: +1
  PCI is a common subsystem, although the vulnerable operation is a control-plane path rather than a packet or syscall fast path.

Negative signals:

* Hard or unreliable race / special timing required: -1
  Triggering depends on a race between driver matching and `driver_override` update or release.

* Requires admin/root/CAP-like privileges in typical deployments: -2 for conservative score only
  Writing PCI `driver_override`, binding, unbinding, or forcing reprobe is usually restricted to root or a privileged device manager.

Not awarded:

* Remote reachable: +0
  No network trigger is present.

* Strong LPE plausibility: +0
  The patch shows UAF, but not attacker-controlled reclaim, write-after-free, callback dispatch, type confusion, or refcount takeover.

* Confidentiality / Integrity impact: +0 conservative
  No concrete info leak or write primitive is shown. Paranoid handling still keeps this manually actionable because it is kernel UAF in a device-management path.

## 3. Reachability analysis

The realistic trigger is local PCI device-management activity: changing `driver_override`, binding or unbinding drivers, reprobe paths, VFIO-related assignment flows, or Xen pciback style binding. In typical host deployments this requires root or equivalent administrative privileges, so the conservative score is low.

Namespaces and containers can matter. If a reduced-capability root, container root, VFIO manager, or service account can control PCI binding or assignment without full host-root equivalence, the practical PR barrier is lower. The bug is not remotely reachable by packets or ordinary network traffic.

The path is present in a broadly deployed subsystem, but the vulnerable operation is not default attacker-facing for ordinary local users.

## 4. Severity interpretation

This is not an ordinary cleanup bug because the commit explicitly identifies a UAF. However, the demonstrated primitive is weak: an unlocked read of a freed string pointer during a race, with no shown controlled reclaim, overwrite, or callback hijack.

Conservatively, this behaves like a privileged local DoS / weak UAF race. Paranoid triage should treat it as Actionable Moderate because kernel UAFs in PCI/VFIO-style control paths can be underestimated when device-management privileges are delegated.

## 5. One-sentence report phrase

PCI driver matching could race with driver_override update or release, causing a kernel use-after-free in a local device-management path that is usually privileged but may be reachable by delegated VFIO or container device managers.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the bug class is a kernel UAF race in PCI driver binding/matching. Even though typical triggering requires privileged device-management access and no strong exploitation primitive is demonstrated, delegated PCI/VFIO management makes this unsuitable for automatic closure.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: PCI: use generic driver_override infrastructure [ Upstream
Commit: dfe950d9464cad609f3b118c6203e2708055bc61
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dfe950d9464cad609f3b118c6203e2708055bc61

Changed files:
  drivers/pci/pci-driver.c
  drivers/pci/pci-sysfs.c
  drivers/pci/probe.c
  drivers/vfio/pci/vfio_pci_core.c
  drivers/xen/xen-pciback/pci_stub.c
  include/linux/pci.h

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dfe950d9464cad609f3b118c6203e2708055bc61

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53120 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53120

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 2
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).