Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39883: mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory

Noroxi assessment

Priority: Monitor (action score 28/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.15% (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 3d278e89c2ea62b1aaa4b0d8a9766a35b3a3164a, 63a327a2375a8ce7a47dec5aaa4d8a9ae0a00b96, 7618fd443aa4cfa553a64cacf5721581653ee7b0; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.

Low priority for now. Upgrade to Linux Linux 3d278e89c2ea62b1aaa4b0d8a9766a35b3a3164a, 63a327a2375a8ce7a47dec5aaa4d8a9ae0a00b96, 7618fd443aa4cfa553a64cacf5721581653ee7b0; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 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/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory When I did memory failure tests, below panic occurs: page dumped because: VM_BUG_ON_PAGE(PagePoisoned(page)) kernel BUG at include/linux/page-flags.h:616! Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 720 Comm: bash Not tainted 6.10.0-rc1-00195-g148743902568 #40 RIP: 0010:unpoison_memory+0x2f3/0x590 RSP: 0018:ffffa57fc8787d60 EFLAGS: 00000246 RAX: 0000000000000037 RBX: 0000000000000009 RCX: ffff9be25fcdc9c8 RDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff9be25fcdc9c0 RBP: 0000000000300000 R08: ffffffffb4956f88 R09: 0000000000009ffb R10: 0000000000000284 R11: ffffffffb4926fa0 R12: ffffe6b00c000000 R13: ffff9bdb453dfd00 R14: 0000000000000000 R15: fffffffffffffffe FS: 00007f08f04e4740(0000) GS:ffff9be25fcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000564787a30410 CR3: 000000010d4e2000 CR4: 00000000000006f0 Call Trace: <TASK> unpoison_memory+0x2f3/0x590 simple_attr_write_xsigned.constprop.0.isra.0+0xb3/0x110 debugfs_attr_write+0x42/0x60 full_proxy_write+0x5b/0x80 vfs_write+0xd5/0x540 ksys_write+0x64/0xe0 do_syscall_64+0xb9/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f08f0314887 RSP: 002b:00007ffece710078 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 00007f08f0314887 RDX: 0000000000000009 RSI: 0000564787a30410 RDI: 0000000000000001 RBP: 0000564787a30410 R08: 000000000000fefe R09: 000000007fffffff R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000009 R13: 00007f08f041b780 R14: 00007f08f0417600 R15: 00007f08f0416a00 </TASK> Modules linked in: hwpoison_inject ---[ end trace 0000000000000000 ]--- RIP: 0010:unpoison_memory+0x2f3/0x590 RSP: 0018:ffffa57fc8787d60 EFLAGS: 00000246 RAX: 0000000000000037 RBX: 0000000000000009 RCX: ffff9be25fcdc9c8 RDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff9be25fcdc9c0 RBP: 0000000000300000 R08: ffffffffb4956f88 R09: 0000000000009ffb R10: 0000000000000284 R11: ffffffffb4926fa0 R12: ffffe6b00c000000 R13: ffff9bdb453dfd00 R14: 0000000000000000 R15: fffffffffffffffe FS: 00007f08f04e4740(0000) GS:ffff9be25fcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000564787a30410 CR3: 000000010d4e2000 CR4: 00000000000006f0 Kernel panic - not syncing: Fatal exception Kernel Offset: 0x31c00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) ---[ end Kernel panic - not syncing: Fatal exception ]--- The root cause is that unpoison_memory() tries to check the PG_HWPoison flags of an uninitialized page. So VM_BUG_ON_PAGE(PagePoisoned(page)) is triggered. This can be reproduced by below steps: 1.Offline memory block: echo offline > /sys/devices/system/memory/memory12/state 2.Get offlined memory pfn: page-types -b n -rlN 3.Write pfn to unpoison-pfn echo <pfn> > /sys/kernel/debug/hwpoison/unpoison-pfn This scenario can be identified by pfn_to_online_page() returning NULL. And ZONE_DEVICE pages are never expected, so we can simply fail if pfn_to_online_page() == NULL to fix the bug.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Sep 23, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-39883

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
debiandebian linux

Affected versions

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

  • debian debian linux11.0
  • linux linux kernel4.13 and later · before 5.4.300
  • linux linux kernel5.5 and later · before 5.10.245
  • linux linux kernel5.11 and later · before 5.15.194
  • linux linux kernel5.16 and later · before 6.1.153
  • linux linux kernel6.2 and later · before 6.6.107
  • linux linux kernel6.7 and later · before 6.12.48
  • linux linux kernel6.13 and later · before 6.16.8
  • linux linux kernel6.17

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

    • 4.13affected
    • f1dd2cd13c4bbbc9a7c4617b3b034fa643de98fe and later · before 8e01ea186a52c90694c08a9ff57bea1b0e78256aaffected · git
    • f1dd2cd13c4bbbc9a7c4617b3b034fa643de98fe and later · before fb65803ccff37cf9123c50c1c02efd1ed73c4ed5affected · git
    • f1dd2cd13c4bbbc9a7c4617b3b034fa643de98fe and later · before 99f7048957f5ae3cee1c01189147e73a9a96de02affected · git
    • f1dd2cd13c4bbbc9a7c4617b3b034fa643de98fe and later · before e4ec6def5643a1c9511115b3884eb879572294c6affected · git
    • f1dd2cd13c4bbbc9a7c4617b3b034fa643de98fe and later · before 3d278e89c2ea62b1aaa4b0d8a9766a35b3a3164aaffected · git
    • f1dd2cd13c4bbbc9a7c4617b3b034fa643de98fe and later · before 7618fd443aa4cfa553a64cacf5721581653ee7b0affected · git
    • f1dd2cd13c4bbbc9a7c4617b3b034fa643de98fe and later · before 63a327a2375a8ce7a47dec5aaa4d8a9ae0a00b96affected · git
    • f1dd2cd13c4bbbc9a7c4617b3b034fa643de98fe and later · before d613f53c83ec47089c4e25859d5e8e0359f6f8daaffected · git
    • before 4.13not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.16.1.el10_16.12.0-124.16.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.16.1.el10_16.12.0-124.16.1.el10_1
AlmaLinux:8bpftoolbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.87.1.el8_104.18.0-553.87.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.87.1.rt7.428.el8_104.18.0-553.87.1.rt7.428.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.87.1.rt7.428.el8_104.18.0-553.87.1.rt7.428.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.87.1.rt7.428.el8_104.18.0-553.87.1.rt7.428.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.87.1.rt7.428.el8_104.18.0-553.87.1.rt7.428.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.87.1.rt7.428.el8_104.18.0-553.87.1.rt7.428.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.87.1.rt7.428.el8_104.18.0-553.87.1.rt7.428.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.87.1.rt7.428.el8_104.18.0-553.87.1.rt7.428.el8_10

+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-2025-39881Sep 23, 2025 · kernfs: Fix UAF in polling when open file is released
    31Monitor
  • ← EarlierCVE-2025-39882Sep 23, 2025 · drm/mediatek: fix potential OF node use-after-free
    31Monitor
  • Later →CVE-2025-39884Sep 23, 2025 · btrfs: fix subvolume deletion lockup caused by inodes xarray race
    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 Linux3d278e89c2ea62b1aaa4b0d8a9766a35b3a3164aVendor (CNA)
Linux Linux63a327a2375a8ce7a47dec5aaa4d8a9ae0a00b96Vendor (CNA)
Linux Linux7618fd443aa4cfa553a64cacf5721581653ee7b0Vendor (CNA)
Linux Linux8e01ea186a52c90694c08a9ff57bea1b0e78256aVendor (CNA)
Linux Linux99f7048957f5ae3cee1c01189147e73a9a96de02Vendor (CNA)
Linux Linuxd613f53c83ec47089c4e25859d5e8e0359f6f8daVendor (CNA)
Linux Linuxe4ec6def5643a1c9511115b3884eb879572294c6Vendor (CNA)
Linux Linuxfb65803ccff37cf9123c50c1c02efd1ed73c4ed5Vendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.05.15.200.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.87.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.87.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.87.1.rt7.428.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)

+7

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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
high · data can be read
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
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

All records