Skip to content
Book Open access

zBulk: Towards Automatic Compartmentalization in Rust with Zero Manual Retrofitting

Sep 2026 · Programming Languages and Operating Systems · 0 citations · 12 references
Computer Science

TL;DR

This work presents zBulk, an automatic compartmentalization system that requires zero retrofitting to application code and paves the way for flexible fine-grained compartmentalization, and shows how to design zBulk, leveraging rustc's intermediate representations.

Abstract

Memory safety is a dominant driver in security and systems research. Rust has become a viable alternative to C/C++ for systems programming because of its strong memory safety guarantees. However, it is not a silver bullet. Unsafe sections, foreign code, and compiler-soundness bugs still pose vulnerabilities. Compartmentalization splits a program into pieces and executes these in isolated, collaborating contexts. This way, the impact of a software vulnerability can, ideally, be limited to a single compartment. However, manual compartmentalization approaches are considered labor-intensive and error-prone, and require deep system expertise. We present zBulk, an automatic compartmentalization system that requires zero retrofitting to application code and paves the way for flexible fine-grained compartmentalization. We achieve this high degree of automation by leveraging static type- and call information, and language constructs that declare mutability and ownership. We show how to design zBulk, leveraging rustc's intermediate representations. We verify the approach by fully automatically compartmentalizing a relatively small systems application with a single dependency into up to eight compartments. We discuss how this number can be increased for even more flexibility. We report overhead measurements for Intel SGX as a first isolation mechanism, with more to follow.

Read PDF

Similar papers

Sep 2026

C-to-Rust Fallacy: Automatic Refactoring != Memory Security

Rust has emerged as the leading system programming language, offering strong memory and type safety guarantees without compromising performance. This positions it as a compelling alternative to traditional languages like C and C++, which are susceptible to memory security bugs. However, manually transforming C to Rust...

Hung-Mao Chen, Xu He, Bo Lu et al. · 0 citations
Book Open access Sep 2026

Beyond Zero-Cost: Understanding Rust Safety Overheads in Systems Code

Rust is increasingly used as a viable alternative to C and C++ for systems development. A central appeal of Rust is its “zero-cost” abstractions and, specifically, its ability to enforce safety without the overhead of garbage collection. In practice, however, only a subset of safety properties can be enforced staticall...

Soham Bagchi, Manvik Nanda, A. Burtsev · 0 citations
Preprint Sep 2026

UnsafeChecker: Finding Soundness Bugs in Rust Safe Abstractions

UnsafeChecker is presented, a compiler-integrated static analysis framework for detecting potential soundness violations in Rust safe abstractions, and outperforms several state-of-the-art tools, detecting 32 CVEs and covering 36 bugs with 51.6% alert-level precision.

Xi-Zhe Yin, Yao Zhang, Yang Feng et al. · 0 citations
Open access 2026

Rust Without Shortcuts: What Safety Actually Costs

Memory-unsafe languages remain the dominant root cause of severe software vulnerabilities, and national cybersecurity guidance now treats migration to memory-safe languages as a structural requirement. Automated C-to-Rust translation reports four to five percent runtime overhead, but on small programs that avoid dynami...

Juan P. Licona-Luque, L. Muñoz-Ubando, M. A. Romo-Chavero et al. · 0 citations
Open access Oct 2026

Bringing Foundational Verification to Real-World Rust Code

How to extend RefinedRust with several of the high-level abstractions that Rust provides, including traits, closures, and iterators, and in a manner such that they can be used in conjunction with unsafe code.

Lennard Gäher, Vincent Lafeychine, Sascha Kehrli et al. · 0 citations
#software testing Open access Sep 2026

LLM-Assisted Porting of Security-Critical C Libraries to Idiomatic Rust: A Multi-Model Empirical Study

Differential fuzzing reveals complementary bugs in the manual and LLM porting of security-critical C libraries to idiomatic Rust and translates these findings into concrete practical guidance for teams planning a similar migration.

Marco Parrillo, Marco Grassi, Luigi Laura · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.