Dirty Frag: Universal Linux LPE

Dirty Frag is a vulnerability class discovered and reported by Hyunwoo Kim (@V4bel) that chains two Linux kernel vulnerabilities — CVE-2026-43284 (xfrm-ESP Page-Cache Write) and CVE-2026-43500 (RxRPC Page-Cache Write) — to obtain root privileges on major Linux distributions. The vulnerabilities have an effective lifetime of approximately 9 years. Unlike race-condition exploits, Dirty Frag is a deterministic logic bug with no timing window, no kernel panic on failure, and a very high success rate. The two vulnerabilities are chained because xfrm-ESP (present on most distributions) requires namespace creation privileges, which Ubuntu sometimes blocks via AppArmor, while RxRPC (loaded by default on Ubuntu) does not require namespace privileges — together they cover each other's blind spots across all major distributions. Tested distributions include Ubuntu 24.04.4, RHEL 10.1, openSUSE Tumbleweed, CentOS Stream 10, AlmaLinux 10, and Fedora 44. The repository includes proof-of-concept exploit code and mitigation instructions (removing the vulnerable modules and clearing the page cache). Dirty Frag is a descendant of the Dirty Pipe vulnerability class and shares the same sink as Copy Fail, meaning systems with Copy Fail mitigations remain vulnerable to Dirty Frag. 

https://github.com/V4bel/dirtyfrag

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

SecObserve: Simplified Vulnerability and License Management for CI/CD Pipelines

 SecObserve is an open-source tool for managing vulnerabilities and licenses in software development and cloud environments. It integrates various vulnerability scanners into CI/CD pipelines using GitLab CI templates and GitHub Actions for streamlined setup. It offers a centralized dashboard for assessing and reporting vulnerabilities, with tools for filtering, sorting, and evaluating results. SecObserve supports automation and manual assessments to focus on resolving critical issues.  https://github.com/MaibornWolff/SecObserve/tree/dev
Read more

Secure Vibe Coding Guide: Best Practices for Writing Secure Code

Ken Huang's "Secure Vibe Coding Guide" emphasizes the importance of integrating security into the software development lifecycle. The guide provides best practices for writing secure code, including input validation, proper authentication mechanisms, and secure data storage techniques. It also highlights the necessity of regular code reviews and staying updated with the latest security vulnerabilities and patches. By following these guidelines, developers can create applications that are resilient against common security threats and contribute to a safer digital environment.  https://kenhuangus.substack.com/p/secure-vibe-coding-guide
Read more