[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025040146-CVE-2025-21967-114e@gregkh>
Date: Tue, 1 Apr 2025 16:45:52 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-21967: ksmbd: fix use-after-free in ksmbd_free_work_struct
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in ksmbd_free_work_struct
->interim_entry of ksmbd_work could be deleted after oplock is freed.
We don't need to manage it with linked list. The interim request could be
immediately sent whenever a oplock break wait is needed.
The Linux kernel CVE team has assigned CVE-2025-21967 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.84 with commit fb776765bfc21d5e4ed03bb3d4406c2b86ff1ac3
Fixed in 6.12.20 with commit 62746ae3f5414244a96293e3b017be637b641280
Fixed in 6.13.8 with commit eb51f6f59d19b92f6fe84d3873f958495ab32f0a
Fixed in 6.14 with commit bb39ed47065455604729404729d9116868638d31
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-21967
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:
fs/smb/server/ksmbd_work.c
fs/smb/server/ksmbd_work.h
fs/smb/server/oplock.c
fs/smb/server/oplock.h
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/fb776765bfc21d5e4ed03bb3d4406c2b86ff1ac3
https://git.kernel.org/stable/c/62746ae3f5414244a96293e3b017be637b641280
https://git.kernel.org/stable/c/eb51f6f59d19b92f6fe84d3873f958495ab32f0a
https://git.kernel.org/stable/c/bb39ed47065455604729404729d9116868638d31
Powered by blists - more mailing lists