CVE-2023-53373
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 2.6.25 (inc) to 4.14.308 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.276 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.235 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.173 (exc) |
| linux | linux_kernel | From 5.11 (inc) 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 in the Linux kernel's crypto subsystem involves improper handling of the EBUSY error code in the seqiv module. The seqiv module only handled the EINPROGRESS return value correctly, freeing data related to the request in all other cases. However, when the caller specifies MAY_BACKLOG, the seqiv module may receive an EBUSY error, which was not handled properly. This can lead to a use-after-free condition when backlogged requests are processed.
How can this vulnerability impact me? :
The vulnerability can lead to a use-after-free condition in the Linux kernel's crypto subsystem. This type of flaw can cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges by exploiting the improper memory handling.