Back
CVE-2022-48754
phylib: fix potential use-after-free
High7.8EPSS 0.23%
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: phylib: fix potential use-after-free Commit bafbdd527d56 ("phylib: Add device reset GPIO support") added call to phy_device_reset(phydev) after the put_device() call in phy_detach(). The comment before the put_device() call says that the phydev might go away with put_device(). Fix potential use-after-free by calling phy_device_reset() before put_device().
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CISA-ADPADP (enrichment) | 3.1 | High8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.23% · top 87% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Weakness
Affected products
- affected bafbdd527d569c8200521f2f7579f65a044271be – < 67d271760b037ce0806d687ee6057edc8afd4205
- affected bafbdd527d569c8200521f2f7579f65a044271be – < f39027cbada43b33566c312e6be3db654ca3ad17
- affected bafbdd527d569c8200521f2f7579f65a044271be – < bd024e36f68174b1793906c39ca16cee0c9295c2
- affected bafbdd527d569c8200521f2f7579f65a044271be – < aefaccd19379d6c4620269a162bfb88ff687f289
- affected bafbdd527d569c8200521f2f7579f65a044271be – < cb2fab10fc5e7a3aa1bb0a68a3abdcf3e37852af
- affected bafbdd527d569c8200521f2f7579f65a044271be – < cbda1b16687580d5beee38273f6241ae3725960c
- affected 4.16
- unaffected < 4.16
- unaffected 4.19.228 – ≤ 4.19.*
- unaffected 5.4.176 – ≤ 5.4.*
- unaffected 5.10.96 – ≤ 5.10.*
- unaffected 5.15.19 – ≤ 5.15.*
- unaffected 5.16.5 – ≤ 5.16.*
- unaffected 5.17 – ≤ *
References (6)
- https://git.kernel.org/stable/c/67d271760b037ce0806d687ee6057edc8afd4205 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/f39027cbada43b33566c312e6be3db654ca3ad17 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/bd024e36f68174b1793906c39ca16cee0c9295c2 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/aefaccd19379d6c4620269a162bfb88ff687f289 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/cb2fab10fc5e7a3aa1bb0a68a3abdcf3e37852af (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/cbda1b16687580d5beee38273f6241ae3725960c (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-48754)Record last updated .