linux-kernel - [RFC] Proposal: Introducing Rust for memory-safe Linux kernel components

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAPmip_xKv6bA07apqYhyHxTNsnBitVbmcwcYE24xw2RYkDX5oQ@mail.gmail.com>
Date: Mon, 18 Aug 2025 07:43:30 -0400
From: cyber security <cs7778503@...il.com>
To: linux-kernel@...r.kernel.org
Subject: [RFC] Proposal: Introducing Rust for memory-safe Linux kernel components

I am Security Researcher [RelunSec] so let's talk about rust in linux.

Proposal: Incrementally introduce Rust for select kernel components,
focusing on modules or libraries that benefit from Rust's memory
safety guarantees while maintaining the majority of the kernel in C
for compability reason.

Example: You Can expose Rust driver apis for write kernel driver in
rust and write other component in rust if possible keep using Rust
with C binding example write 60% of C and 43%+ of Rust for compability
reason write some critical part in Rust of kernel so in 2025 for
safety reason you need switch to rust unlike 1997 C is a language
actually 2025/2026 Low Level Language will be Rust.

Experience: I"am Security Researcher. I also started write in rust
some software or even hardware and firmware developement and fix issue
with C bugs via reimplement them in Rust.

Requesting comments and discussion on feasibility, potential pitfalls,
and integration strategy.

Kinds regards

RelunSec