GHSA-M5CM-762C-JPJJ
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32
VLAI
Details
In the Linux kernel, the following vulnerability has been resolved:
dax/fsdev: clear vmemmap_shift when binding static pgmap
Clear pgmap->vmemmap_shift for static DAX devices. When rebinding a static device from device_dax (which may set vmemmap_shift based on alignment) to fsdev_dax, the stale vmemmap_shift persists on the shared pgmap. Explicitly zero it before devm_memremap_pages() so the vmemmap is built for order-0 folios as fsdev requires.
{
"affected": [],
"aliases": [
"CVE-2026-93076"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:01Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndax/fsdev: clear vmemmap_shift when binding static pgmap\n\nClear pgmap-\u003evmemmap_shift for static DAX devices. When rebinding a static\ndevice from device_dax (which may set vmemmap_shift based on alignment) to\nfsdev_dax, the stale vmemmap_shift persists on the shared pgmap. Explicitly\nzero it before devm_memremap_pages() so the vmemmap is built for order-0\nfolios as fsdev requires.",
"id": "GHSA-m5cm-762c-jpjj",
"modified": "2026-09-17T18:32:09Z",
"published": "2026-09-17T18:32:09Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93076"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d298a0513aaf7d48f2a9f4a90041de910750cfcf"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e0239229931faf9ca3367e3befcf16f77b2cd45b"
}
],
"schema_version": "1.4.0",
"severity": []
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…