CVE-2023-52925

netfilter: nf_tables: don't fail inserts if duplicate has expired

MEDIUM
5.5
CVSS Score
Published: February 5, 2025 at 09:07 AM UTC
Updated: June 17, 2026 at 06:43 AM UTC
1 product affected across 1 vendorLinux Kernel

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
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: don't fail inserts if duplicate has expired nftables selftests fail: run-tests.sh testcases/sets/0044interval_overlap_0 Expected: 0-2 . 0-3, got: W: [FAILED] ./testcases/sets/0044interval_overlap_0: got 1 Insertion must ignore duplicate but expired entries. Moreover, there is a strange asymmetry in nft_pipapo_activate: It refetches the current element, whereas the other ->activate callbacks (bitmap, hash, rhash, rbtree) use elem->priv. Same for .remove: other set implementations take elem->priv, nft_pipapo_remove fetches elem->priv, then does a relookup, remove this. I suspect this was the reason for the change that prompted the removal of the expired check in pipapo_get() in the first place, but skipping exired elements there makes no sense to me, this helper is used for normal get requests, insertions (duplicate check) and deactivate callback. In first two cases expired elements must be skipped. For ->deactivate(), this gets called for DELSETELEM, so it seems to me that expired elements should be skipped as well, i.e. delete request should fail with -ENOENT error.

Affected

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

v ≥ 4.19.316v ≥ 5.4.2624.19.316 ≤ v < 4.205.4.262 ≤ v < 5.56.4.11 ≤ v < 6.4.121da4874d05da1526b11b82fc7f3c7ac38749ddf824138933b97b055d486e8064b4a1721702442a9b4.19.3165.4.26259dab3bf0b8fc08eb802721c0532f13dd89209b86.4.116.5 rc67c7e658a36f8b1522bd3586d8137e5f93a25ddc594313a196b44184b5b52c1876da6a537701b425ab15ea4017af82011dd55225ce77cce3d4dfc169cbd156ce9553dcaf2d6ee2c825d1a5a1718e86524
Vendor states this is fixed in 156369a702c33ad5434a19c3a689bfb836d4e0b8 (fixed)
Vendor states this is fixed in 59ee68c437c562170265194a99698c805a686bb3 (fixed)
Vendor states this is fixed in 7845914f45f066497ac75b30c50dbc735e84e884 (fixed)
Vendor states this is fixed in 891ca5dfe3b718b441fc786014a7ba8f517da188 (fixed)
Vendor states this is fixed in af78b0489e8898a8c9449ffc0fdd2e181916f0d4 (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.4.12, so it looks safe — our inference, not a vendor statement

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/156369a702c33ad5434a19c3a689bfb836d4e0b8
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/59ee68c437c562170265194a99698c805a686bb3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7845914f45f066497ac75b30c50dbc735e84e884
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/891ca5dfe3b718b441fc786014a7ba8f517da188
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/af78b0489e8898a8c9449ffc0fdd2e181916f0d4

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
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

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