GHSA-585q-cm62-757j json
mnl has segmentation fault and invalid memory read in `mnl::cb_run`
published last yr. modified 9mo ago also RUSTSEC-2025-0142
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The function `mnl::cb_run` is marked as safe but exhibits unsound behavior when processing malformed Netlink message buffers.
Passing a crafted byte slice to `mnl::cb_run` can trigger memory violations. The function does not sufficiently validate the input buffer structure before processing, leading to out-of-bounds reads.
This vulnerability allows an attacker to cause a Denial of Service (segmentation fault) or potentially read unmapped memory by providing a malformed Netlink message.
Patch / fix
- crates.io mnl 0.3.1
- github.com/mullvad/mnl-rs@61929d1 commit
- github.com/mullvad/mnl-rs#21 pull request
Is GHSA-585q-cm62-757j in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | mnl | <0.3.1 >=0.0.0-0, <0.3.1 |
0.3.1 |
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
Sources
- GitHub Advisory GHSA-585q-cm62-757j
- OSV RUSTSEC-2025-0142
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.