CVE-2026-23414

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.5 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, b8a6ff84abbcbbc445463de58704686011edc8e1, <ac435be7c7613eb13a5a8ceb5182e10b50c9ce87, 0, 7.0, <6.1.168, 6.6.114, 6.18, <9f557c7eae127b44d2e863917dc986a4b6cb1269, 39dec4ea3daf77f684308576baf483b55ca7f160, <=6.6.*, 6.19.11, <=6.19.*, 4fc109d0ab196bd943b7451276690fb6bb48c2e0, <2dcf324855c34e7f934ce978aa19b645a8f3ee71, <6.12.80, <=6.18.*, 6.6.131, 6.12.80, 6.1.158, 9f83fd0c179e0f458e824e417f9d5ad53443f685, <6.18, <fd8037e1f18ca5336934d0e0e7e1a4fe097e749d, <6dc11e0bd0a5466bcc76d275c09e5537bd0597dd, <6.6.131, <=*, 6.1.168, 6.18.21, 6.17.5, <84a8335d8300576f1b377ae24abca1d9f197807f, c61d4368197d65c4809d9271f3b85325a600586a, 6.12.55

Description

In the Linux kernel, the following vulnerability has been resolved: tls: Purge async_hold in tls_decrypt_async_wait() The async_hold queue pins encrypted input skbs while the AEAD engine references their scatterlist data. Once tls_decrypt_async_wait() returns, every AEAD operation has completed and the engine no longer references those skbs, so they can be freed unconditionally. A subsequent patch adds batch async decryption to tls_sw_read_sock(), introducing a new call site that must drain pending AEAD operations and release held skbs. Move __skb_queue_purge(&ctx->async_hold) into tls_decrypt_async_wait() so the purge is centralized and every caller -- recvmsg's drain path, the -EBUSY fallback in tls_do_decryption(), and the new read_sock batch path -- releases held skbs on synchronization without each site managing the purge independently. This fixes a leak when tls_strp_msg_hold() fails part-way through, after having added some cloned skbs to the async_hold queue. tls_decrypt_sg() will then call tls_decrypt_async_wait() to process all pending decrypts, and drop back to synchronous mode, but tls_sw_recvmsg() only flushes the async_hold queue when one record has been processed in "fully-async" mode, which may not be the case here. [pabeni@redhat.com: added leak comment]

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, b8a6ff84abbcbbc445463de58704686011edc8e1, <ac435be7c7613eb13a5a8ceb5182e10b50c9ce87, 0, 7.0, <6.1.168, 6.6.114, 6.18, <9f557c7eae127b44d2e863917dc986a4b6cb1269, 39dec4ea3daf77f684308576baf483b55ca7f160, <=6.6.*, 6.19.11, <=6.19.*, 4fc109d0ab196bd943b7451276690fb6bb48c2e0, <2dcf324855c34e7f934ce978aa19b645a8f3ee71, <6.12.80, <=6.18.*, 6.6.131, 6.12.80, 6.1.158, 9f83fd0c179e0f458e824e417f9d5ad53443f685, <6.18, <fd8037e1f18ca5336934d0e0e7e1a4fe097e749d, <6dc11e0bd0a5466bcc76d275c09e5537bd0597dd, <6.6.131, <=*, 6.1.168, 6.18.21, 6.17.5, <84a8335d8300576f1b377ae24abca1d9f197807f, c61d4368197d65c4809d9271f3b85325a600586a, 6.12.55) 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