LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52457: serial: 8250: omap: Don't skip resource freeing if pm_runtime_resume_and_get() failed

In the Linux kernel, the following vulnerability has been resolved: serial: 8250: omap: Don't skip resource freeing if pm_runtime_resume_and_get() failed Returning an error code from .remove() makes the driver core emit the little helpful error message: remove callback returned a non-zero value. This will be ignored. and then remove the device anyhow. So all resources that were not freed are leaked in this case. Skipping serial8250_unregister_port() has the potential to keep enough of the UART around to trigger a use-after-free. So replace the error return (and with it the little helpful error message) by a more useful error message and continue to cleanup.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52457 is a Linux kernel cleanup bug in the OMAP 8250 serial driver. If device removal hits a runtime power-management failure, resources may not be freed correctly, potentially leaving kernel objects behind and creating use-after-free risk. Public sources do not provide CVSS, severity, or active exploitation evidence.

Executive priority

Treat as a targeted kernel maintenance issue, not an emergency internet-wide exposure based on current evidence. Patch through normal kernel update processes, with higher priority for embedded or hardware platforms using the affected serial driver.

Technical view

The flaw is in the Linux serial 8250 OMAP driver remove path. Returning an error after pm_runtime_resume_and_get() failure caused cleanup to be skipped even though the driver core removed the device anyway. The fix logs the failure and continues cleanup, including serial8250_unregister_port().

Likely exposure

Exposure is likely limited to Linux systems using the affected kernel versions and the OMAP 8250 serial driver path. The source bundle does not identify distributions beyond a Debian LTS advisory or confirm broad default exposure.

Exploitation context

No active exploitation is cited, and KEV status is false. The source describes a potential kernel use-after-free condition during device removal, but does not provide exploitability details, prerequisites, or real-world abuse evidence.

Researcher notes

The strongest evidence is the upstream kernel fix rationale: cleanup was skipped after pm_runtime_resume_and_get() failure, while device removal still proceeded. Missing data includes CVSS, CWE mapping, exploit prerequisites, and distribution-specific impact outside cited Debian LTS material.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Review Debian LTS guidance if running affected Debian LTS kernels.
  • Prioritize systems using OMAP 8250 serial hardware or related embedded platforms.
  • Track vendor advisories for exact package and reboot requirements.

Validation and detection

  • Inventory kernel versions against the affected versions listed in the CVE record.
  • Confirm whether the OMAP 8250 serial driver is present and in use.
  • Verify installed kernel changelogs include the referenced stable commit fixes.
  • Check distribution advisories for patched package versions.
Prepared
Confidence
medium
Sources
10

Public sources used

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.

cve · low confidence lookup

CVE-2023-52457 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2d66412563ef8953e2bac2d98d2d832b3f3f49cd, d833cba201adf9237168e19f0d76e4d7aa69f303, e0db709a58bdeb8966890882261a3f8438c5c9b7, e3f0c638f428fd66b5871154b62706772045f91a, e3f0c638f428fd66b5871154b62706772045f91a, e3f0c638f428fd66b5871154b62706772045f91a, e3f0c638f428fd66b5871154b62706772045f91a, 02eed6390dbe61115f3e3f63829c95c611aee67bunaffected
LinuxLinux6.1, 0, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.