CVE-2023-52923 | netfilter: nf_tables: adapt set backend to use GC transaction API

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: adapt set backend to use GC transaction API Use the GC transaction API to replace the old and buggy gc API and the busy mark approach. No set elements are removed from async garbage collection anymore, instead the _DEAD bit is set on so the set element is not visible from lookup path anymore. Async GC enqueues transaction work that might be aborted and retried later. rbtree and pipapo set backends does not set on the _DEAD bit from the sync GC path since this runs in control plane path where mutex is held. In this case, set elements are deactivated, removed and then released via RCU callback, sync GC never fails.

Published: 2025-01-20 Last update: 2026-06-17 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-52923 is rated Low Risk (27.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.23%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-52923

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.23% +0.22%
2 2026-02-28 0.05% 0.01% -0.04%
3 2025-03-30 — 0.05% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-52923

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2023-52923

OS Trackers for CVE-2023-52923

vendor priority summary link
debian not yet assigned CVE-2023-52923 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-52923
redhat medium — https://access.redhat.com/security/cve/CVE-2023-52923
suse medium — https://www.suse.com/security/cve/CVE-2023-52923/
ubuntu medium CVE-2023-52923 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 149, released 142, not-affected 95, needed 19, needs-triage 1. https://ubuntu.com/security/CVE-2023-52923

Affected software / configurations for CVE-2023-52923

Vendor Product Version Raw CPE
linux linux_kernel >= 4.1, < 4.19.316 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 4.20, < 5.4.262 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.5, < 5.10.198 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.134 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 6.1.56 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.4.11 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc1:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc2:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc3:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc4:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc5:*:*:*:*:*:*

References for CVE-2023-52923

cvelogic Threat Intelligence