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
&&
Watch
Unwatch
Watching
Releases Only
Ignoring
128
Star
73
Fork
331
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
DevLens
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-38062
Backlog
#ICGAFW
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2025-06-19 11:36
一、漏洞信息 漏洞编号:[CVE-2025-38062](https://nvd.nist.gov/vuln/detail/CVE-2025-38062) 漏洞归属组件:[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 V3.0分值: BaseScore:N/A None Vector:CVSS:3.0/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:genirq/msi: Store the IOMMU IOVA directly in msi_desc instead of iommu_cookieThe IOMMU translation for MSI message addresses has been a 2-step process,separated in time: 1) iommu_dma_prepare_msi(): A cookie pointer containing the IOVA address is stored in the MSI descriptor when an MSI interrupt is allocated. 2) iommu_dma_compose_msi_msg(): this cookie pointer is used to compute a translated message address.This has an inherent lifetime problem for the pointer stored in the cookiethat must remain valid between the two steps. However, there is no lockingat the irq layer that helps protect the lifetime. Today, this works underthe assumption that the iommu domain is not changed while MSI interruptsbeing programmed. This is true for normal DMA API users within the kernel,as the iommu domain is attached before the driver is probed and cannot bechanged while a driver is attached.Classic VFIO type1 also prevented changing the iommu domain while VFIO wasrunning as it does not support changing the container after starting up.However, iommufd has improved this so that the iommu domain can be changedduring VFIO operation. This potentially allows userspace to directly raceVFIO_DEVICE_ATTACH_IOMMUFD_PT (which calls iommu_attach_group()) andVFIO_DEVICE_SET_IRQS (which calls into iommu_dma_compose_msi_msg()).This potentially causes both the cookie pointer and the unlocked call toiommu_get_domain_for_dev() on the MSI translation path to become UAFs.Fix the MSI cookie UAF by removing the cookie pointer. The translated IOVAaddress is already known during iommu_dma_prepare_msi() and cannot change.Thus, it can simply be stored as an integer in the MSI descriptor.The other UAF related to iommu_get_domain_for_dev() will be addressed inpatch iommu: Make iommu_dma_prepare_msi() into a generic operation byusing the IOMMU group mutex. 漏洞公开时间:2025-06-18 18:15:39 漏洞创建时间:2025-06-19 11:36:40 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2025-38062 <details> <summary>更多参考(点击展开)</summary> 无 </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://github.com/gregkh/linux/commit/1f7df3a691740a7736bbc99dc4ed536120eb4746.patch | | ljqc | </details> 二、漏洞分析结构反馈 影响性分析说明: openEuler评分: 受影响版本排查(受影响/不受影响): 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.openEuler-24.03-LTS-Next: 7.openEuler-24.03-LTS-SP1: 8.openEuler-24.03-LTS-SP2: 修复是否涉及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.openEuler-24.03-LTS-Next: 7.openEuler-24.03-LTS-SP1: 8.openEuler-24.03-LTS-SP2: 原因说明: 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.openEuler-24.03-LTS-Next: 7.openEuler-24.03-LTS-SP1: 8.openEuler-24.03-LTS-SP2:
一、漏洞信息 漏洞编号:[CVE-2025-38062](https://nvd.nist.gov/vuln/detail/CVE-2025-38062) 漏洞归属组件:[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 V3.0分值: BaseScore:N/A None Vector:CVSS:3.0/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:genirq/msi: Store the IOMMU IOVA directly in msi_desc instead of iommu_cookieThe IOMMU translation for MSI message addresses has been a 2-step process,separated in time: 1) iommu_dma_prepare_msi(): A cookie pointer containing the IOVA address is stored in the MSI descriptor when an MSI interrupt is allocated. 2) iommu_dma_compose_msi_msg(): this cookie pointer is used to compute a translated message address.This has an inherent lifetime problem for the pointer stored in the cookiethat must remain valid between the two steps. However, there is no lockingat the irq layer that helps protect the lifetime. Today, this works underthe assumption that the iommu domain is not changed while MSI interruptsbeing programmed. This is true for normal DMA API users within the kernel,as the iommu domain is attached before the driver is probed and cannot bechanged while a driver is attached.Classic VFIO type1 also prevented changing the iommu domain while VFIO wasrunning as it does not support changing the container after starting up.However, iommufd has improved this so that the iommu domain can be changedduring VFIO operation. This potentially allows userspace to directly raceVFIO_DEVICE_ATTACH_IOMMUFD_PT (which calls iommu_attach_group()) andVFIO_DEVICE_SET_IRQS (which calls into iommu_dma_compose_msi_msg()).This potentially causes both the cookie pointer and the unlocked call toiommu_get_domain_for_dev() on the MSI translation path to become UAFs.Fix the MSI cookie UAF by removing the cookie pointer. The translated IOVAaddress is already known during iommu_dma_prepare_msi() and cannot change.Thus, it can simply be stored as an integer in the MSI descriptor.The other UAF related to iommu_get_domain_for_dev() will be addressed inpatch iommu: Make iommu_dma_prepare_msi() into a generic operation byusing the IOMMU group mutex. 漏洞公开时间:2025-06-18 18:15:39 漏洞创建时间:2025-06-19 11:36:40 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2025-38062 <details> <summary>更多参考(点击展开)</summary> 无 </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://github.com/gregkh/linux/commit/1f7df3a691740a7736bbc99dc4ed536120eb4746.patch | | ljqc | </details> 二、漏洞分析结构反馈 影响性分析说明: openEuler评分: 受影响版本排查(受影响/不受影响): 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.openEuler-24.03-LTS-Next: 7.openEuler-24.03-LTS-SP1: 8.openEuler-24.03-LTS-SP2: 修复是否涉及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.openEuler-24.03-LTS-Next: 7.openEuler-24.03-LTS-SP1: 8.openEuler-24.03-LTS-SP2: 原因说明: 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.openEuler-24.03-LTS-Next: 7.openEuler-24.03-LTS-SP1: 8.openEuler-24.03-LTS-SP2:
Comments (
3
)
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 (
-
)
Tags (
-
)
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
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