Sign in
Sign up
Explore
Enterprise
Education
Search
Help
Terms of use
About Us
Explore
Enterprise
Education
Gitee Premium
Gitee AI
AI teammates
Sign in
Sign up
Fetch the repository succeeded.
description of repo status
Open Source
>
Other
>
Operation System
&&
Donate
Please sign in before you donate.
Cancel
Sign in
Scan WeChat QR to Pay
Cancel
Complete
Prompt
Switch to Alipay.
OK
Cancel
Watch
Unwatch
Watching
Releases Only
Ignoring
128
Star
73
Fork
333
src-openEuler
/
kernel
Closed
Code
Issues
1197
Pull Requests
35
Wiki
Insights
Pipelines
Service
JavaDoc
PHPDoc
Quality Analysis
Jenkins for Gitee
Tencent CloudBase
Tencent Cloud Serverless
悬镜安全
Aliyun SAE
Codeblitz
SBOM
Don’t show this again
Update failed. Please try again later!
Remove this flag
Content Risk Flag
This task is identified by
as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
CVE-2025-40048
Backlog
#ID3WG6
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2025-10-28 20:42
一、漏洞信息 漏洞编号:[CVE-2025-40048](https://nvd.nist.gov/vuln/detail/CVE-2025-40048) 漏洞归属组件:[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.4.0,6.6.0 CVSS V4.0分值: BaseScore:N/A None Vector: 漏洞简述: In the Linux kernel, a race condition vulnerability exists in the uio_hv_generic driver. The driver s default interrupt mask setting logic is flawed, as the interrupt mask value should be completely controlled by user space. If the mask bit gets changed by the driver concurrently with user mode operating on the ring, the mask bit may be set when it is supposed to be clear, causing the user-mode driver to miss an interrupt and leading to a system hang.Specifically, when the driver sets the inbound ring buffer interrupt mask to 1, the host does not interrupt the guest on the UIO VMBus channel. However, setting the mask does not prevent the host from putting a message in the inbound ring buffer. This results in the host putting a message into the ring buffer without interruption. Subsequently, when user space code in the guest sets the inbound ring buffer interrupt mask to 0 and waits for an interrupt via pread(), since there s already a message in the ring buffer, no new interrupt is generated, causing pread() to wait indefinitely.The fix removes all instances where interrupt_mask is changed, while keeping the one in set_event() unchanged to enable user space control of the interrupt mask by writing 0/1 to /dev/uioX. 漏洞公开时间:2025-10-28 20:15:38 漏洞创建时间:2025-10-28 20:42:32 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2025-40048 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40204 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40200 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38705 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40055 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.115 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.111 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40141 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37828 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39694 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.109 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38011 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40110 | | | | https://git.kernel.org/stable/c/37bd91f22794dc05436130d6983302cb90ecfe7e | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40082 | | | | https://bugs.mageia.org/show_bug.cgi?id=34721 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40134 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40169 | | | | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2765 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40179 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40120 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40192 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38729 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40171 | | | | https://linux.oracle.com/cve/CVE-2025-40048.html | | | | https://advisories.mageia.org/MGASA-2025-0309.html | | | | https://git.kernel.org/stable/c/b15b7d2a1b09ef5428a8db260251897405a19496 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40178 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40125 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40129 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40187 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-21915 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40183 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40164 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39703 | | | | https://linux.oracle.com/errata/ELSA-2025-28049.html | | | | https://lore.kernel.org/linux-cve-announce/2025102814-CVE-2025-40048-3bce@gregkh/T/#u | | | | https://bugzilla.redhat.com/show_bug.cgi?id=2406741 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38234 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40035 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40140 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40211 | | | | https://git.kernel.org/stable/c/01ce972e6f9974a7c76943bcb7e93746917db83a | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38349 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.108 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38214 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40048 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40201 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38100 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37839 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.110 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40109 | | | | https://linux.oracle.com/errata/ELSA-2025-28040.html | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.114 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37891 | | | | https://git.kernel.org/stable/c/e29587c07537929684faa365027f4b0d87521e1b | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.106 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.116 | | | | https://linux.oracle.com/errata/ELSA-2025-28048.html | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39964 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37785 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.112 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39931 | | | | https://www.cve.org/CVERecord?id=CVE-2025-40048 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39940 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40176 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38173 | | | | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2766 | | | | https://git.kernel.org/stable/c/65d40acd911c7011745cbbd2aaac34eb5266d11e | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40123 | | | | https://git.kernel.org/stable/c/a44f61f878f32071d6378e8dd7c2d47f9490c8f7 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38084 | | | | https://advisories.mageia.org/MGASA-2025-0310.html | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40088 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39751 | | | | https://security-tracker.debian.org/tracker/CVE-2025-40048 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40084 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38581 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40167 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40194 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40173 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37812 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40190 | | | | https://nvd.nist.gov/vuln/detail/CVE-2024-36357 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40198 | | | | https://lore.kernel.org/linux-cve-announce/2025102814-CVE-2025-40048-3bce@gregkh/T | | | | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2767 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39938 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40153 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.113 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40053 | | | | https://bugs.mageia.org/show_bug.cgi?id=34713 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-23150 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-22080 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40202 | | | | http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-40048 | | | | https://advisory.echohq.com/cve/CVE-2025-40048 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37863 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40206 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38717 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39692 | | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://git.kernel.org/stable/c/a44f61f878f32071d6378e8dd7c2d47f9490c8f7 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/01ce972e6f9974a7c76943bcb7e93746917db83a | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/2af39ab5e6dc46b835a52e80a22d0cad430985e3 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/37bd91f22794dc05436130d6983302cb90ecfe7e | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/e29587c07537929684faa365027f4b0d87521e1b | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/b15b7d2a1b09ef5428a8db260251897405a19496 | | ljqc | | | | https://git.kernel.org/stable/c/37bd91f22794dc05436130d6983302cb90ecfe7e | | cvelistv5 | | | | https://git.kernel.org/stable/c/b15b7d2a1b09ef5428a8db260251897405a19496 | | cvelistv5 | | | | https://git.kernel.org/stable/c/01ce972e6f9974a7c76943bcb7e93746917db83a | | cvelistv5 | | | | https://git.kernel.org/stable/c/e29587c07537929684faa365027f4b0d87521e1b | | cvelistv5 | | | | https://git.kernel.org/stable/c/65d40acd911c7011745cbbd2aaac34eb5266d11e | | cvelistv5 | | | | https://git.kernel.org/stable/c/a44f61f878f32071d6378e8dd7c2d47f9490c8f7 | | cvelistv5 | | | | https://git.kernel.org/stable/c/2af39ab5e6dc46b835a52e80a22d0cad430985e3 | | cvelistv5 | | | | https://git.kernel.org/stable/c/540aac117eaea5723cef5e4cbf3035c4ac654d92 | | cvelistv5 | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:uio_hv_generic: Let userspace take care of interrupt maskRemove the logic to set interrupt mask by default in uio_hv_genericdriver as the interrupt mask value is supposed to be controlledcompletely by the user space. If the mask bit gets changedby the driver, concurrently with user mode operating on the ring,the mask bit may be set when it is supposed to be clear, and theuser-mode driver will miss an interrupt which will cause a hang.For eg- when the driver sets inbound ring buffer interrupt mask to 1,the host does not interrupt the guest on the UIO VMBus channel.However, setting the mask does not prevent the host from putting amessage in the inbound ring buffer. So let’s assume that happens,the host puts a message into the ring buffer but does not interrupt.Subsequently, the user space code in the guest sets the inbound ringbuffer interrupt mask to 0, saying “Hey, I’m ready for interrupts”.User space code then calls pread() to wait for an interrupt.Then one of two things happens:* The host never sends another message. So the pread() waits forever.* The host does send another message. But because there’s already a message in the ring buffer, it doesn’t generate an interrupt. This is the correct behavior, because the host should only send an interrupt when the inbound ring buffer transitions from empty to not-empty. Adding an additional message to a ring buffer that is not empty is not supposed to generate an interrupt on the guest. Since the guest is waiting in pread() and not removing messages from the ring buffer, the pread() waits forever.This could be easily reproduced in hv_fcopy_uio_daemon if we delaysetting interrupt mask to 0.Similarly if hv_uio_channel_cb() sets the interrupt_mask to 1,there’s a race condition. Once user space empties the inbound ringbuffer, but before user space sets interrupt_mask to 0, the host couldput another message in the ring buffer but it wouldn’t interrupt.Then the next pread() would hang.Fix these by removing all instances where interrupt_mask is changed,while keeping the one in set_event() unchanged to enable userspacecontrol the interrupt mask by writing 0/1 to /dev/uioX.The Linux kernel CVE team has assigned CVE-2025-40048 to this issue. openEuler评分: 6.2 Vector:CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H 受影响版本排查(受影响/不受影响): 1.openEuler-20.03-LTS-SP4(4.19.90):受影响 2.openEuler-22.03-LTS-SP3(5.10.0):受影响 3.openEuler-22.03-LTS-SP4(5.10.0):受影响 4.openEuler-24.03-LTS(6.6.0):受影响 5.openEuler-24.03-LTS-SP1(6.6.0):受影响 6.openEuler-24.03-LTS-SP2(6.6.0):受影响 7.master(6.12.33):不受影响 8.openEuler-24.03-LTS-Next(6.6.0):不受影响 修复是否涉及abi变化(是/否): 1.master(6.12.33):否 2.openEuler-20.03-LTS-SP4(4.19.90):否 3.openEuler-22.03-LTS-SP3(5.10.0):否 4.openEuler-22.03-LTS-SP4(5.10.0):否 5.openEuler-24.03-LTS(6.6.0):否 6.openEuler-24.03-LTS-Next(6.6.0):否 7.openEuler-24.03-LTS-SP1(6.6.0):否 8.openEuler-24.03-LTS-SP2(6.6.0):否 原因说明: 1.openEuler-24.03-LTS(6.6.0):正常修复 2.openEuler-24.03-LTS-SP1(6.6.0):正常修复 3.openEuler-24.03-LTS-SP2(6.6.0):正常修复 4.openEuler-20.03-LTS-SP4(4.19.90):不修复-超出修复范围 5.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围 6.openEuler-22.03-LTS-SP4(5.10.0):不修复-超出修复范围 7.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 8.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
一、漏洞信息 漏洞编号:[CVE-2025-40048](https://nvd.nist.gov/vuln/detail/CVE-2025-40048) 漏洞归属组件:[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.4.0,6.6.0 CVSS V4.0分值: BaseScore:N/A None Vector: 漏洞简述: In the Linux kernel, a race condition vulnerability exists in the uio_hv_generic driver. The driver s default interrupt mask setting logic is flawed, as the interrupt mask value should be completely controlled by user space. If the mask bit gets changed by the driver concurrently with user mode operating on the ring, the mask bit may be set when it is supposed to be clear, causing the user-mode driver to miss an interrupt and leading to a system hang.Specifically, when the driver sets the inbound ring buffer interrupt mask to 1, the host does not interrupt the guest on the UIO VMBus channel. However, setting the mask does not prevent the host from putting a message in the inbound ring buffer. This results in the host putting a message into the ring buffer without interruption. Subsequently, when user space code in the guest sets the inbound ring buffer interrupt mask to 0 and waits for an interrupt via pread(), since there s already a message in the ring buffer, no new interrupt is generated, causing pread() to wait indefinitely.The fix removes all instances where interrupt_mask is changed, while keeping the one in set_event() unchanged to enable user space control of the interrupt mask by writing 0/1 to /dev/uioX. 漏洞公开时间:2025-10-28 20:15:38 漏洞创建时间:2025-10-28 20:42:32 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2025-40048 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40204 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40200 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38705 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40055 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.115 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.111 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40141 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37828 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39694 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.109 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38011 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40110 | | | | https://git.kernel.org/stable/c/37bd91f22794dc05436130d6983302cb90ecfe7e | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40082 | | | | https://bugs.mageia.org/show_bug.cgi?id=34721 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40134 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40169 | | | | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2765 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40179 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40120 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40192 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38729 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40171 | | | | https://linux.oracle.com/cve/CVE-2025-40048.html | | | | https://advisories.mageia.org/MGASA-2025-0309.html | | | | https://git.kernel.org/stable/c/b15b7d2a1b09ef5428a8db260251897405a19496 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40178 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40125 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40129 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40187 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-21915 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40183 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40164 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39703 | | | | https://linux.oracle.com/errata/ELSA-2025-28049.html | | | | https://lore.kernel.org/linux-cve-announce/2025102814-CVE-2025-40048-3bce@gregkh/T/#u | | | | https://bugzilla.redhat.com/show_bug.cgi?id=2406741 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38234 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40035 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40140 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40211 | | | | https://git.kernel.org/stable/c/01ce972e6f9974a7c76943bcb7e93746917db83a | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38349 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.108 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38214 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40048 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40201 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38100 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37839 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.110 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40109 | | | | https://linux.oracle.com/errata/ELSA-2025-28040.html | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.114 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37891 | | | | https://git.kernel.org/stable/c/e29587c07537929684faa365027f4b0d87521e1b | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.106 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.116 | | | | https://linux.oracle.com/errata/ELSA-2025-28048.html | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39964 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37785 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.112 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39931 | | | | https://www.cve.org/CVERecord?id=CVE-2025-40048 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39940 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40176 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38173 | | | | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2766 | | | | https://git.kernel.org/stable/c/65d40acd911c7011745cbbd2aaac34eb5266d11e | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40123 | | | | https://git.kernel.org/stable/c/a44f61f878f32071d6378e8dd7c2d47f9490c8f7 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38084 | | | | https://advisories.mageia.org/MGASA-2025-0310.html | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40088 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39751 | | | | https://security-tracker.debian.org/tracker/CVE-2025-40048 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40084 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38581 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40167 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40194 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40173 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37812 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40190 | | | | https://nvd.nist.gov/vuln/detail/CVE-2024-36357 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40198 | | | | https://lore.kernel.org/linux-cve-announce/2025102814-CVE-2025-40048-3bce@gregkh/T | | | | https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2767 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39938 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40153 | | | | https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.113 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40053 | | | | https://bugs.mageia.org/show_bug.cgi?id=34713 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-23150 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-22080 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40202 | | | | http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-40048 | | | | https://advisory.echohq.com/cve/CVE-2025-40048 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-37863 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-40206 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-38717 | | | | https://nvd.nist.gov/vuln/detail/CVE-2025-39692 | | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://git.kernel.org/stable/c/a44f61f878f32071d6378e8dd7c2d47f9490c8f7 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/01ce972e6f9974a7c76943bcb7e93746917db83a | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/2af39ab5e6dc46b835a52e80a22d0cad430985e3 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/37bd91f22794dc05436130d6983302cb90ecfe7e | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/e29587c07537929684faa365027f4b0d87521e1b | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/b15b7d2a1b09ef5428a8db260251897405a19496 | | ljqc | | | | https://git.kernel.org/stable/c/37bd91f22794dc05436130d6983302cb90ecfe7e | | cvelistv5 | | | | https://git.kernel.org/stable/c/b15b7d2a1b09ef5428a8db260251897405a19496 | | cvelistv5 | | | | https://git.kernel.org/stable/c/01ce972e6f9974a7c76943bcb7e93746917db83a | | cvelistv5 | | | | https://git.kernel.org/stable/c/e29587c07537929684faa365027f4b0d87521e1b | | cvelistv5 | | | | https://git.kernel.org/stable/c/65d40acd911c7011745cbbd2aaac34eb5266d11e | | cvelistv5 | | | | https://git.kernel.org/stable/c/a44f61f878f32071d6378e8dd7c2d47f9490c8f7 | | cvelistv5 | | | | https://git.kernel.org/stable/c/2af39ab5e6dc46b835a52e80a22d0cad430985e3 | | cvelistv5 | | | | https://git.kernel.org/stable/c/540aac117eaea5723cef5e4cbf3035c4ac654d92 | | cvelistv5 | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:uio_hv_generic: Let userspace take care of interrupt maskRemove the logic to set interrupt mask by default in uio_hv_genericdriver as the interrupt mask value is supposed to be controlledcompletely by the user space. If the mask bit gets changedby the driver, concurrently with user mode operating on the ring,the mask bit may be set when it is supposed to be clear, and theuser-mode driver will miss an interrupt which will cause a hang.For eg- when the driver sets inbound ring buffer interrupt mask to 1,the host does not interrupt the guest on the UIO VMBus channel.However, setting the mask does not prevent the host from putting amessage in the inbound ring buffer. So let’s assume that happens,the host puts a message into the ring buffer but does not interrupt.Subsequently, the user space code in the guest sets the inbound ringbuffer interrupt mask to 0, saying “Hey, I’m ready for interrupts”.User space code then calls pread() to wait for an interrupt.Then one of two things happens:* The host never sends another message. So the pread() waits forever.* The host does send another message. But because there’s already a message in the ring buffer, it doesn’t generate an interrupt. This is the correct behavior, because the host should only send an interrupt when the inbound ring buffer transitions from empty to not-empty. Adding an additional message to a ring buffer that is not empty is not supposed to generate an interrupt on the guest. Since the guest is waiting in pread() and not removing messages from the ring buffer, the pread() waits forever.This could be easily reproduced in hv_fcopy_uio_daemon if we delaysetting interrupt mask to 0.Similarly if hv_uio_channel_cb() sets the interrupt_mask to 1,there’s a race condition. Once user space empties the inbound ringbuffer, but before user space sets interrupt_mask to 0, the host couldput another message in the ring buffer but it wouldn’t interrupt.Then the next pread() would hang.Fix these by removing all instances where interrupt_mask is changed,while keeping the one in set_event() unchanged to enable userspacecontrol the interrupt mask by writing 0/1 to /dev/uioX.The Linux kernel CVE team has assigned CVE-2025-40048 to this issue. openEuler评分: 6.2 Vector:CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H 受影响版本排查(受影响/不受影响): 1.openEuler-20.03-LTS-SP4(4.19.90):受影响 2.openEuler-22.03-LTS-SP3(5.10.0):受影响 3.openEuler-22.03-LTS-SP4(5.10.0):受影响 4.openEuler-24.03-LTS(6.6.0):受影响 5.openEuler-24.03-LTS-SP1(6.6.0):受影响 6.openEuler-24.03-LTS-SP2(6.6.0):受影响 7.master(6.12.33):不受影响 8.openEuler-24.03-LTS-Next(6.6.0):不受影响 修复是否涉及abi变化(是/否): 1.master(6.12.33):否 2.openEuler-20.03-LTS-SP4(4.19.90):否 3.openEuler-22.03-LTS-SP3(5.10.0):否 4.openEuler-22.03-LTS-SP4(5.10.0):否 5.openEuler-24.03-LTS(6.6.0):否 6.openEuler-24.03-LTS-Next(6.6.0):否 7.openEuler-24.03-LTS-SP1(6.6.0):否 8.openEuler-24.03-LTS-SP2(6.6.0):否 原因说明: 1.openEuler-24.03-LTS(6.6.0):正常修复 2.openEuler-24.03-LTS-SP1(6.6.0):正常修复 3.openEuler-24.03-LTS-SP2(6.6.0):正常修复 4.openEuler-20.03-LTS-SP4(4.19.90):不修复-超出修复范围 5.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围 6.openEuler-22.03-LTS-SP4(5.10.0):不修复-超出修复范围 7.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 8.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
Comments (
11
)
Sign in
to comment
Status
Backlog
Backlog
已挂起
Doing
Done
Declined
Assignees
Not set
CTC-Xibo.Wang
CTC-XiboWang
Assignee
Collaborator
+Assign
+Mention
Labels
CVE/UNFIXED
sig/Kernel
Not set
Projects
Unprojected
Unprojected
Milestones
No related milestones
No related milestones
Pull Requests
None yet
None yet
Successfully merging a pull request will close this issue.
Branches
No related branch
Branches (38)
Tags (271)
master
openEuler-24.03-LTS-SP3
openEuler-24.03-LTS-SP2
openEuler-24.03-LTS-SP1
openEuler-24.03-LTS
openEuler-20.03-LTS-SP4
openEuler-22.03-LTS-SP4
openEuler-22.03-LTS-SP3
openEuler-25.09
openEuler-24.03-LTS-Next
openEuler-25.03
openEuler-22.03-LTS-SP2
openEuler-22.03-LTS-SP1
openEuler-22.03-LTS-SP4-64KB
openEuler-24.09
openEuler-22.03-LTS-Next
openEuler-24.03-LTS-Loongarch
openEuler-22.03-LTS
openEuler-20.03-LTS-SP1
sync-pr1519-openEuler-24.03-LTS-to-openEuler-24.03-LTS-Next
sync-pr1486-master-to-openEuler-24.03-LTS-Next
loongarch-support
openEuler-20.03-LTS-SP3
sync-pr1314-openEuler-22.03-LTS-SP3-to-openEuler-22.03-LTS-Next
openEuler-23.09
openEuler-23.03
openEuler-22.03-LTS-LoongArch
openEuler-22.09
openEuler-22.09-HeXin
openEuler-20.03-LTS-SP2
openEuler-21.09
openEuler-20.03-LTS
openEuler-20.03-LTS-Next
openEuler-21.03
openEuler-20.09
openEuler-20.03-LTS-SP1-testing
openEuler1.0
openEuler1.0-base
openEuler-24.03-LTS-SP1-update-20251024
openEuler-20.03-LTS-SP4-update-20251024
openEuler-24.03-LTS-update-20251024
openEuler-22.03-LTS-SP3-update-20251024
openEuler-22.03-LTS-SP4-update-20251024
openEuler-24.03-LTS-SP2-update-20251024
openEuler-20.03-LTS-SP4-update-20251017
openEuler-22.03-LTS-SP3-update-20251017
openEuler-24.03-LTS-update-20251017
openEuler-24.03-LTS-SP1-update-20251017
openEuler-24.03-LTS-SP2-update-20251017
openEuler-22.03-LTS-SP4-update-20251017
openEuler-20.03-LTS-SP4-update-20251011
openEuler-22.03-LTS-SP4-update-20251011
openEuler-22.03-LTS-SP3-update-20251011
openEuler-24.03-LTS-update-20250929
openEuler-25.09-release
openEuler-20.03-LTS-SP4-update-20250926
openEuler-24.03-LTS-update-20250926
openEuler-22.03-LTS-SP3-update-20250926
openEuler-22.03-LTS-SP4-update-20250926
openEuler-24.03-LTS-SP1-update-20250926
openEuler-24.03-LTS-SP2-update-20250926
openEuler-20.03-LTS-SP4-update-20250919
openEuler-22.03-LTS-SP3-update-20250919
openEuler-24.03-LTS-update-20250919
openEuler-22.03-LTS-SP4-update-20250919
openEuler-24.03-LTS-SP1-update-20250919
openEuler-24.03-LTS-SP2-update-20250919
openEuler-20.03-LTS-SP4-update-20250912
openEuler-22.03-LTS-SP3-update-20250912
openEuler-22.03-LTS-SP4-update-20250912
openEuler-24.03-LTS-update-20250912
openEuler-24.03-LTS-SP1-update-20250912
openEuler-24.03-LTS-SP2-update-20250912
openEuler-24.03-LTS-SP1-update-20250911
openEuler-24.03-LTS-update-20250905
openEuler-20.03-LTS-SP4-update-20250905
openEuler-22.03-LTS-SP3-update-20250905
openEuler-22.03-LTS-SP4-update-20250905
openEuler-24.03-LTS-SP1-update-20250905
openEuler-24.03-LTS-SP2-update-20250905
openEuler-20.03-LTS-SP4-update-20250829
openEuler-22.03-LTS-SP4-update-20250829
openEuler-24.03-LTS-SP1-update-20250829
openEuler-24.03-LTS-update-20250829
openEuler-24.03-LTS-SP2-update-20250829
openEuler-22.03-LTS-SP3-update-20250822
openEuler-22.03-LTS-SP4-update-20250822
openEuler-24.03-LTS-update-20250822
openEuler-24.03-LTS-SP1-update-20250822
openEuler-24.03-LTS-SP2-update-20250822
openEuler-22.03-LTS-SP4-update-20250815
openEuler-22.03-LTS-SP3-update-20250815
openEuler-24.03-LTS-SP2-update-20250815
openEuler-20.03-LTS-SP4-update-20250815
openEuler-24.03-LTS-update-20250815
openEuler-24.03-LTS-SP1-update-20250815
openEuler-20.03-LTS-SP4-update-20250808
openEuler-22.03-LTS-SP3-update-20250808
openEuler-22.03-LTS-SP4-update-20250808
openEuler-24.03-LTS-update-20250808
openEuler-24.03-LTS-SP1-update-20250808
openEuler-24.03-LTS-SP2-update-20250808
openEuler-22.03-LTS-SP3-update-20250801
openEuler-22.03-LTS-SP4-update-20250801
openEuler-24.03-LTS-update-20250801
openEuler-24.03-LTS-SP1-update-20250801
openEuler-24.03-LTS-SP2-update-20250801
openEuler-20.03-LTS-SP4-update-20250725
openEuler-22.03-LTS-SP3-update-20250725
openEuler-22.03-LTS-SP4-update-20250725
openEuler-24.03-LTS-update-20250725
openEuler-24.03-LTS-SP1-update-20250725
openEuler-24.03-LTS-SP2-update-20250725
openEuler-20.03-LTS-SP4-update-20250718
openEuler-22.03-LTS-SP3-update-20250718
openEuler-22.03-LTS-SP4-update-20250718
openEuler-24.03-LTS-update-20250718
openEuler-24.03-LTS-SP1-update-20250718
openEuler-24.03-LTS-SP2-update-20250718
openEuler-20.03-LTS-SP4-update-20250711
openEuler-22.03-LTS-SP3-update-20250711
openEuler-22.03-LTS-SP4-update-20250711
openEuler-24.03-LTS-update-20250711
openEuler-24.03-LTS-SP1-update-20250711
openEuler-20.03-LTS-SP4-update-20250704
openEuler-22.03-LTS-SP3-update-20250704
openEuler-22.03-LTS-SP4-update-20250704
openEuler-24.03-LTS-update-20250704
openEuler-24.03-LTS-SP1-update-20250704
openEuler-20.03-LTS-SP4-update-20250627
openEuler-22.03-LTS-SP3-update-20250627
openEuler-22.03-LTS-SP4-update-20250627
openEuler-20.03-LTS-SP4-update-20250620
openEuler-22.03-LTS-SP3-update-20250620
openEuler-22.03-LTS-SP4-update-20250620
openEuler-24.03-LTS-update-20250620
openEuler-24.03-LTS-SP1-update-20250620
openEuler-24.03-LTS-SP2-release
openEuler-20.03-LTS-SP4-update-20250613
openEuler-22.03-LTS-SP3-update-20250613
openEuler-22.03-LTS-SP4-update-20250613
openEuler-24.03-LTS-update-20250613
openEuler-24.03-LTS-SP1-update-20250613
openEuler-20.03-LTS-SP4-update-20250606
openEuler-22.03-LTS-SP3-update-20250606
openEuler-22.03-LTS-SP4-update-20250606
openEuler-24.03-LTS-update-20250606
openEuler-24.03-LTS-SP1-update-20250606
openEuler-20.03-LTS-SP4-update-20250530
openEuler-22.03-LTS-SP3-update-20250530
openEuler-22.03-LTS-SP4-update-20250530
openEuler-24.03-LTS-update-20250530
openEuler-24.03-LTS-SP1-update-20250530
openEuler-20.03-LTS-SP4-update-20250523
openEuler-24.03-LTS-update-20250523
openEuler-24.03-LTS-SP1-update-20250523
openEuler-24.03-LTS-SP1-update-20250516
openEuler-24.03-LTS-update-20250516
openEuler-22.03-LTS-SP4-update-20250516
openEuler-22.03-LTS-SP3-update-20250516
openEuler-20.03-LTS-SP4-update-20250516
openEuler-24.03-LTS-SP1-update-20250509
openEuler-24.03-LTS-update-20250509
openEuler-22.03-LTS-SP4-update-20250509
openEuler-22.03-LTS-SP3-update-20250509
openEuler-20.03-LTS-SP4-update-20250509
openEuler-24.03-LTS-update-20250425
openEuler-22.03-LTS-SP3-update-20250425
openEuler-24.03-LTS-SP1-update-20250425
openEuler-24.03-LTS-SP1-update-20250428
openEuler-22.03-LTS-SP4-update-20250425
openEuler-20.03-LTS-SP4-update-20250425
openEuler-22.03-LTS-SP3-update-20250418
openEuler-22.03-LTS-SP4-update-20250418
openEuler-20.03-LTS-SP4-update-20250418
openEuler-22.03-LTS-SP3-update-20250411
openEuler-22.03-LTS-SP4-update-20250411
openEuler-20.03-LTS-SP4-update-20250411
openEuler-20.03-LTS-SP4-update-20250403
openEuler-24.03-LTS-SP1-update-20250403
openEuler-24.03-LTS-update-20250403
openEuler-25.03-release
openEuler-20.03-LTS-SP4-update-20250329
openEuler-22.03-LTS-SP4-update-20250329
openEuler-22.03-LTS-SP3-update-20250329
openEuler-24.03-LTS-SP1-update-20250329
openEuler-24.03-LTS-update-20250329
openEuler-24.03-LTS-update-20250321
openEuler-24.03-LTS-SP1-update-20250321
openEuler-20.03-LTS-SP4-update-20250321
openEuler-24.03-LTS-update-20250314
openEuler-24.03-LTS-SP1-update-20250314
openEuler-22.03-LTS-SP3-update-20250314
openEuler-22.03-LTS-SP4-update-20250314
openEuler-20.03-LTS-SP4-update-20250314
openEuler-24.03-LTS-update-20250307
openEuler-24.03-LTS-SP1-update-20250307
openEuler-22.03-LTS-SP3-update-20250307
openEuler-22.03-LTS-SP4-update-20250307
openEuler-20.03-LTS-SP4-update-20250307
openEuler-24.03-LTS-update-20250228
openEuler-24.03-LTS-SP1-update-20250228
openEuler-22.03-LTS-SP3-update-20250228
openEuler-22.03-LTS-SP4-update-20250228
openEuler-20.03-LTS-SP4-update-20250228
openEuler-24.03-LTS-SP1-update-20250221
openEuler-24.03-LTS-update-20250221
openEuler-22.03-LTS-SP4-update-20250221
openEuler-22.03-LTS-SP3-update-20250221
openEuler-20.03-LTS-SP4-update-20250221
openEuler-24.03-LTS-update-20250214
openEuler-24.03-LTS-SP1-update-20250214
openEuler-22.03-LTS-SP4-update-20250214
openEuler-22.03-LTS-SP3-update-20250214
openEuler-20.03-LTS-SP4-update-20250214
openEuler-24.03-LTS-update-20250208
openEuler-20.03-LTS-SP4-update-20250208
openEuler-22.03-LTS-SP3-update-20250208
openEuler-22.03-LTS-SP4-update-20250208
openEuler-24.03-LTS-SP1-update-20250208
openEuler-24.03-LTS-SP1-update-20250124
openEuler-22.03-LTS-SP4-update-20250124
openEuler-22.03-LTS-SP3-update-20250124
openEuler-20.03-LTS-SP4-update-20250124
openEuler-24.03-LTS-update-20250124
openEuler-22.03-LTS-SP3-update-20250117
openEuler-22.03-LTS-SP4-update-20250117
openEuler-20.03-LTS-SP4-update-20250117
openEuler-24.03-LTS-update-20250110
openEuler-24.03-LTS-SP1-update-20250110
openEuler-22.03-LTS-SP1-update-20250110
openEuler-22.03-LTS-SP3-update-20250110
openEuler-20.03-LTS-SP4-update-20250110
openEuler-22.03-LTS-SP4-update-20250110
openEuler-22.03-LTS-SP4-update-20250103
openEuler-22.03-LTS-SP3-update-20250103
openEuler-22.03-LTS-SP1-update-20250103
openEuler-20.03-LTS-SP4-update-20250103
openEuler-24.03-LTS-SP1-release
openEuler-24.03-LTS-update-20241227
openEuler-22.03-LTS-SP3-update-20241227
openEuler-22.03-LTS-SP4-update-20241227
openEuler-20.03-LTS-SP4-update-20241227
openEuler-22.03-LTS-SP4-update-20241220
openEuler-22.03-LTS-SP3-update-20241220
openEuler-20.03-LTS-SP4-update-20241220
openEuler-24.03-LTS-update-20241213
openEuler-22.03-LTS-SP4-update-20241213
openEuler-22.03-LTS-SP3-update-20241213
openEuler-22.03-LTS-SP1-update-20241213
openEuler-20.03-LTS-SP4-update-20241213
openEuler-24.03-LTS-update-20241206
openEuler-22.03-LTS-SP4-update-20241206
openEuler-22.03-LTS-SP3-update-20241206
openEuler-22.03-LTS-SP1-update-20241206
openEuler-20.03-LTS-SP4-update-20241206
openEuler-20.03-LTS-SP4-update-20241129
openEuler-22.03-LTS-SP1-update-20241129
openEuler-22.03-LTS-SP3-update-20241129
openEuler-22.03-LTS-SP4-update-20241129
openEuler-24.03-LTS-update-20241129
openEuler-24.03-LTS-update-20241122
openEuler-22.03-LTS-SP4-update-20241122
openEuler-22.03-LTS-SP3-update-20241122
openEuler-22.03-LTS-SP1-update-20241122
openEuler-20.03-LTS-SP4-update-20241122
openEuler-20.03-LTS-SP4-update-20241115
openEuler-22.03-LTS-SP1-update-20241115
openEuler-22.03-LTS-SP3-update-20241115
openEuler-22.03-LTS-SP4-update-20241115
openEuler-24.03-LTS-update-20241115
openEuler-24.03-LTS-update-20241108
openEuler-22.03-LTS-SP4-update-20241108
openEuler-22.03-LTS-SP3-update-20241108
openEuler-22.03-LTS-SP1-update-20241108
openEuler-20.03-LTS-SP4-update-20241108
openEuler-22.03-LTS-SP4-update-before-20241025
openEuler-22.03-LTS-SP4-before-20241025
openEuler-24.03-LTS-update-before-20241025
openEuler-20.03-LTS-SP4-update-20241101
openEuler-22.03-LTS-SP1-update-20241101
openEuler-22.03-LTS-SP3-update-20241101
openEuler-22.03-LTS-SP4-update-20241101
openEuler-24.03-LTS-update-20241101
openEuler-20.03-LTS-SP4-update-20241025
openEuler-22.03-LTS-SP1-update-20241025
openEuler-22.03-LTS-SP3-update-20241025
openEuler-22.03-LTS-SP4-update-20241025
openEuler-24.03-LTS-update-20241025
openEuler-22.03-LTS-SP4-release
openEuler-24.09-release
openEuler-24.03-LTS-release
openEuler-22.03-LTS-SP3-release
openEuler-23.09-rc5
openEuler-22.03-LTS-SP1-release
openEuler-22.09-release
openEuler-22.09-rc5
openEuler-22.09-20220829
openEuler-22.03-LTS-20220331
openEuler-22.03-LTS-round5
openEuler-22.03-LTS-round3
openEuler-22.03-LTS-round2
openEuler-22.03-LTS-round1
openEuler-20.03-LTS-SP3-release
openEuler-20.03-LTS-SP2-20210624
openEuler-21.03-20210330
openEuler-20.09-20200929
openEuler-20.03-LTS-20200606
openEuler-20.03-LTS-tag
Planed to start   -   Planed to end
-
Top level
Not Top
Top Level: High
Top Level: Medium
Top Level: Low
Priority
Not specified
Serious
Main
Secondary
Unimportant
Duration
(hours)
参与者(1)
1
https://gitee.com/src-openeuler/kernel.git
git@gitee.com:src-openeuler/kernel.git
src-openeuler
kernel
kernel
Going to Help Center
Search
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
Comment
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register