Patch musl's CVE-2026-6042 and CVE-2026-40200#155171
Patch musl's CVE-2026-6042 and CVE-2026-40200#155171rust-bors[bot] merged 1 commit intorust-lang:mainfrom
Conversation
|
rustbot has assigned @Mark-Simulacrum. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
Nominating for 1.96-beta and 1.95-stable. @rustbot label +beta-nominated +stable-nominated |
|
@bors try jobs=dist-arm-linux-musl,dist-i586-gnu-i586-i686-musl,dist-various-1,dist-various-2,dist-x86_64-musl,test-various |
This comment has been minimized.
This comment has been minimized.
Patch musl's CVE-2026-6042 and CVE-2025-26519 try-job: dist-arm-linux-musl try-job: dist-i586-gnu-i586-i686-musl try-job: dist-various-1 try-job: dist-various-2 try-job: dist-x86_64-musl try-job: test-various
- [CVE-2026-6042] is a denial of service in `iconv`. - [CVE-2026-40200] is an out-of-bounds write in `qsort`. Neither is relevant to Rust itself, but they could be used in mixed- language projects that link with our `self-contained/libc.a`. [CVE-2026-6042]: https://www.openwall.com/lists/oss-security/2026/04/09/19 [CVE-2026-40200]: https://www.openwall.com/lists/musl/2026/04/10/3
|
Sorry, I mixed up my CVE numbers and links when writing the commit message, now fixed. The patches were the right ones though, so the try build should still be testing the right thing. |
|
r=me in principle, and I think I'll probably pull this into stable artifact building ~Monday. Not sure we really have a team to approve the backport (compiler? libs?) but it feels like it should be uncontroversial. |
|
@bors r+ p=1 |
Rollup of 4 pull requests Successful merges: - #155171 (Patch musl's CVE-2026-6042 and CVE-2026-40200) - #153630 (Deprioritize doc(hidden) re-exports in diagnostic paths) - #152613 (unsafe keyword docs: bring back unsafe_op_in_unsafe_fn lint discussion) - #155142 (impl const Residual for ControlFlow)
Rollup merge of #155171 - cuviper:musl-cves, r=Mark-Simulacrum Patch musl's CVE-2026-6042 and CVE-2026-40200 - [CVE-2026-6042] is a denial of service in `iconv`. - [CVE-2026-40200] is an out-of-bounds write in `qsort`. Neither is relevant to Rust itself, but they could be used in mixed-language projects that link with our `self-contained/libc.a`. [CVE-2026-6042]: https://www.openwall.com/lists/oss-security/2026/04/09/19 [CVE-2026-40200]: https://www.openwall.com/lists/musl/2026/04/10/3
|
Leaving the beta nomination (and acceptance) so this goes into 1.96, manually bringing it into 1.95 (not technically a stable backport). |
|
And included it in the beta branch PR as well, so should be handled. |
[stable] Rust 1.95.0 release https://forge.rust-lang.org/release/process.html#stable-pr This also backports: * Patch musl's CVE-2026-6042 and CVE-2026-40200 #155171 and cherry picks latest release notes. r? me
[beta] branch 1.96 release This follows https://forge.rust-lang.org/release/process.html#beta-pr to branch beta. It also includes a backport of: * Patch musl's CVE-2026-6042 and CVE-2026-40200 #155171 since it landed after beta branched but per security discussion is getting backported direct to stable. r? me
[stable] Rust 1.95.0 release https://forge.rust-lang.org/release/process.html#stable-pr This also backports: * Patch musl's CVE-2026-6042 and CVE-2026-40200 #155171 and cherry picks latest release notes. r? me
[beta] branch 1.96 release This follows https://forge.rust-lang.org/release/process.html#beta-pr to branch beta. It also includes a backport of: * Patch musl's CVE-2026-6042 and CVE-2026-40200 #155171 since it landed after beta branched but per security discussion is getting backported direct to stable. r? me
iconv.qsort.Neither is relevant to Rust itself, but they could be used in mixed-language projects that link with our
self-contained/libc.a.