CVE-2026-53243
Last modified
CVE-2026-53243 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 7.0.10, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53243?
How severe is CVE-2026-53243?
How do I fix CVE-2026-53243?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53238In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53239In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5324The Brizy – Page Builder plugin for WordPress is vulnerable …7.2
- CVE-2026-53240In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53241In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53242In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53244In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53245In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53246In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53247In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53248In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53249In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53243?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
