LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53504: RDMA/bnxt_re: Properly order ib_device_unalloc() to avoid UAF

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Properly order ib_device_unalloc() to avoid UAF ib_dealloc_device() should be called only after device cleanup. Fix the dealloc sequence.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux RDMA driver can free a device object before cleanup finishes, creating a use-after-free condition. A local, low-privileged attacker could potentially crash an affected system or compromise its confidentiality and integrity. Risk is concentrated on systems using the bnxt_re driver, rather than every Linux installation.

Executive priority

Treat as a high-priority maintenance issue for exposed RDMA hosts, especially shared or multi-user systems where untrusted users obtain local access. Ordinary systems without bnxt_re usage are less likely to be exposed. Confirm affected assets before emergency-wide disruption.

Technical view

The bnxt_re teardown sequence deallocated an RDMA device before completing device cleanup, allowing later cleanup activity to reference freed memory. The kernel correction reorders deallocation so cleanup completes first. The supplied CVSS 3.1 score is 7.8, with local access, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impacts.

Likely exposure

Exposure requires an affected Linux kernel and relevant bnxt_re RDMA functionality. The bundle associates affected version data with Linux 6.3 through 6.5, but does not establish precise distribution-package boundaries. Vendor backports may change exposure, so kernel version alone is insufficient.

Exploitation context

The CVSS vector describes a local, low-privileged attack requiring no user interaction. The source bundle does not report active exploitation, and the CVE is not identified as CISA KEV. It provides no evidence about public proof-of-concept availability or demonstrated privilege escalation.

Researcher notes

The evidence establishes a teardown-order use-after-free and supplies two stable-kernel commits. It does not document the triggering lifecycle path, exploit reliability, affected distribution packages, or observed attacks. Researchers should distinguish driver presence from active hardware use and verify backports by patch content rather than version strings alone.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced bnxt_re device-deallocation fix or an equivalent backport.
  • Prioritize hosts where the bnxt_re RDMA driver is installed, loaded, or tied to active hardware.
  • If immediate updating is impossible, consult the distribution vendor for supported temporary mitigation guidance.

Validation and detection

  • Inventory kernel versions and distribution package releases on systems providing RDMA services.
  • Determine whether bnxt_re is present, loaded, and associated with active RDMA hardware.
  • Verify package changelogs or vendor advisories show either referenced fix commit or an equivalent backport.
  • After updating, confirm the running kernel changed and exercise approved device cleanup while monitoring kernel errors.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2023-53504 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.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-53504Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6d758147c7b80a46465f72e9e6294d244ee98a21, 6d758147c7b80a46465f72e9e6294d244ee98a21unaffected
LinuxLinux6.3, 0, 6.4.11, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.