CVE-2025-38465
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-11-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a flaw in the Linux kernel's netlink implementation where the sk_rmem_alloc variable, which tracks socket memory usage, can wrap around due to improper handling of integer overflow. Specifically, the code compares signed integers where it should use unsigned integers, allowing a socket to allocate more memory than intended. This can lead to a single socket consuming excessive memory until the system runs out of memory (OOM). The fix involves using atomic_add_return() and comparing the variables as unsigned integers to prevent wraparound.
How can this vulnerability impact me? :
This vulnerability can allow a single socket to consume an excessive amount of memory by exploiting the wraparound issue in sk_rmem_alloc. This can lead to the system running out of memory (OOM), potentially causing denial of service or system instability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by inspecting netlink socket statistics for abnormal Recv-Q values that indicate wraparound of sk->sk_rmem_alloc. The example command to check netlink sockets is: ss -f netlink. Look for unusually large or negative Recv-Q values, which may indicate the wraparound issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version that includes the fix for the sk->sk_rmem_alloc wraparound issue. The fix uses atomic_add_return() and compares variables as unsigned int to prevent wraparound. Until the update is applied, monitoring netlink socket usage and limiting socket buffer sizes may help reduce risk.