Security readout for executives and security teams
Plain-English summary
CVE-2022-48754 is a Linux kernel flaw in phylib, the library used by some network PHY drivers. A device object could be released before reset handling finished, creating a potential use-after-free. The CVSS score is high, but the supplied evidence describes local attack conditions, not remote exploitation.
Executive priority
Treat this as a high-priority kernel maintenance item, especially for Linux infrastructure and embedded or network-facing appliances. There is no supplied evidence of active exploitation, but kernel memory-safety flaws can carry severe impact and should not wait for routine patch cycles.
Technical view
The issue is CWE-416 in Linux kernel phylib. In phy_detach(), phy_device_reset() was called after put_device(), even though put_device() might free phydev. Stable fixes reorder the logic so reset occurs before the reference is dropped. The affected data names Linux kernel versions/ranges and the introducing commit bafbdd527d56.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel builds with phylib and PHY reset GPIO support. The bundle does not map exposure to specific distributions or appliances, so kernel package backports and vendor advisories must be checked before declaring a system affected.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit use. CVSS lists local access, low complexity, no privileges, and no user interaction, with high confidentiality, integrity, and availability impact if successfully exploited.
Researcher notes
The useful validation question is not only kernel version, but whether the vendor tree contains the reordered phy_detach() fix. The supplied affected data is version-oriented and commit-oriented, so distro backport analysis is necessary. No exploit mechanics are provided in the sources.
Mitigation direction
- Update to a vendor-supported kernel containing the relevant stable phylib fix.
- Check distribution advisories for backported fixes under CVE-2022-48754.
- Prioritize Linux hosts or appliances using affected network PHY drivers.
- Review kernel vendor guidance before applying compensating controls.
Validation and detection
- Inventory Linux kernel versions and package build identifiers across managed systems.
- Confirm whether vendor kernels include one of the referenced stable commits.
- Identify systems using phylib-dependent network hardware or reset GPIO paths.
- Review kernel logs for unexplained network driver crashes or detach failures.
Public sources used
- CVE Program
- CVE List V5
- Linux stable commit 67d271760b037ce0806d687ee6057edc8afd4205
- Linux stable commit f39027cbada43b33566c312e6be3db654ca3ad17
- Linux stable commit bd024e36f68174b1793906c39ca16cee0c9295c2
- Linux stable commit aefaccd19379d6c4620269a162bfb88ff687f289
- Linux stable commit cb2fab10fc5e7a3aa1bb0a68a3abdcf3e37852af
- Linux stable commit cbda1b16687580d5beee38273f6241ae3725960c
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-48754 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/67d271760b037ce0806d687ee6057edc8afd4205CVE reference, Linux
- https://git.kernel.org/stable/c/f39027cbada43b33566c312e6be3db654ca3ad17CVE reference, Linux
- https://git.kernel.org/stable/c/bd024e36f68174b1793906c39ca16cee0c9295c2CVE reference, Linux
- https://git.kernel.org/stable/c/aefaccd19379d6c4620269a162bfb88ff687f289CVE reference, Linux
- https://git.kernel.org/stable/c/cb2fab10fc5e7a3aa1bb0a68a3abdcf3e37852afCVE reference, Linux
- https://git.kernel.org/stable/c/cbda1b16687580d5beee38273f6241ae3725960cCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.