CVE-2026-43500: Dirty Frag: Linux RxRPC page-cache write
- Vendor
- Linux
CVE-2026-43500 is a local privilege-escalation vulnerability in the Linux kernel's RxRPC DATA and RESPONSE packet processing. The handlers rxrpc_input_call_event() and rxrpc_verify_response() linearize socket buffers before security operations only when skb_cloned() is true. Non-cloned buffers containing externally owned paged fragments or chained fragment lists can therefore undergo in-place decryption, with skb_to_sgvec() mapping shared pages directly into cryptographic scatter-gather lists. Fragments originating from splice() into a UDP socket can reference file-backed page-cache memory, allowing decryption to corrupt cached contents of files the attacker cannot write. The vulnerability is the RxRPC component of Dirty Frag.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
A low-privileged local attacker can corrupt page-cache contents of readable, otherwise non-writable files and use a modified privileged executable to obtain root privileges. Successful exploitation can compromise system confidentiality and integrity and cause denial of service. Cached contents can differ from the unchanged on-disk file. Container workloads may also expose the host kernel when the required RxRPC functionality is reachable; guest-to-host virtualization escape requires a separate vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Where RxRPC/AFS is unnecessary, disable the relevant functionality and prevent rxrpc and afs modules from loading, following vendor guidance. Account for automatic module loading; an unloaded module alone does not establish protection. Restrict untrusted local workloads and access while patching is pending. Disabling unprivileged user namespaces alone does not mitigate this RxRPC vulnerability. Module restrictions do not reverse page-cache corruption caused by prior exploitation.
Remediation
Patch, then assume compromise.
Install the distribution or product vendor's kernel update for CVE-2026-43500 and reboot into the corrected kernel. The upstream correction extends the unsharing condition in both affected handlers to include skb_has_frag_list() and skb_has_shared_frag(), ensuring externally shared fragments are copied before decryption. Echo guidance specifies linux and related packages version 6.1.170-3 or later; this version threshold is specific to that package stream. Validate the running kernel against the applicable vendor advisory because downstream fixes may be backported.
Exploits
13 exploits validated by Mallory's analysis. Hidden: 28 rejected by Mallory's analysis as not a working exploit; 3 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-43500 exploited in the wild?
- Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-43500?
- Yes. Mallory tracks 13 public exploits or proofs of concept for CVE-2026-43500, the earliest disclosed May 8, 2026.
- Is there a patch for CVE-2026-43500?
- Install the distribution or product vendor's kernel update for CVE-2026-43500 and reboot into the corrected kernel. The upstream correction extends the unsharing condition in both affected handlers to include skb_has_frag_list() and skb_has_shared_frag(), ensuring externally shared fragments are copied before decryption.
- What products are affected by CVE-2026-43500?
- Linux Kernel.
- How severe is CVE-2026-43500?
- CVE-2026-43500 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 94.1% (100th percentile) as of Nov 16, 2026.
Recent activity
273 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.