{
  "cveId": "CVE-2026-53024",
  "url": "https://patchblox.com/security/cve/CVE-2026-53024",
  "summary": "CVE-2026-53024 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-53024, released June 25, 2026. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  greybus: raw: fix use-after-free if write is cal...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  greybus: raw: fix use-after-free if write is called after disconnect  If a user writes to the chardev after disconnect has been called, the kernel panics with the following trace (with CONFIG_INIT_ON_FREE_DEFAULT_ON=y):          BUG: kernel NULL pointer dereference, address: 0000000000000218          ...         Call Trace:          \u003CTASK\u003E          gb_operation_create_common\u002B0x61/0x180          gb_operation_create_flags\u002B0x28/0xa0          gb_operation_sync_timeout\u002B0x6f/0x100          raw_write\u002B0x7b/0xc7 [gb_raw]          vfs_write\u002B0xcf/0x420          ? task_mm_cid_work\u002B0x136/0x220          ksys_write\u002B0x63/0xe0          do_syscall_64\u002B0xa4/0x290          entry_SYSCALL_64_after_hwframe\u002B0x77/0x7f  Disconnect calls gb_connection_destroy, which ends up freeing the connection object. When gb_operation_sync is called in the write file operations, its gets a freed connection as parameter and the kernel panics.  The gb_connection_destroy cannot be moved out of the disconnect function, as the Greybus subsystem expect all connections belonging to a bundle to be destroyed when disconnect returns.  To prevent this bug, use a rw lock to synchronize access between write and disconnect. This guarantees that the write function doesn\u0027t try to use a disconnected connection.",
  "published": "2026-06-24T17:17:13Z",
  "severity": "high",
  "cvss": 7.8,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss": 0.0017,
  "epssPercentile": 0.06429,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.115-2",
      "fix": "DEBIAN-CVE-2026-53024",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-53024",
      "released": "2026-06-25T17:23:13Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.0.10-1",
      "fix": "DEBIAN-CVE-2026-53024",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-53024",
      "released": "2026-06-25T17:23:13Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T19:38:12Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}