[CVE-2026-74717][LOW] net/mlx5: fw_tracer, return NULL on create error [ Upstream

[CVE-2026-74717][LOW] net/mlx5: fw_tracer, return NULL on create error [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74717
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: net/mlx5: fw_tracer, return NULL on create error [ Upstream
Commit: 47fe0d2571e5b446a0f0b0c1d6b99f55e51f5cc0
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=47fe0d2571e5b446a0f0b0c1d6b99f55e51f5cc0
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74717
Analysis date: Sat, 22 Aug 2026 14:10:11 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-74717	LOW	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-252;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 'mlx5_fw_tracer_create could return ERR_PTR on tracer creation failure while later users treated the stored tracer value as either NULL or a valid object. The FW reporter core dump path missed the ERR_PTR check and could dereference this invalid pointer, causing an Oops and kernel panic. For the CVSS the PR:L reflects the paranoid case where local low privileged activity may contribute to resource pressure or driver recovery conditions, although reliable triggering normally depends on mlx5 hardware, tracer creation failure, and a later health reporter dump. The issue is not directly network reachable from the patch context. Impact is denial of service only via kernel crash. There is no evidence of UAF, OOB access, arbitrary write, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-74717 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE TRACE NOMEMCHK NETWORK KERNEL_PANIC_PLUS_UAF HARDWARE IPV6  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=2
ActionableScoreLower=1

1. ActionableScore
* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Firmware-mediated external influence: +1. The crash path is tied to mlx5 device health or firmware reporter activity rather than a directly exposed network packet path.
* Reliable kernel crash / strong DoS: +1. The commit includes a concrete Oops and kernel panic caused by dereferencing an ERR_PTR in the FW reporter dump path.
* Rare or hardware-specific condition: -1. The issue requires mlx5 hardware, failed tracer creation, and later FW reporter dump activity.
* No generic memory corruption signal. This is an invalid ERR_PTR dereference, not UAF, double free, OOB write, refcount takeover, or type confusion.
* No LPE signal. The patch does not show attacker-controlled reclaim, object replacement, callback control, writable stale object access, or arbitrary write.
* No confidentiality or integrity signal. The demonstrated impact is kernel crash only.

3. Reachability analysis
The practical trigger requires an mlx5 device, failure of `mlx5_fw_tracer_create()`, storage of the ERR_PTR-like value, and later execution of the FW reporter core dump path. A normal remote network peer is not shown to control this path directly. A local low-privileged user might theoretically contribute to resource pressure, but reliable triggering appears dependent on device state, firmware health events, or privileged device management activity. Namespace or container delegation does not obviously make this broadly reachable without access to the relevant device or devlink management paths.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like kernel DoS rather than an Important-class vulnerability. The crash is real and system-wide once the bad state is reached, but the exploitability is constrained by hardware and error-path preconditions. Theoretical escalation is not supported because the primitive is an invalid ERR_PTR dereference, not reusable memory corruption.

5. One-sentence report phrase
An ERR_PTR returned from mlx5 FW tracer creation could be stored as a tracer object and later dereferenced by the FW reporter dump path, causing a hardware-dependent local or firmware-mediated kernel panic without evidence of privilege escalation.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. The issue has a concrete crash trace but no supported memory corruption, LPE, information disclosure, network reachability, or cross-boundary primitive.

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

Patch: net/mlx5: fw_tracer, return NULL on create error [ Upstream
Commit: 47fe0d2571e5b446a0f0b0c1d6b99f55e51f5cc0
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=47fe0d2571e5b446a0f0b0c1d6b99f55e51f5cc0

Changed files:
  drivers/net/ethernet/mellanox/mlx5/core/diag/fw_tracer.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=47fe0d2571e5b446a0f0b0c1d6b99f55e51f5cc0

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

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

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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