CVE-2023-54262
Use-After-Free in Linux mlx5e Driver Due to Double Attribute Cloning
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 |
|---|---|---|
| mlx5 | mlx5_core | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's mlx5e driver involves improper handling of flow post action attributes. The code mistakenly clones these attributes twice, which is unnecessary and leads to a use-after-free error. Specifically, the second cloned copy is not properly updated, causing memory access issues that can result in kernel bugs and crashes.
How can this vulnerability impact me? :
The vulnerability can cause kernel crashes or instability due to use-after-free errors in the mlx5e driver. This can lead to system reliability issues, potential denial of service, and unexpected behavior in network operations relying on this driver.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for specific error messages related to the mlx5_core module, such as use-after-free bugs reported by KASAN (Kernel Address Sanitizer). Look for log entries mentioning 'BUG: KASAN: use-after-free in mlx5_cmd_set_fte', 'mlx5_core: Failed to add post action rule', or 'Failed to update flow post acts'. Commands to check these logs include: 'dmesg | grep mlx5_core' or 'journalctl -k | grep mlx5_core'.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, as the issue is resolved by correcting the cloning of flow post action attributes in the mlx5e driver. Until an update is applied, monitoring for related kernel errors and avoiding configurations that trigger mlx5e post action rules may reduce risk.