CVE-2024-36904: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). Anderson Nascimento reported a use-after-free splat in tcp_twsk_unique() with nice analysis. Since commit ec94c2696f0b ("tcp/dccp: avoid one atomic operation for timewait hashdance"), inet_twsk_hashdance() sets TIME-WAIT socket's sk_refcnt after putting it into ehash and releasing the bucket lock. Thus, there is a small race window where other threads could try to reuse the port during connect() and call sock_hold() in tcp_twsk_unique() for the TIME-WAIT socket with zero refcnt. If that happens, the refcnt taken by tcp_twsk_unique() is overwritten and sock_put() will cause underflow, triggering a real use-after-free somewhere else. To avoid the use-after-free, we need to use refcount_inc_not_zero() in tcp_twsk_unique() and give up on reusing the port if it returns false. [0]: refcount_t: addition on 0; use-after-free. WARNING: CPU: 0 PID: 1039313 at lib/refcount.c:25 refcount_warn_saturate+0xe5/0x110 CPU: 0 PID: 1039313 Comm: trigger Not tainted 6.8.6-200.fc39.x86_64 #1 Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023 RIP: 0010:refcount_warn_saturate+0xe5/0x110 Code: 42 8e ff 0f 0b c3 cc cc cc cc 80 3d aa 13 ea 01 00 0f 85 5e ff ff ff 48 c7 c7 f8 8e b7 82 c6 05 96 13 ea 01 01 e8 7b 42 8e ff <0f> 0b c3 cc cc cc cc 48 c7 c7 50 8f b7 82 c6 05 7a 13 ea 01 01 e8 RSP: 0018:ffffc90006b43b60 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff888009bb3ef0 RCX: 0000000000000027 RDX: ffff88807be218c8 RSI: 0000000000000001 RDI: ffff88807be218c0 RBP: 0000000000069d70 R08: 0000000000000000 R09: ffffc90006b439f0 R10: ffffc90006b439e8 R11: 0000000000000003 R12: ffff8880029ede84 R13: 0000000000004e20 R14: ffffffff84356dc0 R15: ffff888009bb3ef0 FS: 00007f62c10926c0(0000) GS:ffff88807be00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020ccb000 CR3: 000000004628c005 CR4: 0000000000f70ef0 PKRU: 55555554 Call Trace: <TASK> ? refcount_warn_saturate+0xe5/0x110 ? __warn+0x81/0x130 ? refcount_warn_saturate+0xe5/0x110 ? report_bug+0x171/0x1a0 ? refcount_warn_saturate+0xe5/0x110 ? handle_bug+0x3c/0x80 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? refcount_warn_saturate+0xe5/0x110 tcp_twsk_unique+0x186/0x190 __inet_check_established+0x176/0x2d0 __inet_hash_connect+0x74/0x7d0 ? __pfx___inet_check_established+0x10/0x10 tcp_v4_connect+0x278/0x530 __inet_stream_connect+0x10f/0x3d0 inet_stream_connect+0x3a/0x60 __sys_connect+0xa8/0xd0 __x64_sys_connect+0x18/0x20 do_syscall_64+0x83/0x170 entry_SYSCALL_64_after_hwframe+0x78/0x80 RIP: 0033:0x7f62c11a885d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a3 45 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007f62c1091e58 EFLAGS: 00000296 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 0000000020ccb004 RCX: 00007f62c11a885d RDX: 0000000000000010 RSI: 0000000020ccb000 RDI: 0000000000000003 RBP: 00007f62c1091e90 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000296 R12: 00007f62c10926c0 R13: ffffffffffffff88 R14: 0000000000000000 R15: 00007ffe237885b0 </TASK>
AI Analysis
Technical Summary
CVE-2024-36904 is a use-after-free vulnerability identified in the Linux kernel's TCP stack, specifically within the tcp_twsk_unique() function. The vulnerability arises due to a race condition introduced after commit ec94c2696f0b, which modified the handling of TIME-WAIT sockets in the inet_twsk_hashdance() function. This commit sets the socket's reference count (sk_refcnt) after placing the TIME-WAIT socket into the ehash and releasing the bucket lock, creating a small window where concurrent threads can attempt to reuse the port during a connect() call. During this window, if another thread calls sock_hold() on the TIME-WAIT socket with a zero reference count, the reference count increment is incorrectly handled. The tcp_twsk_unique() function uses a standard increment rather than a safe conditional increment, leading to an underflow in the reference count when sock_put() is later called. This underflow triggers a use-after-free condition, where the kernel may access freed memory, potentially causing system instability or crashes. The patch involves replacing the reference count increment with refcount_inc_not_zero(), which only increments if the count is non-zero, thereby preventing reuse of the port in this race window and eliminating the use-after-free scenario. The vulnerability was reported by Anderson Nascimento and affects Linux kernel versions including and around commit ec94c2696f0b. There are no known exploits in the wild at the time of publication, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running vulnerable Linux kernel versions, which are widely used in servers, cloud infrastructure, and embedded devices across Europe. Exploitation could lead to kernel crashes or denial of service (DoS) conditions, impacting availability of critical services. In environments with high concurrency and network connection rates, the race condition could be triggered more frequently, increasing the risk of instability. Although no direct remote code execution or privilege escalation is indicated, the use-after-free could potentially be leveraged in complex attack chains to escalate privileges or bypass security mechanisms if combined with other vulnerabilities. Given the prevalence of Linux in European data centers, telecommunications, and government infrastructure, the vulnerability could disrupt operations if exploited or triggered unintentionally. The lack of known exploits reduces immediate risk, but the vulnerability's nature warrants prompt patching to maintain system reliability and security.
Mitigation Recommendations
European organizations should prioritize updating Linux kernels to versions that include the fix for CVE-2024-36904, specifically those incorporating the patch that replaces the reference count increment with refcount_inc_not_zero() in tcp_twsk_unique(). Kernel updates should be tested and deployed promptly in production environments, especially on systems handling high volumes of TCP connections. For environments where immediate patching is not feasible, organizations should monitor kernel logs for refcount warnings or crashes indicative of this issue. Network administrators can also consider limiting unnecessary TCP connection churn or implementing connection rate limiting to reduce the likelihood of triggering the race condition. Additionally, organizations should maintain robust kernel crash recovery and monitoring mechanisms to quickly detect and respond to instability potentially caused by this vulnerability. Coordination with Linux distribution vendors for timely patch releases and advisories is recommended to ensure comprehensive coverage.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland
CVE-2024-36904: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). Anderson Nascimento reported a use-after-free splat in tcp_twsk_unique() with nice analysis. Since commit ec94c2696f0b ("tcp/dccp: avoid one atomic operation for timewait hashdance"), inet_twsk_hashdance() sets TIME-WAIT socket's sk_refcnt after putting it into ehash and releasing the bucket lock. Thus, there is a small race window where other threads could try to reuse the port during connect() and call sock_hold() in tcp_twsk_unique() for the TIME-WAIT socket with zero refcnt. If that happens, the refcnt taken by tcp_twsk_unique() is overwritten and sock_put() will cause underflow, triggering a real use-after-free somewhere else. To avoid the use-after-free, we need to use refcount_inc_not_zero() in tcp_twsk_unique() and give up on reusing the port if it returns false. [0]: refcount_t: addition on 0; use-after-free. WARNING: CPU: 0 PID: 1039313 at lib/refcount.c:25 refcount_warn_saturate+0xe5/0x110 CPU: 0 PID: 1039313 Comm: trigger Not tainted 6.8.6-200.fc39.x86_64 #1 Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023 RIP: 0010:refcount_warn_saturate+0xe5/0x110 Code: 42 8e ff 0f 0b c3 cc cc cc cc 80 3d aa 13 ea 01 00 0f 85 5e ff ff ff 48 c7 c7 f8 8e b7 82 c6 05 96 13 ea 01 01 e8 7b 42 8e ff <0f> 0b c3 cc cc cc cc 48 c7 c7 50 8f b7 82 c6 05 7a 13 ea 01 01 e8 RSP: 0018:ffffc90006b43b60 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff888009bb3ef0 RCX: 0000000000000027 RDX: ffff88807be218c8 RSI: 0000000000000001 RDI: ffff88807be218c0 RBP: 0000000000069d70 R08: 0000000000000000 R09: ffffc90006b439f0 R10: ffffc90006b439e8 R11: 0000000000000003 R12: ffff8880029ede84 R13: 0000000000004e20 R14: ffffffff84356dc0 R15: ffff888009bb3ef0 FS: 00007f62c10926c0(0000) GS:ffff88807be00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020ccb000 CR3: 000000004628c005 CR4: 0000000000f70ef0 PKRU: 55555554 Call Trace: <TASK> ? refcount_warn_saturate+0xe5/0x110 ? __warn+0x81/0x130 ? refcount_warn_saturate+0xe5/0x110 ? report_bug+0x171/0x1a0 ? refcount_warn_saturate+0xe5/0x110 ? handle_bug+0x3c/0x80 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? refcount_warn_saturate+0xe5/0x110 tcp_twsk_unique+0x186/0x190 __inet_check_established+0x176/0x2d0 __inet_hash_connect+0x74/0x7d0 ? __pfx___inet_check_established+0x10/0x10 tcp_v4_connect+0x278/0x530 __inet_stream_connect+0x10f/0x3d0 inet_stream_connect+0x3a/0x60 __sys_connect+0xa8/0xd0 __x64_sys_connect+0x18/0x20 do_syscall_64+0x83/0x170 entry_SYSCALL_64_after_hwframe+0x78/0x80 RIP: 0033:0x7f62c11a885d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a3 45 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007f62c1091e58 EFLAGS: 00000296 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 0000000020ccb004 RCX: 00007f62c11a885d RDX: 0000000000000010 RSI: 0000000020ccb000 RDI: 0000000000000003 RBP: 00007f62c1091e90 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000296 R12: 00007f62c10926c0 R13: ffffffffffffff88 R14: 0000000000000000 R15: 00007ffe237885b0 </TASK>
AI-Powered Analysis
Technical Analysis
CVE-2024-36904 is a use-after-free vulnerability identified in the Linux kernel's TCP stack, specifically within the tcp_twsk_unique() function. The vulnerability arises due to a race condition introduced after commit ec94c2696f0b, which modified the handling of TIME-WAIT sockets in the inet_twsk_hashdance() function. This commit sets the socket's reference count (sk_refcnt) after placing the TIME-WAIT socket into the ehash and releasing the bucket lock, creating a small window where concurrent threads can attempt to reuse the port during a connect() call. During this window, if another thread calls sock_hold() on the TIME-WAIT socket with a zero reference count, the reference count increment is incorrectly handled. The tcp_twsk_unique() function uses a standard increment rather than a safe conditional increment, leading to an underflow in the reference count when sock_put() is later called. This underflow triggers a use-after-free condition, where the kernel may access freed memory, potentially causing system instability or crashes. The patch involves replacing the reference count increment with refcount_inc_not_zero(), which only increments if the count is non-zero, thereby preventing reuse of the port in this race window and eliminating the use-after-free scenario. The vulnerability was reported by Anderson Nascimento and affects Linux kernel versions including and around commit ec94c2696f0b. There are no known exploits in the wild at the time of publication, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running vulnerable Linux kernel versions, which are widely used in servers, cloud infrastructure, and embedded devices across Europe. Exploitation could lead to kernel crashes or denial of service (DoS) conditions, impacting availability of critical services. In environments with high concurrency and network connection rates, the race condition could be triggered more frequently, increasing the risk of instability. Although no direct remote code execution or privilege escalation is indicated, the use-after-free could potentially be leveraged in complex attack chains to escalate privileges or bypass security mechanisms if combined with other vulnerabilities. Given the prevalence of Linux in European data centers, telecommunications, and government infrastructure, the vulnerability could disrupt operations if exploited or triggered unintentionally. The lack of known exploits reduces immediate risk, but the vulnerability's nature warrants prompt patching to maintain system reliability and security.
Mitigation Recommendations
European organizations should prioritize updating Linux kernels to versions that include the fix for CVE-2024-36904, specifically those incorporating the patch that replaces the reference count increment with refcount_inc_not_zero() in tcp_twsk_unique(). Kernel updates should be tested and deployed promptly in production environments, especially on systems handling high volumes of TCP connections. For environments where immediate patching is not feasible, organizations should monitor kernel logs for refcount warnings or crashes indicative of this issue. Network administrators can also consider limiting unnecessary TCP connection churn or implementing connection rate limiting to reduce the likelihood of triggering the race condition. Additionally, organizations should maintain robust kernel crash recovery and monitoring mechanisms to quickly detect and respond to instability potentially caused by this vulnerability. Coordination with Linux distribution vendors for timely patch releases and advisories is recommended to ensure comprehensive coverage.
Affected Countries
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
- 2024-05-30T15:25:07.067Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9828c4522896dcbe2614
Added to database: 5/21/2025, 9:08:56 AM
Last enriched: 6/29/2025, 9:57:23 AM
Last updated: 7/30/2025, 5:59:52 PM
Views: 16
Related Threats
CVE-2025-55286: CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer in vancluever z2d
HighCVE-2025-52621: CWE-346 Origin Validation Error in HCL Software BigFix SaaS Remediate
MediumCVE-2025-52620: CWE-20 Improper Input Validation in HCL Software BigFix SaaS Remediate
MediumCVE-2025-52619: CWE-209 Generation of Error Message Containing Sensitive Information in HCL Software BigFix SaaS Remediate
MediumCVE-2025-52618: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in HCL Software BigFix SaaS Remediate
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.