CVE-2025-68322
- Published: 2025-12-16T16:16:11.793
In the Linux kernel, the following vulnerability has been resolved:
parisc: Avoid crash due to unaligned access in unwinder
Guenter Roeck reported this kernel crash on his emulated B160L machine:
Starting network: udhcpc: started, v1.36.1
Backtrace:
[] unwind_once+0x1c/0x5c
[] walk_stackframe.isra.0+0x74/0xb8
[] arch_stack_walk+0x28/0x38
[] stack_trace_save+0x48/0x5c
[] set_track_prepare+0x44/0x6c
[] ___slab_alloc+0xfc4/0x1024
[] __slab_alloc.isra.0+0x58/0x90
[] kmem_cache_alloc_noprof+0x2ac/0x4a0
[] __anon_vma_prepare+0x60/0x280
[] __vmf_anon_prepare+0x68/0x94
[] do_wp_page+0x8cc/0xf10
[] handle_mm_fault+0x6c0/0xf08
[] do_page_fault+0x110/0x440
[] handle_interruption+0x184/0x748
[] schedule+0x4c/0x190
BUG: spinlock recursion on CPU#0, ifconfig/2420
lock: terminate_lock.2+0x0/0x1c, .magic: dead4ead, .owner: ifconfig/2420, .owner_cpu: 0
While creating the stack trace, the unwinder uses the stack pointer to guess
the previous frame to read the previous stack pointer from memory. The crash
happens, because the unwinder tries to read from unaligned memory and as such
triggers the unalignment trap handler which then leads to the spinlock
recursion and finally to a deadlock.
Fix it by checking the alignment before accessing the memory.
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
No vendor taxonomy on this entry.
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2025-68322
Description: In the Linux kernel, the following vulnerability has been resolved: parisc: Avoid crash due to unaligned access in unwinder Guenter Roeck reported this kernel crash on his emulated B160L machine: Starting network: udhcpc: started, v1.36.1 Backtrace: [] unwind_once+0x1c/0x5c [] walk_stackframe.isra.0+0x74/0xb8 [] arch_stack_walk+0x28/0x38 [] stack_trace_save+0x48/0x5c [] set_track_prepare+0x44/0x6c [] ___slab_alloc+0xfc4/0x1024 [] __slab_alloc.isra.0+0x58/0x90 [] kmem_cache_alloc_noprof+0x2ac/0x4a0 [] __anon_vma_prepare+0x60/0x280 [] […]
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
- Check if you're running the affected product
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Exploit Difficulty Assessment
Vulnerability Timeline
CVE details first published to NVD database
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
No vendor/product data available.