CVE-2025-37899 | In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in session logoff The sess->user object can currently be in use by another thread, for example if another connection has sent a session setup request to bind to the session being free'd. The handler for that connection could be in the smb2_sess_setup function which makes use of sess->user.
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in session logoff
The sess->user object can currently be in use by another thread, for
example if another connection has sent a session setup request to
bind to the session being free'd. The handler for that connection could
be in the smb2_sess_setup function which makes use of sess->user.
- 🔗 git.kernel.org/stable/c/931dc8a3670f71c45c0b1379ea4e92da…
- 🔗 git.kernel.org/stable/c/70ad6455139e26e85f48f95d0e21f351…
- 🔗 git.kernel.org/stable/c/d5ec1d79509b3ee01de02c236f096bc0…
- 🔗 git.kernel.org/stable/c/02d16046cd11a5c037b28c12ffb818c5…
- 🔗 git.kernel.org/stable/c/2fc9feff45d92a92cd5f96487655d5be…
- 🔗 news.ycombinator.com/item
- 🔗 sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025…
Zero-Day & Vulnerability Intelligence Hub
Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
| Tier | 2026-08-30 | 2026-09-18 |
|---|---|---|
| ≥90 % | 0 | 0 |
| ≥50 % | 0 | 0 |
| ≥10 % | 0 | 0 |
| <10 % | 300 | 300 |
CVE-2025-37899 | In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in session logoff The sess->user object can currently be in use by another thread, for example if another connection has sent a session setup request to bind to the session being free'd. The handler for that connection could be in the smb2_sess_setup function which makes use of sess->user.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in session logoff The sess->user object can currently be in use by another thread, for example if another connection has sent a session setup re