{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.105-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.8-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux-6.12"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.107-1~deb12u1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure  Two paths through vmw_vkms_init() can leave vmw-\u003ecrc_workq NULL while still leaving the rest of the driver in a state that calls vmw_vkms_cleanup() at module unload:    1. vmw_host_get_guestinfo(GUESTINFO_VBLANK, ...) failing or      returning an oversized buffer -- the common case on hosts      without a VBLANK guestinfo entry -- early-returned before the      workqueue allocation.   2. alloc_ordered_workqueue() returning NULL on memory pressure.  vmw_vkms_cleanup() then calls destroy_workqueue(NULL), which dereferences wq-\u003ename and panics.  Fix the first case by removing the early return: vmw-\u003evkms_enabled is already false on the rpci-failure path so no work will ever be queued, and allocating the workqueue unconditionally keeps the control flow simple.  Fix the second case by guarding the cleanup with a NULL check, since alloc_ordered_workqueue() can still fail under low memory.",
  "id": "DEBIAN-CVE-2026-74442",
  "modified": "2026-09-19T21:47:33.265759504Z",
  "published": "2026-08-15T13:17:48.760Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-74442"
    }
  ],
  "upstream": [
    "CVE-2026-74442"
  ]
}