Linux Kernel up to 6.6.139/6.12.85/6.18.26/7.0.3 rxrpc privilege escalation

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

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.6.139/6.12.85/6.18.26/7.0.3. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component rxrpc. This manipulation causes an unknown weakness. The identification of this vulnerability is CVE-2026-46085. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.139/6.12.85/6.18.26/7.0.3. It has been declared as critical. Affected by this vulnerability is an unknown function of the component rxrpc. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix rxkad crypto unalignment handling Fix handling of a packet with a misaligned crypto length. Also handle non-ENOMEM errors from decryption by aborting. Further, remove the WARN_ON_ONCE() so that it can't be remotely triggered (a trace line can still be emitted).

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-46085 since 05/13/2026. The exploitation appears to be difficult. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/25/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 f1c6bd0cc786a8fa74829ce3c4b3673944a308f4/440d20d95e844b657a93a0b2dcc2aae155efdce6/f0d3efd03b2a9e0f1ffa6df8fcb264af3d494286/af9271eb666d07b6f65612dc160a47f7cb5220ed/def304aae2edf321d2671fd6ca766a93c21f877e 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 vulnerability database at EUVD (EUVD-2026-32468). 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.0
VulDB Meta Temp Score: 5.9

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
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: Privilege escalation
CWE: Unknown
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: f1c6bd0cc786a8fa74829ce3c4b3673944a308f4/440d20d95e844b657a93a0b2dcc2aae155efdce6/f0d3efd03b2a9e0f1ffa6df8fcb264af3d494286/af9271eb666d07b6f65612dc160a47f7cb5220ed/def304aae2edf321d2671fd6ca766a93c21f877e

Timelineinfo

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

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46085 (🔒)
GCVE (CVE): GCVE-0-2026-46085
GCVE (VulDB): GCVE-100-366289
EUVD: 🔒

Entryinfo

Created: 05/27/2026 17:29
Updated: 06/25/2026 02:14
Changes: 05/27/2026 17:29 (57), 05/27/2026 18:16 (1), 06/25/2026 02:14 (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 want to use VulDB in your project?

Use the official API to access entries easily!