CVE-2026-93201 (GCVE-0-2026-93201)
Vulnerability from cvelistv5 – Published: 2026-09-17 16:12 – Updated: 2026-09-17 16:12
VLAI
EPSS
VEX
Title
dm-pcache: validate seg_id fields from persistent memory
Summary
In the Linux kernel, the following vulnerability has been resolved:
dm-pcache: validate seg_id fields from persistent memory
cache_pos_decode(), cache_key_decode() and the last-kset branches of
cache_replay(), the writeback worker and the GC worker take a cache
segment id from the cache device metadata and index cache->segments[]
with it without checking it against cache->n_segs. That metadata is only
CRC-protected with a fixed public seed, so whoever supplies the cache
device on a table load (CAP_SYS_ADMIN) controls the id; an out-of-range
value forms a wild pcache_cache_segment pointer that is dereferenced and
written through -- an out-of-bounds read and write driven by on-disk data.
Add cache_seg_id_valid() and reject an out-of-range id at each decode
site, failing the operation with -EIO instead of indexing past the array.
Bound the id against the initialized-segment count (cache_info.n_segs)
rather than the physical device total. A forged cache_info.n_segs below
seg_num otherwise leaves segments[cache_info.n_segs..seg_num) as zeroed
structs whose data pointer is NULL, so a forged id in that window would
still be dereferenced. A later patch guarantees cache_info.n_segs <=
seg_num, and a driver-created cache sets the two equal, so valid images
are unaffected.
Severity
No CVSS data available.
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 , < b4bf8af5e7d7db4c5e179e15017da55857761ac4
(git)
Affected: 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 , < 90c990a68460d7b5720e5634cf650eccdf0f4098 (git) |
guessed | |
| Linux | Linux |
Affected:
6.18
Unaffected: 0 , < 6.18 (semver) Unaffected: 7.2.6 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/md/dm-pcache/cache.c",
"drivers/md/dm-pcache/cache.h",
"drivers/md/dm-pcache/cache_gc.c",
"drivers/md/dm-pcache/cache_key.c",
"drivers/md/dm-pcache/cache_writeback.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "b4bf8af5e7d7db4c5e179e15017da55857761ac4",
"status": "affected",
"version": "1d57628ff95b32d5cfa8d8f50e07690c161e9cf0",
"versionType": "git"
},
{
"lessThan": "90c990a68460d7b5720e5634cf650eccdf0f4098",
"status": "affected",
"version": "1d57628ff95b32d5cfa8d8f50e07690c161e9cf0",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/md/dm-pcache/cache.c",
"drivers/md/dm-pcache/cache.h",
"drivers/md/dm-pcache/cache_gc.c",
"drivers/md/dm-pcache/cache_key.c",
"drivers/md/dm-pcache/cache_writeback.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.18"
},
{
"lessThan": "6.18",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.6",
"versionStartIncluding": "6.18",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3-rc1",
"versionStartIncluding": "6.18",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm-pcache: validate seg_id fields from persistent memory\n\ncache_pos_decode(), cache_key_decode() and the last-kset branches of\ncache_replay(), the writeback worker and the GC worker take a cache\nsegment id from the cache device metadata and index cache-\u003esegments[]\nwith it without checking it against cache-\u003en_segs. That metadata is only\nCRC-protected with a fixed public seed, so whoever supplies the cache\ndevice on a table load (CAP_SYS_ADMIN) controls the id; an out-of-range\nvalue forms a wild pcache_cache_segment pointer that is dereferenced and\nwritten through -- an out-of-bounds read and write driven by on-disk data.\n\nAdd cache_seg_id_valid() and reject an out-of-range id at each decode\nsite, failing the operation with -EIO instead of indexing past the array.\nBound the id against the initialized-segment count (cache_info.n_segs)\nrather than the physical device total. A forged cache_info.n_segs below\nseg_num otherwise leaves segments[cache_info.n_segs..seg_num) as zeroed\nstructs whose data pointer is NULL, so a forged id in that window would\nstill be dereferenced. A later patch guarantees cache_info.n_segs \u003c=\nseg_num, and a driver-created cache sets the two equal, so valid images\nare unaffected."
}
],
"providerMetadata": {
"dateUpdated": "2026-09-17T16:12:22.392Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/b4bf8af5e7d7db4c5e179e15017da55857761ac4"
},
{
"url": "https://git.kernel.org/stable/c/90c990a68460d7b5720e5634cf650eccdf0f4098"
}
],
"title": "dm-pcache: validate seg_id fields from persistent memory",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-93201",
"datePublished": "2026-09-17T16:12:22.392Z",
"dateReserved": "2026-09-17T16:02:15.092Z",
"dateUpdated": "2026-09-17T16:12:22.392Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2026-93201\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-09-17T17:18:16.403\",\"lastModified\":\"2026-09-17T17:18:16.403\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndm-pcache: validate seg_id fields from persistent memory\\n\\ncache_pos_decode(), cache_key_decode() and the last-kset branches of\\ncache_replay(), the writeback worker and the GC worker take a cache\\nsegment id from the cache device metadata and index cache-\u003esegments[]\\nwith it without checking it against cache-\u003en_segs. That metadata is only\\nCRC-protected with a fixed public seed, so whoever supplies the cache\\ndevice on a table load (CAP_SYS_ADMIN) controls the id; an out-of-range\\nvalue forms a wild pcache_cache_segment pointer that is dereferenced and\\nwritten through -- an out-of-bounds read and write driven by on-disk data.\\n\\nAdd cache_seg_id_valid() and reject an out-of-range id at each decode\\nsite, failing the operation with -EIO instead of indexing past the array.\\nBound the id against the initialized-segment count (cache_info.n_segs)\\nrather than the physical device total. A forged cache_info.n_segs below\\nseg_num otherwise leaves segments[cache_info.n_segs..seg_num) as zeroed\\nstructs whose data pointer is NULL, so a forged id in that window would\\nstill be dereferenced. A later patch guarantees cache_info.n_segs \u003c=\\nseg_num, and a driver-created cache sets the two equal, so valid images\\nare unaffected.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/md/dm-pcache/cache.c\",\"drivers/md/dm-pcache/cache.h\",\"drivers/md/dm-pcache/cache_gc.c\",\"drivers/md/dm-pcache/cache_key.c\",\"drivers/md/dm-pcache/cache_writeback.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"1d57628ff95b32d5cfa8d8f50e07690c161e9cf0\",\"lessThan\":\"b4bf8af5e7d7db4c5e179e15017da55857761ac4\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"1d57628ff95b32d5cfa8d8f50e07690c161e9cf0\",\"lessThan\":\"90c990a68460d7b5720e5634cf650eccdf0f4098\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/md/dm-pcache/cache.c\",\"drivers/md/dm-pcache/cache.h\",\"drivers/md/dm-pcache/cache_gc.c\",\"drivers/md/dm-pcache/cache_key.c\",\"drivers/md/dm-pcache/cache_writeback.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.18\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.18\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.2.6\",\"lessThanOrEqual\":\"7.2.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.3-rc1\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/90c990a68460d7b5720e5634cf650eccdf0f4098\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b4bf8af5e7d7db4c5e179e15017da55857761ac4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
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…