CVE-2023-53660
BaseFortify
Publication date: 2025-10-07
Last updated on: 2026-02-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.2 (inc) to 6.4.10 (inc) |
| linux | linux_kernel | 6.5.0-rc2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves improper handling of skb (socket buffer) objects during cleanup in the bpf cpumap feature. Specifically, the __cpu_map_ring_cleanup() function does not handle skb mode correctly and mistakenly treats skbs in ptr_ring as XDP frames, which leads to warnings and potential incorrect behavior. The issue arises when a kernel thread (kthread) stops prematurely, causing ptr_ring to contain skbs that are not properly freed, resulting in a warning about incorrect XDP memory type usage.
How can this vulnerability impact me? :
This vulnerability can cause warnings and potentially unstable behavior in the Linux kernel when using the bpf cpumap feature with skb mode enabled. It may lead to improper cleanup of network buffers, which could affect system stability or performance during network packet processing, especially under stress conditions. However, no direct security impact or exploitation details are provided.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing the kernel warning messages related to XDP memory type usage. Specifically, look for warnings like 'Incorrect XDP memory type (-2128176192) usage' in the kernel logs. You can check for such messages using the command: dmesg | grep -i 'Incorrect XDP memory type' or dmesg | grep -i xdp. Monitoring kernel logs for warnings related to xdp_redirect_cpu and skb-mode stress conditions can help identify the issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability is resolved, as the issue is fixed by handling skb cleanup properly in ptr_ring and fixing prematurely stopped kthreads. Until an update is applied, avoid running xdp_redirect_cpu with both skb-mode and stress-mode enabled simultaneously to prevent triggering the warning and potential instability.