dm-integrity: fix buffer overflow in inline mode with large tag size
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix buffer overflow in inline mode with large tag size In inline mode, dm_integrity_check and dm_integrity_inline_recheck compute the checksum of each block into an on-stack buffer of HASH_MAX_DIGESTSIZE bytes. integrity_sector_checksum pads its result with zeroes up to the tag size, so if the tag size is larger than HASH_MAX_DIGESTSIZE, the padding runs past the end of the buffer. With CONFIG_STACKPROTECTOR the kernel panics in dm_integrity_check on the first read. Enlarge both buffers to hold MAX_TAG_SIZE bytes, as commit b93b6643e9b5 ("dm integrity: fix a crash with unusually large tag size") did for integrity_metadata. Note that this is not a security bug because the buffer overflow can only be triggered by root.
- Products
- Linux
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-99098
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 10:28 UTC · Revision 1
Source evidence
dm-integrity: fix buffer overflow in inline mode with large tag size
core-cve · Original sourcePublished 26 Oct 2026, 14:52 UTC
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix buffer overflow in inline mode with large tag size In inline mode, dm_integrity_check and dm_integrity_inline_recheck compute the checksum of each block into an on-stack buffer of HASH_MAX_DIGESTSIZE bytes. integrity_sector_checksum pads its result with zeroes up to the tag size, so if the tag size is larger than HASH_MAX_DIGESTSIZE, the padding runs past the end of the buffer. With CONFIG_STACKPROTECTOR the kernel panics in dm_integrity_check on the first read. Enlarge both buffers to hold MAX_TAG_SIZE bytes, as commit b93b6643e9b5 ("dm integrity: fix a crash with unusually large tag size") did for integrity_metadata. Note that this is not a security bug because the buffer overflow can only be triggered by root.
cve:CVE-2026-99098
Linux
Fixed versions: Not specified
Linux
Fixed versions: Not specified
Complete source record
{
"id": "7027e3cf48b43111bc3aafc83922fa9cec53b00b4769377218ba5675dbd411e2",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-99098",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "dm-integrity: fix buffer overflow in inline mode with large tag size",
"summary": "In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix buffer overflow in inline mode with large tag size In inline mode, dm_integrity_check and dm_integrity_inline_recheck compute the checksum of each block into an on-stack buffer of HASH_MAX_DIGESTSIZE bytes. integrity_sector_checksum pads its result with zeroes up to the tag size, so if the tag size is larger than HASH_MAX_DIGESTSIZE, the padding runs past the end of the buffer. With CONFIG_STACKPROTECTOR the kernel panics in dm_integrity_check on the first read. Enlarge both buffers to hold MAX_TAG_SIZE bytes, as commit b93b6643e9b5 (\"dm integrity: fix a crash with unusually large tag size\") did for integrity_metadata. Note that this is not a security bug because the buffer overflow can only be triggered by root.",
"evidence": "cve:CVE-2026-99098",
"products": [
{
"name": {
"value": "Linux",
"evidence": "/containers/cna/affected/0/product"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
},
{
"name": {
"value": "Linux",
"evidence": "/containers/cna/affected/1/product"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-99098",
"aliases": [
"CVE-2026-99098"
],
"metrics": [],
"affected": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "fb0987682c629c1d2c476f35f6fde405a5e304a4",
"lessThan": "3c7aad85aeb9e28386672e3a009aa2e61f751b86",
"versionType": "git"
},
{
"status": "affected",
"version": "fb0987682c629c1d2c476f35f6fde405a5e304a4",
"lessThan": "4f0ee735dc68e3e6c4dd9a666d7f7047163c4165",
"versionType": "git"
},
{
"status": "affected",
"version": "fb0987682c629c1d2c476f35f6fde405a5e304a4",
"lessThan": "f49cd7820cd0a96f20e1aa2708adb002124e38a7",
"versionType": "git"
},
{
"status": "affected",
"version": "fb0987682c629c1d2c476f35f6fde405a5e304a4",
"lessThan": "764b683a6180fd72c931c13fea98d383506a3475",
"versionType": "git"
}
],
"programFiles": [
"drivers/md/dm-integrity.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.11"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.11",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.12.114",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.57",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.11",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/md/dm-integrity.c"
],
"defaultStatus": "affected"
}
],
"modified": "2026-10-26T14:52:04.416Z",
"provider": "cve",
"references": [
"https://git.kernel.org/stable/c/3c7aad85aeb9e28386672e3a009aa2e61f751b86",
"https://git.kernel.org/stable/c/4f0ee735dc68e3e6c4dd9a666d7f7047163c4165",
"https://git.kernel.org/stable/c/f49cd7820cd0a96f20e1aa2708adb002124e38a7",
"https://git.kernel.org/stable/c/764b683a6180fd72c931c13fea98d383506a3475"
],
"provider_metadata": {
"cna": {
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux",
"dateUpdated": "2026-10-26T14:52:04.416Z"
}
}
},
"related_cves": [
{
"value": "CVE-2026-99098",
"evidence": "/cveMetadata/cveId"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-cve",
"document_id": 311613,
"published_at": "2026-10-26T14:52:04.416+00:00"
}