[CVE-2026-53069][MODERATE REGULAR] net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master [ Upstream

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

CVE: CVE-2026-53069
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master [ Upstream
Commit: 3128b294b426533c8d9162187446d93a8a160359
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3128b294b426533c8d9162187446d93a8a160359
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53069
Analysis date: Wed, 24 Jun 2026 13:10:40 -0400
ActionableScore: 4
ActionableScore lower bound: 2
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
A NULL pointer dereference in the XDP master redirect path can crash the kernel when a down bonding master without initialized round-robin state is reached from packet processing, requiring local network configuration privileges in typical deployments.

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

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

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-53069	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-754;CWE-703;Other CVSS 'AV:L/AC:H/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 XDP master redirect path because xdp_master_redirect() may call the master ndo_xdp_get_xmit_slave() callback even when the master device is down and its XDP related state was never initialized. In the bonding round robin case, bond_rr_gen_slave_id() dereferences rr_tx_counter, which is allocated only after bond_open(), so a never opened bond can crash the kernel when this path is reached. For the CVSS the PR:L is used in the paranoid score because reliable triggering may be possible for a local user or service with delegated network administration capability such as CAP_NET_ADMIN, container root, or a network management component rather than full host root. The issue is not a pure remote network vulnerability by itself because creating the vulnerable bonding and XDP state normally requires local control plane access. However, after such a configuration exists, packet processing through the XDP_TX path may reach the bug, so network datapath exposure should be considered during manual review. Impact is denial of service via kernel crash. No confidentiality or integrity impact is assigned because the primitive shown by the code is a NULL pointer dereference, not UAF, OOB access, information disclosure, or arbitrary write.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 3)	YES	REMOTE NULLPTR INIT BPF HARDWARE SYZBOT  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	YES	NO	checked

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

ActionableScore=4
ActionableScoreLower=2

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1
  The commit explicitly describes a kernel panic from NULL dereference in `bond_rr_gen_slave_id()` via `xdp_master_redirect()`.

* Common networking core path or packet-processing path: +1
  The affected function is in `net/core/filter.c` and is reached from the XDP packet-processing path.

* Requires admin/root/CAP_NET_ADMIN in typical deployments: -2
  Creating bonding devices, configuring round-robin mode, attaching native XDP, and arranging the master/slave setup normally require `CAP_NET_ADMIN`.

* Availability impact realistic: +1
  Once the vulnerable configuration exists, packet processing through the XDP path can crash the kernel. This is a real availability impact, but it is not counted as remote unauthenticated exposure.

* Broad/default/common subsystem: +1
  Networking and BPF/XDP are important kernel subsystems, but the exact trigger depends on non-default bonding/XDP configuration.

Paranoid interpretation:

* The `CAP_NET_ADMIN` penalty is not fully applied in the paranoid score because delegated network administration, container root, or a network-management service account may be materially less privileged than full host root.
* No memory corruption, UAF, OOB write, confidentiality impact, integrity impact, or privilege escalation signal is awarded. The primitive shown by the patch is a NULL pointer dereference.

## 3. Reachability analysis

The bug is typically triggered by a local actor able to configure bonding and XDP state, usually requiring `CAP_NET_ADMIN`. It is not a pure remote network vulnerability because an attacker cannot normally create the vulnerable master/slave/XDP configuration using packets alone.

However, after the vulnerable configuration exists, the crash path is in packet processing through `XDP_TX -> xdp_master_redirect()`. That means network traffic may be the final trigger in a prepared or misconfigured environment. Namespaces and containers matter because `CAP_NET_ADMIN` may be delegated to container root or network-management services, making PR:L a defensible paranoid interpretation.

The path is not default-enabled for ordinary systems. It requires bonding, round-robin behavior, native XDP exposure, and a down or never-opened master state.

## 4. Severity interpretation

This behaves like a high-confidence DoS bug, not an Important-class memory corruption issue. The patch supports NULL pointer dereference and kernel panic, but does not show UAF, stale reuse, type confusion, controlled overwrite, arbitrary write, or information disclosure.

Conservatively this is ordinary Moderate / Low-like because reliable setup usually requires administrative network configuration. Paranoid triage should keep it as borderline actionable because it is in a network datapath and delegated `CAP_NET_ADMIN` deployments are realistic.

## 5. One-sentence report phrase

A NULL pointer dereference in the XDP master redirect path can crash the kernel when a down bonding master without initialized round-robin state is reached from packet processing, requiring local network configuration privileges in typical deployments.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Manual review is recommended because the crash occurs in an XDP packet-processing path and delegated `CAP_NET_ADMIN` environments may make the practical privilege requirement lower than full host root. It is not marked as required Important-class review because the demonstrated primitive is NULL dereference DoS only, with no supported LPE or memory-corruption primitive.

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

Patch: net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master [ Upstream
Commit: 3128b294b426533c8d9162187446d93a8a160359
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3128b294b426533c8d9162187446d93a8a160359

Changed files:
  net/core/filter.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=3128b294b426533c8d9162187446d93a8a160359

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

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

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