{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53282 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-53282 is a medium-severity vulnerability in Linux kernel, published on 26 Jun 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-53282 and fix it if it is affected.\n\nWhat it is: CVE-2026-53282 is a medium-severity vulnerability in Linux kernel, published on 26 Jun 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-53282 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-53282/ (Markdown: https://insights.sbomify.com/CVE-2026-53282/index.md)","id":"CVE-2026-53282","markdown":"https://insights.sbomify.com/CVE-2026-53282/index.md","name":"CVE-2026-53282","record":{"aliases":["BELL-CVE-2026-53282","DEBIAN-CVE-2026-53282","GHSA-865v-r97p-c9pq","UBUNTU-CVE-2026-53282"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A missing stack push in the Linux kernel kexec path causes a fault when purgatory accesses a non-existent return address, leading to a crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nx86/kexec: Push kjump return address even for non-kjump kexec\n\nThe version of purgatory code shipped by kexec-tools attempts to look above\nthe top of its stack to find a return address for a kjump, even in a non-kjump\nkexec.\n\nAfter the commit in Fixes: the word above the stack might not be there,\nleading to a fault (which is at least now caught by my exception-handling code\nin kexec).\n\nThat commit fixed things for the actual kjump path, but no longer\n\"gratuitously\" pushes the unused return address to the stack in the non-kjump\npath. Put that *back* in the non-kjump path, to prevent purgatory from\ncrashing when trying to access it.","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":"x86/kexec: Push kjump return address even for non-kjump kexec","id":"CVE-2026-53282","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"iommu/amd: Bounds-check devid in __rlookup_amd_iommu()","id":"CVE-2026-53283"},"packages":[],"prev":{"headline":"iommu/vt-d: Avoid NULL pointer dereference or refcount corruption","id":"CVE-2026-53281"},"products":["Linux"],"published":"2026-06-26","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-06-26","vendors":["Linux"]},"summary":"A missing stack push in the Linux kernel kexec path causes a fault when purgatory accesses a non-existent return address, leading to a crash.","url":"https://insights.sbomify.com/CVE-2026-53282/"}