[CVE-2026-68139][MODERATE REGULAR] net/mlx5e: Use sender devcom for MPV master-up

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

CVE: CVE-2026-68139
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net/mlx5e: Use sender devcom for MPV master-up
Commit: c698b2735613f1f35c55688bd2252f75f31c49ad
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c698b2735613f1f35c55688bd2252f75f31c49ad
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68139
Analysis date: Mon, 10 Aug 2026 12:00:18 -0400
ActionableScore: 3
ActionableScore lower bound: 1
Actionable bucket: Borderline Moderate. Manual review recommended, but not an Important candidate
Manual review required: YES

Summary:
A NULL pointer dereference in mlx5e MPV devcom handling can panic the host during PCIe DPC recovery or related reload paths when a master-up affiliation event reaches a peer before its devcom backpointer is initialized.

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

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

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-68139	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	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-665;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'mlx5e MPV devcom handling can dereference a NULL peer devcom pointer during affiliation replay after PCIe DPC recovery or a related reload path. The peer private data may be visible in the devcom component list before mlx5e_devcom_init_mpv stores the returned component device in priv devcom, so MPV_DEVCOM_MASTER_UP can reach a peer with priv devcom still NULL and crash the kernel. For the CVSS the PR:L is used for the paranoid score because delegated device management or recovery control could let a non administrator service account trigger reload or reset paths, while the normal deployment often requires administrator control. The issue is not directly network reachable through packet traffic. Impact is denial of service via kernel crash, with no clear evidence of information disclosure or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline Moderate. Manual review recommended, but not an Important candidate (with actual score 2)  SKIP CVE-2026-68139 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE DANGER NULLPTR NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	checked

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

ActionableScore=3
ActionableScoreLower=1

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: **+1**. The commit shows a real host panic from NULL pointer dereference in `mlx5_devcom_comp_set_ready`.
* Hard or special timing required: **-1**. The crash depends on affiliation replay racing with MPV devcom initialization.
* Physical or rare hardware condition: **-1**. The reported trigger involves PCIe DPC recovery after a fatal PCIe bus error.
* Requires privileged or device-management conditions in typical deployments: **-1**. Reliable triggering normally requires device reset, PCI recovery, firmware or hardware fault conditions, not ordinary unprivileged user activity.
* Net result is low but nonzero because the panic is real.

Paranoid signals:

* Firmware-mediated external influence: **+1**. PCIe error recovery and device firmware or hardware behavior can influence the path.
* Reliable kernel crash / strong DoS: **+1**. The failure is a demonstrated kernel panic.
* Broad datacenter exposure: **+1**. `mlx5` devices are common in high-value server, RDMA, and cloud environments.
* No memory corruption / LPE bonus. This is a NULL dereference, not UAF, OOB write, type confusion, stale callback, or attacker-controlled reuse.

## 3. Reachability analysis

The bug is not directly network reachable through packet traffic. The practical trigger is PCIe DPC recovery or a related mlx5 reload/resume path where RDMA multiport affiliation events are replayed while MPV devcom registration is incomplete.

Typical exploitation requires control over device-management, reset, recovery, firmware behavior, or a faulting PCIe device. A normal local unprivileged user is unlikely to trigger this reliably. Namespaces or containers do not obviously reduce the privilege requirement unless the environment delegates device reset or RDMA management capabilities to a less privileged service account.

The path is relevant only on systems with affected mlx5 MPV/RDMA multiport configurations and PCIe recovery behavior.

## 4. Severity interpretation

This behaves like a reliability-impacting Moderate issue rather than an Important vulnerability. The demonstrated impact is host DoS via kernel panic. The patch and call trace support a NULL pointer dereference caused by initialization ordering, but do not show UAF, stale object reuse, attacker-controlled reclaim, write-after-free, arbitrary write, or privilege escalation.

Paranoid handling is justified for manual review because the bug is in a high-value NIC/RDMA driver recovery path and can panic the host, but the evidence does not support elevating it to Actionable Moderate or Important.

## 5. One-sentence report phrase

A NULL pointer dereference in mlx5e MPV devcom handling can panic the host during PCIe DPC recovery or related reload paths when a master-up affiliation event reaches a peer before its devcom backpointer is initialized.

## 6. Manual review recommendation

**MANUAL CHECK RECOMMENDED**

Manual review is recommended because this is a real host panic in a widely deployed datacenter NIC/RDMA driver path, but it should not be treated as Important without additional evidence of attacker-controlled triggering, memory corruption, or privilege escalation.

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

Patch: net/mlx5e: Use sender devcom for MPV master-up
Commit: c698b2735613f1f35c55688bd2252f75f31c49ad
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c698b2735613f1f35c55688bd2252f75f31c49ad

Commit description:

After PCIe DPC recovery, mlx5 reloads the affected functions and
replays multiport affiliation events. In the reported failure, the
first relevant device error was:

  pcieport 0000:10:01.1: DPC: containment event
  pcieport 0000:10:01.1: PCIe Bus Error: severity=Uncorrected (Fatal)
  pcieport 0000:10:01.1:    [ 5] SDES                   (First)

mlx5 recovered the PCI functions and resumed 0000:11:00.1. During
that resume, RDMA multiport binding replayed
MLX5_DRIVER_EVENT_AFFILIATION_DONE and mlx5e sent
MPV_DEVCOM_MASTER_UP. The host then panicked with:

  BUG: kernel NULL pointer dereference, address: 0000000000000010
  RIP: mlx5_devcom_comp_set_ready+0x5/0x40 [mlx5_core]
  RDI: 0000000000000000

Call trace included:

  mlx5_devcom_comp_set_ready
  mlx5e_devcom_event_mpv
  mlx5_devcom_send_event
  mlx5_ib_bind_slave_port
  mlx5r_mp_probe
  mlx5_pci_resume

MPV devcom registration publishes mlx5e private data to the component
peer list before mlx5e_devcom_init_mpv() stores the returned component
device in priv->devcom. A concurrent master-up event can therefore
reach a peer whose private data is visible but whose priv->devcom
backpointer is still NULL.

MPV_DEVCOM_MASTER_UP already carries the sender/master mlx5e private
data as event_data. The ready bit is stored on the shared devcom
component, not on an individual peer. Use the sender devcom when
marking the MPV component ready.

This preserves the readiness transition while avoiding a NULL
dereference of the peer devcom pointer during affiliation replay after
PCI error recovery.

Fixes: bf11485 ("net/mlx5: Register mlx5e priv to devcom in MPV mode")
Assisted-by: Codex:gpt-5
Signed-off-by: Manjunath Patil <manjunath.b.patil@oracle.com>
Cc: stable@vger.kernel.org # 6.7+
Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
Link: https://patch.msgid.link/20260707233911.3651139-1-manjunath.b.patil@oracle.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/net/ethernet/mellanox/mlx5/core/en_main.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=c698b2735613f1f35c55688bd2252f75f31c49ad

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

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

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