CVE-2024-49992: drm/stm: Avoid use-after-free issues with crtc and plane
In the Linux kernel, the following vulnerability has been resolved:
drm/stm: Avoid use-after-free issues with crtc and plane
ltdcload() calls functions drmcrtcinitwithplanes(), drmuniversalplaneinit() and drmencoderinit(). These functions should not be called with parameters allocated with devmkzalloc() to avoid use-after-free issues [1].
Use allocations managed by the DRM framework.
Found by Linux Verification Center (linuxtesting.org).
[1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-49992?
The severity of CVE-2024-49992 is classified as medium due to its potential impact on use-after-free vulnerabilities in the Linux kernel.
How do I fix CVE-2024-49992?
To fix CVE-2024-49992, users should upgrade to a patched version of the Linux kernel that addresses this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-49992?
CVE-2024-49992 affects Linux kernel versions prior to 6.1.113 and between specific ranges, namely from 6.2 to 6.6.55, from 6.7 to 6.10.14, and from 6.11 to 6.11.3.
What are the implications of CVE-2024-49992 for Linux users?
The implications for Linux users include potential exploitation risks that could lead to stability issues and unauthorized access.
Is there a workaround for CVE-2024-49992 if I cannot upgrade?
There are no official workarounds for CVE-2024-49992, so upgrading to a secure version is highly recommended.