Skip to main content
CVE-2025-68192VulnerabilityPublished Updated

CVE-2025-68192: Linux kernel · net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup Raw IP

Source GCVE Database

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel by initializing the MAC header offset in the qmimux_rx_fixup function. Users should apply the official kernel updates that include this fix. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply them accordingly.

Description

A critical vulnerability in the Linux kernel's net: usb: qmi_wwan component was resolved by initializing the MAC header offset in qmimux_rx_fixup. Raw IP packets previously left the MAC header uninitialized, which could cause kernel panics on ARM64 and ARM architectures when subsystems like xfrm accessed this offset due to strict alignment checks. This issue specifically affected IPsec operations over the qmimux0 interface and could lead to system crashes.

References

Community reviews

Loading reviews…