Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-52923, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 9d0982927e79049675cb6c6c04a0ebb3dad5a434 – < cb4d00b563675ba8ff6ef94b077f58d816f68ba3
    • affected 9d0982927e79049675cb6c6c04a0ebb3dad5a434 – < c357648929c8dff891502349769aafb8f0452bc2
    • affected 9d0982927e79049675cb6c6c04a0ebb3dad5a434 – < 146c76866795553dbc19998f36718d7986ad302b
    • affected 9d0982927e79049675cb6c6c04a0ebb3dad5a434 – < 479a2cf5259347d6a1f658b0f791d27a34908e91
    • affected 9d0982927e79049675cb6c6c04a0ebb3dad5a434 – < df650d6a4bf47248261b61ef6b174d7c54034d15
    • affected 9d0982927e79049675cb6c6c04a0ebb3dad5a434 – < e4d71d6a9c7db93f7bf20c3a0f0659d63d7de681
    • affected 9d0982927e79049675cb6c6c04a0ebb3dad5a434 – < f6c383b8c31a93752a52697f8430a71dcbc46adf
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • unaffected 4.19.316 – ≤ 4.19.*
    • unaffected 5.4.262 – ≤ 5.4.*
    • unaffected 5.10.198 – ≤ 5.10.*
    • unaffected 5.15.134 – ≤ 5.15.*
    • unaffected 6.1.56 – ≤ 6.1.*
    • unaffected 6.4.11 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52923 badge
[![CVE-2023-52923](https://cveledger.app/badge/CVE-2023-52923.svg)](https://cveledger.app/cve/CVE-2023-52923)

Record last updated .