CVE-2023-53699

UNRATEDCVSS · not yet scored

Also known asEUVD-2023-60029 (ENISA EUVD) · GHSA-q328-fmmj-x9cj (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

riscv: move memblock_allow_resize() after linear mapping is ready

The initial memblock metadata is accessed from kernel image mapping. The regions arrays need to "reallocated" from memblock and accessed through linear mapping to cover more memblock regions. So the resizing should not be allowed until linear mapping is ready. Note that there are memblock allocations when building linear mapping.

This patch is similar to 24cc61d8cb5a ("arm64: memblock: don't permit memblock resizing until linear mapping is up").

In following log, many memblock regions are reserved before create_linear_mapping_page_table(). And then it triggered reallocation of memblock.reserved.regions and memcpy the old array in kernel image mapping to the new array in linear mapping which caused a page fault.

[ 0.000000] memblock_reserve: [0x00000000bf01f000-0x00000000bf01ffff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf021000-0x00000000bf021fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf023000-0x00000000bf023fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf025000-0x00000000bf025fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf027000-0x00000000bf027fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf029000-0x00000000bf029fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf02b000-0x00000000bf02bfff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf02d000-0x00000000bf02dfff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf02f000-0x00000000bf02ffff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] memblock_reserve: [0x00000000bf030000-0x00000000bf030fff] early_init_fdt_scan_reserved_mem+0x28c/0x2c6 [ 0.000000] OF: reserved mem: 0x0000000080000000..0x000000008007ffff (512 KiB) map non-reusable mmode_resv0@80000000 [ 0.000000] memblock_reserve: [0x00000000bf000000-0x00000000bf001fed] paging_init+0x19a/0x5ae [ 0.000000] memblock_phys_alloc_range: 4096 bytes align=0x1000 from=0x0000000000000000 max_addr=0x0000000000000000 alloc_pmd_fixmap+0x14/0x1c [ 0.000000] memblock_reserve: [0x000000017ffff000-0x000000017fffffff] memblock_alloc_range_nid+0xb8/0x128 [ 0.000000] memblock: reserved is doubled to 256 at [0x000000017fffd000-0x000000017fffe7ff] [ 0.000000] Unable to handle kernel paging request at virtual address ff600000ffffd000 [ 0.000000] Oops [#1] [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 6.4.0-rc1-00011-g99a670b2069c #66 [ 0.000000] Hardware name: riscv-virtio,qemu (DT) [ 0.000000] epc : __memcpy+0x60/0xf8 [ 0.000000] ra : memblock_double_array+0x192/0x248 [ 0.000000] epc : ffffffff8081d214 ra : ffffffff80a3dfc0 sp : ffffffff81403bd0 [ 0.000000] gp : ffffffff814fbb38 tp : ffffffff8140dac0 t0 : 0000000001600000 [ 0.000000] t1 : 0000000000000000 t2 : 000000008f001000 s0 : ffffffff81403c60 [ 0.000000] s1 : ffffffff80c0bc98 a0 : ff600000ffffd000 a1 : ffffffff80c0bcd8 [ 0.000000] a2 : 0000000000000c00 a3 : ffffffff80c0c8d8 a4 : 0000000080000000 [ 0.000000] a5 : 0000000000080000 a6 : 0000000000000000 a7 : 0000000080200000 [ 0.000000] s2 : ff600000ffffd000 s3 : 0000000000002000 s4 : 0000000000000c00 [ 0.000000] s5 : ffffffff80c0bc60 s6 : ffffffff80c0bcc8 s7 : 0000000000000000 [ 0.000000] s8 : ffffffff814fd0a8 s9 : 000000017fffe7ff s10: 0000000000000000 [ 0.000000] s11: 0000000000001000 t3 : 0000000000001000 t4 : 0000000000000000 [ 0.000000] t5 : 000000008f003000 t6 : ff600000ffffd000 [ 0.000000] status: 0000000200000100 badaddr: ff600000ffffd000 cause: 000000000000000f [ 0.000000] [

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 22, 2025

Last Modified

October 28, 2026

References (4)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.121 (fixes >=5.3.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (499 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 225 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-11-04 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-28 19:28 UTCEG score recompute
  11. 2026-10-28 19:28 UTCGHSA enrichmentGHSA-q328-fmmj-x9cj
  12. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-25 17:27 UTCEG score recompute
  16. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-25 08:48 UTCEG score recompute
  18. 2026-10-25 08:48 UTCGHSA enrichmentGHSA-q328-fmmj-x9cj
  19. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 69 more
  1. 2026-10-18 07:40 UTCEG score recompute
  2. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-12 18:12 UTCEG score recompute
  8. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-11 21:37 UTCEG score recompute
  10. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-06 07:54 UTCOSV refresh
  17. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-30 16:37 UTCEG score recompute
  22. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-09-16 15:25 UTCOSV refresh
  31. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  32. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  35. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  36. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  38. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  40. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  41. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  47. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  49. 2026-08-28 15:23 UTCOSV refresh
  50. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  51. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  52. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  57. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  58. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  59. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  60. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  61. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  62. 2026-08-12 03:34 UTCOSV refresh
  63. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  64. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  65. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  66. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  67. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  68. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  69. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile

Frequently asked(4)

What is CVE-2023-53699?
CVE-2023-53699 is a vulnerability whose severity is not yet rated; its CVE record was published on October 22, 2025. In the Linux kernel, the following vulnerability has been resolved: riscv: move memblock_allow_resize() after linear mapping is ready The initial memblock metadata is accessed from kernel image mapping. The regions arrays need to "reallocated" from memblock and accessed through linear mapping to…
When was the CVE record for CVE-2023-53699 published?
The CVE record for CVE-2023-53699 was published on October 22, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 28, 2026; the record at its source may have been updated since.
Is CVE-2023-53699 actively exploited?
CVE-2023-53699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2023-53699?
A fix for CVE-2023-53699 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53699

Explore →

Is Your Infrastructure Affected by CVE-2023-53699?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs