Security readout for executives and security teams
Plain-English summary
A bounds-checking error in the Linux bnxt_re RDMA driver can write beyond allocated memory while collecting hardware pacing statistics. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability impact. Exposure appears limited to systems using the affected driver and relevant adapters.
Executive priority
Treat this as a high-priority, targeted kernel update rather than an internet-wide emergency. Identify exposed RDMA hosts promptly and patch according to distribution guidance, emphasizing systems accessible to untrusted local users. No active exploitation is established by the supplied evidence.
Technical view
The bnxt_re hardware-statistics path incorrectly checks rdev->dbr_pacing when parsing pacing statistics that are exported only for GenP5 and P7 adapters. KASAN observed an eight-byte slab-out-of-bounds write in bnxt_re_get_hw_stats. The supplied CVSS 3.1 score is 7.8, requiring local access and low privileges without user interaction.
Likely exposure
Prioritize Linux systems running affected kernel builds where the bnxt_re RDMA driver and relevant hardware are present. The supplied version data names 6.6, 6.6.59, 6.11.6, and 6.12 but is insufficiently structured to establish precise vulnerable ranges; confirm distribution backports and vendor status.
Exploitation context
The supplied CVSS vector indicates local, low-privileged exploitation with low complexity and no user interaction. CISA KEV status is false, and the source bundle provides no evidence of active exploitation or a public exploit. Practical reachability beyond the reported KASAN trace is not established.
Researcher notes
The record describes an out-of-bounds write, while the supplied CWE-125 denotes out-of-bounds read; preserve that discrepancy during triage. Three stable-kernel commits are referenced, suggesting branch-specific fixes. Exact vulnerable and corrected version boundaries cannot be reliably reconstructed from the flattened affected-version data alone.
Mitigation direction
- Install a vendor or distribution kernel containing the referenced stable fix or an equivalent backport.
- Check Linux distribution advisories to determine the corrected package version for each deployed release.
- Where operationally acceptable, limit use of the affected RDMA driver until patched.
- Prioritize multi-user or otherwise untrusted systems where local low-privileged access is available.
Validation and detection
- Inventory deployed kernel versions and identify systems using or loading the bnxt_re driver.
- Determine whether relevant GenP5 or P7 adapter configurations are present.
- Verify the installed kernel includes one referenced fix commit or a documented equivalent backport.
- Review kernel and KASAN diagnostics for bnxt_re_get_hw_stats out-of-bounds reports after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2024-50158 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/05c5fcc1869a08e36a29691699b6534e5a00a82bCVE reference, Linux
- https://git.kernel.org/stable/c/c11b9b03ea5252898f91f3388c248f0dc47bda52CVE reference, Linux
- https://git.kernel.org/stable/c/a9e6e7443922ac0a48243c35d03834c96926bff1CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.