VulnerabilityPublished 8 May 2026Updated 6 Nov 2026

CVE-2026-43287: Linux kernel · drm: Account property blob allocations to memcg

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in cb8b9a1755fe9f38e4fb7f287486d7e7fab3dba4 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:04 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in cb8b9a1755fe9f38e4fb7f287486d7e7fab3dba4, bbfaa5761f589a81031b493cb01275a990d6fb25, b6117210ed349356f8e6027ff020b4d620bca42b +5

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ e2f5d2ea479b9b2619965d43db70939589afe43a, < cb8b9a1755fe9f38e4fb7f287486d7e7fab3dba4	Fixed in cb8b9a1755fe9f38e4fb7f287486d7e7fab3dba4
LinuxLinux	Affected ≥ e2f5d2ea479b9b2619965d43db70939589afe43a, < bbfaa5761f589a81031b493cb01275a990d6fb25	Fixed in bbfaa5761f589a81031b493cb01275a990d6fb25
LinuxLinux	Affected ≥ e2f5d2ea479b9b2619965d43db70939589afe43a, < b6117210ed349356f8e6027ff020b4d620bca42b	Fixed in b6117210ed349356f8e6027ff020b4d620bca42b
LinuxLinux	Affected ≥ e2f5d2ea479b9b2619965d43db70939589afe43a, < 866e0c1a9e7244d58ed74853cb22b81e1900cfdd	Fixed in 866e0c1a9e7244d58ed74853cb22b81e1900cfdd
LinuxLinux	Affected ≥ e2f5d2ea479b9b2619965d43db70939589afe43a, < 815fa29cab3c67bebb9d0b5f41145cdd3a14d04d	Fixed in 815fa29cab3c67bebb9d0b5f41145cdd3a14d04d
LinuxLinux	Affected ≥ e2f5d2ea479b9b2619965d43db70939589afe43a, < 405fd652d8fedff219a8f48daf8f20e881e303ab	Fixed in 405fd652d8fedff219a8f48daf8f20e881e303ab

Description

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.

References

Community reviews

Loading reviews…