CVE-2023-52872 Affecting kernel-livepatch-5_14_21-150400_24_122-default package, versions <1-150400.9.3.2


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES154-KERNELLIVEPATCH5142115040024122DEFAULT-7398191
  • published26 Jun 2024
  • disclosed25 Jun 2024

Introduced: 25 Jun 2024

CVE-2023-52872  (opens in a new tab)

How to fix?

Upgrade SLES:15.4 kernel-livepatch-5_14_21-150400_24_122-default to version 1-150400.9.3.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-5_14_21-150400_24_122-default package and not the kernel-livepatch-5_14_21-150400_24_122-default package as distributed by SLES. See How to fix? for SLES:15.4 relevant fixed versions and status.

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.

CVSS Scores

version 3.1