CVE-2024-53186
published 2024-12-27CVE-2024-53186: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in SMB request handling A race condition exists between SMB…
PriorityP431high7CVSS 3.1
AVLACHPRLUINSUCHIHAH
EPSS
0.18%
7.3th percentile
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in SMB request handling
A race condition exists between SMB request handling in
`ksmbd_conn_handler_loop()` and the freeing of `ksmbd_conn` in the
workqueue handler `handle_ksmbd_work()`. This leads to a UAF.
- KASAN: slab-use-after-free Read in handle_ksmbd_work
- KASAN: slab-use-after-free in rtlock_slowlock_locked
This race condition arises as follows:
- `ksmbd_conn_handler_loop()` waits for `conn->r_count` to reach zero:
`wait_event(conn->r_count_q, atomic_read(&conn->r_count) == 0);`
- Meanwhile, `handle_ksmbd_work()` decrements `conn->r_count` using
`atomic_dec_return(&conn->r_count)`, and if it reaches zero, calls
`ksmbd_conn_free()`, which frees `conn`.
- However, after `handle_ksmbd_work()` decrements `conn->r_count`,
it may still access `conn->r_count_q` in the following line:
`waitqueue_active(&conn->r_count_q)` or `wake_up(&conn->r_count_q)`
This results in a UAF, as `conn` has already been freed.
The discovery of this UAF can be referenced in the following PR for
syzkaller's support for SMB requests.
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.12.3-1 (forky) | linux 6.12.3-1 (forky) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 18f06bacc197d4ac9b518ad1c69999bc3d83e7aa < a96f9eb7add30ba0fafcfe7b7aca090978196800 | a96f9eb7add30ba0fafcfe7b7aca090978196800 |
| linux | linux | >= 6.10.14 < 6.11 | 6.11 |
| linux | linux | >= 6.11.3 < 6.11.11 | 6.11.11 |
| linux | linux | >= 6.6.55 < 6.6.64 | 6.6.64 |
| linux | linux | >= e9dac92f4482a382e8c0fe1bc243da5fc3526b0c < f20b77f7897e6aab9ce5527e6016ad2be5d70a33 | f20b77f7897e6aab9ce5527e6016ad2be5d70a33 |
| linux | linux | >= ee426bfb9d09b29987369b897fe9b6485ac2be27 < 96261adb998a3b513468b6ce17dbec76be5507d4 | 96261adb998a3b513468b6ce17dbec76be5507d4 |
| linux | linux | >= ee426bfb9d09b29987369b897fe9b6485ac2be27 < 9a8c5d89d327ff58e9b2517f8a6afb4181d32c6e | 9a8c5d89d327ff58e9b2517f8a6afb4181d32c6e |
| linux | linux_kernel | >= 0 < 6.12.3-1 | 6.12.3-1 |
| linux | linux_kernel | >= 0 < 6.12.3-1 | 6.12.3-1 |
| linux | linux_kernel | >= 6.10.14 < 6.11 | 6.11 |
| linux | linux_kernel | >= 6.11.3 < 6.11.11 | 6.11.11 |
| linux | linux_kernel | >= 6.12 < 6.12.2 | 6.12.2 |
| linux | linux_kernel | >= 6.6.55 < 6.6.64 | 6.6.64 |
| msrc | azl3_kernel_6.6.57.1-7_on_azure_linux_3.0 | — | — |
CVSS provenance
nvdv3.17.0HIGHCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.0HIGH
vendor_debian7.0LOW
vendor_redhat7.0HIGH
vendor_msrc4.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-w9v5-63v9-9qvj: In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in SMB request handling
A race condition exists betwee
ghsa_unreviewed·2024-12-27
CVE-2024-53186 [HIGH] CWE-362 GHSA-w9v5-63v9-9qvj: In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in SMB request handling
A race condition exists betwee
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in SMB request handling
A race condition exists between SMB request handling in
`ksmbd_conn_handler_loop()` and the freeing of `ksmbd_conn` in the
workqueue handler `handle_ksmbd_work()`. This leads to a UAF.
- KASAN: slab-use-after-free Read in handle_ksmbd_work
- KASAN: slab-use-after-free in rtlock_slowlock_locked
This race condition arises as follows:
- `ksmbd_conn_handler_loop()` waits for `conn->r_count` to reach zero:
`wait_event(conn->r_count_q, atomic_read(&conn->r_count) == 0);`
- Meanwhile, `handle_ksmbd_work()` decrements `conn->r_count` using
`atomic_dec_return(&conn->r_count)`, and if it reaches zero, calls
`ksmbd_conn_free()`, which frees `conn`.
- However, after `handle_ksmbd_wo
OSV
CVE-2024-53186: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in SMB request handling A race condition exists between
osv·2024-12-27·CVSS 7.0
CVE-2024-53186 [HIGH] CVE-2024-53186: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in SMB request handling A race condition exists between
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in SMB request handling A race condition exists between SMB request handling in `ksmbd_conn_handler_loop()` and the freeing of `ksmbd_conn` in the workqueue handler `handle_ksmbd_work()`. This leads to a UAF. - KASAN: slab-use-after-free Read in handle_ksmbd_work - KASAN: slab-use-after-free in rtlock_slowlock_locked This race condition arises as follows: - `ksmbd_conn_handler_loop()` waits for `conn->r_count` to reach zero: `wait_event(conn->r_count_q, atomic_read(&conn->r_count) == 0);` - Meanwhile, `handle_ksmbd_work()` decrements `conn->r_count` using `atomic_dec_return(&conn->r_count)`, and if it reaches zero, calls `ksmbd_conn_free()`, which frees `conn`. - However, after `handle_ksmbd_work(
Red Hat
kernel: ksmbd: fix use-after-free in SMB request handling
vendor_redhat·2024-12-27·CVSS 7.0
CVE-2024-53186 [HIGH] CWE-416 kernel: ksmbd: fix use-after-free in SMB request handling
kernel: ksmbd: fix use-after-free in SMB request handling
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in SMB request handling
A race condition exists between SMB request handling in
`ksmbd_conn_handler_loop()` and the freeing of `ksmbd_conn` in the
workqueue handler `handle_ksmbd_work()`. This leads to a UAF.
- KASAN: slab-use-after-free Read in handle_ksmbd_work
- KASAN: slab-use-after-free in rtlock_slowlock_locked
This race condition arises as follows:
- `ksmbd_conn_handler_loop()` waits for `conn->r_count` to reach zero:
`wait_event(conn->r_count_q, atomic_read(&conn->r_count) == 0);`
- Meanwhile, `handle_ksmbd_work()` decrements `conn->r_count` using
`atomic_dec_return(&conn->r_count)`, and if it reaches zero, calls
`ksmbd_conn_free()
Microsoft
ksmbd: fix use-after-free in SMB request handling
vendor_msrc·2024-12-10·CVSS 4.5
CVE-2024-53186 [HIGH] CWE-362 ksmbd: fix use-after-free in SMB request handling
ksmbd: fix use-after-free in SMB request handling
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
Linux: Linux
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://learn.micro
Debian
CVE-2024-53186: linux - In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix ...
vendor_debian·2024·CVSS 7.0
CVE-2024-53186 [HIGH] CVE-2024-53186: linux - In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix ...
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in SMB request handling A race condition exists between SMB request handling in `ksmbd_conn_handler_loop()` and the freeing of `ksmbd_conn` in the workqueue handler `handle_ksmbd_work()`. This leads to a UAF. - KASAN: slab-use-after-free Read in handle_ksmbd_work - KASAN: slab-use-after-free in rtlock_slowlock_locked This race condition arises as follows: - `ksmbd_conn_handler_loop()` waits for `conn->r_count` to reach zero: `wait_event(conn->r_count_q, atomic_read(&conn->r_count) == 0);` - Meanwhile, `handle_ksmbd_work()` decrements `conn->r_count` using `atomic_dec_return(&conn->r_count)`, and if it reaches zero, calls `ksmbd_conn_free()`, which frees `conn`. - However, after `handle_ksmbd_work(
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-12-27
Published