[CVE-2026-98443][IMPORTANT] xfs: fix cursor and pointer handling when recovering iunlink buckets [ Upstream

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

CVE: CVE-2026-98443
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: YES
Patch: xfs: fix cursor and pointer handling when recovering iunlink buckets [ Upstream
Commit: 8c9d5b8a96d6b93eb24e07b4163c89341ba29bd1
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8c9d5b8a96d6b93eb24e07b4163c89341ba29bd1
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98443
Analysis date: Mon, 19 Oct 2026 05:30:22 -0400
ActionableScore: 6
ActionableScore lower bound: 5
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
XFS log recovery can release the same inode reference twice after an inodegc flush failure, creating a concrete use-after-free and post-lifetime refcount mutation that requires mandatory exploitation review.

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

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

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: IMPORTANT
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-98443	IMPORTANT	https://www.kernelcve.org/list/?q=CVE-2026-98443 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=IMPORTANT RESULT=DIFF INDEPENDENT_LEGACY=IMPORTANT INDEPENDENT_RESULT=DIFF TEMP_KPANIC_MERGE=IMPORTANT_WINS_DISAGREEMENT PRE_MERGE_LEGACY=IMPORTANT (final Legacy and Aegis differ; FINAL: IMPORTANT, Aegis: MODERATE_KPANIC)	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-401;CWE-682;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7';DESCR 'xlog_recover_iunlink_bucket can retain prev_ip after xfs_irele and use the stale inode reference again if xfs_inodegc_flush fails during XFS log recovery. This creates a use-after-free and repeated release candidate on an error path, while related pointer ordering errors can leak the current inode reference or create self-referential i_prev_unlinked entries. For the CVSS the PR:L reflects the paranoid case where a local user can influence unlink workload and inode state on an accessible XFS filesystem. Reliable triggering still requires log recovery and an inodegc flush failure, so AC:H is appropriate and administrative control may be required in typical deployments. The issue is not network reachable. Impact is at least a local denial of service through filesystem recovery failure or kernel crash. In the worst case the stale inode lifetime handling may permit confidentiality and integrity impact through memory corruption, although practical privilege escalation is not demonstrated. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 7 and the production ActionableScore returned 6 with recommendation Actionable Moderate / Strong Important candidate requiring manual review. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage LOW to MODERATE_KPANIC because the ActionableScore threshold rule was applied. ActionableScore thresholds stage MODERATE_KPANIC to IMPORTANT because the ActionableScore threshold rule was applied. KP and FD specialist checks stage IMPORTANT to IMPORTANT because a specific evidence based protection or manual review veto was applied. The legacy KP specialist produced a review artifact and its decision was processed by the applicable KP rules. The legacy FD or DH downgrade specialist produced a review artifact and its decision was processed by the applicable downgrade and preservation rules. Exact triggered rule markers were INCREASED_TO_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4 and INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHERTHAN5 and V33_ACTIVE_STATE_BOUNDARY_CANDIDATE and IMPORTANT_CANDIDATE_MANUAL_REVIEW and KP_ONLY_DOWNGRADE_VETO and TEMP_KPANIC_MERGE_IMPORTANT_WINS. The independent weaker Aegis shadow evaluated CVSS 1.9 and ActionableScore 1 with primitive class CLASS_B and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is IMPORTANT.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 6)	MAYBE	DISK LEAK UAF LINUS  KPANIC INCREASED_TO_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4 KPANIC INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHERTHAN5 V33_ACTIVE_STATE_BOUNDARY_CANDIDATE IMPORTANT_CANDIDATE_MANUAL_REVIEW KP_ONLY_DOWNGRADE_VETO TEMP_KPANIC_MERGE_IMPORTANT_WINS	-	-	checked

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

ActionableScore=6
ActionableScoreLower=5
PrimitiveClass=CLASS_B
RealUAF=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=YES
ManualReview=REQUIRED
AutoDowngradeAllowed=NO
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

## 1. ActionableScore

* Raw conservative score: 5
* Conservative score: 5
* Raw paranoid score: 6
* Paranoid score: 6
* No cap changed either score. The repeated-release FLOOR 5 applies conceptually but does not change the conservative raw score.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

## 2. Signal breakdown

Conservative positive signals:

* +2 Real UAF or lifetime violation. `xfs_irele(prev_ip)` can end the inode reference lifetime, but `prev_ip` remains non-NULL and reachable after the release.
* +1 Concrete repeated release or refcount mutation. If `xfs_inodegc_flush()` fails, control reaches the final cleanup block and calls `xfs_irele(prev_ip)` again on the exact same potentially dangling reference.
* +1 Concrete persistent reference leak. The current `ip` reference is leaked on the failed flush path in the vulnerable code.
* +1 Important filesystem path. The defects affect XFS unlinked-inode processing during journal recovery.

Paranoid signal:

* +1 Unresolved post-free lifetime mutation. The second `xfs_irele()` can perform a write-like refcount or lifetime mutation after the first release may already have ended the original inode lifetime. This is grounded in the visible control flow and is not based merely on theoretical allocator reuse.

Repeated-release checks:

* First release can end lifetime: yes.
* Exact same reference survives: yes, because `prev_ip` was not cleared.
* Second operation mutates lifetime or refcount: yes, through the second `xfs_irele(prev_ip)`.
* Concrete repeated-release signal awarded: yes, +1.
* Paranoid repeated-refcount leverage awarded: yes, +1.
* FLOOR 5 checked: yes. It does not alter the raw conservative score of 5.

Not awarded:

* No crash point. The commit establishes UAF problems but does not document a reproduced Oops or panic.
* No controlled reclaim, attacker-shaped replacement object, arbitrary write, callback control, disclosure, or demonstrated LPE.
* No separate structured stale-object leverage point. The relevant stale operation is already counted as the concrete second lifetime mutation.
* No Weak LPE point for the same repeated-release fact.
* No confidentiality or integrity point based only on hypothetical reclaimed-memory corruption.
* No unprivileged-trigger bonus because the complete recovery and flush-failure trigger is unresolved.
* No metadata-corruption bonus. Self-referential `i_prev_unlinked` entries are established, but the commit states that these loops do not surface because each inode is flushed immediately.
* NEW52 B5-R does not apply because no retry-accumulated heap OOB write exists.
* NEW53 B3-PENDING does not apply because no shared-backing write exists.
* V33 and V32 do not apply because no attacker-controlled networking metadata write exists.
* NEW54 B4-PENDING does not apply because there is no authorization decision or DENY-to-ALLOW bypass.

## 3. Reachability analysis

The vulnerable function runs while recovering XFS unlinked-inode buckets. Triggering the repeated release requires an existing multi-inode iunlink chain, successful inode loading, release of `prev_ip`, and a subsequent `xfs_inodegc_flush()` failure.

An ordinary user may influence normal create and unlink workload on an accessible XFS filesystem, but the supplied evidence does not establish that such a user can independently force journal recovery or the required inodegc flush failure. Mount and recovery are commonly administrator-controlled, but host-admin privilege is not positively established as a necessary attacker prerequisite by the supplied call path. Therefore `HostAdminRequired=UNKNOWN`.

No complete user-namespace or mount-namespace path is established, so `NamespaceScopedPrivilege=UNKNOWN`. There is no network trigger, special hardware prerequisite, or timing race. This is an ordered error-path sequence rather than a narrow race.

## 4. Primitive and severity interpretation

The exact primitive is:

`xfs_irele(prev_ip)`
followed by an inodegc flush failure
followed by another `xfs_irele(prev_ip)` on the same uncleared reference.

The inode is an active structured, reference-counted kernel object. The vulnerable use occurs in recovery error handling, but it is not merely a stale field read that immediately faults. The second operation can actively mutate lifetime state after the first release may have destroyed the object. This is category B repeated lifetime corruption and therefore `PrimitiveClass=CLASS_B`, not crash-only Class C.

The demonstrated defects are a UAF candidate, repeated inode-reference release, leaked current inode reference, and incorrect unlinked-list cursor state. Controlled reclaim, arbitrary kernel read or write, privilege escalation, and a reliable kernel crash are not demonstrated.

`ImportantCandidate=YES` because the concrete second lifetime mutation leaves meaningful post-lifetime corruption leverage unresolved. `AutoDowngradeAllowed=NO` because automatically reducing the issue to an ordinary recovery failure would discard that established repeated-release primitive. This is not independently proven Important severity or Class A.

## 5. One-sentence report phrase

XFS log recovery can release the same inode reference twice after an inodegc flush failure, creating a concrete use-after-free and post-lifetime refcount mutation that requires mandatory exploitation review.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

The exact same reference can survive an initial lifetime-ending release and reach a second `xfs_irele()` operation, while controlled reclaim and practical attacker reachability remain unresolved.

## 7. Call-site confidence

Call-site confidence: high

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

Patch: xfs: fix cursor and pointer handling when recovering iunlink buckets [ Upstream
Commit: 8c9d5b8a96d6b93eb24e07b4163c89341ba29bd1
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8c9d5b8a96d6b93eb24e07b4163c89341ba29bd1

Changed files:
  fs/xfs/xfs_log_recover.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=8c9d5b8a96d6b93eb24e07b4163c89341ba29bd1

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

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

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: 5
  Paranoid ActionableScore: 6

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

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