Skip to content
Fencer Vulns
medium 5.5

CVE-2025-39753 json

gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops

published 2025-09-11 13 mo ago modified 2026-11-05 3 d ago also EUVD-2025-28958

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

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

Patch / fix

  • Linux Linux 6.12.43, 6.15.11, 6.16.2, 6.17
  • linux Debian 13 6.12.43-1
  • linux Debian 14 6.16.3-1

debian advisories DEBIAN-CVE-2025-39753

  • kernel-syms SLES 16.0, Linux Micro Extras 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1
  • kernel-obs-build Linux Micro Extras 6.2 6.12.0-160000.27.1
  • kernel-rt Linux Micro 6.2 6.12.0-160000.27.1
  • kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1
  • kernel-source SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1
  • kernel-default SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1
  • kernel-default-base SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1.160000.2.8
  • kernel-azure SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.27.1

suse advisories SUSE-SU-2026:20873-1SUSE-SU-2026:20838-1SUSE-SU-2026:20931-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.27.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.27.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.27.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.27.1
  • kernel-azure openSUSE Leap 16.0 6.12.0-160000.27.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.27.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.27.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.27.1

opensuse advisories openSUSE-SU-2026:20416-1

  • kernel Azure Linux 3.0 6.6.104.2-1

azure linux advisories AZL-67163

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-39753 updated cvss 5.5

kernel: Linux kernel (gfs2): Denial of Service due to missing migrate_folio implementation

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 d ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.