Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-26910 | First vendor Publication | 2024-04-17 |
| Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
|---|---|---|---|
| Overall CVSS Score | 4.7 | ||
| Base Score | 4.7 | Environmental Score | 4.7 |
| impact SubScore | 3.6 | Temporal Score | 4.7 |
| Exploitabality Sub Score | 1 | ||
| Attack Vector | Local | Attack Complexity | High |
| Privileges Required | Low | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | None |
| Integrity Impact | None | Availability Impact | High |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: fix performance regression in swap operation The patch "netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test", commit 28628fa9 fixes a race condition. But the synchronize_rcu() added to the swap function unnecessarily slows it down: it can safely be moved to destroy and use call_rcu() instead. Eric Dumazet pointed out that simply calling the destroy functions as rcu callback does not work: sets with timeout use garbage collectors which need cancelling at destroy which can wait. Therefore the destroy functions are split into two: cancelling garbage collectors safely at executing the command received by netlink and moving the remaining part only into the rcu callback. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26910 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-362 | Race Condition |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 02:29:56 |
|
| 2025-06-25 12:30:06 |
|
| 2025-06-24 02:34:25 |
|
| 2025-05-27 02:36:36 |
|
| 2025-03-29 03:35:35 |
|
| 2025-03-28 13:41:38 |
|
| 2025-03-28 03:14:38 |
|
| 2025-03-19 03:10:11 |
|
| 2025-03-18 03:22:52 |
|
| 2025-03-14 03:10:27 |
|
| 2025-02-22 03:20:18 |
|
| 2025-01-08 03:02:10 |
|
| 2025-01-07 03:01:44 |
|
| 2024-12-25 03:00:29 |
|
| 2024-12-12 03:03:30 |
|
| 2024-11-25 09:26:03 |
|
| 2024-11-22 21:24:22 |
|
| 2024-11-21 21:24:09 |
|
| 2024-11-20 02:57:14 |
|
| 2024-11-13 21:22:03 |
|
| 2024-11-09 00:28:33 |
|
| 2024-11-05 13:27:58 |
|
| 2024-10-26 02:54:59 |
|
| 2024-10-25 02:56:54 |
|
| 2024-10-23 02:56:08 |
|
| 2024-10-03 02:51:30 |
|
| 2024-10-02 02:49:54 |
|
| 2024-09-15 02:47:48 |
|
| 2024-09-12 02:47:20 |
|
| 2024-09-04 02:48:52 |
|
| 2024-08-22 02:46:56 |
|
| 2024-08-02 13:56:01 |
|
| 2024-08-02 01:35:22 |
|
| 2024-06-26 05:27:34 |
|
| 2024-04-30 00:27:31 |
|
| 2024-04-17 21:27:23 |
|
