CVE-2026-43271

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-06. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

md-cluster: fix NULL pointer dereference in process_metadata_update

The function process_metadata_update() blindly dereferences the 'thread' pointer (acquired via rcu_dereference_protected) within the wait_event() macro.

While the code comment states "daemon thread must exist", there is a valid race condition window during the MD array startup sequence (md_run):

  • bitmap_load() is called, which invokes md_cluster_ops->join().
  • join() starts the "cluster_recv" thread (recv_daemon).
  • At this point, recv_daemon is active and processing messages.
  • However, mddev->thread (the main MD thread) is not initialized until
later in md_run().

If a METADATA_UPDATED message is received from a remote node during this specific window, process_metadata_update() will be called while mddev->thread is still NULL, leading to a kernel panic.

To fix this, we must validate the 'thread' pointer. If it is NULL, we release the held lock (no_new_dev_lockres) and return early, safely ignoring the update request as the array is not yet fully ready to process it.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 8, 2026

Advisory Details (5)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

md-cluster: fix NULL pointer dereference in process_metadata_update - kernel/git/stable/linux.git - Linux kernel stable tree

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

md-cluster: fix NULL pointer dereference in process_metadata_update - kernel/git/stable/linux.git - Linux kernel stable tree

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

md-cluster: fix NULL pointer dereference in process_metadata_update - kernel/git/stable/linux.git - Linux kernel stable tree

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

md-cluster: fix NULL pointer dereference in process_metadata_update - kernel/git/stable/linux.git - Linux kernel stable tree

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

md-cluster: fix NULL pointer dereference in process_metadata_update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/721599e837d3f4c0e6cc14da059612c017b6d3ec

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
linuxKernel @ 6.6.128—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
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 (116 versions)6.19.6-1—

Weakness Classification(1)

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

All Vendor Advisories

(12)

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

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

Frequently asked(5)

What is CVE-2026-43271?
CVE-2026-43271 is a medium vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: md-cluster: fix NULL pointer dereference in processmetadataupdate The function processmetadataupdate() blindly dereferences the 'thread' pointer (acquired via rcudereferenceprotected) within the wait_event() macro. While the code…
When was CVE-2026-43271 disclosed?
CVE-2026-43271 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 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-43271 actively exploited?
CVE-2026-43271 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 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43271?
CVE-2026-43271 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43271?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43271, 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-43271

Explore →

Is Your Infrastructure Affected by CVE-2026-43271?

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

Start Free Scan →Browse All CVEs