Linux Kernel up to 6.6.139/6.12.85/6.18.26/7.0.3 smc_clc_wait_msg state issue

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.
6.4$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 6.6.139/6.12.85/6.18.26/7.0.3. This impacts the function smc_clc_wait_msg. This manipulation causes state issue. This vulnerability is registered as CVE-2026-46027. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.6.139/6.12.85/6.18.26/7.0.3. Affected by this vulnerability is the function smc_clc_wait_msg. The manipulation with an unknown input leads to a state issue vulnerability. The CWE definition for the vulnerability is CWE-371. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: net/smc: avoid early lgr access in smc_clc_wait_msg A CLC decline can be received while the handshake is still in an early stage, before the connection has been associated with a link group. The decline handling in smc_clc_wait_msg() updates link-group level sync state for first-contact declines, but that state only exists after link group setup has completed. Guard the link-group update accordingly and keep the per-socket peer diagnosis handling unchanged. This preserves the existing sync_err handling for established link-group contexts and avoids touching link-group state before it is available.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-46027 since 05/13/2026. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/17/2026).

Upgrading to version 6.6.140, 6.12.86, 6.18.27, 7.0.4 or 7.1-rc1 eliminates this vulnerability. Applying the patch f0858e1d5624bb120b198f2a8528f97a9b0ae069/6180a296ca65b08a81914805cbc0f78da5f10a1f/ea0b5d0fe96356dce38f98375a57c52a04e13712/83bcf9228b0501694fb2589ed1d142855a2887f2/5a8db80f721deee8e916c2cfdee78decda02ce4f 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.5
CNA Vector (Linux): 🔒

CVSSv2info

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

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

Exploitinginfo

Class: State issue
CWE: CWE-371
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

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.140/6.12.86/6.18.27/7.0.4/7.1-rc1
Patch: f0858e1d5624bb120b198f2a8528f97a9b0ae069/6180a296ca65b08a81914805cbc0f78da5f10a1f/ea0b5d0fe96356dce38f98375a57c52a04e13712/83bcf9228b0501694fb2589ed1d142855a2887f2/5a8db80f721deee8e916c2cfdee78decda02ce4f

Timelineinfo

05/13/2026 CVE reserved
05/27/2026 +14 days Advisory disclosed
05/27/2026 +0 days VulDB entry created
06/17/2026 +20 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46027 (🔒)
GCVE (CVE): GCVE-0-2026-46027
GCVE (VulDB): GCVE-100-366265

Entryinfo

Created: 05/27/2026 17:23
Updated: 06/17/2026 00:25
Changes: 05/27/2026 17:23 (58), 06/17/2026 00:25 (11)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!