Loading vulnerability…
CVE-2022-1280 is a race-condition use-after-free in the Linux kernel DRM lease-handling code. The flaw occurs in drm_lease_held when drm_mode_getresources retains a DRM master pointer while drm_setmaster_ioctl, through drm_new_set_master, can concurrently free the prior pointer. Insufficient synchronization of DRM master-pointer access permits dereference of freed memory. The issue was fixed upstream in Linux kernel 5.15-rc1 through changes that serialize and lock access to DRM master pointers.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel DRM use-after-free arising from concurrency between drm_setmaster_ioctl() and drm_mode_getresources().
Linux kernel DRM concurrency use-after-free vulnerability.
Linux kernel vulnerability addressed by RHSA-2022:7683; no flaw details are provided in this advisory text.
A Linux kernel DRM concurrency use-after-free race condition between drm_setmaster_ioctl and drm_mode_getresources. The race can result in use of a freed DRM master pointer because appropriate locking was absent.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.