GHSA-477F-QMJ2-58HM
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-93146"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:09Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ntime/namespace: Validate nanosecond field in proc_timens_set_offset()\n\nThe function validates tv_sec to be within [-KTIME_SEC_MAX, KTIME_SEC_MAX]\nbut never validates that tv_nsec is within the valid range of\n[0, NSEC_PER_SEC-1] before using it in timespec64_add().\n\ntimespec64_add() expects both timespec64 structures to have normalized\nvalues with tv_nsec in the range [0, 999999999]. If off-\u003eval.tv_nsec\ncontains invalid values (negative or \u003e= NSEC_PER_SEC), it could lead to\nincorrect calculations or unexpected behavior.\n\nAdd validation to ensure tv_nsec is within the valid range before\nperforming the addition.",
"id": "GHSA-477f-qmj2-58hm",
"modified": "2026-09-17T18:32:12Z",
"published": "2026-09-17T18:32:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93146"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/06aba58e58492d2b8eae059274caed29025ea96e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1f0c3c0c36c7aedf55a60d9c71c4bd258b8937ce"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/db667d2970c756cc7b483f45f272440f845a665b"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.