Linux KernelOperating system · Linux
CVE-2022-1419
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe root cause of this vulnerability is that the ioctl$DRM_IOCTL_MODE_DESTROY_DUMB can decrease refcount of *drm_vgem_gem_object *(created in *vgem_gem_dumb_create*) concurrently, and *vgem_gem_dumb_create *will access the freed drm_vgem_gem_object.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA race condition in the Linux kernel's VGEM (Virtual GEM) driver allows ioctl$DRM_IOCTL_MODE_DESTROY_DUMB to decrease the reference count of a drm_vgem_gem_object while vgem_gem_dumb_create concurrently accesses the already-freed object, resulting in a use-after-free vulnerability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
< 5.6= 5.6
Debian LinuxOperating system
= 10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check kernel versionRun 'uname -r' or 'cat /proc/version' to get the running kernel versionAffected if Kernel version is less than 5.6 or exactly 5.6 (e.g., 5.6.x)
-
Verify VGEM driver availabilityCheck if the vgem module exists in the kernel: 'ls /sys/module/vgem' or 'grep -i vgem /proc/modules' (if modular) or check kernel config at /boot/config-$(uname -r) for CONFIG_DRM_VGEM=yAffected if VGEM driver is compiled into the kernel or loaded as a module
-
Check for DRM device nodesList DRM device nodes: 'ls -la /dev/dri/' or check for /dev/dri/card* entries that may use the VGEM driverAffected if DRM device nodes exist and are accessible to the user
-
Verify user access to DRM ioctlsCheck if unprivileged users can access DRM devices: 'ls -la /dev/dri/' and verify group permissions. The vulnerable ioctl is DRM_IOCTL_MODE_DESTROY_DUMBAffected if Users have permission to invoke DRM ioctls on /dev/dri/ devices backed by VGEM
The system is affected if it runs a kernel version < 5.6 or = 5.6, has the VGEM DRM driver available, and allows user access to the DRM ioctl interface where the race condition can be triggered.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.6
Apply the upstream kernel patch that adds proper synchronization to prevent concurrent access to the drm_vgem_gem_object during destruction. Update to a kernel version containing the fix.
Linux Kernel 5.7 or later; Debian 10 should update to a kernel version containing the vgem driver fix
- Check current kernel version using: uname -r
- Research available kernel versions for your distribution that include the fix for CVE-2022-1419
- For Debian 10 (Buster), check if a point release or backported kernel is available that includes the fix
- Update package lists: apt update
- Install the newer kernel: apt install linux-image-<version>
- Reboot the system into the new kernel: systemctl reboot
- Verify the new kernel is running and the vulnerability is addressed: uname -r
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1419 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1419 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data