CVE-2024-36906

一、漏洞信息
漏洞编号：CVE-2024-36906
漏洞归属组件：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 Low
Vector：CVSS：2.0/
漏洞简述：
In the Linux kernel, the following vulnerability has been resolved:ARM: 9381/1: kasan: clear stale stack poisonWe found below OOB crash:[ 33.452494] ==================================================================[ 33.453513] BUG: KASAN: stack-out-of-bounds in refresh_cpu_vm_stats.constprop.0+0xcc/0x2ec[ 33.454660] Write of size 164 at addr c1d03d30 by task swapper/0/0[ 33.455515][ 33.455767] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O 6.1.25-mainline #1[ 33.456880] Hardware name: Generic DT based system[ 33.457555] unwind_backtrace from show_stack+0x18/0x1c[ 33.458326] show_stack from dump_stack_lvl+0x40/0x4c[ 33.459072] dump_stack_lvl from print_report+0x158/0x4a4[ 33.459863] print_report from kasan_report+0x9c/0x148[ 33.460616] kasan_report from kasan_check_range+0x94/0x1a0[ 33.461424] kasan_check_range from memset+0x20/0x3c[ 33.462157] memset from refresh_cpu_vm_stats.constprop.0+0xcc/0x2ec[ 33.463064] refresh_cpu_vm_stats.constprop.0 from tick_nohz_idle_stop_tick+0x180/0x53c[ 33.464181] tick_nohz_idle_stop_tick from do_idle+0x264/0x354[ 33.465029] do_idle from cpu_startup_entry+0x20/0x24[ 33.465769] cpu_startup_entry from rest_init+0xf0/0xf4[ 33.466528] rest_init from arch_post_acpi_subsys_init+0x0/0x18[ 33.467397][ 33.467644] The buggy address belongs to stack of task swapper/0/0[ 33.468493] and is located at offset 112 in frame:[ 33.469172] refresh_cpu_vm_stats.constprop.0+0x0/0x2ec[ 33.469917][ 33.470165] This frame has 2 objects:[ 33.470696] [32, 76) global_zone_diff [ 33.470729] [112, 276) global_node_diff [ 33.471294][ 33.472095] The buggy address belongs to the physical page:[ 33.472862] page:3cd72da8 refcount:1 mapcount:0 mapping:00000000 index:0x0 pfn:0x41d03[ 33.473944] flags: 0x1000(reserved|zone=0)[ 33.474565] raw: 00001000 ed741470 ed741470 00000000 00000000 00000000 ffffffff 00000001[ 33.475656] raw: 00000000[ 33.476050] page dumped because: kasan: bad access detected[ 33.476816][ 33.477061] Memory state around the buggy address:[ 33.477732] c1d03c00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00[ 33.478630] c1d03c80: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 00[ 33.479526] >c1d03d00: 00 04 f2 f2 f2 f2 00 00 00 00 00 00 f1 f1 f1 f1[ 33.480415] ^[ 33.481195] c1d03d80: 00 00 00 00 00 00 00 00 00 00 04 f3 f3 f3 f3 f3[ 33.482088] c1d03e00: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00[ 33.482978] ==================================================================We find the root cause of this OOB is that arm does not clear stale stackpoison in the case of cpuidle.This patch refer to arch/arm64/kernel/sleep.S to resolve this issue.From cited commit [1] that explain the problemFunctions which the compiler has instrumented for KASAN place poison onthe stack shadow upon entry and remove this poison prior to returning.In the case of cpuidle, CPUs exit the kernel a number of levels deep inC code. Any instrumented functions on this critical path will leaveportions of the stack shadow poisoned.If CPUs lose context and return to the kernel via a cold path, werestore a prior context saved in __cpu_suspend_enter are forgotten, andwe never remove the poison they placed in the stack shadow area byfunctions calls between this and the actual exit of the kernel.Thus, (depending on stackframe layout) subsequent calls to instrumentedfunctions may hit this stale poison, resulting in (spurious) KASANsplats to the console.To avoid this, clear any stale poison from the idle thread for a CPUprior to bringing a CPU online.From cited commit [2]Extend to check for CONFIG_KASAN_STACK[1] commit 0d97e6d8024c ( arm64: kasan: clear stale stack poison )[2] commit d56a9ef84bd0 ( kasan, arm64: unpoison stack only with CONFIG_KASAN_STACK )
漏洞公开时间：2024-05-31 00:15:14
漏洞创建时间：2024-06-04 02:29:07
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-36906

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/20ac71bee028ffbae4fc14ed679b23b4d3e95726
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/ad702338fe423cb1e79745787090317256a98dab
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/b26f353786d365e658cebc9a9ace88e04fc2325e
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/c4238686f9093b98bd6245a348bcf059cdce23af
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/ee0ce7573e5083031960faf602c9db693ab5b477
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-36906	https://bugzilla.suse.com/show_bug.cgi?id=1225715
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-36906.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1225715
suse_bugzilla	https://git.kernel.org/stable/c/20ac71bee028ffbae4fc14ed679b23b4d3e95726	https://bugzilla.suse.com/show_bug.cgi?id=1225715
suse_bugzilla	https://git.kernel.org/stable/c/ad702338fe423cb1e79745787090317256a98dab	https://bugzilla.suse.com/show_bug.cgi?id=1225715
suse_bugzilla	https://git.kernel.org/stable/c/ee0ce7573e5083031960faf602c9db693ab5b477	https://bugzilla.suse.com/show_bug.cgi?id=1225715
suse_bugzilla	https://git.kernel.org/stable/c/b26f353786d365e658cebc9a9ace88e04fc2325e	https://bugzilla.suse.com/show_bug.cgi?id=1225715
suse_bugzilla	https://git.kernel.org/stable/c/c4238686f9093b98bd6245a348bcf059cdce23af	https://bugzilla.suse.com/show_bug.cgi?id=1225715
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-36906	https://bugzilla.suse.com/show_bug.cgi?id=1225715
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2024053036-CVE-2024-36906-736b@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2284537
ubuntu	https://www.cve.org/CVERecord?id=CVE-2024-36906	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://git.kernel.org/linus/c4238686f9093b98bd6245a348bcf059cdce23af (6.9)	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://git.kernel.org/stable/c/20ac71bee028ffbae4fc14ed679b23b4d3e95726	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://git.kernel.org/stable/c/ad702338fe423cb1e79745787090317256a98dab	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://git.kernel.org/stable/c/ee0ce7573e5083031960faf602c9db693ab5b477	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://git.kernel.org/stable/c/b26f353786d365e658cebc9a9ace88e04fc2325e	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://git.kernel.org/stable/c/c4238686f9093b98bd6245a348bcf059cdce23af	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://nvd.nist.gov/vuln/detail/CVE-2024-36906	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://launchpad.net/bugs/cve/CVE-2024-36906	https://ubuntu.com/security/CVE-2024-36906
ubuntu	https://security-tracker.debian.org/tracker/CVE-2024-36906	https://ubuntu.com/security/CVE-2024-36906
debian		https://security-tracker.debian.org/tracker/CVE-2024-36906
amazon_linux_explore	https://access.redhat.com/security/cve/CVE-2024-36906	https://explore.alas.aws.amazon.com/CVE-2024-36906.html
amazon_linux_explore	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36906	https://explore.alas.aws.amazon.com/CVE-2024-36906.html

漏洞分析指导链接：
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息：

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
linux		https://git.kernel.org/linus/c4238686f9093b98bd6245a348bcf059cdce23af	https://git.kernel.org/linus/5615f69bc2097452ecc954f5264d784e158d6801	ubuntu

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:ARM: 9381/1: kasan: clear stale stack poisonWe found below OOB crash:[ 33.452494] ==================================================================[ 33.453513] BUG: KASAN: stack-out-of-bounds in refresh_cpu_vm_stats.constprop.0+0xcc/0x2ec[ 33.454660] Write of size 164 at addr c1d03d30 by task swapper/0/0[ 33.455515][ 33.455767] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O 6.1.25-mainline #1[ 33.456880] Hardware name: Generic DT based system[ 33.457555] unwind_backtrace from show_stack+0x18/0x1c[ 33.458326] show_stack from dump_stack_lvl+0x40/0x4c[ 33.459072] dump_stack_lvl from print_report+0x158/0x4a4[ 33.459863] print_report from kasan_report+0x9c/0x148[ 33.460616] kasan_report from kasan_check_range+0x94/0x1a0[ 33.461424] kasan_check_range from memset+0x20/0x3c[ 33.462157] memset from refresh_cpu_vm_stats.constprop.0+0xcc/0x2ec[ 33.463064] refresh_cpu_vm_stats.constprop.0 from tick_nohz_idle_stop_tick+0x180/0x53c[ 33.464181] tick_nohz_idle_stop_tick from do_idle+0x264/0x354[ 33.465029] do_idle from cpu_startup_entry+0x20/0x24[ 33.465769] cpu_startup_entry from rest_init+0xf0/0xf4[ 33.466528] rest_init from arch_post_acpi_subsys_init+0x0/0x18[ 33.467397][ 33.467644] The buggy address belongs to stack of task swapper/0/0[ 33.468493] and is located at offset 112 in frame:[ 33.469172] refresh_cpu_vm_stats.constprop.0+0x0/0x2ec[ 33.469917][ 33.470165] This frame has 2 objects:[ 33.470696] [32, 76) 'global_zone_diff'[ 33.470729] [112, 276) 'global_node_diff'[ 33.471294][ 33.472095] The buggy address belongs to the physical page:[ 33.472862] page:3cd72da8 refcount:1 mapcount:0 mapping:00000000 index:0x0 pfn:0x41d03[ 33.473944] flags: 0x1000(reserved|zone=0)[ 33.474565] raw: 00001000 ed741470 ed741470 00000000 00000000 00000000 ffffffff 00000001[ 33.475656] raw: 00000000[ 33.476050] page dumped because: kasan: bad access detected[ 33.476816][ 33.477061] Memory state around the buggy address:[ 33.477732] c1d03c00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00[ 33.478630] c1d03c80: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 00[ 33.479526] >c1d03d00: 00 04 f2 f2 f2 f2 00 00 00 00 00 00 f1 f1 f1 f1[ 33.480415] ^[ 33.481195] c1d03d80: 00 00 00 00 00 00 00 00 00 00 04 f3 f3 f3 f3 f3[ 33.482088] c1d03e00: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00[ 33.482978] ==================================================================We find the root cause of this OOB is that arm does not clear stale stackpoison in the case of cpuidle.This patch refer to arch/arm64/kernel/sleep.S to resolve this issue.<spanclass= q >>From cited commit [1] that explain the problemFunctions which the compiler has instrumented for KASAN place poison onthe stack shadow upon entry and remove this poison prior to returning.In the case of cpuidle, CPUs exit the kernel a number of levels deep inC code. Any instrumented functions on this critical path will leaveportions of the stack shadow poisoned.If CPUs lose context and return to the kernel via a cold path, werestore a prior context saved in __cpu_suspend_enter are forgotten, andwe never remove the poison they placed in the stack shadow area byfunctions calls between this and the actual exit of the kernel.Thus, (depending on stackframe layout) subsequent calls to instrumentedfunctions may hit this stale poison, resulting in (spurious) KASANsplats to the console.To avoid this, clear any stale poison from the idle thread for a CPUprior to bringing a CPU online.<spanclass= q >>From cited commit [2]Extend to check for CONFIG_KASAN_STACK[1] commit 0d97e6d8024c ("arm64: kasan: clear stale stack poison")[2] commit d56a9ef84bd0 ("kasan, arm64: unpoison stack only with CONFIG_KASAN_STACK")The Linux kernel CVE team has assigned CVE-2024-36906 to this issue.
openEuler评分：
5.5
Vector：CVSS：2.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N
受影响版本排查(受影响/不受影响)：
1.openEuler-22.03-LTS-SP1(5.10.0):受影响
2.openEuler-22.03-LTS-SP3(5.10.0):受影响
3.openEuler-20.03-LTS-SP1(4.19.90):不受影响
4.openEuler-20.03-LTS-SP4(4.19.90):不受影响
5.openEuler-22.03-LTS(5.10.0):不受影响
6.openEuler-22.03-LTS-SP2(5.10.0):不受影响
7.openEuler-22.03-LTS-SP4(5.10.0):不受影响
8.master(6.1.0):不受影响
9.openEuler-22.03-LTS-Next(5.10.0):不受影响
10.openEuler-24.03-LTS(6.6.0):不受影响
11.openEuler-24.03-LTS-Next(6.6.0):不受影响

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

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1707

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

@YangYingliang ,@jiaoff ,@AlexGuo ,@hanjun-guo ,@woqidaideshi ,@Jackie Liu ,@Zhang Yi ,@colyli ,@ThunderTown ,@htforge ,@Chiqijun ,@冷嘲啊 ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@Kefeng ,@SuperSix173 ,@WangShaoBo ,@Zheng Zucheng ,@陈结松
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(6.1.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-Next(5.10.0):
4.openEuler-22.03-LTS-SP1(5.10.0):
5.openEuler-22.03-LTS-SP3(5.10.0):
6.openEuler-22.03-LTS-SP4(5.10.0):
7.openEuler-24.03-LTS(6.6.0):
8.openEuler-24.03-LTS-Next(6.6.0):

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

issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2024-36906	None	None	https://git.kernel.org/stable/c/ad702338fe423cb1e79745787090317256a98dab https://git.kernel.org/stable/c/c4238686f9093b98bd6245a348bcf059cdce23af https://git.kernel.org/stable/c/ee0ce7573e5083031960faf602c9db693ab5b477 https://git.kernel.org/stable/c/20ac71bee028ffbae4fc14ed679b23b4d3e95726 https://git.kernel.org/stable/c/b26f353786d365e658cebc9a9ace88e04fc2325e
https://ubuntu.com/security/CVE-2024-36906	None	None	https://git.kernel.org/stable/c/ad702338fe423cb1e79745787090317256a98dab https://git.kernel.org/stable/c/c4238686f9093b98bd6245a348bcf059cdce23af https://discourse.ubuntu.com/c/ubuntu-pro https://git.kernel.org/stable/c/ee0ce7573e5083031960faf602c9db693ab5b477 https://git.kernel.org/stable/c/20ac71bee028ffbae4fc14ed679b23b4d3e95726 https://git.kernel.org/stable/c/b26f353786d365e658cebc9a9ace88e04fc2325e https://git.kernel.org/linus/5615f69bc2097452ecc954f5264d784e158d6801 https://git.kernel.org/linus/c4238686f9093b98bd6245a348bcf059cdce23af
https://www.opencve.io/cve/CVE-2024-36906	None	None	https://git.kernel.org/stable/c/ad702338fe423cb1e79745787090317256a98dab https://git.kernel.org/stable/c/c4238686f9093b98bd6245a348bcf059cdce23af https://git.kernel.org/stable/c/ee0ce7573e5083031960faf602c9db693ab5b477 https://git.kernel.org/stable/c/20ac71bee028ffbae4fc14ed679b23b4d3e95726 https://git.kernel.org/stable/c/b26f353786d365e658cebc9a9ace88e04fc2325e
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-36906
https://security-tracker.debian.org/tracker/CVE-2024-36906	None	None	https://git.kernel.org/linus/c4238686f9093b98bd6245a348bcf059cdce23af

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

@ci-robot 请确认分支: master,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-Next,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP3,openEuler-22.03-LTS-SP4,openEuler-24.03-LTS,openEuler-24.03-LTS-Next 受影响/不受影响.
请确认分支信息是否填写完整,否则将无法关闭当前issue.

CVE-2024-36906

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

ARM: 9381/1: kasan: clear stale stack poison

We found below OOB crash:

[ 33.452494] ==================================================================
[ 33.453513] BUG: KASAN: stack-out-of-bounds in refresh_cpu_vm_stats.constprop.0+0xcc/0x2ec
[ 33.454660] Write of size 164 at addr c1d03d30 by task swapper/0/0
[ 33.455515]
[ 33.455767] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O 6.1.25-mainline #1
[ 33.456880] Hardware name: Generic DT based system
[ 33.457555] unwind_backtrace from show_stack+0x18/0x1c
[ 33.458326] show_stack from dump_stack_lvl+0x40/0x4c
[ 33.459072] dump_stack_lvl from print_report+0x158/0x4a4
[ 33.459863] print_report from kasan_report+0x9c/0x148
[ 33.460616] kasan_report from kasan_check_range+0x94/0x1a0
[ 33.461424] kasan_check_range from memset+0x20/0x3c
[ 33.462157] memset from refresh_cpu_vm_stats.constprop.0+0xcc/0x2ec
[ 33.463064] refresh_cpu_vm_stats.constprop.0 from tick_nohz_idle_stop_tick+0x180/0x53c
[ 33.464181] tick_nohz_idle_stop_tick from do_idle+0x264/0x354
[ 33.465029] do_idle from cpu_startup_entry+0x20/0x24
[ 33.465769] cpu_startup_entry from rest_init+0xf0/0xf4
[ 33.466528] rest_init from arch_post_acpi_subsys_init+0x0/0x18
[ 33.467397]
[ 33.467644] The buggy address belongs to stack of task swapper/0/0
[ 33.468493] and is located at offset 112 in frame:
[ 33.469172] refresh_cpu_vm_stats.constprop.0+0x0/0x2ec
[ 33.469917]
[ 33.470165] This frame has 2 objects:
[ 33.470696] [32, 76) 'global_zone_diff'
[ 33.470729] [112, 276) 'global_node_diff'
[ 33.471294]
[ 33.472095] The buggy address belongs to the physical page:
[ 33.472862] page:3cd72da8 refcount:1 mapcount:0 mapping:00000000 index:0x0 pfn:0x41d03
[ 33.473944] flags: 0x1000(reserved|zone=0)
[ 33.474565] raw: 00001000 ed741470 ed741470 00000000 00000000 00000000 ffffffff 00000001
[ 33.475656] raw: 00000000
[ 33.476050] page dumped because: kasan: bad access detected
[ 33.476816]
[ 33.477061] Memory state around the buggy address:
[ 33.477732] c1d03c00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 33.478630] c1d03c80: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 00
[ 33.479526] >c1d03d00: 00 04 f2 f2 f2 f2 00 00 00 00 00 00 f1 f1 f1 f1
[ 33.480415] ^
[ 33.481195] c1d03d80: 00 00 00 00 00 00 00 00 00 00 04 f3 f3 f3 f3 f3
[ 33.482088] c1d03e00: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
[ 33.482978] ==================================================================

We find the root cause of this OOB is that arm does not clear stale stack
poison in the case of cpuidle.

This patch refer to arch/arm64/kernel/sleep.S to resolve this issue.

>From cited commit [1] that explain the problem

Functions which the compiler has instrumented for KASAN place poison on
the stack shadow upon entry and remove this poison prior to returning.

In the case of cpuidle, CPUs exit the kernel a number of levels deep in
C code. Any instrumented functions on this critical path will leave
portions of the stack shadow poisoned.

If CPUs lose context and return to the kernel via a cold path, we
restore a prior context saved in __cpu_suspend_enter are forgotten, and
we never remove the poison they placed in the stack shadow area by
functions calls between this and the actual exit of the kernel.

Thus, (depending on stackframe layout) subsequent calls to instrumented
functions may hit this stale poison, resulting in (spurious) KASAN
splats to the console.

To avoid this, clear any stale poison from the idle thread for a CPU
prior to bringing a CPU online.

>From cited commit [2]

Extend to check for CONFIG_KASAN_STACK

[1] commit 0d97e6d8024c ("arm64: kasan: clear stale stack poison")
[2] commit d56a9ef84bd0 ("kasan, arm64: unpoison stack only with CONFIG_KASAN_STACK")

The Linux kernel CVE team has assigned CVE-2024-36906 to this issue.

openEuler评分:(评分和向量)
5.5
CVSS: 3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP1:不受影响
2.openEuler-20.03-LTS-SP4:不受影响
3.openEuler-22.03-LTS:不受影响
4.openEuler-22.03-LTS-SP1:受影响
5.openEuler-22.03-LTS-SP2:不受影响
6.openEuler-22.03-LTS-SP3:受影响
7.openEuler-22.03-LTS-SP4:不受影响
8.master(6.1.0):不受影响
9.openEuler-22.03-LTS-Next:不受影响
10.openEuler-24.03-LTS:不受影响
11.openEuler-24.03-LTS-Next:不受影响

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