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-52619pstore/ram: Fix crash when setting number of cpus to an odd number

Description

In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Fix crash when setting number of cpus to an odd number When the number of cpu cores is adjusted to 7 or other odd numbers, the zone size will become an odd number. The address of the zone will become: addr of zone0 = BASE addr of zone1 = BASE + zone_size addr of zone2 = BASE + zone_size*2 ... The address of zone1/3/5/7 will be mapped to non-alignment va. Eventually crashes will occur when accessing these va. So, use ALIGN_DOWN() to make sure the zone size is even to avoid this bug.

Timeline

  1. ID reserved

    By Linux

  2. · 12 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-52619, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 84% of all CVEs (16 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected de83209249d64bad993f25d3ea4bba57683e2e2e – < 8b69c30f4e8b69131d92096cb296dc1f217101e4
    • affected de83209249d64bad993f25d3ea4bba57683e2e2e – < e9f6ac50890104fdf8194f2865680689239d30fb
    • affected de83209249d64bad993f25d3ea4bba57683e2e2e – < a63e48cd835c34c38ef671d344cc029b1ea5bf10
    • affected de83209249d64bad993f25d3ea4bba57683e2e2e – < 2a37905d47bffec61e95d99f0c1cc5dc6377956c
    • affected de83209249d64bad993f25d3ea4bba57683e2e2e – < 75b0f71b26b3ad833c5c0670109c0af6e021e86a
    • affected de83209249d64bad993f25d3ea4bba57683e2e2e – < 0593cfd321df9001142a9d2c58d4144917dff7ee
    • affected de83209249d64bad993f25d3ea4bba57683e2e2e – < cd40e43f870cf21726b22487a95ed223790b3542
    • affected de83209249d64bad993f25d3ea4bba57683e2e2e – < d49270a04623ce3c0afddbf3e984cb245aa48e9c
  • Linux · Linux

    • affected 4.10
    • unaffected < 4.10
    • unaffected 4.19.307 – ≤ 4.19.*
    • unaffected 5.4.269 – ≤ 5.4.*
    • unaffected 5.10.210 – ≤ 5.10.*
    • unaffected 5.15.149 – ≤ 5.15.*
    • unaffected 6.1.77 – ≤ 6.1.*
    • unaffected 6.6.16 – ≤ 6.6.*
    • unaffected 6.7.4 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .