https://vulnerability.circl.lu/sightings/feed 2026-05-06T00:43:45.009840+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/3a5cad47-c720-42fb-936e-d04ae9d82304/export 2026-05-06T00:43:45.427193+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "3a5cad47-c720-42fb-936e-d04ae9d82304", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46846", "type": "seen", "source": "https://t.me/cvedetector/6527", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46846 - Rockchip spi unbalanced Power Management\", \n \"Content\": \"CVE ID : CVE-2024-46846 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nspi: rockchip: Resolve unbalanced runtime PM / system PM handling \n \nCommit e882575efc77 (\"spi: rockchip: Suspend and resume the bus during \nNOIRQ_SYSTEM_SLEEP_PM ops\") stopped respecting runtime PM status and \nsimply disabled clocks unconditionally when suspending the system. This \ncauses problems when the device is already runtime suspended when we go \nto sleep -- in which case we double-disable clocks and produce a \nWARNing. \n \nSwitch back to pm_runtime_force_{suspend,resume}(), because that still \nseems like the right thing to do, and the aforementioned commit makes no \nexplanation why it stopped using it. \n \nAlso, refactor some of the resume() error handling, because it's not \nactually a good idea to re-disable clocks on failure. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:35.000000Z"} 2024-09-27T15:53:35+00:00