# GSD-2023-1000640: fs/ntfs3: Harden against integer overflows

> Hardening against integer overflows in the Linux kernel NTFS3 filesystem driver to prevent potential security issues.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 17 Jan 2023

## What is GSD-2023-1000640?

GSD-2023-1000640 is a vulnerability in Kernel, published on 17 Jan 2023. 

### Official description

fs/ntfs3: Harden against integer overflows

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v6.0.16 by commit 25869ba2dcada03a30e1652c1825e9af5eb5b644, it was introduced in version v5.15 by commit be71b5cba2e6485e8959da7a9f9a44461a1bb074. For more details please see the references link.

## Which versions are affected by GSD-2023-1000640?

1 open source package ship an affected version, including Kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Kernel` | Linux | All versions | None |

## How do I fix GSD-2023-1000640?

No fix has been published for GSD-2023-1000640 yet. Limit exposure of the affected software until one is available.

## Is GSD-2023-1000640 being exploited?

There is no known exploitation of GSD-2023-1000640 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2023-1000640 and fix it if it is affected.

What it is: GSD-2023-1000640 is a vulnerability in Kernel, published on 17 Jan 2023. 
Exploitation: There is no known exploitation of GSD-2023-1000640 in the wild and no public exploit code.

Affected packages and fixed versions:
- Kernel (Linux): affected all versions; no fix listed

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/GSD-2023-1000640/ (Markdown: https://insights.sbomify.com/GSD-2023-1000640/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2023-1000640

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