CVE-2023-53376
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.14 (inc) to 6.1.18 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.5 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is in the Linux kernel's mpi3mr driver, where bitmap sizes were managed incorrectly using bytes instead of bits. The driver allocated bitmaps based on byte units, but the bitmap helper functions expected bit units, causing memory access beyond allocated bitmap sizes. This led to a kernel bug detected by KASAN as a slab-out-of-bounds error, occurring during firmware download to eHBA-9600. The issue was fixed by changing the bitmap management to use the number of bits, using appropriate bitmap allocation and free functions, and removing obsolete fields related to bitmap byte sizes.
How can this vulnerability impact me? :
This vulnerability can cause out-of-bounds memory access in the Linux kernel, leading to kernel crashes or instability during operations involving the mpi3mr driver, such as firmware downloads to eHBA-9600 devices. This can result in system reliability issues and potential denial of service.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the mpi3mr driver uses the corrected bitmap management approach. Specifically, ensure that the driver uses number of bits to manage bitmap sizes instead of bytes, and uses bitmap_zalloc(), bitmap_free(), and bitmap_clear() functions as described in the fix. Avoid using vulnerable kernel versions that allocate bitmaps incorrectly in the mpi3mr driver.