[CVE-2026-80917][LOW] PCI: host-generic: Fix NULL pointer dereference on 32-bit CAM systems

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

CVE: CVE-2026-80917
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: PCI: host-generic: Fix NULL pointer dereference on 32-bit CAM systems
Commit: 5e52eb0290f66ba0732956dcb1e365b5ca3c5108
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5e52eb0290f66ba0732956dcb1e365b5ca3c5108
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80917
Analysis date: Wed, 09 Sep 2026 13:17:08 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
Manual review required: NO

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

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

CVE-2026-80917	LOW	https://www.kernelcve.org/list/?q=CVE-2026-80917 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-665;CWE-754;BEST CVSS score: '4.1';DESCR 'A NULL pointer dereference can occur in the generic PCI CAM host path on 32 bit systems because pci_host_cam_generic used CAM ops without add_bus and remove_bus callbacks. On such systems pci_ecam_create maps config space per bus and expects add_bus to populate cfg winp for each bus, so pci_ecam_map_bus can later return a valid base for config reads. Without that per bus mapping the first PCI config access during enumeration can dereference a NULL base and crash the kernel. For the CVSS the PR:H is used because reliable triggering normally requires administrator control over platform firmware device tree or PCI host controller configuration. The issue is not network reachable and is tied to affected 32 bit CAM platform setup. Impact is denial of service through a boot time or enumeration time kernel crash.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	YES	OOB DANGER NULLPTR KERNEL_PANIC_PLUS_UAF HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=YES
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 1
* Conservative score: 1. No floor or cap applied.
* Raw paranoid score: 1
* Paranoid score: 1. No floor or cap applied.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

Positive signals:

* +1 Reliable kernel crash / strong DoS. The commit shows a concrete NULL pointer dereference during PCI bus enumeration on affected 32-bit CAM systems.

Negative / limiting signals considered but not separately scored:

* Host-admin-equivalent or platform-control requirement is positively supported. Reliable triggering normally requires control over platform firmware, device tree, PCI host configuration, or boot-time hardware setup.
* Special platform dependency is present. The issue is tied to 32-bit hosts using pci-host-cam-generic with dynamically mapped CAM/ECAM windows.
* No UAF, double free, refcount corruption, OOB access, arbitrary write, controlled reclaim, security-boundary bypass, or information disclosure is established.
* No extra Availability point is awarded because the only demonstrated impact is the same kernel crash during enumeration.
* No Confidentiality or Integrity impact is awarded because the patch supports only a NULL base dereference and crash.

3. Reachability analysis

The vulnerable path is reached during PCI host probing and bus enumeration. The attacker model is not an ordinary local user, namespace user, or remote network attacker.

Reliable triggering requires an affected 32-bit CAM platform and a platform description using pci-host-cam-generic. Changing that condition normally requires host administrator, firmware, device tree, or hardware configuration control. There is no evidence that an unprivileged user can instantiate the affected PCI host controller path at runtime.

Namespace-scoped privilege does not apply. No network namespace, user namespace, or delegated capability path is involved. No remote packet or device-independent network trigger is established.

There is no race. The failure is deterministic on affected platform configuration when per-bus mappings are not populated before the first PCI config read.

4. Primitive and severity interpretation

The exact primitive is a NULL pointer dereference in PCI config access. The missing add_bus callback means cfg->winp[] is not populated for per-bus mappings on 32-bit CAM systems. pci_ecam_map_bus then uses a NULL base for config space access, leading to an Oops during enumeration.

This is Class C invalid-state / crash behavior. It is not an active structured UAF, not fixed stale storage, and not a repeated release/refcount mutation. The demonstrated consequence is boot-time or enumeration-time denial of service on affected platforms.

Speculative consequences beyond DoS are not supported. There is no meaningful exploitation leverage beyond crash, no attacker-controlled payload or target, and no evidence of privilege escalation.

ImportantCandidate=NO because the primitive is a constrained NULL dereference without memory corruption or boundary bypass. AutoDowngradeAllowed=YES because no unresolved Important-grade primitive remains.

Likely operational severity is low to ordinary moderate, mainly a platform reliability issue for affected 32-bit CAM systems.

5. One-sentence report phrase

A NULL pointer dereference in the generic PCI CAM host path can crash affected 32 bit systems during PCI enumeration when per bus config mappings are not initialized.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

The issue is a platform-specific NULL dereference DoS with no UAF, no memory corruption primitive, no network reachability, and no plausible below-host-admin trigger shown.

7. Call-site confidence

Call-site confidence: high

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

Patch: PCI: host-generic: Fix NULL pointer dereference on 32-bit CAM systems
Commit: 5e52eb0290f66ba0732956dcb1e365b5ca3c5108
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5e52eb0290f66ba0732956dcb1e365b5ca3c5108

Commit description:

On 32-bit systems the config space is too large to ioremap in one go, so
pci_ecam_create() maps each bus segment separately and relies on the
->add_bus callback (pci_ecam_add_bus) to populate the per-bus mapping in
cfg->winp[]. pci_ecam_map_bus() then uses that mapping as the base for
every config access.

The generic ECAM ops (pci_generic_ecam_ops) already provide the ->add_bus
and ->remove_bus callbacks, but the CAM (legacy) ops in pci-host-generic.c
do not. As a result, on a 32-bit host using "pci-host-cam-generic" the
per-bus mapping is never set up and the first config read dereferences a
NULL base, crashing during bus enumeration:

 Unable to handle kernel NULL pointer dereference at virtual address 00000800
 Oops [#1]
 CPU: 0 PID: 1 Comm: swapper Not tainted 6.9.7+ #43
 Hardware name: Digilent Nexys-Video-A7 RV32 (DT)
 epc : pci_generic_config_read+0x40/0xb0
  ra : pci_generic_config_read+0x2c/0xb0
 [<c038db9c>] pci_generic_config_read+0x40/0xb0
 [<c038da04>] pci_bus_read_config_dword+0x50/0xb0
 [<c0391e94>] pci_bus_generic_read_dev_vendor_id+0x3c/0x1ec
 [<c039245c>] pci_scan_single_device+0xa4/0x11c
 [<c0392570>] pci_scan_slot+0x9c/0x23c
 [<c039388c>] pci_scan_child_bus_extend+0x58/0x2f4
 [<c0393db0>] pci_scan_root_bus_bridge+0x64/0xe8
 [<c0393e54>] pci_host_probe+0x20/0xc8
 [<c03bc6f4>] pci_host_common_probe+0x144/0x1e4

Fix this by giving the CAM ops the same ->add_bus/->remove_bus callbacks.
Since pci_ecam_add_bus() and pci_ecam_remove_bus() are static to ecam.c,
move the CAM ops definition there as pci_generic_cam_ops (mirroring
pci_generic_ecam_ops) and export it for pci-host-generic.c to reference.

Fixes: 8fe55ef ("PCI: Dynamically map ECAM regions")
Signed-off-by: Steffen Persvold <spersvold@gmail.com>
[mani: removed timestamp from log]
Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20260709122446.3151899-1-spersvold@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/pci/controller/pci-host-generic.c
  drivers/pci/ecam.c
  include/linux/pci-ecam.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=5e52eb0290f66ba0732956dcb1e365b5ca3c5108

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

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

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: Not available
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.1

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: unknown
  Paranoid ActionableScore: 1

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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