CVE-2024-53071

一、漏洞信息
 漏洞编号：[CVE-2024-53071](https://nvd.nist.gov/vuln/detail/CVE-2024-53071)
 漏洞归属组件：[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：5.5 Medium
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:drm/panthor: Be stricter about IO mapping flagsThe current panthor_device_mmap_io() implementation has two issues:1. For mapping DRM_PANTHOR_USER_FLUSH_ID_MMIO_OFFSET,   panthor_device_mmap_io() bails if VM_WRITE is set, but does not clear   VM_MAYWRITE. That means userspace can use mprotect() to make the mapping   writable later on. This is a classic Linux driver gotcha.   I don t think this actually has any impact in practice:   When the GPU is powered, writes to the FLUSH_ID seem to be ignored; and   when the GPU is not powered, the dummy_latest_flush page provided by the   driver is deliberately designed to not do any flushes, so the only thing   writing to the dummy_latest_flush could achieve would be to make *more*   flushes happen.2. panthor_device_mmap_io() does not block MAP_PRIVATE mappings (which are   mappings without the VM_SHARED flag).   MAP_PRIVATE in combination with VM_MAYWRITE indicates that the VMA has   copy-on-write semantics, which for VM_PFNMAP are semi-supported but   fairly cursed.   In particular, in such a mapping, the driver can only install PTEs   during mmap() by calling remap_pfn_range() (because remap_pfn_range()   wants to **store the physical address of the mapped physical memory into   the vm_pgoff of the VMA**); installing PTEs later on with a fault   handler (as panthor does) is not supported in private mappings, and so   if you try to fault in such a mapping, vmf_insert_pfn_prot() splats when   it hits a BUG() check.Fix it by clearing the VM_MAYWRITE flag (userspace writing to the FLUSH_IDdoesn t make sense) and requiring VM_SHARED (copy-on-write semantics forthe FLUSH_ID don t make sense).Reproducers for both scenarios are in the notes of my patch on the mailinglist; I tested that these bugs exist on a Rock 5B machine.Note that I only compile-tested the patch, I haven t tested it; I don thave a working kernel build setup for the test machine yet. Please test itbefore applying it.
 漏洞公开时间：2024-11-20 02:15:26
 漏洞创建时间：2024-11-20 02:40:22
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-53071
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2604afd65043e8f9d4be036cb1242adf6b5723cf |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f432a1621f049bb207e78363d9d0e3c6fa2da5db |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-53071 | https://bugzilla.suse.com/show_bug.cgi?id=1233716 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-53071.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1233716 |
| suse_bugzilla | https://git.kernel.org/stable/c/2604afd65043e8f9d4be036cb1242adf6b5723cf | https://bugzilla.suse.com/show_bug.cgi?id=1233716 |
| suse_bugzilla | https://git.kernel.org/stable/c/f432a1621f049bb207e78363d9d0e3c6fa2da5db | https://bugzilla.suse.com/show_bug.cgi?id=1233716 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-53071 | https://bugzilla.suse.com/show_bug.cgi?id=1233716 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2327375 | https://bugzilla.suse.com/show_bug.cgi?id=1233716 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024111934-CVE-2024-53071-ddbc@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2327375 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-53071 |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
|  |  | https://git.kernel.org/stable/c/2604afd65043e8f9d4be036cb1242adf6b5723cf |  | nvd |
|  |  | https://git.kernel.org/stable/c/f432a1621f049bb207e78363d9d0e3c6fa2da5db |  | nvd |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:drm/panthor: Be stricter about IO mapping flagsThe current panthor_device_mmap_io() implementation has two issues:1. For mapping DRM_PANTHOR_USER_FLUSH_ID_MMIO_OFFSET,   panthor_device_mmap_io() bails if VM_WRITE is set, but does not clear   VM_MAYWRITE. That means userspace can use mprotect() to make the mapping   writable later on. This is a classic Linux driver gotcha.   I don t think this actually has any impact in practice:   When the GPU is powered, writes to the FLUSH_ID seem to be ignored; and   when the GPU is not powered, the dummy_latest_flush page provided by the   driver is deliberately designed to not do any flushes, so the only thing   writing to the dummy_latest_flush could achieve would be to make *more*   flushes happen.2. panthor_device_mmap_io() does not block MAP_PRIVATE mappings (which are   mappings without the VM_SHARED flag).   MAP_PRIVATE in combination with VM_MAYWRITE indicates that the VMA has   copy-on-write semantics, which for VM_PFNMAP are semi-supported but   fairly cursed.   In particular, in such a mapping, the driver can only install PTEs   during mmap() by calling remap_pfn_range() (because remap_pfn_range()   wants to **store the physical address of the mapped physical memory into   the vm_pgoff of the VMA**); installing PTEs later on with a fault   handler (as panthor does) is not supported in private mappings, and so   if you try to fault in such a mapping, vmf_insert_pfn_prot() splats when   it hits a BUG() check.Fix it by clearing the VM_MAYWRITE flag (userspace writing to the FLUSH_IDdoesn t make sense) and requiring VM_SHARED (copy-on-write semantics forthe FLUSH_ID don t make sense).Reproducers for both scenarios are in the notes of my patch on the mailinglist; I tested that these bugs exist on a Rock 5B machine.Note that I only compile-tested the patch, I haven t tested it; I don thave a working kernel build setup for the test machine yet. Please test itbefore applying it.
 openEuler评分：
  5.5
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):不受影响
2.openEuler-22.03-LTS-SP1(5.10.0):不受影响
3.openEuler-22.03-LTS-SP3(5.10.0):不受影响
4.openEuler-22.03-LTS-SP4(5.10.0):不受影响
5.master(6.6.0):不受影响
6.openEuler-24.03-LTS(6.6.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响
8.openEuler-24.03-LTS-SP1(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP1(5.10.0):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.master(6.6.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-22.03-LTS-SP4(5.10.0):否
8.openEuler-24.03-LTS-SP1(6.6.0):否

原因说明：
  1.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在
2.openEuler-22.03-LTS-SP1(5.10.0):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在
4.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在
5.master(6.6.0):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不存在
8.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在

src-openEuler/kernel
Closed

Content Risk Flag

Comments (6)

src-openEuler/kernelClosed .gitee-modal { width: 500px !important; }

Content Risk Flag

CVE-2024-53071

Comments (6)

Search

src-openEuler/kernel
Closed