I’ve been patiently waiting for the TrueNas software status page to tell me to upgrade from my current 25.04.2.6 to 25.10.3[.1] (I’m extremely conservative, not wanting to bust things and then having to spend hours repairing it by methods I don’t really understand).
I noticed that the advice for me was to upgrade now and hence take care of this vulnerability. Last night I completed the upgrade, then found my GPU wasn’t working, so downgraded, found it was still broken, vaguely remembered something to do with UUIDs from a year ago, tried to run the commands I found (they didn’t work), rebooted into the newer kernel, tried again (they didn’t work) then found that the API had changed and I needed to use -j rather than -job and then I worked through this.
Having had to spend hours repairing this bust system using methods I didn’t really understand, my temper was thus worsened when I realised it was my fault because I had assumed that the enterprise ready upgrade would work with all of my hardware, not realising that my Nvidia card is now out of date.
So - I hope that a minor point backport or whatever it is called will be released because I am now “stuck” on 25.04.2.6 until such a time as I can afford a new graphics card. But, thanks to @Lycestra I was able to implement that local fix and I have done an init script (with help from AI to explain where to find it and implement it) which will keep me “safe” when I occasionally reboot even if TN don’t up-issue.
edit, after several days of reading:
and
and
so if I can summon up the courage, it appears that there’s a way for me to upgrade TN to the latest version whilst maintaining compatibility with older Nvidia drivers (which might include my P620).