Unverified50% confidenceFactExact time
In io_uring, if Rust code drops the object owning a buffer between buffer submission and completion, the kernel will still write data to the already-freed memory, causing a use-after-free vulnerability.
1
Sources
50%
Confidence
Long-term
Relevance
8/9/2026
First Seen
Sources
Rust不可移动类型与保证析构深度解析
Related Claims
UnverifiedA Use-After-Free vulnerability refers to a program retaining a dangling pointer after freeing memory and continuing to use that memory, triggering undefined behavior.70% similarVerifiedRust's ownership mechanism and borrow checker can eliminate at compile time memory safety vulnerabilities common in traditional C/C++, such as dangling pointers, buffer overflows, and data races — vulnerabilities that have historically accounted for more than 70% of serious security flaws.68% similarVerifiedRust通过所有权与借用检查机制在编译期静态验证内存访问的合法性，无需运行时垃圾回收即可避免空指针和数据竞争64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/714199API
curl https://kongchang.com/api/v1/knowledge/claims/714199MCP
get_claim(id=714199)