Linux Kernel up to 6.18.19/6.19.9 crash_dump read_key_from_user_keying debug log file

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 was found in Linux Kernel up to 6.18.19/6.19.9. It has been classified as critical. This impacts the function read_key_from_user_keying of the component crash_dump. The manipulation leads to debug log file. This vulnerability is uniquely identified as CVE-2026-31543. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.18.19/6.19.9 and classified as problematic. This issue affects the function read_key_from_user_keying of the component crash_dump. The manipulation with an unknown input leads to a debug log file vulnerability. Using CWE to declare the problem leads to CWE-534. This entry has been deprecated because its abstraction was too low-level. See CWE-532. Impacted is confidentiality. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: crash_dump: don't log dm-crypt key bytes in read_key_from_user_keying When debug logging is enabled, read_key_from_user_keying() logs the first 8 bytes of the key payload and partially exposes the dm-crypt key. Stop logging any key bytes.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-31543 since 03/09/2026. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 6.18.20 or 6.19.10 eliminates this vulnerability. Applying the patch 4897bd307ba8757c31a3325ba6730961be606016/ed8d91f469845d62d44c565a55d2ab1767969357/36f46b0e36892eba08978eef7502ff3c94ddba77 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 CERT Bund (WID-SEC-2026-1279). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel

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: Debug log file
CWE: CWE-534 / CWE-532 / CWE-200
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.18.20/6.19.10
Patch: 4897bd307ba8757c31a3325ba6730961be606016/ed8d91f469845d62d44c565a55d2ab1767969357/36f46b0e36892eba08978eef7502ff3c94ddba77

Timelineinfo

03/09/2026 CVE reserved
04/24/2026 +45 days Advisory disclosed
04/24/2026 +0 days VulDB entry created
06/11/2026 +48 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-31543 (🔒)
GCVE (CVE): GCVE-0-2026-31543
GCVE (VulDB): GCVE-100-359357
CERT Bund: WID-SEC-2026-1279 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 04/24/2026 17:34
Updated: 06/11/2026 08:24
Changes: 04/24/2026 17:34 (59), 05/25/2026 17:22 (7), 06/11/2026 08:24 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!