ROOT-OS-UBUNTU-2204-CVE-2025-37952 CVE-2025-37952 in linux - Patched by Root

Root has patched CVE-2025-37952 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available...

CVE-2025-37952

creationtimestamp| type| source ---|---|--- 2026-03-19 00:00:00+00:00| seen| https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/...

Azure Linux 3.0 Security Update: kernel (CVE-2025-37952)

The version of kernel installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2025-37952 advisory. - In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix UAF in closefiletableids A...

CVE-2025-37952 affecting package kernel for versions less than 6.6.92.2-1

CVE-2025-37952 affecting package kernel for versions less than 6.6.92.2-1. An upgraded version of the package is available that resolves this issue...

CVE-2025-37952

In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix UAF in closefiletableids A use-after-free is possible if one thread destroys the file via ksmbdclosefd while another thread holds a reference to it. The existing checks on fp-refcount are not sufficient to prevent this...

CVE-2025-37952

In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix UAF in closefiletableids A use-after-free is possible if one thread destroys the file via ksmbdclosefd while another thread holds a reference to it. The existing checks on fp-refcount are not sufficient to prevent this...

CVE-2025-37952 ksmbd: Fix UAF in __close_file_table_ids

In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix UAF in closefiletableids A use-after-free is possible if one thread destroys the file via ksmbdclosefd while another thread holds a reference to it. The existing checks on fp-refcount are not sufficient to prevent this...

CVE-2025-37952

In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix UAF in closefiletableids A use-after-free is possible if one thread destroys the file via ksmbdclosefd while another thread holds a reference to it. The existing checks on fp-refcount are not sufficient to prevent this...