| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-22032: wifi: mt76: mt7921: fix kernel panic due to null pointer dereference |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| wifi: mt76: mt7921: fix kernel panic due to null pointer dereference |
| |
| Address a kernel panic caused by a null pointer dereference in the |
| `mt792x_rx_get_wcid` function. The issue arises because the `deflink` structure |
| is not properly initialized with the `sta` context. This patch ensures that the |
| `deflink` structure is correctly linked to the `sta` context, preventing the |
| null pointer dereference. |
| |
| BUG: kernel NULL pointer dereference, address: 0000000000000400 |
| #PF: supervisor read access in kernel mode |
| #PF: error_code(0x0000) - not-present page |
| PGD 0 P4D 0 |
| Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI |
| CPU: 0 UID: 0 PID: 470 Comm: mt76-usb-rx phy Not tainted 6.12.13-gentoo-dist #1 |
| Hardware name: /AMD HUDSON-M1, BIOS 4.6.4 11/15/2011 |
| RIP: 0010:mt792x_rx_get_wcid+0x48/0x140 [mt792x_lib] |
| RSP: 0018:ffffa147c055fd98 EFLAGS: 00010202 |
| RAX: 0000000000000000 RBX: ffff8e9ecb652000 RCX: 0000000000000000 |
| RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8e9ecb652000 |
| RBP: 0000000000000685 R08: ffff8e9ec6570000 R09: 0000000000000000 |
| R10: ffff8e9ecd2ca000 R11: ffff8e9f22a217c0 R12: 0000000038010119 |
| R13: 0000000080843801 R14: ffff8e9ec6570000 R15: ffff8e9ecb652000 |
| FS: 0000000000000000(0000) GS:ffff8e9f22a00000(0000) knlGS:0000000000000000 |
| CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 |
| CR2: 0000000000000400 CR3: 000000000d2ea000 CR4: 00000000000006f0 |
| Call Trace: |
| <TASK> |
| ? __die_body.cold+0x19/0x27 |
| ? page_fault_oops+0x15a/0x2f0 |
| ? search_module_extables+0x19/0x60 |
| ? search_bpf_extables+0x5f/0x80 |
| ? exc_page_fault+0x7e/0x180 |
| ? asm_exc_page_fault+0x26/0x30 |
| ? mt792x_rx_get_wcid+0x48/0x140 [mt792x_lib] |
| mt7921_queue_rx_skb+0x1c6/0xaa0 [mt7921_common] |
| mt76u_alloc_queues+0x784/0x810 [mt76_usb] |
| ? __pfx___mt76_worker_fn+0x10/0x10 [mt76] |
| __mt76_worker_fn+0x4f/0x80 [mt76] |
| kthread+0xd2/0x100 |
| ? __pfx_kthread+0x10/0x10 |
| ret_from_fork+0x34/0x50 |
| ? __pfx_kthread+0x10/0x10 |
| ret_from_fork_asm+0x1a/0x30 |
| </TASK> |
| ---[ end trace 0000000000000000 ]--- |
| |
| The Linux kernel CVE team has assigned CVE-2025-22032 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.12.13 with commit 3fe7acc6f4b42ccb1056c5847f18f8eb2fec0834 and fixed in 6.12.23 with commit 0cfea60966e4b1239d20bebf02258295e189e82a |
| Issue introduced in 6.13.2 with commit c9e40880416791287292046917e84bcb3a17e2d2 and fixed in 6.13.11 with commit effec50381991bc067acf4b3351a57831c74d27f |
| Issue introduced in 6.14 with commit 90c10286b176421068b136da51ed83059a68e322 and fixed in 6.14.2 with commit 5a57f8eb2a17d469d65cd1186cea26b798221d4a |
| Issue introduced in 6.14 with commit 90c10286b176421068b136da51ed83059a68e322 and fixed in 6.15 with commit adc3fd2a2277b7cc0b61692463771bf9bd298036 |
| |
| 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-22032 |
| 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/wireless/mediatek/mt76/mt7921/main.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/0cfea60966e4b1239d20bebf02258295e189e82a |
| https://git.kernel.org/stable/c/effec50381991bc067acf4b3351a57831c74d27f |
| https://git.kernel.org/stable/c/5a57f8eb2a17d469d65cd1186cea26b798221d4a |
| https://git.kernel.org/stable/c/adc3fd2a2277b7cc0b61692463771bf9bd298036 |
