https://vulnerability.circl.lu/sightings/feed 2026-05-09T23:44:17.144047+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/80fee1e1-a2c5-4917-8857-d17daf278c28/export 2026-05-09T23:44:17.509165+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "80fee1e1-a2c5-4917-8857-d17daf278c28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45023", "type": "seen", "source": "https://t.me/cvedetector/5370", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45023 - Linux Kernel Md Raid Data Corruption Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45023 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : 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 -> return false \n choose_best_rdev \n -> normal disk is not recovered, return -1 \n choose_bb_rdev \n -> missing the checking of recovery, return the normal disk \n -> 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(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:22.000000Z"} 2024-09-11T18:41:22+00:00