What is CVE-2022-48929?

CVE-2022-48929 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Out-of-bounds Read flaw (CWE-125), affecting Linux kernel versions from 5.16.11 onward and patched in 5.16.12. CVE-2022-48929 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2022-48929?

CVE-2022-48929 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2022-48929?

Yes, CVE-2022-48929 has been patched. Fixed versions include 5.16.12. If you are running Linux kernel 5.16.11 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2022-48929 actively exploited?

CVE-2022-48929 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Out-of-bounds Read (CWE-125)?

The product reads data past the end or before the beginning of the intended buffer. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/125.html

CVE-2022-48929

Medium

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.

Package Linux Kernel

Published 2024-08-22

Last modified 2024-08-23

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-125

CVE-2022-48929 is a Out-of-bounds Read vulnerability

What is Out-of-bounds Read?

The product reads data past the end or before the beginning of the intended buffer. Learn more on MITRE CWE

Affected versions

Linux kernel versions 5.16.11 and later are affected. Fixed in 5.16.12 and their respective stable series.

Affected from

≥ 5.16.11

Fixed in

✓ 5.16.12 5.16.x

References

3 total

Kernel Git
https://git.kernel.org/stable/c/45ce4b4f9009102cd9f581196d480a59208690c1

Patch
Kernel Git
https://git.kernel.org/stable/c/8c39925e98d498b9531343066ef82ae39e41adae

Patch
Kernel Git
https://git.kernel.org/stable/c/f0ce1bc9e0235dd7412240be493d7ea65ed9eadc

Patch

Details

CVE ID CVE-2022-48929

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2024-08-22

Modified 2024-08-23

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2022-48929?

CVE-2022-48929 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Out-of-bounds Read flaw (CWE-125) . It affects Linux kernel versions from 5.16.11 onward and has been patched in 5.16.12. CVE-2022-48929 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2022-48929?

CVE-2022-48929 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2022-48929?

Yes. CVE-2022-48929 has been patched. Fixed versions include 5.16.12. If you are running Linux kernel 5.16.11 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2022-48929 actively exploited?

No. CVE-2022-48929 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.