CVE-2026-31444

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free and NULL deref in smb_grant_oplock() smb_grant_oplock() has two issues in the oplock publication sequence: 1) opinfo is linked into ci->m_op_list (via opinfo_add) before add_lease_global_list() is called. If add_lease_global_list() fails (kmalloc returns NULL), the error path frees the opinfo via __free_opinfo() while it is still linked in ci->m_op_list. Concurrent m_op_list readers (opinfo_get_list, or direct iteration in smb_break_all_levII_oplock) dereference the freed node. 2) opinfo->o_fp is assigned after add_lease_global_list() publishes the opinfo on the global lease list. A concurrent find_same_lease_key() can walk the lease list and dereference opinfo->o_fp->f_ci while o_fp is still NULL. Fix by restructuring the publication sequence to eliminate post-publish failure: - Set opinfo->o_fp before any list publication (fixes NULL deref). - Preallocate lease_table via alloc_lease_table() before opinfo_add() so add_lease_global_list() becomes infallible after publication. - Keep the original m_op_list publication order (opinfo_add before lease list) so concurrent opens via same_client_has_lease() and opinfo_get_list() still see the in-flight grant. - Use opinfo_put() instead of __free_opinfo() on err_out so that the RCU-deferred free path is used. This also requires splitting add_lease_global_list() to take a preallocated lease_table and changing its return type from int to void, since it can no longer fail.

Gravité et risque d'exploitation

CVE-2026-31444 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.65 %, ce qui la place devant 50.3 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions ce8507ee82c888126d8e7565e27c016308d24cde, <7de55bba69cbf0f9280daaea385daf08bc076121, <48623ec358c1c600fa1e38368746f933e0f1a617, <6.6.131, 6.19.9, <6.19.11, 1d6abf145615dbfe267ce3b0a271f95e3780e18e, 6.12.78, <6.12.80, <a5c6f6d6ceefed2d5210ee420fb75f8362461f46, 08aa9f3c8cf4d0bee44df540dfe34e8d64069f2c, 6.18.19, <6.18.21, 1dfd062caa165ec9d7ee0823087930f3ab8a6294, 6.6.130, <9e785f004cbc56390479b77375726ea9b0d1a8a6, 302fef75512b2c8329a3f5efab1ae7ba2562387a, <6d7e5a918c1d0aad06db0e17677b66fc9a471021) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/9e785f004cbc56390479b77375726ea9b0d1a8a6
• https://git.kernel.org/stable/c/7de55bba69cbf0f9280daaea385daf08bc076121
• https://git.kernel.org/stable/c/a5c6f6d6ceefed2d5210ee420fb75f8362461f46
• https://git.kernel.org/stable/c/6d7e5a918c1d0aad06db0e17677b66fc9a471021
• https://git.kernel.org/stable/c/48623ec358c1c600fa1e38368746f933e0f1a617