dm cache: fix potential out-of-bounds access on the first resume
In the Linux kernel, the following vulnerability has been resolved: dm cache: fix potential out-of-bounds access on the first resume Out-of-bounds access occurs if the fast device is expanded unexpectedly before the first-time resume of the cache table. This happens because expanding the fast device requires reloading the cache table for cache_create to allocate new in-core data structures that fit the new size, and the check in cache_preresume is not performed during the first resume, leading to the issue. Reproduce steps: 1. prepare component devices: dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc 262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct 2. load a cache table of 512 cache blocks, and deliberately expand the fast device before resuming the cache, making the in-core data structures inadequate. dmsetup create cache --notable dmsetup reload cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" dmsetup reload cdata --table "0 131072 linear /dev/sdc 8192" dmsetup resume cdata dmsetup resume cache 3. suspend the cache to write out the in-core dirty bitset and hint array, leading to out-of-bounds access to the dirty bitset at offset 0x40: dmsetup suspend cache KASAN reports: BUG: KASAN: vmalloc-out-of-bounds in is_dirty_callback+0x2b/0x80 Read of size 8 at addr f
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.19.324, 5.10.230, 5.15.172, 5.4.286, 6.1.117, 6.11.8, 6.6.61
- CVEs
- CVE-2024-50278
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 00:56 UTC · Revision 1
Source evidence
dm cache: fix potential out-of-bounds access on the first resume
core-osv · Original sourcePublished 19 Nov 2024, 01:30 UTC
In the Linux kernel, the following vulnerability has been resolved: dm cache: fix potential out-of-bounds access on the first resume Out-of-bounds access occurs if the fast device is expanded unexpectedly before the first-time resume of the cache table. This happens because expanding the fast device requires reloading the cache table for cache_create to allocate new in-core data structures that fit the new size, and the check in cache_preresume is not performed during the first resume, leading to the issue. Reproduce steps: 1. prepare component devices: dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc 262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct 2. load a cache table of 512 cache blocks, and deliberately expand the fast device before resuming the cache, making the in-core data structures inadequate. dmsetup create cache --notable dmsetup reload cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" dmsetup reload cdata --table "0 131072 linear /dev/sdc 8192" dmsetup resume cdata dmsetup resume cache 3. suspend the cache to write out the in-core dirty bitset and hint array, leading to out-of-bounds access to the dirty bitset at offset 0x40: dmsetup suspend cache KASAN reports: BUG: KASAN: vmalloc-out-of-bounds in is_dirty_callback+0x2b/0x80 Read of size 8 at addr f
osv:CVE-2024-50278
Kernel
Fixed versions: 4.19.324, 5.4.286, 5.10.230, 5.15.172, 6.1.117, 6.6.61, 6.11.8
Complete source record
{
"id": "32a54babefbbb5f51e0dd13823c29c6298ee8c69aec5613c56709de7235a5dac",
"url": "https://osv.dev/vulnerability/CVE-2024-50278",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "dm cache: fix potential out-of-bounds access on the first resume",
"summary": "In the Linux kernel, the following vulnerability has been resolved: dm cache: fix potential out-of-bounds access on the first resume Out-of-bounds access occurs if the fast device is expanded unexpectedly before the first-time resume of the cache table. This happens because expanding the fast device requires reloading the cache table for cache_create to allocate new in-core data structures that fit the new size, and the check in cache_preresume is not performed during the first resume, leading to the issue. Reproduce steps: 1. prepare component devices: dmsetup create cmeta --table \"0 8192 linear /dev/sdc 0\" dmsetup create cdata --table \"0 65536 linear /dev/sdc 8192\" dmsetup create corig --table \"0 524288 linear /dev/sdc 262144\" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct 2. load a cache table of 512 cache blocks, and deliberately expand the fast device before resuming the cache, making the in-core data structures inadequate. dmsetup create cache --notable dmsetup reload cache --table \"0 524288 cache /dev/mapper/cmeta \\ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\" dmsetup reload cdata --table \"0 131072 linear /dev/sdc 8192\" dmsetup resume cdata dmsetup resume cache 3. suspend the cache to write out the in-core dirty bitset and hint array, leading to out-of-bounds access to the dirty bitset at offset 0x40: dmsetup suspend cache KASAN reports: BUG: KASAN: vmalloc-out-of-bounds in is_dirty_callback+0x2b/0x80 Read of size 8 at addr f",
"evidence": "osv:CVE-2024-50278",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.19.324",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.286",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.230",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.172",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.117",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.61",
"evidence": "/affected/1/ranges"
},
{
"value": "6.11.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-50278",
"aliases": [
"CVE-2024-50278"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498"
},
{
"fixed": "e492f71854ce03474d49e87fd98b8df1f7cd1d2d"
},
{
"fixed": "2222b0929d00e2d13732b799b63be391b5de4492"
},
{
"fixed": "483b7261b35a9d369082ab298a6670912243f0be"
},
{
"fixed": "fdef3b94dfebd57e3077a578b6e309a2bb6fa688"
},
{
"fixed": "c52ec00cb2f9bebfada22edcc0db385b910a1cdb"
},
{
"fixed": "036dd6e3d2638103e0092864577ea1d091466b86"
},
{
"fixed": "13ed3624c6ef283acefa4cc42cc8ae54fd4391a4"
},
{
"fixed": "c0ade5d98979585d4f5a93e4514c2e9a65afa08d"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-50278.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.13.0"
},
{
"fixed": "4.19.324"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.286"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.230"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.172"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.117"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.61"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.11.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-50278.json"
}
}
],
"modified": "2026-10-28T02:30:41.343656621Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/036dd6e3d2638103e0092864577ea1d091466b86",
"https://git.kernel.org/stable/c/13ed3624c6ef283acefa4cc42cc8ae54fd4391a4",
"https://git.kernel.org/stable/c/2222b0929d00e2d13732b799b63be391b5de4492",
"https://git.kernel.org/stable/c/483b7261b35a9d369082ab298a6670912243f0be",
"https://git.kernel.org/stable/c/c0ade5d98979585d4f5a93e4514c2e9a65afa08d",
"https://git.kernel.org/stable/c/c52ec00cb2f9bebfada22edcc0db385b910a1cdb",
"https://git.kernel.org/stable/c/e492f71854ce03474d49e87fd98b8df1f7cd1d2d",
"https://git.kernel.org/stable/c/fdef3b94dfebd57e3077a578b6e309a2bb6fa688",
"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50278.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-50278",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50278.json"
}
},
"related_cves": [
{
"value": "CVE-2024-50278",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 508797,
"published_at": "2024-11-19T01:30:19.352+00:00"
}