drm/client: Fix memory leak in drm_client_modeset_probe
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a2889606636d135148de101fe3311dfea67baf1c · < 2329cc7a101af1a844fbf706c0724c0baea38365| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/client: Fix memory leak in drm_client_modeset_probe
When a new mode is set to modeset->mode, the previous mode should be freed. This fixes the following kmemleak report:
drm_mode_duplicate+0x45/0x220 [drm] drm_client_modeset_probe+0x944/0xf50 [drm] __drm_fb_helper_initial_config_and_unlock+0xb4/0x2c0 [drm_kms_helper] drm_fbdev_client_hotplug+0x2bc/0x4d0 [drm_kms_helper] drm_client_register+0x169/0x240 [drm] ast_pci_probe+0x142/0x190 [ast] local_pci_probe+0xdc/0x180 work_for_cpu_fn+0x4e/0xa0 process_one_work+0x8b7/0x1540 worker_thread+0x70a/0xed0 kthread+0x29f/0x340 ret_from_fork+0x1f/0x30
From the CVE record · Linux
The Linux kernel’s DRM client modeset probe leaks memory when it replaces a mode without freeing the previous one. The input does not describe an attacker path or specify whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with DRM client modesetting should check whether their kernel includes the fix; affected versions are not specified.