Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2022-48929 | First vendor Publication | 2024-08-22 |
| Vendor | Cve | Last vendor Modification | 2024-08-23 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
|---|---|---|---|
| Overall CVSS Score | 5.5 | ||
| Base Score | 5.5 | Environmental Score | 5.5 |
| impact SubScore | 3.6 | Temporal Score | 5.5 |
| Exploitabality Sub Score | 1.8 | ||
| Attack Vector | Local | Attack Complexity | Low |
| Privileges Required | Low | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | None |
| Integrity Impact | None | Availability Impact | High |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| In the Linux kernel, the following vulnerability has been resolved: bpf: Fix crash due to out of bounds access into reg2btf_ids. When commit e6ac2450d6de ("bpf: Support bpf program calling kernel function") added kfunc support, it defined reg2btf_ids as a cheap way to translate the verifier reg type to the appropriate btf_vmlinux BTF ID, however commit c25b2ae13603 ("bpf: Replace PTR_TO_XXX_OR_NULL with PTR_TO_XXX | PTR_MAYBE_NULL") moved the __BPF_REG_TYPE_MAX from the last member of bpf_reg_type enum to after the base register types, and defined other variants using type flag composition. However, now, the direct usage of reg->type to index into reg2btf_ids may no longer fall into __BPF_REG_TYPE_MAX range, and hence lead to out of bounds access and kernel crash on dereference of bad pointer. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48929 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-125 | Out-of-bounds Read |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-01-08 02:47:31 |
|
| 2025-01-07 02:47:08 |
|
| 2024-12-25 02:45:55 |
|
| 2024-12-12 02:48:48 |
|
| 2024-11-22 02:46:13 |
|
| 2024-11-20 02:43:37 |
|
| 2024-11-14 02:43:29 |
|
| 2024-11-09 02:44:08 |
|
| 2024-10-26 02:41:53 |
|
| 2024-10-25 02:43:39 |
|
| 2024-10-23 02:43:03 |
|
| 2024-10-03 02:39:07 |
|
| 2024-10-02 02:37:30 |
|
| 2024-09-04 02:36:46 |
|
| 2024-08-23 09:27:31 |
|
| 2024-08-23 02:48:13 |
|
| 2024-08-23 02:34:45 |
|
| 2024-08-22 17:27:24 |
|
| 2024-08-22 09:27:25 |
|
