CVE-2024-35969: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: ipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr Although ipv6_get_ifaddr walks inet6_addr_lst under the RCU lock, it still means hlist_for_each_entry_rcu can return an item that got removed from the list. The memory itself of such item is not freed thanks to RCU but nothing guarantees the actual content of the memory is sane. In particular, the reference count can be zero. This can happen if ipv6_del_addr is called in parallel. ipv6_del_addr removes the entry from inet6_addr_lst (hlist_del_init_rcu(&ifp->addr_lst)) and drops all references (__in6_ifa_put(ifp) + in6_ifa_put(ifp)). With bad enough timing, this can happen: 1. In ipv6_get_ifaddr, hlist_for_each_entry_rcu returns an entry. 2. Then, the whole ipv6_del_addr is executed for the given entry. The reference count drops to zero and kfree_rcu is scheduled. 3. ipv6_get_ifaddr continues and tries to increments the reference count (in6_ifa_hold). 4. The rcu is unlocked and the entry is freed. 5. The freed entry is returned. Prevent increasing of the reference count in such case. The name in6_ifa_hold_safe is chosen to mimic the existing fib6_info_hold_safe. [ 41.506330] refcount_t: addition on 0; use-after-free. [ 41.506760] WARNING: CPU: 0 PID: 595 at lib/refcount.c:25 refcount_warn_saturate+0xa5/0x130 [ 41.507413] Modules linked in: veth bridge stp llc [ 41.507821] CPU: 0 PID: 595 Comm: python3 Not tainted 6.9.0-rc2.main-00208-g49563be82afa #14 [ 41.508479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) [ 41.509163] RIP: 0010:refcount_warn_saturate+0xa5/0x130 [ 41.509586] Code: ad ff 90 0f 0b 90 90 c3 cc cc cc cc 80 3d c0 30 ad 01 00 75 a0 c6 05 b7 30 ad 01 01 90 48 c7 c7 38 cc 7a 8c e8 cc 18 ad ff 90 <0f> 0b 90 90 c3 cc cc cc cc 80 3d 98 30 ad 01 00 0f 85 75 ff ff ff [ 41.510956] RSP: 0018:ffffbda3c026baf0 EFLAGS: 00010282 [ 41.511368] RAX: 0000000000000000 RBX: ffff9e9c46914800 RCX: 0000000000000000 [ 41.511910] RDX: ffff9e9c7ec29c00 RSI: ffff9e9c7ec1c900 RDI: ffff9e9c7ec1c900 [ 41.512445] RBP: ffff9e9c43660c9c R08: 0000000000009ffb R09: 00000000ffffdfff [ 41.512998] R10: 00000000ffffdfff R11: ffffffff8ca58a40 R12: ffff9e9c4339a000 [ 41.513534] R13: 0000000000000001 R14: ffff9e9c438a0000 R15: ffffbda3c026bb48 [ 41.514086] FS: 00007fbc4cda1740(0000) GS:ffff9e9c7ec00000(0000) knlGS:0000000000000000 [ 41.514726] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 41.515176] CR2: 000056233b337d88 CR3: 000000000376e006 CR4: 0000000000370ef0 [ 41.515713] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 41.516252] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 41.516799] Call Trace: [ 41.517037] <TASK> [ 41.517249] ? __warn+0x7b/0x120 [ 41.517535] ? refcount_warn_saturate+0xa5/0x130 [ 41.517923] ? report_bug+0x164/0x190 [ 41.518240] ? handle_bug+0x3d/0x70 [ 41.518541] ? exc_invalid_op+0x17/0x70 [ 41.520972] ? asm_exc_invalid_op+0x1a/0x20 [ 41.521325] ? refcount_warn_saturate+0xa5/0x130 [ 41.521708] ipv6_get_ifaddr+0xda/0xe0 [ 41.522035] inet6_rtm_getaddr+0x342/0x3f0 [ 41.522376] ? __pfx_inet6_rtm_getaddr+0x10/0x10 [ 41.522758] rtnetlink_rcv_msg+0x334/0x3d0 [ 41.523102] ? netlink_unicast+0x30f/0x390 [ 41.523445] ? __pfx_rtnetlink_rcv_msg+0x10/0x10 [ 41.523832] netlink_rcv_skb+0x53/0x100 [ 41.524157] netlink_unicast+0x23b/0x390 [ 41.524484] netlink_sendmsg+0x1f2/0x440 [ 41.524826] __sys_sendto+0x1d8/0x1f0 [ 41.525145] __x64_sys_sendto+0x1f/0x30 [ 41.525467] do_syscall_64+0xa5/0x1b0 [ 41.525794] entry_SYSCALL_64_after_hwframe+0x72/0x7a [ 41.526213] RIP: 0033:0x7fbc4cfcea9a [ 41.526528] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89 [ 41.527942] RSP: 002b:00007f ---truncated---
AI Analysis
Technical Summary
CVE-2024-35969 is a medium-severity vulnerability in the Linux kernel's IPv6 implementation, specifically involving a race condition between the functions ipv6_get_ifaddr and ipv6_del_addr. The vulnerability arises because ipv6_get_ifaddr iterates over the inet6_addr_lst list under an RCU (Read-Copy-Update) lock, but the iteration can still return a list entry that has been concurrently removed by ipv6_del_addr. Although the memory of the removed entry is not immediately freed due to RCU mechanisms, the content of that memory may become inconsistent or invalid. The critical issue is that the reference count of the entry can drop to zero if ipv6_del_addr executes concurrently, leading to the scheduling of kfree_rcu to free the memory. If ipv6_get_ifaddr then attempts to increment the reference count after it has dropped to zero but before the memory is freed, it results in a use-after-free condition. This can cause kernel warnings, potential crashes, or undefined behavior. The patch introduces a safer reference count increment function, in6_ifa_hold_safe, to prevent incrementing the reference count on entries that are being freed. The vulnerability is identified as CWE-770 (Use of a Resource after Expiration or Release). The CVSS 3.1 score is 5.5 (medium severity), with the vector indicating local attack vector, low complexity, low privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, but high impact on availability. No known exploits are reported in the wild as of the publication date. This vulnerability affects Linux kernel versions prior to the patch and is relevant to systems using IPv6 networking stacks.
Potential Impact
For European organizations, the impact of CVE-2024-35969 primarily concerns the availability and stability of Linux-based systems that utilize IPv6 networking. Many European enterprises, government agencies, and service providers rely heavily on Linux servers and infrastructure, often with IPv6 enabled or in dual-stack configurations. Exploitation of this race condition could lead to kernel crashes or denial of service (DoS) conditions, disrupting critical services such as web hosting, cloud services, telecommunications, and internal network operations. While the vulnerability does not directly compromise confidentiality or integrity, the resulting instability could cause operational outages, impacting business continuity and service level agreements. Systems running containerized workloads or virtualized environments on Linux hosts may also be affected, as the kernel is shared. Given the widespread adoption of Linux in European data centers and the increasing deployment of IPv6, the vulnerability poses a tangible risk to network infrastructure reliability. However, exploitation requires local access with at least low privileges, limiting remote attack vectors. Nonetheless, insider threats or compromised accounts could leverage this flaw to cause service disruptions.
Mitigation Recommendations
European organizations should prioritize patching Linux kernel versions to the fixed releases that address CVE-2024-35969. Since the vulnerability involves kernel-level race conditions, updating to the latest stable kernel versions provided by trusted Linux distributions is the most effective mitigation. Organizations should: 1) Identify all Linux systems running affected kernel versions, especially those with IPv6 enabled. 2) Schedule and apply kernel updates as soon as vendor patches become available, ensuring minimal downtime through maintenance windows. 3) For environments where immediate patching is not feasible, consider temporarily disabling IPv6 if it is not required, to reduce exposure. 4) Monitor system logs for kernel warnings related to refcount or use-after-free errors that may indicate exploitation attempts or instability. 5) Implement strict access controls and monitoring to limit local user privileges and detect suspicious activities that could trigger the vulnerability. 6) Employ kernel live patching solutions where supported to reduce the need for reboots while applying fixes. 7) Coordinate with Linux distribution vendors for timely security advisories and patches. These steps go beyond generic advice by focusing on IPv6 usage assessment, kernel update prioritization, and operational monitoring specific to this vulnerability's characteristics.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Denmark, Ireland, Belgium, Italy
CVE-2024-35969: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: ipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr Although ipv6_get_ifaddr walks inet6_addr_lst under the RCU lock, it still means hlist_for_each_entry_rcu can return an item that got removed from the list. The memory itself of such item is not freed thanks to RCU but nothing guarantees the actual content of the memory is sane. In particular, the reference count can be zero. This can happen if ipv6_del_addr is called in parallel. ipv6_del_addr removes the entry from inet6_addr_lst (hlist_del_init_rcu(&ifp->addr_lst)) and drops all references (__in6_ifa_put(ifp) + in6_ifa_put(ifp)). With bad enough timing, this can happen: 1. In ipv6_get_ifaddr, hlist_for_each_entry_rcu returns an entry. 2. Then, the whole ipv6_del_addr is executed for the given entry. The reference count drops to zero and kfree_rcu is scheduled. 3. ipv6_get_ifaddr continues and tries to increments the reference count (in6_ifa_hold). 4. The rcu is unlocked and the entry is freed. 5. The freed entry is returned. Prevent increasing of the reference count in such case. The name in6_ifa_hold_safe is chosen to mimic the existing fib6_info_hold_safe. [ 41.506330] refcount_t: addition on 0; use-after-free. [ 41.506760] WARNING: CPU: 0 PID: 595 at lib/refcount.c:25 refcount_warn_saturate+0xa5/0x130 [ 41.507413] Modules linked in: veth bridge stp llc [ 41.507821] CPU: 0 PID: 595 Comm: python3 Not tainted 6.9.0-rc2.main-00208-g49563be82afa #14 [ 41.508479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) [ 41.509163] RIP: 0010:refcount_warn_saturate+0xa5/0x130 [ 41.509586] Code: ad ff 90 0f 0b 90 90 c3 cc cc cc cc 80 3d c0 30 ad 01 00 75 a0 c6 05 b7 30 ad 01 01 90 48 c7 c7 38 cc 7a 8c e8 cc 18 ad ff 90 <0f> 0b 90 90 c3 cc cc cc cc 80 3d 98 30 ad 01 00 0f 85 75 ff ff ff [ 41.510956] RSP: 0018:ffffbda3c026baf0 EFLAGS: 00010282 [ 41.511368] RAX: 0000000000000000 RBX: ffff9e9c46914800 RCX: 0000000000000000 [ 41.511910] RDX: ffff9e9c7ec29c00 RSI: ffff9e9c7ec1c900 RDI: ffff9e9c7ec1c900 [ 41.512445] RBP: ffff9e9c43660c9c R08: 0000000000009ffb R09: 00000000ffffdfff [ 41.512998] R10: 00000000ffffdfff R11: ffffffff8ca58a40 R12: ffff9e9c4339a000 [ 41.513534] R13: 0000000000000001 R14: ffff9e9c438a0000 R15: ffffbda3c026bb48 [ 41.514086] FS: 00007fbc4cda1740(0000) GS:ffff9e9c7ec00000(0000) knlGS:0000000000000000 [ 41.514726] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 41.515176] CR2: 000056233b337d88 CR3: 000000000376e006 CR4: 0000000000370ef0 [ 41.515713] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 41.516252] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 41.516799] Call Trace: [ 41.517037] <TASK> [ 41.517249] ? __warn+0x7b/0x120 [ 41.517535] ? refcount_warn_saturate+0xa5/0x130 [ 41.517923] ? report_bug+0x164/0x190 [ 41.518240] ? handle_bug+0x3d/0x70 [ 41.518541] ? exc_invalid_op+0x17/0x70 [ 41.520972] ? asm_exc_invalid_op+0x1a/0x20 [ 41.521325] ? refcount_warn_saturate+0xa5/0x130 [ 41.521708] ipv6_get_ifaddr+0xda/0xe0 [ 41.522035] inet6_rtm_getaddr+0x342/0x3f0 [ 41.522376] ? __pfx_inet6_rtm_getaddr+0x10/0x10 [ 41.522758] rtnetlink_rcv_msg+0x334/0x3d0 [ 41.523102] ? netlink_unicast+0x30f/0x390 [ 41.523445] ? __pfx_rtnetlink_rcv_msg+0x10/0x10 [ 41.523832] netlink_rcv_skb+0x53/0x100 [ 41.524157] netlink_unicast+0x23b/0x390 [ 41.524484] netlink_sendmsg+0x1f2/0x440 [ 41.524826] __sys_sendto+0x1d8/0x1f0 [ 41.525145] __x64_sys_sendto+0x1f/0x30 [ 41.525467] do_syscall_64+0xa5/0x1b0 [ 41.525794] entry_SYSCALL_64_after_hwframe+0x72/0x7a [ 41.526213] RIP: 0033:0x7fbc4cfcea9a [ 41.526528] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89 [ 41.527942] RSP: 002b:00007f ---truncated---
AI-Powered Analysis
Technical Analysis
CVE-2024-35969 is a medium-severity vulnerability in the Linux kernel's IPv6 implementation, specifically involving a race condition between the functions ipv6_get_ifaddr and ipv6_del_addr. The vulnerability arises because ipv6_get_ifaddr iterates over the inet6_addr_lst list under an RCU (Read-Copy-Update) lock, but the iteration can still return a list entry that has been concurrently removed by ipv6_del_addr. Although the memory of the removed entry is not immediately freed due to RCU mechanisms, the content of that memory may become inconsistent or invalid. The critical issue is that the reference count of the entry can drop to zero if ipv6_del_addr executes concurrently, leading to the scheduling of kfree_rcu to free the memory. If ipv6_get_ifaddr then attempts to increment the reference count after it has dropped to zero but before the memory is freed, it results in a use-after-free condition. This can cause kernel warnings, potential crashes, or undefined behavior. The patch introduces a safer reference count increment function, in6_ifa_hold_safe, to prevent incrementing the reference count on entries that are being freed. The vulnerability is identified as CWE-770 (Use of a Resource after Expiration or Release). The CVSS 3.1 score is 5.5 (medium severity), with the vector indicating local attack vector, low complexity, low privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, but high impact on availability. No known exploits are reported in the wild as of the publication date. This vulnerability affects Linux kernel versions prior to the patch and is relevant to systems using IPv6 networking stacks.
Potential Impact
For European organizations, the impact of CVE-2024-35969 primarily concerns the availability and stability of Linux-based systems that utilize IPv6 networking. Many European enterprises, government agencies, and service providers rely heavily on Linux servers and infrastructure, often with IPv6 enabled or in dual-stack configurations. Exploitation of this race condition could lead to kernel crashes or denial of service (DoS) conditions, disrupting critical services such as web hosting, cloud services, telecommunications, and internal network operations. While the vulnerability does not directly compromise confidentiality or integrity, the resulting instability could cause operational outages, impacting business continuity and service level agreements. Systems running containerized workloads or virtualized environments on Linux hosts may also be affected, as the kernel is shared. Given the widespread adoption of Linux in European data centers and the increasing deployment of IPv6, the vulnerability poses a tangible risk to network infrastructure reliability. However, exploitation requires local access with at least low privileges, limiting remote attack vectors. Nonetheless, insider threats or compromised accounts could leverage this flaw to cause service disruptions.
Mitigation Recommendations
European organizations should prioritize patching Linux kernel versions to the fixed releases that address CVE-2024-35969. Since the vulnerability involves kernel-level race conditions, updating to the latest stable kernel versions provided by trusted Linux distributions is the most effective mitigation. Organizations should: 1) Identify all Linux systems running affected kernel versions, especially those with IPv6 enabled. 2) Schedule and apply kernel updates as soon as vendor patches become available, ensuring minimal downtime through maintenance windows. 3) For environments where immediate patching is not feasible, consider temporarily disabling IPv6 if it is not required, to reduce exposure. 4) Monitor system logs for kernel warnings related to refcount or use-after-free errors that may indicate exploitation attempts or instability. 5) Implement strict access controls and monitoring to limit local user privileges and detect suspicious activities that could trigger the vulnerability. 6) Employ kernel live patching solutions where supported to reduce the need for reboots while applying fixes. 7) Coordinate with Linux distribution vendors for timely security advisories and patches. These steps go beyond generic advice by focusing on IPv6 usage assessment, kernel update prioritization, and operational monitoring specific to this vulnerability's characteristics.
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-17T13:50:33.140Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9828c4522896dcbe2311
Added to database: 5/21/2025, 9:08:56 AM
Last enriched: 6/29/2025, 8:41:13 AM
Last updated: 8/15/2025, 6:50:02 AM
Views: 13
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.