CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops
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.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 5c8f12cf1e64e0e8e6cb80b0c935389973e8be8d, 9d9b053f7f9c5a35049abe56af9e6ac70b6b0e4b, 9f745095c382b76e68407fd6f15ef27baf2a013f; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
Low priority for now. Upgrade to Linux Linux 5c8f12cf1e64e0e8e6cb80b0c935389973e8be8d, 9d9b053f7f9c5a35049abe56af9e6ac70b6b0e4b, 9f745095c382b76e68407fd6f15ef27baf2a013f; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-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: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops Clears up the warning added in 7ee3647243e5 ("migrate: Remove call to ->writepage") that occurs in various xfstests, causing "something found in dmesg" failures. [ 341.136573] gfs2_meta_aops does not implement migrate_folio [ 341.136953] WARNING: CPU: 1 PID: 36 at mm/migrate.c:944 move_to_new_folio+0x2f8/0x300
- Published
- Sep 11, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.6.103
- linux linux kernel6.7 and later · before 6.12.43
- linux linux kernel6.13 and later · before 6.15.11
- linux linux kernel6.16 and later · before 6.16.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
- 6.12affected
- 901849e7070b2b74ba1adaaf025a09a1f381fefe and later · before 9d9b053f7f9c5a35049abe56af9e6ac70b6b0e4baffected · git
- 901849e7070b2b74ba1adaaf025a09a1f381fefe and later · before 9f745095c382b76e68407fd6f15ef27baf2a013faffected · git
- 901849e7070b2b74ba1adaaf025a09a1f381fefe and later · before e89cab180eb22950b6eb7b3462623c2aa81e5835affected · git
- 901849e7070b2b74ba1adaaf025a09a1f381fefe and later · before 5c8f12cf1e64e0e8e6cb80b0c935389973e8be8daffected · git
- before 6.12not affected · semver
- 6.12.43 and later · up to and including 6.12.*not affected · semver
- 6.15.11 and later · up to and including 6.15.*not affected · semver
- 6.16.2 and later · up to and including 6.16.*not affected · semver
- 6.17 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.43-1 | 6.12.43-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.27.1.160000.2.8 | 6.12.0-160000.27.1.160000.2.8 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.27.1.160000.2.8 | 6.12.0-160000.27.1.160000.2.8 |
| SUSE:Linux Micro 6.2 | kernel-rt | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
+3
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39750Sep 11, 2025 · wifi: ath12k: Correct tid cleanup when tid setup fails28Monitor
- ← EarlierCVE-2025-39752Sep 11, 2025 · ARM: rockchip: fix kernel hang during smp initialization22Monitor
- Later →CVE-2025-39754Sep 11, 2025 · mm/smaps: fix race between smaps_hugetlb_range and migration18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5c8f12cf1e64e0e8e6cb80b0c935389973e8be8d | Vendor (CNA) |
| Linux Linux | 9d9b053f7f9c5a35049abe56af9e6ac70b6b0e4b | Vendor (CNA) |
| Linux Linux | 9f745095c382b76e68407fd6f15ef27baf2a013f | Vendor (CNA) |
| Linux Linux | e89cab180eb22950b6eb7b3462623c2aa81e5835 | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.43-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.27.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.27.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.27.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.27.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.27.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.27.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
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.
Credits
All researchersFinders, 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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.