CVE-2023-53224
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.16 (inc) to 4.19.274 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.233 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.170 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.96 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.14 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves a function prototype mismatch in the Linux kernel's ext4 filesystem module. Specifically, the 'ext4_feat_ktype' function was setting a 'release' handler to 'kfree', which does not match the expected function prototype. With Clang's kernel control flow integrity (kCFI) enabled, indirect function calls are checked against expected prototypes to prevent invalid calls that could lead to security issues like ROP attacks. Because of the mismatch, when the ext4 module is unloaded, this causes a runtime failure such as a kernel panic or thread termination. The fix involved adding a wrapper with the correct function prototype to prevent these failures.
How can this vulnerability impact me? :
If you are using the ext4 filesystem as a loadable kernel module and it is unloaded, this vulnerability can cause a kernel panic or cause threads to be killed due to control flow integrity failures. This can lead to system instability or crashes, potentially disrupting services or causing data loss during module unload operations.