[CVE-2026-93138][MODERATE REGULAR] bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux [ Upstream

[CVE-2026-93138][MODERATE REGULAR] bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux [ Upstream

[AL-KERNEL]

CVE: CVE-2026-93138
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux [ Upstream
Commit: f32a4a40bc635be25d6816da4bd91e9e58c31bf3
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f32a4a40bc635be25d6816da4bd91e9e58c31bf3
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93138
Analysis date: Fri, 18 Sep 2026 05:31:47 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-93138	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-93138 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:L/I:L/A:H';CWE-362;CWE-662;CWE-665;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.8';DESCR 'bpf_get_btf_vmlinux lazily initializes vmlinux BTF under bpf_verifier_lock but previously published the global pointer with a plain store and read it on the lockless fast path with a plain load. On weakly ordered architectures, a concurrent first time caller could observe the pointer before all parsed BTF contents and related globals are visible, creating a verifier state consistency race. For the CVSS the PR:L is used in the paranoid score because a local user or service with BPF program load access may reach this path without full host administration in some deployments. The issue is not network reachable and requires local interaction with BPF verifier paths. Impact is at least denial of service or verifier malfunction, and in worst case may allow limited confidentiality or integrity impact due to inconsistent BTF metadata visibility.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3)	YES	OOB BPF RACE HARDWARE  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	NO	NO	checked

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

ActionableScore=3
ActionableScoreLower=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: 3
* Paranoid score: 3
* Final recommended bucket: **Borderline / manual review recommended**::

No floor or cap changed the score.

2. Signal breakdown

Conservative signals:

* +1 Weak or indirect corruption candidate. The bug can expose a published btf_vmlinux pointer before the struct btf contents and related globals are fully visible on weakly ordered architectures.
* +1 Security-sensitive verifier state consistency concern. The affected object is vmlinux BTF used by BPF verifier paths, including metadata such as bpf_ctx_convert.t.
* +0 Local unprivileged trigger not awarded. BPF program loading or verifier reachability below host-admin-equivalent privilege is not established from the supplied evidence.
* +0 Reliable kernel crash not awarded. The commit describes a theoretical memory-ordering race, not an observed panic, UAF, OOB access, or deterministic crash.
* +0 C/I impact not awarded. No concrete disclosure, arbitrary write, verifier bypass, or privilege escalation primitive is established.
* +0 Real UAF not awarded. No freed or post-lifetime object use is shown.
* -0 Race penalty not applied conservatively. Although this is a first-time initialization race on weakly ordered architectures, the prompt forbids subtracting merely because the bug is a race, and repeatability is not fully characterized.

Paranoid additional signal:

* +1 Plausible verifier malfunction impact. A first-time concurrent reader observing partially initialized BTF metadata could plausibly cause verifier misbehavior or DoS, but this remains below Important-grade because no concrete memory corruption or bypass primitive is shown.

Non-awarded material signals:

* Controlled reclaim not demonstrated.
* Arbitrary write not demonstrated.
* Real UAF not demonstrated.
* Remote reachability not established.
* Structured stale-object leverage not awarded because there is no stale post-free object.
* Weak LPE not awarded because inconsistent BTF visibility alone does not establish a useful exploitation primitive.
* Extra Availability not awarded because no distinct persistent availability impact is shown.
* BPF floor 5 is not applied because this is a privileged control-plane verifier path with no UAF, no repeated refcount mutation, no controlled replacement, and no demonstrated LPE.

3. Reachability analysis

The vulnerable path is bpf_get_btf_vmlinux(), used by BPF verifier related code when vmlinux BTF is lazily initialized. A trigger requires local interaction with BPF verifier paths and a concurrent first-time call pattern on an architecture where plain store and lockless load ordering is insufficient.

Ordinary unprivileged reachability is not established. Modern deployments often restrict BPF loading through CAP_BPF, CAP_SYS_ADMIN, CAP_NET_ADMIN, sysctls, or other host policy, but the supplied patch does not fully resolve the exact privilege boundary. Therefore HostAdminRequired is UNKNOWN rather than YES or NO.

NamespaceScopedPrivilege is UNKNOWN. The patch does not show that all required BPF loading, verifier, attach, and trigger stages are available inside attacker-created namespaces.

No direct network trigger is established. No special device hardware is required, but weak memory ordering and concurrent first-time initialization are relevant conditions. Race repeatability is unresolved.

4. Primitive and severity interpretation

The exact primitive is a memory-ordering race during lazy publication of a global vmlinux BTF pointer. The old code used a plain store to publish btf_vmlinux and a plain lockless load on the fast path. On weakly ordered architectures, another caller could observe the pointer before the initialized BTF contents and related globals are visible.

This is not a UAF, not a double release, not an OOB access, and not an arbitrary write. It is best classified as CLASS_C invalid-state behavior in a security-sensitive verifier path.

Demonstrated consequence is potential verifier inconsistency or malfunction. Speculative consequence is limited C/I impact if inconsistent BTF metadata affected verifier decisions, but the patch does not establish a concrete verifier bypass, information leak, or privilege escalation chain.

ImportantCandidate is NO because there is no Class A primitive and no strong Class B lifetime or corruption primitive. ManualReview is RECOMMENDED because BPF verifier state consistency bugs can be security-sensitive and the patch explicitly mentions globals outside the returned object. AutoDowngradeAllowed is YES because no concrete UAF, repeated refcount mutation, controlled corruption, authorization bypass, or demonstrated LPE remains unresolved.

Likely operational severity is low to borderline Moderate, with manual review useful mainly to confirm whether any verifier decision can consume partially visible BTF state in a security-relevant way.

5. One-sentence report phrase

A memory ordering race in bpf_get_btf_vmlinux could let a concurrent first time BPF verifier user observe vmlinux BTF before all parsed contents and related globals are visible, causing possible verifier malfunction or DoS, but no concrete UAF, arbitrary write, information leak, or privilege escalation primitive is established.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the affected path is BPF verifier metadata initialization, and verifier state consistency is security-sensitive, but the supplied evidence establishes only a weakly ordered initialization race without a concrete exploitation primitive.

7. Call-site confidence

Call-site confidence: medium

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

Patch: bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux [ Upstream
Commit: f32a4a40bc635be25d6816da4bd91e9e58c31bf3
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f32a4a40bc635be25d6816da4bd91e9e58c31bf3

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=f32a4a40bc635be25d6816da4bd91e9e58c31bf3

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

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

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:L/I:L/A:H
  The Best / paranoid CVSS score: 5.8

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