CVE-2023-54216
Use-After-Free Vulnerability in Linux mlx5e TC NIC Mode
Publication date: 2025-12-30
Last updated on: 2025-12-30
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mlx | mlx5_core | * |
| mlx5 | mlx5_core | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by monitoring your system logs for kernel messages indicating a KASAN slab-use-after-free bug related to mlx5_core, specifically messages similar to the trace shown in the description. Checking dmesg or journalctl logs for entries containing 'BUG: KASAN: slab-use-after-free in mlx5_add_flow_rules' or related mlx5_core errors can help identify the issue. For example, use commands like 'dmesg | grep mlx5_core' or 'journalctl -k | grep mlx5_core' to look for these error messages.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version that includes the fix for this vulnerability, which corrects the use of eswitch object mapping pool in nic mode. Until an update is applied, monitoring for the error messages and avoiding configurations that trigger the mlx5e TC eswitch mapping in nic mode may reduce exposure. Applying vendor patches or kernel updates that address this issue is the recommended step.
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's mlx5_core driver involves improper use of the eswitch object mapping pool when operating in nic mode. The eswitch mapping pool is used without being initialized in nic mode, leading to a use-after-free bug detected by KASAN (Kernel Address Sanitizer). This bug can cause the kernel to access freed memory, potentially leading to system instability or crashes.
How can this vulnerability impact me? :
The vulnerability can cause kernel crashes or instability due to use-after-free errors in the mlx5_core driver. This may affect network functionality on systems using this driver, potentially leading to denial of service or degraded performance.