Descrizione
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free after a failed durable reconnect ksmbd_reopen_durable_fd() republishes a detached durable handle in the reconnecting session's file table and takes no reference for that entry. If smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() to remove the volatile id. Two reconnects of the same handle can both take a lookup reference before either attaches it. If the one that reopens first then fails and drops its references first, the other request makes the final put through ksmbd_put_durable_fd(). That frees the handle without removing the first session's table entry, so tearing that session down writes to freed memory. BUG: KASAN: slab-use-after-free in __close_file_table_ids+0x14d/0x740 [ksmbd] Call Trace: __close_file_table_ids+0x14d/0x740 [ksmbd] ksmbd_destroy_file_table+0x76/0x100 [ksmbd] ksmbd_session_destroy+0xf8/0x480 [ksmbd] ksmbd_dispose_sessions+0x13e/0x200 [ksmbd] ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd] Freed by task 1030: __ksmbd_close_fd+0x97d/0x1000 [ksmbd] smb2_open+0x14eb/0xd9f0 [ksmbd] Commit 3515503322f4 ("ksmbd: fix durable reconnect error path file lifetime") handles a final put made by the reconnecting request, but not one made by another holder. Remove the volatile id under the file-table lock on this error path, before the references are dropped, as ksmbd_close_fd() does on the request_open path just above. Removal then no longer depends on which holder makes the final put. The stale comment in the reconnect cleanup is updated to match. A successful reconnect is unchanged.
Come correggere
Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 7.5, EPSS 0.2% (percentile 5).
Versioni da aggiornare
- Linux Linux: vulnerabili le versioni dalla
6.6.32precedenti alla6.7→ aggiornare alla6.7o successiva. - Linux Linux: versione corretta
6.12.117(o successiva). - Linux Linux: versione corretta
6.18.61(o successiva). - Linux Linux: versione corretta
7.3.2(o successiva). - Linux Linux: versione corretta
7.4-rc1(o successiva). - Linux Linux: vulnerabile la versione
6.9→ installare l'ultima release supportata dal vendor.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Ridurre l'esposizione del componente vulnerabile (segmentazione, accesso solo da reti fidate) finché la patch non è applicata.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| Linux | Linux | ≥ 6.6.32 < 6.7 | 6.7 |
| Linux | Linux | — | 6.12.117 |
| Linux | Linux | — | 6.18.61 |
| Linux | Linux | — | 7.3.2 |
| Linux | Linux | — | 7.4-rc1 |
| Linux | Linux | 6.9 | — |
Riferimenti
- Riferimentohttps://git.kernel.org/stable/c/248b5819591c577727930e4e255a455235fab50a
- Riferimentohttps://git.kernel.org/stable/c/5078a4e41b29acdf6be52e4a7cc8a59c2a72a471
- Riferimentohttps://git.kernel.org/stable/c/bd47ee501b6ac4a26ae41f780a43b7967302a269
- Riferimentohttps://git.kernel.org/stable/c/edacf65866a9f397438d5b9ff9f43312b29b4b3c