Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-52872

tty: n_gsm: fix race condition in status line change on dead connections

High7.8EPSS 0.18%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2023-52872, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected dd37f657387853623f20c1b2482afbb9cd8ece33 – < 81a4dd5e6c78f5d8952fa8c9d36565db1fe01444
    • affected c568f7086c6e771c77aad13d727c70ef70e07243 – < df6cfab66ff2a44bd23ad5dd5309cb3421bb6593
    • affected c568f7086c6e771c77aad13d727c70ef70e07243 – < 19d34b73234af542cc8a218cf398dee73cdb1890
    • affected c568f7086c6e771c77aad13d727c70ef70e07243 – < ce4df90333c4fe65acb8b5089fdfe9b955ce976a
    • affected c568f7086c6e771c77aad13d727c70ef70e07243 – < 3a75b205de43365f80a33b98ec9289785da56243
    • affected d834aba5f30d9a6f98f4ca1eb07e501f1989331c
    • affected 692e847a8e6607909c4a3f98ab16ccee7849bd11
    • affected 5.15.61 – < 5.15.138
    • affected 5.18.18 – < 5.19
    • affected 5.19.2 – < 5.20
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 5.15.138 – ≤ 5.15.*
    • unaffected 6.1.62 – ≤ 6.1.*
    • unaffected 6.5.11 – ≤ 6.5.*
    • unaffected 6.6.1 – ≤ 6.6.*
    • unaffected 6.7 – ≤ *

References (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52872 badge
[![CVE-2023-52872](https://trackcve.app/badge/CVE-2023-52872.svg)](https://trackcve.app/cve/CVE-2023-52872)

Record last updated .