CVE-2023-52837
Medium
Elevated severity or exploit probability.
CVSS base
7.8
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS — probability of exploitation (30 days)
0.3%
16.7th percentile
CISA KEV
Not listed
Weakness / dates
CWE-416
Published 2024-05-21 · modified 2026-08-04
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2024-05-21 — Published (NVD)
- 2026-08-04 — Last modified (NVD)
Description
In the Linux kernel, the following vulnerability has been resolved: nbd: fix uaf in nbd_open Commit 4af5f2e03013 ("nbd: use blk_mq_alloc_disk and blk_cleanup_disk") cleans up disk by blk_cleanup_disk() and it won't set disk->private_data as NULL as before. UAF may be triggered in nbd_open() if someone tries to open nbd device right after nbd_put() since nbd has been free in nbd_dev_remove(). Fix this by implementing ->free_disk and free private data in it.
Affected
References
- https://git.kernel.org/stable/c/327462725b0f759f093788dfbcb2f1fd132f956b
- https://git.kernel.org/stable/c/4e9b3ec84dc97909876641dad14e0a2300d6c2a3
- https://git.kernel.org/stable/c/56bd7901b5e9dbc9112036ea615ebcba1565fafe
- https://git.kernel.org/stable/c/879947f4180bc6e83af64eb0515e0cf57fce15db
- https://git.kernel.org/stable/c/327462725b0f759f093788dfbcb2f1fd132f956b
- https://git.kernel.org/stable/c/4e9b3ec84dc97909876641dad14e0a2300d6c2a3
- https://git.kernel.org/stable/c/56bd7901b5e9dbc9112036ea615ebcba1565fafe
- https://git.kernel.org/stable/c/879947f4180bc6e83af64eb0515e0cf57fce15db