Linux Kernel up to 6.4.10 netfilter nf_tables_set_elem_destroy privilege escalation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Linux Kernel up to 6.4.10. This affects the function nf_tables_set_elem_destroy of the component netfilter. The manipulation results in an unknown weakness.
This vulnerability is cataloged as CVE-2023-52924. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in Linux Kernel up to 6.4.10. Affected is the function nf_tables_set_elem_destroy of the component netfilter. The impact remains unknown. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: don't skip expired elements during walk There is an asymmetry between commit/abort and preparation phase if the following conditions are met: 1. set is a verdict map ("1.2.3.4 : jump foo") 2. timeouts are enabled In this case, following sequence is problematic: 1. element E in set S refers to chain C 2. userspace requests removal of set S 3. kernel does a set walk to decrement chain->use count for all elements from preparation phase 4. kernel does another set walk to remove elements from the commit phase (or another walk to do a chain->use increment for all elements from abort phase) If E has already expired in 1), it will be ignored during list walk, so its use count won't have been changed. Then, when set is culled, ->destroy callback will zap the element via nf_tables_set_elem_destroy(), but this function is only safe for elements that have been deactivated earlier from the preparation phase: lack of earlier deactivate removes the element but leaks the chain use count, which results in a WARN splat when the chain gets removed later, plus a leak of the nft_chain structure. Update pipapo_get() not to skip expired elements, otherwise flush command reports bogus ENOENT errors.
The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2023-52924 since 08/21/2024. Technical details are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 232643 (SUSE SLES12 Security Update : kernel (SUSE-SU-2025:0834-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.19.316, 5.4.262, 5.10.198, 5.15.134, 6.1.56 or 6.4.11 eliminates this vulnerability. Applying the patch 94313a196b44184b5b52c1876da6a537701b425a/1da4874d05da1526b11b82fc7f3c7ac38749ddf8/b15ea4017af82011dd55225ce77cce3d4dfc169c/7c7e658a36f8b1522bd3586d8137e5f93a25ddc5/59dab3bf0b8fc08eb802721c0532f13dd89209b8/bd156ce9553dcaf2d6ee2c825d1a5a1718e86524/24138933b97b055d486e8064b4a1721702442a9b is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (232643) and CERT Bund (WID-SEC-2025-1439). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- SUSE Linux
- Dell Secure Connect Gateway
Product
Type
Vendor
Name
Version
- 4.19.315
- 5.4.261
- 5.10.197
- 5.15.133
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.1.28
- 6.1.29
- 6.1.30
- 6.1.31
- 6.1.32
- 6.1.33
- 6.1.34
- 6.1.35
- 6.1.36
- 6.1.37
- 6.1.38
- 6.1.39
- 6.1.40
- 6.1.41
- 6.1.42
- 6.1.43
- 6.1.44
- 6.1.45
- 6.1.46
- 6.1.47
- 6.1.48
- 6.1.49
- 6.1.50
- 6.1.51
- 6.1.52
- 6.1.53
- 6.1.54
- 6.1.55
- 6.4.0
- 6.4.1
- 6.4.2
- 6.4.3
- 6.4.4
- 6.4.5
- 6.4.6
- 6.4.7
- 6.4.8
- 6.4.9
- 6.4.10
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 232643
Nessus Name: SUSE SLES12 Security Update : kernel (SUSE-SU-2025:0834-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 4.19.316/5.4.262/5.10.198/5.15.134/6.1.56/6.4.11
Patch: 94313a196b44184b5b52c1876da6a537701b425a/1da4874d05da1526b11b82fc7f3c7ac38749ddf8/b15ea4017af82011dd55225ce77cce3d4dfc169c/7c7e658a36f8b1522bd3586d8137e5f93a25ddc5/59dab3bf0b8fc08eb802721c0532f13dd89209b8/bd156ce9553dcaf2d6ee2c825d1a5a1718e86524/24138933b97b055d486e8064b4a1721702442a9b
Timeline
08/21/2024 🔍02/05/2025 🔍
02/05/2025 🔍
01/21/2026 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-52924 (🔍)
GCVE (CVE): GCVE-0-2023-52924
GCVE (VulDB): GCVE-100-294714
CERT Bund: WID-SEC-2025-1439 - Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff
Entry
Created: 02/05/2025 10:55Updated: 01/21/2026 00:31
Changes: 02/05/2025 10:55 (57), 03/12/2025 18:46 (2), 10/16/2025 01:46 (11), 01/21/2026 00:31 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.