{"uuid": "aa8d8d54-2a95-4ddc-8575-3c4552da9fa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://t.me/cvedetector/23126", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22124 - Linux Kernel Clustermd Memory Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22124 \nPublished : April 16, 2025, 3:16 p.m. | 23\u00a0minutes ago \nDescription : 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T17:43:51.000000Z"}