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
72
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-2024-36979
Done
#IA6S78
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2024-06-19 23:19
一、漏洞信息 漏洞编号：[CVE-2024-36979](https://nvd.nist.gov/vuln/detail/CVE-2024-36979) 漏洞归属组件：[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 V2.0分值： BaseScore：0.0 High Vector：CVSS：2.0/ 漏洞简述： In the Linux kernel, the following vulnerability has been resolved:net: bridge: mst: fix vlan use-after-freesyzbot reported a suspicious rcu usage[1] in bridge s mst code. Whilefixing it I noticed that nothing prevents a vlan to be freed whilewalking the list from the same path (br forward delay timer). Fix the rcuusage and also make sure we are not accessing freed memory by makingbr_mst_vlan_set_state use rcu read lock.[1] WARNING: suspicious RCU usage 6.9.0-rc6-syzkaller #0 Not tainted ----------------------------- net/bridge/br_private.h:1599 suspicious rcu_dereference_protected() usage! ... stack backtrace: CPU: 1 PID: 8017 Comm: syz-executor.1 Not tainted 6.9.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712 nbp_vlan_group net/bridge/br_private.h:1599 [inline] br_mst_set_state+0x1ea/0x650 net/bridge/br_mst.c:105 br_set_state+0x28a/0x7b0 net/bridge/br_stp.c:47 br_forward_delay_timer_expired+0x176/0x440 net/bridge/br_stp_timer.c:88 call_timer_fn+0x18e/0x650 kernel/time/timer.c:1793 expire_timers kernel/time/timer.c:1844 [inline] __run_timers kernel/time/timer.c:2418 [inline] __run_timer_base+0x66a/0x8e0 kernel/time/timer.c:2429 run_timer_base kernel/time/timer.c:2438 [inline] run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2448 __do_softirq+0x2c6/0x980 kernel/softirq.c:554 invoke_softirq kernel/softirq.c:428 [inline] __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633 irq_exit_rcu+0x9/0x30 kernel/softirq.c:645 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702 RIP: 0010:lock_acquire+0x264/0x550 kernel/locking/lockdep.c:5758 Code: 2b 00 74 08 4c 89 f7 e8 ba d1 84 00 f6 44 24 61 02 0f 85 85 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25 RSP: 0018:ffffc90013657100 EFLAGS: 00000206 RAX: 0000000000000001 RBX: 1ffff920026cae2c RCX: 0000000000000001 RDX: dffffc0000000000 RSI: ffffffff8bcaca00 RDI: ffffffff8c1eaa60 RBP: ffffc90013657260 R08: ffffffff92efe507 R09: 1ffffffff25dfca0 R10: dffffc0000000000 R11: fffffbfff25dfca1 R12: 1ffff920026cae28 R13: dffffc0000000000 R14: ffffc90013657160 R15: 0000000000000246 漏洞公开时间：2024-06-19 22:15:13 漏洞创建时间：2024-06-19 23:19:45 漏洞详情参考链接： https://nvd.nist.gov/vuln/detail/CVE-2024-36979 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3a7c1661ae1383364cd6092d851f5e5da64d476b | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/4488617e5e995a09abe4d81add5fb165674edb59 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/8ca9a750fc711911ef616ceb627d07357b04545e | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a2b01e65d9ba8af2bb086d3b7288ca53a07249ac | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e43dd2b1ec746e105b7db5f9ad6ef14685a615a4 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-36979 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-36979.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/8ca9a750fc711911ef616ceb627d07357b04545e | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/4488617e5e995a09abe4d81add5fb165674edb59 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/a2b01e65d9ba8af2bb086d3b7288ca53a07249ac | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/e43dd2b1ec746e105b7db5f9ad6ef14685a615a4 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/3a7c1661ae1383364cd6092d851f5e5da64d476b | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-36979 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2293194 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024061945-CVE-2024-36979-b4a6@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2293276 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-36979 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/linus/3a7c1661ae1383364cd6092d851f5e5da64d476b (6.10-rc1) | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/8ca9a750fc711911ef616ceb627d07357b04545e | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/4488617e5e995a09abe4d81add5fb165674edb59 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/a2b01e65d9ba8af2bb086d3b7288ca53a07249ac | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/e43dd2b1ec746e105b7db5f9ad6ef14685a615a4 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/3a7c1661ae1383364cd6092d851f5e5da64d476b | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-36979 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2024-36979 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-36979 | https://ubuntu.com/security/CVE-2024-36979 | | debian | | https://security-tracker.debian.org/tracker/CVE-2024-36979 | | mageia | | http://advisories.mageia.org/MGASA-2024-0263.html | </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/3a7c1661ae1383364cd6092d851f5e5da64d476b | https://git.kernel.org/linus/ec7328b59176227216c461601c6bd0e922232a9b | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明： In the Linux kernel, the following vulnerability has been resolved:net: bridge: mst: fix vlan use-after-freesyzbot reported a suspicious rcu usage[1] in bridge's mst code. Whilefixing it I noticed that nothing prevents a vlan to be freed whilewalking the list from the same path (br forward delay timer). Fix the rcuusage and also make sure we are not accessing freed memory by makingbr_mst_vlan_set_state use rcu read lock.[1] WARNING: suspicious RCU usage 6.9.0-rc6-syzkaller #0 Not tainted ----------------------------- net/bridge/br_private.h:1599 suspicious rcu_dereference_protected() usage! ... stack backtrace: CPU: 1 PID: 8017 Comm: syz-executor.1 Not tainted 6.9.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712 nbp_vlan_group net/bridge/br_private.h:1599 [inline] br_mst_set_state+0x1ea/0x650 net/bridge/br_mst.c:105 br_set_state+0x28a/0x7b0 net/bridge/br_stp.c:47 br_forward_delay_timer_expired+0x176/0x440 net/bridge/br_stp_timer.c:88 call_timer_fn+0x18e/0x650 kernel/time/timer.c:1793 expire_timers kernel/time/timer.c:1844 [inline] __run_timers kernel/time/timer.c:2418 [inline] __run_timer_base+0x66a/0x8e0 kernel/time/timer.c:2429 run_timer_base kernel/time/timer.c:2438 [inline] run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2448 __do_softirq+0x2c6/0x980 kernel/softirq.c:554 invoke_softirq kernel/softirq.c:428 [inline] __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633 irq_exit_rcu+0x9/0x30 kernel/softirq.c:645 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702 RIP: 0010:lock_acquire+0x264/0x550 kernel/locking/lockdep.c:5758 Code: 2b 00 74 08 4c 89 f7 e8 ba d1 84 00 f6 44 24 61 02 0f 85 85 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25 RSP: 0018:ffffc90013657100 EFLAGS: 00000206 RAX: 0000000000000001 RBX: 1ffff920026cae2c RCX: 0000000000000001 RDX: dffffc0000000000 RSI: ffffffff8bcaca00 RDI: ffffffff8c1eaa60 RBP: ffffc90013657260 R08: ffffffff92efe507 R09: 1ffffffff25dfca0 R10: dffffc0000000000 R11: fffffbfff25dfca1 R12: 1ffff920026cae28 R13: dffffc0000000000 R14: ffffc90013657160 R15: 0000000000000246The Linux kernel CVE team has assigned CVE-2024-36979 to this issue. openEuler评分： 7.0 Vector：CVSS：2.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H 受影响版本排查(受影响/不受影响)： 1.openEuler-24.03-LTS(6.6.0):受影响 2.openEuler-20.03-LTS-SP4(4.19.90):不受影响 3.openEuler-22.03-LTS-SP1(5.10.0):不受影响 4.openEuler-22.03-LTS-SP3(5.10.0):不受影响 5.openEuler-22.03-LTS-SP4(5.10.0):不受影响 6.master(6.1.0):不受影响 7.openEuler-24.03-LTS-Next(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.1.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):否 三、漏洞修复 安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1897
一、漏洞信息 漏洞编号：[CVE-2024-36979](https://nvd.nist.gov/vuln/detail/CVE-2024-36979) 漏洞归属组件：[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 V2.0分值： BaseScore：0.0 High Vector：CVSS：2.0/ 漏洞简述： In the Linux kernel, the following vulnerability has been resolved:net: bridge: mst: fix vlan use-after-freesyzbot reported a suspicious rcu usage[1] in bridge s mst code. Whilefixing it I noticed that nothing prevents a vlan to be freed whilewalking the list from the same path (br forward delay timer). Fix the rcuusage and also make sure we are not accessing freed memory by makingbr_mst_vlan_set_state use rcu read lock.[1] WARNING: suspicious RCU usage 6.9.0-rc6-syzkaller #0 Not tainted ----------------------------- net/bridge/br_private.h:1599 suspicious rcu_dereference_protected() usage! ... stack backtrace: CPU: 1 PID: 8017 Comm: syz-executor.1 Not tainted 6.9.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712 nbp_vlan_group net/bridge/br_private.h:1599 [inline] br_mst_set_state+0x1ea/0x650 net/bridge/br_mst.c:105 br_set_state+0x28a/0x7b0 net/bridge/br_stp.c:47 br_forward_delay_timer_expired+0x176/0x440 net/bridge/br_stp_timer.c:88 call_timer_fn+0x18e/0x650 kernel/time/timer.c:1793 expire_timers kernel/time/timer.c:1844 [inline] __run_timers kernel/time/timer.c:2418 [inline] __run_timer_base+0x66a/0x8e0 kernel/time/timer.c:2429 run_timer_base kernel/time/timer.c:2438 [inline] run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2448 __do_softirq+0x2c6/0x980 kernel/softirq.c:554 invoke_softirq kernel/softirq.c:428 [inline] __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633 irq_exit_rcu+0x9/0x30 kernel/softirq.c:645 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702 RIP: 0010:lock_acquire+0x264/0x550 kernel/locking/lockdep.c:5758 Code: 2b 00 74 08 4c 89 f7 e8 ba d1 84 00 f6 44 24 61 02 0f 85 85 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25 RSP: 0018:ffffc90013657100 EFLAGS: 00000206 RAX: 0000000000000001 RBX: 1ffff920026cae2c RCX: 0000000000000001 RDX: dffffc0000000000 RSI: ffffffff8bcaca00 RDI: ffffffff8c1eaa60 RBP: ffffc90013657260 R08: ffffffff92efe507 R09: 1ffffffff25dfca0 R10: dffffc0000000000 R11: fffffbfff25dfca1 R12: 1ffff920026cae28 R13: dffffc0000000000 R14: ffffc90013657160 R15: 0000000000000246 漏洞公开时间：2024-06-19 22:15:13 漏洞创建时间：2024-06-19 23:19:45 漏洞详情参考链接： https://nvd.nist.gov/vuln/detail/CVE-2024-36979 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3a7c1661ae1383364cd6092d851f5e5da64d476b | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/4488617e5e995a09abe4d81add5fb165674edb59 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/8ca9a750fc711911ef616ceb627d07357b04545e | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a2b01e65d9ba8af2bb086d3b7288ca53a07249ac | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e43dd2b1ec746e105b7db5f9ad6ef14685a615a4 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-36979 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-36979.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/8ca9a750fc711911ef616ceb627d07357b04545e | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/4488617e5e995a09abe4d81add5fb165674edb59 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/a2b01e65d9ba8af2bb086d3b7288ca53a07249ac | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/e43dd2b1ec746e105b7db5f9ad6ef14685a615a4 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://git.kernel.org/stable/c/3a7c1661ae1383364cd6092d851f5e5da64d476b | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-36979 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2293194 | https://bugzilla.suse.com/show_bug.cgi?id=1226604 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024061945-CVE-2024-36979-b4a6@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2293276 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-36979 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/linus/3a7c1661ae1383364cd6092d851f5e5da64d476b (6.10-rc1) | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/8ca9a750fc711911ef616ceb627d07357b04545e | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/4488617e5e995a09abe4d81add5fb165674edb59 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/a2b01e65d9ba8af2bb086d3b7288ca53a07249ac | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/e43dd2b1ec746e105b7db5f9ad6ef14685a615a4 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://git.kernel.org/stable/c/3a7c1661ae1383364cd6092d851f5e5da64d476b | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-36979 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2024-36979 | https://ubuntu.com/security/CVE-2024-36979 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-36979 | https://ubuntu.com/security/CVE-2024-36979 | | debian | | https://security-tracker.debian.org/tracker/CVE-2024-36979 | | mageia | | http://advisories.mageia.org/MGASA-2024-0263.html | </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/3a7c1661ae1383364cd6092d851f5e5da64d476b | https://git.kernel.org/linus/ec7328b59176227216c461601c6bd0e922232a9b | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明： In the Linux kernel, the following vulnerability has been resolved:net: bridge: mst: fix vlan use-after-freesyzbot reported a suspicious rcu usage[1] in bridge's mst code. Whilefixing it I noticed that nothing prevents a vlan to be freed whilewalking the list from the same path (br forward delay timer). Fix the rcuusage and also make sure we are not accessing freed memory by makingbr_mst_vlan_set_state use rcu read lock.[1] WARNING: suspicious RCU usage 6.9.0-rc6-syzkaller #0 Not tainted ----------------------------- net/bridge/br_private.h:1599 suspicious rcu_dereference_protected() usage! ... stack backtrace: CPU: 1 PID: 8017 Comm: syz-executor.1 Not tainted 6.9.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712 nbp_vlan_group net/bridge/br_private.h:1599 [inline] br_mst_set_state+0x1ea/0x650 net/bridge/br_mst.c:105 br_set_state+0x28a/0x7b0 net/bridge/br_stp.c:47 br_forward_delay_timer_expired+0x176/0x440 net/bridge/br_stp_timer.c:88 call_timer_fn+0x18e/0x650 kernel/time/timer.c:1793 expire_timers kernel/time/timer.c:1844 [inline] __run_timers kernel/time/timer.c:2418 [inline] __run_timer_base+0x66a/0x8e0 kernel/time/timer.c:2429 run_timer_base kernel/time/timer.c:2438 [inline] run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2448 __do_softirq+0x2c6/0x980 kernel/softirq.c:554 invoke_softirq kernel/softirq.c:428 [inline] __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633 irq_exit_rcu+0x9/0x30 kernel/softirq.c:645 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702 RIP: 0010:lock_acquire+0x264/0x550 kernel/locking/lockdep.c:5758 Code: 2b 00 74 08 4c 89 f7 e8 ba d1 84 00 f6 44 24 61 02 0f 85 85 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25 RSP: 0018:ffffc90013657100 EFLAGS: 00000206 RAX: 0000000000000001 RBX: 1ffff920026cae2c RCX: 0000000000000001 RDX: dffffc0000000000 RSI: ffffffff8bcaca00 RDI: ffffffff8c1eaa60 RBP: ffffc90013657260 R08: ffffffff92efe507 R09: 1ffffffff25dfca0 R10: dffffc0000000000 R11: fffffbfff25dfca1 R12: 1ffff920026cae28 R13: dffffc0000000000 R14: ffffc90013657160 R15: 0000000000000246The Linux kernel CVE team has assigned CVE-2024-36979 to this issue. openEuler评分： 7.0 Vector：CVSS：2.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H 受影响版本排查(受影响/不受影响)： 1.openEuler-24.03-LTS(6.6.0):受影响 2.openEuler-20.03-LTS-SP4(4.19.90):不受影响 3.openEuler-22.03-LTS-SP1(5.10.0):不受影响 4.openEuler-22.03-LTS-SP3(5.10.0):不受影响 5.openEuler-22.03-LTS-SP4(5.10.0):不受影响 6.master(6.1.0):不受影响 7.openEuler-24.03-LTS-Next(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.1.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):否 三、漏洞修复 安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1897
Comments (
15
)
Sign in
to comment
Status
Done
Backlog
已挂起
Doing
Done
Declined
Assignees
Not set
sanglipeng
sanglipeng
Assignee
Collaborator
+Assign
+Mention
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）
参与者（3）
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
