[CVE-2026-53032][MODERATE REGULAR] bpf: Fix NULL deref in map_kptr_match_type for scalar regs [ Upstream

[CVE-2026-53032][MODERATE REGULAR] bpf: Fix NULL deref in map_kptr_match_type for scalar regs [ Upstream

[AL-KERNEL]

CVE: CVE-2026-53032
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: bpf: Fix NULL deref in map_kptr_match_type for scalar regs [ Upstream
Commit: 520454e839710c327808c2fcc98e28cee77355fc
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=520454e839710c327808c2fcc98e28cee77355fc
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53032
Analysis date: Fri, 26 Jun 2026 10:34:36 -0400
ActionableScore: 4
ActionableScore lower bound: 0
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
A crafted BPF program can trigger a NULL pointer dereference in map_kptr_match_type() by causing btf_is_kernel() to run on a scalar register with no BTF metadata, leading to a local kernel crash when BPF program loading is permitted.

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

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

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-53032	MODERATE	CHECK	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-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 in the BPF verifier can occur in map_kptr_match_type because btf_is_kernel(reg btf) may be called before verifying that the register base type is PTR_TO_BTF_ID. A crafted BPF program can place a scalar register into a kptr slot, where reg btf is NULL, and trigger a kernel crash during verification. For the CVSS the PR:L is used for the paranoid score because some deployments may allow delegated BPF access through CAP_BPF, service accounts, container root, or unprivileged BPF policy rather than full administrative control. The issue is not network reachable and requires local ability to submit BPF programs to the verifier. Impact is denial of service only based on the available primitive, with no supported evidence of information disclosure or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 2) 	MAYBE	BPF SIMPLEFIX HARDWARE LINUS  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=4
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 4
* Final recommended bucket: **Borderline, manual review recommended**::

## 2. Signal breakdown

Paranoid score signals:

* Local unprivileged or reduced privilege trigger: +1
  Some deployments may allow BPF program loading through CAP_BPF, service accounts, container root, or permissive unprivileged BPF policy rather than full host root.

* Reliable kernel crash / strong DoS: +1
  A crafted BPF program can cause a NULL dereference in the verifier by reaching btf_is_kernel(reg->btf) with reg->btf equal to NULL.

* Local high-control kernel data-plane API: +1
  BPF verifier input is highly attacker-shaped, even though access is commonly restricted.

* Broad/common subsystem exposure: +1
  BPF is a common kernel subsystem and the verifier is a security-sensitive attack surface.

Conservative score adjustments:

* Requires admin/CAP_BPF/CAP_SYS_ADMIN in typical deployments: -2
  On many production systems this path is restricted to privileged users.

Not counted:

* Generic memory corruption: +0
  The patch shows a NULL pointer dereference, not UAF, OOB write, double free, or controlled overwrite.

* Privilege escalation plausible: +0
  No supported LPE primitive is visible from the patch.

* Confidentiality or integrity impact: +0
  No info leak, arbitrary write, or object corruption primitive is demonstrated.

## 3. Reachability analysis

The bug is reachable by submitting a crafted BPF program that stores a scalar register into a kptr slot, causing map_kptr_match_type() to access reg->btf before validating that the register is PTR_TO_BTF_ID. In typical deployments this requires CAP_BPF, CAP_SYS_ADMIN, or equivalent BPF-loading privileges, so the conservative interpretation is privileged local DoS. In less restrictive deployments, delegated BPF access, container root, service accounts, or unprivileged BPF policy may make the practical PR closer to local low privilege. The issue is not network reachable.

## 4. Severity interpretation

This behaves like a local verifier-triggered DoS, not an Important-class memory corruption issue. The theoretical concern is elevated because BPF verifier bugs are security-sensitive and privilege assumptions vary across deployments. Realistically, the shown primitive is a NULL dereference during verification, so current evidence supports availability impact only.

## 5. One-sentence report phrase

A crafted BPF program can trigger a NULL pointer dereference in map_kptr_match_type() by causing btf_is_kernel() to run on a scalar register with no BTF metadata, leading to a local kernel crash when BPF program loading is permitted.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Manual review is recommended because the bug is in the BPF verifier attack surface and practical severity depends strongly on whether BPF loading is restricted to full administrators or delegated to lower-privileged users.

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

Patch: bpf: Fix NULL deref in map_kptr_match_type for scalar regs [ Upstream
Commit: 520454e839710c327808c2fcc98e28cee77355fc
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=520454e839710c327808c2fcc98e28cee77355fc

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=520454e839710c327808c2fcc98e28cee77355fc

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

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

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: 4

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