{"uuid": "cbda0d52-7100-4870-80f6-ffdf5e094846", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52923", "type": "seen", "source": "https://t.me/cvedetector/15884", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52923 - Linux Kernel Netfilter nf_tables Dead Element Unlinking Anywhere\", \n  \"Content\": \"CVE ID : CVE-2023-52923 \nPublished : Jan. 20, 2025, 11:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: nf_tables: adapt set backend to use GC transaction API  \n  \nUse the GC transaction API to replace the old and buggy gc API and the  \nbusy mark approach.  \n  \nNo set elements are removed from async garbage collection anymore,  \ninstead the _DEAD bit is set on so the set element is not visible from  \nlookup path anymore. Async GC enqueues transaction work that might be  \naborted and retried later.  \n  \nrbtree and pipapo set backends does not set on the _DEAD bit from the  \nsync GC path since this runs in control plane path where mutex is held.  \nIn this case, set elements are deactivated, removed and then released  \nvia RCU callback, sync GC never fails. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"20 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-20T13:22:16.000000Z"}