There are 6 open security issues in trixie.
Among the 107 debian patches available in version 122.0.6261.128-1 of the package, we noticed the following issues:
commit 50f5be4d05ef0251dd8819e4555417341e6eb1c3 Author: Andres Salomon <dilinger@queued.net> Date: Tue Mar 19 02:43:22 2024 -0400 add a rust crate build fix commit bbf5ca2f1c483d0f3e8e8a472d030e755108f9e4 Author: Andres Salomon <dilinger@queued.net> Date: Tue Mar 19 01:46:44 2024 -0400 move std-to-address.patch from fixes/ to upstream/; document v124 removal Upstream realized that std::to_address is broken, and with https://chromium-review.googlesource.com/c/chromium/src/+/5307601 they began switching back to base::to_address. For 123 we still need it, but the commit below is in 124 so we can drop this patch then. commit cc318b731178fa93ef0ab7b18980df16aefbc56e Author: Nick Diego Yamane <nickdiego@igalia.com> Date: Tue Feb 27 03:51:45 2024 +0000 switch away from std::to_address This is a semi-mechanical change, which shouldn't imply in any functional change. It's one step forward to ban std::to_address in favor of its SFINAE-compatible base::to_address wrapper. commit b58c1737bf2498812e8c12b24935a0e7797e5945 Author: Andres Salomon <dilinger@queued.net> Date: Tue Mar 19 01:28:02 2024 -0400 a bunch more prep for 123 We get to finally drop disable/angle-perftests.patch, yay! Replaced with angle_build_tests=false The commit we reverted in bookworm/undo-internal-alloc.patch was fixed by https://chromium-review.googlesource.com/c/chromium/src/+/5231905 "[PA] Fix InternalAllocator for GCC builds" commit f0242ab7196f5b1477127310eb92f9a21a4ba45e Author: Andres Salomon <dilinger@queued.net> Date: Mon Mar 18 14:45:52 2024 -0400 start preparing v123