Advisory

RUSTSEC-2026-0411

Also known as: None

Summary

Out-of-bounds read in Log2Cache::nlog2n(), nlog2n_difference() and plog2p()

Details

Log2Cache::new(n) fills its three tables with entries for 0..=n, but the
three accessor methods index those tables with get_unchecked on a value the
caller supplies. Nothing bounds the argument and nothing documents a bound, so
any value above the n the cache was built with reads past the end of the
vector. CountType is u32, so the read can land up to u32::MAX elements
away, and plog2p() returns the value it read, disclosing whatever lies there.

For example, Log2Cache::new(4) builds tables holding 5 entries (indices
0,1,2,3,4). Then cache.nlog2n(60000) reads index 60000, far outside the
allocation. Under AddressSanitizer this faults with SEGV; Miri reports it as
undefined behavior at src/log2cache.rs:42.

nlog2n_difference() is off by one further: in the affected versions new(n)
pushes n entries into that table rather than n + 1, so even
nlog2n_difference(n) is out of bounds.

This can be triggered through safe public APIs — Log2Cache::new() and any of
nlog2n(), nlog2n_difference() and plog2p() — with no unsafe required
from the caller.

Severity

Not rated by the source.

Dates

Published
2026-10-22 12:00 UTC
Modified
2026-10-26 14:00 UTC

Affected packages and fixes

dahl-salso

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.7.0 (semver)

Fixed versions

0.7.0

Fix

  • Fixed version 0.7.0
    cargo update -p dahl-salso --precise 0.7.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences