Skip to main content

Linux Kernel EUVDEUVD-2026-49028

| CVE-2026-64316 MEDIUM
2026-07-25 Linux GHSA-gf2r-w27p-ph9q
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

CONFIG_DYNAMIC_DEBUG required (AC:H); local ring-buffer read access needed (AV:L/PR:L); impact is key disclosure only (C:H), with no integrity or availability effect.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
5.5 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Sep 03, 2026 - 16:04 vuln.today
CVSS changed
Sep 03, 2026 - 15:52 NVD
5.5 (MEDIUM)
Patch available
Jul 25, 2026 - 11:18 EUVD
CVE Published
Jul 25, 2026 - 08:49 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 25, 2026 - 08:49 nvd
MEDIUM 5.5

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

crypto: caam - use print_hex_dump_devel to guard key hex dumps

Use print_hex_dump_devel() for dumping sensitive key material in *_setkey() and gen_split_key() to avoid leaking secrets at runtime when CONFIG_DYNAMIC_DEBUG is enabled.

AnalysisAI

Sensitive cryptographic key material handled by the Linux kernel's CAAM (Cryptographic Acceleration and Assurance Module) driver was unconditionally emitted to the kernel ring buffer via unguarded hex-dump calls in *_setkey() and gen_split_key(), exposing raw key bytes to any local user with dmesg access on kernels built with CONFIG_DYNAMIC_DEBUG. The exposure affects NXP CAAM-equipped platforms (i.MX, QorIQ SoC families) running kernel versions from approximately 5.3 through the fix commits across all active stable branches. No public exploit code exists and EPSS probability is 0.22%, but key material disclosure on a crypto-accelerator driver carries genuine confidentiality risk that the vendor-assigned CVSS (C:N/I:N/A:H) incorrectly characterizes - the real primary impact is confidentiality loss, not availability.

Technical ContextAI

The CAAM driver (drivers/crypto/caam/) provides kernel-mode access to NXP's hardware cryptographic engine present on i.MX and QorIQ SoCs, supporting AES, HMAC, and related algorithms. The vulnerable pattern is the use of print_hex_dump() - or functionally equivalent non-debug-gated dump calls - inside *_setkey() and gen_split_key(), which run during session key establishment. When the kernel is compiled with CONFIG_DYNAMIC_DEBUG and debug output is enabled for the caam module, these calls emit raw key bytes to the kernel ring buffer. The fix replaces these calls with print_hex_dump_devel(), which expands to a no-op in production builds (CONFIG_DYNAMIC_DEBUG disabled) and gates output behind dynamic-debug runtime controls otherwise. No CWE was formally assigned; CWE-532 (Insertion of Sensitive Information into Log File) is the most precise classification, with CWE-312 (Cleartext Storage of Sensitive Information) as secondary.

RemediationAI

Upgrade to a patched stable kernel: 5.10.261+, 5.15.212+, 6.1.178+, 6.6.145+, 6.12.96+, 6.18.39+, or 7.1.4+, as confirmed by the upstream stable commits at git.kernel.org/stable/c/45c0e3615e5bca5f1fc93357af8d19975c092d4f and related references in the EUVD advisory. For embedded platforms where a full kernel upgrade is not immediately feasible, the most direct compensating control is to restrict kernel ring buffer access via sysctl: set kernel.dmesg_restrict=1, which prevents non-privileged users from reading dmesg output (side effect: may impair non-root diagnostic tooling). A second option is to suppress caam debug output at runtime without rebooting by disabling it via the dynamic debug interface: echo 'module caam -p' > /sys/kernel/debug/dynamic_debug/control - this prevents the dumps from appearing without a kernel rebuild. For new builds, disabling CONFIG_DYNAMIC_DEBUG at compile time eliminates the exposure entirely. Rotating any cryptographic keys that may have been exposed during the vulnerable window is advisable on systems where dmesg logs could have been accessed.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.208 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.184 Affected
Container suse/sl-micro/6.0/kvm-os-container:2.1.3-6.218 Container suse/sl-micro/6.1/kvm-os-container:2.2.1-5.186 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.237 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.180 Affected
SUSE Linux Enterprise Real Time 15 SP7 SUSE Real Time Module 15 SP7 Fixed
SUSE Linux Micro 6.0 Fixed

Share

EUVD-2026-49028 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy