---
id: CVE-2026-23414
title: |-
  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
summary: |-
  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_decr…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-401
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 6.1.158, < 6.1.168'
  - 'linux_kernel >= 6.6.114, < 6.6.131'
  - 'linux_kernel >= 6.12.55, < 6.12.80'
  - 'linux_kernel >= 6.17.5, < 6.18'
  - 'linux_kernel >= 6.18.1, < 6.18.21'
  - 'linux_kernel >= 6.19, < 6.19.11'
  - linux_kernel = 6.18
  - linux_kernel = 7.0
patched:
  - linux_kernel 6.19.11
published: '2026-04-02'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T02:18:55.510'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-23414'
references:
  - url: 'https://git.kernel.org/stable/c/2dcf324855c34e7f934ce978aa19b645a8f3ee71'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6dc11e0bd0a5466bcc76d275c09e5537bd0597dd'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/84a8335d8300576f1b377ae24abca1d9f197807f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/9f557c7eae127b44d2e863917dc986a4b6cb1269'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ac435be7c7613eb13a5a8ceb5182e10b50c9ce87'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/fd8037e1f18ca5336934d0e0e7e1a4fe097e749d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-019113.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-082556.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-457936.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.0037
epssPercentile: 0.31137
ingestedAt: '2026-09-08T15:33:26.992Z'
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-10-16T15:07:51.357373Z'
---

## Overview

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]

## Affected

- `linux_kernel >= 6.1.158, < 6.1.168`
- `linux_kernel >= 6.6.114, < 6.6.131`
- `linux_kernel >= 6.12.55, < 6.12.80`
- `linux_kernel >= 6.17.5, < 6.18`
- `linux_kernel >= 6.18.1, < 6.18.21`
- `linux_kernel >= 6.19, < 6.19.11`
- `linux_kernel = 6.18`
- `linux_kernel = 7.0`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.19.11`