[CVE-2026-98134][LOW] bpf: check_cond_jmp_op(): properly infer if register is null [ Upstream

[CVE-2026-98134][LOW] bpf: check_cond_jmp_op(): properly infer if register is null [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98134
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: bpf: check_cond_jmp_op(): properly infer if register is null [ Upstream
Commit: b55c9f019e169ed0d01394f96e172286a8b21b99
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b55c9f019e169ed0d01394f96e172286a8b21b99
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98134
Analysis date: Fri, 25 Sep 2026 08:22:39 -0400
ActionableScore: 2
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-98134	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98134 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;*CWE-20;CWE-693;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'An incorrect non null inference in the eBPF verifier can allow a verifier accepted BPF program to dereference a NULL pointer. The issue occurs when two pointers are compared and the verifier treats absence of PTR_MAYBE_NULL on one pointer type as proof that the runtime value cannot be NULL. A local attacker who can load the affected BPF program may trigger a kernel NULL pointer dereference and denial of service. For the CVSS the PR:L value is used for the paranoid score because some deployments delegate BPF access to containers service accounts or unprivileged users when unprivileged BPF is enabled. The issue is not directly network reachable because loading or executing the crafted BPF program requires local code execution or a local BPF capable context. The available patch context demonstrates a NULL dereference and kernel crash risk but does not demonstrate an arbitrary write information leak or privilege escalation primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2)	YES	NULLPTR BPF IMPROVEONLY LINUS 	YES	NO	checked

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

ActionableScore=2
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 2
* Conservative score: 2
* Raw paranoid score: 2
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 Weak invalid-pointer primitive. The verifier can incorrectly mark a nullable `PTR_TO_MAP_VALUE` register as non-NULL after comparison with a pointer type that lacks `PTR_MAYBE_NULL` but can still be NULL at runtime.
* +1 Kernel DoS plausibility. The verifier may accept a BPF program that performs a kernel NULL-pointer dereference, with kernel Oops or panic behavior depending on configuration.
* No local-unprivileged-trigger bonus. The supplied evidence does not establish that the complete BPF load and execution path is available to an ordinary unprivileged user in the evaluated product.
* No remote-reachability bonus. Loading and executing the crafted BPF program requires a local BPF-capable context.
* No UAF, stale reference, refcount mutation, OOB access, arbitrary write, controlled reclaim, information disclosure, or authorization bypass is established.
* No confidentiality or integrity points. Writing through the demonstrated NULL pointer does not establish an attacker-controlled target, arbitrary kernel write, or useful corruption primitive.
* No paranoid escalation. The possible presence of delegated BPF access or enabled unprivileged BPF in some deployments is insufficient evidence that the complete trigger is reachable below host-admin-equivalent privilege.

3. Reachability analysis

The evaluated attacker is a local process that can load and execute the affected eBPF program. The patch and supplied context do not establish whether this requires `CAP_BPF`, `CAP_SYS_ADMIN`, a product-specific delegated capability, or whether unprivileged BPF loading is enabled.

`HostAdminRequired=UNKNOWN` because the complete BPF loading and trigger privilege boundary is not resolved by the supplied patch. `NamespaceScopedPrivilege=UNKNOWN` because no evidence establishes that all required stages, including program loading and execution, are available inside an attacker-controlled namespace.

No network trigger, special hardware, race condition, device setup, or prior privileged object setup is established by the patch. The practical impact depends strongly on the product BPF policy, including unprivileged BPF sysctl settings and access to BPF-capable service interfaces.

4. Primitive and severity interpretation

The exact primitive is verifier unsoundness causing acceptance of a BPF path that dereferences a runtime NULL pointer. This is an invalid-state and crash-oriented primitive, not a real UAF, active-object lifetime violation, controlled type confusion, arbitrary write, or security-boundary bypass.

The demonstrated consequence is a local kernel NULL-pointer dereference and potential denial of service. A privilege-escalation consequence is speculative and unsupported because the shown store targets a NULL pointer rather than an attacker-selected or reused kernel object. The verifier is security-sensitive, but the specific patch-supported behavior remains `CLASS_C`.

`ImportantCandidate=NO` because no meaningful exploitation leverage beyond the crash path is demonstrated. `AutoDowngradeAllowed=YES` because the issue is a constrained verifier-accepted NULL dereference with no demonstrated memory-corruption or authorization primitive.

5. One-sentence report phrase

An eBPF verifier nullness inference bug can accept a program that dereferences a runtime NULL map value pointer and may cause a local kernel denial of service.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Confirm the evaluated product BPF policy, including unprivileged BPF settings, delegated `CAP_BPF` access, and whether untrusted local workloads can load and run affected programs. No patch-supported evidence currently justifies treating the issue as privilege escalation or Important-class memory corruption.

7. Call-site confidence

Call-site confidence: medium

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

Patch: bpf: check_cond_jmp_op(): properly infer if register is null [ Upstream
Commit: b55c9f019e169ed0d01394f96e172286a8b21b99
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b55c9f019e169ed0d01394f96e172286a8b21b99

Changed files:
  kernel/bpf/verifier.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=b55c9f019e169ed0d01394f96e172286a8b21b99

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

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

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

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