{"api_version":"1","generated_at":"2026-06-26T17:17:24+00:00","cve":"CVE-2026-53243","urls":{"html":"https://cve.report/CVE-2026-53243","api":"https://cve.report/api/cve/CVE-2026-53243.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53243","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53243"},"summary":{"title":"rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nrseq: Fix using an uninitialized stack variable in rseq_exit_user_update()\n\nThere is an bug in which an uninitialized stack variable is used in\nrseq_exit_user_update() as reported by syzbot:\n\nBUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]\n\nThe local variable:\n\n\tstruct rseq_ids ids = {\n\t\t.cpu_id\t = task_cpu(t),\n\t\t.mm_cid\t = task_mm_cid(t),\n\t\t.node_id = cpu_to_node(ids.cpu_id),\n\t};\n\nAccording to the C standard, the evaluation order of expressions in an\ninitializer list is indeterminately sequenced. The compiler (Clang, in\nthis KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before*\n`ids.cpu_id` is initialized with `task_cpu(t)`.\n\nThis is fixed by moving the assignment of ids.node_id outside the\nstructure initialization.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-25 09:16:42","updated_at":"2026-06-25 09:16:42"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/6d99479799c69c3cb588fcda19c81d8f61d64ecd","name":"https://git.kernel.org/stable/c/6d99479799c69c3cb588fcda19c81d8f61d64ecd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e12d20a63b61aaf9de4772effccf42cc9a003e58","name":"https://git.kernel.org/stable/c/e12d20a63b61aaf9de4772effccf42cc9a003e58","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53243","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53243","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d242126fd21ab8f1631fdbc8589e43a9d4229f3b e12d20a63b61aaf9de4772effccf42cc9a003e58 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 82f572449cfe75f12ea985986da60e11f308f77d 6d99479799c69c3cb588fcda19c81d8f61d64ecd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0.10 7.0.13 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"53243","cve":"CVE-2026-53243","epss":"0.001620000","percentile":"0.057690000","score_date":"2026-06-25","updated_at":"2026-06-26 00:06:14"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["include/linux/rseq_entry.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"e12d20a63b61aaf9de4772effccf42cc9a003e58","status":"affected","version":"d242126fd21ab8f1631fdbc8589e43a9d4229f3b","versionType":"git"},{"lessThan":"6d99479799c69c3cb588fcda19c81d8f61d64ecd","status":"affected","version":"82f572449cfe75f12ea985986da60e11f308f77d","versionType":"git"}]},{"defaultStatus":"unaffected","product":"Linux","programFiles":["include/linux/rseq_entry.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"7.0.13","status":"affected","version":"7.0.10","versionType":"semver"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.13","versionStartIncluding":"7.0.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nrseq: Fix using an uninitialized stack variable in rseq_exit_user_update()\n\nThere is an bug in which an uninitialized stack variable is used in\nrseq_exit_user_update() as reported by syzbot:\n\nBUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]\n\nThe local variable:\n\n\tstruct rseq_ids ids = {\n\t\t.cpu_id\t = task_cpu(t),\n\t\t.mm_cid\t = task_mm_cid(t),\n\t\t.node_id = cpu_to_node(ids.cpu_id),\n\t};\n\nAccording to the C standard, the evaluation order of expressions in an\ninitializer list is indeterminately sequenced. The compiler (Clang, in\nthis KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before*\n`ids.cpu_id` is initialized with `task_cpu(t)`.\n\nThis is fixed by moving the assignment of ids.node_id outside the\nstructure initialization."}],"providerMetadata":{"dateUpdated":"2026-06-25T08:39:37.794Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/e12d20a63b61aaf9de4772effccf42cc9a003e58"},{"url":"https://git.kernel.org/stable/c/6d99479799c69c3cb588fcda19c81d8f61d64ecd"}],"title":"rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53243","datePublished":"2026-06-25T08:39:37.794Z","dateReserved":"2026-06-09T07:44:35.393Z","dateUpdated":"2026-06-25T08:39:37.794Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-25 09:16:42","lastModifiedDate":"2026-06-25 09:16:42","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53243","Ordinal":"1","Title":"rseq: Fix using an uninitialized stack variable in rseq_exit_use","CVE":"CVE-2026-53243","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53243","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nrseq: Fix using an uninitialized stack variable in rseq_exit_user_update()\n\nThere is an bug in which an uninitialized stack variable is used in\nrseq_exit_user_update() as reported by syzbot:\n\nBUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]\n\nThe local variable:\n\n\tstruct rseq_ids ids = {\n\t\t.cpu_id\t = task_cpu(t),\n\t\t.mm_cid\t = task_mm_cid(t),\n\t\t.node_id = cpu_to_node(ids.cpu_id),\n\t};\n\nAccording to the C standard, the evaluation order of expressions in an\ninitializer list is indeterminately sequenced. The compiler (Clang, in\nthis KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before*\n`ids.cpu_id` is initialized with `task_cpu(t)`.\n\nThis is fixed by moving the assignment of ids.node_id outside the\nstructure initialization.","Type":"Description","Title":"rseq: Fix using an uninitialized stack variable in rseq_exit_use"}]}}}