rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()
Summary
| CVE | CVE-2026-53243 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-25 09:16:42 UTC |
| Updated | 2026-06-25 09:16:42 UTC |
| Description | 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: struct rseq_ids ids = { .cpu_id = task_cpu(t), .mm_cid = task_mm_cid(t), .node_id = cpu_to_node(ids.cpu_id), }; 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. |
Risk And Classification
EPSS: 0.001620000 probability, percentile 0.057690000 (date 2026-06-25)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected d242126fd21ab8f1631fdbc8589e43a9d4229f3b e12d20a63b61aaf9de4772effccf42cc9a003e58 git | Not specified |
| CNA | Linux | Linux | affected 82f572449cfe75f12ea985986da60e11f308f77d 6d99479799c69c3cb588fcda19c81d8f61d64ecd git | Not specified |
| CNA | Linux | Linux | affected 7.0.10 7.0.13 semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/6d99479799c69c3cb588fcda19c81d8f61d64ecd | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e12d20a63b61aaf9de4772effccf42cc9a003e58 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.