[CVE-2026-80533][LOW] xfs: don't walk off the end of a null sc->sa.agi_bp in AGI repair

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

CVE: CVE-2026-80533
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: xfs: don't walk off the end of a null sc->sa.agi_bp in AGI repair
Commit: 43b4ecbc948a2e441804c9d7b772deb6b2e44e3d
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=43b4ecbc948a2e441804c9d7b772deb6b2e44e3d
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80533
Analysis date: Wed, 26 Aug 2026 11:24:15 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
XFS AGI repair may dereference a NULL `sc->sa.agi_bp` after AGI verifier failure, allowing a privileged local repair operation on corrupted metadata to crash the kernel.

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

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

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-80533	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'XFS AGI repair can dereference a NULL sc sa agi_bp pointer when the AGI buffer verifier fails and the repair path continues with damaged metadata. This can crash the kernel during online repair of an XFS filesystem with corrupted or malicious AGI state. For the CVSS the PR:L in the paranoid score is used only for environments where a local user can indirectly cause a privileged scrub or repair service to process attacker influenced filesystem metadata. In the typical case PR:H is more realistic because XFS repair and scrub control is administrative. The issue is not network reachable. Impact is denial of service via kernel crash, with no clear UAF, OOB write, or privilege escalation primitive supported by the patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)	YES	DISK SIMPLEFIX LINUS  DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS_AND_CIANNH	YES	NO	checked

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

ActionableScore=2
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1
  The patch prevents a NULL pointer dereference of `sc->sa.agi_bp` when the AGI buffer verifier fails during XFS AGI repair.
* Important filesystem/storage path: +1
  The bug is in XFS online repair code for AGI unlinked inode metadata.
* Requires admin/root/CAP_* in typical deployments: -2
  Triggering this path normally requires administrative control of XFS scrub or repair operations and a corrupted filesystem state.

Conservative total: 1

Paranoid additional interpretation:

* Local unprivileged trigger: +1
  Only in a narrow model where a local user can influence filesystem metadata and a privileged scrub or repair service later processes it automatically.

Paranoid total: 2

Not awarded:

* No generic memory corruption signal. This is a NULL dereference, not UAF, OOB write, double free, or type confusion.
* No privilege escalation signal. The patch does not show controlled reclaim, overwrite, callback control, or object replacement.
* No confidentiality or integrity impact. The supported impact is crash only.
* No network reachability.

Call-site confidence: high. The changed dereference and the repair call context are visible in the supplied patch and commit message.

## 3. Reachability analysis

The realistic trigger is local and privileged. An administrator or privileged repair service must run XFS online repair against an XFS filesystem whose AGI verifier fails. A normal unprivileged user usually cannot directly invoke this repair path or create arbitrary AGI verifier failure conditions.

Namespaces and containers do not normally lower this to a broad unprivileged attack unless the environment delegates filesystem repair or scrub control to less privileged users. The path is not network reachable. The condition also depends on corrupted or malicious filesystem metadata, so it is not a broad default-exposure kernel path.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like DoS issue. The theoretical concern is kernel crash during filesystem repair, but the patch supports only NULL pointer dereference, not exploitable memory corruption. There is no demonstrated or strongly implied LPE primitive.

The issue should not be treated as Important-class without extra evidence of UAF, writable stale object access, filesystem ownership bypass, or attacker-controlled metadata corruption reachable from an unprivileged user.

## 5. One-sentence report phrase

XFS AGI repair may dereference a NULL `sc->sa.agi_bp` after AGI verifier failure, allowing a privileged local repair operation on corrupted metadata to crash the kernel.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: the patch shows a straightforward NULL pointer dereference in an administrative XFS repair path, with no supported UAF, OOB write, privilege escalation, information leak, or network trigger.

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

Patch: xfs: don't walk off the end of a null sc->sa.agi_bp in AGI repair
Commit: 43b4ecbc948a2e441804c9d7b772deb6b2e44e3d
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=43b4ecbc948a2e441804c9d7b772deb6b2e44e3d

Commit description:

LOLLM noticed a longstanding bug where xrep_iunlink_walk_ondisk_bucket
tries to walk ragi->sc->sa.agi_bp to rebuild the unlinked inode lists.
Unfortunately, it's possible for agi_bp to be null if the buffer
verifier fails, so we have to use ragi->agi_bp (which skips verifier
checks) instead.

Cc: stable@vger.kernel.org # v6.10
Fixes: ab97f4b ("xfs: repair AGI unlinked inode bucket lists")
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Assisted-by: LOLLM # finding obvious bugs
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  fs/xfs/scrub/agheader_repair.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=43b4ecbc948a2e441804c9d7b772deb6b2e44e3d

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

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

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:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.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: 1
  Paranoid ActionableScore: 2

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