Vulnerability · Published Mar 12, 2025 · Assigned by Linux

CVE-2025-21862drop_monitor: fix incorrect initialization order

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 17% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.5Medium
Exploit odds (30 days)0.3%top 83.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: drop_monitor: fix incorrect initialization order Syzkaller reports the following bug: BUG: spinlock bad magic on CPU#1, syz-executor.0/7995 lock: 0xffff88805303f3e0, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0 CPU: 1 PID: 7995 Comm: syz-executor.0 Tainted: G E 5.10.209+ #1 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x119/0x179 lib/dump_stack.c:118 debug_spin_lock_before kernel/locking/spinlock_debug.c:83 [inline] do_raw_spin_lock+0x1f6/0x270 kernel/locking/spinlock_debug.c:112 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:117 [inline] _raw_spin_lock_irqsave+0x50/0x70 kernel/locking/spinlock.c:159 reset_per_cpu_data+0xe6/0x240 [drop_monitor] net_dm_cmd_trace+0x43d/0x17a0 [drop_monitor] genl_family_rcv_msg_doit+0x22f/0x330 net/netlink/genetlink.c:739 genl_family_rcv_msg net/netlink/genetlink.c:783 [inline] genl_rcv_msg+0x341/0x5a0 net/netlink/genetlink.c:800 netlink_rcv_skb+0x14d/0x440 net/netlink/af_netlink.c:2497 genl_rcv+0x29/0x40 net/netlink/genetlink.c:811 netlink_unicast_kernel net/netlink/af_netlink.c:1322 [inline] netlink_unicast+0x54b/0x800 net/netlink/af_netlink.c:1348 netlink_sendmsg+0x914/0xe00 net/netlink/af_netlink.c:1916 sock_sendmsg_nosec net/socket.c:651 [inline] __sock_sendmsg+0x157/0x190 net/socket.c:663 ____sys_sendmsg+0x712/0x870 net/socket.c:2378 ___sys_sendmsg+0xf8/0x170 net/socket.c:2432 __sys_sendmsg+0xea/0x1b0 net/socket.c:2461 do_syscall_64+0x30/0x40 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x62/0xc7 RIP: 0033:0x7f3f9815aee9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f3f972bf0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f3f9826d050 RCX: 00007f3f9815aee9 RDX: 0000000020000000 RSI: 0000000020001300 RDI: 0000000000000007 RBP: 00007f3f981b63bd R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000006e R14: 00007f3f9826d050 R15: 00007ffe01ee6768 If drop_monitor is built as a kernel module, syzkaller may have time to send a netlink NET_DM_CMD_START message during the module loading. This will call the net_dm_monitor_start() function that uses a spinlock that has not yet been initialized. To fix this, let's place resource initialization above the registration of a generic netlink family. Found by InfoTeCS on behalf of Linux Verification Center (linuxtesting.org) with Syzkaller.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.133-1DEBIAN-CVE-2025-21862
Debian:12linux6.1.133-1DSA-5900-1
Debian:13linux6.12.17-1DEBIAN-CVE-2025-21862
Debian:14linux6.12.17-1DEBIAN-CVE-2025-21862
Ubuntu:22.04:LTSlinux5.15.0-140.150UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux6.8.0-78.78UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-aws5.15.0-1084.91UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-aws6.8.0-1035.37UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1035.37~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-azure5.15.0-1089.98UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-azure6.8.0-1034.39UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1015.15~24.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1034.39~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1089.98.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-azure-nvidia6.8.0-1022.23UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-gcp5.15.0-1083.92UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-gcp6.8.0-1036.38UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1015.15~24.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1036.38~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-gke5.15.0-1081.87UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-gke6.8.0-1032.36UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1066.74UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1019.21UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-hwe-6.116.11.0-26.26~24.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-78.78~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-ibm5.15.0-1076.79UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-ibm6.8.0-1033.33UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1033.33~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1079.85UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-kvm5.15.0-1080.85UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-140.150UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-78.78.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.116.11.0-1014.15~24.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-78.78.1~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1078.79UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1035.38UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1010.10UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1035.38~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1035.38.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1037.37UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1009.9UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1026.26UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1022.22UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-oracle5.15.0-1081.87UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-oracle6.8.0-1032.33UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1032.33~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-raspi5.15.0-1078.81UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-raspi6.8.0-1035.39UBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-78.78~22.04.1UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-21862
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1017.18UBUNTU-CVE-2025-21862
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1050.54UBUNTU-CVE-2025-21862

Affected products (as reported)

VendorProductVersions
Linux Linux 9a8afc8d3962f3ed26fd6b56db34133860ed1e72 – before 6e9e0f224ffd8b819da3ea247dda404795fdd1829a8afc8d3962f3ed26fd6b56db34133860ed1e72 – before 29f9cdcab3d96d5207a5c92b52c40ad75e5915d89a8afc8d3962f3ed26fd6b56db34133860ed1e72 – before 872c7c7e57a746046796ddfead529c9d37b9f6b49a8afc8d3962f3ed26fd6b56db34133860ed1e72 – before fcfc00bfec7bb6661074cb21356d05a4c9470a3c9a8afc8d3962f3ed26fd6b56db34133860ed1e72 – before 0efa6c42f81c60d8f72ba7f5ed8d4fec8c5262829a8afc8d3962f3ed26fd6b56db34133860ed1e72 – before b7859e8643e75619b2705b4fcac93ffd94d72b4a9a8afc8d3962f3ed26fd6b56db34133860ed1e72 – before 219a47d0e6195bd202f22855e35f25bd15bc4d589a8afc8d3962f3ed26fd6b56db34133860ed1e72 – before 07b598c0e6f06a0f254c88dafb4ad50f8a8c6eea
Linux Linux 2.6.30

Weakness: CWE-908 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

References