{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.13-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()  There is an bug in which an uninitialized stack variable is used in rseq_exit_user_update() as reported by syzbot:  BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]  The local variable:  \tstruct rseq_ids ids = { \t\t.cpu_id\t = task_cpu(t), \t\t.mm_cid\t = task_mm_cid(t), \t\t.node_id = cpu_to_node(ids.cpu_id), \t};  According to the C standard, the evaluation order of expressions in an initializer list is indeterminately sequenced. The compiler (Clang, in this KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before* `ids.cpu_id` is initialized with `task_cpu(t)`.  This is fixed by moving the assignment of ids.node_id outside the structure initialization.",
  "id": "DEBIAN-CVE-2026-53243",
  "modified": "2026-09-14T16:47:34.593181945Z",
  "published": "2026-06-25T09:16:42.260Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-53243"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-53243"
  ]
}