[CVE-2026-98804][MODERATE 7.0] net: page_pool: fix use-after-free in page_pool_recycle_ring_bulk() [ Upstream

[CVE-2026-98804][MODERATE 7.0] net: page_pool: fix use-after-free in page_pool_recycle_ring_bulk() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98804
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: net: page_pool: fix use-after-free in page_pool_recycle_ring_bulk() [ Upstream
Commit: f78d45d5f1ac4141a03f033141368671da4293e4
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f78d45d5f1ac4141a03f033141368671da4293e4
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98804
Analysis date: Sat, 24 Oct 2026 09:50:18 -0400
ActionableScore: 4
ActionableScore lower bound: unknown
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
A lock-ordering race permits a statistics increment through a freed page-pool pointer, causing a constrained post-free slab write with unresolved exploit leverage.

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

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

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-98804	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98804 CHECK WITH IMPACT FROM ORIG NN IMPORTANT | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=3 LEGACY=MODERATE_KPANIC RESULT=SAME V39_AEGIS_ONE_STEP_UP=MODERATE->MODERATE_KPANIC (final reconciliation agrees; DECISION: both 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-362;*CWE-672;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7';DESCR 'With CONFIG_PAGE_POOL_STATS enabled page_pool_recycle_ring_bulk could release the producer lock before recycle_stat_add accessed the page pool. If the same operation returned the last inflight netmems then page_pool_release could pass the lock barrier and free the pool first. The later statistics update performs a constrained write through a freed pool pointer and can cause kernel memory corruption or a crash. For the CVSS the PR:L value is selected because reliable adversarial triggering normally requires a local user or process able to coordinate page pool destruction or network device reconfiguration with recycling activity. AC:H reflects the race window. Remote traffic may influence recycling timing but is not sufficient evidence of direct remote reachability or control over pool destruction. Automated impact decision path. The original SimpleNet classifier selected IMPORTANT. The primary LLM estimated paranoid CVSS 7 and the production ActionableScore returned 4 with recommendation Actionable Moderate / Strong Important candidate requiring manual review. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were ActionableScore thresholds stage IMPORTANT to MODERATE_KPANIC because the ActionableScore threshold rule was applied. KP and FD specialist checks stage MODERATE_KPANIC to MODERATE because KP specialist did not establish a qualifying panic. final reconciliation stage MODERATE to MODERATE_KPANIC because the cross model evidence reconciliation rule 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 has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN5 and DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP and V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 2.5 and ActionableScore 3 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 MODERATE_KPANIC.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 4)	MAYBE	REMOTE UAF  DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN5 DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP KPANIC V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED	-	-	checked

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

ActionableScore=4
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 base score: 2.
* Conservative score: 4. REAL UAF FLOOR 4 applied: 2 -> 4.
* Raw paranoid score: 2.
* Paranoid score: 4. No additional exploit primitive is established.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

* +2 Real UAF: after the producer lock is dropped, pool destruction can pass its barrier and free `pool`; `recycle_stat_add(pool, ring, i)` then updates statistics through the stale pointer.
* +1 Reliable kernel crash/strong DoS: a write into freed slab storage plausibly causes memory corruption or a kernel fault.
* -1 Hard race: execution requires recycling the final inflight netmems and pool release/free to occur in the narrow interval before the statistics update.
* No privilege penalty: host-admin-equivalent privilege is not positively established.
* No separate overwrite bonus: the constrained post-free statistics write is the stale use already scored by the UAF signal.
* No controlled reclaim, attacker-selected target/payload, arbitrary write, disclosure, authorization bypass, or LPE is shown.
* No second Availability point: it would duplicate the same crash.
* No repeated release/refcount signal exists; FLOOR 5 therefore does not apply.

3. Reachability analysis

Network activity can influence recycling, while pool destruction or device reconfiguration controls the lifetime transition. The supplied evidence does not establish that one below-host-admin actor controls the complete race, nor that host administration is necessarily required. Direct remote triggering and complete namespace-scoped capability reachability are unproven. `CONFIG_PAGE_POOL_STATS=y` is required. No special hardware requirement is established.

4. Primitive and severity reading

This is a real post-lifetime write to a freed `struct page_pool`, not merely a stale read or guard-detected condition. The pool is being destroyed, but the statistics update may mutate reclaimed slab storage before any guaranteed fault. That is CLASS_B uncontrolled post-free corruption, not CLASS_A because reclaim, replacement contents, target selection, and useful adjacent-object corruption are not demonstrated.

The shown effect is possible kernel corruption/crash. Exploitation beyond that remains unresolved. ImportantCandidate is YES because the stale operation is an actual write into potentially reallocated kernel storage; mandatory review is warranted even though Important severity is not proven. Auto-downgrade is disallowed because reducing it to crash-only would discard this unresolved post-free corruption primitive.

5. One-sentence report phrase

A lock-ordering race permits a statistics increment through a freed page-pool pointer, causing a constrained post-free slab write with unresolved exploit leverage.

6. Manual review advice

MANUAL CHECK REQUIRED

Confirm complete attacker reachability, slab-cache reuse behavior, written offsets and widths, and whether pool destruction can be induced below host-admin privilege.

7. Call-site confidence

Call-site confidence: medium

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

Patch: net: page_pool: fix use-after-free in page_pool_recycle_ring_bulk() [ Upstream
Commit: f78d45d5f1ac4141a03f033141368671da4293e4
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f78d45d5f1ac4141a03f033141368671da4293e4

Changed files:
  net/core/page_pool.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=f78d45d5f1ac4141a03f033141368671da4293e4

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

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

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:L/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: unknown
  Paranoid ActionableScore: 4

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