Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52490: mm: migrate: fix getting incorrect page mapping during page migration

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1ce870a2d85969e2c9dafd2af20f205494a490f6, 3889a418b6eb9a1113fb989aaadecf2f64964767, 6.1.191.

Low priority for now. Upgrade to Linux Linux 1ce870a2d85969e2c9dafd2af20f205494a490f6, 3889a418b6eb9a1113fb989aaadecf2f64964767, 6.1.191 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: mm: migrate: fix getting incorrect page mapping during page migration When running stress-ng testing, we found below kernel crash after a few hours: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 pc : dentry_name+0xd8/0x224 lr : pointer+0x22c/0x370 sp : ffff800025f134c0 ...... Call trace: dentry_name+0xd8/0x224 pointer+0x22c/0x370 vsnprintf+0x1ec/0x730 vscnprintf+0x2c/0x60 vprintk_store+0x70/0x234 vprintk_emit+0xe0/0x24c vprintk_default+0x3c/0x44 vprintk_func+0x84/0x2d0 printk+0x64/0x88 __dump_page+0x52c/0x530 dump_page+0x14/0x20 set_migratetype_isolate+0x110/0x224 start_isolate_page_range+0xc4/0x20c offline_pages+0x124/0x474 memory_block_offline+0x44/0xf4 memory_subsys_offline+0x3c/0x70 device_offline+0xf0/0x120 ...... After analyzing the vmcore, I found this issue is caused by page migration. The scenario is that, one thread is doing page migration, and we will use the target page's ->mapping field to save 'anon_vma' pointer between page unmap and page move, and now the target page is locked and refcount is 1. Currently, there is another stress-ng thread performing memory hotplug, attempting to offline the target page that is being migrated. It discovers that the refcount of this target page is 1, preventing the offline operation, thus proceeding to dump the page. However, page_mapping() of the target page may return an incorrect file mapping to crash the system in dump_mapping(), since the target page->mapping only saves 'anon_vma' pointer without setting PAGE_MAPPING_ANON flag. There are seveval ways to fix this issue: (1) Setting the PAGE_MAPPING_ANON flag for target page's ->mapping when saving 'anon_vma', but this can confuse PageAnon() for PFN walkers, since the target page has not built mappings yet. (2) Getting the page lock to call page_mapping() in __dump_page() to avoid crashing the system, however, there are still some PFN walkers that call page_mapping() without holding the page lock, such as compaction. (3) Using target page->private field to save the 'anon_vma' pointer and 2 bits page state, just as page->mapping records an anonymous page, which can remove the page_mapping() impact for PFN walkers and also seems a simple way. So I choose option 3 to fix this issue, and this can also fix other potential issues for PFN walkers, such as compaction.

Published
Mar 11, 2024
Updated
Oct 30, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
5.5
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-52490

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.3affected
    • 8ca5f0ea52e1eef5e7dcbdff1d1afe602764ea93 and later · before 1ce870a2d85969e2c9dafd2af20f205494a490f6affected · git
    • 64c8902ed4418317cd416c566f896bd4a92b2efc and later · before 9128bfbc5c80d8f4874dd0a0424d1f5fb010df1baffected · git
    • 64c8902ed4418317cd416c566f896bd4a92b2efc and later · before 3889a418b6eb9a1113fb989aaadecf2f64964767affected · git
    • 64c8902ed4418317cd416c566f896bd4a92b2efc and later · before d1adb25df7111de83b64655a80b5a135adbded61affected · git
    • 6.1.116 and later · before 6.1.191affected · semver
    • before 6.3not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.15 and later · up to and including 6.6.*not affected · semver
    • 6.7.3 and later · up to and including 6.7.*not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.3 and later · before 6.6.15
  • linux linux kernel6.7 and later · before 6.7.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.4.0-503.26.1.el9_57.4.0-503.26.1.el9_5
AlmaLinux:9kernelbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64kbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-corebefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-debugbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-develbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-corebefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-cross-headersbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-debugbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-debug-corebefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-debug-develbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-503.26.1.el9_55.14.0-503.26.1.el9_5

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26619Mar 11, 2024 · riscv: Fix module loading free order
    31Monitor
  • ← EarlierCVE-2024-26620Mar 11, 2024 · s390/vfio-ap: always filter entire AP matrix
    30Monitor
  • Later →CVE-2023-52608Mar 13, 2024 · firmware: arm_scmi: Check mailbox/SMT channel for consistency
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1ce870a2d85969e2c9dafd2af20f205494a490f6Vendor (CNA)
Linux Linux3889a418b6eb9a1113fb989aaadecf2f64964767Vendor (CNA)
Linux Linux6.1.191Vendor (CNA)
Linux Linux9128bfbc5c80d8f4874dd0a0424d1f5fb010df1bVendor (CNA)
Linux Linuxd1adb25df7111de83b64655a80b5a135adbded61Vendor (CNA)
almalinux:bpftool7.4.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-503.26.1.el9_5 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.192-1 · Debian:12Package registry (OSV)
debian:linux6.6.15-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.4.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-503.26.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records