Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
smithay/wayland-rs
master @ 41d6f7f
9
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Memory Safety: 3 prior fixes. Scrutinize any change in this area.
wayland-client: most-fixed (2 issues). Treat as high-risk during review.
7 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Use After Free: User data associated with Wayland proxies can be prematurely deallocated or accessed after destruction during callback dispatch, leading to severe memory corruption. Realizing safe FFI bindings requires strict tracking of proxy lifetimes.
Memory Safety: Accessing non-Send/Sync data across thread boundaries can lead to data races and undefined behavior if thread identity is not verified at runtime.
Memory Corruption: Premature deallocation of a global's user_data prior to the explicit destruction of the global leads to memory corruption when the underlying native library attempts to reference it.