CVE-2022-49520

一、漏洞信息
 漏洞编号：[CVE-2022-49520](https://nvd.nist.gov/vuln/detail/CVE-2022-49520)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.1.8,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:arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscallIf a compat process tries to execute an unknown system call above the__ARM_NR_COMPAT_END number, the kernel sends a SIGILL signal to theoffending process. Information about the error is printed to dmesg incompat_arm_syscall() -> arm64_notify_die() -> arm64_force_sig_fault() ->arm64_show_signal().arm64_show_signal() interprets a non-zero value forcurrent->thread.fault_code as an exception syndrome and displays themessage associated with the ESR_ELx.EC field (bits 31:26).current->thread.fault_code is set in compat_arm_syscall() ->arm64_notify_die() with the bad syscall number instead of a valid ESR_ELxvalue. This means that the ESR_ELx.EC field has the value that the user setfor the syscall number and the kernel can end up printing bogus exceptionmessages*. For example, for the syscall number 0x68000000, which evaluatesto ESR_ELx.EC value of 0x1A (ESR_ELx_EC_FPAC) the kernel prints this error:[   18.349161] syscall[300]: unhandled exception: ERET/ERETAA/ERETAB, ESR 0x68000000, Oops - bad compat syscall(2) in syscall[10000+50000][   18.350639] CPU: 2 PID: 300 Comm: syscall Not tainted 5.18.0-rc1 #79[   18.351249] Hardware name: Pine64 RockPro64 v2.0 (DT)[..]which is misleading, as the bad compat syscall has nothing to do withpointer authentication.Stop arm64_show_signal() from printing exception syndrome information byhaving compat_arm_syscall() set the ESR_ELx value to 0, as it has nomeaning for an invalid system call number. The example above now becomes:[   19.935275] syscall[301]: unhandled exception: Oops - bad compat syscall(2) in syscall[10000+50000][   19.936124] CPU: 1 PID: 301 Comm: syscall Not tainted 5.18.0-rc1-00005-g7e08006d4102 #80[   19.936894] Hardware name: Pine64 RockPro64 v2.0 (DT)[..]which although shows less information because the syscall number,wrongfully advertised as the ESR value, is missing, it is better thanshowing plainly wrong information. The syscall number can be easilyobtained with strace.*A 32-bit value above or equal to 0x8000_0000 is interpreted as a negativeinteger in compat_arm_syscal() and the condition scno < __ARM_NR_COMPAT_ENDevaluates to true; the syscall will exit to userspace in this case with theENOSYS error code instead of arm64_notify_die() being called.
 漏洞公开时间：2025-02-26 15:01:28
 漏洞创建时间：2025-02-26 14:26:30
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2022-49520
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/095e975f8150ccd7f852eb578c1cdbdd2f517c7a |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3910ae71cb963fa2b68e684489d4fc3d105afda0 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3fed9e551417b84038b15117732ea4505eee386b |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/621916afe8cd4f322eb12759b64a2f938d4e551d |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ad97425d23af3c3b8d4f6a2bb666cb485087c007 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/efd183d988b416fcdf6f7c298a17ced4859ca77d |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-49520 | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-49520.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| suse_bugzilla | https://git.kernel.org/stable/c/efd183d988b416fcdf6f7c298a17ced4859ca77d | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| suse_bugzilla | https://git.kernel.org/stable/c/ad97425d23af3c3b8d4f6a2bb666cb485087c007 | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| suse_bugzilla | https://git.kernel.org/stable/c/621916afe8cd4f322eb12759b64a2f938d4e551d | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| suse_bugzilla | https://git.kernel.org/stable/c/095e975f8150ccd7f852eb578c1cdbdd2f517c7a | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| suse_bugzilla | https://git.kernel.org/stable/c/3910ae71cb963fa2b68e684489d4fc3d105afda0 | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| suse_bugzilla | https://git.kernel.org/stable/c/3fed9e551417b84038b15117732ea4505eee386b | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2347923 | https://bugzilla.suse.com/show_bug.cgi?id=1238836 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2025022611-CVE-2022-49520-465c@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2347923 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2025022611-CVE-2022-49520-465c@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2347923 |

</details>

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

无
</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscallIf a compat process tries to execute an unknown system call above the__ARM_NR_COMPAT_END number, the kernel sends a SIGILL signal to theoffending process. Information about the error is printed to dmesg incompat_arm_syscall() -> arm64_notify_die() -> arm64_force_sig_fault() ->arm64_show_signal().arm64_show_signal() interprets a non-zero value forcurrent->thread.fault_code as an exception syndrome and displays themessage associated with the ESR_ELx.EC field (bits 31:26).current->thread.fault_code is set in compat_arm_syscall() ->arm64_notify_die() with the bad syscall number instead of a valid ESR_ELxvalue. This means that the ESR_ELx.EC field has the value that the user setfor the syscall number and the kernel can end up printing bogus exceptionmessages*. For example, for the syscall number 0x68000000, which evaluatesto ESR_ELx.EC value of 0x1A (ESR_ELx_EC_FPAC) the kernel prints this error:[   18.349161] syscall[300]: unhandled exception: ERET/ERETAA/ERETAB, ESR 0x68000000, Oops - bad compat syscall(2) in syscall[10000+50000][   18.350639] CPU: 2 PID: 300 Comm: syscall Not tainted 5.18.0-rc1 #79[   18.351249] Hardware name: Pine64 RockPro64 v2.0 (DT)[..]which is misleading, as the bad compat syscall has nothing to do withpointer authentication.Stop arm64_show_signal() from printing exception syndrome information byhaving compat_arm_syscall() set the ESR_ELx value to 0, as it has nomeaning for an invalid system call number. The example above now becomes:[   19.935275] syscall[301]: unhandled exception: Oops - bad compat syscall(2) in syscall[10000+50000][   19.936124] CPU: 1 PID: 301 Comm: syscall Not tainted 5.18.0-rc1-00005-g7e08006d4102 #80[   19.936894] Hardware name: Pine64 RockPro64 v2.0 (DT)[..]which although shows less information because the syscall number,wrongfully advertised as the ESR value, is missing, it is better thanshowing plainly wrong information. The syscall number can be easilyobtained with strace.*A 32-bit value above or equal to 0x8000_0000 is interpreted as a negativeinteger in compat_arm_syscal() and the condition scno < __ARM_NR_COMPAT_ENDevaluates to true; the syscall will exit to userspace in this case with theENOSYS error code instead of arm64_notify_die() being called.
 openEuler评分：
  3.3
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
 受影响版本排查(受影响/不受影响)：
  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.12.33):不受影响
5.openEuler-24.03-LTS:不受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:不受影响

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

原因说明：
  1.openEuler-20.03-LTS-SP4(4.19.90):不修复-超出修复范围
2.master(6.12.33):不受影响-漏洞代码不能被攻击者触发
3.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
4.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS:不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在

src-openEuler/kernel
关闭

内容风险标识

评论 (11)

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

内容风险标识

CVE-2022-49520

评论 (11)

搜索帮助

src-openEuler/kernel
关闭