CVE-2026-43071

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-05. the CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
32%
KEV
Not listed

Published

May 5, 2026

Last Modified

June 14, 2026

Advisory Details (6)

Auto-updated May 9, 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/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/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/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/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/277cedabb0ab86baae83fa58218be13c6d3e5526

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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 29× 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 161 total refreshes for this CVE.

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

Related CVEs(same product + 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 June 14, 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 68.4% of all scored CVEs.
What is the CVSS score of CVE-2026-43071?
CVE-2026-43071 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
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

Explore the affected products and dependency analysis for 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