CVE-2024-39503

netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type

HIGH
7
CVSS Score
Published: July 12, 2024 at 12:20 PM UTC
Updated: October 15, 2026 at 01:18 AM UTC
7 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFPRUGGEDCOM RST2428P Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type Lion Ackermann reported that there is a race condition between namespace cleanup in ipset and the garbage collection of the list:set type. The namespace cleanup can destroy the list:set type of sets while the gc of the set type is waiting to run in rcu cleanup. The latter uses data from the destroyed set which thus leads use after free. The patch contains the following parts: - When destroying all sets, first remove the garbage collectors, then wait if needed and then destroy the sets. - Fix the badly ordered "wait then remove gc" for the destroy a single set case. - Fix the missing rcu locking in the list:set type in the userspace test case. - Use proper RCU list handlings in the list:set type. The patch depends on c1193d9bbbd3 (netfilter: ipset: Add list flush to cancel_gc).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.210 ≤ v < 5.10.2215.15.149 ≤ v < 5.15.1625.4.269 ≤ v < 5.4.2796.1.79 ≤ v < 6.1.956.6.18 ≤ v < 6.6.356.7.6 ≤ v < 6.86.8.1 ≤ v < 6.9.65.10.2105.15.1495.4.2696.1.796.106.10 rc16.10 rc26.10 rc36.6.186.7.66.86.8 rc36.8 rc46.8 rc56.8 rc66.8 rc7653bc5e6d9995d7d5f497c665b321875a626161c970709a67696b100a57b33af1a3d75fc34b747eb97f7cf1cd80eeed3b7c808b7c12463295c751001a24d5f2ac8ef702a58e55ec276aad29b4bd97e05b93a6756a01f4fd2f329a39216f9824c56a66397c2dc077d8f722a1c73a24e674f925602ee5ece49c7f2733e5011bfd136f1ca93497394d43aa76225
Vendor states this is fixed in 0f1bb77c6d837c9513943bc7c08f04c5cc5c6568 (fixed)
Vendor states this is fixed in 2ba35b37f780c6410bb4bba9c3072596d8576702 (fixed)
Vendor states this is fixed in 390b353d1a1da3e9c6c0fd14fe650d69063c95d6 (fixed)
Vendor states this is fixed in 4e7aaa6b82d63e8ddcbfb56b4fd3d014ca586f10 (fixed)
Vendor states this is fixed in 90ae20d47de602198eb69e6cd7a3db3420abfc08 (fixed)
Vendor states this is fixed in 93b53c202b51a69e42ca57f5a183f7e008e19f83 (fixed)
Vendor states this is fixed in c0761d1f1ce1d5b85b5e82bbb714df12de1aa8c3 (fixed)
Vendor states this is fixed in 5.10.221 (unaffected)
Vendor states this is fixed in 5.15.162 (unaffected)
Vendor states this is fixed in 5.4.279 (unaffected)
Vendor states this is fixed in 6.1.95 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.6.35 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)
Vendor states this is fixed in 6.9.6 (unaffected)
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement

References (11)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0f1bb77c6d837c9513943bc7c08f04c5cc5c6568
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2ba35b37f780c6410bb4bba9c3072596d8576702
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/390b353d1a1da3e9c6c0fd14fe650d69063c95d6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4e7aaa6b82d63e8ddcbfb56b4fd3d014ca586f10
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/90ae20d47de602198eb69e6cd7a3db3420abfc08
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/93b53c202b51a69e42ca57f5a183f7e008e19f83
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c0761d1f1ce1d5b85b5e82bbb714df12de1aa8c3
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-362CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card