CVE-2024-50208: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages
In the Linux kernel, the following vulnerability has been resolved:
RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages
Avoid memory corruption while setting up Level-2 PBL pages for the non MR
resources when num_pages > 256K.
There will be a single PDE page address (contiguous pages in the case of >
PAGE_SIZE), but, current logic assumes multiple pages, leading to invalid
memory access after 256K PBL entries in the PDE.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux bnxt_re RDMA driver can corrupt kernel memory when unusually large page-buffer resources are configured. Successful triggering requires local, low-privileged access according to the supplied CVSS data. Impact could include system compromise or disruption, but the supplied sources do not establish exploitation in the wild.
Executive priority
Treat as a high-priority kernel update for bnxt_re RDMA systems, especially shared compute or infrastructure allowing local untrusted access. Patch through supported distribution channels. Other Linux systems should still be inventoried, but urgency depends on whether the affected driver and resource path are reachable.
Technical view
For non-memory-region resources exceeding 256K PBL entries, bnxt_re incorrectly treats one contiguous Level-2 PDE allocation as multiple pages. Subsequent indexing can access invalid memory and cause kernel memory corruption. The supplied CVSS 3.1 vector is local, low-complexity, low-privilege, no-user-interaction, with high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is concentrated on affected Linux systems using the bnxt_re RDMA driver and capable of creating the unusually large resources involved. Systems without that driver or relevant RDMA use are less likely exposed. The supplied version data is ambiguous, so distribution-specific package status should control decisions.
Exploitation context
The supplied bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. The required access is local rather than network-based. Practical reachability also appears dependent on bnxt_re hardware, driver use, and allocation of more than 256K PBL entries.
Researcher notes
The record maps the issue to CWE-125, while its description more broadly states invalid memory access and memory corruption. Do not infer a specific exploitation primitive from that wording alone. Exact vulnerable and fixed version boundaries are not clearly represented in the supplied affected-version list; verify stable commits and distribution backports.
Mitigation direction
Install the vendor-supported kernel package containing the bnxt_re correction.
Consult the Linux distribution advisory to confirm the fixed package version or backport.
Prioritize RDMA hosts where untrusted or lower-privileged users can access relevant resources.
If immediate patching is impossible, restrict affected RDMA functionality after operational review.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.