mlsanityData to 7 Oct 2026

KVerus: Scalable and Resilient Formal Verification Proof Generation for Rust Code

arXiv 2605.03822 ↗First posted 5 May 2026cs.SE cs.CRcited by 5

Not on the map. Why?

Abstract (arXiv)

Formal verification provides the highest assurance of software correctness and security, but its application to large-scale, evolving systems remains a major challenge. While large language models (LLMs) have shown promise in automating proof generation, they often fail in real-world settings due to their inability to handle complex cross-module dependencies or changes in the codebase or the verification toolchain. We identify the fundamental problem as the Semantic-Structural Gap: LLMs operate on semantic code patterns, whereas formal verification is governed by rigid structural dependencies, a disconnect that leads to brittle, unsustainable proofs. To bridge this gap, we propose a new paradigm of self-adaptive verification and present KVerus, a retrieval-augmented system for Verus-based Rust verification that can adapt to an evolving software environment. KVerus constructs a dynamic knowledge base of code metadata, lemma semantics, and toolchain specifics. By combining dependency-aware program analysis, semantic lemma indexing, and error-driven self-refinement, it can navigate intricate cross-file dependencies to synthesize proofs and automatically repair proofs when faced with common evolutionary changes. Across three single-file benchmarks, KVerus verifies 80.2% of tasks, outperforming the state-of-the-art AutoVerus (56.9%) and degrades less than AutoVerus under breaking Verus updates. On three repository-level benchmarks with cross-file dependencies, KVerus achieves a 51.0% success rate, compared to 4.5% for a multi-round prompting baseline. Finally, on the Asterinas Rust OS kernel, KVerus produces upstream-accepted proofs that verify 23 previously unverified functions (21.0% of proof code) in the memory-management module. KVerus represents a significant step towards making formal verification a scalable and sustainable practice for modern, security-critical software.

Key facts. Cited by 5 papers in the map (data through 7 Oct 2026). First posted on arXiv 5 May 2026.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 7 Oct)

Citing papers per year: 2026: 5.

5 papers.

Similar, not cited

Close in wording, no citation either way

  1. 2026Reducing the Costs of Proof Synthesis on Rust Systems by Scaling Up a Seed Training Set
  2. 2024AutoVerus: Automated Proof Generation for Rust Code
  3. 2025RAG-Verus: Repository-Level Program Verification with LLMs using Retrieval Augmented Generation
  4. 2025Towards Repository-Level Program Verification with Large Language Models
  5. 2025VeruSAGE: A Study of Agent-Based Verification for Rust Systems
  6. 2026Fewer Assumptions by Design: A Reusable Skill for LLM-Assisted Verus Verification
  7. 2026SWE-Proof: Can Language Models Resolve Real-World Issues with Machine-Checked Proofs?
  8. 2026PROMISE: Proof Automation as Structural Imitation of Human Reasoning