CVE-2026-43068

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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:

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal()

There's issue as follows: ... EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost

EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost

EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost

EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost

EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 2243 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost

EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 2239 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost

EXT4-fs (mmcblk0p1): error count since last fsck: 1 EXT4-fs (mmcblk0p1): initial error at time 1765597433: ext4_mb_generate_buddy:760 EXT4-fs (mmcblk0p1): last error at time 1765597433: ext4_mb_generate_buddy:760 ...

According to the log analysis, blocks are always requested from the corrupted block group. This may happen as follows: ext4_mb_find_by_goal ext4_mb_load_buddy ext4_mb_load_buddy_gfp ext4_mb_init_cache ext4_read_block_bitmap_nowait ext4_wait_block_bitmap ext4_validate_block_bitmap if (!grp || EXT4_MB_GRP_BBITMAP_CORRUPT(grp)) return -EFSCORRUPTED; // There's no logs. if (err) return err; // Will return error ext4_lock_group(ac->ac_sb, group); if (unlikely(EXT4_MB_GRP_BBITMAP_CORRUPT(e4b->bd_info))) // Unreachable goto out;

After commit 9008a58e5dce ("ext4: make the bitmap read routines return real error codes") merged, Commit 163a203ddb36 ("ext4: mark block group as corrupt on block bitmap error") is no real solution for allocating blocks from corrupted block groups. This is because if 'EXT4_MB_GRP_BBITMAP_CORRUPT(e4b->bd_info)' is true, then 'ext4_mb_load_buddy()' may return an error. This means that the block allocation will fail. Therefore, check block group if corrupted when ext4_mb_load_buddy() returns error.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
1.9%
KEV
Not listed

Published

May 5, 2026

Last Modified

May 20, 2026

References (8)

Vendor Advisories for CVE-2026-43068(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-43068?
CVE-2026-43068 is a medium vulnerability published on May 5, 2026. In the Linux kernel, the following vulnerability has been resolved: ext4: avoid allocate block from corrupted group in ext4mbfindbygoal() There's issue as follows: ... EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs…
When was CVE-2026-43068 disclosed?
CVE-2026-43068 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on May 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43068 actively exploited?
CVE-2026-43068 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43068?
CVE-2026-43068 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43068?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43068, 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-43068

Explore →

Is Your Infrastructure Affected by CVE-2026-43068?

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

Start Free Scan →Browse All CVEs