🛡️ UBUNTU-CVE-2025-22089
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Don't expose hw_counters 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: error_code(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:hw_stat_device_show+0x1e/0x40 [ib_core] [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 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] [42021.953842] [] ? show_regs+0x64/0x70 [42021.959030] [] ? __die+0x78/0xc0 [42021.963874] [] ? page_fault_oops+0x2b5/0x3b0 [42021.969749] [] ? exc_page_fault+0x1a2/0x3c0 [42021.975549] [] ? asm_exc_page_fault+0x26/0x30 [42021.981517] [] ? __pfx_show_hw_stats+0x10/0x10 [ib_core] [42021.988482] [] ? hw_stat_device_show+0x1e/0x40 [ib_core] [42021.995438] [] dev_attr_show+0x1e/0x50 [42022.000803] [] sysfs_kf_seq_show+0x81/0xe0 [42022.006508] [] seq_read_iter+0xf4/0x410 [42022.011954] [] vfs_read+0x16e/0x2f0 [42022.017058] [] ksys_read+0x6e/0xe0 [42022.022073] [] do_syscall_64+0x6a/0xa0 [42022.027441] [] entry_SYSCALL_64_after_hwframe+0x78/0xe2 The problem can be reproduced using the following steps: ip netns add foo ip netns exec foo bash cat /sys/class/infiniband/mlx4_0/hw_counters/* The panic occurs because of casting the device pointer into an ib_device pointer using container_of() in hw_stat_device_show() 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 hw_counters group for compat devices during the initialization. With this fix applied hw_counters are not available in a non-init net namespace: find /sys/class/infiniband/mlx4_0/ -name hw_counters /sys/class/infiniband/mlx4_0/ports/1/hw_counters /sys/class/infiniband/mlx4_0/ports/2/hw_counters /sys/class/infiniband/mlx4_0/hw_counters ip netns add foo ip netns exec foo bash find /sys/class/infiniband/mlx4_0/ -name hw_counters

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-04-16
Updated 2026-06-15
Modified 2026-06-08
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 6.8.0-86.87
linux-allwinner-5.19
linux-aws 6.8.0-1041.43
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1086.93~20.04.1
linux-aws-5.19
linux-aws-5.3
linux-aws-5.8
linux-aws-6.2
linux-aws-6.5
linux-aws-6.8 6.8.0-1041.43~22.04.1
linux-aws-fips 6.8.0-1041.43+fips1
linux-azure 6.8.0-1041.47
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1091.100~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.8
linux-azure-6.11 6.11.0-1018.18~24.04.1
linux-azure-6.2
linux-azure-6.5
linux-azure-6.8 6.8.0-1041.47~22.04.1
linux-azure-edge
linux-azure-fde
linux-azure-fde-5.19
linux-azure-fde-6.17
linux-azure-fde-6.2
linux-azure-fips 6.8.0-1044.50+fips1
linux-azure-nvidia 6.8.0-1029.32
linux-bluefield
linux-fips 6.8.0-86.87+fips1
linux-gcp 6.8.0-1042.45
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1085.94~20.04.1
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.8
linux-gcp-6.11 6.11.0-1016.16~24.04.1
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-6.8 6.8.0-1042.45~22.04.1
linux-gcp-fips 6.8.0-1042.45+fips1
linux-gke 6.8.0-1038.43
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 6.8.0-1025.28
linux-gkeop-5.15
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-142.152~20.04.1
linux-hwe-5.19
linux-hwe-5.8
linux-hwe-6.11 6.11.0-28.28~24.04.1
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-6.8 6.8.0-86.87~22.04.1
linux-hwe-edge
linux-ibm 6.8.0-1039.39
linux-ibm-5.15 5.15.0-1078.81~20.04.1
linux-ibm-6.8 6.8.0-1039.39~22.04.1
linux-intel
linux-intel-5.13
linux-intel-iot-realtime 5.15.0-1079.81
linux-intel-iotg 5.15.0-1081.87
linux-intel-iotg-5.15 5.15.0-1083.89~20.04.1
linux-kvm 5.15.0-1082.87
linux-lowlatency 6.8.0-86.87.1
linux-lowlatency-hwe-5.15 5.15.0-142.152~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.11 6.11.0-1015.16~24.04.2
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lowlatency-hwe-6.8 6.8.0-86.87.1~22.04.1
linux-nvidia 6.8.0-1041.44
linux-nvidia-6.11 6.11.0-1012.12
linux-nvidia-6.2
linux-nvidia-6.5
linux-nvidia-6.8 6.8.0-1041.44~22.04.2
linux-nvidia-lowlatency 6.8.0-1041.44.1
linux-nvidia-tegra 6.8.0-1012.12
linux-nvidia-tegra-5.15 5.15.0-1039.39~20.04.1
linux-nvidia-tegra-igx 5.15.0-1028.28
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.11 6.11.0-1024.24
linux-oem-6.5
linux-oem-6.8
linux-oracle 6.8.0-1038.39
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1083.89~20.04.1
linux-oracle-5.3
linux-oracle-5.8
linux-oracle-6.5
linux-oracle-6.8 6.8.0-1038.39~22.04.1
linux-raspi 6.8.0-1041.45
linux-raspi-realtime 6.8.0-2032.33
linux-raspi2
linux-realtime 6.8.1-1036.37
linux-realtime-6.8 6.8.1-1036.37~22.04.1
linux-riscv
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1081.85~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.5
linux-riscv-6.8 6.8.0-86.87~22.04.1
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5
linux-xilinx 6.8.0-1018.19
linux-xilinx-zynqmp 5.15.0-1050.54

References

Similar Threats

Site Security Check

Concerned your site may already be targeted?

BotEraser analyzes incoming traffic patterns and helps identify bot behavior consistent with known exploit attempts.

Check My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.