CVE-2022-48815
What it is
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() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Starfighter 2 is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.101
- Linux Kernel < 5.15.24
- Linux Kernel < 5.16.10
- Linux Kernel 5.17
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-48815.md and follow it. Check whether this project is affected by CVE-2022-48815. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85cae
- https://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889d
- https://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83
- https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783
- https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85cae
- https://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889d
- https://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83
- https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783
References
- https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85cae
- https://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889d
- https://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83
- https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783
- https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85cae
- https://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889d
- https://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83
- https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783