CVE-2024-57841: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in tcp_conn_request() If inet_csk_reqsk_queue_hash_add() return false, tcp_conn_request() will return without free the dst memory, which allocated in af_ops->route_req. Here is the kmemleak stack: unreferenced object 0xffff8881198631c0 (size 240): comm "softirq", pid 0, jiffies 4299266571 (age 1802.392s) hex dump (first 32 bytes): 00 10 9b 03 81 88 ff ff 80 98 da bc ff ff ff ff ................ 81 55 18 bb ff ff ff ff 00 00 00 00 00 00 00 00 .U.............. backtrace: [<ffffffffb93e8d4c>] kmem_cache_alloc+0x60c/0xa80 [<ffffffffba11b4c5>] dst_alloc+0x55/0x250 [<ffffffffba227bf6>] rt_dst_alloc+0x46/0x1d0 [<ffffffffba23050a>] __mkroute_output+0x29a/0xa50 [<ffffffffba23456b>] ip_route_output_key_hash+0x10b/0x240 [<ffffffffba2346bd>] ip_route_output_flow+0x1d/0x90 [<ffffffffba254855>] inet_csk_route_req+0x2c5/0x500 [<ffffffffba26b331>] tcp_conn_request+0x691/0x12c0 [<ffffffffba27bd08>] tcp_rcv_state_process+0x3c8/0x11b0 [<ffffffffba2965c6>] tcp_v4_do_rcv+0x156/0x3b0 [<ffffffffba299c98>] tcp_v4_rcv+0x1cf8/0x1d80 [<ffffffffba239656>] ip_protocol_deliver_rcu+0xf6/0x360 [<ffffffffba2399a6>] ip_local_deliver_finish+0xe6/0x1e0 [<ffffffffba239b8e>] ip_local_deliver+0xee/0x360 [<ffffffffba239ead>] ip_rcv+0xad/0x2f0 [<ffffffffba110943>] __netif_receive_skb_one_core+0x123/0x140 Call dst_release() to free the dst memory when inet_csk_reqsk_queue_hash_add() return false in tcp_conn_request().
AI Analysis
Technical Summary
CVE-2024-57841 is a memory leak vulnerability identified in the Linux kernel's TCP networking stack, specifically within the tcp_conn_request() function. The issue arises when the function inet_csk_reqsk_queue_hash_add() returns false, causing tcp_conn_request() to exit without freeing the destination (dst) memory that was allocated via af_ops->route_req. This memory allocation is part of the routing subsystem, where dst structures represent cached routing information. The vulnerability was detected through kmemleak, a kernel memory leak detector, which identified unreferenced objects in the kernel memory allocated during TCP connection request processing. The root cause is a missing call to dst_release() to free the allocated dst memory when inet_csk_reqsk_queue_hash_add() fails. This leads to a gradual memory leak in the kernel's networking code, potentially causing increased memory consumption over time, which can degrade system performance or lead to resource exhaustion. The vulnerability affects multiple Linux kernel versions identified by specific commit hashes, indicating it is present in several recent kernel builds. No known exploits are reported in the wild as of the publication date (January 15, 2025), and no CVSS score has been assigned. The fix involves ensuring that dst_release() is called to properly free the allocated memory when the queue hash addition fails, preventing the leak.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions, which are common in servers, network appliances, and embedded devices. The memory leak can lead to gradual degradation of system stability and performance, especially in high-traffic network environments such as data centers, cloud infrastructure, and telecommunications equipment. Over time, the leak could cause kernel memory exhaustion, potentially leading to system crashes or forced reboots, impacting availability of critical services. While this vulnerability does not directly allow code execution or privilege escalation, the denial-of-service-like impact through resource exhaustion can disrupt business operations. Organizations relying on Linux-based infrastructure for web hosting, financial services, healthcare, or critical industrial control systems could experience service interruptions. Additionally, the leak could be exploited by attackers to increase the likelihood of denial-of-service conditions by triggering numerous TCP connection requests, amplifying the impact. Given the widespread use of Linux in European IT environments, the vulnerability's impact could be significant if left unpatched.
Mitigation Recommendations
To mitigate CVE-2024-57841, European organizations should: 1) Identify and inventory all Linux systems running affected kernel versions by checking kernel commit hashes or version numbers. 2) Apply the official Linux kernel patches that fix the memory leak as soon as they become available from trusted sources such as the Linux kernel mailing list or vendor security advisories. 3) For systems where immediate patching is not feasible, implement monitoring of kernel memory usage and network subsystem metrics to detect abnormal memory growth indicative of the leak. 4) Limit exposure by restricting unnecessary TCP connection requests from untrusted networks, using firewall rules or network segmentation to reduce attack surface. 5) Employ kernel live patching solutions if supported by the environment to apply fixes without downtime. 6) Regularly update and audit network-facing services to ensure they do not inadvertently trigger excessive TCP connection requests. 7) Engage with Linux distribution vendors for backported patches and security updates tailored to their kernels. These steps go beyond generic advice by emphasizing proactive inventory, monitoring, and network-level controls specific to this vulnerability's nature.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Poland, Belgium, Finland
CVE-2024-57841: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in tcp_conn_request() If inet_csk_reqsk_queue_hash_add() return false, tcp_conn_request() will return without free the dst memory, which allocated in af_ops->route_req. Here is the kmemleak stack: unreferenced object 0xffff8881198631c0 (size 240): comm "softirq", pid 0, jiffies 4299266571 (age 1802.392s) hex dump (first 32 bytes): 00 10 9b 03 81 88 ff ff 80 98 da bc ff ff ff ff ................ 81 55 18 bb ff ff ff ff 00 00 00 00 00 00 00 00 .U.............. backtrace: [<ffffffffb93e8d4c>] kmem_cache_alloc+0x60c/0xa80 [<ffffffffba11b4c5>] dst_alloc+0x55/0x250 [<ffffffffba227bf6>] rt_dst_alloc+0x46/0x1d0 [<ffffffffba23050a>] __mkroute_output+0x29a/0xa50 [<ffffffffba23456b>] ip_route_output_key_hash+0x10b/0x240 [<ffffffffba2346bd>] ip_route_output_flow+0x1d/0x90 [<ffffffffba254855>] inet_csk_route_req+0x2c5/0x500 [<ffffffffba26b331>] tcp_conn_request+0x691/0x12c0 [<ffffffffba27bd08>] tcp_rcv_state_process+0x3c8/0x11b0 [<ffffffffba2965c6>] tcp_v4_do_rcv+0x156/0x3b0 [<ffffffffba299c98>] tcp_v4_rcv+0x1cf8/0x1d80 [<ffffffffba239656>] ip_protocol_deliver_rcu+0xf6/0x360 [<ffffffffba2399a6>] ip_local_deliver_finish+0xe6/0x1e0 [<ffffffffba239b8e>] ip_local_deliver+0xee/0x360 [<ffffffffba239ead>] ip_rcv+0xad/0x2f0 [<ffffffffba110943>] __netif_receive_skb_one_core+0x123/0x140 Call dst_release() to free the dst memory when inet_csk_reqsk_queue_hash_add() return false in tcp_conn_request().
AI-Powered Analysis
Technical Analysis
CVE-2024-57841 is a memory leak vulnerability identified in the Linux kernel's TCP networking stack, specifically within the tcp_conn_request() function. The issue arises when the function inet_csk_reqsk_queue_hash_add() returns false, causing tcp_conn_request() to exit without freeing the destination (dst) memory that was allocated via af_ops->route_req. This memory allocation is part of the routing subsystem, where dst structures represent cached routing information. The vulnerability was detected through kmemleak, a kernel memory leak detector, which identified unreferenced objects in the kernel memory allocated during TCP connection request processing. The root cause is a missing call to dst_release() to free the allocated dst memory when inet_csk_reqsk_queue_hash_add() fails. This leads to a gradual memory leak in the kernel's networking code, potentially causing increased memory consumption over time, which can degrade system performance or lead to resource exhaustion. The vulnerability affects multiple Linux kernel versions identified by specific commit hashes, indicating it is present in several recent kernel builds. No known exploits are reported in the wild as of the publication date (January 15, 2025), and no CVSS score has been assigned. The fix involves ensuring that dst_release() is called to properly free the allocated memory when the queue hash addition fails, preventing the leak.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions, which are common in servers, network appliances, and embedded devices. The memory leak can lead to gradual degradation of system stability and performance, especially in high-traffic network environments such as data centers, cloud infrastructure, and telecommunications equipment. Over time, the leak could cause kernel memory exhaustion, potentially leading to system crashes or forced reboots, impacting availability of critical services. While this vulnerability does not directly allow code execution or privilege escalation, the denial-of-service-like impact through resource exhaustion can disrupt business operations. Organizations relying on Linux-based infrastructure for web hosting, financial services, healthcare, or critical industrial control systems could experience service interruptions. Additionally, the leak could be exploited by attackers to increase the likelihood of denial-of-service conditions by triggering numerous TCP connection requests, amplifying the impact. Given the widespread use of Linux in European IT environments, the vulnerability's impact could be significant if left unpatched.
Mitigation Recommendations
To mitigate CVE-2024-57841, European organizations should: 1) Identify and inventory all Linux systems running affected kernel versions by checking kernel commit hashes or version numbers. 2) Apply the official Linux kernel patches that fix the memory leak as soon as they become available from trusted sources such as the Linux kernel mailing list or vendor security advisories. 3) For systems where immediate patching is not feasible, implement monitoring of kernel memory usage and network subsystem metrics to detect abnormal memory growth indicative of the leak. 4) Limit exposure by restricting unnecessary TCP connection requests from untrusted networks, using firewall rules or network segmentation to reduce attack surface. 5) Employ kernel live patching solutions if supported by the environment to apply fixes without downtime. 6) Regularly update and audit network-facing services to ensure they do not inadvertently trigger excessive TCP connection requests. 7) Engage with Linux distribution vendors for backported patches and security updates tailored to their kernels. These steps go beyond generic advice by emphasizing proactive inventory, monitoring, and network-level controls specific to this vulnerability's nature.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-01-15T13:08:59.716Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9820c4522896dcbdd1af
Added to database: 5/21/2025, 9:08:48 AM
Last enriched: 6/27/2025, 10:55:27 PM
Last updated: 8/8/2025, 6:22:10 PM
Views: 14
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.