Hi Peter, thanks for the feedback.
On 5/18/26 20:57, Peter Verbaan wrote:
After the new image is installed (and the system is rebooted), the mitigations for these fixed vulnerabilities would still be in place until a new update of the l-v-m package is installed, or the user runs `l-v-m auto` manually.
right, I'll see if there's some possibility to trigger the execution of l-v-m auto after an update of the kernel and/or during the boot process (I'll have to see what possible scenarios there are and find/offer a way to address each/most of them).
Unfortunately, I am currently running the 6.12.86+deb13-amd64 image from trixy-security (because of issues with the nvidia-kernel-dkms package), and your 'status' options only seem to check the upstream image version, without taking backported fixes into account.
absolutely - I just went with the 'easy' way first (doing the checks for testing/unstable). I'm going to work on the ones for stable/oldstable etc. next.
Regards, Daniel
