CVE-2026-43288

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
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:

ext4: move ext4_percpu_param_init() before ext4_mb_init()

When running kvm-xfstests -c ext4/1k -C 1 generic/383 with the DOUBLE_CHECK macro defined, the following panic is triggered:

================================================================== EXT4-fs error (device vdc): ext4_validate_block_bitmap:423: comm mount: bg 0: bad block bitmap checksum BUG: unable to handle page fault for address: ff110000fa2cc000 PGD 3e01067 P4D 3e02067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 2386 Comm: mount Tainted: G W 6.18.0-gba65a4e7120a-dirty #1152 PREEMPT(none) RIP: 0010:percpu_counter_add_batch+0x13/0xa0 Call Trace: ext4_mark_group_bitmap_corrupted+0xcb/0xe0 ext4_validate_block_bitmap+0x2a1/0x2f0 ext4_read_block_bitmap+0x33/0x50 mb_group_bb_bitmap_alloc+0x33/0x80 ext4_mb_add_groupinfo+0x190/0x250 ext4_mb_init_backend+0x87/0x290 ext4_mb_init+0x456/0x640 __ext4_fill_super+0x1072/0x1680 ext4_fill_super+0xd3/0x280 get_tree_bdev_flags+0x132/0x1d0 vfs_get_tree+0x29/0xd0 vfs_cmd_create+0x59/0xe0 __do_sys_fsconfig+0x4f6/0x6b0 do_syscall_64+0x50/0x1f0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ==================================================================

This issue can be reproduced using the following commands: mkfs.ext4 -F -q -b 1024 /dev/sda 5G tune2fs -O quota,project /dev/sda mount /dev/sda /tmp/test

With DOUBLE_CHECK defined, mb_group_bb_bitmap_alloc() reads and validates the block bitmap. When the validation fails, ext4_mark_group_bitmap_corrupted() attempts to update sbi->s_freeclusters_counter. However, this percpu_counter has not been initialized yet at this point, which leads to the panic described above.

Fix this by moving the execution of ext4_percpu_param_init() to occur before ext4_mb_init(), ensuring the per-CPU counters are initialized before they are used.

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

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (5)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

ext4: move ext4_percpu_param_init() before ext4_mb_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: move ext4_percpu_param_init() before ext4_mb_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: move ext4_percpu_param_init() before ext4_mb_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e9fb259bcddf459a0168f4a964e979e500a68a5
generic

ext4: move ext4_percpu_param_init() before ext4_mb_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/270564513489d98b721a1e4a10017978d5213bff
generic

ext4: move ext4_percpu_param_init() before ext4_mb_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d5fcb063cdabb9aeaa8554b7fedad2092c4150e

Vendor Advisories for CVE-2026-43288(1)

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

Patch Availability(13)

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~rc5-1~exp1 (335 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 (113 versions)6.19.6-1

Weakness Classification(1)

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

All Vendor Advisories

(12)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43288?
CVE-2026-43288 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: ext4: move ext4percpuparaminit() before ext4mb_init() When running kvm-xfstests -c ext4/1k -C 1 generic/383 with the DOUBLE_CHECK macro defined, the following panic is triggered:…
When was CVE-2026-43288 disclosed?
CVE-2026-43288 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43288 actively exploited?
CVE-2026-43288 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43288?
CVE-2026-43288 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43288?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43288, 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-43288

Explore →

Is Your Infrastructure Affected by CVE-2026-43288?

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