Repository navigation
fix: bump memmap2 to 0.9.11 (RUSTSEC-2026-0186) - #1771
Merged
Legend-Master merged 1 commit intoJul 17, 2026
Merged
Conversation
Contributor
Package Changes Through 9eedd73There are 1 changes which include wry with minor Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
Legend-Master
approved these changes
Jul 17, 2026
Legend-Master
left a comment
Legend-Master
left a comment
Contributor
There was a problem hiding this comment.
Thanks!
Also you'll need to sign your commits for me to merge this
memmap2 0.9.5 is pulled in via winit (a dev-dependency of wry) -> smithay-client-toolkit / sctk-adwaita (Linux Wayland decoration theming). Affected versions under-validated the offset/len parameters on Mmap::advise_range() and friends, allowing an out-of-bounds pointer to reach the madvise/msync syscalls (undefined behavior, though the invalid pointer is never dereferenced). A plain `cargo update -p memmap2` resolves to the patched 0.9.11 with no other bumps needed. Cargo.lock only, no source changes. Verified `cargo check --workspace` passes. Fixes tauri-apps#1770
albatrossflyon-coder
force-pushed
the
fix/memmap2-rustsec
branch
from
July 17, 2026 03:01
eed91cf to
9eedd73
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1770
memmap2was locked at 0.9.5, pulled in viawinit(a dev-dependency of wry) →smithay-client-toolkit/sctk-adwaita(Linux Wayland window-decoration theming).RUSTSEC-2026-0186: affected versions under-validated the
offset/lenparameters onMmap::[unchecked_]advise_range(),MmapMut::[unchecked_]advise_range(), andMmapMut::flush[_async]_range(), allowing an out-of-bounds value to reachpointer::offset()/pointer::add()before being passed to themadvise/msyncsyscalls (or Windows equivalents). The invalid pointer is never dereferenced, but passing it to those syscalls is undefined behavior. Fixed upstream inmemmap20.9.11.Note this dependency chain is dev-dependency-only (Linux/Wayland decoration theming for wry's own examples), not part of the published library's runtime graph on other platforms — lower real-world exposure than a direct runtime dependency, but worth clearing for
cargo auditcleanliness and Linux dev builds.A plain
cargo update -p memmap2resolves cleanly to 0.9.11 with no other version bumps required.Cargo.lockonly, no source changes. Verifiedcargo check --workspacepasses.