cve.bz

CVE-2026-64026 linux linux kernel: Out-of-bounds Write

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix DATA decrypt vs splice() by copying data to buffer in recvmsg This improves the fix for CVE-2026-43500. Fix the pagecache corruption from in-place decryption of a DATA packet transmitted locally by splice() by getting rid of the packet sharing in the I/O thread and unconditionally extracting the packet content into a bounce buffer in which the buffer is decrypted. recvmsg() (or the kernel equivalent) then copies the data from the bounce buffer to the destination buffer. The sk_buff then remains unmodified. This has an additional advantage in that the packet is then arranged in the buffer with the correct alignment required for the crypto algorithms to process directly. The performance of the crypto does seem to be a little faster and, surprisingly, the unencrypted performance doesn't seem to change much - possibly due to removing complexity from the I/O thread. Yet another advantage is that the I/O thread doesn't have to copy packets which would slow down packet distribution, ACK generation, etc.. The buffer belongs to the call and is allocated initially at 2K, sufficiently large to hold a whole jumbo subpacket, but the buffer will be increased in size if needed. However, to take this work, MSG_PEEK may cause a later packet to be decrypted into the buffer, in which case the earlier one will need re-decrypting for a subsequent recvmsg(). Note that rx_pkt_offset may legitimately see 0 as a valid offset now, so switch to using USHRT_MAX to indicate an invalid offset. Note also that I would generally prefer to replace the buffers of the current sk_buff with a new kmalloc'd buffer of the right size, ditching the old data and frags as this makes the handling of MSG_PEEK easier and removes the re-decryption issue, but this looks like quite a complicated thing to achieve. skb_morph() looks half way to what I want, but I don't want to have to allocate a new sk_buff.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-787 Out-of-bounds Write
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-64026 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64026?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64026?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64026 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.3 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.143
Linux6.126.12.93
Linux6.186.18.35
Linux7.07.0.11
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linuxno fix listedDEBIAN-CVE-2026-64026
Debian13linux6.12.94-1DEBIAN-CVE-2026-64026
Debian14linux7.0.12-1DEBIAN-CVE-2026-64026
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-64026
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-64026
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-64026
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 47 moreno fix listedUBUNTU-CVE-2026-64026
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1066.69~22.04.1UBUNTU-CVE-2026-64026 USN-8903-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1068.75~22.04.1UBUNTU-CVE-2026-64026 USN-8904-1
Ubuntu22.04:LTSlinux-gcp-6.8, linux-azure-6.86.8.0-1070.78~22.04.1UBUNTU-CVE-2026-64026 USN-8904-1 USN-8905-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-64026 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1066.67~22.04.1UBUNTU-CVE-2026-64026 USN-8906-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-146.146.1~22.04.1UBUNTU-CVE-2026-64026 USN-8903-2
Ubuntu22.04:LTSlinux-nvidia-6.86.8.0-1064.67~22.04.1UBUNTU-CVE-2026-64026 USN-8903-2
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-64026 USN-9025-1
45 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita23linux-ltsno fix listedBELL-CVE-2026-64026
Alpaquita25linux-lts6.12.95-r0BELL-CVE-2026-64026
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-64026

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in the Linux kernel's rxrpc protocol implementation. A local user with low privileges could use the splice() system call to supply a DATA packet whose contents are later decrypted in place by the rxrpc I/O thread while the packet is still shared with the page cache, resulting in pagecache corruption that compromises data integrity and system stability. This flaw is an improvement to the fix for CVE-2026-43500. Red Hat rated this flaw as IMPORTANT with a CVSS 3.1 score of 7.0, lower than the upstream CVEORG score of 7.8, because successfully triggering the race between in-place decryption and splice()-based packet sharing requires high attack complexity. The kernel and kernel-rt packages in Red Hat Enterprise Linux 9 and 10 and the kernel components of Red Hat In-Vehicle OS are affected, and fixes are being pursued through the delegated kernel maintenance process. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those streams.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-64026.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON