** Description changed: + [ Impact ] + + * The bug is a rare race condition, which under the right circumstances, + could lead to database corruption. + + * The bug only affects databases in WAL mode when there are two or more + database connections open on the same file, in separate threads or + processes, and when those two connections attempt to write or checkpoint at + the same instant. + + * The upstream patch adds a check of the checkpoint and live WAL salts + before WAL gets actually sync to disk. + + [ Test Plan ] + + * See the bug-attached repro.sh script. + Considering the nature of the issue (niche race), I've kept it out of + autopkgtest to avoid test flakiness. + + [ Where problems could occur ] + + * The change has already been shipped and backported by upstream. + + * The patch affects sqlite databases enabling WAL journal mode, which + is not the default. + Erroneous branching would make the WAL skip the checkpoint sync. + + [ Original description ] + I wonder if the Ubuntu/Debian packages could include a fix for the serious WAL corruption bug which has been fixed in SQLite 3.51.3 (2026-03-13). It has been present in all SQLite releases since 3.7.0 (2010-07-21). https://www.sqlite.org/wal.html#walresetbug Backports of the fix are available for some earlier releases as well: 3.44.6 (https://sqlite.org/src/info/863c171b76cd36e0) and 3.50.7 (https://sqlite.org/src/info/c7facf7ac58d2cda).
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2171337 Title: sqlite wal corruption bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2171337/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
