<html><body><div dir="auto">Control: tags -1 + fixed-upstream patch<br><br>Hi,<br><br>Upstream issue #1758 is still open, but upstream fixed the code on master<br>in this commit:<br><br> <a href="https://www.google.com/url?q=https://gitlab.freedesktop.org/poppler/poppler/-/commit/94c499fe&source=gmail&ust=1793769493640000&sa=E">https://www.google.com/url?q=https://gitlab.freedesktop.org/poppler/poppler/-/commit/94c499fe&source=gmail&ust=1793769493640000&sa=E</a><br> "Fix shift overflow when a sampled function has 32-bit samples"<br> (2026-09-28, after 26.07.0)<br><br>--- a/poppler/Function.cc<br>+++ b/poppler/Function.cc<br>@@ -373,7 +373,8 @@<br>- bitMask = (1 << sampleBits) - 1;<br>+ // sampleBits can be 32, so shift a 64-bit value to avoid overflowing int<br>+ bitMask = static_cast<unsigned int>((1ULL << sampleBits) - 1);<br><br>It applies cleanly to poppler-26.07.0's Function.cc, and none of<br>26.07.0-3's debian/patches touch that file. I checked only that it<br>applies; I did not do a full poppler build.<br><br>On severity: sampleBits is limited to 1..32 just above. The only value<br>that reaches the undefined shift is 32, and the sampleBits == 32 case<br>reads the four bytes directly in its own branch, so bitMask is never<br>used there. The issue is therefore the undefined-behaviour shift itself,<br>as UBSan reports it; there is no memory-safety impact in this code path.<br>That may support no-dsa/unimportant for stable, with the one-line<br>cherry-pick for unstable.<br><br>Thanks!<br></div></body></html>