# CVE-2017-2634: Memory corruption in kernel:

> A remote attacker can crash the Linux kernel by exploiting a memory corruption flaw in the DCCP protocol implementation.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/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:** 27 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qmpj-vx37-329m

## What is CVE-2017-2634?

CVE-2017-2634 is a high-severity memory corruption vulnerability in Linux kernel, published on 27 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was found that the Linux kernel's Datagram Congestion Control Protocol (DCCP) implementation before 2.6.22.17 used the IPv4-only inet_sk_rebuild_header() function for both IPv4 and IPv6 DCCP connections, which could result in memory corruptions. A remote attacker could use this flaw to crash the system.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2017-2634?

It affects 5 products.


Products: Linux kernel, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2017-2634?

Apply the vendor's patch.

## Is CVE-2017-2634 being exploited?

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

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

## Sources

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

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