Read the docs
TI-2026-45591 Aliases CVE-2026-64026GHSA-97h7-gm2v-v84m

rxrpc: Fix DATA decrypt vs splice() by copying data to buffer in recvmsg

Priority LOW 35CWE-362Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Partial Red Hat: 2 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-787 and the CVSS impact.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00109 1st percentileScored 2026-11-07
Fix Partial Linux (Linux): 6.6.143, 6.12.93, 6.18.35 +2Red Hat: 2 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
LinuxLinux5.3 and later6.6.143, 6.12.93, 6.18.35, 7.0.11, 7.1Patch availableCNA
  • Linux VendorLinux Affected 5.3 and later Fixed in 6.6.143, 6.12.93, 6.18.35, 7.0.11, 7.1 Patch available CNA

CPE configurations NVD · 8

CPEVersionsRoleVendor
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*5.3.1 to before 6.6.143; 6.7 to before 6.12.93; 6.13 to before 6.18.35; 6.19 to before 7.0.11VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.3:-:*:*:*:*:*:*5.3VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.3:rc7:*:*:*:*:*:*5.3 rc7VulnerableLinux
cpe:2.3:o:linux:linux_kernel:5.3:rc8:*:*:*:*:*:*5.3 rc8VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*7.1 rc1VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*7.1 rc2VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*7.1 rc3VulnerableLinux
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*7.1 rc4VulnerableLinux
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions 5.3.1 to before 6.6.143; 6.7 to before 6.12.93; 6.13 to before 6.18.35; 6.19 to before 7.0.11 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.3:-:*:*:*:*:*:* Versions 5.3 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.3:rc7:*:*:*:*:*:* Versions 5.3 rc7 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:5.3:rc8:*:*:*:*:*:* Versions 5.3 rc8 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* Versions 7.1 rc1 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* Versions 7.1 rc2 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* Versions 7.1 rc3 Vulnerable ·Linux
  • cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* Versions 7.1 rc4 Vulnerable ·Linux

Remediation

  • Fix · CNA Linux (Linux) Fixed in 6.6.143, 6.12.93, 6.18.35, 7.0.11, 7.1

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise Linux 10AffectedNo fix yet
Red Hat Enterprise Linux 9AffectedNo fix yet
Not affected: 3 products
  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-64026
  2. 2026-10-03 Alias added: GHSA-97h7-gm2v-v84m
  3. 2026-10-13 Affected versions changed · Red Hat
  4. 2026-10-13 Weakness changed · NVD
  5. 2026-10-16 CISA SSVC decision points changed
  6. 2026-10-19 Weakness changed · CISA ADP

References

  • TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
  • TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
  • TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
  • TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
  • TI-2021-05514 Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACE KEVCVSS 3.1HIGH 8.3
See all 15278 →

Sources