[CVE-2026-53325][LOW] agp/amd64: Fix broken error propagation in agp_amd64_probe()

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

CVE: CVE-2026-53325
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: agp/amd64: Fix broken error propagation in agp_amd64_probe()
Commit: 53483a9f4ee9eeb18aa866ec16cce79e136987e1
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=53483a9f4ee9eeb18aa866ec16cce79e136987e1
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53325
Analysis date: Mon, 29 Jun 2026 01:50:44 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-53325	LOW	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';CWE-252;**CWE-476;CWE-754;BEST CVSS score: '4.4';DESCR 'A NULL pointer dereference can occur in the AMD64 AGP probe path because agp_amd64_probe checked cache_nbs only against -1 instead of treating any negative error as a failure. In a virtualized environment without a physical AMD northbridge, cache_nbs may return ENODEV, the driver can continue initialization, and amd64_fetch_size may dereference a NULL value returned by node_to_amd_nb(0). For the CVSS the PR:H is used because reliable triggering normally requires administrative control over driver loading, device binding, or boot time hardware configuration. The issue is not network reachable and affects the local kernel or guest where the driver is probed. Impact is denial of service via kernel crash only, with no supported path to information disclosure or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)	YES	DANGER NULLPTR HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	guess

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

ActionableScore=0

1. ActionableScore
* Conservative score: 0
* Paranoid score: 0
* Final recommended bucket: **Ordinary Moderate / Low-like**

2. Signal breakdown
* Reliable kernel crash / strong DoS: +1. The described failure is a GPF or NULL pointer dereference in `amd64_fetch_size()` after probe continues without AMD northbridge state.
* Requires admin/root/CAP-level control in typical deployments: -2. Reliable triggering normally requires driver loading, device binding, boot-time module configuration, or equivalent administrative control.
* Legacy / non-default execution mode: -1. AGP AMD64 probing is a legacy hardware path and the reported condition depends on an unusual virtualized environment without the expected AMD northbridge.
* No memory corruption primitive: +0. The patch shows NULL dereference caused by bad error propagation, not UAF, OOB write, type confusion, refcount misuse, or attacker-controlled overwrite.
* No confidentiality or integrity impact: +0. There is no supported read disclosure, data modification, privilege escalation, or policy bypass.

3. Reachability analysis
The bug is local to the kernel instance where the AMD64 AGP driver is probed. It is not network reachable. A normal unprivileged local user should not be able to trigger it reliably unless they can influence module loading or PCI driver binding through an already privileged service. Namespaces and containers do not materially lower the requirement in typical deployments because hardware driver binding is not delegated to unprivileged containers. The path is configuration and hardware dependent, mainly relevant to legacy AGP support and specific virtualized setups.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like kernel DoS issue. The realistic impact is a local kernel crash during driver probe or initialization. Theoretical privilege escalation is not supported by the patch because the failure mode is a NULL pointer dereference with no reclaim, stale object reuse, write-after-free, callback dispatch, or controllable corruption sink.

5. One-sentence report phrase
Broken error propagation in `agp_amd64_probe()` can allow AMD64 AGP initialization to continue without required northbridge state, causing a local NULL pointer dereference and kernel crash when the driver is probed in affected virtualized or legacy hardware configurations.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. The issue is admin-triggered, not network reachable, legacy/configuration dependent, and the patch supports DoS-only impact without a concrete memory corruption or privilege escalation primitive.

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

Patch: agp/amd64: Fix broken error propagation in agp_amd64_probe()
Commit: 53483a9f4ee9eeb18aa866ec16cce79e136987e1
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=53483a9f4ee9eeb18aa866ec16cce79e136987e1

Commit description:

A NULL pointer dereference was observed in the AMD64 AGP driver when
running in a virtualized environment (e.g. qemu/kvm) without a physical
AMD northbridge. The crash occurs in amd64_fetch_size() when attempting
to dereference the pointer returned by node_to_amd_nb(0).

The root cause of this crash is broken error propagation in
agp_amd64_probe(): When no AMD northbridges are found, cache_nbs()
correctly returns -ENODEV. However, the probe function erroneously
checks the return value against exactly -1, rather than < 0.

As a result, the hardware absence error is masked, allowing the driver
to improperly proceed with initialization. It eventually calls
agp_add_bridge(), which invokes amd64_fetch_size(). Since the hardware
does not exist, node_to_amd_nb(0) returns NULL, leading to a General
Protection Fault (GPF) when accessing its ->misc member.

Fix the issue by correcting the error check in agp_amd64_probe() to
abort properly when cache_nbs() returns any negative error code. This
prevents the driver from erroneously proceeding without hardware, thereby
avoiding the subsequent NULL pointer dereference at its source.

Fixes: a32073b ("[PATCH] x86_64: Clean and enhance up K8 northbridge access code")
Signed-off-by: Mingyu Wang <25181214217@stu.xidian.edu.cn>
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Reviewed-by: Lukas Wunner <lukas@wunner.de>
Cc: stable@vger.kernel.org # v2.6.18+
Link: https://patch.msgid.link/20260504074823.99377-1-w15303746062@163.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/char/agp/amd64-agp.c

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=53483a9f4ee9eeb18aa866ec16cce79e136987e1

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

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

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:L/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.4

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: 0

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