CVE-2023-52923
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 4.19.316
- Linux Kernel < 5.4.262
- Linux Kernel < 5.10.198
- Linux Kernel < 5.15.134
- Linux Kernel < 6.1.56
- Linux Kernel < 6.4.11
- Linux Kernel 6.5
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-52923.md and follow it. Check whether this project is affected by CVE-2023-52923. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/146c76866795553dbc19998f36718d7986ad302b
- https://git.kernel.org/stable/c/479a2cf5259347d6a1f658b0f791d27a34908e91
- https://git.kernel.org/stable/c/c357648929c8dff891502349769aafb8f0452bc2
- https://git.kernel.org/stable/c/cb4d00b563675ba8ff6ef94b077f58d816f68ba3
- https://git.kernel.org/stable/c/df650d6a4bf47248261b61ef6b174d7c54034d15
- https://git.kernel.org/stable/c/e4d71d6a9c7db93f7bf20c3a0f0659d63d7de681
- https://git.kernel.org/stable/c/f6c383b8c31a93752a52697f8430a71dcbc46adf
References
- https://git.kernel.org/stable/c/146c76866795553dbc19998f36718d7986ad302b
- https://git.kernel.org/stable/c/479a2cf5259347d6a1f658b0f791d27a34908e91
- https://git.kernel.org/stable/c/c357648929c8dff891502349769aafb8f0452bc2
- https://git.kernel.org/stable/c/cb4d00b563675ba8ff6ef94b077f58d816f68ba3
- https://git.kernel.org/stable/c/df650d6a4bf47248261b61ef6b174d7c54034d15
- https://git.kernel.org/stable/c/e4d71d6a9c7db93f7bf20c3a0f0659d63d7de681
- https://git.kernel.org/stable/c/f6c383b8c31a93752a52697f8430a71dcbc46adf