SECUFOCUSNOW
Home›CVE index›CVE-2025-68192
Review reviewCritical

CVE-2025-68192

Linux

In the Linux kernel, the following vulnerability has been resolved: net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup Raw IP packets have no MAC header, leaving skb->mac_header uninitialized. This can trigger kernel panics on ARM64 when xfrm or other subsystems access the offset due to strict alignment checks. Initialize the MAC header to prevent such crashes. This can trigger kernel panics on ARM when running IPsec over the qmimux0 interface. Example trace: Internal error: Oops: 000000009600004f [#1] SMP CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb4...

CVSS
9.8
EPSS
0.55%
42.8% percentile
CISA KEV
Not listed
Published
2025.12.16
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.55%
Technical severityCVSS 9.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup Raw IP packets have no MAC header, leaving skb->mac_header uninitialized. This can trigger kernel panics on ARM64 when xfrm or other subsystems access the offset due to strict alignment checks. Initialize the MAC header to prevent such crashes. This can trigger kernel panics on ARM when running IPsec over the qmimux0 interface. Example trace: Internal error: Oops: 000000009600004f [#1] SMP CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb4...

Affected product and versions

Product
Linux
Affected versions
>= c6adf77953bcec0ad63d7782479452464e50f7a3 < d693c47fb902b988f5752182e4f7fbde5e6dcaf9, >= c6adf77953bcec0ad63d7782479452464e50f7a3 < 0aabccdcec1f4a36f95829ea2263f845bbc77223, >= c6adf77953bcec0ad63d7782479452464e50f7a3 < 4e6b9004f01d0fef5b19778399bc5bf55f8c2d71, >= c6adf77953bcec0ad63d7782479452464e50f7a3 < bf527b80b80a282ab5bf1540546211fc35e5cd42, >= c6adf77953bcec0ad63d7782479452464e50f7a3 < dd03780c29f87c26c0e0bb7e0db528c8109461fb, >= c6adf77953bcec0ad63d7782479452464e50f7a3 < ae811175cea35b03ac6d7c910f43a82a43b9c3b3, >= c6adf77953bcec0ad63d7782479452464e50f7a3 < 8ab3b8f958d861a7f725a5be60769106509fbd69, >= c6adf77953bcec0ad63d7782479452464e50f7a3 < e120f46768d98151ece8756ebd688b0e43dc8b29, >= 4.12
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
Not available