netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.35, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From c7f2733e5011bfd136f1ca93497394d43aa76225 · fixed in c0761d1f1ce1d5b85b5e82bbb714df12de1aa8c3; From a24d5f2ac8ef702a58e55ec276aad29b4bd97e05 · fixed in 93b53c202b51a69e42ca57f5a183f7e008e19f83; From c2dc077d8f722a1c73a24e674f925602ee5ece49 · fixed in 0f1bb77c6d837c9513943bc7c08f04c5cc5c6568; From 653bc5e6d9995d7d5f497c665b321875a626161c · fixed in 390b353d1a1da3e9c6c0fd14fe650d69063c95d6; From b93a6756a01f4fd2f329a39216f9824c56a66397 · fixed in 2ba35b37f780c6410bb4bba9c3072596d8576702; From 97f7cf1cd80eeed3b7c808b7c12463295c751001 · fixed in 90ae20d47de602198eb69e6cd7a3db3420abfc08; From 97f7cf1cd80eeed3b7c808b7c12463295c751001 · fixed in 4e7aaa6b82d63e8ddcbfb56b4fd3d014ca586f10; From 5.4.269 · fixed in 5.4.279; From 5.10.210 · fixed in 5.10.221; From 5.15.149 · fixed in 5.15.162; From 6.1.79 · fixed in 6.1.95; From 6.6.18 · fixed in 6.6.35; From 6.7.6 · fixed in 6.8
- Linux Linux
6.8
- KernelLinux
fixed in 5.4.279; From 5.5.0 · fixed in 5.10.221; From 5.11.0 · fixed in 5.15.162; From 5.16.0 · fixed in 6.1.95; From 6.2.0 · fixed in 6.6.35; From 6.7.0 · fixed in 6.9.6
References 7
git.kernel.org
- stable/c/c0761d1f1ce1d5b85b5e82bbb714df12de1aa8c3
- stable/c/93b53c202b51a69e42ca57f5a183f7e008e19f83
- stable/c/0f1bb77c6d837c9513943bc7c08f04c5cc5c6568
- stable/c/390b353d1a1da3e9c6c0fd14fe650d69063c95d6
- stable/c/2ba35b37f780c6410bb4bba9c3072596d8576702
- stable/c/90ae20d47de602198eb69e6cd7a3db3420abfc08
- stable/c/4e7aaa6b82d63e8ddcbfb56b4fd3d014ca586f10