CVE-2026-45257

The record

The KTLS receive path decrypted each record in place, assuming that the mbufs holding received data were anonymous and safe to modify. This assumption does not hold for data placed on a socket by sendfile(2), which can reference file-backed memory directly through non-anonymous M_EXTPG pages or EXT_SFBUF mbufs. When the sender transmits such data over a loopback connection without enabling KTLS on the transmit side, the file-backed mbufs reach the receiver's decryption path unchanged. Decrypting a record in place then overwrites the backing file's page cache instead of a private copy of the data. An unprivileged local user who can read a file can overwrite its contents with data of their choosing by sending the file over a loopback connection on which they have enabled KTLS receive. The write modifies the page cache directly, so it bypasses file flags such as schg and is written back to disk. By overwriting a setuid binary or other trusted file, a local user can escalate privileges, potentially gaining full control of the affected system.

Affected packages

Related vulnerabilities

• CVE-2026-81579 In WibuKey for Windows before version 6.71, an untrusted pointer dereference in the… CWE-123
• CVE-2026-20469 In trusted_mem, there is a possible escalation of privilege due to improper input… CWE-123
• GHSA-g6pc-6676-c23j Remotion: arbitrary file write vulnerability CWE-123
• CVE-2026-30121 remotion-dev remotion v4.0.409 was discovered to contain an arbitrary file write… CWE-123
• CVE-2026-43284 In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid… CWE-123
• CVE-2026-41952 Local privilege escalation due to improper input validation. CWE-123
• CVE-2025-14857 An improper access control vulnerability exists in Semtech LoRa LR11xxx transceivers… CWE-123
• CVE-2025-69809 A write-what-where condition in p2r3 Bareiron commit 8e4d40 allows unauthenticated… CWE-123