https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Fri, 29 May 2026 23:07:12 +0000 https://vulnerability.circl.lu/sighting/aa8d8d54-2a95-4ddc-8575-3c4552da9fa9/export {"uuid": "aa8d8d54-2a95-4ddc-8575-3c4552da9fa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"} {"uuid": "aa8d8d54-2a95-4ddc-8575-3c4552da9fa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"} https://vulnerability.circl.lu/sighting/aa8d8d54-2a95-4ddc-8575-3c4552da9fa9/export Wed, 16 Apr 2025 17:43:51 +0000 https://vulnerability.circl.lu/sighting/0b924a4f-b0e9-42d8-927a-cefa50cbf625/export {"uuid": "0b924a4f-b0e9-42d8-927a-cefa50cbf625", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"} {"uuid": "0b924a4f-b0e9-42d8-927a-cefa50cbf625", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"} https://vulnerability.circl.lu/sighting/0b924a4f-b0e9-42d8-927a-cefa50cbf625/export Sun, 04 May 2025 13:18:46 +0000 https://vulnerability.circl.lu/sighting/f2871095-a5c6-4620-a01a-590b58e730fa/export {"uuid": "f2871095-a5c6-4620-a01a-590b58e730fa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "f2871095-a5c6-4620-a01a-590b58e730fa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://vulnerability.circl.lu/sighting/f2871095-a5c6-4620-a01a-590b58e730fa/export Thu, 19 Mar 2026 00:00:00 +0000 https://vulnerability.circl.lu/sighting/72099ee1-2186-4a6a-a8bd-e22b68400b28/export {"uuid": "72099ee1-2186-4a6a-a8bd-e22b68400b28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0397/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"} {"uuid": "72099ee1-2186-4a6a-a8bd-e22b68400b28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0397/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"} https://vulnerability.circl.lu/sighting/72099ee1-2186-4a6a-a8bd-e22b68400b28/export Thu, 02 Apr 2026 17:00:00 +0000 https://vulnerability.circl.lu/sighting/2815e12e-b996-4d19-86d8-324b1d039926/export {"uuid": "2815e12e-b996-4d19-86d8-324b1d039926", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260408", "content": "", "creation_timestamp": "2026-04-07T18:00:00.000000Z"} {"uuid": "2815e12e-b996-4d19-86d8-324b1d039926", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260408", "content": "", "creation_timestamp": "2026-04-07T18:00:00.000000Z"} https://vulnerability.circl.lu/sighting/2815e12e-b996-4d19-86d8-324b1d039926/export Tue, 07 Apr 2026 18:00:00 +0000 https://vulnerability.circl.lu/sighting/13a6a5d9-5f63-46ac-bbc1-b631180b7823/export {"uuid": "13a6a5d9-5f63-46ac-bbc1-b631180b7823", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260511", "content": "", "creation_timestamp": "2026-05-10T18:00:00.000000Z"} {"uuid": "13a6a5d9-5f63-46ac-bbc1-b631180b7823", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-22124", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260511", "content": "", "creation_timestamp": "2026-05-10T18:00:00.000000Z"} https://vulnerability.circl.lu/sighting/13a6a5d9-5f63-46ac-bbc1-b631180b7823/export Sun, 10 May 2026 18:00:00 +0000