7.8
CVE-2023-0461
- EPSS 0.12%
- Published 28.02.2023 15:15:11
- Last modified 21.11.2024 07:37:13
- Source cve-coordination@google.com
- CVE-Watchlists
- Open
LoginThere is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege. There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock. When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket. The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is created from the listener, the context is inherited and vulnerable. The setsockopt TCP_ULP operation does not require any privilege. We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c
Data is provided by the National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 4.13.0 < 4.14.303
Linux ≫ Linux Kernel Version >= 4.19 < 4.19.270
Linux ≫ Linux Kernel Version >= 5.4 < 5.4.229
Linux ≫ Linux Kernel Version >= 5.10 < 5.10.163
Linux ≫ Linux Kernel Version >= 5.15 < 5.15.88
Linux ≫ Linux Kernel Version >= 6.0 < 6.0.19
Linux ≫ Linux Kernel Version >= 6.1 < 6.1.5
Linux ≫ Linux Kernel Version6.2 Updaterc1
Linux ≫ Linux Kernel Version6.2 Updaterc2
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.12% | 0.316 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
| cve-coordination@google.com | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
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.