[CVE-2026-98378][IMPORTANT] bpf: Skip unsettled links in link iterator [ Upstream

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

CVE: CVE-2026-98378
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: YES
Patch: bpf: Skip unsettled links in link iterator [ Upstream
Commit: 68930f8d40ab4c10ca3b019f076136758fd100a8
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=68930f8d40ab4c10ca3b019f076136758fd100a8
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98378
Analysis date: Fri, 09 Oct 2026 22:29:21 -0400
ActionableScore: 6
ActionableScore lower bound: 5
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-98378	IMPORTANT	https://www.kernelcve.org/list/?q=CVE-2026-98378 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=4 LEGACY=IMPORTANT RESULT=DIFF INDEPENDENT_LEGACY=IMPORTANT TEMP_KPANIC_MERGE=IMPORTANT_WINS_DISAGREEMENT PRE_MERGE_LEGACY=IMPORTANT (independent 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-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 'A race in the BPF link lifecycle can expose an unsettled link through the link iterator while its ID is still zero. If anon_inode_getfile() fails after the iterator takes a reference, the creator can remove and free the private link while the iterator retains a dangling reference. A later bpf_link_put() performs an 8 byte write to freed slab memory, resulting in a confirmed use after free and a possible kernel panic. For the CVSS the PR:L is selected because triggering requires local access to BPF link and iterator operations, which may be available through BPF related capabilities or delegated service permissions without full system administration. AC:H reflects the required race window and the need for the link creation path to fail before settlement. The issue is not network reachable. Impact is at least a local denial of service via kernel crash and in the worst case may allow confidentiality or integrity impact and privilege escalation through reuse of the freed slab object. Reliable exploitation beyond denial of service is not demonstrated and requires manual review.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 6)	MAYBE	BPF UAF HARDWARE LINUS  KPANIC INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK KPANIC INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHERTHAN5 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
* REAL UAF FLOOR 5 was checked and applies because the same dangling reference reaches a concrete lifetime mutation. It does not change the conservative score because the raw score is already 5.
* The BPF privileged control-plane exception was checked. It does not suppress FLOOR 5 because this is a concrete post-free refcount mutation rather than an ordinary cleanup-only stale dereference.
* The BPF conservative cap of 5 and paranoid cap of 6 were checked. Neither changes the corresponding raw score.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

Positive conservative signals:

* +2 Real UAF. The creator directly frees an unsettled `bpf_link` while the iterator retains a reference, and the later `bpf_link_put()` accesses freed slab storage.
* +1 Concrete repeated lifetime or refcount mutation. The initial direct free ends the object lifetime, the exact pointer remains in the iterator, and `bpf_link_put()` subsequently modifies lifetime metadata through that dangling pointer.
* +1 Reliable kernel crash or strong DoS. KASAN reports an eight-byte slab UAF write and the supplied trace reaches kernel panic with `panic_on_warn`.
* +1 Attacker-influenced lifetime sequence. A process with the necessary BPF access can drive link creation and iterator reads repeatedly, and these operations directly participate in publication, failed settlement, freeing, and stale use.

Additional paranoid signal:

* +1 Unresolved post-free refcount corruption. The stale operation itself performs a confirmed write-like refcount mutation after the original object has been freed. This is stronger than generic theoretical allocator reuse, although controlled reclaim is not established.

Concrete repeated-release checks:

* First lifetime operation can end lifetime: yes. The failed creator path directly frees the still-private link.
* Exact same reference survives: yes. The iterator retains the pointer obtained before settlement failed.
* Second operation mutates lifetime or refcount state: yes. `bpf_link_put()` performs the confirmed eight-byte write.
* Concrete repeated release or refcount +1 awarded: yes.
* Paranoid repeated-refcount leverage +1 awarded: yes, because KASAN confirms that the second operation writes through already freed storage.
* FLOOR 5 applied: applicable but numerically unnecessary because the raw conservative score is already 5.

Material signals not awarded:

* No controlled reclaim, object substitution, refcount takeover, arbitrary write, callback influence, or demonstrated LPE.
* No Structured stale-object leverage point. The only established stale structured operation is the refcount mutation already scored under the dedicated repeated-lifetime rule.
* No separate Weak LPE point for the same refcount mutation.
* No confidentiality or integrity point based only on theoretical reuse of freed memory.
* No additional Availability point because it would duplicate the same kernel panic.
* No local-unprivileged bonus because complete below-host-admin BPF reachability is not established.
* No privilege penalty because host-admin-equivalent privilege is also not positively established.
* No race penalty. The supplied evidence does not establish that the race is one-shot, externally uncontrollable, or materially difficult to retry.
* No remote-reachability point. The path is exercised through local BPF and iterator operations.
* B5-R is not applicable. There is no retry-accumulated heap OOB write.
* B3-PENDING is not applicable. There is no shared-backing write.
* B4-PENDING is not applicable. No authorization decision changes from DENY to ALLOW.

3. Reachability analysis

The evaluated attacker is a local process able to create the relevant BPF link and access the BPF link iterator. The creator must enter the interval after insertion into `link_idr` but before `bpf_link_settle()`, while `anon_inode_getfile()` subsequently fails. A concurrent iterator can then retain the unsettled link.

The supplied evidence does not resolve all BPF program-loading, iterator-creation, attachment, and capability checks. It therefore does not prove either ordinary unprivileged access or a host-admin-only requirement. `HostAdminRequired` and `NamespaceScopedPrivilege` remain UNKNOWN. The presence of potentially delegable BPF capabilities is insufficient to establish a complete namespace-scoped path.

No network trigger, special hardware, device assignment, or virtualization role is involved. The actor can retry link creation and iterator activity, but reliably forcing the `anon_inode_getfile()` failure may require file-descriptor or allocation pressure. This limits trigger confidence without establishing a hard-race deduction.

4. Primitive and severity interpretation

The exact primitive is a slab UAF write in `bpf_link_put()`. The `bpf_link` is an active structured kernel object, but the demonstrated stale use is specifically a lifetime/refcount operation rather than broad consumption of callbacks, pointers, or attacker-shaped replacement fields.

This is category B repeated lifetime corruption, not an ordinary stale cleanup read:

* The creator directly frees the object after failed settlement.
* The iterator still holds the exact pointer.
* The later `bpf_link_put()` actively modifies refcount or lifetime state at the freed address.

It is therefore CLASS_B rather than CLASS_C. It is not CLASS_A because controlled reclaim, directed corruption, refcount takeover, arbitrary kernel read/write, or privilege escalation is not demonstrated.

The demonstrated consequence is kernel memory corruption followed by a KASAN panic. The technically defensible unresolved consequence is corruption of reused slab storage through the stale refcount mutation. A useful replacement object or exploitation chain has not been shown.

`ImportantCandidate=YES` and `ManualReview=REQUIRED` are warranted because the second operation concretely mutates lifetime metadata through freed storage. `AutoDowngradeAllowed=NO` follows from this unresolved post-lifetime mutation, not merely from the presence of a UAF or a complex BPF object. The likely operational floor is Actionable Moderate, with Important classification dependent on reclaim and privilege analysis.

5. One-sentence report phrase

A failed BPF link settlement can race with link iteration and leave the iterator holding a freed link whose later `bpf_link_put()` performs a confirmed post-free refcount write, causing kernel panic and requiring manual review for unresolved exploitation leverage.

6. Manual review recommendation

MANUAL CHECK REQUIRED

The confirmed slab UAF write is a concrete second lifetime mutation through an already freed object, while BPF privilege boundaries and post-free exploitation leverage remain unresolved.

7. Call-site confidence

Call-site confidence: high

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

Patch: bpf: Skip unsettled links in link iterator [ Upstream
Commit: 68930f8d40ab4c10ca3b019f076136758fd100a8
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=68930f8d40ab4c10ca3b019f076136758fd100a8

Changed files:
  kernel/bpf/syscall.c
  kernel/bpf/link_iter.c
  kernel/bpf/bpf_iter.c
  fs/read_write.c
  arch/x86/entry/syscall_64.c
  arch/x86/entry/entry_64.S

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=68930f8d40ab4c10ca3b019f076136758fd100a8

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

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

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