CVE-2026-45924

ksmbd: call ksmbd_vfs_kern_path_end_removing() on some error paths

MEDIUM

5.5

CVSS Score

Published: May 27, 2026 at 12:17 PM UTC

Updated: June 27, 2026 at 11:41 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: call ksmbd_vfs_kern_path_end_removing() on some error paths There are two places where ksmbd_vfs_kern_path_end_removing() needs to be called in order to balance what the corresponding successful call to ksmbd_vfs_kern_path_start_removing() has done, i.e. drop inode locks and put the taken references. Otherwise there might be potential deadlocks and unbalanced locks which are caught like: BUG: workqueue leaked lock or atomic: kworker/5:21/0x00000000/7596 last function: handle_ksmbd_work 2 locks held by kworker/5:21/7596: #0: ffff8881051ae448 (sb_writers#3){.+.+}-{0:0}, at: ksmbd_vfs_kern_path_locked+0x142/0x660 #1: ffff888130e966c0 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: ksmbd_vfs_kern_path_locked+0x17d/0x660 CPU: 5 PID: 7596 Comm: kworker/5:21 Not tainted 6.1.162-00456-gc29b353f383b #138 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 Workqueue: ksmbd-io handle_ksmbd_work Call Trace: <TASK> dump_stack_lvl+0x44/0x5b process_one_work.cold+0x57/0x5c worker_thread+0x82/0x600 kthread+0x153/0x190 ret_from_fork+0x22/0x30 </TASK> Found by Linux Verification Center (linuxtesting.org).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 6.15.11v ≥ 6.16.25.15.190 ≤ v < 5.15.2036.1.149 ≤ v < 6.1.1676.12.43 ≤ v < 6.12.786.15.11 ≤ v < 6.166.16.2 ≤ v < 6.176.16.2 ≤ v < 6.18.176.17 ≤ v < 6.18.176.17 ≤ v < 6.19.46.17 ≤ v < 7.06.19 ≤ v < 6.19.46.6.103 ≤ v < 6.6.1301e858a7a51c7b8b009d8f246de7ceb7743b44a715.15.190 6.1.149 6.12.43 6.15.11 6.16.2 6.17 6.6.103814cfdb6358d9b84fcbec9918c8f938cc096a43a9d5012ffe14120f978ee34aef4df3d6cb026b7c4a726fef6d7d4cfc365d3434e3916dbfe78991a33a7dddd62578c2eb6cb28b8835556a121b5157323ac98d54630d5b52e3f684d872f0d82c06c418ea9d5fc1400a34b4ea5e8f2ce296ea12bf8c8421694

Vendor states this is fixed in 0c578e8065c4b08d5635a4cbc0f6321df9d20f79 (fixed)

Vendor states this is fixed in 34d6691933682f0516259a31b39d2cebcedec0a5 (fixed)

Vendor states this is fixed in 4c38600feb81c670edb82e49d201d3d2d00cd4c3 (fixed)

Vendor states this is fixed in 8e3a3192ef78d8302916408d62813b1fddfc8972 (fixed)

Vendor states this is fixed in a09dc10d1353f0e92c21eae2a79af1c2b1ddcde8 (fixed)

Vendor states this is fixed in cf29329a13df79c198b45dfc92577638d30b56fa (fixed)

Vendor states this is fixed in f221baa80e5959a0c08a7e34abbf2a4d3cf0e1c2 (fixed)

Vendor states this is fixed in 5.15.203 (unaffected)

Vendor states this is fixed in 6.1.167 (unaffected)

Vendor states this is fixed in 6.12.78 (unaffected)

Affected range stops below 6.16, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.17 (unaffected)