UBUNTU-CVE-2025-71107: Medium severity ubuntu/linux-hwe-edge vulnerability

Q: Which systems are realistically exposed to this issue?

Systems using an affected listed Ubuntu kernel package and mounting F2FS filesystems are exposed. The failure occurs during F2FS unmount while node-page reads are still incomplete.

Q: What access would an attacker need to trigger the problem?

The supplied vector indicates local access with low privileges and no user interaction is required. The available data does not describe a remote attack path or confidentiality or integrity impact.

Q: What is the practical impact of successful triggering?

The reported outcome is a kernel BUG during F2FS unmount, resulting in a denial-of-service condition. The severity vector reports availability impact only, with no confidentiality or integrity impact.

Q: How can administrators identify a likely occurrence?

Look for F2FS unmount failures reporting a filesystem reference-count leak followed by a kernel BUG in f2fs_put_super(). The supplied example includes the message "detect filesystem reference count leak during umount" and an invalid-opcode crash trace.

Published Jan 14, 2026

Updated

In the Linux kernel, the following vulnerability has been resolved: f2fs: ensure node page reads complete before f2fsputsuper() finishes Xfstests generic/335, generic/336 sometimes crash with the following message: F2FS-fs (dm-0): detect filesystem reference count leak during umount, type: 9, count: 1 ------------[ cut here ]------------ kernel BUG at fs/f2fs/super.c:1939! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 609351 Comm: umount Tainted: G W 6.17.0-rc5-xfstests-g9dd1835ecda5 #1 PREEMPT(none) Tainted: [W]=WARN Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:f2fsputsuper+0x3b3/0x3c0 Call Trace: <TASK> genericshutdownsuper+0x7e/0x190 killblocksuper+0x1a/0x40 killf2fssuper+0x9d/0x190 deactivatelockedsuper+0x30/0xb0 cleanupmnt+0xba/0x150 taskworkrun+0x5c/0xa0 exittousermodeloop+0xb7/0xc0 dosyscall64+0x1ae/0x1c0 entrySYSCALL64afterhwframe+0x76/0x7e </TASK> ---[ end trace 0000000000000000 ]--- It appears that sometimes it is possible that f2fsputsuper() is called before all node page reads are completed. Adding a call to f2fswaitonallpages() for F2FSRDNODE fixes the problem.

Affected Software

150 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-aws-6.8<6.8.0-1052.55~22.04.1

6.8.0-1052.55~22.04.1

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-6.8<6.8.0-1059.65~22.04.1

6.8.0-1059.65~22.04.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-azure-fde-6.8<6.8.0-1058.65~22.04.1

6.8.0-1058.65~22.04.1

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gcp-6.8<6.8.0-1054.57~22.04.1

6.8.0-1054.57~22.04.1

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-hwe-6.8<6.8.0-110.110~22.04.1

6.8.0-110.110~22.04.1

ubuntu/linux-ibm-6.8<6.8.0-1051.51~22.04.1

6.8.0-1051.51~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-lowlatency-hwe-6.8<6.8.0-110.110.1~22.04.1

6.8.0-110.110.1~22.04.1

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8<6.8.0-1051.54~22.04.1

6.8.0-1051.54~22.04.1

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-oracle-6.8<6.8.0-1049.50~22.04.1

6.8.0-1049.50~22.04.1

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-riscv-6.8<6.8.0-110.110~22.04.1

6.8.0-110.110~22.04.1

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-realtime-6.8<6.8.1-1047.48~22.04.1

6.8.1-1047.48~22.04.1

ubuntu/linux<6.8.0-110.110

6.8.0-110.110

ubuntu/linux-aws<6.8.0-1052.55

6.8.0-1052.55

ubuntu/linux-aws-6.14*

ubuntu/linux-aws-6.17<6.17.0-1012.12~24.04.1

6.17.0-1012.12~24.04.1

ubuntu/linux-azure<6.8.0-1054.60

6.8.0-1054.60

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-6.14*

ubuntu/linux-azure-6.17<6.17.0-1013.13~24.04.1

6.17.0-1013.13~24.04.1

ubuntu/linux-azure-fde<6.8.0-1058.65

6.8.0-1058.65

ubuntu/linux-azure-fde-6.14*

ubuntu/linux-azure-nvidia<6.8.0-1039.42

6.8.0-1039.42

ubuntu/linux-azure-nvidia-6.14*

ubuntu/linux-gcp<6.8.0-1054.57

6.8.0-1054.57

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14*

ubuntu/linux-gcp-6.17<6.17.0-1012.12~24.04.1

6.17.0-1012.12~24.04.1

ubuntu/linux-gke<6.8.0-1050.56

6.8.0-1050.56

ubuntu/linux-gkeop<6.8.0-1037.40

6.8.0-1037.40

ubuntu/linux-hwe-6.11*

ubuntu/linux-hwe-6.14*

ubuntu/linux-hwe-6.17<6.17.0-22.22~24.04.1

6.17.0-22.22~24.04.1

ubuntu/linux-ibm<6.8.0-1051.51

6.8.0-1051.51

ubuntu/linux-lowlatency<6.8.0-110.110.1

6.8.0-110.110.1

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia<6.8.0-1051.54

6.8.0-1051.54

ubuntu/linux-nvidia-6.11*

ubuntu/linux-nvidia-6.17<6.17.0-1018.18

6.17.0-1018.18

ubuntu/linux-nvidia-lowlatency<6.8.0-1051.54.1

6.8.0-1051.54.1

ubuntu/linux-nvidia-tegra<6.8.0-1022.22

6.8.0-1022.22

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14*

ubuntu/linux-oem-6.17<6.17.0-1020.20

6.17.0-1020.20

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle<6.8.0-1049.50

6.8.0-1049.50

ubuntu/linux-oracle-6.14*

ubuntu/linux-oracle-6.17<6.17.0-1011.11~24.04.1

6.17.0-1011.11~24.04.1

ubuntu/linux-raspi<6.8.0-1052.56

6.8.0-1052.56

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14*

ubuntu/linux-riscv-6.17<6.17.0-22.22.1~24.04.1

6.17.0-22.22.1~24.04.1

ubuntu/linux-xilinx<6.8.0-1028.29

6.8.0-1028.29

ubuntu/linux-bluefield<6.8.0-1017.21

6.8.0-1017.21

ubuntu/linux-raspi-realtime<6.8.0-2042.43

6.8.0-2042.43

ubuntu/linux-realtime<6.8.1-1047.48

6.8.1-1047.48

ubuntu/linux-realtime-6.14*

ubuntu/linux-realtime-6.17<6.17.0-1010.11~24.04.1

6.17.0-1010.11~24.04.1

ubuntu/linux-aws-fips<6.8.0-1052.55+fips1

6.8.0-1052.55+fips1

ubuntu/linux-azure-fips<6.8.0-1053.59+fips1

6.8.0-1053.59+fips1

ubuntu/linux-fips<6.8.0-110.110+fips2

6.8.0-110.110+fips2

ubuntu/linux-gcp-fips<6.8.0-1054.57+fips1

6.8.0-1054.57+fips1

ubuntu/linux<6.17.0-22.22

6.17.0-22.22

ubuntu/linux-aws<6.17.0-1012.12

6.17.0-1012.12

ubuntu/linux-azure<6.17.0-1013.13

6.17.0-1013.13

ubuntu/linux-azure-fde*

ubuntu/linux-gcp<6.17.0-1012.12

6.17.0-1012.12

ubuntu/linux-oracle<6.17.0-1011.11

6.17.0-1011.11

ubuntu/linux-raspi<6.17.0-1013.13

6.17.0-1013.13

ubuntu/linux-realtime<6.17.0-1010.11

6.17.0-1010.11

ubuntu/linux-riscv<6.17.0-22.22.1

6.17.0-22.22.1

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1052.55~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1059.65~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1058.65~22.04.1
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1054.57~22.04.1
Upgrade
Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-110.110~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1051.51~22.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-110.110.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1051.54~22.04.1
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1049.50~22.04.1
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-110.110~22.04.1
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1047.48~22.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-110.110
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1052.55
Upgrade
Upgrade ubuntu/linux-aws-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1012.12~24.04.1
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1054.60
Upgrade
Upgrade ubuntu/linux-azure-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1013.13~24.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 6.8.0-1058.65
Upgrade
Upgrade ubuntu/linux-azure-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.42
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1054.57
Upgrade
Upgrade ubuntu/linux-gcp-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1012.12~24.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1050.56
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1037.40
Upgrade
Upgrade ubuntu/linux-hwe-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-22.22~24.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1051.51
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-110.110.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1051.54
Upgrade
Upgrade ubuntu/linux-nvidia-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1018.18
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1051.54.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 6.8.0-1022.22
Upgrade
Upgrade ubuntu/linux-oem-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1020.20
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1049.50
Upgrade
Upgrade ubuntu/linux-oracle-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1011.11~24.04.1
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1052.56
Upgrade
Upgrade ubuntu/linux-riscv-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-22.22.1~24.04.1
Upgrade
Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.
Fixed in 6.8.0-1028.29
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.21
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2042.43
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1047.48
Upgrade
Upgrade ubuntu/linux-realtime-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1010.11~24.04.1
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1052.55+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1053.59+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-110.110+fips2
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1054.57+fips1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.17.0-22.22
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.17.0-1012.12
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.17.0-1013.13
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.17.0-1012.12
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.17.0-1011.11
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.17.0-1013.13
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.17.0-1010.11
Upgrade
Upgrade ubuntu/linux-riscv to a version that resolves this vulnerability.
Fixed in 6.17.0-22.22.1
Compensating control
Add a call to f2fs_wait_on_all_pages() for F2FS_RD_NODE so node page reads complete before f2fs_put_super() finishes.

Event History

Jan 14, 2026

CVE Published

via OSV·03:15 PM

Data Sourced

via OSV·03:15 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are realistically exposed to this issue?

Systems using an affected listed Ubuntu kernel package and mounting F2FS filesystems are exposed. The failure occurs during F2FS unmount while node-page reads are still incomplete.

What access would an attacker need to trigger the problem?

The supplied vector indicates local access with low privileges and no user interaction is required. The available data does not describe a remote attack path or confidentiality or integrity impact.

What is the practical impact of successful triggering?

The reported outcome is a kernel BUG during F2FS unmount, resulting in a denial-of-service condition. The severity vector reports availability impact only, with no confidentiality or integrity impact.

How can administrators identify a likely occurrence?

Look for F2FS unmount failures reporting a filesystem reference-count leak followed by a kernel BUG in f2fs_put_super(). The supplied example includes the message "detect filesystem reference count leak during umount" and an invalid-opcode crash trace.

UBUNTU-CVE-2025-71107: Medium severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are realistically exposed to this issue?

What access would an attacker need to trigger the problem?

What is the practical impact of successful triggering?

How can administrators identify a likely occurrence?

Company

Resources

Contact

Frequently Asked Questions

Which systems are realistically exposed to this issue?

What access would an attacker need to trigger the problem?

What is the practical impact of successful triggering?

How can administrators identify a likely occurrence?