{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-53135 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53135 is a high-severity memory corruption vulnerability in Linux kernel, published on 2 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-53135 and fix it if it is affected.\n\nWhat it is: CVE-2023-53135 is a high-severity memory corruption vulnerability in Linux kernel, published on 2 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-53135 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-53135/ (Markdown: https://insights.sbomify.com/CVE-2023-53135/index.md)","id":"CVE-2023-53135","markdown":"https://insights.sbomify.com/CVE-2023-53135/index.md","name":"CVE-2023-53135","record":{"aliases":["BELL-CVE-2023-53135","DEBIAN-CVE-2023-53135","GHSA-2c79-g4hv-82qp","UBUNTU-CVE-2023-53135"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A stack-out-of-bounds read in the RISC-V kernel unwinder can cause a kernel crash when KASAN is enabled and frame pointers are disabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode\n\nWhen CONFIG_FRAME_POINTER is unset, the stack unwinding function\nwalk_stackframe randomly reads the stack and then, when KASAN is enabled,\nit can lead to the following backtrace:\n\n[    0.000000] ==================================================================\n[    0.000000] BUG: KASAN: stack-out-of-bounds in walk_stackframe+0xa6/0x11a\n[    0.000000] Read of size 8 at addr ffffffff81807c40 by task swapper/0\n[    0.000000]\n[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 6.2.0-12919-g24203e6db61f #43\n[    0.000000] Hardware name: riscv-virtio,qemu (DT)\n[    0.000000] Call Trace:\n[    0.000000] [\u003cffffffff80007ba8\u003e] walk_stackframe+0x0/0x11a\n[    0.000000] [\u003cffffffff80099ecc\u003e] init_param_lock+0x26/0x2a\n[    0.000000] [\u003cffffffff80007c4a\u003e] walk_stackframe+0xa2/0x11a\n[    0.000000] [\u003cffffffff80c49c80\u003e] dump_stack_lvl+0x22/0x36\n[    0.000000] [\u003cffffffff80c3783e\u003e] print_report+0x198/0x4a8\n[    0.000000] [\u003cffffffff80099ecc\u003e] init_param_lock+0x26/0x2a\n[    0.000000] [\u003cffffffff80007c4a\u003e] walk_stackframe+0xa2/0x11a\n[    0.000000] [\u003cffffffff8015f68a\u003e] kasan_report+0x9a/0xc8\n[    0.000000] [\u003cffffffff80007c4a\u003e] walk_stackframe+0xa2/0x11a\n[    0.000000] [\u003cffffffff80007c4a\u003e] walk_stackframe+0xa2/0x11a\n[    0.000000] [\u003cffffffff8006e99c\u003e] desc_make_final+0x80/0x84\n[    0.000000] [\u003cffffffff8009a04e\u003e] stack_trace_save+0x88/0xa6\n[    0.000000] [\u003cffffffff80099fc2\u003e] filter_irq_stacks+0x72/0x76\n[    0.000000] [\u003cffffffff8006b95e\u003e] devkmsg_read+0x32a/0x32e\n[    0.000000] [\u003cffffffff8015ec16\u003e] kasan_save_stack+0x28/0x52\n[    0.000000] [\u003cffffffff8006e998\u003e] desc_make_final+0x7c/0x84\n[    0.000000] [\u003cffffffff8009a04a\u003e] stack_trace_save+0x84/0xa6\n[    0.000000] [\u003cffffffff8015ec52\u003e] kasan_set_track+0x12/0x20\n[    0.000000] [\u003cffffffff8015f22e\u003e] __kasan_slab_alloc+0x58/0x5e\n[    0.000000] [\u003cffffffff8015e7ea\u003e] __kmem_cache_create+0x21e/0x39a\n[    0.000000] [\u003cffffffff80e133ac\u003e] create_boot_cache+0x70/0x9c\n[    0.000000] [\u003cffffffff80e17ab2\u003e] kmem_cache_init+0x6c/0x11e\n[    0.000000] [\u003cffffffff80e00fd6\u003e] mm_init+0xd8/0xfe\n[    0.000000] [\u003cffffffff80e011d8\u003e] start_kernel+0x190/0x3ca\n[    0.000000]\n[    0.000000] The buggy address belongs to stack of task swapper/0\n[    0.000000]  and is located at offset 0 in frame:\n[    0.000000]  stack_trace_save+0x0/0xa6\n[    0.000000]\n[    0.000000] This frame has 1 object:\n[    0.000000]  [32, 56) 'c'\n[    0.000000]\n[    0.000000] The buggy address belongs to the physical page:\n[    0.000000] page:(____ptrval____) refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x81a07\n[    0.000000] flags: 0x1000(reserved|zone=0)\n[    0.000000] raw: 0000000000001000 ff600003f1e3d150 ff600003f1e3d150 0000000000000000\n[    0.000000] raw: 0000000000000000 0000000000000000 00000001ffffffff\n[    0.000000] page dumped because: kasan: bad access detected\n[    0.000000]\n[    0.000000] Memory state around the buggy address:\n[    0.000000]  ffffffff81807b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n[    0.000000]  ffffffff81807b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n[    0.000000] \u003effffffff81807c00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 f3\n[    0.000000]                                            ^\n[    0.000000]  ffffffff81807c80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00\n[    0.000000]  ffffffff81807d00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n[    0.000000] ==================================================================\n\nFix that by using READ_ONCE_NOCHECK when reading the stack in imprecise\nmode.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode","id":"CVE-2023-53135","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"af_unix: fix struct pid leaks in OOB support","id":"CVE-2023-53136"},"packages":[],"prev":{"headline":"bnxt_en: Avoid order-5 memory allocation for TPA data","id":"CVE-2023-53134"},"products":["Linux"],"published":"2025-05-02","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A stack-out-of-bounds read in the RISC-V kernel unwinder can cause a kernel crash when KASAN is enabled and frame pointers are disabled.","url":"https://insights.sbomify.com/CVE-2023-53135/"}