CVE-2025-39753
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-11

Last updated on: 2025-11-25

Assigner: kernel.org

Description
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
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-11
Last Modified
2025-11-25
Generated
2026-06-16
AI Q&A
2025-09-11
EPSS Evaluated
2026-06-15
NVD
CVE-2025-39753
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-NVD-CWE-noinfo
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability relates to the Linux kernel's gfs2 filesystem code where the .migrate_folio function was not set in gfs2_{rgrp,meta}_aops. This omission caused warnings and failures during certain filesystem tests (xfstests), specifically warnings about gfs2_meta_aops not implementing migrate_folio and related kernel warnings.

Impact Analysis

The impact is primarily related to system stability and reliability during filesystem operations and testing. The missing .migrate_folio implementation caused warnings and test failures, which could indicate potential issues in memory management or filesystem migration processes, possibly leading to degraded system performance or unexpected behavior under certain conditions.

Detection Guidance

You can detect this vulnerability by checking your system logs for specific warning messages related to gfs2 and migrate_folio. For example, look for messages like '[ 341.136573] gfs2_meta_aops does not implement migrate_folio' or warnings from migrate.c such as 'WARNING: CPU: 1 PID: 36 at mm/migrate.c:944 move_to_new_folio'. You can use the command 'dmesg | grep migrate_folio' or 'journalctl -k | grep migrate_folio' to find these warnings in the kernel logs.

Mitigation Strategies

The immediate mitigation is to update your Linux kernel to a version where the gfs2 .migrate_folio implementation has been fixed as described. Applying the patch that sets .migrate_folio in gfs2_{rgrp,meta}_aops will clear the warning and prevent related failures in xfstests.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-39753. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart