# CVE-2022-1678: Memory corruption in kernel

> Remote attackers can cause memory and network namespace leaks in the Linux kernel TCP pacing, leading to resource exhaustion and denial of service.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-1678, GHSA-x4fc-h5x4-26gr, UBUNTU-CVE-2022-1678

## What is CVE-2022-1678?

CVE-2022-1678 is a medium-severity memory corruption vulnerability in Linux kernel, published on 25 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the Linux Kernel from 4.18 to 4.19, an improper update of sock reference in TCP pacing can lead to memory/netns leak, which can be used by remote clients.

Weakness: CWE-911 (Improper Update of Reference Count)

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

It affects 17 products.


Products: Linux kernel, Netapp Active Iq Unified Manager, Netapp Bootstrap Os, Netapp Cloud Volumes Ontap Mediator, Netapp E-Series Santricity Os Controller, Netapp Element Software, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H700e Firmware, Netapp H700s Firmware, Netapp Hci Management Node, Netapp Solidfire, Netapp Storagegrid.

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

Apply the vendor's patch.

## Is CVE-2022-1678 being exploited?

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

What it is: CVE-2022-1678 is a medium-severity memory corruption vulnerability in Linux kernel, published on 25 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1678 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-1678/ (Markdown: https://insights.sbomify.com/CVE-2022-1678/index.md)
```

## Sources

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

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