🛡️ CVE-2025-23163 on Ubuntu — linux
Description
In the Linux kernel, the following vulnerability has been resolved: net: vlan: don't propagate flags on open With the device instance lock, there is now a possibility of a deadlock: [ 1.211455] ============================================ [ 1.211571] WARNING: possible recursive locking detected [ 1.211687] 6.14.0-rc5-01215-g032756b4ca7a-dirty #5 Not tainted [ 1.211823] -------------------------------------------- [ 1.211936] ip/184 is trying to acquire lock: [ 1.212032] ffff8881024a4c30 (&dev->lock){+.+.}-{4:4}, at: dev_set_allmulti+0x4e/0xb0 [ 1.212207] [ 1.212207] but task is already holding lock: [ 1.212332] ffff8881024a4c30 (&dev->lock){+.+.}-{4:4}, at: dev_open+0x50/0xb0 [ 1.212487] [ 1.212487] other info that might help us debug this: [ 1.212626] Possible unsafe locking scenario: [ 1.212626] [ 1.212751] CPU0 [ 1.212815] ---- [ 1.212871] lock(&dev->lock); [ 1.212944] lock(&dev->lock); [ 1.213016] [ 1.213016] *** DEADLOCK *** [ 1.213016] [ 1.213143] May be due to missing lock nesting notation [ 1.213143] [ 1.213294] 3 locks held by ip/184: [ 1.213371] #0: ffffffff838b53e0 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock+0x1b/0xa0 [ 1.213543] #1: ffffffff84e5fc70 (&net->rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock+0x37/0xa0 [ 1.213727] #2: ffff8881024a4c30 (&dev->lock){+.+.}-{4:4}, at: dev_open+0x50/0xb0 [ 1.213895] [ 1.213895] stack backtrace: [ 1.213991] CPU: 0 UID: 0 PID: 184 Comm: ip Not tainted 6.14.0-rc5-01215-g032756b4ca7a-dirty #5 [ 1.213993] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 [ 1.213994] Call Trace: [ 1.213995] [ 1.213996] dump_stack_lvl+0x8e/0xd0 [ 1.214000] print_deadlock_bug+0x28b/0x2a0 [ 1.214020] lock_acquire+0xea/0x2a0 [ 1.214027] __mutex_lock+0xbf/0xd40 [ 1.214038] dev_set_allmulti+0x4e/0xb0 # real_dev->flags & IFF_ALLMULTI [ 1.214040] vlan_dev_open+0xa5/0x170 # ndo_open on vlandev [ 1.214042] __dev_open+0x145/0x270 [ 1.214046] __dev_change_flags+0xb0/0x1e0 [ 1.214051] netif_change_flags+0x22/0x60 # IFF_UP vlandev [ 1.214053] dev_change_flags+0x61/0xb0 # for each device in group from dev->vlan_info [ 1.214055] vlan_device_event+0x766/0x7c0 # on netdevsim0 [ 1.214058] notifier_call_chain+0x78/0x120 [ 1.214062] netif_open+0x6d/0x90 [ 1.214064] dev_open+0x5b/0xb0 # locks netdevsim0 [ 1.214066] bond_enslave+0x64c/0x1230 [ 1.214075] do_set_master+0x175/0x1e0 # on netdevsim0 [ 1.214077] do_setlink+0x516/0x13b0 [ 1.214094] rtnl_newlink+0xaba/0xb80 [ 1.214132] rtnetlink_rcv_msg+0x440/0x490 [ 1.214144] netlink_rcv_skb+0xeb/0x120 [ 1.214150] netlink_unicast+0x1f9/0x320 [ 1.214153] netlink_sendmsg+0x346/0x3f0 [ 1.214157] __sock_sendmsg+0x86/0xb0 [ 1.214160] ____sys_sendmsg+0x1c8/0x220 [ 1.214164] ___sys_sendmsg+0x28f/0x2d0 [ 1.214179] __x64_sys_sendmsg+0xef/0x140 [ 1.214184] do_syscall_64+0xec/0x1d0 [ 1.214190] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 1.214191] RIP: 0033:0x7f2d1b4a7e56 Device setup: netdevsim0 (down) ^ ^ bond netdevsim1.100@netdevsim1 allmulticast=on (down) When we enslave the lower device (netdevsim0) which has a vlan, we propagate vlan's allmuti/promisc flags during ndo_open. This causes (re)locking on of the real_dev. Propagate allmulti/promisc on flags change, not on the open. There is a slight semantics change that vlans that are down now propagate the flags, but this seems unlikely to result in the real issues. Reproducer: echo 0 1 > /sys/bus/netdevsim/new_device dev_path=$(ls -d /sys/bus/netdevsim/devices/netdevsim0/net/*) dev=$(echo $dev_path | rev | cut -d/ -f1 | rev) ip link set dev $dev name netdevsim0 ip link set dev netdevsim0 up ip link add link netdevsim0 name netdevsim0.100 type vlan id 100 ip link set dev netdevsim0.100 allm ---truncated---
Distribution advisory
This page covers CVE-2025-23163 as tracked by Ubuntu, for the package linux. The fix is available in version 6.8.0-100.100; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
Affected software and timeline
Affected software: linux (fixed in 6.8.0-100.100), linux-allwinner-5.19, linux-aws (fixed in 6.8.0-1046.49), linux-aws-5.0, linux-aws-5.11, linux-aws-5.13, linux-aws-5.15 (fixed in 5.15.0-1088.95~20.04.1), linux-aws-5.19, linux-aws-5.3, linux-aws-5.4, linux-aws-5.8, linux-aws-6.2, linux-aws-6.5, linux-aws-6.8 (fixed in 6.8.0-1046.49~22.04.1), linux-aws-fips (fixed in 6.8.0-1046.49+fips1), linux-aws-hwe, linux-azure (fixed in 6.8.0-1046.52), linux-azure-4.15, linux-azure-5.11, linux-azure-5.13, linux-azure-5.15 (fixed in 5.15.0-1094.103~20.04.1), linux-azure-5.19, linux-azure-5.3, linux-azure-5.4, linux-azure-5.8, linux-azure-6.11, linux-azure-6.2, linux-azure-6.5, linux-azure-6.8 (fixed in 6.8.0-1051.57~22.04.1), linux-azure-edge, linux-azure-fde, linux-azure-fde-5.15 (fixed in 5.15.0-1114.123~20.04.1), linux-azure-fde-5.19, linux-azure-fde-6.17, linux-azure-fde-6.2, linux-azure-fde-6.8, linux-azure-fips (fixed in 6.8.0-1046.52+fips1), linux-azure-nvidia, linux-bluefield, linux-fips (fixed in 6.8.0-100.100+fips1), linux-gcp (fixed in 6.8.0-1047.50), linux-gcp-4.15, linux-gcp-5.11, linux-gcp-5.13, linux-gcp-5.15 (fixed in 5.15.0-1087.96~20.04.2), linux-gcp-5.19, linux-gcp-5.3, linux-gcp-5.4, linux-gcp-5.8, linux-gcp-6.11, linux-gcp-6.2, linux-gcp-6.5, linux-gcp-6.8 (fixed in 6.8.0-1047.50~22.04.2), linux-gcp-fips (fixed in 6.8.0-1047.50+fips1), linux-gke (fixed in 6.8.0-1043.48), linux-gke-4.15, linux-gke-5.15, linux-gke-5.4, linux-gkeop (fixed in 6.8.0-1030.33), linux-gkeop-5.15, linux-gkeop-5.4, linux-hwe, linux-hwe-5.11, linux-hwe-5.13, linux-hwe-5.15 (fixed in 5.15.0-144.157~20.04.1), linux-hwe-5.19, linux-hwe-5.4, linux-hwe-5.8, linux-hwe-6.11, linux-hwe-6.2, linux-hwe-6.5, linux-hwe-6.8 (fixed in 6.8.0-100.100~22.04.1), linux-hwe-edge, linux-ibm (fixed in 6.8.0-1044.44), linux-ibm-5.15 (fixed in 5.15.0-1080.83~20.04.1), linux-ibm-5.4, linux-ibm-6.8 (fixed in 6.8.0-1044.44~22.04.1), linux-intel, linux-intel-5.13, linux-intel-iot-realtime (fixed in 5.15.0-1081.83), linux-intel-iotg (fixed in 5.15.0-1083.89), linux-intel-iotg-5.15 (fixed in 5.15.0-1083.89~20.04.1), linux-iot, linux-kvm (fixed in 5.15.0-1084.89), linux-lowlatency (fixed in 6.8.0-100.100.1), linux-lowlatency-hwe-5.15 (fixed in 5.15.0-144.157~20.04.1), linux-lowlatency-hwe-5.19, linux-lowlatency-hwe-6.11, linux-lowlatency-hwe-6.2, linux-lowlatency-hwe-6.5, linux-lowlatency-hwe-6.8 (fixed in 6.8.0-100.100.1~22.04.1), linux-lts-xenial, linux-nvidia (fixed in 6.8.0-1046.49), linux-nvidia-6.11, linux-nvidia-6.2, linux-nvidia-6.5, linux-nvidia-6.8 (fixed in 6.8.0-1046.49~22.04.1), linux-nvidia-lowlatency (fixed in 6.8.0-1046.49.1), linux-nvidia-tegra (fixed in 6.8.0-1020.20), linux-nvidia-tegra-5.15 (fixed in 5.15.0-1041.41~20.04.1), linux-nvidia-tegra-igx (fixed in 5.15.0-1030.30), linux-oem, linux-oem-5.10, linux-oem-5.13, linux-oem-5.14, linux-oem-5.17, linux-oem-5.6, linux-oem-6.0, linux-oem-6.1, linux-oem-6.11, linux-oem-6.5, linux-oem-6.8, linux-oracle (fixed in 6.8.0-1043.44), linux-oracle-5.0, linux-oracle-5.11, linux-oracle-5.13, linux-oracle-5.15 (fixed in 5.15.0-1085.91~20.04.3), linux-oracle-5.3, linux-oracle-5.4, linux-oracle-5.8, linux-oracle-6.5, linux-oracle-6.8 (fixed in 6.8.0-1043.44~22.04.1), linux-raspi (fixed in 6.8.0-1047.51), linux-raspi-5.4, linux-raspi-realtime (fixed in 6.8.0-2037.38), linux-raspi2, linux-realtime (fixed in 6.8.1-1041.42), linux-realtime-6.8 (fixed in 6.8.1-1041.42~22.04.1), linux-riscv, linux-riscv-5.11, linux-riscv-5.15 (fixed in 5.15.0-1083.87~20.04.1), linux-riscv-5.19, linux-riscv-5.8, linux-riscv-6.5, linux-riscv-6.8 (fixed in 6.8.0-100.100~22.04.1), linux-starfive-5.19, linux-starfive-6.2, linux-starfive-6.5, linux-xilinx (fixed in 6.8.0-1023.24) and linux-xilinx-zynqmp (fixed in 5.15.0-1052.56). Published on 1 May 2025 and last revised on 11 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
ubuntu.com (Report)
www.cve.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
CVE-2025-23163 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 6.8.0-100.100 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 6.8.0-1046.49 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1088.95~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | — |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-6.8 | — | 6.8.0-1046.49~22.04.1 |
| linux-aws-fips | — | 6.8.0-1046.49+fips1 |
| linux-aws-hwe | — | — |
| linux-azure | — | 6.8.0-1046.52 |
| linux-azure-4.15 | — | — |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1094.103~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | — |
| linux-azure-5.8 | — | — |
| linux-azure-6.11 | — | — |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-6.8 | — | 6.8.0-1051.57~22.04.1 |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.15 | — | 5.15.0-1114.123~20.04.1 |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.17 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fde-6.8 | — | — |
| linux-azure-fips | — | 6.8.0-1046.52+fips1 |
| linux-azure-nvidia | — | — |
| linux-bluefield | — | — |
| linux-fips | — | 6.8.0-100.100+fips1 |
| linux-gcp | — | 6.8.0-1047.50 |
| linux-gcp-4.15 | — | — |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1087.96~20.04.2 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | — |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.11 | — | — |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gcp-6.8 | — | 6.8.0-1047.50~22.04.2 |
| linux-gcp-fips | — | 6.8.0-1047.50+fips1 |
| linux-gke | — | 6.8.0-1043.48 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 6.8.0-1030.33 |
| linux-gkeop-5.15 | — | — |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-144.157~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | — |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.11 | — | — |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-6.8 | — | 6.8.0-100.100~22.04.1 |
| linux-hwe-edge | — | — |
| linux-ibm | — | 6.8.0-1044.44 |
| linux-ibm-5.15 | — | 5.15.0-1080.83~20.04.1 |
| linux-ibm-5.4 | — | — |
| linux-ibm-6.8 | — | 6.8.0-1044.44~22.04.1 |
| linux-intel | — | — |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1081.83 |
| linux-intel-iotg | — | 5.15.0-1083.89 |
| linux-intel-iotg-5.15 | — | 5.15.0-1083.89~20.04.1 |
| linux-iot | — | — |
| linux-kvm | — | 5.15.0-1084.89 |
| linux-lowlatency | — | 6.8.0-100.100.1 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-144.157~20.04.1 |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.11 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | — |
| linux-lowlatency-hwe-6.8 | — | 6.8.0-100.100.1~22.04.1 |
| linux-lts-xenial | — | — |
| linux-nvidia | — | 6.8.0-1046.49 |
| linux-nvidia-6.11 | — | — |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-nvidia-6.8 | — | 6.8.0-1046.49~22.04.1 |
| linux-nvidia-lowlatency | — | 6.8.0-1046.49.1 |
| linux-nvidia-tegra | — | 6.8.0-1020.20 |
| linux-nvidia-tegra-5.15 | — | 5.15.0-1041.41~20.04.1 |
| linux-nvidia-tegra-igx | — | 5.15.0-1030.30 |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.11 | — | — |
| linux-oem-6.5 | — | — |
| linux-oem-6.8 | — | — |
| linux-oracle | — | 6.8.0-1043.44 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1085.91~20.04.3 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | — |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-oracle-6.8 | — | 6.8.0-1043.44~22.04.1 |
| linux-raspi | — | 6.8.0-1047.51 |
| linux-raspi-5.4 | — | — |
| linux-raspi-realtime | — | 6.8.0-2037.38 |
| linux-raspi2 | — | — |
| linux-realtime | — | 6.8.1-1041.42 |
| linux-realtime-6.8 | — | 6.8.1-1041.42~22.04.1 |
| linux-riscv | — | — |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1083.87~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-riscv-6.8 | — | 6.8.0-100.100~22.04.1 |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
| linux-xilinx | — | 6.8.0-1023.24 |
| linux-xilinx-zynqmp | — | 5.15.0-1052.56 |
References
Similar Threats
- Unknown CGA-23jx-hhcx-m389
- Unknown CGA-2qp7-6757-fmgc
- Unknown CGA-2rj5-jc55-r267
- Unknown CGA-3m96-cwq8-6xmx
- Unknown CGA-3qj9-973w-fh9g
Vulnerability Monitoring
Track new vulnerabilities in linux
UBUNTU-CVE-2025-23163 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
