drm: Account property blob allocations to memcg
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f5d2ea479b9b2619965d43db70939589afe43a · < cb8b9a1755fe9f38e4fb7f287486d7e7fab3dba4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm: Account property blob allocations to memcg
DRM_IOCTL_MODE_CREATEPROPBLOB 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 GFP_KERNEL_ACCOUNT 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.
From the CVE record · Linux
The Linux kernel does not charge DRM property blob data allocations to the allocating process's memory cgroup. An unprivileged local user can request arbitrary-sized blobs and potentially exhaust system memory, causing a system-wide out-of-memory condition. No user interaction is required.
Engineers running Linux kernels with the affected DRM property blob allocation behavior should check their systems; affected versions were not provided.