{"api_version":"1","generated_at":"2026-09-14T04:31:50+00:00","cve":"CVE-2026-80962","urls":{"html":"https://cve.report/CVE-2026-80962","api":"https://cve.report/api/cve/CVE-2026-80962.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80962","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80962"},"summary":{"title":"dm-pcache: validate geometry fields from on-disk cache_info","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm-pcache: validate geometry fields from on-disk cache_info\n\ncache_segs_init() iterates cache_info->n_segs times indexing\ncache->segments[], which is sized to the cache device geometry, and\nget_seg_id() takes each segment id from the on-media cache_info and the\nper-segment next_seg link. Both come from cache device metadata that is\nonly CRC-protected with a fixed public seed, so whoever supplies the\ncache device on a table load (CAP_SYS_ADMIN) controls them: an oversized\nn_segs or an out-of-range id drives an out-of-bounds access of\ncache->segments[] and a wild CACHE_DEV_SEGMENT() pointer into the device\nmapping -- an out-of-bounds read and write from on-disk data.\n\nReject an n_segs that exceeds the device segment count and a segment id\nthat is out of range before either is used. Valid metadata is unaffected.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:19:02","updated_at":"2026-09-13 07:17:03"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/ab5dcde6fa96bc115b85f3621c60e39c66229a90","name":"https://git.kernel.org/stable/c/ab5dcde6fa96bc115b85f3621c60e39c66229a90","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/32d1809da31094ef76fd98dc1f1a8b55ca1295dd","name":"https://git.kernel.org/stable/c/32d1809da31094ef76fd98dc1f1a8b55ca1295dd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3e19172089ec81132a8a48e802b1034a744209f4","name":"https://git.kernel.org/stable/c/3e19172089ec81132a8a48e802b1034a744209f4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80962","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80962","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 ab5dcde6fa96bc115b85f3621c60e39c66229a90 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 3e19172089ec81132a8a48e802b1034a744209f4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 32d1809da31094ef76fd98dc1f1a8b55ca1295dd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80962","cve":"CVE-2026-80962","epss":"0.001610000","percentile":"0.056680000","score_date":"2026-09-13","updated_at":"2026-09-14 00:18:01"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/md/dm-pcache/cache.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ab5dcde6fa96bc115b85f3621c60e39c66229a90","status":"affected","version":"1d57628ff95b32d5cfa8d8f50e07690c161e9cf0","versionType":"git"},{"lessThan":"3e19172089ec81132a8a48e802b1034a744209f4","status":"affected","version":"1d57628ff95b32d5cfa8d8f50e07690c161e9cf0","versionType":"git"},{"lessThan":"32d1809da31094ef76fd98dc1f1a8b55ca1295dd","status":"affected","version":"1d57628ff95b32d5cfa8d8f50e07690c161e9cf0","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/md/dm-pcache/cache.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":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","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":"6.18.50","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","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 geometry fields from on-disk cache_info\n\ncache_segs_init() iterates cache_info->n_segs times indexing\ncache->segments[], which is sized to the cache device geometry, and\nget_seg_id() takes each segment id from the on-media cache_info and the\nper-segment next_seg link. Both come from cache device metadata that is\nonly CRC-protected with a fixed public seed, so whoever supplies the\ncache device on a table load (CAP_SYS_ADMIN) controls them: an oversized\nn_segs or an out-of-range id drives an out-of-bounds access of\ncache->segments[] and a wild CACHE_DEV_SEGMENT() pointer into the device\nmapping -- an out-of-bounds read and write from on-disk data.\n\nReject an n_segs that exceeds the device segment count and a segment id\nthat is out of range before either is used. Valid metadata is unaffected."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The OOB access is reached only through a local device-mapper table load on /dev/mapper/control (ctl_ioctl → table_load → populate_table → dm_pcache_ctr → pcache_start → pcache_cache_start → cache_segs_init/get_seg_id). No network, Bluetooth, or USB path feeds on-disk cache_info geometry.\nAC:L - The attacker fully controls on-media cache_info.n_segs, cache_info.seg_id and each segment next_seg, and can forge a passing CRC because PCACHE_CRC_SEED (0x3B15A) is public, so a crafted INIT_DONE image with oversized n_segs or out-of-range ids hits the OOB on every table load with no race.\nPR:L - ctl_ioctl gates DM_TABLE_LOAD with capable(CAP_SYS_ADMIN). In the most severe reasonable deployment that capability is held by a container or storage-stack administrator with delegated mapper and DAX/pmem nodes rather than exclusive host root, which kernel-CNA scoring of device-mapper table-load bugs maps to Low.\nUI:N - The attacker crafts the DAX cache-device metadata and issues DM_TABLE_LOAD themselves; no separate victim must mount a filesystem, open a file, or otherwise interact.\nS:U - Out-of-bounds indexing of cache->segments[] and wild CACHE_DEV_SEGMENT() pointers corrupt kernel memory on the same host that loaded the table. This stays within one kernel security authority and is not a VM escape or IOMMU bypass.\nC:H - An out-of-range seg_id makes CACHE_DEV_SEGMENT() point past the DAX mapping into kernel memory, and cache_seg_meta_load() copy_mc_to_kernel's that region; oversized n_segs also reads past the kvalloc'd segments[] array. That kernel memory-corruption read primitive is Confidentiality High.\nI:H - cache_seg_init() writes pcache_cache_segment fields past the kvalloc'd cache->segments[] when n_segs exceeds seg_num, and a wild CACHE_DEV_SEGMENT() is later written through memcpy_flushcache/memset. That out-of-bounds kernel write is Integrity High and exploitable for code execution.\nA:H - Heap overflow of cache->segments[] or dereference of a mapping-relative pointer past the DAX device causes a kernel oops or panic at table load, fully denying availability."}]}],"providerMetadata":{"dateUpdated":"2026-09-13T06:28:34.108Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ab5dcde6fa96bc115b85f3621c60e39c66229a90"},{"url":"https://git.kernel.org/stable/c/3e19172089ec81132a8a48e802b1034a744209f4"},{"url":"https://git.kernel.org/stable/c/32d1809da31094ef76fd98dc1f1a8b55ca1295dd"}],"title":"dm-pcache: validate geometry fields from on-disk cache_info","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80962","datePublished":"2026-09-11T19:42:28.500Z","dateReserved":"2026-08-26T14:34:25.809Z","dateUpdated":"2026-09-13T06:28:34.108Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:19:02","lastModifiedDate":"2026-09-13 07:17:03","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80962","Ordinal":"1","Title":"dm-pcache: validate geometry fields from on-disk cache_info","CVE":"CVE-2026-80962","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80962","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm-pcache: validate geometry fields from on-disk cache_info\n\ncache_segs_init() iterates cache_info->n_segs times indexing\ncache->segments[], which is sized to the cache device geometry, and\nget_seg_id() takes each segment id from the on-media cache_info and the\nper-segment next_seg link. Both come from cache device metadata that is\nonly CRC-protected with a fixed public seed, so whoever supplies the\ncache device on a table load (CAP_SYS_ADMIN) controls them: an oversized\nn_segs or an out-of-range id drives an out-of-bounds access of\ncache->segments[] and a wild CACHE_DEV_SEGMENT() pointer into the device\nmapping -- an out-of-bounds read and write from on-disk data.\n\nReject an n_segs that exceeds the device segment count and a segment id\nthat is out of range before either is used. Valid metadata is unaffected.","Type":"Description","Title":"dm-pcache: validate geometry fields from on-disk cache_info"}]}}}