CVE-2023-53504
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-01

Last updated on: 2025-10-02

Assigner: kernel.org

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-01
Last Modified
2025-10-02
Generated
2026-06-16
AI Q&A
2025-10-01
EPSS Evaluated
2026-06-14
NVD
CVE-2023-53504
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves improper ordering of the function ib_device_unalloc() in the RDMA/bnxt_re driver. The function ib_dealloc_device() was being called before the device cleanup was completed, which could lead to a use-after-free (UAF) condition. The fix ensures that ib_dealloc_device() is called only after the device cleanup, preventing the UAF issue.

Impact Analysis

The vulnerability could lead to a use-after-free condition in the Linux kernel's RDMA/bnxt_re driver, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or cause denial of service. The exact impact depends on the environment and how the affected driver is used.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2023-53504. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart