{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68322 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68322 is a denial of service vulnerability in Linux, published on 16 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2025-68322 and fix it if it is affected.\n\nWhat it is: CVE-2025-68322 is a denial of service vulnerability in Linux, published on 16 Dec 2025. \nExploitation: There is no known exploitation of CVE-2025-68322 in the wild and no public exploit code.\n\nAffected product: Linux. 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-2025-68322/ (Markdown: https://insights.sbomify.com/CVE-2025-68322/index.md)","id":"CVE-2025-68322","markdown":"https://insights.sbomify.com/CVE-2025-68322/index.md","name":"CVE-2025-68322","record":{"aliases":["BELL-CVE-2025-68322","DEBIAN-CVE-2025-68322","GHSA-5cpg-hfmf-h5fh","ROOT-OS-DEBIAN-11-CVE-2025-68322","ROOT-OS-DEBIAN-12-CVE-2025-68322","ROOT-OS-DEBIAN-13-CVE-2025-68322","ROOT-OS-UBUNTU-2204-CVE-2025-68322","ROOT-OS-UBUNTU-2404-CVE-2025-68322","UBUNTU-CVE-2025-68322"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A local attacker can cause a kernel deadlock and system crash on PA-RISC architectures by triggering unaligned memory access in the stack unwinder.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nparisc: Avoid crash due to unaligned access in unwinder\n\nGuenter Roeck reported this kernel crash on his emulated B160L machine:\n\nStarting network: udhcpc: started, v1.36.1\n Backtrace:\n  [\u003c104320d4\u003e] unwind_once+0x1c/0x5c\n  [\u003c10434a00\u003e] walk_stackframe.isra.0+0x74/0xb8\n  [\u003c10434a6c\u003e] arch_stack_walk+0x28/0x38\n  [\u003c104e5efc\u003e] stack_trace_save+0x48/0x5c\n  [\u003c105d1bdc\u003e] set_track_prepare+0x44/0x6c\n  [\u003c105d9c80\u003e] ___slab_alloc+0xfc4/0x1024\n  [\u003c105d9d38\u003e] __slab_alloc.isra.0+0x58/0x90\n  [\u003c105dc80c\u003e] kmem_cache_alloc_noprof+0x2ac/0x4a0\n  [\u003c105b8e54\u003e] __anon_vma_prepare+0x60/0x280\n  [\u003c105a823c\u003e] __vmf_anon_prepare+0x68/0x94\n  [\u003c105a8b34\u003e] do_wp_page+0x8cc/0xf10\n  [\u003c105aad88\u003e] handle_mm_fault+0x6c0/0xf08\n  [\u003c10425568\u003e] do_page_fault+0x110/0x440\n  [\u003c10427938\u003e] handle_interruption+0x184/0x748\n  [\u003c11178398\u003e] schedule+0x4c/0x190\n  BUG: spinlock recursion on CPU#0, ifconfig/2420\n  lock: terminate_lock.2+0x0/0x1c, .magic: dead4ead, .owner: ifconfig/2420, .owner_cpu: 0\n\nWhile creating the stack trace, the unwinder uses the stack pointer to guess\nthe previous frame to read the previous stack pointer from memory.  The crash\nhappens, because the unwinder tries to read from unaligned memory and as such\ntriggers the unalignment trap handler which then leads to the spinlock\nrecursion and finally to a deadlock.\n\nFix it by checking the alignment before accessing the memory.","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":"parisc: Avoid crash due to unaligned access in unwinder","id":"CVE-2025-68322","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"usb: typec: ucsi: fix use-after-free caused by uec-\u003ework","id":"CVE-2025-68323"},"packages":[],"prev":{"headline":"page_pool: always add GFP_NOWARN for ATOMIC allocations","id":"CVE-2025-68321"},"products":["Linux"],"published":"2025-12-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can cause a kernel deadlock and system crash on PA-RISC architectures by triggering unaligned memory access in the stack unwinder.","url":"https://insights.sbomify.com/CVE-2025-68322/"}