CVE-2024-45023 (GCVE-0-2024-45023)
Vulnerability from cvelistv5
Published
2024-09-11 15:13
Modified
2026-08-05 11:37
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
md/raid1: Fix data corruption for degraded array with slow disk
read_balance() will avoid reading from slow disks as much as possible,
however, if valid data only lands in slow disks, and a new normal disk
is still in recovery, unrecovered data can be read:
raid1_read_request
read_balance
raid1_should_read_first
-> return false
choose_best_rdev
-> normal disk is not recovered, return -1
choose_bb_rdev
-> missing the checking of recovery, return the normal disk
-> read unrecovered data
Root cause is that the checking of recovery is missing in
choose_bb_rdev(). Hence add such checking to fix the problem.
Also fix similar problem in choose_slow_rdev().
References
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-45023",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-09-29T15:47:27.863341Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-09-29T15:47:42.110Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/md/raid1.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2febf5fdbf5d9a52ddc3e986971c8609b1582d67",
"status": "affected",
"version": "dfa8ecd167c1753d4fc24a517e1d79c603183c94",
"versionType": "git"
},
{
"lessThan": "c916ca35308d3187c9928664f9be249b22a3a701",
"status": "affected",
"version": "dfa8ecd167c1753d4fc24a517e1d79c603183c94",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/md/raid1.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.9"
},
{
"lessThan": "6.9",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.7",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.10.7",
"versionStartIncluding": "6.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.11",
"versionStartIncluding": "6.9",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid1: Fix data corruption for degraded array with slow disk\n\nread_balance() will avoid reading from slow disks as much as possible,\nhowever, if valid data only lands in slow disks, and a new normal disk\nis still in recovery, unrecovered data can be read:\n\nraid1_read_request\n read_balance\n raid1_should_read_first\n -\u003e return false\n choose_best_rdev\n -\u003e normal disk is not recovered, return -1\n choose_bb_rdev\n -\u003e missing the checking of recovery, return the normal disk\n -\u003e read unrecovered data\n\nRoot cause is that the checking of recovery is missing in\nchoose_bb_rdev(). Hence add such checking to fix the problem.\n\nAlso fix similar problem in choose_slow_rdev()."
}
],
"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 vulnerable code is the md/raid1 read path, reached by submitting a READ bio to the local md block device \u2014 via a normal file read on a mounted filesystem or a direct block-device read. No remote protocol input is involved.\nAC:L - There is no race, timing window, or memory-layout dependency; once the array is in the ordinary and frequently occurring degraded-plus-rebuilding state (write-mostly member holding valid data, or surviving member with recorded badblocks), every read in the unrecovered range deterministically selects the wrong disk and returns bad data with repeatable success.\nPR:L - No capability or permission check exists anywhere on the raid1_make_request \u2192 raid1_read_request \u2192 read_balance path; any local unprivileged user reading a file on the filesystem backed by the array triggers the faulty disk selection.\nUI:N - No victim action is required \u2014 the recovery state is driven by the kernel\u0027s background rebuild, and the corrupt reads occur on the attacker\u0027s own I/O as well as on all normal system I/O.\nS:U - The faulty disk selection and its consequences are confined to the md block device and the kernel storage stack, the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - Reads are served from sectors of the replacement member that have not yet been rebuilt, returning that disk\u0027s prior contents \u2014 stale blocks from a re-added or repurposed drive that under the current filesystem layout can belong to other users\u0027 or root-owned files \u2014 so an unprivileged reader obtains data it is not authorized to see.\nI:H - The array silently returns wrong data instead of valid data or an I/O error, and any read-modify-write above md (filesystem metadata, journal, sub-block or database updates) writes that garbage back, after which raid1_write_request() mirrors it to all members and the corruption becomes permanent and unrecoverable.\nA:H - Corrupted metadata delivered to the filesystem drives error handling into forced read-only remount, XFS shutdown, or panic on errors=panic, and the persisted corruption destroys the array\u0027s data \u2014 loss of availability of the storage and potentially of the ability to boot."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T11:37:48.080Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/2febf5fdbf5d9a52ddc3e986971c8609b1582d67"
},
{
"url": "https://git.kernel.org/stable/c/c916ca35308d3187c9928664f9be249b22a3a701"
}
],
"title": "md/raid1: Fix data corruption for degraded array with slow disk",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-45023",
"datePublished": "2024-09-11T15:13:56.451Z",
"dateReserved": "2024-08-21T05:34:56.684Z",
"dateUpdated": "2026-08-05T11:37:48.080Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-45023\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-29T15:47:27.863341Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-29T15:47:31.971Z\"}}], \"cna\": {\"title\": \"md/raid1: Fix data corruption for degraded array with slow disk\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.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\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The vulnerable code is the md/raid1 read path, reached by submitting a READ bio to the local md block device \\u2014 via a normal file read on a mounted filesystem or a direct block-device read. No remote protocol input is involved.\\nAC:L - There is no race, timing window, or memory-layout dependency; once the array is in the ordinary and frequently occurring degraded-plus-rebuilding state (write-mostly member holding valid data, or surviving member with recorded badblocks), every read in the unrecovered range deterministically selects the wrong disk and returns bad data with repeatable success.\\nPR:L - No capability or permission check exists anywhere on the raid1_make_request \\u2192 raid1_read_request \\u2192 read_balance path; any local unprivileged user reading a file on the filesystem backed by the array triggers the faulty disk selection.\\nUI:N - No victim action is required \\u2014 the recovery state is driven by the kernel\u0027s background rebuild, and the corrupt reads occur on the attacker\u0027s own I/O as well as on all normal system I/O.\\nS:U - The faulty disk selection and its consequences are confined to the md block device and the kernel storage stack, the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\\nC:H - Reads are served from sectors of the replacement member that have not yet been rebuilt, returning that disk\u0027s prior contents \\u2014 stale blocks from a re-added or repurposed drive that under the current filesystem layout can belong to other users\u0027 or root-owned files \\u2014 so an unprivileged reader obtains data it is not authorized to see.\\nI:H - The array silently returns wrong data instead of valid data or an I/O error, and any read-modify-write above md (filesystem metadata, journal, sub-block or database updates) writes that garbage back, after which raid1_write_request() mirrors it to all members and the corruption becomes permanent and unrecoverable.\\nA:H - Corrupted metadata delivered to the filesystem drives error handling into forced read-only remount, XFS shutdown, or panic on errors=panic, and the persisted corruption destroys the array\u0027s data \\u2014 loss of availability of the storage and potentially of the ability to boot.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"dfa8ecd167c1753d4fc24a517e1d79c603183c94\", \"lessThan\": \"2febf5fdbf5d9a52ddc3e986971c8609b1582d67\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"dfa8ecd167c1753d4fc24a517e1d79c603183c94\", \"lessThan\": \"c916ca35308d3187c9928664f9be249b22a3a701\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/md/raid1.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.9\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.9\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.10.7\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.10.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/md/raid1.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/2febf5fdbf5d9a52ddc3e986971c8609b1582d67\"}, {\"url\": \"https://git.kernel.org/stable/c/c916ca35308d3187c9928664f9be249b22a3a701\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmd/raid1: Fix data corruption for degraded array with slow disk\\n\\nread_balance() will avoid reading from slow disks as much as possible,\\nhowever, if valid data only lands in slow disks, and a new normal disk\\nis still in recovery, unrecovered data can be read:\\n\\nraid1_read_request\\n read_balance\\n raid1_should_read_first\\n -\u003e return false\\n choose_best_rdev\\n -\u003e normal disk is not recovered, return -1\\n choose_bb_rdev\\n -\u003e missing the checking of recovery, return the normal disk\\n -\u003e read unrecovered data\\n\\nRoot cause is that the checking of recovery is missing in\\nchoose_bb_rdev(). Hence add such checking to fix the problem.\\n\\nAlso fix similar problem in choose_slow_rdev().\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.10.7\", \"versionStartIncluding\": \"6.9\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11\", \"versionStartIncluding\": \"6.9\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:37:48.080Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2024-45023\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T11:37:48.080Z\", \"dateReserved\": \"2024-08-21T05:34:56.684Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-09-11T15:13:56.451Z\", \"assignerShortName\": \"Linux\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…