CVE-2023-53282
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-12-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | to 5.15.99 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.16 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free bug in the Linux kernel's lpfc driver during the sysfs firmware write process. Specifically, the driver accesses memory (wr_object pointer data) that has already been freed and returned to the mailbox pool, causing a use-after-free read error. The issue occurs because the mailbox free calls happen too early in the routine, and the fix involves moving these free calls to the end to avoid referencing freed memory.
How can this vulnerability impact me? :
This vulnerability can cause kernel instability or crashes due to use-after-free memory access. It may lead to system reliability issues or potential exploitation if an attacker can trigger the firmware write process, possibly resulting in denial of service or other unintended behavior.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the kernel logs for KFENCE use-after-free read warnings related to the lpfc driver during sysfs firmware write operations. Specifically, look for messages similar to: 'BUG: KFENCE: use-after-free read in lpfc_wr_object'. You can use the command 'dmesg | grep -i kfence' or 'journalctl -k | grep -i kfence' to find such warnings in the kernel logs.
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. The fix involves changes in the lpfc driver to avoid referencing mailbox memory after it has been released. Until an update is applied, avoid performing sysfs firmware write operations on the lpfc driver to reduce the risk of triggering the use-after-free condition.