Answer in brief
CVE-2023-52439 records a High severity (CVSS 7.8) vulnerability in uio: Fix use-after-free in uio_open. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-52439 records a High severity (CVSS 7.8) vulnerability in uio: Fix use-after-free in uio_open. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:rc7:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:rc8:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <3174e0f7de1ba392dc191625da83df02d695b60c || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <e93da893d52d82d57fc0db2ca566024e0f26ff50 || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <5e0be1229ae199ebb90b33102f74a0f22d152570 || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <5cf604ee538ed0c467abe3b4cda5308a6398f0f7 || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <17a8519cb359c3b483fb5c7367efa9a8a508bdea || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <35f102607054faafe78d2a6994b18d5d9d6e92ad || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <913205930da6213305616ac539447702eaa85e41 || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <0c9ae0b8605078eafc3bea053cc78791e97ba2e2 || 13af019c87f2d90e663742cb1a819834048842ae || >=4.14.100 <4.15 | 3174e0f7de1ba392dc191625da83df02d695b60c, e93da893d52d82d57fc0db2ca566024e0f26ff50, 5e0be1229ae199ebb90b33102f74a0f22d152570, 5cf604ee538ed0c467abe3b4cda5308a6398f0f7, 17a8519cb359c3b483fb5c7367efa9a8a508bdea, 35f102607054faafe78d2a6994b18d5d9d6e92ad, 913205930da6213305616ac539447702eaa85e41, 0c9ae0b8605078eafc3bea053cc78791e97ba2e2, 4.15 |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Feb 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:rc7:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.18:rc8:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <3174e0f7de1ba392dc191625da83df02d695b60c || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <e93da893d52d82d57fc0db2ca566024e0f26ff50 || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <5e0be1229ae199ebb90b33102f74a0f22d152570 || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <5cf604ee538ed0c467abe3b4cda5308a6398f0f7 || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <17a8519cb359c3b483fb5c7367efa9a8a508bdea || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <35f102607054faafe78d2a6994b18d5d9d6e92ad || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <913205930da6213305616ac539447702eaa85e41 || >=57c5f4df0a5a0ee83df799991251e2ee93a5e4e9 <0c9ae0b8605078eafc3bea053cc78791e97ba2e2 || 13af019c87f2d90e663742cb1a819834048842ae || >=4.14.100 <4.15 | 3174e0f7de1ba392dc191625da83df02d695b60c, e93da893d52d82d57fc0db2ca566024e0f26ff50, 5e0be1229ae199ebb90b33102f74a0f22d152570, 5cf604ee538ed0c467abe3b4cda5308a6398f0f7, 17a8519cb359c3b483fb5c7367efa9a8a508bdea, 35f102607054faafe78d2a6994b18d5d9d6e92ad, 913205930da6213305616ac539447702eaa85e41, 0c9ae0b8605078eafc3bea053cc78791e97ba2e2, 4.15 |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Feb 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.