[CVE-2026-72498][MODERATE REGULAR] RDMA/bnxt_re: Avoid displaying the kernel pointer [ Upstream

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

CVE: CVE-2026-72498
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: RDMA/bnxt_re: Avoid displaying the kernel pointer [ Upstream
Commit: 95d46a8d3ba9fdbe356fe7ed0117bc78dac9d557
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=95d46a8d3ba9fdbe356fe7ed0117bc78dac9d557
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72498
Analysis date: Sat, 15 Aug 2026 16:27:07 -0400
ActionableScore: 1
ActionableScore lower bound: 0
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-72498 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72498

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: NO

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

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

CVE-2026-72498	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N';*CWE-200;CWE-497;CWE-668;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N';BEST CVSS score: '3.3';DESCR 'bnxt_re exposed the mr_hwq kernel pointer in RDMA driver specific MR resource output through the rdma tool. This is a local information disclosure that can reveal a kernel address and weaken KASLR, which may help an attacker chain this bug with a separate kernel memory corruption issue. For the CVSS the PR:L is used for the paranoid score because local users, service accounts, container root, or delegated RDMA administration contexts may be able to query RDMA resource dumps without being full host root. The issue is not network reachable by packet traffic and does not directly provide write access, code execution, or denial of service. Impact is confidentiality only via kernel address disclosure.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	NETWORK  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS	YES	NO	checked

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

ActionableScore=1
ActionableScoreLower=0

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

2. Signal breakdown
* Confidentiality impact plausible: +1. The RDMA resource dump exposed `mr_hwq`, which is a kernel pointer and can weaken KASLR.
* Local unprivileged trigger: +1 only in the paranoid interpretation. This depends on whether non-root local users or delegated RDMA administration contexts can query this RDMA resource dump.
* Requires admin/root/CAP_* in typical deployments: -2 for the conservative score. RDMA resource inspection is commonly limited to privileged administration contexts.
* Rare AND difficult-to-reach subsystem/configuration: -1. The issue is specific to the Broadcom `bnxt_re` RDMA driver and requires the relevant hardware, driver, and RDMA tooling path.
* No memory corruption signal. The patch removes a printed pointer and does not indicate UAF, OOB access, arbitrary write, refcount misuse, or object lifetime corruption.
* No reliable DoS signal. The bug is information disclosure only.

3. Reachability analysis
The bug is triggered through the RDMA netlink/resource dump path used by the `rdma` tool when dumping MR information for `bnxt_re`. It is not reachable by ordinary network packet traffic. In conservative scoring, the attacker needs administrative or RDMA-management privileges, so the score remains very low. In the paranoid case, local service accounts, container root, or delegated RDMA administration may have enough access to query the resource dump without being full host root, but that still yields only a kernel pointer leak.

Call-site confidence: high. The provided diff directly shows the removed `rdma_nl_put_driver_u64_hex(..., "hwq", (unsigned long)mr_hwq)` output.

4. Severity interpretation
This behaves like a low-severity local information disclosure, not an Important-class vulnerability. The realistic impact is KASLR weakening that may assist a separate exploit chain, but there is no standalone privilege escalation, integrity impact, availability impact, or memory corruption primitive shown by the patch. Manual verification of RDMA netlink permissions is useful, but the technical bug itself is not an actionable Moderate by the scoring formula.

5. One-sentence report phrase
`bnxt_re exposed a kernel pointer in RDMA MR resource dump output, allowing local disclosure of a kernel address and possible KASLR weakening, but without direct memory corruption, privilege escalation, or DoS.`

6. Manual review recommendation
MANUAL CHECK RECOMMENDED.
Check whether the affected product allows non-root users, container root, or delegated RDMA service accounts to run the relevant RDMA resource dump operation. If access is root-only in the target configuration, this can likely be treated as low priority.

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

Patch: RDMA/bnxt_re: Avoid displaying the kernel pointer [ Upstream
Commit: 95d46a8d3ba9fdbe356fe7ed0117bc78dac9d557
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=95d46a8d3ba9fdbe356fe7ed0117bc78dac9d557

Changed files:
  drivers/infiniband/hw/bnxt_re/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=95d46a8d3ba9fdbe356fe7ed0117bc78dac9d557

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

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

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:H/UI:N/S:U/C:L/I:N/A:N
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
  The Best / paranoid CVSS score: 3.3

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: 0
  Paranoid ActionableScore: 1

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