Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-52457, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS: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 86% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 2d66412563ef8953e2bac2d98d2d832b3f3f49cd – < b502fb43f7fb55aaf07f6092ab44657595214b93
    • affected d833cba201adf9237168e19f0d76e4d7aa69f303 – < bc57f3ef8a9eb0180606696f586a6dcfaa175ed0
    • affected e0db709a58bdeb8966890882261a3f8438c5c9b7 – < 828cd829483f0cda920710997aed79130b0af690
    • affected e3f0c638f428fd66b5871154b62706772045f91a – < d74173bda29aba58f822175d983d07c8ed335494
    • affected e3f0c638f428fd66b5871154b62706772045f91a – < 887a558d0298d36297daea039954c39940228d9b
    • affected e3f0c638f428fd66b5871154b62706772045f91a – < 95e4e0031effad9837af557ecbfd4294a4d8aeee
    • affected e3f0c638f428fd66b5871154b62706772045f91a – < ad90d0358bd3b4554f243a425168fc7cebe7d04e
    • affected 02eed6390dbe61115f3e3f63829c95c611aee67b
    • affected 5.4.225 – < 5.4.268
    • affected 5.10.156 – < 5.10.209
    • affected 5.15.80 – < 5.15.148
    • affected 6.0.10 – < 6.1
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 5.4.268 – ≤ 5.4.*
    • unaffected 5.10.209 – ≤ 5.10.*
    • unaffected 5.15.148 – ≤ 5.15.*
    • unaffected 6.1.75 – ≤ 6.1.*
    • unaffected 6.6.14 – ≤ 6.6.*
    • unaffected 6.7.2 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52457 badge
[![CVE-2023-52457](https://cveledger.app/badge/CVE-2023-52457.svg)](https://cveledger.app/cve/CVE-2023-52457)

Record last updated .