CVE-2026-43071

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-05. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

May 5, 2026

Last Modified

September 8, 2026

Advisory Details (7)

Auto-updated Sep 7, 2026
No patch confirmed yet.
generic

dcache: Limit the minimal number of bucket to two - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f08fe8891c3eeb63b73f9f1f6d97aa629c821579
generic

dcache: Limit the minimal number of bucket to two - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/277cedabb0ab86baae83fa58218be13c6d3e5526
generic

dcache: Limit the minimal number of bucket to two - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5718df131ab78897a9dd1f2e71c3ba732d4392af
generic

dcache: Limit the minimal number of bucket to two - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/755b40903eff563768d4d96fd4ef51ec48adde3b
generic

dcache: Limit the minimal number of bucket to two - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ddd57ebce245f9c7e2f6902a6c087d6186d2385d
generic

dcache: Limit the minimal number of bucket to two - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/426ef05e82ee52c8d0e95fc0808b7383d8352d73
generic

dcache: Limit the minimal number of bucket to two - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45b06bb5ea96f75ad81d7ef446f832ea6b0026fe

Vendor Advisories for CVE-2026-43071(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-09-08ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-09-08ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-09-08ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.185.166) @ jammy2026-09-08ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-09-08ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1108.114~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-09-08ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-08ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-08ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1017.19) @ questing2026-09-08ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1167.173~18.04.1) @ bionic2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1080 (5.4.0-1080.84) @ focal2026-09-08ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.257.269~16.04.1) @ xenial2026-09-08ubuntu
ubuntulinux-tools-azure (4.15.0.1206.221~14.04.1) @ trusty2026-09-08ubuntu
ubuntulinux-tools-gcp-fips-5.4 (5.4.0.1165.107) @ focal2026-09-08ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1161.171~18.04.1) @ bionic2026-09-08ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.287.293) @ xenial2026-09-08ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-08ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-08ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1105.103) @ jammy2026-09-08ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-09-08ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1106.112~20.04.1) @ focal2026-09-08ubuntu
linuxKernel @ 6.1.175—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (129 versions)6.19.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 339 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-08 09:46 UTCEG score recompute
  8. 2026-09-08 09:46 UTCGHSA enrichment
  9. 2026-09-08 09:02 UTCEG score recompute
  10. 2026-09-08 09:02 UTCVendor advisory
  11. 2026-09-08 09:02 UTCGHSA enrichment
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-23 20:55 UTCEG score recompute
  24. 2026-08-23 20:55 UTCVendor advisory
  25. 2026-08-23 20:54 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 13:03 UTCEG score recompute
  8. 2026-08-17 13:03 UTCVendor advisory
  9. 2026-08-17 13:02 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 09:14 UTCVendor advisory
  12. 2026-08-16 09:14 UTCGHSA enrichment
  13. 2026-08-16 04:59 UTCEG score recompute
  14. 2026-08-16 04:59 UTCVendor advisory
  15. 2026-08-16 04:59 UTCGHSA enrichment
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 02:19 UTCEG score recompute
  18. 2026-08-15 02:19 UTCVendor advisory
  19. 2026-08-15 02:19 UTCGHSA enrichment
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 22:32 UTCVendor advisory
  22. 2026-08-14 22:32 UTCGHSA enrichment
  23. 2026-08-14 18:44 UTCVendor advisory
  24. 2026-08-14 18:44 UTCGHSA enrichment
  25. 2026-08-14 14:57 UTCVendor advisory
  26. 2026-08-14 14:57 UTCGHSA enrichment
  27. 2026-08-14 11:09 UTCVendor advisory
  28. 2026-08-14 11:09 UTCGHSA enrichment
  29. 2026-08-14 07:22 UTCVendor advisory
  30. 2026-08-14 07:22 UTCGHSA enrichment
  31. 2026-08-14 03:34 UTCEG score recompute
  32. 2026-08-14 03:34 UTCVendor advisory
  33. 2026-08-14 03:34 UTCGHSA enrichment
  34. 2026-08-13 22:00 UTCEPSS rescore
  35. 2026-08-13 08:22 UTCVendor advisory
  36. 2026-08-13 08:22 UTCGHSA enrichment
  37. 2026-08-13 04:34 UTCVendor advisory
  38. 2026-08-13 04:34 UTCGHSA enrichment
  39. 2026-08-13 00:47 UTCVendor advisory
  40. 2026-08-13 00:47 UTCGHSA enrichment
  41. 2026-08-12 20:59 UTCVendor advisory
  42. 2026-08-12 20:59 UTCGHSA enrichment
  43. 2026-08-12 17:12 UTCEG score recompute
  44. 2026-08-12 17:12 UTCVendor advisory
  45. 2026-08-12 17:11 UTCGHSA enrichment
  46. 2026-08-12 13:51 UTCEPSS rescore
  47. 2026-08-11 23:37 UTCVendor advisory
  48. 2026-08-11 23:37 UTCGHSA enrichment
  49. 2026-08-11 19:50 UTCVendor advisory
  50. 2026-08-11 19:50 UTCGHSA enrichment
  51. 2026-08-11 16:03 UTCEG score recompute
  52. 2026-08-11 16:03 UTCVendor advisory
  53. 2026-08-11 16:03 UTCGHSA enrichment
  54. 2026-08-11 13:43 UTCEPSS rescore
  55. 2026-08-11 09:12 UTCVendor advisory
  56. 2026-08-11 09:12 UTCGHSA enrichment
  57. 2026-08-11 05:24 UTCVendor advisory
  58. 2026-08-11 05:24 UTCGHSA enrichment
  59. 2026-08-11 01:36 UTCEG score recompute
  60. 2026-08-11 01:36 UTCVendor advisory
  61. 2026-08-11 01:36 UTCGHSA enrichment
  62. 2026-08-11 00:00 UTCEPSS rescore
  63. 2026-08-10 13:04 UTCVendor advisory
  64. 2026-08-10 13:04 UTCGHSA enrichment
  65. 2026-08-10 09:16 UTCVendor advisory
  66. 2026-08-10 09:16 UTCGHSA enrichment
  67. 2026-08-10 05:28 UTCVendor advisory
  68. 2026-08-10 05:28 UTCGHSA enrichment
  69. 2026-08-10 01:41 UTCVendor advisory
  70. 2026-08-10 01:41 UTCGHSA enrichment
  71. 2026-08-09 21:53 UTCVendor advisory
  72. 2026-08-09 21:53 UTCGHSA enrichment
  73. 2026-08-09 18:06 UTCVendor advisory
  74. 2026-08-09 18:06 UTCGHSA enrichment
  75. 2026-08-09 14:18 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43071?
CVE-2026-43071 is a critical vulnerability published on May 5, 2026. 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…
When was CVE-2026-43071 disclosed?
CVE-2026-43071 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43071 actively exploited?
CVE-2026-43071 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.5% of all scored CVEs.
What is the CVSS score of CVE-2026-43071?
CVE-2026-43071 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-43071?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43071, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43071

Explore →

Is Your Infrastructure Affected by CVE-2026-43071?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs