7
CVE-2023-6546
- EPSS 0.29%
- Published 21.12.2023 20:15:08
- Last modified 21.11.2024 08:44:04
- Source secalert@redhat.com
- Teams watchlist Login
- Open Login
A race condition was found in the GSM 0710 tty multiplexor in the Linux kernel. This issue occurs when two threads execute the GSMIOC_SETCONF ioctl on the same tty file descriptor with the gsm line discipline enabled, and can lead to a use-after-free problem on a struct gsm_dlci while restarting the gsm mux. This could allow a local unprivileged user to escalate their privileges on the system.
Data is provided by the National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version < 6.5
Linux ≫ Linux Kernel Version6.5 Updaterc1
Linux ≫ Linux Kernel Version6.5 Updaterc2
Linux ≫ Linux Kernel Version6.5 Updaterc3
Linux ≫ Linux Kernel Version6.5 Updaterc4
Linux ≫ Linux Kernel Version6.5 Updaterc5
Linux ≫ Linux Kernel Version6.5 Updaterc6
Fedoraproject ≫ Fedora Version39
Redhat ≫ Enterprise Linux Version8.0
Redhat ≫ Enterprise Linux Version9.0
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.29% | 0.521 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 7 | 1 | 5.9 |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
|
| secalert@redhat.com | 7 | 1 | 5.9 |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
|
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.