CVE-2026-43287: drm: Account property blob allocations to memcg
In the Linux kernel, the following vulnerability has been resolved:
drm: Account property blob allocations to memcg
DRMIOCTLMODECREATEPROPBLOB allows userspace to allocate arbitrary-sized property blobs backed by kernel memory.
Currently, the blob data allocation is not accounted to the allocating process's memory cgroup, allowing unprivileged users to trigger unbounded kernel memory consumption and potentially cause system-wide OOM.
Mark the property blob data allocation with GFPKERNELACCOUNT so that the memory is properly charged to the caller's memcg. This ensures existing cgroup memory limits apply and prevents uncontrolled kernel memory growth without introducing additional policy or per-file limits.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43287?
CVE-2026-43287 has been classified as a moderate severity vulnerability due to potential memory allocation issues.
How do I fix CVE-2026-43287?
To fix CVE-2026-43287, it is recommended to update to the latest stable version of the Linux kernel where the vulnerability has been patched.
Who is affected by CVE-2026-43287?
All users of the affected Linux kernel versions utilizing the DRM (Direct Rendering Manager) subsystem are susceptible to CVE-2026-43287.
What are the potential consequences of CVE-2026-43287?
CVE-2026-43287 could potentially lead to denial of service or arbitrary memory access in affected systems.
Is CVE-2026-43287 being actively exploited in the wild?
As of now, there is no evidence to suggest CVE-2026-43287 is being actively exploited, but users should still apply the necessary updates.