# CVE-2026-93146: time/namespace: Validate nanosecond field in proc_timens_set_offset()

> A missing validation in the Linux kernel time namespace allows local attackers to cause incorrect calculations or unexpected behavior via invalid nanosecond values.

- **Severity:** Not scored
- **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:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102281, BELL-CVE-2026-93146, DEBIAN-CVE-2026-93146, GHSA-477f-qmj2-58hm, UBUNTU-CVE-2026-93146

## What is CVE-2026-93146?

CVE-2026-93146 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

time/namespace: Validate nanosecond field in proc_timens_set_offset()

The function validates tv_sec to be within [-KTIME_SEC_MAX, KTIME_SEC_MAX]
but never validates that tv_nsec is within the valid range of
[0, NSEC_PER_SEC-1] before using it in timespec64_add().

timespec64_add() expects both timespec64 structures to have normalized
values with tv_nsec in the range [0, 999999999]. If off->val.tv_nsec
contains invalid values (negative or >= NSEC_PER_SEC), it could lead to
incorrect calculations or unexpected behavior.

Add validation to ensure tv_nsec is within the valid range before
performing the addition.

## Which versions are affected by CVE-2026-93146?


## How do I fix CVE-2026-93146?

Apply the vendor's patch.

## Is CVE-2026-93146 being exploited?

There is no known exploitation of CVE-2026-93146 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93146 and fix it if it is affected.

What it is: CVE-2026-93146 is a vulnerability in Linux, published on 17 Sep 2026. 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-2026-93146 in the wild and no public exploit code.

Affected product: Linux. 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-2026-93146/ (Markdown: https://insights.sbomify.com/CVE-2026-93146/index.md)
```

## Sources

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

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