[CVE-2026-72497][LOW] RDMA/bnxt_re: Add a max slot check for SQ [ Upstream

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

CVE: CVE-2026-72497
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: RDMA/bnxt_re: Add a max slot check for SQ [ Upstream
Commit: a59d815cbe667929b693b5fa6716a074e6a31c5b
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a59d815cbe667929b693b5fa6716a074e6a31c5b
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72497
Analysis date: Sat, 15 Aug 2026 23:46:20 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like. Not an Actionable Moderate candidate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-72497	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	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-20;CWE-1284;**CWE-400;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'RDMA/bnxt_re did not validate the user supplied sq_slots value for variable WQE mode before using it for SQ configuration. A local user process with access to the bnxt_re RDMA uverbs device could request zero slots or a value above the hardware supported 64K limit, potentially causing invalid QP setup and driver or device availability problems. For the CVSS the PR:L is used because reliable triggering requires local access to the RDMA userspace device interface, but not full administrator privileges in deployments where uverbs access is delegated to users or services. The issue is not directly network reachable because a remote RDMA peer does not supply this local QP creation parameter. Impact is primarily denial of service or failed RDMA resource setup, with no concrete evidence of information disclosure or privilege escalation from the shown code path.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like. Not an Actionable Moderate candidate (with actual score 2)	YES	SIMPLEFIX NETWORK  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=2
ActionableScoreLower=1

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

2. Signal breakdown
* Local unprivileged trigger: +1. A local process with access to the bnxt_re RDMA uverbs device can supply the sq_slots value during QP creation or setup.
* Availability impact realistic: +1 for paranoid only. An invalid SQ slot count may cause failed QP setup or device or driver availability problems, but the patch does not show a concrete panic, UAF, OOB write, or firmware crash.
* Rare and device-specific subsystem: -1 conservative. This requires Broadcom bnxt_re RDMA hardware, variable WQE support, and local RDMA userspace access.
* No memory corruption signal. The patch is a validation-only fix that rejects sq_slots equal to zero or greater than 65536 with EINVAL.
* No LPE signal. There is no demonstrated reclaim, overwrite, stale callback, refcount abuse, type confusion, or arbitrary write.
* No high-control API bonus. RDMA uverbs object configuration alone is not enough without evidence of attacker control over memory lifetime, layout, DMA mappings, callbacks, or page ownership.

3. Reachability analysis
A local user or service with permission to use the bnxt_re RDMA userspace device can trigger the affected path by requesting variable WQE mode with an invalid sq_slots value. This is not directly network reachable because the value is supplied by the local QP creation path, not by a remote RDMA peer. Namespace or container impact depends on whether RDMA device access is delegated into the container. If access is not delegated, practical reachability is limited to privileged or trusted local users. The path is hardware and configuration dependent and is not a broad default Linux exposure.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like validation issue rather than an Important kernel vulnerability. The theoretical impact is local device or driver availability degradation from an unsupported SQ configuration. Realistic exploitation evidence is weak because the patch and commit do not show memory corruption, a reliable kernel crash, privilege escalation, information disclosure, or a cross-boundary security bypass. The validation-only unspecified-corruption cap applies.

5. One-sentence report phrase
RDMA/bnxt_re failed to validate the user supplied sq_slots value for variable WQE mode, allowing a local RDMA uverbs user to request zero or above 64K SQ slots and potentially cause invalid QP setup or device availability problems.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. This is a validation-only RDMA device configuration issue with no concrete memory corruption or privilege escalation primitive shown.

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

Patch: RDMA/bnxt_re: Add a max slot check for SQ [ Upstream
Commit: a59d815cbe667929b693b5fa6716a074e6a31c5b
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a59d815cbe667929b693b5fa6716a074e6a31c5b

Changed files:
  drivers/infiniband/hw/bnxt_re/ib_verbs.c
  drivers/infiniband/hw/bnxt_re/qplib_sp.h

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=a59d815cbe667929b693b5fa6716a074e6a31c5b

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

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

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:L/UI:N/S:U/C:N/I:N/A:L
  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: 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).