Bug 1227756 (CVE-2024-39503) - VUL-0: CVE-2024-39503: kernel: netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type
Summary: VUL-0: CVE-2024-39503: kernel: netfilter: ipset: Fix race between namespace c...
Status: RESOLVED INVALID
Alias: CVE-2024-39503
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/413818/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-39503:6.4:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-15 08:09 UTC by SMASH SMASH
Modified: 2024-07-16 11:53 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-07-15 08:09:34 UTC
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).

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-39503
https://www.cve.org/CVERecord?id=CVE-2024-39503
https://git.kernel.org/stable/c/0f1bb77c6d837c9513943bc7c08f04c5cc5c6568
https://git.kernel.org/stable/c/2ba35b37f780c6410bb4bba9c3072596d8576702
https://git.kernel.org/stable/c/390b353d1a1da3e9c6c0fd14fe650d69063c95d6
https://git.kernel.org/stable/c/4e7aaa6b82d63e8ddcbfb56b4fd3d014ca586f10
https://git.kernel.org/stable/c/90ae20d47de602198eb69e6cd7a3db3420abfc08
https://git.kernel.org/stable/c/93b53c202b51a69e42ca57f5a183f7e008e19f83
https://git.kernel.org/stable/c/c0761d1f1ce1d5b85b5e82bbb714df12de1aa8c3
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-39503.mbox
Comment 2 Andrea Mattiazzo 2024-07-16 11:53:20 UTC
No codestream are affected, closing.