https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sun, 10 May 2026 22:07:20 +0000 https://vulnerability.circl.lu/sighting/0d50cdd4-2ec0-4f0c-b071-48d0c0086c13/export {"uuid": "0d50cdd4-2ec0-4f0c-b071-48d0c0086c13", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48815", "type": "seen", "source": "https://t.me/cvedetector/943", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48815 - Linux Kernel bcm_sf2 MDIobus Vulnerability (Buffer Pointer Corruption)\", \n \"Content\": \"CVE ID : CVE-2022-48815 \nPublished : July 16, 2024, 12:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet: dsa: bcm_sf2: don't use devres for mdiobus \n \nAs explained in commits: \n74b6d7d13307 (\"net: dsa: realtek: register the MDIO bus under devres\") \n5135e96a3dd2 (\"net: dsa: don't allocate the slave_mii_bus using devres\") \n \nmdiobus_free() will panic when called from devm_mdiobus_free() remove on ->shutdown) do not apply. But there is one more which \napplies here. \n \nIf the DSA master itself is on a bus that calls ->remove from ->shutdown \n(like dpaa2-eth, which is on the fsl-mc bus), there is a device link \nbetween the switch and the DSA master, and device_links_unbind_consumers() \nwill unbind the bcm_sf2 switch driver on shutdown. \n \nSo the same treatment must be applied to all DSA switch drivers, which \nis: either use devres for both the mdiobus allocation and registration, \nor don't use devres at all. \n \nThe bcm_sf2 driver has the code structure in place for orderly mdiobus \nremoval, so just replace devm_mdiobus_alloc() with the non-devres \nvariant, and add manual free where necessary, to ensure that we don't \nlet devres free a still-registered bus. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Jul 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-16T15:26:29.000000Z"} {"uuid": "0d50cdd4-2ec0-4f0c-b071-48d0c0086c13", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48815", "type": "seen", "source": "https://t.me/cvedetector/943", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48815 - Linux Kernel bcm_sf2 MDIobus Vulnerability (Buffer Pointer Corruption)\", \n \"Content\": \"CVE ID : CVE-2022-48815 \nPublished : July 16, 2024, 12:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet: dsa: bcm_sf2: don't use devres for mdiobus \n \nAs explained in commits: \n74b6d7d13307 (\"net: dsa: realtek: register the MDIO bus under devres\") \n5135e96a3dd2 (\"net: dsa: don't allocate the slave_mii_bus using devres\") \n \nmdiobus_free() will panic when called from devm_mdiobus_free() remove on ->shutdown) do not apply. But there is one more which \napplies here. \n \nIf the DSA master itself is on a bus that calls ->remove from ->shutdown \n(like dpaa2-eth, which is on the fsl-mc bus), there is a device link \nbetween the switch and the DSA master, and device_links_unbind_consumers() \nwill unbind the bcm_sf2 switch driver on shutdown. \n \nSo the same treatment must be applied to all DSA switch drivers, which \nis: either use devres for both the mdiobus allocation and registration, \nor don't use devres at all. \n \nThe bcm_sf2 driver has the code structure in place for orderly mdiobus \nremoval, so just replace devm_mdiobus_alloc() with the non-devres \nvariant, and add manual free where necessary, to ensure that we don't \nlet devres free a still-registered bus. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Jul 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-16T15:26:29.000000Z"} https://vulnerability.circl.lu/sighting/0d50cdd4-2ec0-4f0c-b071-48d0c0086c13/export Tue, 16 Jul 2024 15:26:29 +0000