CVE-2025-68192
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 |
|---|---|---|
| linux | linux_kernel | 6.12.34 |
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 usb qmi_wwan driver where raw IP packets lack a MAC header, leaving the mac_header field uninitialized. This uninitialized field can cause kernel panics on ARM64 and ARM architectures when subsystems like xfrm access it due to strict alignment checks. The issue is fixed by initializing the MAC header offset to prevent such crashes.
How can this vulnerability impact me? :
The vulnerability can cause kernel panics on ARM64 and ARM systems when running IPsec over the qmimux0 interface. This can lead to system crashes and instability, potentially disrupting network communications and services relying on the affected Linux kernel.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be done by monitoring for kernel panic logs related to the xfrm subsystem or IPsec over the qmimux0 interface, especially on ARM64 architectures. Look for kernel messages containing 'Oops' errors or call traces involving xfrm_input, ip6_input, or qmimux0. Commands such as 'dmesg | grep -i oops' or 'journalctl -k | grep -i qmimux0' may help identify these crashes.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the MAC header offset initialization in qmimux_rx_fixup is applied, which prevents uninitialized MAC headers and kernel panics. If updating is not immediately possible, avoid using IPsec over the qmimux0 interface on affected ARM64 systems until a patch is applied.