TrueNAS 25.10.6 is Now Available

The TrueNAS team is pleased to release TrueNAS 25.10.6!

This release updates the Linux kernel and NVIDIA GPU driver to address security vulnerabilities and maintain driver support. It also fixes Fibre Channel crashes on Enterprise systems, an NFS server hang, false drive self-test alerts, deduplication table pruning errors, and directory services configuration changes.

Notable changes:

  • Updates the Linux kernel to the latest 6.12 LTS release (v6.12.99) (NAS-142007).
    TrueNAS 25.10.6 advances the kernel from v6.12.95 in the previous release to v6.12.99. This update includes fixes for more than 250 upstream CVEs, including several critical issues in components TrueNAS uses: a reference count underflow in the TCP request socket queue (CVE-2026-53260), an NFS server failure to release layout state after an unsuccessful lease request (CVE-2026-53399), out-of-bounds reads in the NVMe target discovery log page and authentication reply handling (CVE-2026-64320 and CVE-2026-64319), unbounded transfer lengths in the siw and rtrs-srv RDMA drivers (CVE-2026-64268 and CVE-2026-64269), a traffic control action handling issue (CVE-2026-64530), a BPF device map issue with fragmented frames (CVE-2026-64355), and an out-of-bounds read in TIPC broadcast acknowledgment handling (CVE-2026-64450).

  • Updates the NVIDIA GPU driver to version 580.173.02 (NAS-142008).
    The 570 driver branch included in earlier releases reached end of life and does not build against the 6.12.99 kernel. TrueNAS now ships the 580 long-term support branch, which NVIDIA supports through June 2028.

  • Fixes crashes when Fibre Channel target mode starts or stops (NAS-142014, NAS-142018).
    If the Fibre Channel target driver detached while the adapter still delivered traffic, an incoming login or abort request could reference memory that was already released and crash the system. TrueNAS now checks for this condition and drops or rejects the request instead. TrueNAS also reports an error and leaves target mode disabled when target registration fails, rather than enabling the port anyway.

  • Fixes an NFS server hang that could stop the server from expiring clients (NAS-142112).
    A leaked callback reference on an NFSv4 delegation could leave client teardown waiting forever. After this happened, no further NFSv4 client cleanup could complete, and the rpc.nfsd process could not be stopped without a system reboot. A brief network interruption on a client that held a write delegation was enough to trigger it. This release includes two upstream kernel fixes that prevent the leak.

  • Fixes false drive self-test failure alerts and errors when TrueNAS reads drive SMART data (NAS-140652, NAS-141951).
    TrueNAS read the oldest NVMe self-test result instead of the newest, so some drives raised a “failed a SMART selftest” alert for a test that did not fail. A drive that returned a self-test entry without a status also produced a KeyError that filled /var/log/middlewared.log with errors and stopped the SMART alert check from completing. TrueNAS now handles both cases so self-test alerts reflect actual drive results.

  • Fixes several issues with deduplication table (DDT) pruning (NAS-142045).
    Pruning could select the wrong entries when the target age matched a histogram boundary, and the youngest age bin did not start at zero, so the age of recent entries could be misjudged. Counters could also overflow on tables with more than two billion entries. Pruning now uses the time the histogram build starts as the age cutoff and handles large tables correctly.

  • Fixes the Save button that stayed unavailable on the directory services configuration screen (NAS-138641).
    After an upgrade from 25.04 to 25.10, the Save button in Credentials > Directory Services could stay greyed out no matter which setting changed, which blocked all directory services configuration changes. The button now becomes available when a setting changes.

  • Adds the ability to change the ALUA setting when the standby controller is unreachable (NAS-142057).
    On Enterprise HA systems, TrueNAS blocked changes to the ALUA setting when it could not reach the standby controller. Administrators can now turn ALUA on or off while the standby controller is down.

  • Improves failover speed by moving a remote disk scan out of the critical failover path (NAS-141988, NAS-140406).
    On Enterprise HA systems, failover asked the other controller to rescan its disks before it imported the pool, which could stall failover for a minute or more while services stayed offline. The request now runs outside the critical failover section and does not wait for a response.

  • Fixes audit entry parsing that could restart the audit handler (NAS-139610).
    A local authentication event could produce an audit message with a hostname value that contained spaces and its own key and value pairs. The audit parser did not expect this format, which raised an exception and forced truenas_audit_handler to restart. The parser now handles these messages correctly.

See the Release Notes and changelog for more details.

25.10.6 Documentation : https://www.truenas.com/docs/scale/25.10
Download : https://www.truenas.com/download-truenas-community-edition

11 Likes

Downloaded, seems to have installed fine. My ongoing (since like v24) issues with my NIC that require a post-init to even connect to LAN are still ongoing, but I generally blame my NIC itself for that & have a workaround.

I don’t see anything obviously broken. VMs, Apps, Reporting, etc seem to be working well.

Reporting on “Dashboard” seemed to be slow to load in & gave an We are working in the background to generate relevant data. Please try again in a few minutes. error, but clearing cache looks to have resolved it.

Transcoding & drivers for my 3050 seem to still be working as well.

Edit: One thing I noticed that I like is in “Data Protection” tab, generally after an update I’d have my Snapshot state be reset until the next scheduled event, which was a very minor annoyance. Seems to actually correctly show now.

Updated my system remotely just now. Everything seemed to have started up fine. A small fix may be that disk device naming seems to be stable now. sg_map -i now shows consistent sd* device name mapping to sg* SCSI endpoint addresses.

2 Likes

Did the upgrade.
Thanks to all developers. Great work!

1 Like

all went well here.

1 Like

Just updated both my systems from remote, all went well.

Thank you Team(s) :+1:

Ps: Give it a bit of time, to apply the update :wink:

2 Likes

CPU Usage seems to be through the roof again with VMs. I have one one VM playing video. Within the VM, the CPU usage shows as 10%. Yet in the TrueNAS GUI, the CPU usage of all 24 cores shows as 30-50%. Something is inefficient here.

1 Like

CPU Usage seems to be through the roof again with VMs

Not for me. One VM, running Ubuntu Server, 1% avg. 27C, on Ryzen 5600X.

Is it only when you’re playing video? What GPU setup are you using?

There seems to be a regression caused by upstream Linux kernel updates introduced with 25.10.5.

Only certain guest OS are affected, e.g. Windows 11 with enabled Hyper V enlightments.

Those kernel changes in combination with KVM prevent the CPU from entering C-States correctly, which leads to high usage and/or high power consumption.

We probably need to tweak some parameters (stimer and synic). I am currently looking into a way to do this via midclt but did not find a solution yet.

I don’t see this update (or 25.10.5). How do I get it?

I’m running 25.10.4. I updated from 24.10 (I think) to that. I noticed I haven’t seen any updates in a while and came here.

Updates just says “current version: 25.10.4” and “System is up to date”

What Update train are you showing on that screen? System - Update.
Does your show Mission Critical? Are you on the Community Edition of the first page of your GUI?
Another issue could be internet access is blocked to the update server.

Yes it says “Mission Critical” but I never set that. Should it be another one?

If you switch to GA, you will see the updates. MC was an option before and you must have never switched. MC is more for the Enterprise customers.

I booted back to 25.10.4 and I don’t have a MC option. I think that was from a previous version upgrade that stuck with you.

3 Likes

Ah okay, that’s weird I don’t remember doing that but who knows. Yes I’m just a home lab guy here, so I don’t need that.

Yes I switched to General and it showed up! Thanks and sorry for the extra work!

1 Like

Over 10,000 systems have updated to 25.10.6 with very good success.

This is looking like a very high-quality version which we will promote for Community and Enterprise users. However, we do not think this is the end of the CVE tsunami…

The cpu usage increase is general and not related to playing video. I was playing video on an emby client and video was simple pass throughout without transcoding. Fundamentally I see see that even when VMs are idle, I see cpu usage of ~10% in 25.10.6, up from 5% in 25.10.5. I have seen this increases previously after updating from 25.10.3 to 25.10.4, and then it went down for 25.10.5. My VMs use VirtIO for NIC but disks are AHCI.

Please post when you find a solution. My affected OS are indeed Windows VMs.

Hi, I see in JIRA that SCALE-25.10.6 (Goldeye) is UNRELEASED. Is this correct?