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-53989arm64: mm: fix VA-range sanity check

Description

In the Linux kernel, the following vulnerability has been resolved: arm64: mm: fix VA-range sanity check Both create_mapping_noalloc() and update_mapping_prot() sanity-check their 'virt' parameter, but the check itself doesn't make much sense. The condition used today appears to be a historical accident. The sanity-check condition: if ((virt >= PAGE_END) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } ... can only be true for the KASAN shadow region or the module region, and there's no reason to exclude these specifically for creating and updateing mappings. When arm64 support was first upstreamed in commit: c1cc1552616d0f35 ("arm64: MMU initialisation") ... the condition was: if (virt < VMALLOC_START) { [ ... warning here ... ] return; } At the time, VMALLOC_START was the lowest kernel address, and this was checking whether 'virt' would be translated via TTBR1. Subsequently in commit: 14c127c957c1c607 ("arm64: mm: Flip kernel VA space") ... the condition was changed to: if ((virt >= VA_START) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } This appear to have been a thinko. The commit moved the linear map to the bottom of the kernel address space, with VMALLOC_START being at the halfway point. The old condition would warn for changes to the linear map below this, and at the time VA_START was the end of the linear map. Subsequently we cleaned up the naming of VA_START in commit: 77ad4ce69321abbe ("arm64: memory: rename VA_START to PAGE_END") ... keeping the erroneous condition as: if ((virt >= PAGE_END) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } Correct the condition to check against the start of the TTBR1 address space, which is currently PAGE_OFFSET. This simplifies the logic, and more clearly matches the "outside kernel range" message in the warning.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 14c127c957c1c6070647c171e72f06e0db275ebf – < 9d8d3df71516ec3236d8d93ff029d251377ba4b1
    • affected 14c127c957c1c6070647c171e72f06e0db275ebf – < 32020fc2a8373d3de35ae6d029d5969a42651e7a
    • affected 14c127c957c1c6070647c171e72f06e0db275ebf – < 621619f626cbe702ddbdc54117f3868b8ebd8129
    • affected 14c127c957c1c6070647c171e72f06e0db275ebf – < c7a9e967cc9615a1dabc5e0e6fdbe88a172d5a5b
    • affected 14c127c957c1c6070647c171e72f06e0db275ebf – < b03c7fcc5ed854d0e1b27e9abf12428bfa751a37
    • affected 14c127c957c1c6070647c171e72f06e0db275ebf – < ab9b4008092c86dc12497af155a0901cc1156999
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.4.251 – ≤ 5.4.*
    • unaffected 5.10.188 – ≤ 5.10.*
    • unaffected 5.15.150 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.4.7 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .