CVE-2023-53331
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-12-10
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 3.18.133 (inc) to 3.19 (exc) |
| linux | linux_kernel | From 4.4.172 (inc) to 4.5 (exc) |
| linux | linux_kernel | From 4.9.153 (inc) to 4.10 (exc) |
| linux | linux_kernel | From 4.14.96 (inc) to 4.14.326 (exc) |
| linux | linux_kernel | From 4.19.18 (inc) to 4.19.295 (exc) |
| linux | linux_kernel | From 4.20.5 (inc) to 5.4.257 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.195 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.132 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.53 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.4.16 (exc) |
| linux | linux_kernel | From 6.5 (inc) to 6.5.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes 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 pstore/ram component. After a certain commit, the initialization process incorrectly assumed that a persistent RAM zone (prz) was valid if its buffer size was zero, without properly checking the start position of the buffer. This unchecked start value could be outside the buffer bounds, which may lead to kernel panics when the system tries to write to this invalid memory area. The fix involves adding a check for the start position during initialization to ensure it is valid and resetting the buffer if it is not.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic due to invalid memory access when writing to an improperly initialized persistent RAM buffer. Such kernel panics can lead to system crashes, instability, and potential data loss or downtime.