CVE-2026-53243 rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()

Medium 5.5 Published Updated

An uninitialized stack variable in the Linux kernel rseq subsystem allows local attackers to read sensitive kernel memory.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-53243?

CVE-2026-53243 is a medium-severity vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-908

Which versions are affected by CVE-2026-53243?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-53243?

Apply the vendor's patch.

Is CVE-2026-53243 being exploited?

There is no known exploitation of CVE-2026-53243 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as DEBIAN-CVE-2026-53243, GHSA-qhcg-6255-c538, UBUNTU-CVE-2026-53243.

Is CVE-2026-53243 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free