The Switch 6.0.0 system update was released on September 18, 2018. This Switch update was released for the following regions: ALL.
Security flaws fixed: <fill this in manually later, see the updatedetails page from the ninupdates-report page(s) once available for now>.
Official ALL change-log:
- Nintendo Switch Online* features and functionality have been added, including:
- Save Data Cloud Backup
- User your internet connection to back up game save data for compatible games
- Some games are not compatible with Save Data Cloud
- To back up save data or download a previous backup, head to System Settings > Data Management > Save Data Cloud Backup
- *Nintendo Switch Online membership (sold separately) and Nintendo Account required for online play. Not available in all countries. Internet access required for online features. Save Data Cloud backup available in compatible games. Terms apply. To learn more, click here.
- Added the following system functionality
- Upload up to four Album screenshots at once on supported social network services
- Only one captured video can be uploaded at once
- Select from six new Captain Toad icons for your user
- To edit your user icon, head to your My Page on the top left of the Home Menu > Profile
- Play your digital software and content on non-primary consoles by linking your Nintendo Account
- The term "active console" has been renamed "primary console" in Nintendo eShops
- Playing software in multiple consoles has certain restrictions
- Display of Nintendo Switch News articles will be limited to match the restricted software parental controls setting selections
- Please note that the restriction will only apply to News articles distributed after the release of version 6.0.0.
- Change the layout of the USB keyboard to the desired language
- To change the language, head to the System Settings > System > USB Keyboard
- Removed the following system functionality
- After installing the system update, it will no longer be possible to unlink your Nintendo Account from your Nintendo Switch user
- General system stability improvements to enhance the user's experience, including:
- Compatibility improvements have been made for a controller licensed by Nintendo
- All sysmodules were updated.
- Most 8XX titles were updated.
- All applets except "error" and "cabinet" were updated.
- 1 new title was added: olsc-sysmodule.
- New services were added, see here.
This new sysmodule handles cloud saves.
- Accidentially exported symbols have been renamed:
nn::kern::board::NXand now contains the class
ResumeEntryis now a non-static method of
- Kernel now reserves 1024 pages (1MB) of memory in SYSTEM memregion/pool for use by applets (1 at a time) for personal mmheap.
- Memory regions arrange changed, APPLET has 6MB less in all memory arranges.
- Maximum number of sessions and events both increased by 100.
- Kernel mmheap size decreased to 0x10DF000 bytes (was 0x1117000), the both KMemoryBlock pools' capacity is unchanged, but less page tables can be allocated.
- Kernel now properly reports DRAM size in default reslimit.
- Two new svcGetInfoTypes: types 21 and 22. These are like type 6 and 7, but without the contiguous, in-security-carveout, personalmmheap allocation.
- KASLR was changed to invoke smcGetRandomBytes(8) each time, instead of using Mersenne Twister.
- Another layer of randomization has been added to slabheaps (before, it was just the order of slabheaps): an array of N (= 21 = number of slabheaps) random integers, in range (0, 0x200000) is now constructed, sorted via bubble sort; at each slabheap construction the heap offset is further incremented by
array[id+1]-array[id], then page rounded.
- With the exception of KSessionRequest which is not in any KObjectAllocator, all KAutoObject types now use an intrusive rbtree instead of an intrusive list for their KObjectAllocator membership. Comparison key is PID for processes, thread ID for threads, address for others (using a new virtual method).
- A new anonymous KAutoObject type, which sole purpose is to hold a comparison key, is now used for thread lookup by ID.
- Breaking changes in svcGetFutureThreadInfo, which has potentially been renamed. Signature and use case have radically changed, it is now:
Result svcGetFutureThreadInfo(ThreadInfo *outThreadInfo, u64 *outTid, Handle debugHandle, s64 timeout).
- Huge scheduler force-pause and last thread reporting refactor:
- Scheduling flags are now u16 and force-pause flags are 3-nibble-long instead of 1.
- The requirements and mechanism for force-pausing (activity svc, debug, etc.) threads have been considerably simplified:
- It used to delay the force-pause after end-of-svc, and used some convoluted mechanism.
- The condition is now "a thread is force-pausable iff no thread is waiting for a kernel mutex it is holding", mechanism is just ORRing scheduling status with force-pause flags now. Appropriate changes have been made to accomodate for this change.
- Abovementionned convoluted mechanism has been refactored, too, but remains unused.
- When the scheduler selects a process's thread, it now stored the selected thread in an array in the KProcess, for information. It also stores in itself and in array in the selected KProcess the number of times it detected a core being idle before load balancing. Used by BreakDebugProcess.
- All threads created and started in kernel main() are started force-paused with flags=0x100. This fixes the hypotetical case where a compromised KIP would perform gmmuhax and dump the INI1 (which is stored in APPLICATION -- KIPs are only started after all of them have been loaded). They are unpaused after all KIPs have been created.
- GetThreadContext3 (unprivileged SVC) now dumps TPIDR_EL0.
- DebugActiveProcess now returns 0xFA01 if an attempt to debug the current process is made -- instead of possibly deadlocking
- GetDebugThreadContext and SetDebugThreadContext now return 0xF001 if flags > 15. Additionally, their functionality is now restricted to threads that have been force-paused for debug, not just any kind of force-paused threads anymore.
- ContinueDebugEvent now returns 0xF001 if flags > 15 as well.
- svcSleepSystem has been refactored. Instead of the initiator thread manually starting the sleep handler threads then storing a weak reference to itself, the handler threads are started in kernel init in main() immediately after their creation, and two mutexes are used: one for the initiator/covering svcSleepSystem, another for the handler threads. This likely fixes an UaF or race condition.
- If svcReturnFromException passes the exception the KDebug, ie. if the argument errorCode is not 0, and if the latter has DontCatchExceptions set, the process is terminated (unless errorCode is 0x10001).
- Performance improvements to svcInvalidateProcessDataCache.
System update report(s):