Vulnerability · Published May 5, 2026 · Assigned by Linux
CVE-2026-43071dcache: Limit the minimal number of bucket to two
Critical 9.1
In plain English
A critical-severity out-of-bounds read in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 40% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: dcache: Limit the minimal number of bucket to two There is an OOB read problem on dentry_hashtable when user sets 'dhash_entries=1': BUG: unable to handle page fault for address: ffff888b30b774b0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP PTI RIP: 0010:__d_lookup+0x56/0x120 Call Trace: d_lookup.cold+0x16/0x5d lookup_dcache+0x27/0xf0 lookup_one_qstr_excl+0x2a/0x180 start_dirop+0x55/0xa0 simple_start_creating+0x8d/0xa0 debugfs_start_creating+0x8c/0x180 debugfs_create_dir+0x1d/0x1c0 pinctrl_init+0x6d/0x140 do_one_initcall+0x6d/0x3d0 kernel_init_freeable+0x39f/0x460 kernel_init+0x2a/0x260 There will be only one bucket in dentry_hashtable when dhash_entries is set as one, and d_hash_shift is calculated as 32 by dcache_init(). Then, following process will access more than one buckets(which memory region is not allocated) in dentry_hashtable: d_lookup b = d_hash(hash) dentry_hashtable + ((u32)hashlen >> d_hash_shift) // The C standard defines the behavior of right shift amounts // exceeding the bit width of the operand as undefined. The // result of '(u32)hashlen >> d_hash_shift' becomes 'hashlen', // so 'b' will point to an unallocated memory region. hlist_bl_for_each_entry_rcu(b) hlist_bl_first_rcu(head) h->first // read OOB! Fix it by limiting the minimal number of dentry_hashtable bucket to two, so that 'd_hash_shift' won't exceeds the bit width of type u32.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.176-1 | DEBIAN-CVE-2026-43071 |
| Debian:13 | linux | 6.12.85-1 | DEBIAN-CVE-2026-43071 |
| Debian:14 | linux | 6.19.14-1 | DEBIAN-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux | 5.15.0-185.195 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux | 5.15.0-185.195 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux | 6.8.0-134.134 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux | 6.17.0-40.40 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux | 6.17.0-40.40 | USN-8490-1 |
| Ubuntu:26.04:LTS | linux | 7.0.0-27.27 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1111.118 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1111.118 | USN-8493-1 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1060.63 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1019.19 | USN-8490-1 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1019.19 | UBUNTU-CVE-2026-43071 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1008.8 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1019.19~24.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1019.19~24.04.1 | USN-8490-1 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1060.63~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1116.125 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1116.125 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1063.71 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1010.10 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1021.21~24.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1063.71~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1116.125 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1062.69 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1009.9 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1062.69~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1111.121 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1111.121 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1063.69 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1020.22 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1020.22 | USN-8490-1 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1007.7 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1020.22~24.04.1 | USN-8490-1 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1020.22~24.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1063.69~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1107.113 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1107.113 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1058.64 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1094.102 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1094.102 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1045.48 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-40.40~24.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-40.40~24.04.1 | USN-8545-1 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-136.136~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-28.28~24.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1105.109 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1105.109 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1060.61 | UBUNTU-CVE-2026-43071 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1009.9 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1060.61~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1106.112 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1106.112 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1103.108 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1103.108 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-183.193 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-183.193 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-134.134.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-134.134.1~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1106.107 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1106.107 | USN-8493-1 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1058.61 | UBUNTU-CVE-2026-43071 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1013.13 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1026.26 | USN-8508-1 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1026.26 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1058.61~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1058.61.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1063.63 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1063.63 | USN-8493-1 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1029.30 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1052.52 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1052.52 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1028.28 | USN-8491-1 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1028.28 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1108.114 | USN-8493-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1108.114 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1057.58 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1018.18 | USN-8490-1 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1018.18 | UBUNTU-CVE-2026-43071 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1007.7 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1018.18~24.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1018.18~24.04.1 | USN-8490-1 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1057.58~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1105.108 | USN-8527-1 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1105.108 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1060.64 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1021.21 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1021.21 | USN-8546-1 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1014.14 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1017.19 | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1017.19 | USN-8490-2 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-27.27.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-40.40.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-27.27.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-134.134~22.04.1 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-vmware | 6.8.0-1008.8 | UBUNTU-CVE-2026-43071 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1032.33 | UBUNTU-CVE-2026-43071 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1074.78 | UBUNTU-CVE-2026-43071 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 99d263d4c5b2f541dfacb5391e22e8c91ea982a6 – before 45b06bb5ea96f75ad81d7ef446f832ea6b0026fe99d263d4c5b2f541dfacb5391e22e8c91ea982a6 – before 426ef05e82ee52c8d0e95fc0808b7383d8352d7399d263d4c5b2f541dfacb5391e22e8c91ea982a6 – before ddd57ebce245f9c7e2f6902a6c087d6186d2385d99d263d4c5b2f541dfacb5391e22e8c91ea982a6 – before 755b40903eff563768d4d96fd4ef51ec48adde3b99d263d4c5b2f541dfacb5391e22e8c91ea982a6 – before 5718df131ab78897a9dd1f2e71c3ba732d4392af99d263d4c5b2f541dfacb5391e22e8c91ea982a6 – before 277cedabb0ab86baae83fa58218be13c6d3e552699d263d4c5b2f541dfacb5391e22e8c91ea982a6 – before f08fe8891c3eeb63b73f9f1f6d97aa629c821579d4c96061fddd129778ce8b70fb093aa532f422d0 |
| Linux | Linux | 3.17 |
Weakness: CWE-125 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
References
- https://git.kernel.org/stable/c/45b06bb5ea96f75ad81d7ef446f832ea6b0026fe
- https://git.kernel.org/stable/c/426ef05e82ee52c8d0e95fc0808b7383d8352d73
- https://git.kernel.org/stable/c/ddd57ebce245f9c7e2f6902a6c087d6186d2385d
- https://git.kernel.org/stable/c/755b40903eff563768d4d96fd4ef51ec48adde3b
- https://git.kernel.org/stable/c/5718df131ab78897a9dd1f2e71c3ba732d4392af
- https://git.kernel.org/stable/c/277cedabb0ab86baae83fa58218be13c6d3e5526
- https://git.kernel.org/stable/c/f08fe8891c3eeb63b73f9f1f6d97aa629c821579
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
- https://cert-portal.siemens.com/productcert/html/ssa-784472.html