CVE-2025-68320
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dropbear | dropbear | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's lan966x driver where a sleeping function (mutex lock) is called from an atomic context, which is invalid. Specifically, a mutex is used in a context where sleeping is not allowed, causing a BUG warning. The fix involves replacing the mutex with a spinlock, which is appropriate for atomic contexts.
How can this vulnerability impact me? :
This vulnerability can cause kernel warnings and potentially system instability or crashes when the affected code path is executed, such as when connecting via ssh using dropbear. It may lead to unexpected behavior or degraded system reliability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel logs for the specific warning message: 'BUG: sleeping function called from invalid context at kernel/locking/mutex.c:575'. You can check the kernel log using the command 'dmesg | grep "sleeping function called from invalid context"' or monitor system logs with 'journalctl -k | grep "sleeping function called from invalid context"'. These messages indicate that a mutex is being used in an atomic context, which is incorrect.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this issue is fixed, specifically where the mutex usage in atomic context is replaced with a spinlock as per the fix. Until an update is applied, avoid workloads or operations that trigger the problematic code path, such as certain SSH connections that cause the warning. Monitoring logs for the warning can help identify if the issue is occurring.