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
330
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-2022-48664
Done
#I9KHGY
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2024-04-28 22:31
一、漏洞信息 漏洞编号：[CVE-2022-48664](https://nvd.nist.gov/vuln/detail/CVE-2022-48664) 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0 CVSS V3.0分值： BaseScore：0.0 None Vector：CVSS：3.0/ 漏洞简述： In the Linux kernel, the following vulnerability has been resolved:btrfs: fix hang during unmount when stopping a space reclaim workerOften when running generic/562 from fstests we can hang during unmount,resulting in a trace like this: Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00 Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds. Sep 07 11:55:32 debian9 kernel: Not tainted 6.0.0-rc2-btrfs-next-122 #1 Sep 07 11:55:32 debian9 kernel: echo 0 > /proc/sys/kernel/hung_task_timeout_secs disables this message. Sep 07 11:55:32 debian9 kernel: task:umount state:D stack: 0 pid:49438 ppid: 25683 flags:0x00004000 Sep 07 11:55:32 debian9 kernel: Call Trace: Sep 07 11:55:32 debian9 kernel: <TASK> Sep 07 11:55:32 debian9 kernel: __schedule+0x3c8/0xec0 Sep 07 11:55:32 debian9 kernel: ? rcu_read_lock_sched_held+0x12/0x70 Sep 07 11:55:32 debian9 kernel: schedule+0x5d/0xf0 Sep 07 11:55:32 debian9 kernel: schedule_timeout+0xf1/0x130 Sep 07 11:55:32 debian9 kernel: ? lock_release+0x224/0x4a0 Sep 07 11:55:32 debian9 kernel: ? lock_acquired+0x1a0/0x420 Sep 07 11:55:32 debian9 kernel: ? trace_hardirqs_on+0x2c/0xd0 Sep 07 11:55:32 debian9 kernel: __wait_for_common+0xac/0x200 Sep 07 11:55:32 debian9 kernel: ? usleep_range_state+0xb0/0xb0 Sep 07 11:55:32 debian9 kernel: __flush_work+0x26d/0x530 Sep 07 11:55:32 debian9 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Sep 07 11:55:32 debian9 kernel: ? trace_clock_local+0xc/0x30 Sep 07 11:55:32 debian9 kernel: __cancel_work_timer+0x11f/0x1b0 Sep 07 11:55:32 debian9 kernel: ? close_ctree+0x12b/0x5b3 [btrfs] Sep 07 11:55:32 debian9 kernel: ? __trace_bputs+0x10b/0x170 Sep 07 11:55:32 debian9 kernel: close_ctree+0x152/0x5b3 [btrfs] Sep 07 11:55:32 debian9 kernel: ? evict_inodes+0x166/0x1c0 Sep 07 11:55:32 debian9 kernel: generic_shutdown_super+0x71/0x120 Sep 07 11:55:32 debian9 kernel: kill_anon_super+0x14/0x30 Sep 07 11:55:32 debian9 kernel: btrfs_kill_super+0x12/0x20 [btrfs] Sep 07 11:55:32 debian9 kernel: deactivate_locked_super+0x2e/0xa0 Sep 07 11:55:32 debian9 kernel: cleanup_mnt+0x100/0x160 Sep 07 11:55:32 debian9 kernel: task_work_run+0x59/0xa0 Sep 07 11:55:32 debian9 kernel: exit_to_user_mode_prepare+0x1a6/0x1b0 Sep 07 11:55:32 debian9 kernel: syscall_exit_to_user_mode+0x16/0x40 Sep 07 11:55:32 debian9 kernel: do_syscall_64+0x48/0x90 Sep 07 11:55:32 debian9 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd Sep 07 11:55:32 debian9 kernel: RIP: 0033:0x7fcde59a57a7 Sep 07 11:55:32 debian9 kernel: RSP: 002b:00007ffe914217c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 Sep 07 11:55:32 debian9 kernel: RAX: 0000000000000000 RBX: 00007fcde5ae8264 RCX: 00007fcde59a57a7 Sep 07 11:55:32 debian9 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000055b57556cdd0 Sep 07 11:55:32 debian9 kernel: RBP: 000055b57556cba0 R08: 0000000000000000 R09: 00007ffe91420570 Sep 07 11:55:32 debian9 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Sep 07 11:55:32 debian9 kernel: R13: 000055b57556cdd0 R14: 000055b57556ccb8 R15: 0000000000000000 Sep 07 11:55:32 debian9 kernel: </TASK>What happens is the following:1) The cleaner kthread tries to start a transaction to delete an unused block group, but the metadata reservation can not be satisfied right away, so a reservation ticket is created and it starts the async metadata reclaim task (fs_info->async_reclaim_work);2) Writeback for all the filler inodes with an i_size of 2K starts (generic/562 creates a lot of 2K files with the goal of filling metadata space). We try to create an inline extent for them, but we fail when trying to insert the inline extent with -ENOSPC (at cow_file_range_inline()) - since this is not critical, we fallback to non-inline mode (back to cow_file_range()), reserve extents---truncated--- 漏洞公开时间：2024-04-28 21:15:08 漏洞创建时间：2024-04-28 14:31:09 漏洞详情参考链接： https://nvd.nist.gov/vuln/detail/CVE-2022-48664 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a362bb864b8db4861977d00bd2c3222503ccc34b | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c338bea1fec5504290dc0acf026c9e7dba25004b | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d8a76a2e514fbbb315a6dfff2d342de2de833994 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48664 | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2022-48664 | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/stable/c/6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8 | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/stable/c/a362bb864b8db4861977d00bd2c3222503ccc34b | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/stable/c/c338bea1fec5504290dc0acf026c9e7dba25004b | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/stable/c/d8a76a2e514fbbb315a6dfff2d342de2de833994 | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48664.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024042801-CVE-2022-48664-d281@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2277795 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2022-48664 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/linus/a362bb864b8db4861977d00bd2c3222503ccc34b (6.0-rc7) | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/stable/c/6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/stable/c/d8a76a2e514fbbb315a6dfff2d342de2de833994 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/stable/c/c338bea1fec5504290dc0acf026c9e7dba25004b | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/stable/c/a362bb864b8db4861977d00bd2c3222503ccc34b | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2022-48664 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2022-48664 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2022-48664 | https://ubuntu.com/security/CVE-2022-48664 | | anolis | | https://anas.openanolis.cn/cves/detail/CVE-2022-48664 | </details> 漏洞分析指导链接： https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息： <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | linux | | https://git.kernel.org/linus/a362bb864b8db4861977d00bd2c3222503ccc34b | https://git.kernel.org/linus/d6fd0ae25c6495674dc5a41a8d16bc8e0073276d | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明： Reserved. 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-SP3(5.10.0):不受影响 3.openEuler-22.03-LTS-SP4(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-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.master(6.6.0):不受影响-漏洞代码不能被攻击者触发 3.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 4.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在 5.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在 6.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不存在 7.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在
一、漏洞信息 漏洞编号：[CVE-2022-48664](https://nvd.nist.gov/vuln/detail/CVE-2022-48664) 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0 CVSS V3.0分值： BaseScore：0.0 None Vector：CVSS：3.0/ 漏洞简述： In the Linux kernel, the following vulnerability has been resolved:btrfs: fix hang during unmount when stopping a space reclaim workerOften when running generic/562 from fstests we can hang during unmount,resulting in a trace like this: Sep 07 11:52:00 debian9 unknown: run fstests generic/562 at 2022-09-07 11:52:00 Sep 07 11:55:32 debian9 kernel: INFO: task umount:49438 blocked for more than 120 seconds. Sep 07 11:55:32 debian9 kernel: Not tainted 6.0.0-rc2-btrfs-next-122 #1 Sep 07 11:55:32 debian9 kernel: echo 0 > /proc/sys/kernel/hung_task_timeout_secs disables this message. Sep 07 11:55:32 debian9 kernel: task:umount state:D stack: 0 pid:49438 ppid: 25683 flags:0x00004000 Sep 07 11:55:32 debian9 kernel: Call Trace: Sep 07 11:55:32 debian9 kernel: <TASK> Sep 07 11:55:32 debian9 kernel: __schedule+0x3c8/0xec0 Sep 07 11:55:32 debian9 kernel: ? rcu_read_lock_sched_held+0x12/0x70 Sep 07 11:55:32 debian9 kernel: schedule+0x5d/0xf0 Sep 07 11:55:32 debian9 kernel: schedule_timeout+0xf1/0x130 Sep 07 11:55:32 debian9 kernel: ? lock_release+0x224/0x4a0 Sep 07 11:55:32 debian9 kernel: ? lock_acquired+0x1a0/0x420 Sep 07 11:55:32 debian9 kernel: ? trace_hardirqs_on+0x2c/0xd0 Sep 07 11:55:32 debian9 kernel: __wait_for_common+0xac/0x200 Sep 07 11:55:32 debian9 kernel: ? usleep_range_state+0xb0/0xb0 Sep 07 11:55:32 debian9 kernel: __flush_work+0x26d/0x530 Sep 07 11:55:32 debian9 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Sep 07 11:55:32 debian9 kernel: ? trace_clock_local+0xc/0x30 Sep 07 11:55:32 debian9 kernel: __cancel_work_timer+0x11f/0x1b0 Sep 07 11:55:32 debian9 kernel: ? close_ctree+0x12b/0x5b3 [btrfs] Sep 07 11:55:32 debian9 kernel: ? __trace_bputs+0x10b/0x170 Sep 07 11:55:32 debian9 kernel: close_ctree+0x152/0x5b3 [btrfs] Sep 07 11:55:32 debian9 kernel: ? evict_inodes+0x166/0x1c0 Sep 07 11:55:32 debian9 kernel: generic_shutdown_super+0x71/0x120 Sep 07 11:55:32 debian9 kernel: kill_anon_super+0x14/0x30 Sep 07 11:55:32 debian9 kernel: btrfs_kill_super+0x12/0x20 [btrfs] Sep 07 11:55:32 debian9 kernel: deactivate_locked_super+0x2e/0xa0 Sep 07 11:55:32 debian9 kernel: cleanup_mnt+0x100/0x160 Sep 07 11:55:32 debian9 kernel: task_work_run+0x59/0xa0 Sep 07 11:55:32 debian9 kernel: exit_to_user_mode_prepare+0x1a6/0x1b0 Sep 07 11:55:32 debian9 kernel: syscall_exit_to_user_mode+0x16/0x40 Sep 07 11:55:32 debian9 kernel: do_syscall_64+0x48/0x90 Sep 07 11:55:32 debian9 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd Sep 07 11:55:32 debian9 kernel: RIP: 0033:0x7fcde59a57a7 Sep 07 11:55:32 debian9 kernel: RSP: 002b:00007ffe914217c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 Sep 07 11:55:32 debian9 kernel: RAX: 0000000000000000 RBX: 00007fcde5ae8264 RCX: 00007fcde59a57a7 Sep 07 11:55:32 debian9 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000055b57556cdd0 Sep 07 11:55:32 debian9 kernel: RBP: 000055b57556cba0 R08: 0000000000000000 R09: 00007ffe91420570 Sep 07 11:55:32 debian9 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Sep 07 11:55:32 debian9 kernel: R13: 000055b57556cdd0 R14: 000055b57556ccb8 R15: 0000000000000000 Sep 07 11:55:32 debian9 kernel: </TASK>What happens is the following:1) The cleaner kthread tries to start a transaction to delete an unused block group, but the metadata reservation can not be satisfied right away, so a reservation ticket is created and it starts the async metadata reclaim task (fs_info->async_reclaim_work);2) Writeback for all the filler inodes with an i_size of 2K starts (generic/562 creates a lot of 2K files with the goal of filling metadata space). We try to create an inline extent for them, but we fail when trying to insert the inline extent with -ENOSPC (at cow_file_range_inline()) - since this is not critical, we fallback to non-inline mode (back to cow_file_range()), reserve extents---truncated--- 漏洞公开时间：2024-04-28 21:15:08 漏洞创建时间：2024-04-28 14:31:09 漏洞详情参考链接： https://nvd.nist.gov/vuln/detail/CVE-2022-48664 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a362bb864b8db4861977d00bd2c3222503ccc34b | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c338bea1fec5504290dc0acf026c9e7dba25004b | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d8a76a2e514fbbb315a6dfff2d342de2de833994 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48664 | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2022-48664 | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/stable/c/6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8 | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/stable/c/a362bb864b8db4861977d00bd2c3222503ccc34b | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/stable/c/c338bea1fec5504290dc0acf026c9e7dba25004b | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/stable/c/d8a76a2e514fbbb315a6dfff2d342de2de833994 | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48664.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1223524 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024042801-CVE-2022-48664-d281@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2277795 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2022-48664 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/linus/a362bb864b8db4861977d00bd2c3222503ccc34b (6.0-rc7) | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/stable/c/6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/stable/c/d8a76a2e514fbbb315a6dfff2d342de2de833994 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/stable/c/c338bea1fec5504290dc0acf026c9e7dba25004b | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://git.kernel.org/stable/c/a362bb864b8db4861977d00bd2c3222503ccc34b | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2022-48664 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2022-48664 | https://ubuntu.com/security/CVE-2022-48664 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2022-48664 | https://ubuntu.com/security/CVE-2022-48664 | | anolis | | https://anas.openanolis.cn/cves/detail/CVE-2022-48664 | </details> 漏洞分析指导链接： https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息： <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | linux | | https://git.kernel.org/linus/a362bb864b8db4861977d00bd2c3222503ccc34b | https://git.kernel.org/linus/d6fd0ae25c6495674dc5a41a8d16bc8e0073276d | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明： Reserved. 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-SP3(5.10.0):不受影响 3.openEuler-22.03-LTS-SP4(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-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.master(6.6.0):不受影响-漏洞代码不能被攻击者触发 3.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 4.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在 5.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在 6.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不存在 7.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在
Comments (
12
)
Sign in
to comment
Status
Done
Backlog
已挂起
Doing
Done
Declined
Assignees
Not set
Labels
CVE/FIXED
sig/Kernel
Not set
Projects
Unprojected
Unprojected
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）
参与者（2）
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
