ghsa-f2qv-j847-m6vp
Vulnerability from github
Published
2025-01-20 12:30
Modified
2025-01-20 12:30
Details
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.
{ "affected": [], "aliases": [ "CVE-2023-52923" ], "database_specific": { "cwe_ids": [], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2025-01-20T11:15:07Z", "severity": null }, "details": "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.", "id": "GHSA-f2qv-j847-m6vp", "modified": "2025-01-20T12:30:51Z", "published": "2025-01-20T12:30:51Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52923" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/146c76866795553dbc19998f36718d7986ad302b" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/479a2cf5259347d6a1f658b0f791d27a34908e91" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/c357648929c8dff891502349769aafb8f0452bc2" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/cb4d00b563675ba8ff6ef94b077f58d816f68ba3" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/df650d6a4bf47248261b61ef6b174d7c54034d15" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/e4d71d6a9c7db93f7bf20c3a0f0659d63d7de681" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/f6c383b8c31a93752a52697f8430a71dcbc46adf" } ], "schema_version": "1.4.0", "severity": [] }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.