CVE-2025-22124

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2025-22124", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2024-12-29T08:45:45.823Z", "datePublished": "2025-04-16T14:13:08.134Z", "dateUpdated": "2026-10-15T21:51:58.133Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-09-14T11:57:56.837Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/md-bitmap: fix wrong bitmap_limit for clustermd when write sb\n\nIn clustermd, separate write-intent-bitmaps are used for each cluster\nnode:\n\n0 4k 8k 12k\n-------------------------------------------------------------------\n| idle | md super | bm super [0] + bits |\n| bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] |\n| bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits |\n| bm bits [3, contd] | | |\n\nSo in node 1, pg_index in __write_sb_page() could equal to\nbitmap->storage.file_pages. Then bitmap_limit will be calculated to\n0. md_super_write() will be called with 0 size.\nThat means the first 4k sb area of node 1 will never be updated\nthrough filemap_write_page().\nThis bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.\n\nHere use (pg_index % bitmap->storage.file_pages) to make calculation\nof bitmap_limit correct."}], "metrics": [{"cvssV3_1": {"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"}, "scenarios": [{"lang": "en", "value": "AV:L - The vulnerable code is in the md bitmap writeback path of a local block device stack, reached via I/O to a clustered md array on the local system. No remote attacker input reaches `__write_sb_page()` directly.\nAC:L - On a clustered md array the miscalculation is deterministic for every node with cluster_slot >= 1 \u2014 no race, no memory-layout dependency, and it fires on every bitmap superblock/page writeback driven by ordinary I/O.\nPR:L - The buggy path carries no capability check; an unprivileged local user writing to a filesystem backed by the clustered md array dirties bitmap pages and triggers the writeback. Array configuration is a deployment precondition, not a privilege the attacker must hold.\nUI:N - No victim action is needed \u2014 the flawed write occurs automatically during normal bitmap superblock updates and daemon writeback.\nS:U - The out-of-bounds read, on-disk metadata corruption, and hang all stay within the kernel's own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - With the clamp defeated by the unsigned underflow, up to `bdev_io_opt()` bytes (commonly 256KB) are read from a single bitmap page, leaking ~252KB of adjacent kernel memory into the RAID member's on-disk metadata area \u2014 and over the network for nvme-tcp backing devices \u2014 where it is recoverable by anyone able to read the raw device.\nI:H - The oversized write overruns the node's own bitmap slot and overwrites neighbouring cluster nodes' on-disk write-intent bitmaps with arbitrary kernel memory, while the zero-length-write variant leaves the bitmap superblock permanently stale so post-crash resync skips genuinely dirty regions, silently diverging the mirrors.\nA:H - The commit documents a hang of the cluster grow/resize path, the original bug this regresses caused `mdadm` to hang on nvme-tcp via `sendpage_ok()` failure, and the out-of-bounds page walk can touch unmapped memory and oops."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/md/md-bitmap.c"], "versions": [{"version": "655cc01889fa9b65441922565cddee64af49e6d6", "lessThan": "5eaf57fdfa37c869e61e9908e03edd707f9145b8", "status": "affected", "versionType": "git"}, {"version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "lessThan": "60196f92bbc7901eb5cfa5d456651b87ea50a4a3", "status": "affected", "versionType": "git"}, {"version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "lessThan": "bc3a9788961631359527763d7e1fcf26554c7cb1", "status": "affected", "versionType": "git"}, {"version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "lessThan": "6130825f34d41718c98a9b1504a79a23e379701e", "status": "affected", "versionType": "git"}, {"version": "5600d6013c634c2b6b6c6c55c8ecb50c3a6211f2", "status": "affected", "versionType": "git"}, {"version": "6.6.44", "lessThan": "6.6.157", "status": "affected", "versionType": "semver"}, {"version": "6.10.3", "lessThan": "6.11", "status": "affected", "versionType": "semver"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/md/md-bitmap.c"], "versions": [{"version": "6.11", "status": "affected"}, {"version": "0", "lessThan": "6.11", "status": "unaffected", "versionType": "semver"}, {"version": "6.6.157", "lessThanOrEqual": "6.6.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.12.46", "lessThanOrEqual": "6.12.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.14.2", "lessThanOrEqual": "6.14.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.15", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.6.44", "versionEndExcluding": "6.6.157"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.11", "versionEndExcluding": "6.12.46"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.11", "versionEndExcluding": "6.14.2"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.11", "versionEndExcluding": "6.15"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.10.3"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/5eaf57fdfa37c869e61e9908e03edd707f9145b8"}, {"url": "https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3"}, {"url": "https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1"}, {"url": "https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e"}], "title": "md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb", "x_generator": {"engine": "bippy-1.2.0"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2025-22124", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-10-15T21:44:34.243767Z"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-15T21:51:58.133Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2025-22124", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-10-15T21:44:34.243767Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-15T21:44:35.085Z"}}], "cna": {"title": "md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb", "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 in the md bitmap writeback path of a local block device stack, reached via I/O to a clustered md array on the local system. No remote attacker input reaches `__write_sb_page()` directly.\nAC:L - On a clustered md array the miscalculation is deterministic for every node with cluster_slot >= 1 \u2014 no race, no memory-layout dependency, and it fires on every bitmap superblock/page writeback driven by ordinary I/O.\nPR:L - The buggy path carries no capability check; an unprivileged local user writing to a filesystem backed by the clustered md array dirties bitmap pages and triggers the writeback. Array configuration is a deployment precondition, not a privilege the attacker must hold.\nUI:N - No victim action is needed \u2014 the flawed write occurs automatically during normal bitmap superblock updates and daemon writeback.\nS:U - The out-of-bounds read, on-disk metadata corruption, and hang all stay within the kernel's own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - With the clamp defeated by the unsigned underflow, up to `bdev_io_opt()` bytes (commonly 256KB) are read from a single bitmap page, leaking ~252KB of adjacent kernel memory into the RAID member's on-disk metadata area \u2014 and over the network for nvme-tcp backing devices \u2014 where it is recoverable by anyone able to read the raw device.\nI:H - The oversized write overruns the node's own bitmap slot and overwrites neighbouring cluster nodes' on-disk write-intent bitmaps with arbitrary kernel memory, while the zero-length-write variant leaves the bitmap superblock permanently stale so post-crash resync skips genuinely dirty regions, silently diverging the mirrors.\nA:H - The commit documents a hang of the cluster grow/resize path, the original bug this regresses caused `mdadm` to hang on nvme-tcp via `sendpage_ok()` failure, and the out-of-bounds page walk can touch unmapped memory and oops."}]}], "affected": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "655cc01889fa9b65441922565cddee64af49e6d6", "lessThan": "5eaf57fdfa37c869e61e9908e03edd707f9145b8", "versionType": "git"}, {"status": "affected", "version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "lessThan": "60196f92bbc7901eb5cfa5d456651b87ea50a4a3", "versionType": "git"}, {"status": "affected", "version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "lessThan": "bc3a9788961631359527763d7e1fcf26554c7cb1", "versionType": "git"}, {"status": "affected", "version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "lessThan": "6130825f34d41718c98a9b1504a79a23e379701e", "versionType": "git"}, {"status": "affected", "version": "5600d6013c634c2b6b6c6c55c8ecb50c3a6211f2", "versionType": "git"}, {"status": "affected", "version": "6.6.44", "lessThan": "6.6.157", "versionType": "semver"}, {"status": "affected", "version": "6.10.3", "lessThan": "6.11", "versionType": "semver"}], "programFiles": ["drivers/md/md-bitmap.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.6.157", "versionType": "semver", "lessThanOrEqual": "6.6.*"}, {"status": "unaffected", "version": "6.12.46", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.14.2", "versionType": "semver", "lessThanOrEqual": "6.14.*"}, {"status": "unaffected", "version": "6.15", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/md/md-bitmap.c"], "defaultStatus": "affected"}], "references": [{"url": "https://git.kernel.org/stable/c/5eaf57fdfa37c869e61e9908e03edd707f9145b8"}, {"url": "https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3"}, {"url": "https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1"}, {"url": "https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e"}], "x_generator": {"engine": "bippy-1.2.0"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/md-bitmap: fix wrong bitmap_limit for clustermd when write sb\n\nIn clustermd, separate write-intent-bitmaps are used for each cluster\nnode:\n\n0 4k 8k 12k\n-------------------------------------------------------------------\n| idle | md super | bm super [0] + bits |\n| bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] |\n| bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits |\n| bm bits [3, contd] | | |\n\nSo in node 1, pg_index in __write_sb_page() could equal to\nbitmap->storage.file_pages. Then bitmap_limit will be calculated to\n0. md_super_write() will be called with 0 size.\nThat means the first 4k sb area of node 1 will never be updated\nthrough filemap_write_page().\nThis bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.\n\nHere use (pg_index % bitmap->storage.file_pages) to make calculation\nof bitmap_limit correct."}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.6.157", "versionStartIncluding": "6.6.44"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.12.46", "versionStartIncluding": "6.11"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.14.2", "versionStartIncluding": "6.11"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.15", "versionStartIncluding": "6.11"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionStartIncluding": "6.10.3"}], "operator": "OR"}]}], "providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-09-14T11:57:56.837Z"}}}, "cveMetadata": {"cveId": "CVE-2025-22124", "state": "PUBLISHED", "dateUpdated": "2026-10-15T21:51:58.133Z", "dateReserved": "2024-12-29T08:45:45.823Z", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "datePublished": "2025-04-16T14:13:08.134Z", "assignerShortName": "Linux"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["drivers/md/md-bitmap.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "5eaf57fdfa37c869e61e9908e03edd707f9145b8", "status": "affected", "version": "655cc01889fa9b65441922565cddee64af49e6d6", "versionType": "git"}, {"lessThan": "60196f92bbc7901eb5cfa5d456651b87ea50a4a3", "status": "affected", "version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "versionType": "git"}, {"lessThan": "bc3a9788961631359527763d7e1fcf26554c7cb1", "status": "affected", "version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "versionType": "git"}, {"lessThan": "6130825f34d41718c98a9b1504a79a23e379701e", "status": "affected", "version": "ab99a87542f194f28e2364a42afbf9fb48b1c724", "versionType": "git"}, {"status": "affected", "version": "5600d6013c634c2b6b6c6c55c8ecb50c3a6211f2", "versionType": "git"}, {"lessThan": "6.6.157", "status": "affected", "version": "6.6.44", "versionType": "semver"}, {"lessThan": "6.11", "status": "affected", "version": "6.10.3", "versionType": "semver"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["drivers/md/md-bitmap.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "6.11"}, {"lessThan": "6.11", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "6.6.*", "status": "unaffected", "version": "6.6.157", "versionType": "semver"}, {"lessThanOrEqual": "6.12.*", "status": "unaffected", "version": "6.12.46", "versionType": "semver"}, {"lessThanOrEqual": "6.14.*", "status": "unaffected", "version": "6.14.2", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "6.15", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "7D3276FE-8702-415A-8C4D-382A8F3F8D3A", "versionEndExcluding": "6.7", "versionStartIncluding": "6.6.44", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "EEBB6B04-47A8-4B7D-BC19-E09F6715D820", "versionEndExcluding": "6.12.46", "versionStartIncluding": "6.10.3", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "633A38C1-75C8-452D-8F1C-DA0269FD2687", "versionEndExcluding": "6.14.2", "versionStartIncluding": "6.13", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/md-bitmap: fix wrong bitmap_limit for clustermd when write sb\n\nIn clustermd, separate write-intent-bitmaps are used for each cluster\nnode:\n\n0 4k 8k 12k\n-------------------------------------------------------------------\n| idle | md super | bm super [0] + bits |\n| bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] |\n| bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits |\n| bm bits [3, contd] | | |\n\nSo in node 1, pg_index in __write_sb_page() could equal to\nbitmap->storage.file_pages. Then bitmap_limit will be calculated to\n0. md_super_write() will be called with 0 size.\nThat means the first 4k sb area of node 1 will never be updated\nthrough filemap_write_page().\nThis bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.\n\nHere use (pg_index % bitmap->storage.file_pages) to make calculation\nof bitmap_limit correct."}, {"lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: md/md-bitmap: corrige bitmap_limit incorrecto para clustermd al escribir sb En clustermd, se usan mapas de bits de intenci\u00f3n de escritura separados para cada nodo del cl\u00faster: 0 4k 8k 12k ------------------------------------------------------------------- | idle | md super | bm super [0] + bits | | bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] | | bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits | | bm bits [3, contd] | | | Entonces, en el nodo 1, pg_index en __write_sb_page() podr\u00eda ser igual a bitmap->storage.file_pages. Entonces, bitmap_limit se calcular\u00e1 como 0. md_super_write() se llamar\u00e1 con un tama\u00f1o de 0. Esto significa que la primera \u00e1rea de 4k del nodo 1 nunca se actualizar\u00e1 mediante filemap_write_page(). Este error provoca el bloqueo de mdadm/clustermd_tests/01r1_Grow_resize. En este caso, utilice (pg_index % bitmap->storage.file_pages) para que el c\u00e1lculo de bitmap_limit sea correcto."}], "id": "CVE-2025-22124", "lastModified": "2026-10-15T22:18:15.483", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 7.8, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 5.9, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 5.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-22124", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-10-15T21:44:34.243767Z", "version": "2.0.3"}}]}, "published": "2025-04-16T15:16:06.540", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/5eaf57fdfa37c869e61e9908e03edd707f9145b8"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/60196f92bbc7901eb5cfa5d456651b87ea50a4a3"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "NVD-CWE-noinfo"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{"bugzilla": {"description": "kernel: md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb", "id": "2360235", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2360235"}, "csaw": false, "cvss3": {"cvss3_base_score": "6.0", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H", "status": "draft"}, "cwe": "CWE-131", "details": ["In the Linux kernel, the following vulnerability has been resolved:\nmd/md-bitmap: fix wrong bitmap_limit for clustermd when write sb\nIn clustermd, separate write-intent-bitmaps are used for each cluster\nnode:\n0 4k 8k 12k\n-------------------------------------------------------------------\n| idle | md super | bm super [0] + bits |\n| bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] |\n| bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits |\n| bm bits [3, contd] | | |\nSo in node 1, pg_index in __write_sb_page() could equal to\nbitmap->storage.file_pages. Then bitmap_limit will be calculated to\n0. md_super_write() will be called with 0 size.\nThat means the first 4k sb area of node 1 will never be updated\nthrough filemap_write_page().\nThis bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.\nHere use (pg_index % bitmap->storage.file_pages) to make calculation\nof bitmap_limit correct."], "name": "CVE-2025-22124", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Out of support scope", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Out of support scope", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Out of support scope", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Out of support scope", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2025-04-16T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2025-22124\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-22124\nhttps://lore.kernel.org/linux-cve-announce/2025041629-CVE-2025-22124-4561@gregkh/T"], "threat_severity": "Moderate"}

{}