# CVE-2022-48929: bpf: Fix crash due to out of bounds access into reg2btf_ids.

> A local attacker can trigger a kernel crash via out-of-bounds access in the BPF subsystem, causing a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2024
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-48929, GHSA-5752-wxxv-m9xh, ROOT-OS-DEBIAN-11-CVE-2022-48929, ROOT-OS-UBUNTU-2204-CVE-2022-48929, ROOT-OS-UBUNTU-2404-CVE-2022-48929, UBUNTU-CVE-2022-48929

## What is CVE-2022-48929?

CVE-2022-48929 is a medium-severity memory corruption vulnerability in Linux kernel, published on 22 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2022-48929?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2022-48929?

Apply the vendor's patch.

## Is CVE-2022-48929 being exploited?

There is no known exploitation of CVE-2022-48929 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48929 and fix it if it is affected.

What it is: CVE-2022-48929 is a medium-severity memory corruption vulnerability in Linux kernel, published on 22 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48929 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48929/ (Markdown: https://insights.sbomify.com/CVE-2022-48929/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48929
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48929
- OSV: https://osv.dev/vulnerability/CVE-2022-48929

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48929/
Summaries are generated and may contain mistakes; the official description above is the record.