7.8
CVE-2023-52439
- EPSS 0.01%
- Veröffentlicht 20.02.2024 21:15:08
- Zuletzt bearbeitet 27.12.2024 16:15:23
- Quelle 416baaa9-dc9f-4396-8d5f-8c081f
- CVE-Watchlists
- Unerledigt
In the Linux kernel, the following vulnerability has been resolved: uio: Fix use-after-free in uio_open core-1 core-2 ------------------------------------------------------- uio_unregister_device uio_open idev = idr_find() device_unregister(&idev->dev) put_device(&idev->dev) uio_device_release get_device(&idev->dev) kfree(idev) uio_free_minor(minor) uio_release put_device(&idev->dev) kfree(idev) ------------------------------------------------------- In the core-1 uio_unregister_device(), the device_unregister will kfree idev when the idev->dev kobject ref is 1. But after core-1 device_unregister, put_device and before doing kfree, the core-2 may get_device. Then: 1. After core-1 kfree idev, the core-2 will do use-after-free for idev. 2. When core-2 do uio_release and put_device, the idev will be double freed. To address this issue, we can get idev atomic & inc idev reference with minor_lock.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version > 4.18.0 < 4.19.306
Linux ≫ Linux Kernel Version >= 4.20.0 < 5.4.268
Linux ≫ Linux Kernel Version >= 5.5.0 < 5.10.209
Linux ≫ Linux Kernel Version >= 5.11.0 < 5.15.148
Linux ≫ Linux Kernel Version >= 5.16.0 < 6.1.74
Linux ≫ Linux Kernel Version >= 6.2.0 < 6.6.13
Linux ≫ Linux Kernel Version >= 6.7.0 < 6.7.1
Linux ≫ Linux Kernel Version4.18 Update-
Linux ≫ Linux Kernel Version4.18 Updaterc5
Linux ≫ Linux Kernel Version4.18 Updaterc6
Linux ≫ Linux Kernel Version4.18 Updaterc7
Linux ≫ Linux Kernel Version4.18 Updaterc8
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.01% | 0.009 |
| Quelle | 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
|
CWE-415 Double Free
The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.