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
&&
Watch
Unwatch
Watching
Releases Only
Ignoring
128
Star
73
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-2022-49961
Done
#ICG9E1
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2025-06-19 10:39
一、漏洞信息 漏洞编号：[CVE-2022-49961](https://nvd.nist.gov/vuln/detail/CVE-2022-49961) 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本：5.10.0 CVSS V3.0分值： BaseScore：N/A None Vector：CVSS：3.0/ 漏洞简述： In the Linux kernel, the following vulnerability has been resolved:bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZEROPrecision markers need to be propagated whenever we have an ARG_CONST_*style argument, as the verifier cannot consider imprecise scalars to beequivalent for the purposes of states_equal check when such argumentsrefine the return value (in this case, set mem_size for PTR_TO_MEM). Theresultant mem_size for the R0 is derived from the constant value, and ifthe verifier incorrectly prunes states considering them equivalent wheresuch arguments exist (by seeing that both registers have reg->precise asfalse in regsafe), we can end up with invalid programs passing theverifier which can do access beyond what should have been the correctmem_size in that explored state.To show a concrete example of the problem:0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32 *)(r1 + 0) = r2 7: r1 = *(u32 *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -10000000000000058 <LBB5_3>: 11: r1 = 0 ll 13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7 <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18: w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpf_ringbuf_submit00000000000000b8 <LBB5_5>: 23: w0 = 0 24: exitFor the first case, the single line execution s exploration will prunethe search at insn 14 for the branch insn 9 s second leg as it will beverified first using r2 = -1 (UINT_MAX), while as w1 at insn 9 willalways be 0 so at runtime we don t get error for being greater thanUINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe justsees reg->precise as false for both r2 registers in both states, henceconsiders them equal for purposes of states_equal.If we propagated precise markers using the backtracking support, wewould use the precise marking to then ensure that old r2 (UINT_MAX) waswithin the new r2 (1) and this would never be true, so the verificationwould rightfully fail.The end result is that the out of bounds access at instruction 19 wouldbe permitted without this fix.Note that reg->precise is always set to true when user does not haveCAP_BPF (or when subprog count is greater than 1 (i.e. use of any staticor global functions)), hence this is only a problem when precision marksneed to be explicitly propagated (i.e. privileged users with CAP_BPF).A simplified test case has been included in the next patch to preventfuture regressions. 漏洞公开时间：2025-06-18 19:15:23 漏洞创建时间：2025-06-19 10:39:03 漏洞详情参考链接： https://nvd.nist.gov/vuln/detail/CVE-2022-49961 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | </details> 漏洞分析指导链接： https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息： <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://github.com/gregkh/linux/commit/2459615a8d7f44ac81f0965bc094e55ccb254717.patch | | ljqc | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | nvd | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | nvd | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | snyk | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | snyk | </details> 二、漏洞分析结构反馈 影响性分析说明： In the Linux kernel, the following vulnerability has been resolved:bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZEROPrecision markers need to be propagated whenever we have an ARG_CONST_*style argument, as the verifier cannot consider imprecise scalars to beequivalent for the purposes of states_equal check when such argumentsrefine the return value (in this case, set mem_size for PTR_TO_MEM). Theresultant mem_size for the R0 is derived from the constant value, and ifthe verifier incorrectly prunes states considering them equivalent wheresuch arguments exist (by seeing that both registers have reg->precise asfalse in regsafe), we can end up with invalid programs passing theverifier which can do access beyond what should have been the correctmem_size in that explored state.To show a concrete example of the problem:0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32 *)(r1 + 0) = r2 7: r1 = *(u32 *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -10000000000000058 <LBB5_3>: 11: r1 = 0 ll 13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7 <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18: w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpf_ringbuf_submit00000000000000b8 <LBB5_5>: 23: w0 = 0 24: exitFor the first case, the single line execution's exploration will prunethe search at insn 14 for the branch insn 9's second leg as it will beverified first using r2 = -1 (UINT_MAX), while as w1 at insn 9 willalways be 0 so at runtime we don't get error for being greater thanUINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe justsees reg->precise as false for both r2 registers in both states, henceconsiders them equal for purposes of states_equal.If we propagated precise markers using the backtracking support, wewould use the precise marking to then ensure that old r2 (UINT_MAX) waswithin the new r2 (1) and this would never be true, so the verificationwould rightfully fail.The end result is that the out of bounds access at instruction 19 wouldbe permitted without this fix.Note that reg->precise is always set to true when user does not haveCAP_BPF (or when subprog count is greater than 1 (i.e. use of any staticor global functions)), hence this is only a problem when precision marksneed to be explicitly propagated (i.e. privileged users with CAP_BPF).A simplified test case has been included in the next patch to preventfuture regressions.The Linux kernel CVE team has assigned CVE-2022-49961 to this issue. openEuler评分： 3.9 Vector：CVSS：3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L 受影响版本排查(受影响/不受影响)： 1.openEuler-22.03-LTS-SP3(5.10.0):受影响 2.openEuler-22.03-LTS-SP4(5.10.0):受影响 3.master(6.12.33):不受影响 4.openEuler-20.03-LTS-SP4(4.19.90):不受影响 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):不受影响 8.openEuler-24.03-LTS-SP2(6.6.0):不受影响 修复是否涉及abi变化(是/否)： 1.master(6.12.33):否 2.openEuler-20.03-LTS-SP4(4.19.90):否 3.openEuler-22.03-LTS-SP3(5.10.0):否 4.openEuler-22.03-LTS-SP4(5.10.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):否 8.openEuler-24.03-LTS-SP2(6.6.0):否 原因说明： 1.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围 2.openEuler-22.03-LTS-SP4(5.10.0):不修复-超出修复范围 3.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 4.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不能被攻击者触发 5.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 6.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不能被攻击者触发 7.openEuler-24.03-LTS-SP2(6.6.0):不受影响-漏洞代码不能被攻击者触发 8.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在 三、漏洞修复 安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1877
一、漏洞信息 漏洞编号：[CVE-2022-49961](https://nvd.nist.gov/vuln/detail/CVE-2022-49961) 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本：5.10.0 CVSS V3.0分值： BaseScore：N/A None Vector：CVSS：3.0/ 漏洞简述： In the Linux kernel, the following vulnerability has been resolved:bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZEROPrecision markers need to be propagated whenever we have an ARG_CONST_*style argument, as the verifier cannot consider imprecise scalars to beequivalent for the purposes of states_equal check when such argumentsrefine the return value (in this case, set mem_size for PTR_TO_MEM). Theresultant mem_size for the R0 is derived from the constant value, and ifthe verifier incorrectly prunes states considering them equivalent wheresuch arguments exist (by seeing that both registers have reg->precise asfalse in regsafe), we can end up with invalid programs passing theverifier which can do access beyond what should have been the correctmem_size in that explored state.To show a concrete example of the problem:0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32 *)(r1 + 0) = r2 7: r1 = *(u32 *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -10000000000000058 <LBB5_3>: 11: r1 = 0 ll 13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7 <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18: w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpf_ringbuf_submit00000000000000b8 <LBB5_5>: 23: w0 = 0 24: exitFor the first case, the single line execution s exploration will prunethe search at insn 14 for the branch insn 9 s second leg as it will beverified first using r2 = -1 (UINT_MAX), while as w1 at insn 9 willalways be 0 so at runtime we don t get error for being greater thanUINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe justsees reg->precise as false for both r2 registers in both states, henceconsiders them equal for purposes of states_equal.If we propagated precise markers using the backtracking support, wewould use the precise marking to then ensure that old r2 (UINT_MAX) waswithin the new r2 (1) and this would never be true, so the verificationwould rightfully fail.The end result is that the out of bounds access at instruction 19 wouldbe permitted without this fix.Note that reg->precise is always set to true when user does not haveCAP_BPF (or when subprog count is greater than 1 (i.e. use of any staticor global functions)), hence this is only a problem when precision marksneed to be explicitly propagated (i.e. privileged users with CAP_BPF).A simplified test case has been included in the next patch to preventfuture regressions. 漏洞公开时间：2025-06-18 19:15:23 漏洞创建时间：2025-06-19 10:39:03 漏洞详情参考链接： https://nvd.nist.gov/vuln/detail/CVE-2022-49961 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | | | https://access.redhat.com/security/cve/CVE-2022-49961 | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | </details> 漏洞分析指导链接： https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息： <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://github.com/gregkh/linux/commit/2459615a8d7f44ac81f0965bc094e55ccb254717.patch | | ljqc | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | nvd | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | nvd | | | | https://git.kernel.org/stable/c/2459615a8d7f44ac81f0965bc094e55ccb254717 | | snyk | | | | https://git.kernel.org/stable/c/2fc31465c5373b5ca4edf2e5238558cb62902311 | | snyk | </details> 二、漏洞分析结构反馈 影响性分析说明： In the Linux kernel, the following vulnerability has been resolved:bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZEROPrecision markers need to be propagated whenever we have an ARG_CONST_*style argument, as the verifier cannot consider imprecise scalars to beequivalent for the purposes of states_equal check when such argumentsrefine the return value (in this case, set mem_size for PTR_TO_MEM). Theresultant mem_size for the R0 is derived from the constant value, and ifthe verifier incorrectly prunes states considering them equivalent wheresuch arguments exist (by seeing that both registers have reg->precise asfalse in regsafe), we can end up with invalid programs passing theverifier which can do access beyond what should have been the correctmem_size in that explored state.To show a concrete example of the problem:0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32 *)(r1 + 0) = r2 7: r1 = *(u32 *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -10000000000000058 <LBB5_3>: 11: r1 = 0 ll 13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7 <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18: w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpf_ringbuf_submit00000000000000b8 <LBB5_5>: 23: w0 = 0 24: exitFor the first case, the single line execution's exploration will prunethe search at insn 14 for the branch insn 9's second leg as it will beverified first using r2 = -1 (UINT_MAX), while as w1 at insn 9 willalways be 0 so at runtime we don't get error for being greater thanUINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe justsees reg->precise as false for both r2 registers in both states, henceconsiders them equal for purposes of states_equal.If we propagated precise markers using the backtracking support, wewould use the precise marking to then ensure that old r2 (UINT_MAX) waswithin the new r2 (1) and this would never be true, so the verificationwould rightfully fail.The end result is that the out of bounds access at instruction 19 wouldbe permitted without this fix.Note that reg->precise is always set to true when user does not haveCAP_BPF (or when subprog count is greater than 1 (i.e. use of any staticor global functions)), hence this is only a problem when precision marksneed to be explicitly propagated (i.e. privileged users with CAP_BPF).A simplified test case has been included in the next patch to preventfuture regressions.The Linux kernel CVE team has assigned CVE-2022-49961 to this issue. openEuler评分： 3.9 Vector：CVSS：3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L 受影响版本排查(受影响/不受影响)： 1.openEuler-22.03-LTS-SP3(5.10.0):受影响 2.openEuler-22.03-LTS-SP4(5.10.0):受影响 3.master(6.12.33):不受影响 4.openEuler-20.03-LTS-SP4(4.19.90):不受影响 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):不受影响 8.openEuler-24.03-LTS-SP2(6.6.0):不受影响 修复是否涉及abi变化(是/否)： 1.master(6.12.33):否 2.openEuler-20.03-LTS-SP4(4.19.90):否 3.openEuler-22.03-LTS-SP3(5.10.0):否 4.openEuler-22.03-LTS-SP4(5.10.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):否 8.openEuler-24.03-LTS-SP2(6.6.0):否 原因说明： 1.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围 2.openEuler-22.03-LTS-SP4(5.10.0):不修复-超出修复范围 3.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 4.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不能被攻击者触发 5.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 6.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不能被攻击者触发 7.openEuler-24.03-LTS-SP2(6.6.0):不受影响-漏洞代码不能被攻击者触发 8.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在 三、漏洞修复 安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1877
Comments (
7
)
Sign in
to comment
Status
Done
Backlog
已挂起
Doing
Done
Declined
Assignees
Not set
CTC-Xibo.Wang
CTC-XiboWang
Assignee
Collaborator
+Assign
+Mention
Labels
CVE/FIXED
sig/Kernel
Not set
Projects
Unprojected
Unprojected
Milestones
No related milestones
No related milestones
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
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
