# CVE-2017-17053: Use after free in n/a

> A local attacker can trigger a use-after-free in the Linux kernel LDT handling to execute code or escalate privileges, requiring a specific kernel configuration.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/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:** 29 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-17053, GHSA-qv5h-fq2w-c68j, UBUNTU-CVE-2017-17053

## What is CVE-2017-17053?

CVE-2017-17053 is a high-severity use after free vulnerability in Linux kernel, published on 29 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The init_new_context function in arch/x86/include/asm/mmu_context.h in the Linux kernel before 4.12.10 does not correctly handle errors from LDT table allocation when forking a new process, allowing a local attacker to achieve a use-after-free or possibly have unspecified other impact by running a specially crafted program. This vulnerability only affected kernels built with CONFIG_MODIFY_LDT_SYSCALL=y.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2017-17053 being exploited?

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

What it is: CVE-2017-17053 is a high-severity use after free vulnerability in Linux kernel, published on 29 Nov 2017. 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-2017-17053 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-17053/ (Markdown: https://insights.sbomify.com/CVE-2017-17053/index.md)
```

## Sources

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

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