{
  "cveId": "CVE-2026-53204",
  "url": "https://patchblox.com/security/cve/CVE-2026-53204",
  "summary": "CVE-2026-53204 is fixed in linux on 1 platform by DEBIAN-CVE-2026-53204 (version 7.0.13-1), released June 28, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  firmware: stratix10-rsu: Fix NULL deref on rsu_s...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  firmware: stratix10-rsu: Fix NULL deref on rsu_send_msg() timeout in probe  rsu_send_msg() can return -ETIMEDOUT when wait_for_completion_interruptible_timeout() fires while the SMC call is still pending. In stratix10_rsu_probe(), the error paths for COMMAND_RSU_DCMF_VERSION, COMMAND_RSU_DCMF_STATUS, COMMAND_RSU_MAX_RETRY and COMMAND_RSU_GET_SPT_TABLE call stratix10_svc_free_channel() - which sets chan-\u003Escl to NULL - but then fall through and queue the next request on the same channel. The next svc kthread that runs will dereference pdata-\u003Echan-\u003Escl in its receive callback path, triggering a NULL pointer dereference identical to the one fixed by commit c45f7263100c (\u0022firmware: stratix10-rsu: Fix NULL pointer dereference when RSU is disabled\u0022) for the COMMAND_RSU_STATUS path.  Apply the same cleanup pattern to the remaining failure paths: remove the async client, free the channel, and return early so no further messages are queued on a channel whose scl has been cleared.  While at it, clean up stratix10_rsu_probe() in two ways without changing behavior:  - Drop redundant zero-initialization of fields already cleared by   devm_kzalloc(): client.receive_cb, status.* and spt0/1_address   (INVALID_SPT_ADDRESS is 0x0).  - Replace five identical 3-line error-cleanup blocks   (stratix10_svc_remove_async_client() \u002B stratix10_svc_free_channel() \u002B   return ret) with goto labels (remove_async_client, free_channel),   matching the standard kernel resource-unwinding pattern and making it   easier to extend the probe sequence without forgetting matching   cleanup.  Also move init_completion() next to mutex_init() so sync-primitive initialization is grouped before anything that could trigger a callback.  --- v2: Add a minor clean-up of the function stratix10_rsu_probe() to have a     centralize exit for all the rsu_send_async_msg() and rsu_send_msg().",
  "published": "2026-06-25T09:16:37Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00143,
  "epssPercentile": 0.03658,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.0.13-1",
      "fix": "DEBIAN-CVE-2026-53204",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-53204",
      "released": "2026-06-28T17:47:07Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}