UBUNTU-CVE-2025-22089: Null Pointer Dereference

Q: Which systems are exposed to this issue?

Exposure is limited to the listed Ubuntu kernel packages when RDMA hardware counters are accessible from a non-initial network namespace. Systems without RDMA use, or where unprivileged users cannot access such namespaces and counter files, have less practical exposure.

Q: What does an attacker need to do to trigger the failure?

An attacker needs local access with low privileges and must be able to read RDMA hardware counter sysfs attributes from a non-initial network namespace. Reading those counters can dereference a NULL pointer and crash the kernel.

Q: What is the expected impact if exploitation succeeds?

The reported impact is availability loss: the kernel can crash due to a NULL pointer dereference. The supplied vector does not indicate confidentiality or integrity impact.

Q: How can administrators identify possible exposure?

Look for kernel crashes or NULL pointer dereferences in hw_stat_device_show within the ib_core module, particularly after attempts to read RDMA hardware counters from non-initial network namespaces. The provided crash trace identifies this function as the fault location.

Published Apr 16, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Don't expose hwcounters outside of init net namespace Commit 467f432a521a ("RDMA/core: Split port and device counter sysfs attributes") accidentally almost exposed hw counters to non-init net namespaces. It didn't expose them fully, as an attempt to read any of those counters leads to a crash like this one: [42021.807566] BUG: kernel NULL pointer dereference, address: 0000000000000028 [42021.814463] #PF: supervisor read access in kernel mode [42021.819549] #PF: errorcode(0x0000) - not-present page [42021.824636] PGD 0 P4D 0 [42021.827145] Oops: 0000 [#1] SMP PTI [42021.830598] CPU: 82 PID: 2843922 Comm: switchto-defaul Kdump: loaded Tainted: G S W I XXX [42021.841697] Hardware name: XXX [42021.849619] RIP: 0010:hwstatdeviceshow+0x1e/0x40 [ibcore] [42021.855362] Code: 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 49 89 d0 4c 8b 5e 20 48 8b 8f b8 04 00 00 48 81 c7 f0 fa ff ff <48> 8b 41 28 48 29 ce 48 83 c6 d0 48 c1 ee 04 69 d6 ab aa aa aa 48 [42021.873931] RSP: 0018:ffff97fe90f03da0 EFLAGS: 00010287 [42021.879108] RAX: ffff9406988a8c60 RBX: ffff940e1072d438 RCX: 0000000000000000 [42021.886169] RDX: ffff94085f1aa000 RSI: ffff93c6cbbdbcb0 RDI: ffff940c7517aef0 [42021.893230] RBP: ffff97fe90f03e70 R08: ffff94085f1aa000 R09: 0000000000000000 [42021.900294] R10: ffff94085f1aa000 R11: ffffffffc0775680 R12: ffffffff87ca2530 [42021.907355] R13: ffff940651602840 R14: ffff93c6cbbdbcb0 R15: ffff94085f1aa000 [42021.914418] FS: 00007fda1a3b9700(0000) GS:ffff94453fb80000(0000) knlGS:0000000000000000 [42021.922423] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [42021.928130] CR2: 0000000000000028 CR3: 00000042dcfb8003 CR4: 00000000003726f0 [42021.935194] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [42021.942257] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [42021.949324] Call Trace: [42021.951756] <TASK> [42021.953842] [<ffffffff86c58674>] ? showregs+0x64/0x70 [42021.959030] [<ffffffff86c58468>] ? die+0x78/0xc0 [42021.963874] [<ffffffff86c9ef75>] ? pagefaultoops+0x2b5/0x3b0 [42021.969749] [<ffffffff87674b92>] ? excpagefault+0x1a2/0x3c0 [42021.975549] [<ffffffff87801326>] ? asmexcpagefault+0x26/0x30 [42021.981517] [<ffffffffc0775680>] ? pfxshowhwstats+0x10/0x10 [ibcore] [42021.988482] [<ffffffffc077564e>] ? hwstatdeviceshow+0x1e/0x40 [ibcore] [42021.995438] [<ffffffff86ac7f8e>] devattrshow+0x1e/0x50 [42022.000803] [<ffffffff86a3eeb1>] sysfskfseqshow+0x81/0xe0 [42022.006508] [<ffffffff86a11134>] seqreaditer+0xf4/0x410 [42022.011954] [<ffffffff869f4b2e>] vfsread+0x16e/0x2f0 [42022.017058] [<ffffffff869f50ee>] ksysread+0x6e/0xe0 [42022.022073] [<ffffffff8766f1ca>] dosyscall64+0x6a/0xa0 [42022.027441] [<ffffffff8780013b>] entrySYSCALL64afterhwframe+0x78/0xe2 The problem can be reproduced using the following steps: ip netns add foo ip netns exec foo bash cat /sys/class/infiniband/mlx40/hwcounters/ The panic occurs because of casting the device pointer into an ibdevice pointer using containerof() in hwstatdeviceshow() is wrong and leads to a memory corruption. However the real problem is that hw counters should never been exposed outside of the non-init net namespace. Fix this by saving the index of the corresponding attribute group (it might be 1 or 2 depending on the presence of driver-specific attributes) and zeroing the pointer to hwcounters group for compat devices during the initialization. With this fix applied hwcounters are not available in a non-init net namespace: find /sys/class/infiniband/mlx40/ -name hwcounters /sys/class/infiniband/mlx40/ports/1/hwcounters /sys/class/infiniband/mlx40/ports/2/hwcounters /sys/class/infiniband/mlx40/hwcounters ip netns add foo ip netns exec foo bash find /sys/class/infiniband/mlx40/ -name hwcounters

Affected Software

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

5.15.0-1086.93~20.04.1

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

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

5.15.0-1091.100~20.04.1

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

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

5.15.0-1085.94~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-142.152~20.04.1

5.15.0-142.152~20.04.1

ubuntu/linux-hwe-5.8*

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

5.15.0-1078.81~20.04.1

ubuntu/linux-intel-5.13*

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

5.15.0-1083.89~20.04.1

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

5.15.0-142.152~20.04.1

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

5.15.0-1039.39~20.04.1

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

5.15.0-1083.89~20.04.1

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

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

5.15.0-1081.85~20.04.1

ubuntu/linux-riscv-5.8*

ubuntu/linux<5.15.0-142.152

5.15.0-142.152

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws<5.15.0-1086.93

5.15.0-1086.93

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

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

6.8.0-1041.43~22.04.1

ubuntu/linux-azure<5.15.0-1091.100

5.15.0-1091.100

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

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

6.8.0-1041.47~22.04.1

ubuntu/linux-azure-fde<5.15.0-1091.100.1

5.15.0-1091.100.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp<5.15.0-1085.94

5.15.0-1085.94

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

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

6.8.0-1042.45~22.04.1

ubuntu/linux-gke<5.15.0-1083.89

5.15.0-1083.89

ubuntu/linux-gkeop<5.15.0-1068.76

5.15.0-1068.76

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

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

6.8.0-86.87~22.04.1

ubuntu/linux-ibm<5.15.0-1078.81

5.15.0-1078.81

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

6.8.0-1039.39~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-intel-iotg<5.15.0-1081.87

5.15.0-1081.87

ubuntu/linux-kvm<5.15.0-1082.87

5.15.0-1082.87

ubuntu/linux-lowlatency<5.15.0-142.152

5.15.0-142.152

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

6.8.0-86.87.1~22.04.1

ubuntu/linux-nvidia<5.15.0-1080.81

5.15.0-1080.81

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8<6.8.0-1041.44~22.04.2

6.8.0-1041.44~22.04.2

ubuntu/linux-nvidia-tegra<5.15.0-1039.39

5.15.0-1039.39

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

5.15.0-1028.28

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-1083.89

5.15.0-1083.89

ubuntu/linux-oracle-6.5*

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

6.8.0-1038.39~22.04.1

ubuntu/linux-raspi<5.15.0-1080.83

5.15.0-1080.83

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

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

6.8.0-86.87~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-1050.54

5.15.0-1050.54

ubuntu/linux-bluefield<5.15.0-1069.71

5.15.0-1069.71

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

5.15.0-1079.81

ubuntu/linux-realtime<5.15.0-1086.95

5.15.0-1086.95

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

6.8.1-1036.37~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-1086.93+fips1

5.15.0-1086.93+fips1

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

5.15.0-1091.100+fips1

ubuntu/linux-fips<5.15.0-142.152+fips1

5.15.0-142.152+fips1

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

5.15.0-1085.94+fips1

ubuntu/linux<6.8.0-86.87

6.8.0-86.87

ubuntu/linux-aws<6.8.0-1041.43

6.8.0-1041.43

ubuntu/linux-azure<6.8.0-1041.47

6.8.0-1041.47

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

6.11.0-1018.18~24.04.1

ubuntu/linux-azure-nvidia<6.8.0-1029.32

6.8.0-1029.32

ubuntu/linux-gcp<6.8.0-1042.45

6.8.0-1042.45

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

6.11.0-1016.16~24.04.1

ubuntu/linux-gke<6.8.0-1038.43

6.8.0-1038.43

ubuntu/linux-gkeop<6.8.0-1025.28

6.8.0-1025.28

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

6.11.0-28.28~24.04.1

ubuntu/linux-ibm<6.8.0-1039.39

6.8.0-1039.39

ubuntu/linux-intel*

ubuntu/linux-lowlatency<6.8.0-86.87.1

6.8.0-86.87.1

ubuntu/linux-lowlatency-hwe-6.11<6.11.0-1015.16~24.04.2

6.11.0-1015.16~24.04.2

ubuntu/linux-nvidia<6.8.0-1041.44

6.8.0-1041.44

ubuntu/linux-nvidia-6.11<6.11.0-1012.12

6.11.0-1012.12

ubuntu/linux-nvidia-lowlatency<6.8.0-1041.44.1

6.8.0-1041.44.1

ubuntu/linux-nvidia-tegra<6.8.0-1012.12

6.8.0-1012.12

ubuntu/linux-oem-6.11<6.11.0-1024.24

6.11.0-1024.24

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle<6.8.0-1038.39

6.8.0-1038.39

ubuntu/linux-raspi<6.8.0-1041.45

6.8.0-1041.45

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-xilinx<6.8.0-1018.19

6.8.0-1018.19

ubuntu/linux-bluefield<6.8.0-1012.16

6.8.0-1012.16

ubuntu/linux-raspi-realtime<6.8.0-2032.33

6.8.0-2032.33

ubuntu/linux-realtime<6.8.1-1036.37

6.8.1-1036.37

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

6.8.0-1041.43+fips1

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

6.8.0-1044.50+fips1

ubuntu/linux-fips<6.8.0-86.87+fips1

6.8.0-86.87+fips1

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

6.8.0-1042.45+fips1

ubuntu/linux-azure-fde*

ubuntu/linux-vmware*

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-1086.93~20.04.1
Upgrade
Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1091.100~20.04.1
Upgrade
Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1085.94~20.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152~20.04.1
Upgrade
Upgrade ubuntu/linux-ibm-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1078.81~20.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1083.89~20.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152~20.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1039.39~20.04.1
Upgrade
Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1083.89~20.04.1
Upgrade
Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1081.85~20.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.15.0-1086.93
Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.43~22.04.1
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.15.0-1091.100
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.47~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 5.15.0-1091.100.1
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.15.0-1085.94
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1042.45~22.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 5.15.0-1083.89
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 5.15.0-1068.76
Upgrade
Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-86.87~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.15.0-1078.81
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.39~22.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.
Fixed in 5.15.0-1081.87
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.15.0-1082.87
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-86.87.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 5.15.0-1080.81
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.44~22.04.2
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 5.15.0-1039.39
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-igx to a version that resolves this vulnerability.
Fixed in 5.15.0-1028.28
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.15.0-1083.89
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1038.39~22.04.1
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.15.0-1080.83
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-86.87~22.04.1
Upgrade
Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.
Fixed in 5.15.0-1050.54
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 5.15.0-1069.71
Upgrade
Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1079.81
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1086.95
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1036.37~22.04.1
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1086.93+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1091.100+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1085.94+fips1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-86.87
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.43
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.47
Upgrade
Upgrade ubuntu/linux-azure-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1018.18~24.04.1
Upgrade
Upgrade ubuntu/linux-azure-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1029.32
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1042.45
Upgrade
Upgrade ubuntu/linux-gcp-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1016.16~24.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1038.43
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1025.28
Upgrade
Upgrade ubuntu/linux-hwe-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-28.28~24.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.39
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-86.87.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1015.16~24.04.2
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.44
Upgrade
Upgrade ubuntu/linux-nvidia-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1012.12
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.44.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 6.8.0-1012.12
Upgrade
Upgrade ubuntu/linux-oem-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1024.24
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1038.39
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.45
Upgrade
Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.
Fixed in 6.8.0-1018.19
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 6.8.0-1012.16
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2032.33
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1036.37
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1041.43+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1044.50+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-86.87+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1042.45+fips1
Compensating control
During RDMA initialization, save the index of the corresponding attribute group (1 or 2 depending on whether driver-specific attributes are present), zero the hw_counters group pointer for compat devices, and ensure hw_counters are not exposed outside the init network namespace.

Event History

Apr 16, 2025

CVE Published

via OSV·03:16 PM

Data Sourced

via OSV·03:16 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are exposed to this issue?

Exposure is limited to the listed Ubuntu kernel packages when RDMA hardware counters are accessible from a non-initial network namespace. Systems without RDMA use, or where unprivileged users cannot access such namespaces and counter files, have less practical exposure.

What does an attacker need to do to trigger the failure?

An attacker needs local access with low privileges and must be able to read RDMA hardware counter sysfs attributes from a non-initial network namespace. Reading those counters can dereference a NULL pointer and crash the kernel.

What is the expected impact if exploitation succeeds?

The reported impact is availability loss: the kernel can crash due to a NULL pointer dereference. The supplied vector does not indicate confidentiality or integrity impact.

How can administrators identify possible exposure?

Look for kernel crashes or NULL pointer dereferences in hw_stat_device_show within the ib_core module, particularly after attempts to read RDMA hardware counters from non-initial network namespaces. The provided crash trace identifies this function as the fault location.

UBUNTU-CVE-2025-22089: Null Pointer Dereference

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are exposed to this issue?

What does an attacker need to do to trigger the failure?

What is the expected impact if exploitation succeeds?

How can administrators identify possible exposure?

Company

Resources

Contact

Frequently Asked Questions

Which systems are exposed to this issue?

What does an attacker need to do to trigger the failure?

What is the expected impact if exploitation succeeds?

How can administrators identify possible exposure?