CVE-2026-64544

crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents

N/A
Published: July 27, 2026 at 08:10 PM UTC
Updated: October 24, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents pefile_digest_pe_contents() computes the trailing-data hash length as pelen - (hashed_bytes + certs_size). A crafted PE can make the addition exceed pelen, causing the unsigned subtraction to underflow to ~4 GiB. This is passed to crypto_shash_update() which reads out of bounds and panics on unmapped vmalloc guard pages. BUG: unable to handle page fault for address: ffffc900038d8000 Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: 0010:sha256_blocks_generic (lib/crypto/sha256.c:152) Call Trace: <TASK> __sha256_update (lib/crypto/sha256.c:208) crypto_sha256_update (crypto/sha256.c:142) verify_pefile_signature (crypto/asymmetric_keys/verify_pefile.c:436) kexec_kernel_verify_pe_sig (kernel/kexec_file.c:151) __do_sys_kexec_file_load (kernel/kexec_file.c:406) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) </TASK> Kernel panic - not syncing: Fatal exception Validate that the addition does not overflow and the result does not exceed pelen before the subtraction. Return -ELIBBAD on failure.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.17af316fc442ef23901bbfcec5af55e69ca6ce9563
Vendor states this is fixed in 627938383761fb4334b41ebe7ef438d6b8b19d60 (fixed)
Vendor states this is fixed in 6acd2fbd00f9c72aebefce63fc2e73e8f3d79061 (fixed)
Vendor states this is fixed in 7016377699b5b25b7ec3c0bf2ec3f983c7e95f7c (fixed)
Vendor states this is fixed in 803591785d33cf13b6f73ce2796e8b9e6d5e6526 (fixed)
Vendor states this is fixed in 89efd998470a93284b7ad5a20d4e0e3c6858ae8e (fixed)
Vendor states this is fixed in b798ada5a5d1cb4cc4cfa72074b1b463eca6c506 (fixed)
Vendor states this is fixed in e162bc386e71b5412425a38ee048e8d2185491b9 (fixed)
Vendor states this is fixed in f7dd32c5179d7755de18e21d5674b08f9e5cb180 (fixed)
Vendor states this is fixed in 3.17 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card