openharmony 鸿蒙 OpenHarmony-v6.0.0.1-release

2026-08-25 浏览 (1)

OpenHarmony 6.0.0.1 Release

Version Description

OpenHarmony 6.0.0.1 Release provides enhanced system security over OpenHarmony 6.0 Release by rectifying certain known vulnerabilities in open-source components such as Linux kernel, and system stability issues.

Version Mapping

Table 1 Version mapping of software and tools

Software/ToolVersionRemarks
OpenHarmony6.0.0.1 ReleaseN/A
Public SDKOhos_sdk_public 6.0.0.48 (API Version 20 Release)This toolkit is intended for application developers and does not contain system APIs that require system permissions. The SDK obtained by default through DevEco Studio is the Public SDK.
(Optional) HUAWEI DevEco Studio6.0.0 ReleaseRecommended for OpenHarmony application development.
To be provided after release.
(Optional) HUAWEI DevEco Device Tool4.0 ReleaseRecommended for application development for OpenHarmony smart devices.
Click here.

Source Code Acquisition

Prerequisites

  1. Register your account with GitCode.

  2. Register an SSH public key for access to GitCode.

  3. Install the git client and git-lfs, and configure user information.

    git config --global user.name "yourname"
    git config --global user.email "your-email-address"
    git config --global credential.helper store
    
  4. Install the repo tool.

    curl -s https://gitcode.com/oschina/repo/raw/fork_flow/repo-py3 > /usr/local/bin/repo  #If you do not have the permission, download the tool to another directory and add that directory to environment variables. chmod a+x /usr/local/bin/repo
    pip3 install -i https://repo.huaweicloud.com/repository/pypi/simple requests
    

Acquiring Source Code Using the repo Tool

Method 1 (recommended)

Use the repo tool to download the source code over SSH. (You must have an SSH public key for access to GitCode.)

  • Obtain the source code from the version branch. You can obtain the latest source code of the specified version branch, which includes all changes up to the time you run the commands.

    repo init -u git@gitcode.com:openharmony/manifest.git -b OpenHarmony-6.0-Release --no-repo-verify
    repo sync -c
    repo forall -c 'git lfs pull'
    
  • Obtain the source code from the version tag, which is the same as that released with the version.

    repo init -u git@gitcode.com:openharmony/manifest.git -b refs/tags/OpenHarmony-v6.0.0.1-Release --no-repo-verify
    repo sync -c
    repo forall -c 'git lfs pull'
    

Method 2

Use the repo tool to download the source code over HTTPS.

  • Obtain the source code from the version branch. You can obtain the latest source code of the specified version branch, which includes all changes up to the time you run the commands.

    repo init -u https://gitcode.com/openharmony/manifest -b OpenHarmony-6.0-Release --no-repo-verify
    repo sync -c
    repo forall -c 'git lfs pull'
    
  • Obtain the source code from the version tag, which is the same as that released with the version.

    repo init -u https://gitcode.com/openharmony/manifest -b refs/tags/OpenHarmony-v6.0.0.1-Release --no-repo-verify
    repo sync -c
    repo forall -c 'git lfs pull'
    

Acquiring Source Code from Mirrors

Table 2 Mirrors for acquiring source code

Source CodeVersionMirrorSHA-256 ChecksumSoftware Package SizeRemarks
Full code base (for mini, small, and standard systems)6.0.0.1 ReleaseDownloadDownload55.1 GBSuggestion: Before compilation, run the following commands to eliminate environmental interference: 1. repo forall -c 'git reset --hard;git clean -fdx;git lfs pull'
2. **./build/prebuilts_download.sh -skip-ssl **
Hi3861 solution (binary)6.0.0.1 ReleaseDownloadDownload28.7 MB/
Hi3516 solution-LiteOS (binary)6.0.0.1 ReleaseDownloadDownload353.3 MB/
Hi3516 solution-Linux (binary)6.0.0.1 ReleaseDownloadDownload234.8 MB/
RK3568 standard system solution (binary) ROM package6.0.0.1 ReleaseDownloadDownload3.6 GB/
RK3568 standard system solution (binary) XTS package6.0.0.1 ReleaseDownloadDownload4.1 GB/
Public SDK package for the standard system (macOS)6.0.0.48DownloadDownload1.0 GB/
Public SDK package for the standard system (macOS-M1)6.0.0.48DownloadDownload1.2 GB/
Public SDK package for the standard system (Windows/Linux)6.0.0.48DownloadDownload3.0 GB/

What's New

N/A

Fixed Bugs and Security Issues

Table 3 Resolved issues

Issue No.Description
280sysfreeze occurred in resource_schedule_service due to SERVICE_BLOCK, stuck at libstandby_service.z.so.
1698cppcrash occurred in the OS_DfxWatchdog thread under the multimodalinput process, crash stack: libunwinder.z.so
12365[Program access control] Authorization failed when the non-transparent window occludes the position/pastes the control.
7191cppcrash occurred in the OS_IPC_1_1483 thread under the com.ohos.medialibrary.medialibrarydata process, crash stack: libmedialibrary_data_extension.z.so
1688cppcrash occurred in the OS_DfxWatchdog thread under the camera_host process, crash stack: libunwinder.z.so
341jscrash occurred in the com.ohos.note process, crash stack: confirm
828appfreeze occurred in com.ohos.settings due to THREAD_BLOCK_6S
613jscrash occurred in the com.ohos.systemui process, crash stack: createDataShare
6157cppcrash occurred in the OS_IPC_2_2781 thread under the camera_host process, crash stack: libcamera_host_vdi_impl_1.0.z.so
1485cppcrash occurred in the OS_FFRT_2_3 thread under the resource_schedule_service process, crash stack: Not mapped
11717cppcrash occurred in the OS_IPC_10_16215 thread under the com.ohos.mms process, crash stack: libark_jsruntime.so
11961[Window] Authorization failed when the paste control is occluded by the input method.
11960[Window] Authorization failed when the paste control is occluded by a child window.
64924cppcrash occurred in the OS_IPC_4_16933 thread under the com.ohos.mms process, crash stack: libace_compatible.z.so
539cppcrash occurred in the OS_FFRT_Delay thread under the locationhub process, crash stack: libhilog.so
295jscrash occurred in the com.ohos.mms process, stack name: deleteAction
296jscrash occurred in the com.ohos.mms process, stack name: anonymous
63972cppcrash occurred in the m.ohos.contacts thread under the com.ohos.contacts process, crash stack: libace_compatible.z.so
744jscrash occurred in the com.ohos.photos process, stack name: onPhotoChanged
96[Subsystem upgrade] The application crashes when the user clicks to download the installation package during software update.
4923cppcrash occurred in the OS_IPC_1_598 thread under /system/bin/bootanimation process, crash stack: libmedia_foundation.z.so

Table 4 Fixed security vulnerabilities

Vulnerability Ticket No.Description
CVE-2025-40049[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2024-38594[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2024-47674[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53673[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53520[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39902[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53482[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53596[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53594[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53491[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2022-49054[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-40016[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-40064[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-40105[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-40102[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-40035[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-40021[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-40054[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-40077[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39902[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_6.6.
CVE-2022-50552[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53588[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53577[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39931[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39913[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39905[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2022-50445[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39806[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_6.6.
CVE-2025-39913[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_6.6.
CVE-2025-39914[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_6.6.
CVE-2025-39931[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_6.6.
CVE-2025-39946[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_6.6.
CVE-2025-38732[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39702[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39994[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39683[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-38694[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39689[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39730[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-38680[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39760[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-38702[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39724[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2023-53221[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.
CVE-2025-39749[Vulnerability] [OpenHarmony-6.0-Release] A vulnerability exists in kernel_linux_5.10.

Known Issues

Table 5 Known issues

Issue No.DescriptionImpactTo Be Resolved By
23366Web suite execution failed during 6.0 Release XTS testing -xts_acts-AtomGit.Failure of individual certification items.2025-12-30

你可能感兴趣的鸿蒙文章

openharmony 鸿蒙 OpenHarmony-v5.0.0-release

openharmony 鸿蒙 OpenHarmony-v1.1.5-LTS

openharmony 鸿蒙 OpenHarmony-v4.0-beta1

openharmony 鸿蒙 OpenHarmony-v3.0.3-LTS

openharmony 鸿蒙 OpenHarmony-1-1-0-LTS

openharmony 鸿蒙 OpenHarmony-v3.1.5-release

openharmony 鸿蒙 OpenHarmony-v3.2-beta3

openharmony 鸿蒙 OpenHarmony-v3.0.8-LTS

openharmony 鸿蒙 OpenHarmony-v3.2-beta1

openharmony 鸿蒙 OpenHarmony-v4.1.2-release

  • 所属分类: 后端技术
  • 本文标签: 软件 鸿蒙
  • 版权声明: 本文链接 https://seaxiang.com/blog/fCQW2mlR