[CVE-2026-64545][MODERATE REGULAR] net, bpf: check master for NULL in xdp_master_redirect() [ Upstream

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

CVE: CVE-2026-64545
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net, bpf: check master for NULL in xdp_master_redirect() [ Upstream
Commit: c99ca049e910d61ddbd28cc2c47242f2bfbb4970
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c99ca049e910d61ddbd28cc2c47242f2bfbb4970
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64545
Analysis date: Mon, 27 Jul 2026 22:23:00 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / manual review recommended
Manual review required: YES

Summary:
A race during bond slave release can let `xdp_master_redirect()` dereference a NULL master pointer in the XDP path, causing a local privileged or delegated CAP_NET_ADMIN denial of service via kernel panic.

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

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

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-64545	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-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'xdp_master_redirect can dereference a NULL master pointer during a race in bond slave release. The upper master adjacency can be removed before IFF_SLAVE is cleared, so an XDP_TX path may still pass the slave guard while netdev_master_upper_dev_get_rcu returns NULL. This results in a NULL pointer dereference on master flags and can panic the kernel in softirq context. For the CVSS the PR:L is used for the paranoid score because some deployments delegate CAP_NET_ADMIN or bond and XDP control to less trusted local users or service accounts. The issue is not proven to be directly network reachable because reliable triggering depends on local control plane timing around bond release, although packet traffic can participate in the XDP receive path. Impact is denial of service via kernel crash, with no concrete UAF, OOB access, information leak, or privilege escalation primitive visible from the patch context.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / manual review recommended (with actual score 2)	YES	REMOTE NULLPTR BPF HARDWARE LINUS PACKET  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	YES	NO	checked

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

ActionableScore=2
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / manual review recommended**::

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The trace shows a NULL pointer dereference in `xdp_master_redirect()` followed by kernel panic in softirq context.
* Common networking / packet-processing path: +1. The crash occurs in the XDP receive path under `net/core/filter.c`, although the vulnerable state is specific to bond slave teardown.
* Hard or unreliable race / special timing required: -1. Triggering requires the window where the upper-master adjacency is already removed but `IFF_SLAVE` is not yet cleared.
* Requires admin/root/CAP_NET_ADMIN in typical deployments: -2. Reliable triggering normally requires bond device manipulation and XDP/BPF setup, which are privileged in typical product configurations.

Paranoid adjustment:

* Use reduced privilege penalty instead of full admin penalty: +1 relative to conservative. Some environments delegate `CAP_NET_ADMIN`, bond management, or XDP control to containers or service accounts, so PR:L is defensible for paranoid triage.

No added signals:

* No generic memory corruption. This is a NULL pointer dereference, not UAF, OOB write, double free, type confusion, or stale object reuse.
* No privilege escalation signal. The patch does not show attacker-controlled reclaim, write-after-free, callback control, refcount abuse, or arbitrary read/write.
* No remote reachable signal. Packet traffic participates in the XDP path, but reliable triggering depends on local control-plane timing around bond release.

Call-site confidence: high. The provided trace and changed call site directly show the faulting dereference and the exact fixed check.

## 3. Reachability analysis

The bug is reachable when XDP traffic reaches `xdp_master_redirect()` while a bond slave is being released. A local privileged actor can plausibly trigger it by controlling bond teardown and XDP/BPF configuration. In normal deployments this requires `CAP_NET_ADMIN` and often privileged BPF/XDP access, so it is not a true local-unprivileged issue.

Namespaces and containers can lower the practical privilege barrier if a container or service account is delegated network administration capabilities. That supports the paranoid PR:L interpretation, but not PR:N. The issue is not directly network-triggerable because an external packet sender alone does not control the bond release race.

## 4. Severity interpretation

This behaves like an ordinary Moderate kernel DoS with manual-review relevance, not an Important-class vulnerability. The realistic demonstrated impact is kernel panic through NULL pointer dereference. The theoretical risk does not extend to memory corruption or privilege escalation based on the provided patch context.

The score remains low because triggering is timing-dependent and usually requires privileged network control. It is still worth manual review because the affected code is in the networking/BPF/XDP path and the crash occurs in interrupt/softirq context.

## 5. One-sentence report phrase

A race during bond slave release can let `xdp_master_redirect()` dereference a NULL master pointer in the XDP path, causing a local privileged or delegated CAP_NET_ADMIN denial of service via kernel panic.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED.

Reason: the issue is a networking/BPF/XDP race with a reliable kernel panic, but current evidence supports DoS only and does not show UAF, OOB access, privilege escalation, or remote-only triggering.

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

Patch: net, bpf: check master for NULL in xdp_master_redirect() [ Upstream
Commit: c99ca049e910d61ddbd28cc2c47242f2bfbb4970
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c99ca049e910d61ddbd28cc2c47242f2bfbb4970

Changed files:
  net/core/filter.c
  include/net/xdp.h
  net/core/dev.c
  kernel/softirq.c
  include/linux/bottom_half.h
  net/packet/af_packet.c
  net/socket.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=c99ca049e910d61ddbd28cc2c47242f2bfbb4970

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

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

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