CVE-2022-48815
published 2024-07-16CVE-2022-48815: In the Linux kernel, the following vulnerability has been resolved: net: dsa: bcm_sf2: don't use devres for mdiobus As explained in commits: 74b6d7d13307…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.27%
18.8th percentile
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: bcm_sf2: don't use devres for mdiobus
As explained in commits:
74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
mdiobus_free() will panic when called from devm_mdiobus_free() remove on ->shutdown) do not apply. But there is one more which
applies here.
If the DSA master itself is on a bus that calls ->remove from ->shutdown
(like dpaa2-eth, which is on the fsl-mc bus), there is a device link
between the switch and the DSA master, and device_links_unbind_consumers()
will unbind the bcm_sf2 switch driver on shutdown.
So the same treatment must be applied to all DSA switch drivers, which
is: either use devres for both the mdiobus allocation and registration,
or don't use devres at all.
The bcm_sf2 driver has the code structure in place for orderly mdiobus
removal, so just replace devm_mdiobus_alloc() with the non-devres
variant, and add manual free where necessary, to ensure that we don't
let devres free a still-registered bus.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.10-1 (bookworm) | linux 5.16.10-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= ac3a68d56651c3dad2c12c7afce065fe15267f44 < 2770b795294ed312375c11ef1d0b810499c66b83 | 2770b795294ed312375c11ef1d0b810499c66b83 |
| linux | linux | >= ac3a68d56651c3dad2c12c7afce065fe15267f44 < caabb5f64f5c32fceed93356bb688ef1ec6c5783 | caabb5f64f5c32fceed93356bb688ef1ec6c5783 |
| linux | linux | >= ac3a68d56651c3dad2c12c7afce065fe15267f44 < 08e1a3554e99a1a5bd2835907381e2383ee85cae | 08e1a3554e99a1a5bd2835907381e2383ee85cae |
| linux | linux | >= ac3a68d56651c3dad2c12c7afce065fe15267f44 < 08f1a20822349004bb9cc1b153ecb516e9f2889d | 08f1a20822349004bb9cc1b153ecb516e9f2889d |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.103-1 | 5.10.103-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 5.11 < 5.15.24 | 5.15.24 |
| linux | linux_kernel | >= 5.16 < 5.16.10 | 5.16.10 |
| linux | linux_kernel | >= 5.9 < 5.10.101 | 5.10.101 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: net: dsa: bcm_sf2: don't use devres for mdiobus
vendor_redhat·2024-07-16·CVSS 5.5
CVE-2022-48815 [MEDIUM] CWE-99 kernel: net: dsa: bcm_sf2: don't use devres for mdiobus
kernel: net: dsa: bcm_sf2: don't use devres for mdiobus
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: bcm_sf2: don't use devres for mdiobus
As explained in commits:
74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
mdiobus_free() will panic when called from devm_mdiobus_free() remove on ->shutdown) do not apply. But there is one more which
applies here.
If the DSA master itself is on a bus that calls ->remove from ->shutdown
(like dpaa2-eth, which is on the fsl-mc bus), there is a device link
between the switch and the DSA master, and device_links_unbind_consumers()
will unbind the bcm_sf2 switch driver on shutdown.
So the same treatment must be applied to all DSA
Debian
CVE-2022-48815: linux - In the Linux kernel, the following vulnerability has been resolved: net: dsa: b...
vendor_debian·2022·CVSS 5.5
CVE-2022-48815 [MEDIUM] CVE-2022-48815: linux - In the Linux kernel, the following vulnerability has been resolved: net: dsa: b...
In the Linux kernel, the following vulnerability has been resolved: net: dsa: bcm_sf2: don't use devres for mdiobus As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the bcm_sf2 switch driver on shutdown. So the same treatment must be applied to all DSA switch drivers, which is: either use devres for both the
GHSA
GHSA-h976-8v6c-8j56: In the Linux kernel, the following vulnerability has been resolved:
net: dsa: bcm_sf2: don't use devres for mdiobus
As explained in commits:
74b6d7d
ghsa_unreviewed·2024-07-16
CVE-2022-48815 [MEDIUM] GHSA-h976-8v6c-8j56: In the Linux kernel, the following vulnerability has been resolved:
net: dsa: bcm_sf2: don't use devres for mdiobus
As explained in commits:
74b6d7d
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: bcm_sf2: don't use devres for mdiobus
As explained in commits:
74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
mdiobus_free() will panic when called from devm_mdiobus_free() remove on ->shutdown) do not apply. But there is one more which
applies here.
If the DSA master itself is on a bus that calls ->remove from ->shutdown
(like dpaa2-eth, which is on the fsl-mc bus), there is a device link
between the switch and the DSA master, and device_links_unbind_consumers()
will unbind the bcm_sf2 switch driver on shutdown.
So the same treatment must be applied to all DSA switch drivers, which
is: either use devres for both
OSV
CVE-2022-48815: In the Linux kernel, the following vulnerability has been resolved: net: dsa: bcm_sf2: don't use devres for mdiobus As explained in commits: 74b6d7d13
osv·2024-07-16·CVSS 5.5
CVE-2022-48815 [MEDIUM] CVE-2022-48815: In the Linux kernel, the following vulnerability has been resolved: net: dsa: bcm_sf2: don't use devres for mdiobus As explained in commits: 74b6d7d13
In the Linux kernel, the following vulnerability has been resolved: net: dsa: bcm_sf2: don't use devres for mdiobus As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the bcm_sf2 switch driver on shutdown. So the same treatment must be applied to all DSA switch drivers, which is: either use devres for both the
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85caehttps://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889dhttps://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85caehttps://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889dhttps://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783
2024-07-16
Published