DSM Update Version: 7.3.1-86003 Update 1

[fredbert]

Important Update

---

(2025-11-18)

Important notes​

1. Your Synology NAS may not notify you of this DSM update because of the following reasons. If you want to update your DSM to this version now, please click hereto update it manually.
   • The update is not available in your region yet. The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly.
   • Your DSM is working fine without having to update. The system evaluates service statuses and system settings to determine whether it needs to update to this version.
2. This update will restart the device.

Fixed Issues​

1. Fixed a security vulnerability.

Notes:

• This version is released in a staged rollout.

 

[fredbert]

A very similar description of fixes to the initial release notes of the recent BSM. That was later updated to list a security alert.

 

[Jan Janowski]

Doesn’t reply as a -1 though.
Though the release notes pull up as 7.3.1-1, which is the most important Part!

 

[fredbert]

And less than a day later a security alert that’s fixed by this update. There’s also a patch for DSM 7.2.2.

CVE-2025-13392 allows remote attackers to bypass authentication with prior knowledge of the distinguished name (DN)

Synology_SA_25_14 | Synology Inc.

Synology Product Security Advisory

www.synology.com

 

[Telos]

VE-2025-13392 allows remote attackers to bypass authentication with prior knowledge of the distinguished name (DN)

Synology must have their own imaginary CVE stock to cover their poor programming
Negative reports from CVE and NIST:

https://www.cve.org/CVERecord?id=CVE-2025-13392

NVD - CVE-2025-13392

nvd.nist.gov

 

[fredbert]

Given the previous BSM patch getting updated details, I opted to apply this DSM patch to both my NAS yesterday... once CloudFlare was able to grant access to download the .pat files. But it does look like it was a new vulnerability added in DSM 7.2.2, and persisted to 7.3.

 

[Jan Janowski]

Wonder if that’s what’s holding up router roll out?

So far: Both 7.3.1-1 on 3x NAS’s, and 1.3.1-14 (a 2600) are ok, but a second 2600 at -13 doesn’t see roll out.

 

[zombiephysicist]

Did the update on 1821 and 2423rp and both rebooted fine.

 

[chunwang]

Today's update: 7.2.2-72806 Update 5 to version: 7.3.1-86003. Currently, FileStation fails to start and is disabled, and cannot be fixed.

I have already tried downloading and installing FileStation-x86_64-1.4.3-1609.spk, but it still fails to start.


今天更新版本: 7.2.2-72806 Update 5到版本: 7.3.1-86003，目前file station 啟動失敗被停用，無法修復。
已經嘗試下載 FileStation-x86_64-1.4.3-1609.spk 安裝，一樣無法啟動.

 

[Rusty]

Today's update: 7.2.2-72806 Update 5 to version: 7.3.1-86003. Currently, FileStation fails to start and is disabled, and cannot be fixed.

I have already tried downloading and installing FileStation-x86_64-1.4.3-1609.spk, but it still fails to start.


今天更新版本: 7.2.2-72806 Update 5到版本: 7.3.1-86003，目前file station 啟動失敗被停用，無法修復。
已經嘗試下載 FileStation-x86_64-1.4.3-1609.spk 安裝，一樣無法啟動.

Try and use the 7.3.1-86003 Update 1 on top of this and see if that will resolve the issue.

https://global.synologydownload.com/download/DSM/criticalupdate/update_pack/86003-1/synology_broadwell_rs3617rpxs.pat?model=RS3617RPxs&bays=12&dsm_version=7.3.1&build_number=86003-1

 

[chunwang]

2025-11-20T15:29:56+08:00 RackStation systemd[1]: Started SynoAnalytics Analyzer.
2025-11-20T15:29:56+08:00 RackStation systemd[1]: Starting SynoAnalytics Analyzer...
2025-11-20T15:30:31+08:00 RackStation systemd[1]: Stopped FileStation's service unit.
2025-11-20T15:30:31+08:00 RackStation systemd[1]: Reloaded SynoAnalytics Analyzer.
2025-11-20T15:30:31+08:00 RackStation systemd[1]: Reloaded Synology SCGI.
2025-11-20T15:30:32+08:00 RackStation systemd[1]: pkg-SynoAnalytics-analyzer.service holdoff time over, scheduling restart.
2025-11-20T15:30:32+08:00 RackStation systemd[1]: Started SynoAnalytics Analyzer.
2025-11-20T15:30:32+08:00 RackStation systemd[1]: Starting SynoAnalytics Analyzer...
2025-11-20T15:30:32+08:00 RackStation systemd[1]: Reloading.
2025-11-20T15:30:33+08:00 RackStation systemd[1]: Device sys-subsystem-net-devices-eth1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.3/0000:0a:00.0/net/eth2 and /sys/devices/pci0000:00/0000:00:1c.6/0000:0c:00.0/net/eth1
2025-11-20T15:30:33+08:00 RackStation systemd[1]: Device sys-subsystem-net-devices-eth7.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.6/0000:0c:00.0/net/eth1 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0d:00.0/net/eth0
2025-11-20T15:30:33+08:00 RackStation systemd[1]: Device sys-subsystem-net-devices-eth0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/eth3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0d:00.0/net/eth0
2025-11-20T15:30:33+08:00 RackStation systemd[1]: Cannot add dependency job for unit syno-mlnx-rdma-modules-load.service, ignoring: Unit syno-mlnx-rdma-modules-load.service is masked.
2025-11-20T15:30:33+08:00 RackStation systemd[1]: Cannot add dependency job for unit syno-qlogic-rdma-modules-load.service, ignoring: Unit syno-qlogic-rdma-modules-load.service is masked.
2025-11-20T15:30:33+08:00 RackStation systemd[1]: Starting FileStation's service unit...
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Reloaded Synology SCGI.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Reloaded Synology SCGI.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: pkgctl-FileStation.service: main process exited, code=exited, status=1/FAILURE
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Failed to start FileStation's service unit.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Unit pkgctl-FileStation.service entered failed state.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Triggering OnFailure= dependencies of pkgctl-FileStation.service.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Cannot add dependency job for unit syno-mlnx-rdma-modules-load.service, ignoring: Unit syno-mlnx-rdma-modules-load.service is masked.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Cannot add dependency job for unit syno-qlogic-rdma-modules-load.service, ignoring: Unit syno-qlogic-rdma-modules-load.service is masked.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: pkgctl-FileStation.service failed.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Starting Do rollback actions after pkgctl-XXX...
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Stopped "start/stop synovfs daemon".
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Stopped "FileStation Thumbnail Daemon".
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Reloaded Synology Schedule Daemon.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Reloaded SynoAnalytics Analyzer.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Reloaded Synology SCGI.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Stopping Synology Task Scheduler Vmtouch...
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Started Synology Task Scheduler Vmtouch.
2025-11-20T15:30:34+08:00 RackStation systemd[1]: Starting Synology Task Scheduler Vmtouch...
2025-11-20T15:30:35+08:00 RackStation systemd[1]: Started Do rollback actions after pkgctl-XXX.
2025-11-20T15:30:36+08:00 RackStation systemd[1]: pkg-SynoAnalytics-analyzer.service holdoff time over, scheduling restart.
2025-11-20T15:30:36+08:00 RackStation systemd[1]: Started SynoAnalytics Analyzer.
2025-11-20T15:30:36+08:00 RackStation systemd[1]: Starting SynoAnalytics Analyzer...
2025-11-20T15:30:37+08:00 RackStation systemd[1]: Unit pkg-synorelayd.service cannot be reloaded because it is inactive.
2025-11-20T15:30:37+08:00 RackStation systemd[1]: Reloaded Nginx.

 

[Rusty]

And systemctl restart pkgctl-FileStation.service via ssh does not help as well?

If not, I would open a ticket with Synology support on this matter and have them have a look at it.

 

[chunwang]

root@RackStation:~# systemctl restart pkgctl-FileStation.service
Job for pkgctl-FileStation.service failed. See "systemctl status pkgctl-FileStation.service" and "journalctl -xe" for details.
root@RackStation:~# systemctl status pkgctl-FileStation.service -l
● pkgctl-FileStation.service - FileStation's service unit
Loaded: loaded (/usr/local/lib/systemd/system/pkgctl-FileStation.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2025-11-20 16:34:42 CST; 11s ago
Process: 20471 ExecStart=/bin/bash -c /usr/syno/sbin/synopkgctl start $SELF && /bin/touch /var/packages/$SELF/enabled (code=exited, status=1/FAILURE)
Main PID: 20471 (code=exited, status=1/FAILURE)

Nov 20 16:34:42 RackStation synopkgctl[20557]: SYNOPKG: Rollback sdk-plugin for FileStation when 0x0000 (done)
Nov 20 16:34:42 RackStation synopkgctl[20474]: SYNOPKGMGR: Failed to acquire startup resource, pkg=[FileStation].[0x0000 (null):0]
Nov 20 16:34:42 RackStation synopkgctl[20474]: plugin_action.c:76 synoplugin: [POST][package][package_action][MAIN] Plugin Action Start
Nov 20 16:34:42 RackStation synopkgctl[20474]: plugin_action.c:76 synoplugin: [POST][package][package_action][MAIN] Runtime: 0.006s
Nov 20 16:34:42 RackStation synopkgctl[20474]: SYNOPKGMGR: Failed to start package, pkg=[FileStation] context=[{"action":"start","beta":false,"error":{"code":272,"description":"Failed to acquire startup worker","worker_msg":[]},"finished":true,"language":"","last_stage":"prepare_start","package":"FileStation","pid":20474,"stage":"start_failed","status":"start_failed","status_code":272,"status_description":"failed to start on previous startup","success":false,"username":"","version":"1.4.3-1609"}]
Nov 20 16:34:42 RackStation systemd[1]: pkgctl-FileStation.service: main process exited, code=exited, status=1/FAILURE
Nov 20 16:34:42 RackStation systemd[1]: Failed to start FileStation's service unit.
Nov 20 16:34:42 RackStation systemd[1]: Unit pkgctl-FileStation.service entered failed state.
Nov 20 16:34:42 RackStation systemd[1]: Triggering OnFailure= dependencies of pkgctl-FileStation.service.
Nov 20 16:34:42 RackStation systemd[1]: pkgctl-FileStation.service failed.
root@RackStation:~#

 

[chunwang]

 

[Rusty]

root@RackStation:~# systemctl restart pkgctl-FileStation.service
Job for pkgctl-FileStation.service failed. See "systemctl status pkgctl-FileStation.service" and "journalctl -xe" for details.
root@RackStation:~# systemctl status pkgctl-FileStation.service -l
● pkgctl-FileStation.service - FileStation's service unit
Loaded: loaded (/usr/local/lib/systemd/system/pkgctl-FileStation.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2025-11-20 16:34:42 CST; 11s ago
Process: 20471 ExecStart=/bin/bash -c /usr/syno/sbin/synopkgctl start $SELF && /bin/touch /var/packages/$SELF/enabled (code=exited, status=1/FAILURE)
Main PID: 20471 (code=exited, status=1/FAILURE)

Nov 20 16:34:42 RackStation synopkgctl[20557]: SYNOPKG: Rollback sdk-plugin for FileStation when 0x0000 (done)
Nov 20 16:34:42 RackStation synopkgctl[20474]: SYNOPKGMGR: Failed to acquire startup resource, pkg=[FileStation].[0x0000 (null):0]
Nov 20 16:34:42 RackStation synopkgctl[20474]: plugin_action.c:76 synoplugin: [POST][package][package_action][MAIN] Plugin Action Start
Nov 20 16:34:42 RackStation synopkgctl[20474]: plugin_action.c:76 synoplugin: [POST][package][package_action][MAIN] Runtime: 0.006s
Nov 20 16:34:42 RackStation synopkgctl[20474]: SYNOPKGMGR: Failed to start package, pkg=[FileStation] context=[{"action":"start","beta":false,"error":{"code":272,"description":"Failed to acquire startup worker","worker_msg":[]},"finished":true,"language":"","last_stage":"prepare_start","package":"FileStation","pid":20474,"stage":"start_failed","status":"start_failed","status_code":272,"status_description":"failed to start on previous startup","success":false,"username":"","version":"1.4.3-1609"}]
Nov 20 16:34:42 RackStation systemd[1]: pkgctl-FileStation.service: main process exited, code=exited, status=1/FAILURE
Nov 20 16:34:42 RackStation systemd[1]: Failed to start FileStation's service unit.
Nov 20 16:34:42 RackStation systemd[1]: Unit pkgctl-FileStation.service entered failed state.
Nov 20 16:34:42 RackStation systemd[1]: Triggering OnFailure= dependencies of pkgctl-FileStation.service.
Nov 20 16:34:42 RackStation systemd[1]: pkgctl-FileStation.service failed.
root@RackStation:~#

Maybe you could try and force the uninstall via command line:

synopkg uninstall FileStation

and than install it synopkg install <location_of_FileStation_SPK>

By the looks of it, the FS previously failed to start, causing a lock of some sort. I'm sure if you will not be able to uninstall it and remove it, that support will do it remotely.

 

[Jan Janowski]

720+ Login greeted me with 7.3.1-1 update to be installed! I just Did That, What?? 2 days ago!!!!
This was on "Experimental" 720+ that was first to install 7.3.1-1....
And I reported that that install 2 days ago displays without -1!! (as does subsequent 720+ and 718+)

So I let it install! What can go wrong?

Quick update- no packages check, active insight or hybrid share!

And NOW REPORTS: 7.3.1-1 after install !!

Could it be a later update? Or, Roll out that hasn't hit other 720+ or 718+? They still say the 2 days ago 7.3.1-1 install that displays without -1 and says is Current.... ???

Edit 8PM EST 11/20/2025:
Must be another roll out version: 2nd 720+ - that didn’t see update at 3PM Now sees-1 update! Installed as earlier one did: 7.3.1-1 now seen, No Hybrid Share or Active Insight, nor Packages check...

Took two 7.3.1-1 installs but Synology assistant now see's the "Update-1" on both 720+'s

No update seen on 718+ as yet... Maybe tomorrow... ??

Did check - both 720+ & 718+ 7.3.1-1 update files are dated Nov 10, but the update within NAS must be getting file from another dated source - or is this a feature of Roll Out? If so, 720+ has Rolled Out, and 718+ hasn’t?

 

[chunwang]

Maybe you could try and force the uninstall via command line:

synopkg uninstall FileStation

and than install it synopkg install <location_of_FileStation_SPK>

By the looks of it, the FS previously failed to start, causing a lock of some sort. I'm sure if you will not be able to uninstall it and remove it, that support will do it remotely.

We notified Synology customer service yesterday, and things have now returned to normal. Thank you for your assistance.

 

[Jan Janowski]

Awoke to find another 7.3.1-1 Roll Out awaiting on 718+.
(Yesterday verified second 7.3.1-1 worked with all my apps on 720+), Which is good - because my 718+ is doing the most heavy workload here.

Installed 7.3.1-1 On 718+: Displays as 7.3.1-1

All NAS’s are fine. Now.

Checked to see if SRM V1.3.1-14 has rolled out. Nope.