CVE-2023-53622
What it is
In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix possible data races in gfs2_show_options() Some fields such as gt_logd_secs of the struct gfs2_tune are accessed without holding the lock gt_spin in gfs2_show_options(): val = sdp->sd_tune.gt_logd_secs; if (val != 30) seq_printf(s, ",commit=%d", val); And thus can cause data races when gfs2_show_options() and other functions such as gfs2_reconfigure() are concurrently executed: spin_lock(>->gt_spin); gt->gt_logd_secs = newargs->ar_commit; To fix these possible data races, the lock sdp->sd_tune.gt_spin is acquired before accessing the fields of gfs2_tune and released after these accesses. Further changes by Andreas: - Don't hold the spin lock over the seq_printf operations.
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.1% 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.1% in the next 30 days (EPSS).
- Severity: 7.0 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Analyzed
Affected
- Linux Kernel < 4.14.324
- Linux Kernel < 4.19.293
- Linux Kernel < 5.4.255
- Linux Kernel < 5.10.192
- Linux Kernel < 5.15.128
- Linux Kernel < 6.1.47
- Linux Kernel < 6.4.12
Attack profile CVSS 3.1 · 7.0
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:H/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-53622.md and follow it. Check whether this project is affected by CVE-2023-53622. 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/235a5ae73cea29109a3e06f100493f17857e6a93
- https://git.kernel.org/stable/c/42077d4de49e4d9c773c97c42d5383b4899a8f9d
- https://git.kernel.org/stable/c/6fa0a72cbbe45db4ed967a51f9e6f4e3afe61d20
- https://git.kernel.org/stable/c/7c5b2649f6a37d45bfb7abf34c9b71d08677139f
- https://git.kernel.org/stable/c/7e5bbeb7eb813bb2568e1d5d02587df943272e57
- https://git.kernel.org/stable/c/85e888150075cb221270b64bf772341fc6bd11d9
- https://git.kernel.org/stable/c/a4f71523ed2123d63b431cc0cea4e9f363a0f054
- https://git.kernel.org/stable/c/b4a7ab57effbed42624842f2ab2a49b177c21a47
References
- https://git.kernel.org/stable/c/235a5ae73cea29109a3e06f100493f17857e6a93
- https://git.kernel.org/stable/c/42077d4de49e4d9c773c97c42d5383b4899a8f9d
- https://git.kernel.org/stable/c/6fa0a72cbbe45db4ed967a51f9e6f4e3afe61d20
- https://git.kernel.org/stable/c/7c5b2649f6a37d45bfb7abf34c9b71d08677139f
- https://git.kernel.org/stable/c/7e5bbeb7eb813bb2568e1d5d02587df943272e57
- https://git.kernel.org/stable/c/85e888150075cb221270b64bf772341fc6bd11d9
- https://git.kernel.org/stable/c/a4f71523ed2123d63b431cc0cea4e9f363a0f054
- https://git.kernel.org/stable/c/b4a7ab57effbed42624842f2ab2a49b177c21a47