Rust 1.98.1 fixes a compiler miscompilation that can emit undefined behavior

Rust 1.98.1 was released on September 3 to correct a miscompilation introduced in Rust 1.98.0. In some circumstances, rustc generated a trait-object vtable containing a null pointer where a function pointer should have been emitted. The resulting compiled code has undefined behavior: the Rust team says this can present as a null-pointer segfault, but arbitrary effects are possible because the program has already crossed into undefined behavior. The recommended remediation for stable users is to update to 1.98.1 and rebuild relevant code.

Compiler miscompilations are different from ordinary library bugs because the defect can be baked into binaries even when application source code is correct. A team can fix its toolchain and still keep deploying an artifact compiled with the bad version unless it rebuilds. Rust’s safety guarantees also do not protect against incorrect machine code emitted by the compiler itself, so builders that moved quickly to 1.98.0 should treat the point release as a toolchain-correctness update rather than waiting for the next normal release.

Rust 1.98.0 could incorrectly place a null pointer in a trait-object vtable slot that should contain a callable function pointer. If execution reaches that slot, the binary has undefined behavior; a crash is one possible outcome but not the only one.

Installing Rust 1.98.1 prevents new builds from using the affected compiler behavior, but binaries already produced by 1.98.0 do not change automatically. Teams should identify and rebuild artifacts compiled during the affected window, especially long-lived services, release binaries and cached build outputs.

The Rust team published 1.98.1 as a point release focused on this miscompilation rather than bundling a larger feature set. That makes the operational decision simpler: stable users can update without waiting for a normal release cadence just to receive the compiler fix.