CVE-2023-53308: net: fec: Better handle pm_runtime_get() failing in .remove()
In the Linux kernel, the following vulnerability has been resolved:
net: fec: Better handle pm_runtime_get() failing in .remove()
In the (unlikely) event that pm_runtime_get() (disguised as
pm_runtime_resume_and_get()) fails, the remove callback returned an
error early. The problem with this is that the driver core ignores the
error value and continues removing the device. This results in a
resource leak. Worse the devm allocated resources are freed and so if a
callback of the driver is called later the register mapping is already
gone which probably results in a crash.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can turn a rare driver removal error into a resource leak and possible crash. It is rated high because a local, low-privileged attacker could potentially affect confidentiality, integrity, and availability on affected systems. No source provided shows active exploitation.
Executive priority
Prioritize remediation where affected Linux kernels run on production or embedded systems using this driver. The risk is high but appears local-only from supplied evidence, so patch through normal kernel maintenance unless exposed systems are safety-critical or shared multi-user hosts.
Technical view
The Linux kernel FEC network driver returned early when pm_runtime_resume_and_get() failed during remove(). The driver core ignores that return value and continues removal, freeing devm-managed resources. Later callbacks may access an already-freed register mapping, causing leakage and likely crashes.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with the FEC driver present. The source lists affected kernel lines including 5.4 through 6.4 and fixed stable commits, but does not identify distributions or device models.
Exploitation context
The CVSS vector is local, low complexity, low privileges, and no user interaction. KEV is false, and the supplied sources do not report public exploitation. Treat this as a local kernel stability and privilege-risk issue, not confirmed internet-exploited activity.
Researcher notes
Evidence is limited to the CVE record and kernel stable references. The root issue is remove-path error handling after pm_runtime_resume_and_get() failure, with driver-core behavior making the early return unsafe. No exploit details or distribution-specific advisories were provided.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check distribution advisories for backported fixes matching your kernel branch.
Prioritize systems where the FEC driver is present or required.
Avoid unsupported kernels that cannot receive the stable fix.
Schedule reboots where kernel replacement is required.
Validation and detection
Inventory kernel versions against the affected and fixed version data.
Confirm whether the running kernel includes the relevant stable commit.
Check whether the FEC driver is built, loaded, or required.
Review logs for crashes around device removal or runtime power management.
Validate fixes first on representative maintenance systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-415: 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.
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.
1CVSS vectors
3Timeline events
1ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.