Vulnerability · Published Feb 5, 2025 · Assigned by Linux
CVE-2023-52924netfilter: nf_tables: don't skip expired elements during walk
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.64-1 | DEBIAN-CVE-2023-52924 |
| Debian:13 | linux | 6.4.11-1 | DEBIAN-CVE-2023-52924 |
| Debian:14 | linux | 6.4.11-1 | DEBIAN-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux | 5.15.0-87.97 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1048.53 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1050.57 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1050.57.1 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1045.53 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1045.50 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1031.37 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1041.44 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1043.49 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1045.50 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-87.96 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1039.39 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1019.19 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1006.6 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1046.52 | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1041.44 | UBUNTU-CVE-2023-52924 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-52924 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-52924 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9d0982927e79049675cb6c6c04a0ebb3dad5a434 – before 94313a196b44184b5b52c1876da6a537701b425a9d0982927e79049675cb6c6c04a0ebb3dad5a434 – before 1da4874d05da1526b11b82fc7f3c7ac38749ddf89d0982927e79049675cb6c6c04a0ebb3dad5a434 – before b15ea4017af82011dd55225ce77cce3d4dfc169c9d0982927e79049675cb6c6c04a0ebb3dad5a434 – before 7c7e658a36f8b1522bd3586d8137e5f93a25ddc59d0982927e79049675cb6c6c04a0ebb3dad5a434 – before 59dab3bf0b8fc08eb802721c0532f13dd89209b89d0982927e79049675cb6c6c04a0ebb3dad5a434 – before bd156ce9553dcaf2d6ee2c825d1a5a1718e865249d0982927e79049675cb6c6c04a0ebb3dad5a434 – before 24138933b97b055d486e8064b4a1721702442a9b |
| Linux | Linux | 4.1 |
References
- https://git.kernel.org/stable/c/94313a196b44184b5b52c1876da6a537701b425a
- https://git.kernel.org/stable/c/1da4874d05da1526b11b82fc7f3c7ac38749ddf8
- https://git.kernel.org/stable/c/b15ea4017af82011dd55225ce77cce3d4dfc169c
- https://git.kernel.org/stable/c/7c7e658a36f8b1522bd3586d8137e5f93a25ddc5
- https://git.kernel.org/stable/c/59dab3bf0b8fc08eb802721c0532f13dd89209b8
- https://git.kernel.org/stable/c/bd156ce9553dcaf2d6ee2c825d1a5a1718e86524
- https://git.kernel.org/stable/c/24138933b97b055d486e8064b4a1721702442a9b