UBUNTU-CVE-2025-21712: Ubuntu/linux vulnerability

Q: What systems are realistically exposed to this issue?

Systems running one of the listed Ubuntu kernel packages may be exposed when they use the Linux MD RAID subsystem and the affected bitmap statistics path is accessed. The fault occurs while the MD device still exists but its bitmap has been destroyed or has not completed initialization.

Q: What does an attacker or triggering condition need to cause the crash?

The triggering condition is access to bitmap statistics through the MD proc/seq reporting path while the bitmap lifetime state is inconsistent. The provided data does not establish that this requires remote access or any particular privilege level.

Q: What is the likely impact if the issue is triggered?

Dereferencing the bitmap after it is destroyed or before it is fully initialized can cause a kernel general protection fault and crash the system. The report describes a panic in bitmap_get_stats() during a proc read.

Q: How can I identify whether a system has encountered this problem?

Look for kernel panic or Oops logs showing a general protection fault in bitmap_get_stats(), with a call trace including md_seq_show, seq_read_iter, proc_reg_read, and vfs_read. This indicates bitmap statistics were read during an invalid bitmap lifetime state.

Q: What change addresses the race?

The resolved fix protects bitmap_get_stats() with bitmap_info.mutex, synchronizing statistics access with the bitmap lifetime. Apply the relevant Ubuntu kernel update for the installed kernel package when available.

Published Feb 27, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved: md/md-bitmap: Synchronize bitmapgetstats() with bitmap lifetime After commit ec6bb299c7c3 ("md/md-bitmap: add 'syncsize' into struct mdbitmapstats"), following panic is reported: Oops: general protection fault, probably for non-canonical address RIP: 0010:bitmapgetstats+0x2b/0xa0 Call Trace: <TASK> mdseqshow+0x2d2/0x5b0 seqreaditer+0x2b9/0x470 seqread+0x12f/0x180 procregread+0x57/0xb0 vfsread+0xf6/0x380 ksysread+0x6c/0xf0 dosyscall64+0x82/0x170 entrySYSCALL64afterhwframe+0x76/0x7e Root cause is that bitmapgetstats() can be called at anytime if mddev is still there, even if bitmap is destroyed, or not fully initialized. Deferenceing bitmap in this case can crash the kernel. Meanwhile, the above commit start to deferencing bitmap->storage, make the problem easier to trigger. Fix the problem by protecting bitmapgetstats() with bitmapinfo.mutex.

Affected Software

209 affected componentsFixes available

ubuntu/linux*

ubuntu/linux-aws*

ubuntu/linux-azure*

ubuntu/linux-lts-xenial*

ubuntu/linux*

ubuntu/linux-aws*

ubuntu/linux-aws-hwe*

ubuntu/linux-azure*

ubuntu/linux-gcp*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-kvm*

ubuntu/linux-oracle*

ubuntu/linux-fips*

ubuntu/linux*

ubuntu/linux-aws*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-aws-5.4*

ubuntu/linux-azure*

ubuntu/linux-azure-4.15*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-5.4*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-4.15*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gcp-5.4*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-5.4*

ubuntu/linux-hwe-edge*

ubuntu/linux-ibm-5.4*

ubuntu/linux-kvm*

ubuntu/linux-oem*

ubuntu/linux-oracle*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-oracle-5.4*

ubuntu/linux-raspi-5.4*

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux*

ubuntu/linux-aws*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.15<5.15.0-1112.119~20.04.1

5.15.0-1112.119~20.04.1

ubuntu/linux-aws-5.8*

ubuntu/linux-azure*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.15<5.15.0-1117.126~20.04.1

5.15.0-1117.126~20.04.1

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-azure-fde-5.15<5.15.0-1117.126~20.04.2

5.15.0-1117.126~20.04.2

ubuntu/linux-bluefield*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.15<5.15.0-1112.122~20.04.1

5.15.0-1112.122~20.04.1

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.15<5.15.0-186.196~20.04.1

5.15.0-186.196~20.04.1

ubuntu/linux-hwe-5.8*

ubuntu/linux-ibm*

ubuntu/linux-ibm-5.15<5.15.0-1106.110~20.04.1

5.15.0-1106.110~20.04.1

ubuntu/linux-intel-5.13*

ubuntu/linux-intel-iotg-5.15<5.15.0-1107.113~20.04.1

5.15.0-1107.113~20.04.1

ubuntu/linux-iot*

ubuntu/linux-kvm*

ubuntu/linux-lowlatency-hwe-5.15<5.15.0-184.194~20.04.1

5.15.0-184.194~20.04.1

ubuntu/linux-nvidia-tegra-5.15<5.15.0-1064.66~20.04.1

5.15.0-1064.66~20.04.1

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.15<5.15.0-1109.115~20.04.1

5.15.0-1109.115~20.04.1

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.15<5.15.0-1106.110~20.04.1

5.15.0-1106.110~20.04.1

ubuntu/linux-riscv-5.8*

ubuntu/linux-xilinx-zynqmp*

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux<5.15.0-186.196

5.15.0-186.196

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws<5.15.0-1112.119

5.15.0-1112.119

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

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

6.8.0-1035.37~22.04.1

ubuntu/linux-azure<5.15.0-1117.126

5.15.0-1117.126

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

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

6.8.0-1034.39~22.04.1

ubuntu/linux-azure-fde<5.15.0-1117.126

5.15.0-1117.126

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp<5.15.0-1112.122

5.15.0-1112.122

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

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

6.8.0-1036.38~22.04.1

ubuntu/linux-gke<5.15.0-1108.114

5.15.0-1108.114

ubuntu/linux-gkeop<5.15.0-1095.103

5.15.0-1095.103

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

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

6.8.0-78.78~22.04.1

ubuntu/linux-ibm<5.15.0-1106.110

5.15.0-1106.110

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

6.8.0-1033.33~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-intel-iotg<5.15.0-1107.113

5.15.0-1107.113

ubuntu/linux-kvm<5.15.0-1104.109

5.15.0-1104.109

ubuntu/linux-lowlatency<5.15.0-184.194

5.15.0-184.194

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-78.78.1~22.04.1

6.8.0-78.78.1~22.04.1

ubuntu/linux-nvidia<5.15.0-1107.108

5.15.0-1107.108

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

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

6.8.0-1035.38~22.04.1

ubuntu/linux-nvidia-tegra<5.15.0-1064.66

5.15.0-1064.66

ubuntu/linux-nvidia-tegra-igx<5.15.0-1053.53

5.15.0-1053.53

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle<5.15.0-1109.115

5.15.0-1109.115

ubuntu/linux-oracle-6.5*

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

6.8.0-1032.33~22.04.1

ubuntu/linux-raspi<5.15.0-1106.109

5.15.0-1106.109

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

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

6.8.0-78.78~22.04.1

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-xilinx-zynqmp<5.15.0-1075.79

5.15.0-1075.79

ubuntu/linux-bluefield<5.15.0-1096.98

5.15.0-1096.98

ubuntu/linux-intel-iot-realtime<5.15.0-1104.106

5.15.0-1104.106

ubuntu/linux-realtime<5.15.0-1111.120

5.15.0-1111.120

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

6.8.1-1030.31~22.04.1

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux-aws-fips<5.15.0-1112.119+fips1

5.15.0-1112.119+fips1

ubuntu/linux-azure-fips<5.15.0-1117.126+fips1

5.15.0-1117.126+fips1

ubuntu/linux-fips<5.15.0-186.196+fips1

5.15.0-186.196+fips1

ubuntu/linux-gcp-fips<5.15.0-1112.122+fips1

5.15.0-1112.122+fips1

ubuntu/linux<6.8.0-78.78

6.8.0-78.78

ubuntu/linux-aws<6.8.0-1035.37

6.8.0-1035.37

ubuntu/linux-azure<6.8.0-1034.39

6.8.0-1034.39

ubuntu/linux-azure-6.11<6.11.0-1015.15~24.04.1

6.11.0-1015.15~24.04.1

ubuntu/linux-azure-nvidia<6.8.0-1022.23

6.8.0-1022.23

ubuntu/linux-gcp<6.8.0-1036.38

6.8.0-1036.38

ubuntu/linux-gcp-6.11<6.11.0-1015.15~24.04.1

6.11.0-1015.15~24.04.1

ubuntu/linux-gke<6.8.0-1032.36

6.8.0-1032.36

ubuntu/linux-gkeop<6.8.0-1019.21

6.8.0-1019.21

ubuntu/linux-hwe-6.11<6.11.0-26.26~24.04.1

6.11.0-26.26~24.04.1

ubuntu/linux-ibm<6.8.0-1033.33

6.8.0-1033.33

ubuntu/linux-intel*

ubuntu/linux-lowlatency<6.8.0-78.78.1

6.8.0-78.78.1

ubuntu/linux-lowlatency-hwe-6.11<6.11.0-1014.15~24.04.1

6.11.0-1014.15~24.04.1

ubuntu/linux-nvidia<6.8.0-1035.38

6.8.0-1035.38

ubuntu/linux-nvidia-6.11<6.11.0-1010.10

6.11.0-1010.10

ubuntu/linux-nvidia-lowlatency<6.8.0-1035.38.1

6.8.0-1035.38.1

ubuntu/linux-nvidia-tegra<6.8.0-1009.9

6.8.0-1009.9

ubuntu/linux-oem-6.11<6.11.0-1022.22

6.11.0-1022.22

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle<6.8.0-1032.33

6.8.0-1032.33

ubuntu/linux-raspi<6.8.0-1035.39

6.8.0-1035.39

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-xilinx<6.8.0-1017.18

6.8.0-1017.18

ubuntu/linux-raspi-realtime<6.8.0-2028.29

6.8.0-2028.29

ubuntu/linux-realtime<6.8.1-1030.31

6.8.1-1030.31

ubuntu/linux-fips<6.8.0-78.78+fips1

6.8.0-78.78+fips1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.119~20.04.1
Upgrade
Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126~20.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126~20.04.2
Upgrade
Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.122~20.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-186.196~20.04.1
Upgrade
Upgrade ubuntu/linux-ibm-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1106.110~20.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1107.113~20.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-184.194~20.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1064.66~20.04.1
Upgrade
Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1109.115~20.04.1
Upgrade
Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1106.110~20.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.15.0-186.196
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.119
Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1035.37~22.04.1
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1034.39~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.122
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1036.38~22.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 5.15.0-1108.114
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 5.15.0-1095.103
Upgrade
Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-78.78~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.15.0-1106.110
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1033.33~22.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.
Fixed in 5.15.0-1107.113
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.15.0-1104.109
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 5.15.0-184.194
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-78.78.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 5.15.0-1107.108
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1035.38~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 5.15.0-1064.66
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-igx to a version that resolves this vulnerability.
Fixed in 5.15.0-1053.53
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.15.0-1109.115
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1032.33~22.04.1
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.15.0-1106.109
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-78.78~22.04.1
Upgrade
Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.
Fixed in 5.15.0-1075.79
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 5.15.0-1096.98
Upgrade
Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1104.106
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1111.120
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1030.31~22.04.1
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.119+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1117.126+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-186.196+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1112.122+fips1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-78.78
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1035.37
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1034.39
Upgrade
Upgrade ubuntu/linux-azure-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1015.15~24.04.1
Upgrade
Upgrade ubuntu/linux-azure-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1022.23
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1036.38
Upgrade
Upgrade ubuntu/linux-gcp-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1015.15~24.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1032.36
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1019.21
Upgrade
Upgrade ubuntu/linux-hwe-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-26.26~24.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1033.33
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-78.78.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1014.15~24.04.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1035.38
Upgrade
Upgrade ubuntu/linux-nvidia-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1010.10
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1035.38.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 6.8.0-1009.9
Upgrade
Upgrade ubuntu/linux-oem-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1022.22
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1032.33
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1035.39
Upgrade
Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.18
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2028.29
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1030.31
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-78.78+fips1
Configuration
Protect bitmap_get_stats() with bitmap_info.mutex to synchronize access with the bitmap lifetime and prevent dereferencing a destroyed or incompletely initialized bitmap.
Linux kernel md/md-bitmap bitmap_get_stats() synchronization = protected by bitmap_info.mutex

Event History

Feb 27, 2025

CVE Published

via OSV·02:15 AM

Data Sourced

via OSV·02:15 AM

DescriptionSeverityAffected Software

Frequently Asked Questions

What systems are realistically exposed to this issue?

Systems running one of the listed Ubuntu kernel packages may be exposed when they use the Linux MD RAID subsystem and the affected bitmap statistics path is accessed. The fault occurs while the MD device still exists but its bitmap has been destroyed or has not completed initialization.

What does an attacker or triggering condition need to cause the crash?

The triggering condition is access to bitmap statistics through the MD proc/seq reporting path while the bitmap lifetime state is inconsistent. The provided data does not establish that this requires remote access or any particular privilege level.

What is the likely impact if the issue is triggered?

Dereferencing the bitmap after it is destroyed or before it is fully initialized can cause a kernel general protection fault and crash the system. The report describes a panic in bitmap_get_stats() during a proc read.

How can I identify whether a system has encountered this problem?

Look for kernel panic or Oops logs showing a general protection fault in bitmap_get_stats(), with a call trace including md_seq_show, seq_read_iter, proc_reg_read, and vfs_read. This indicates bitmap statistics were read during an invalid bitmap lifetime state.

What change addresses the race?

The resolved fix protects bitmap_get_stats() with bitmap_info.mutex, synchronizing statistics access with the bitmap lifetime. Apply the relevant Ubuntu kernel update for the installed kernel package when available.

UBUNTU-CVE-2025-21712: Ubuntu/linux vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

What systems are realistically exposed to this issue?

What does an attacker or triggering condition need to cause the crash?

What is the likely impact if the issue is triggered?

How can I identify whether a system has encountered this problem?

What change addresses the race?

Company

Resources

Contact

Frequently Asked Questions

What systems are realistically exposed to this issue?

What does an attacker or triggering condition need to cause the crash?

What is the likely impact if the issue is triggered?

How can I identify whether a system has encountered this problem?

What change addresses the race?