Linux Kernel up to 6.6.130/6.12.79/6.18.20/6.19.10/7.0-rc5 tls_decrypt_async_wait information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.6.130/6.12.79/6.18.20/6.19.10/7.0-rc5. Affected by this vulnerability is the function tls_decrypt_async_wait. Such manipulation leads to information disclosure. This vulnerability is referenced as CVE-2026-23414. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.130/6.12.79/6.18.20/6.19.10/7.0-rc5. It has been rated as problematic. Affected by this issue is the function tls_decrypt_async_wait. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:

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]

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-23414 since 01/13/2026. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/08/2026). The MITRE ATT&CK project declares the attack technique as T1592.

Upgrading to version 6.6.131, 6.12.80, 6.18.21, 6.19.11 or 7.0-rc6 eliminates this vulnerability. Applying the patch 2dcf324855c34e7f934ce978aa19b645a8f3ee71/6dc11e0bd0a5466bcc76d275c09e5537bd0597dd/9f557c7eae127b44d2e863917dc986a4b6cb1269/fd8037e1f18ca5336934d0e0e7e1a4fe097e749d/84a8335d8300576f1b377ae24abca1d9f197807f is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at EUVD (EUVD-2026-18195) and CERT Bund (WID-SEC-2026-0985). Once again VulDB remains the best source for vulnerability data.

Affected

  • Open Source Linux Kernel
  • Microsoft Azure Linux

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.131/6.12.80/6.18.21/6.19.11/7.0-rc6
Patch: 2dcf324855c34e7f934ce978aa19b645a8f3ee71/6dc11e0bd0a5466bcc76d275c09e5537bd0597dd/9f557c7eae127b44d2e863917dc986a4b6cb1269/fd8037e1f18ca5336934d0e0e7e1a4fe097e749d/84a8335d8300576f1b377ae24abca1d9f197807f

Timelineinfo

01/13/2026 CVE reserved
04/02/2026 +78 days Advisory disclosed
04/02/2026 +0 days VulDB entry created
04/08/2026 +5 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-23414 (🔒)
GCVE (CVE): GCVE-0-2026-23414
GCVE (VulDB): GCVE-100-354860
EUVD: 🔒
CERT Bund: WID-SEC-2026-0985 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 04/02/2026 14:27
Updated: 04/08/2026 01:25
Changes: 04/02/2026 14:27 (58), 04/02/2026 15:51 (1), 04/08/2026 01:25 (7)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!