Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-22090: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()

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.21% (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 8d6373f83f367dbed316ddeb178130a3a64b5b67, a6623712ba8449876f0b3de9462831523fb851e4, b07398e8a5da517083f5c3f2daa8f6681b48ab28.

Low priority for now. Upgrade to Linux Linux 8d6373f83f367dbed316ddeb178130a3a64b5b67, a6623712ba8449876f0b3de9462831523fb851e4, b07398e8a5da517083f5c3f2daa8f6681b48ab28 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: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it clear initially), and undo the reservation if anything goes wrong while copying the page tables: clearing the VM_PAT flag after undoing the reservation. Note that any copied page table entries will get zapped when the VMA will get removed later, after copy_page_range() succeeded; as VM_PAT is not set then, we won't try cleaning VM_PAT up once more and untrack_pfn() will be happy. Note that leaving these page tables in place without a reservation is not a problem, as we are aborting fork(); this process will never run. A reproducer can trigger this usually at the first try: https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110 Modules linked in: ... CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 RIP: 0010:get_pat_info+0xf6/0x110 ... Call Trace: <TASK> ... untrack_pfn+0x52/0x110 unmap_single_vma+0xa6/0xe0 unmap_vmas+0x105/0x1f0 exit_mmap+0xf6/0x460 __mmput+0x4b/0x120 copy_process+0x1bf6/0x2aa0 kernel_clone+0xab/0x440 __do_sys_clone+0x66/0x90 do_syscall_64+0x95/0x180 Likely this case was missed in: d155df53f310 ("x86/mm/pat: clear VM_PAT if copy_p4d_range failed") ... and instead of undoing the reservation we simply cleared the VM_PAT flag. Keep the documentation of these functions in include/linux/pgtable.h, one place is more than sufficient -- we should clean that up for the other functions like track_pfn_remap/untrack_pfn separately.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 16, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 12th percentile
CWE
—

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
7.3
1.8 point gap

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

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-2025-22090

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

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

Affected versions

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

  • linux linux kernel2.6.29 and later · before 6.6.87
  • linux linux kernel6.7 and later · before 6.12.23
  • linux linux kernel6.13 and later · before 6.13.11
  • linux linux kernel6.14 and later · before 6.14.2

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

    • 2.6.29affected
    • 2ab640379a0ab4cef746ced1d7e04a0941774bcb and later · before a6623712ba8449876f0b3de9462831523fb851e4affected · git
    • 2ab640379a0ab4cef746ced1d7e04a0941774bcb and later · before b07398e8a5da517083f5c3f2daa8f6681b48ab28affected · git
    • 2ab640379a0ab4cef746ced1d7e04a0941774bcb and later · before 8d6373f83f367dbed316ddeb178130a3a64b5b67affected · git
    • 2ab640379a0ab4cef746ced1d7e04a0941774bcb and later · before da381c33f3aa6406406c9fdf07b8b0b63e0ce722affected · git
    • 2ab640379a0ab4cef746ced1d7e04a0941774bcb and later · before de6185b8892d88142ef69768fe4077cbf40109c0affected · git
    • 2ab640379a0ab4cef746ced1d7e04a0941774bcb and later · before dc84bc2aba85a1508f04a936f9f9a15f64ebfb31affected · git
    • before 2.6.29not affected · semver
    • 6.1.160 and later · up to and including 6.1.*not affected · semver
    • 6.6.87 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.162-1~deb11u16.1.162-1~deb11u1
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.25-16.12.25-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-azurebefore 6.4.0-150600.8.48.16.4.0-150600.8.48.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.65.1.150600.12.28.46.4.0-150600.23.65.1.150600.12.28.4
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-source-azurebefore 6.4.0-150600.8.48.16.4.0-150600.8.48.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
openSUSE:Leap 15.6kernel-syms-azurebefore 6.4.0-150600.8.48.16.4.0-150600.8.48.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_14before 1-150600.13.3.41-150600.13.3.4
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_3before 1-150700.15.3.41-150700.15.3.4
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-64kbbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-defaultbefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-default-basebefore 6.4.0-150600.23.65.1.150600.12.28.46.4.0-150600.23.65.1.150600.12.28.4
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-sourcebefore 6.4.0-150600.23.65.16.4.0-150600.23.65.1

+18

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-2025-22077Apr 16, 2025 · Revert "smb: client: fix TCP timers deadlock after rmmod"
    22Monitor
  • ← EarlierCVE-2025-22083Apr 16, 2025 · vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint
    31Monitor
  • Later →CVE-2025-22091Apr 16, 2025 · RDMA/mlx5: Fix page_size variable overflow
    22Monitor

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 Linux8d6373f83f367dbed316ddeb178130a3a64b5b67Vendor (CNA)
Linux Linuxa6623712ba8449876f0b3de9462831523fb851e4Vendor (CNA)
Linux Linuxb07398e8a5da517083f5c3f2daa8f6681b48ab28Vendor (CNA)
Linux Linuxda381c33f3aa6406406c9fdf07b8b0b63e0ce722Vendor (CNA)
Linux Linuxdc84bc2aba85a1508f04a936f9f9a15f64ebfb31Vendor (CNA)
Linux Linuxde6185b8892d88142ef69768fe4077cbf40109c0Vendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0—Microsoft (MSRC)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.162-1~deb11u1 · Debian:11Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.48.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.65.1.150600.12.28.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-qa6.4.0-150600.23.65.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-azure6.4.0-150600.8.48.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-azure6.4.0-150600.8.48.1 · openSUSE:Leap 15.6Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-azure6.4.0-150600.8.48.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.65.1.150600.12.28.4 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-docs6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_141-150600.13.3.4 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-obs-build6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-source6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-source-azure6.4.0-150600.8.48.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)

+3

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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

Weakness class (CWE)

—

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.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records