Vulnerability · Published Dec 24, 2025 · Assigned by Linux
CVE-2023-54091drm/client: Fix memory leak in drm_client_target_cloned
Unrated
In plain English
A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 17% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: drm/client: Fix memory leak in drm_client_target_cloned dmt_mode is allocated and never freed in this function. It was found with the ast driver, but most drivers using generic fbdev setup are probably affected. This fixes the following kmemleak report: backtrace: [<00000000b391296d>] drm_mode_duplicate+0x45/0x220 [drm] [<00000000e45bb5b3>] drm_client_target_cloned.constprop.0+0x27b/0x480 [drm] [<00000000ed2d3a37>] drm_client_modeset_probe+0x6bd/0xf50 [drm] [<0000000010e5cc9d>] __drm_fb_helper_initial_config_and_unlock+0xb4/0x2c0 [drm_kms_helper] [<00000000909f82ca>] drm_fbdev_client_hotplug+0x2bc/0x4d0 [drm_kms_helper] [<00000000063a69aa>] drm_client_register+0x169/0x240 [drm] [<00000000a8c61525>] ast_pci_probe+0x142/0x190 [ast] [<00000000987f19bb>] local_pci_probe+0xdc/0x180 [<000000004fca231b>] work_for_cpu_fn+0x4e/0xa0 [<0000000000b85301>] process_one_work+0x8b7/0x1540 [<000000003375b17c>] worker_thread+0x70a/0xed0 [<00000000b0d43cd9>] kthread+0x29f/0x340 [<000000008d770833>] ret_from_fork+0x1f/0x30 unreferenced object 0xff11000333089a00 (size 128):
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.52-1 | DEBIAN-CVE-2023-54091 |
| Debian:13 | linux | 6.4.11-1 | DEBIAN-CVE-2023-54091 |
| Debian:14 | linux | 6.4.11-1 | DEBIAN-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux | 5.15.0-88.98 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1049.54 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1051.59 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1051.59.1 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1046.54 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1046.51 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1032.38 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1042.45 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1045.51 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1046.51 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-88.98 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1040.40 | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1019.19 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1006.6 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1047.53 | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1042.45 | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-54091 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-54091 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1d42bbc8f7f9ce4d852692ef7aa336b133b0830a – before d3009700f48602b557eade1f22c98b6bc20247e81d42bbc8f7f9ce4d852692ef7aa336b133b0830a – before a4b978249e8fa94956fce8b70a709f7797716f621d42bbc8f7f9ce4d852692ef7aa336b133b0830a – before 52daf6ba2e0d201640cb1ce42049c5c4426b4d6e1d42bbc8f7f9ce4d852692ef7aa336b133b0830a – before 105275879a80503686a8108af2f5c579a1c5aef41d42bbc8f7f9ce4d852692ef7aa336b133b0830a – before a85e23a1ef63e45a18f0a30d7816fcb4a865ca951d42bbc8f7f9ce4d852692ef7aa336b133b0830a – before b5359d7a5087ac398fc429da6833133b4784c2681d42bbc8f7f9ce4d852692ef7aa336b133b0830a – before 4b596a6e2d2e0f9c14e4122506dd715f43fcd7271d42bbc8f7f9ce4d852692ef7aa336b133b0830a – before c2a88e8bdf5f6239948d75283d0ae7e0c7945b03 |
| Linux | Linux | 2.6.35 |
References
- https://git.kernel.org/stable/c/d3009700f48602b557eade1f22c98b6bc20247e8
- https://git.kernel.org/stable/c/a4b978249e8fa94956fce8b70a709f7797716f62
- https://git.kernel.org/stable/c/52daf6ba2e0d201640cb1ce42049c5c4426b4d6e
- https://git.kernel.org/stable/c/105275879a80503686a8108af2f5c579a1c5aef4
- https://git.kernel.org/stable/c/a85e23a1ef63e45a18f0a30d7816fcb4a865ca95
- https://git.kernel.org/stable/c/b5359d7a5087ac398fc429da6833133b4784c268
- https://git.kernel.org/stable/c/4b596a6e2d2e0f9c14e4122506dd715f43fcd727
- https://git.kernel.org/stable/c/c2a88e8bdf5f6239948d75283d0ae7e0c7945b03