{"uuid": "0b924a4f-b0e9-42d8-927a-cefa50cbf625", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22124", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14803", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22124\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2025-04-16T14:13:08.134Z\n\ud83d\udccf Modified: 2025-05-04T13:07:04.537Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/bc3a9788961631359527763d7e1fcf26554c7cb1\n2. https://git.kernel.org/stable/c/6130825f34d41718c98a9b1504a79a23e379701e", "creation_timestamp": "2025-05-04T13:18:46.000000Z"}