LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.

Validation and detection

  • Inventory running kernel versions, loaded bnxt_re modules, and associated RDMA hardware.
  • Map each kernel package to its distribution advisory and backported fix status.
  • Confirm the applicable stable-kernel correction is present in deployed source or package metadata.
  • After updating, reboot into the corrected kernel and verify the active version.
  • Test legitimate large RDMA resource workloads in a controlled environment for stability.
Prepared
Confidence
medium
Sources
5

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-50208 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-50208Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0c4dcd602817502bb3dced7a834a13ef717d65a4, 0c4dcd602817502bb3dced7a834a13ef717d65a4, 0c4dcd602817502bb3dced7a834a13ef717d65a4, 0c4dcd602817502bb3dced7a834a13ef717d65a4, 0c4dcd602817502bb3dced7a834a13ef717d65a4, 0c4dcd602817502bb3dced7a834a13ef717d65a4unaffected
LinuxLinux5.7, 0, 5.10.229, 5.15.170, 6.1.115, 6.6.59, 6.11.6, 6.12affected
Weakness

CWE details

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.