{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64252 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64252 is a medium-severity memory corruption vulnerability in Linux kernel, published on 24 Jul 2026. 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-2026-64252 and fix it if it is affected.\n\nWhat it is: CVE-2026-64252 is a medium-severity memory corruption vulnerability in Linux kernel, published on 24 Jul 2026. 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-2026-64252 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-2026-64252/ (Markdown: https://insights.sbomify.com/CVE-2026-64252/index.md)","id":"CVE-2026-64252","markdown":"https://insights.sbomify.com/CVE-2026-64252/index.md","name":"CVE-2026-64252","record":{"aliases":["BELL-CVE-2026-64252","DEBIAN-CVE-2026-64252","GHSA-4gm6-q4p9-46cj","ROOT-OS-UBUNTU-2204-CVE-2026-64252","UBUNTU-CVE-2026-64252"],"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 memory corruption issue in the Linux kernel MIPS DEC console handler can cause a kernel crash when running in 64-bit configurations.","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":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nMIPS: DEC: Prevent initial console buffer from landing in XKPHYS\n\nIn 64-bit configurations calling the initial console output handler from\na kernel thread other than the initial one will result in a situation\nwhere the stack has been placed in the XKPHYS 64-bit memory segment and\nconsequently so has been the buffer allocated there that is used as the\nargument corresponding to the `%s' output conversion specifier for the\nfirmware's printf() entry point.\n\nThis 64-bit address will then be truncated by 32-bit firmware, resulting\nin an attempt to access the wrong memory location, which in turn will\ncause all kinds of unpredictable behaviour, such as a kernel crash:\n\n  Console: colour dummy device 160x64\n  Calibrating delay loop... 49.36 BogoMIPS (lpj=192512)\n  pid_max: default: 32768 minimum: 301\n  CPU 0 Unable to handle kernel paging request at virtual address 000000000203bd00, epc == ffffffffbfc08364, ra == ffffffffbfc08800\n  Oops[#1]:\n  CPU: 0 PID: 0 Comm: swapper Not tainted 5.18.0-rc2-00254-gfb649bda6f56-dirty #121\n  $ 0   : 0000000000000000 0000000000000001 0000000000000023 ffffffff80684ba0\n  $ 4   : 000000000203bd00 ffffffffbfc0f3b4 ffffffffffffffff 0000000000000073\n  $ 8   : 0a303d7469000000 0000000000000000 0000000000000073 ffffffffbfc0f473\n  $12   : 0000000000000002 0000000000000000 ffffffff80684c1c 0000000000000000\n  $16   : 0000000000000000 ffffffff80596dc9 0000000000000000 ffffffffbfc09240\n  $20   : ffffffff80684c40 ffffffffbfc0f400 000000000000002d 000000000000002b\n  $24   : ffffffffffffffbf 000000000203bd00\n  $28   : ffffffff805f0000 ffffffff80684b58 0000000000000030 ffffffffbfc08800\n  Hi    : 0000000000000000\n  Lo    : 0000000000000aa8\n  epc   : ffffffffbfc08364 0xffffffffbfc08364\n  ra    : ffffffffbfc08800 0xffffffffbfc08800\n  Status: 140120e2        KX SX UX KERNEL EXL\n  Cause : 00000008 (ExcCode 02)\n  BadVA : 000000000203bd00\n  PrId  : 00000430 (R4000SC)\n  Modules linked in:\n  Process swapper (pid: 0, threadinfo=(____ptrval____), task=(____ptrval____), tls=0000000000000000)\n  Stack : 0000000000000000 0000000000000000 0000000000000000 0000004d0000004d\n          80684cc0806a2a40 80596dc80000004d 8061000000000000 bfc0850c80684c38\n          0000000000000000 000000000203bd00 0000000000000000 0000000000000000\n          0000000000000000 00000000bfc0f3b4 0000000000000000 0000000000000000\n          0000000000000000 0000000000000000 0000000000000000 0000000000000000\n          0000000000000000 0000000000000000 0000000000000000 0000000000000000\n          0000002500000000 0000000000000000 0000000000000000 802c1a7400000000\n          0203bd0080596dc8 0203bd4d69000000 6c61632000000018 5f746567646e6172\n          6c616320625f6d6f 5f736e5f6d6f7266 206361323778302b 303d74696e726320\n          806a0a38806b0000 806a0a38806b0000 00000000806b0000 80683c58806b0000\n          ...\n  Call Trace:\n\n  Code: a082ffff  03e00008  00601021 \u003c80820000\u003e 00001821  10400005  24840001  80820000  24630001\n\n  ---[ end trace 0000000000000000 ]---\n  Kernel panic - not syncing: Fatal exception in interrupt\n\n  KN04 V2.1k    (PC: 0xa0026768, SP: 0x806848e8)\n  \u003e\u003e\n\nIn this case the pointer in $4 was truncated from 0x980000000203bd00 to\n0x000000000203bd00.\n\nThis may happen when no final console driver has been enabled in the\nconfiguration and consequently the initial console continues being used\nlate into bootstrap or with an upcoming change that will switch the zs\ndriver to use a platform device, which in turn will make the console\nhandover happen only after other kernel threads have already been\nstarted.\n\nFix the issue by making the buffer static and initdata, and therefore\nplaced in the CKSEG0 32-bit compatibility segment, observing that the\nconsole output handler is called with the console lock held, implying\nno need for this code to be reentrant.  Add an assertion to verify the\nbuffer actually has been placed in a compatibility segment.","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":"MIPS: DEC: Prevent initial console buffer from landing in XKPHYS","id":"CVE-2026-64252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"kernel/fork: clear PF_BLOCK_TS in copy_process()","id":"CVE-2026-64253"},"packages":[],"prev":{"headline":"pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()","id":"CVE-2026-64251"},"products":["Linux"],"published":"2026-07-24","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A memory corruption issue in the Linux kernel MIPS DEC console handler can cause a kernel crash when running in 64-bit configurations.","url":"https://insights.sbomify.com/CVE-2026-64252/"}