[CVE-2026-74335][MODERATE REGULAR] bpf: Fix NULL pointer dereference in bpf_task_from_vpid() [ Upstream

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

CVE: CVE-2026-74335
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: bpf: Fix NULL pointer dereference in bpf_task_from_vpid() [ Upstream
Commit: b7474f4432dd9559ada03b01a8cd3472cd02c61d
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7474f4432dd9559ada03b01a8cd3472cd02c61d
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74335
Analysis date: Sat, 15 Aug 2026 23:30:18 -0400
ActionableScore: 3
ActionableScore lower bound: 1
Actionable bucket: Borderline Moderate. Manual review recommended, not Strong Important
Manual review required: YES

Summary:
A race in `bpf_task_from_vpid()` can let `cgroup_skb` execution in softirq observe an exiting task with no active pid namespace, causing a NULL pointer dereference and kernel DoS when privileged BPF/cgroup setup is present.

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

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

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 REGULAR
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-74335	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-362;CWE-754;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A NULL pointer dereference can occur in bpf_task_from_vpid() because cgroup_skb execution in softirq may interrupt a task that is already in do_exit() after its thread pid has been cleared. In that state task_active_pid_ns(current) can return NULL and find_task_by_vpid() can reach find_pid_ns() with a NULL namespace, causing idr_find() to dereference NULL and crash the kernel. For the CVSS the PR:L is used for the paranoid score because some environments delegate BPF or cgroup control to a reduced capability root, container root, or service account rather than a full host administrator. The issue is not directly network reachable by itself because a suitable cgroup_skb BPF program must be present, but packet processing can be the immediate execution context once such a program is attached. Impact is denial of service via kernel crash. The patch context supports NULL dereference and race behavior, but does not show a UAF, OOB access, information leak, or write primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline Moderate. Manual review recommended, not Strong Important (with actual score 2)  SKIP CVE-2026-74335 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 675c3596ff32c040d1dd2e28dd57e83e634b9f60 YES  NO NO unknown 	MAYBE	LOCK NULLPTR BPF LINUS  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=3
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 3
* Final recommended bucket: **Borderline Moderate. Manual review recommended, not Strong Important**

## 2. Signal breakdown

Conservative scoring:

* Reliable kernel crash / strong DoS: +1
  The patch and trace show a NULL pointer dereference in `idr_find()` from `find_pid_ns()` when `task_active_pid_ns(current)` returns NULL.

* Common packet-processing path: +1
  The crash path runs through `cgroup_skb`, `sk_filter_trim_cap()`, and `tcp_v4_rcv()`, so packet processing can be the immediate execution context once the BPF program is attached.

* Hard or unreliable race / special timing required: -1
  The condition requires softirq execution to interrupt a task in a narrow `do_exit()` window after `thread_pid` has been cleared.

* Requires admin/root/CAP_* in typical deployments: -2
  Loading and attaching a `cgroup_skb` BPF program normally requires privileged BPF and cgroup control, such as `CAP_BPF`, `CAP_SYS_ADMIN`, `CAP_NET_ADMIN`, or root-controlled configuration. Unprivileged BPF should not be assumed.

* Availability impact realistic: +1
  The demonstrated failure is a kernel NULL dereference in IRQ context, which can cause Oops or panic depending configuration.

Paranoid adjustment:

* Reduced privilege / delegated BPF or cgroup control: +2 relative to conservative
  In some container, service, or reduced-capability admin environments, BPF or cgroup control may be delegated below full host-root equivalence. This does not make the bug unprivileged, but it reduces confidence in treating it as purely PR:H operationally.

Not awarded:

* No remote reachable / network-triggerable bonus. Network packets can enter the call path only after a suitable privileged BPF program is attached.
* No generic memory corruption bonus. The demonstrated primitive is NULL dereference, not UAF, OOB write, double free, or type confusion.
* No privilege escalation bonus. The patch does not show reclaim, controlled object replacement, write primitive, callback control, refcount takeover, or arbitrary read/write.
* No BPF high-control unprivileged API bonus. The evaluated configuration gates BPF behind privileges.

## 3. Reachability analysis

The realistic trigger requires a `cgroup_skb` BPF program using `bpf_task_from_vpid()` to be loaded and attached. In typical hardened or enterprise configurations, this is privileged and not available to ordinary local users.

Packets can trigger execution of the already attached program through the receive path, but the vulnerability is not independently remotely reachable because the attacker must first arrange the vulnerable BPF program and cgroup attachment. Namespaces and containers matter only if BPF or cgroup control is delegated to a reduced-capability root or service account. In that case the practical PR may be closer to PR:L than PR:H, but still not PR:N.

The race window is specific: softirq must interrupt a task that is already exiting after `__unhash_process()` has cleared `thread_pid`. This makes exploitation less reliable and supports keeping the main score below Actionable Moderate.

## 4. Severity interpretation

This behaves like an ordinary to borderline Moderate kernel DoS issue, not an Important-class vulnerability based on the supplied patch.

The theoretical concern comes from BPF helper execution in a packet-processing context and a race with task exit state. The realistic evidence shows a NULL namespace dereference leading to crash only. There is no supported UAF, stale object reuse, attacker-controlled reclaim, write-after-free, information leak, or privilege escalation primitive.

Therefore, conservative handling can be low-priority Moderate, while paranoid handling justifies manual review because BPF and cgroup delegation can vary by product configuration.

## 5. One-sentence report phrase

A race in `bpf_task_from_vpid()` can let `cgroup_skb` execution in softirq observe an exiting task with no active pid namespace, causing a NULL pointer dereference and kernel DoS when privileged BPF/cgroup setup is present.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Manual review is recommended because the bug is in BPF helper code and executes from a packet-processing path, but current evidence supports DoS only and does not justify Important severity without additional evidence of memory corruption, unprivileged reachability, or privilege escalation.

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

Patch: bpf: Fix NULL pointer dereference in bpf_task_from_vpid() [ Upstream
Commit: b7474f4432dd9559ada03b01a8cd3472cd02c61d
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7474f4432dd9559ada03b01a8cd3472cd02c61d

Changed files:
  lib/idr.c
  kernel/pid.c
  kernel/bpf/helpers.c
  kernel/bpf/cgroup.c
  net/core/filter.c
  net/ipv4/tcp_ipv4.c
  kernel/exit.c
  kernel/signal.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=b7474f4432dd9559ada03b01a8cd3472cd02c61d

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

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

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

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: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

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