drm: Account property blob allocations to memcg
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.2
References 8
git.kernel.org
- stable/c/b6117210ed349356f8e6027ff020b4d620bca42b
- stable/c/815fa29cab3c67bebb9d0b5f41145cdd3a14d04d
- stable/c/866e0c1a9e7244d58ed74853cb22b81e1900cfdd
- stable/c/bbfaa5761f589a81031b493cb01275a990d6fb25
- stable/c/8e1664b9ee43608eb973d357ae5d858d30cbc9ca
- stable/c/cb8b9a1755fe9f38e4fb7f287486d7e7fab3dba4
- stable/c/405fd652d8fedff219a8f48daf8f20e881e303ab
- stable/c/26b4309a3ab82a0697751cde52eb336c29c19035