Unraid OS 7.2.5-rc.2 available

Unraid OS 7.2.5-rc.2 is now available for testing.

Changes from rc.1

Only the following items are new in rc.2:

- Updated dynamix.unraid.net to version 4.32.3

- Updated the Linux kernel to 6.12.82-Unraid

- Picked up upstream kernel fixes for CVE-2026-31430, a Linux X.509 out-of-bounds access issue triggered by specially crafted certificates

- Added a mitigation for a rare crash

Included from rc.1

This release also includes the previous rc.1 changes:

- Docker updated from 27.5.1 to 29.3.1

- Docker update includes runc fixes for CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881

- Fixed stale or uninspectable “ghost” containers showing in the Docker page

- Fixed stale Tailscale Serve/Funnel state after Docker container restarts

- Fixed mover empty-disk availability on systems with user shares enabled but no pool devices assigned

- Restored custom case-model images on the login page

- Improved registration-state refresh after license updates

- Updated libpng and php for security fixes

Full release notes: https://docs.unraid.net/unraid-os/release-notes/7.2.5/
Please test and report any issues in the Unraid bug tracker (https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback)

So this thing with random mac's generated at docker or server restart is present in this version too I guess.

https://product.unraid.net/p/7-3-0-beta-1-containers-start-with-random-mac

In my case I added --mac-address to all my containers but then I got hit with extremely slow docker service start as containers fully rebuilds every time with --mac-address present.

https://product.unraid.net/p/docker-containers-extrememly-slow-to-start

So I had to remove my --mac-address's but now my router is flooded with random macs that I manually have to remove from the offline list (you could ask how often i reboot but it does happen and every time it adds ~25 new macs as offline). Updating a container generates a new random mac and the router see traffic from the same ip but also the same ip used by several macs (I set "Fixed IP address" for my containers) creating a mess.

I mention this here because I got pm:ed by another user looking for a solution as this also happens in 7.2.5-rc.1 but I'm on 7.3.0 beta.

I understand this has changed in later docker versions. I don't know enough about how docker works to fix it myself. Before it was fine with the generated macs as docker remembered and reused them but now it's some type of random every time-thing. ;)

Edited April 21Apr 21 by Niklas

Thanks, nice to see the Kernel update too

Since upgrading from 7.2.4, I've seen this in my log files, not sure if it's an issue or not:

20:43:03 <hostname> nfsdcltrack[484481]: Unable to write to /proc/fs/nfsd/v4_end_grace: Device or resource busy
20:52:38 <hostname> nfsdcltrack[526390]: Unable to write to /proc/fs/nfsd/v4_end_grace: Device or resource busy
21:10:07 <hostname> nfsdcltrack[603065]: Unable to write to /proc/fs/nfsd/v4_end_grace: Device or resource busy

2 hours ago, warpspeed said:

Since upgrading from 7.2.4, I've seen this in my log files, not sure if it's an issue or not:

Probably related to the kernel update, but should just be a timing issue and harmless, assuming all NFS shares are working normally.

13 hours ago, JorgeB said:

Probably related to the kernel update, but should just be a timing issue and harmless, assuming all NFS shares are working normally.

Possibly this: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.12.83&id=ba4811c8b433bfa681729ca42cc62b6034f223b0

I've been running this version for several days and it's been a complete non-event for me. Everything appears to be working fine.

Can we get 7.2.5 patched for CVE-2026-31431