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.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: 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)
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 5, 2026

Last Modified

May 20, 2026

Advisory Details (8)

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

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9370207b36d26e45a8c8ef0500706d37036edd6b
generic

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46066e3a06647c5b186cc6334409722622d05c44
generic

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d31a5073f86a177edf44015e0dedb0c47cfd6d8
generic

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c0d7c4cde38a887c6d74e0c89ddb25226943c78
generic

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1895f7904be71c48f1e6f338b28f24dabd6b8aeb
generic

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() - kernel/git/stable/linux.git - Linux kernel stable tree

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

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.

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1059.62~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-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-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1107.113~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
linuxKernel @ 5.10.253—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 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
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 (121 versions)6.19.11-1—

Weakness Classification(1)

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

All Vendor Advisories

(25)

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 4× in last 7d / 51× 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 156 total refreshes for this CVE.

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

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

See which npm, PyPI, Go, and Maven packages are affected by 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