# CVE-2022-2964: Memory corruption in kernel

> Out-of-bounds reads and writes in the ASIX AX88179_178A USB Ethernet driver allow attackers to execute code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 9 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** CVE-2022-28748, DEBIAN-CVE-2022-2964, GHSA-fqwg-v36p-p5p4, RHSA-2023:0392, RHSA-2023:0396, RHSA-2023:0404, UBUNTU-CVE-2022-2964

## What is CVE-2022-2964?

CVE-2022-2964 is a high-severity memory corruption vulnerability in Linux kernel, published on 9 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the Linux kernel’s driver for the ASIX AX88179_178A-based USB 2.0/3.0 Gigabit Ethernet Devices. The vulnerability contains multiple out-of-bounds reads and possible out-of-bounds writes.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kpatch-patch-3_10_0-1160_71_1` | Red Hat:enterprise_linux:7::server | All versions | 0:1-2.el7 |
| `kpatch-patch-3_10_0-1160_71_1-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1-2.el7 |
| `kpatch-patch-3_10_0-1160_76_1` | Red Hat:enterprise_linux:7::server | All versions | 0:1-2.el7 |
| `kpatch-patch-3_10_0-1160_76_1-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1-2.el7 |
| `kpatch-patch-3_10_0-1160_80_1` | Red Hat:enterprise_linux:7::server | All versions | 0:1-1.el7 |
| `kpatch-patch-3_10_0-1160_80_1-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1-1.el7 |
| `kpatch-patch-3_10_0-1160_81_1` | Red Hat:enterprise_linux:7::server | All versions | 0:1-1.el7 |
| `kpatch-patch-3_10_0-1160_81_1-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1-1.el7 |
| `kpatch-patch-4_18_0-193_87_1` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_87_1-debuginfo` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_87_1-debugsource` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_90_1` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_90_1-debuginfo` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_90_1-debugsource` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_91_1` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_91_1-debuginfo` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_91_1-debugsource` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-3.el8_2 |
| `kpatch-patch-4_18_0-193_93_1` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-2.el8_2 |
| `kpatch-patch-4_18_0-193_93_1-debuginfo` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-2.el8_2 |
| `kpatch-patch-4_18_0-193_93_1-debugsource` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-2.el8_2 |
| `kpatch-patch-4_18_0-193_95_1` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-1.el8_2 |
| `kpatch-patch-4_18_0-193_95_1-debuginfo` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-1.el8_2 |
| `kpatch-patch-4_18_0-193_95_1-debugsource` | Red Hat:rhel_e4s:8.2::baseos | All versions | 0:1-1.el8_2 |
| `kernel-rt` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-core` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debug` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debug-core` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debug-debuginfo` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debug-devel` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debug-kvm` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debug-modules` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debug-modules-extra` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debuginfo` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-debuginfo-common-x86_64` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-devel` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-kvm` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-modules` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-modules-extra` | Red Hat:rhel_tus:8.2::nfv | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt` | Red Hat:rhel_tus:8.2::realtime | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |
| `kernel-rt-core` | Red Hat:rhel_tus:8.2::realtime | All versions | 0:4.18.0-193.98.1.rt13.149.el8_2 |

Products: Linux kernel, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware, Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2022-2964 being exploited?

There is no known exploitation of CVE-2022-2964 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-2964 and fix it if it is affected.

What it is: CVE-2022-2964 is a high-severity memory corruption vulnerability in Linux kernel, published on 9 Sep 2022. 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-2964 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-2964/ (Markdown: https://insights.sbomify.com/CVE-2022-2964/index.md)
```

## Sources

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

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