linux-cve-announce - CVE-2025-68192: net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025121635-CVE-2025-68192-4491@gregkh>
Date: Tue, 16 Dec 2025 14:43:53 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68192: net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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-gbe78e49cb433 #1
    Hardware name: LS1028A RDB Board (DT)
    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    pc : xfrm_input+0xde8/0x1318
    lr : xfrm_input+0x61c/0x1318
    sp : ffff800080003b20
    Call trace:
     xfrm_input+0xde8/0x1318
     xfrm6_rcv+0x38/0x44
     xfrm6_esp_rcv+0x48/0xa8
     ip6_protocol_deliver_rcu+0x94/0x4b0
     ip6_input_finish+0x44/0x70
     ip6_input+0x44/0xc0
     ipv6_rcv+0x6c/0x114
     __netif_receive_skb_one_core+0x5c/0x8c
     __netif_receive_skb+0x18/0x60
     process_backlog+0x78/0x17c
     __napi_poll+0x38/0x180
     net_rx_action+0x168/0x2f0

The Linux kernel CVE team has assigned CVE-2025-68192 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.12 with commit c6adf77953bcec0ad63d7782479452464e50f7a3 and fixed in 5.4.302 with commit d693c47fb902b988f5752182e4f7fbde5e6dcaf9
	Issue introduced in 4.12 with commit c6adf77953bcec0ad63d7782479452464e50f7a3 and fixed in 5.10.247 with commit 0aabccdcec1f4a36f95829ea2263f845bbc77223
	Issue introduced in 4.12 with commit c6adf77953bcec0ad63d7782479452464e50f7a3 and fixed in 5.15.197 with commit 4e6b9004f01d0fef5b19778399bc5bf55f8c2d71
	Issue introduced in 4.12 with commit c6adf77953bcec0ad63d7782479452464e50f7a3 and fixed in 6.1.159 with commit bf527b80b80a282ab5bf1540546211fc35e5cd42
	Issue introduced in 4.12 with commit c6adf77953bcec0ad63d7782479452464e50f7a3 and fixed in 6.6.117 with commit dd03780c29f87c26c0e0bb7e0db528c8109461fb
	Issue introduced in 4.12 with commit c6adf77953bcec0ad63d7782479452464e50f7a3 and fixed in 6.12.58 with commit ae811175cea35b03ac6d7c910f43a82a43b9c3b3
	Issue introduced in 4.12 with commit c6adf77953bcec0ad63d7782479452464e50f7a3 and fixed in 6.17.8 with commit 8ab3b8f958d861a7f725a5be60769106509fbd69
	Issue introduced in 4.12 with commit c6adf77953bcec0ad63d7782479452464e50f7a3 and fixed in 6.18 with commit e120f46768d98151ece8756ebd688b0e43dc8b29

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-68192
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/net/usb/qmi_wwan.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/d693c47fb902b988f5752182e4f7fbde5e6dcaf9
	https://git.kernel.org/stable/c/0aabccdcec1f4a36f95829ea2263f845bbc77223
	https://git.kernel.org/stable/c/4e6b9004f01d0fef5b19778399bc5bf55f8c2d71
	https://git.kernel.org/stable/c/bf527b80b80a282ab5bf1540546211fc35e5cd42
	https://git.kernel.org/stable/c/dd03780c29f87c26c0e0bb7e0db528c8109461fb
	https://git.kernel.org/stable/c/ae811175cea35b03ac6d7c910f43a82a43b9c3b3
	https://git.kernel.org/stable/c/8ab3b8f958d861a7f725a5be60769106509fbd69
	https://git.kernel.org/stable/c/e120f46768d98151ece8756ebd688b0e43dc8b29