CVE-2026-93146: time/namespace: Validate nanosecond field in proc_timens_set_offset()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 06aba58e58492d2b8eae059274caed29025ea96e, 1f0c3c0c36c7aedf55a60d9c71c4bd258b8937ce, 5b8a40de738b7c4896c2edbc6262bd1b3462ded0.
Low priority for now. Upgrade to Linux Linux 06aba58e58492d2b8eae059274caed29025ea96e, 1f0c3c0c36c7aedf55a60d9c71c4bd258b8937ce, 5b8a40de738b7c4896c2edbc6262bd1b3462ded0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.6affected
- 04a8682a71becdb639ec9c0d82b315a2baef7a5d and later · before ce0dd307dfa3193fbf06371b7c819a6bff7d3d68affected · git
- 04a8682a71becdb639ec9c0d82b315a2baef7a5d and later · before 5b8a40de738b7c4896c2edbc6262bd1b3462ded0affected · git
- 04a8682a71becdb639ec9c0d82b315a2baef7a5d and later · before b20d7085ab314672447322c10cc5d1ba443e3b8eaffected · git
- 04a8682a71becdb639ec9c0d82b315a2baef7a5d and later · before db667d2970c756cc7b483f45f272440f845a665baffected · git
- 04a8682a71becdb639ec9c0d82b315a2baef7a5d and later · before 1f0c3c0c36c7aedf55a60d9c71c4bd258b8937ceaffected · git
- 04a8682a71becdb639ec9c0d82b315a2baef7a5d and later · before 06aba58e58492d2b8eae059274caed29025ea96eaffected · git
- before 5.6not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93144Sep 17, 2026 · bpf: Reject writes through untrusted BTF pointers31Monitor
- ← EarlierCVE-2026-93145Sep 17, 2026 · clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister()0Monitor
- Later →CVE-2026-93147Sep 17, 2026 · s390/bpf: Replace ly instruction with llgf31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 06aba58e58492d2b8eae059274caed29025ea96e | Vendor (CNA) |
| Linux Linux | 1f0c3c0c36c7aedf55a60d9c71c4bd258b8937ce | Vendor (CNA) |
| Linux Linux | 5b8a40de738b7c4896c2edbc6262bd1b3462ded0 | Vendor (CNA) |
| Linux Linux | b20d7085ab314672447322c10cc5d1ba443e3b8e | Vendor (CNA) |
| Linux Linux | ce0dd307dfa3193fbf06371b7c819a6bff7d3d68 | Vendor (CNA) |
| Linux Linux | db667d2970c756cc7b483f45f272440f845a665b | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/1f0c3c0c36c7aedf55a60d9c71c4bd258b8937ce
- git.kernel.org/stable/c/5b8a40de738b7c4896c2edbc6262bd1b3462ded0
- git.kernel.org/stable/c/b20d7085ab314672447322c10cc5d1ba443e3b8e
- git.kernel.org/stable/c/ce0dd307dfa3193fbf06371b7c819a6bff7d3d68
- git.kernel.org/stable/c/db667d2970c756cc7b483f45f272440f845a665b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.