Vulnerability intelligence

CVE-2026-43284, also known as part of the "Dirty Frag" vulnerability, is a flaw identified in the Linux kernel's xfrm-ESP subsystem. This vulnerability arises from an issue where the kernel performs in-place decryption on shared `skb` (socket buffer) fragments. Specifically, when `MSG_SPLICE_PAGES` attaches pages from a pipe directly to an `skb`, the IPv4/IPv6 datagram append paths failed to mark these `skbs` with `SKBFL_SHARED_FRAG` when splicing pages into UDP `skbs`. This oversight causes the ESP input path to decrypt data in place over buffers that are not privately owned by the `skb`, allowing unprivileged processes to retain references to the resulting plaintext. This mechanism effectively provides a write primitive into the page cache. The vulnerability was introduced in January 2017 and is related to a fast path for IPsec ESP receive. It is often discussed in conjunction with CVE-2026-43500, as the combination of these two flaws can be leveraged for local privilege escalation by manipulating the page cache to corrupt privileged files.

CVE-2026-43500 is a vulnerability found within the Linux kernel's RxRPC networking subsystem, forming one half of a pair of flaws collectively dubbed "Dirty Frag." This issue arises when a non-linear socket buffer, which carries a splice-pinned page-cache reference, reaches the RxRPC authentication verification path. Instead of isolating the buffer, the kernel performs an in-place decryption directly on the referenced page-cache page. This behavior can be exploited by an unprivileged local attacker to corrupt the contents of the page-cache. By manipulating cached data in memory, an attacker could potentially overwrite sensitive system files, such as `/etc/passwd`, to achieve unauthorized access or escalate privileges.

CVE-2026-31431, dubbed "Copy Fail," is a local privilege escalation (LPE) vulnerability found within the Linux kernel's cryptographic subsystem. Specifically, it stems from a logic flaw in the `algif_aead` module of the `AF_ALG` (userspace crypto API), which leads to improper memory handling during in-place operations. This flaw allows an unprivileged local user to perform a deterministic, controlled 4-byte write into the page cache of any readable file on the system, including setuid binaries. This vulnerability has been present in Linux kernels since 2017 and impacts a wide range of major distributions, including Red Hat, SUSE, Ubuntu, and Amazon Linux. Exploitation is described as reliable, not requiring race conditions or kernel-specific offsets, and can be achieved with a small Python script. The in-memory corruption means the file on disk remains unchanged, and typical on-disk checksums would not detect the modification.

Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. From version 1.81.16 to before version 1.83.7, a database query used during proxy API key checks mixed the caller-supplied key value into the query text instead of passing it as a separate parameter. An unauthenticated attacker could send a specially crafted Authorization header to any LLM API route (for example POST /chat/completions) and reach this query through the proxy's error-handling path. An attacker could read data from the proxy's database and may be able to modify it, leading to unauthorised access to the proxy and the credentials it manages. This issue has been patched in version 1.83.7.

CVE-2026-31431, dubbed "Copy Fail," is a local privilege escalation (LPE) vulnerability found within the Linux kernel's cryptographic subsystem. Specifically, it stems from a logic flaw in the `algif_aead` module of the `AF_ALG` (userspace crypto API), which leads to improper memory handling during in-place operations. This flaw allows an unprivileged local user to perform a deterministic, controlled 4-byte write into the page cache of any readable file on the system, including setuid binaries. This vulnerability has been present in Linux kernels since 2017 and impacts a wide range of major distributions, including Red Hat, SUSE, Ubuntu, and Amazon Linux. Exploitation is described as reliable, not requiring race conditions or kernel-specific offsets, and can be achieved with a small Python script. The in-memory corruption means the file on disk remains unchanged, and typical on-disk checksums would not detect the modification.