Review reviewCritical

CVE-2026-43071

Linux Linux, linux kernel

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 debug...

CVSS
9.1
EPSS
0.39%
31.7% percentile
CISA KEV
Not listed
Published
2026.05.06
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.39%
Technical severityCVSS 9.1

Vulnerability overview

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 debug...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 99d263d4c5b2f541dfacb5391e22e8c91ea982a6 < 45b06bb5ea96f75ad81d7ef446f832ea6b0026fe, >= 99d263d4c5b2f541dfacb5391e22e8c91ea982a6 < 426ef05e82ee52c8d0e95fc0808b7383d8352d73, >= 99d263d4c5b2f541dfacb5391e22e8c91ea982a6 < ddd57ebce245f9c7e2f6902a6c087d6186d2385d, >= 99d263d4c5b2f541dfacb5391e22e8c91ea982a6 < 755b40903eff563768d4d96fd4ef51ec48adde3b, >= 99d263d4c5b2f541dfacb5391e22e8c91ea982a6 < 5718df131ab78897a9dd1f2e71c3ba732d4392af, >= 99d263d4c5b2f541dfacb5391e22e8c91ea982a6 < 277cedabb0ab86baae83fa58218be13c6d3e5526, >= 99d263d4c5b2f541dfacb5391e22e8c91ea982a6 < f08fe8891c3eeb63b73f9f1f6d97aa629c821579, >= d4c96061fddd129778ce8b70fb093aa532f422d0, >= be2378cbffe50ce0161f0fdee914adee98af53dc, >= a8be8af18485f9fade90e1743d940252a39eec84, >= b5cf3193759f7cd1cfbeef11f5cf067bbce22e55, >= 3.10.55 < 3.11, >= 3.12.29 < 3.13, >= 3.14.19 < 3.15, >= 3.16.3 < 3.17, >= 3.17, >= 3.17.1 < 6.1.175, >= 6.2 < 6.6.136, >= 6.7 < 6.12.83, >= 6.13 < 6.18.24
Fixed versions
3.11, 3.13, 3.15, 3.17, 6.1.175, 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CWE
CWE-125