# CVE-2022-0435: Memory corruption in kernel

> A stack overflow in the Linux kernel TIPC protocol allows remote attackers to crash the system or escalate privileges if they have network access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** A-228560328, AZL-9239, CLSA-2022-1644934107, DEBIAN-CVE-2022-0435, PUB-A-228560328, RHSA-2022:1186, RHSA-2022:1589, RHSA-2022:1619, SUSE-SU-2022:0429-1, UBUNTU-CVE-2022-0435

## What is CVE-2022-0435?

CVE-2022-0435 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 25 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A stack overflow flaw was found in the Linux kernel's TIPC protocol functionality in the way a user sends a packet with malicious content where the number of domain member nodes is higher than the 64 allowed. This flaw allows a remote user to crash the system or possibly escalate their privileges if they have access to the TIPC network.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 30 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bpftool` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `bpftool-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-abi-whitelists` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-core` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debug` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debug-core` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debug-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debug-devel` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debug-modules` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debug-modules-extra` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-debuginfo-common-x86_64` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-devel` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-doc` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-modules` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-modules-extra` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-tools` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-tools-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kernel-tools-libs` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:4.18.0-147.65.1.el8_1 |
| `kpatch-patch-4_18_0-147_48_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-8.el8_1 |
| `kpatch-patch-4_18_0-147_48_1-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-8.el8_1 |
| `kpatch-patch-4_18_0-147_48_1-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-8.el8_1 |
| `kpatch-patch-4_18_0-147_51_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-7.el8_1 |
| `kpatch-patch-4_18_0-147_51_1-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-7.el8_1 |
| `kpatch-patch-4_18_0-147_51_1-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-7.el8_1 |
| `kpatch-patch-4_18_0-147_51_2` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-6.el8_1 |
| `kpatch-patch-4_18_0-147_51_2-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-6.el8_1 |
| `kpatch-patch-4_18_0-147_51_2-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-6.el8_1 |
| `kpatch-patch-4_18_0-147_52_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-5.el8_1 |
| `kpatch-patch-4_18_0-147_52_1-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-5.el8_1 |
| `kpatch-patch-4_18_0-147_52_1-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-5.el8_1 |
| `kpatch-patch-4_18_0-147_54_2` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-4.el8_1 |
| `kpatch-patch-4_18_0-147_54_2-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-4.el8_1 |
| `kpatch-patch-4_18_0-147_54_2-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-4.el8_1 |
| `kpatch-patch-4_18_0-147_56_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-4.el8_1 |
| `kpatch-patch-4_18_0-147_56_1-debuginfo` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-4.el8_1 |
| `kpatch-patch-4_18_0-147_56_1-debugsource` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-4.el8_1 |
| `kpatch-patch-4_18_0-147_57_1` | Red Hat:rhel_e4s:8.1::baseos | All versions | 0:1-3.el8_1 |

Products: Fedoraproject Fedora, Linux kernel, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H700e Firmware, Netapp H700s Firmware, Ovirt Node, Redhat Codeready Linux Builder, Redhat Codeready Linux Builder Eus, Redhat Codeready Linux Builder Eus for Power Little Endian, Redhat Codeready Linux Builder for Power Little Endian Eus, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Power Little Endian Eus and 10 more.

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

Apply the vendor's patch.

## Is CVE-2022-0435 being exploited?

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

Public exploit code:

- https://github.com/wlswotmd/CVE-2022-0435 (github_poc): https://github.com/wlswotmd/CVE-2022-0435
- https://github.com/Spydomain/CVE-2022-0435-Poc (github_poc): https://github.com/Spydomain/CVE-2022-0435-Poc
- https://github.com/sandesh9978/CVE-2022-0435 (github_poc): https://github.com/sandesh9978/CVE-2022-0435

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0435 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 25 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0435 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-0435/ (Markdown: https://insights.sbomify.com/CVE-2022-0435/index.md)
```

## Sources

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

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