[CVE-2026-68337][LOW] bpf: Reject redirect helpers without a bpf_net_context [ Upstream

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

CVE: CVE-2026-68337
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: bpf: Reject redirect helpers without a bpf_net_context [ Upstream
Commit: cabfacbd5af09d3ae898ca224c4a1459e9bba15d
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cabfacbd5af09d3ae898ca224c4a1459e9bba15d
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68337
Analysis date: Mon, 10 Aug 2026 17:37:07 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like, not an Important candidate
Manual review required: NO

Summary:
A NULL pointer dereference in the tc BPF redirect path can crash the kernel when redirect helpers or TC_ACT_REDIRECT are used from a qdisc qevent BPF path without bpf_net_context, but exploitation normally requires local tc/BPF administration privileges and does not show memory corruption or privilege escalation.

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

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

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-68337	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	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-703;CWE-754;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'A NULL pointer dereference can occur in the tc BPF redirect path because bpf_redirect helpers and skb_do_redirect may access per task bpf_net_context when that context was never installed for a qdisc qevent BPF execution path. A local actor who can attach cls_bpf or act_bpf to a qdisc qevent block can trigger the crash either by calling bpf_redirect() from the program or by returning TC_ACT_REDIRECT and letting tcf_qevent_handle reach skb_do_redirect. For the CVSS the PR:L value is used for the paranoid score because some deployments delegate CAP_NET_ADMIN or tc control to container root or service accounts, even though a typical host level setup is closer to PR:H. The issue is not directly network reachable because packet traffic only activates a locally configured qdisc and BPF policy. Impact is denial of service via kernel crash. No UAF, OOB access, information leak, or write primitive is indicated by the code change.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like, not an Important candidate (with actual score 1)	YES	REMOTE BPF SKB QDISC  DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like, not an Important candidate**::

## 2. Signal breakdown

Conservative scoring:

* Reliable kernel crash / strong DoS: +1
  The commit explicitly says the previous behavior was a crash caused by NULL dereference of current->bpf_net_context.
* Common packet-processing or qdisc path exposure: +1
  The bug is in tc BPF / qdisc qevent handling and is activated by packet processing after local configuration.
* Requires admin/root/CAP_* in typical deployments: -2
  Triggering requires configuring qdisc/qevent and attaching cls_bpf or act_bpf, normally requiring CAP_NET_ADMIN and BPF-related privileges.
* Remote reachable / network-triggerable: +0
  Network traffic can activate the configured path, but an attacker cannot trigger it remotely without prior local privileged tc/BPF setup.
* Generic memory corruption: +0
  The patch shows a NULL pointer dereference, not UAF, OOB write, type confusion, refcount abuse, or arbitrary write.
* Privilege escalation plausible: +0
  No reclaim, object replacement, stale callback, write primitive, or information leak is supported by the patch.

Paranoid scoring:

* Reduced-privilege delegation concern: +1 effective uplift
  In some environments CAP_NET_ADMIN or tc control may be delegated to container root or service accounts, making the practical PR closer to PR:L than full host-root.
* Still capped low by BPF privilege gating rule
  Unprivileged BPF is assumed disabled in the evaluated product, and no concrete memory corruption or boundary bypass is shown.

## 3. Reachability analysis

The bug can be triggered by a local actor able to configure tc qdisc qevent blocks and attach cls_bpf or act_bpf programs. In normal host deployments this is privileged administration and requires CAP_NET_ADMIN plus BPF loading capability or equivalent root-controlled setup. Namespaces or containers can matter if a reduced-privilege container root or service account is granted tc/BPF control, but this is still not a plain unprivileged local trigger. The path is not directly network reachable because packets only exercise a previously installed local qdisc/BPF policy.

Call-site confidence: high. The patch includes both helper-side checks in net/core/filter.c and the qevent caller change in net/sched/cls_api.c.

## 4. Severity interpretation

This behaves like an ordinary Moderate / Low-like privileged local DoS. The theoretical impact is a kernel crash through NULL dereference. Realistic exploitation evidence does not show memory corruption beyond invalid NULL access, does not show confidentiality or integrity impact, and does not support privilege escalation. It should not be treated as Important-class unless additional external evidence demonstrates unprivileged reachability or a stronger primitive.

## 5. One-sentence report phrase

A NULL pointer dereference in the tc BPF redirect path can crash the kernel when redirect helpers or TC_ACT_REDIRECT are used from a qdisc qevent BPF path without bpf_net_context, but exploitation normally requires local tc/BPF administration privileges and does not show memory corruption or privilege escalation.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: privileged local NULL dereference DoS only, no UAF/OOB/write primitive, no direct remote reachability, and BPF access is privilege-gated in the evaluated configuration.

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

Patch: bpf: Reject redirect helpers without a bpf_net_context [ Upstream
Commit: cabfacbd5af09d3ae898ca224c4a1459e9bba15d
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cabfacbd5af09d3ae898ca224c4a1459e9bba15d

Changed files:
  net/core/filter.c
  net/sched/cls_api.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=cabfacbd5af09d3ae898ca224c4a1459e9bba15d

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

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

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