Read the docs
TI-2026-18849 Aliases CVE-2026-23414GHSA-8fgp-q3pf-q3rh

tls: Purge async_hold in tls_decrypt_async_wait()

Priority LOW 39CWE-401Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Partial Red Hat: 2 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-401.

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_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. [[email protected]: added leak comment]

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0037 31st percentileScored 2026-11-07
Fix Partial Linux (Linux): 6.1.168, 6.6.131, 6.12.80 +4Red Hat: 2 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
LinuxLinux6.1.158 to before 6.1.168; 6.6.114 to before 6.6.131; 6.12.55 to before 6.12.80; 6.17.5 to before 6.186.1.168, 6.6.131, 6.12.80, 6.18Patch availableCNA
LinuxLinux6.18 and later6.1.168, 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0Patch availableCNA
  • Linux VendorLinux Affected 6.1.158 to before 6.1.168; 6.6.114 to before 6.6.131; 6.12.55 to before 6.12.80; 6.17.5 to before 6.18 Fixed in 6.1.168, 6.6.131, 6.12.80, 6.18 Patch available CNA
  • Linux VendorLinux Affected 6.18 and later Fixed in 6.1.168, 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0 Patch available CNA

CPE configurations NVD · 9

CPEVersionsRoleVendor
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*6.1.158 to before 6.1.168; 6.6.114 to before 6.6.131; 6.12.55 to before 6.12.80; 6.17.5 to before 6.18; 6.18.1 to before 6.18.21; 6.19 to before 6.19.11VulnerableLinux
cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:*6.18VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*7.0 rc1VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*7.0 rc2VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*7.0 rc3VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*7.0 rc4VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*7.0 rc5VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*7.0 rc6VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*7.0 rc7VulnerableLinux
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions 6.1.158 to before 6.1.168; 6.6.114 to before 6.6.131; 6.12.55 to before 6.12.80; 6.17.5 to before 6.18; 6.18.1 to before 6.18.21; 6.19 to before 6.19.11 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:* Versions 6.18 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* Versions 7.0 rc1 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* Versions 7.0 rc2 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* Versions 7.0 rc3 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:* Versions 7.0 rc4 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:* Versions 7.0 rc5 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:* Versions 7.0 rc6 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:* Versions 7.0 rc7 Vulnerable ·Linux

Remediation

  • Fix · CNA Linux (Linux) Fixed in 6.1.168, 6.6.131, 6.12.80, 6.18
  • Fix · CNA Linux (Linux) Fixed in 6.1.168, 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise Linux 10AffectedNo fix yet: Fix deferred
Red Hat Enterprise Linux 9AffectedNo fix yet: Fix deferred
Not affected: 3 products
  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-23414
  2. 2026-10-03 Alias added: GHSA-8fgp-q3pf-q3rh
  3. 2026-10-16 CISA SSVC decision points changed
  4. 2026-10-19 Weakness changed · CISA ADP

References

Patch 6

  • TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
  • TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
  • TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
  • TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
  • TI-2021-05514 Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACE KEVCVSS 3.1HIGH 8.3
See all 15278 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences