{"id":"CVE-2025-22053","title":"net: ibmveth: make veth_pool_store stop hanging","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ibmveth: make veth_pool_store stop hanging\n\nv2:\n- Created a single error handling unlock and exit in veth_pool_store\n- Greatly expanded commit message with previou…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < c1bcbc4ee8f2e4567a9f63ec5a37e29b3fecf15a","Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 1e458c292f4c687dcf5aad32dd4836d03cd2191f","Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 8a88bb092f4208355880b9fdcc69d491aa297595","Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 86cc70f5c85dc09bf7f3e1eee380eefe73c90765","Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 0a2470e3ecde64fc7e3781dc474923193621ae67","Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 053f3ff67d7feefc75797863f3d84b47ad47086f","Linux 2.6.18"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-11-05T20:38:21.380772Z"},"published":"2025-04-16","updated":"2026-11-05","sourceUpdated":"2026-11-05T20:41:49.904Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-22053","references":[{"url":"https://git.kernel.org/stable/c/c1bcbc4ee8f2e4567a9f63ec5a37e29b3fecf15a"},{"url":"https://git.kernel.org/stable/c/1e458c292f4c687dcf5aad32dd4836d03cd2191f"},{"url":"https://git.kernel.org/stable/c/8a88bb092f4208355880b9fdcc69d491aa297595"},{"url":"https://git.kernel.org/stable/c/86cc70f5c85dc09bf7f3e1eee380eefe73c90765"},{"url":"https://git.kernel.org/stable/c/0a2470e3ecde64fc7e3781dc474923193621ae67"},{"url":"https://git.kernel.org/stable/c/053f3ff67d7feefc75797863f3d84b47ad47086f"}],"tags":["cve.org"],"epss":0.00154,"epssPercentile":0.04598,"ingestedAt":"2026-11-03T15:48:07.705Z","slug":"CVE-2025-22053","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ibmveth: make veth_pool_store stop hanging\n\nv2:\n- Created a single error handling unlock and exit in veth_pool_store\n- Greatly expanded commit message with previous explanatory-only text\n\nSummary: Use rtnl_mutex to synchronize veth_pool_store with itself,\nibmveth_close and ibmveth_open, preventing multiple calls in a row to\nnapi_disable.\n\nBackground: Two (or more) threads could call veth_pool_store through\nwriting to /sys/devices/vio/30000002/pool*/*. You can do this easily\nwith a little shell script. This causes a hang.\n\nI configured LOCKDEP, compiled ibmveth.c with DEBUG, and built a new\nkernel. I ran this test again and saw:\n\n    Setting pool0/active to 0\n    Setting pool1/active to 1\n    [   73.911067][ T4365] ibmveth 30000002 eth0: close starting\n    Setting pool1/active to 1\n    Setting pool1/active to 0\n    [   73.911367][ T4366] ibmveth 30000002 eth0: close starting\n    [   73.916056][ T4365] ibmveth 30000002 eth0: close complete\n    [   73.916064][ T4365] ibmveth 30000002 eth0: open starting\n    [  110.808564][  T712] systemd-journald[712]: Sent WATCHDOG=1 notification.\n    [  230.808495][  T712] systemd-journald[712]: Sent WATCHDOG=1 notification.\n    [  243.683786][  T123] INFO: task stress.sh:4365 blocked for more than 122 seconds.\n    [  243.683827][  T123]       Not tainted 6.14.0-01103-g2df0c02dab82-dirty #8\n    [  243.683833][  T123] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n    [  243.683838][  T123] task:stress.sh       state:D stack:28096 pid:4365  tgid:4365  ppid:4364   task_flags:0x400040 flags:0x00042000\n    [  243.683852][  T123] Call Trace:\n    [  243.683857][  T123] [c00000000c38f690] [0000000000000001] 0x1 (unreliable)\n    [  243.683868][  T123] [c00000000c38f840] [c00000000001f908] __switch_to+0x318/0x4e0\n    [  243.683878][  T123] [c00000000c38f8a0] [c000000001549a70] __schedule+0x500/0x12a0\n    [  243.683888][  T123] [c00000000c38f9a0] [c00000000154a878] schedule+0x68/0x210\n    [  243.683896][  T123] [c00000000c38f9d0] [c00000000154ac80] schedule_preempt_disabled+0x30/0x50\n    [  243.683904][  T123] [c00000000c38fa00] [c00000000154dbb0] __mutex_lock+0x730/0x10f0\n    [  243.683913][  T123] [c00000000c38fb10] [c000000001154d40] napi_enable+0x30/0x60\n    [  243.683921][  T123] [c00000000c38fb40] [c000000000f4ae94] ibmveth_open+0x68/0x5dc\n    [  243.683928][  T123] [c00000000c38fbe0] [c000000000f4aa20] veth_pool_store+0x220/0x270\n    [  243.683936][  T123] [c00000000c38fc70] [c000000000826278] sysfs_kf_write+0x68/0xb0\n    [  243.683944][  T123] [c00000000c38fcb0] [c0000000008240b8] kernfs_fop_write_iter+0x198/0x2d0\n    [  243.683951][  T123] [c00000000c38fd00] [c00000000071b9ac] vfs_write+0x34c/0x650\n    [  243.683958][  T123] [c00000000c38fdc0] [c00000000071bea8] ksys_write+0x88/0x150\n    [  243.683966][  T123] [c00000000c38fe10] [c0000000000317f4] system_call_exception+0x124/0x340\n    [  243.683973][  T123] [c00000000c38fe50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec\n    ...\n    [  243.684087][  T123] Showing all locks held in the system:\n    [  243.684095][  T123] 1 lock held by khungtaskd/123:\n    [  243.684099][  T123]  #0: c00000000278e370 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x50/0x248\n    [  243.684114][  T123] 4 locks held by stress.sh/4365:\n    [  243.684119][  T123]  #0: c00000003a4cd3f8 (sb_writers#3){.+.+}-{0:0}, at: ksys_write+0x88/0x150\n    [  243.684132][  T123]  #1: c000000041aea888 (&of->mutex#2){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x154/0x2d0\n    [  243.684143][  T123]  #2: c0000000366fb9a8 (kn->active#64){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x160/0x2d0\n    [  243.684155][  T123]  #3: c000000035ff4cb8 (&dev->lock){+.+.}-{3:3}, at: napi_enable+0x30/0x60\n    [  243.684166][  T123] 5 locks held by stress.sh/4366:\n    [  243.684170][  T123]  #0: c00000003a4cd3f8 (sb_writers#3){.+.+}-{0:0}, at: ksys_write+0x88/0x150\n    [  243.\n---truncated---\n\n## Affected\n\n- `Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < c1bcbc4ee8f2e4567a9f63ec5a37e29b3fecf15a`\n- `Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 1e458c292f4c687dcf5aad32dd4836d03cd2191f`\n- `Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 8a88bb092f4208355880b9fdcc69d491aa297595`\n- `Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 86cc70f5c85dc09bf7f3e1eee380eefe73c90765`\n- `Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 0a2470e3ecde64fc7e3781dc474923193621ae67`\n- `Linux >= 860f242eb5340d0b0cfe243cb86b2a98f92e8b91 < 053f3ff67d7feefc75797863f3d84b47ad47086f`\n- `Linux 2.6.18`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}