CVE-2023-52872
"Linux Kernel GSM TTY Race Condition"
Description
In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix race condition in status line change on dead connections gsm_cleanup_mux() cleans up the gsm by closing all DLCIs, stopping all timers, removing the virtual tty devices and clearing the data queues. This procedure, however, may cause subsequent changes of the virtual modem status lines of a DLCI. More data is being added the outgoing data queue and the deleted kick timer is restarted to handle this. At this point many resources have already been removed by the cleanup procedure. Thus, a kernel panic occurs. Fix this by proving in gsm_modem_update() that the cleanup procedure has not been started and the mux is still alive. Note that writing to a virtual tty is already protected by checks against the DLCI specific connection state.
INFO
Published Date :
May 21, 2024, 4:15 p.m.
Last Modified :
April 2, 2025, 3:15 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-52872.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-52872 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-52872 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Apr. 02, 2025
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.6 up to (excluding) 6.6.1 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.5.11 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.18.18 up to (excluding) 5.19 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.15.61 up to (excluding) 5.15.138 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.19.2 up to (excluding) 6.1.62 Added Reference Type CVE: https://git.kernel.org/stable/c/19d34b73234af542cc8a218cf398dee73cdb1890 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/19d34b73234af542cc8a218cf398dee73cdb1890 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/3a75b205de43365f80a33b98ec9289785da56243 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/3a75b205de43365f80a33b98ec9289785da56243 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/81a4dd5e6c78f5d8952fa8c9d36565db1fe01444 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/81a4dd5e6c78f5d8952fa8c9d36565db1fe01444 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/ce4df90333c4fe65acb8b5089fdfe9b955ce976a Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ce4df90333c4fe65acb8b5089fdfe9b955ce976a Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/df6cfab66ff2a44bd23ad5dd5309cb3421bb6593 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/df6cfab66ff2a44bd23ad5dd5309cb3421bb6593 Types: Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/19d34b73234af542cc8a218cf398dee73cdb1890 Added Reference https://git.kernel.org/stable/c/3a75b205de43365f80a33b98ec9289785da56243 Added Reference https://git.kernel.org/stable/c/81a4dd5e6c78f5d8952fa8c9d36565db1fe01444 Added Reference https://git.kernel.org/stable/c/ce4df90333c4fe65acb8b5089fdfe9b955ce976a Added Reference https://git.kernel.org/stable/c/df6cfab66ff2a44bd23ad5dd5309cb3421bb6593 -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Nov. 06, 2024
Action Type Old Value New Value Added CWE CISA-ADP CWE-362 Added CVSS V3.1 CISA-ADP AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 29, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix race condition in status line change on dead connections gsm_cleanup_mux() cleans up the gsm by closing all DLCIs, stopping all timers, removing the virtual tty devices and clearing the data queues. This procedure, however, may cause subsequent changes of the virtual modem status lines of a DLCI. More data is being added the outgoing data queue and the deleted kick timer is restarted to handle this. At this point many resources have already been removed by the cleanup procedure. Thus, a kernel panic occurs. Fix this by proving in gsm_modem_update() that the cleanup procedure has not been started and the mux is still alive. Note that writing to a virtual tty is already protected by checks against the DLCI specific connection state. Added Reference kernel.org https://git.kernel.org/stable/c/81a4dd5e6c78f5d8952fa8c9d36565db1fe01444 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/df6cfab66ff2a44bd23ad5dd5309cb3421bb6593 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/19d34b73234af542cc8a218cf398dee73cdb1890 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/ce4df90333c4fe65acb8b5089fdfe9b955ce976a [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/3a75b205de43365f80a33b98ec9289785da56243 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-52872 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-52872
weaknesses.