CVE-2004-1017 Memory corruption in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2004-1017 and fix it if it is affected.
What it is: CVE-2004-1017 is a critical memory corruption vulnerability in Linux kernel, published on 31 Dec 2004.
Exploitation: There is no known exploitation of CVE-2004-1017 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-2004-1017/ (Markdown: https://insights.sbomify.com/CVE-2004-1017/index.md)
Multiple overflows in the Linux kernel io_edgeport driver allow attackers to potentially cause memory corruption with unknown impact.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is CVE-2004-1017?
CVE-2004-1017 is a critical memory corruption vulnerability in Linux kernel, published on 31 Dec 2004.
Official description
Multiple "overflows" in the io_edgeport driver for Linux kernel 2.4.x have unknown impact and unknown attack vectors.
Which versions are affected by CVE-2004-1017?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2004-1017?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2004-1017 being exploited?
There is no known exploitation of CVE-2004-1017 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as GHSA-4jh8-f2cr-j6hg.