chore(deps): update rust crate memmap2 to v0.9.11 [security] - #50
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update rust crate memmap2 to v0.9.11 [security]#50renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
renovate
Bot
force-pushed
the
renovate/crate-memmap2-vulnerability
branch
2 times, most recently
from
June 23, 2026 19:44
91b15f4 to
ea08f4a
Compare
renovate
Bot
force-pushed
the
renovate/crate-memmap2-vulnerability
branch
2 times, most recently
from
July 20, 2026 07:43
ea08f4a to
861105a
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR contains the following updates:
0.9.10→0.9.11Unchecked pointer offset in crate
memmap2RUSTSEC-2026-0186
More information
Details
Affected versionf of
memmap2did not perform enough validation on theoffsetandlenparameters ofMmap::[unchecked_]advise_range(),MmapMut::[unchecked_]advise_ranage()and
MmapMut::flush[_async]_range().This can cause undefined behavior due to invalid values being passed to
pointer::offset()andpointer::add()when passing an out-of-bounds range to any of the affected functions.
The flaw was corrected in commit [
cee7cf0] and released in version0.9.11.The invalid pointer is not dereferenced,
but it is passed to the
madviseandmsyncsyscalls and their Windows equivalents.[
cee7cf0] https://github.com/RazrFalcon/memmap2-rs/pull/170/changes/cee7cf03a9ee095982a3c37b7aac8e3f68f1a00cSeverity
Unknown
References
This data is provided by OSV and the Rust Advisory Database (CC0 1.0).
Release Notes
RazrFalcon/memmap2-rs (memmap2)
v0.9.11Compare Source
Fixed
advice_range,unchecked_advise_range,flush_rangeandflush_async_range.Changed
Configuration
📅 Schedule: (in timezone America/Denver)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.