CVE-2023-53190
BaseFortify
Publication date: 2025-09-15
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 | From 5.18 (inc) to 6.0.19 (exc) |
| linux | linux_kernel | From 6.1 (inc) to 6.1.5 (exc) |
| linux | linux_kernel | 6.2 |
| linux | linux_kernel | 6.2 |
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 is a memory leak in the Linux kernel's VXLAN implementation. Specifically, memory allocated by the function vxlan_vnigroup_init() is not properly freed in the error path, which means that if an error occurs during initialization, the allocated memory remains allocated and is not released. This can lead to wasted memory resources over time. The issue is fixed by ensuring that vxlan_vnigroup_uninit() is called to free the memory in the error path.
How can this vulnerability impact me? :
The impact of this vulnerability is that it can cause memory leaks in the Linux kernel when using VXLAN networking features. Over time, these leaks can consume system memory unnecessarily, potentially leading to reduced system performance or even failure to allocate memory for other processes. This could affect system stability and reliability, especially in environments heavily using VXLAN.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by reproducing the memory leak using error injection in the Linux kernel debug interface. The following commands can be used to trigger the issue and observe the memory leak: # echo "100" > /sys/kernel/debug/fail_function/probability # echo "1" > /sys/kernel/debug/fail_function/times # echo "gro_cells_init" > /sys/kernel/debug/fail_function/inject # printf %#x -12 > /sys/kernel/debug/fail_function/gro_cells_init/retval # ip link add name vxlan0 type vxlan dstport 4789 external vnifilter If the last command returns "RTNETLINK answers: Cannot allocate memory", it indicates the memory leak condition related to this vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the fix that calls vxlan_vnigroup_uninit() in the error path to free allocated memory properly. Practically, this means updating the Linux kernel to a version where this vulnerability is resolved. Until then, monitoring for memory leaks related to vxlan and avoiding triggering the error path may help reduce impact.