CVE-2024-40943

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2024-07-12. NVD baseline CVSS 4.7; sources differ by 0.0.

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

A fix is available — apply it.

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

ocfs2: fix races between hole punching and AIO+DIO

After commit "ocfs2: return real error code in ocfs2_dio_wr_get_block", fstests/generic/300 become from always failed to sometimes failed:

======================================================================== [ 473.293420 ] run fstests generic/300

[ 475.296983 ] JBD2: Ignoring recovery information on journal [ 475.302473 ] ocfs2: Mounting device (253,1) on (node local, slot 0) with ordered data mode. [ 494.290998 ] OCFS2: ERROR (device dm-1): ocfs2_change_extent_flag: Owner 5668 has an extent at cpos 78723 which can no longer be found [ 494.291609 ] On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. [ 494.292018 ] OCFS2: File system is now read-only. [ 494.292224 ] (kworker/19:11,2628,19):ocfs2_mark_extent_written:5272 ERROR: status = -30 [ 494.292602 ] (kworker/19:11,2628,19):ocfs2_dio_end_io_write:2374 ERROR: status = -3 fio: io_u error on file /mnt/scratch/racer: Read-only file system: write offset=460849152, buflen=131072 =========================================================================

In __blockdev_direct_IO, ocfs2_dio_wr_get_block is called to add unwritten extents to a list. extents are also inserted into extent tree in ocfs2_write_begin_nolock. Then another thread call fallocate to puch a hole at one of the unwritten extent. The extent at cpos was removed by ocfs2_remove_extent(). At end io worker thread, ocfs2_search_extent_list found there is no such extent at the cpos.

T1 T2 T3 inode lock ... insert extents ... inode unlock ocfs2_fallocate __ocfs2_change_file_space inode lock lock ip_alloc_sem ocfs2_remove_inode_range inode ocfs2_remove_btree_range ocfs2_remove_extent ^---remove the extent at cpos 78723 ... unlock ip_alloc_sem inode unlock ocfs2_dio_end_io ocfs2_dio_end_io_write lock ip_alloc_sem ocfs2_mark_extent_written ocfs2_change_extent_flag ocfs2_search_extent_list ^---failed to find extent ... unlock ip_alloc_sem

In most filesystems, fallocate is not compatible with racing with AIO+DIO, so fix it by adding to wait for all dio before fallocate/punch_hole like ext4.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/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
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
8.4%
KEV
Not listed

Published

July 12, 2024

Last Modified

November 3, 2025

References (17)

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-44.44) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.195.193) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.195.215~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1051 (5.4.0-1051.55) @ focal2026-05-23ubuntu
ubuntulinux-tools-azure (6.8.0-1014.16) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.121.121) @ jammy2026-05-23ubuntu
ubuntulinux-tools-iot (5.4.0.1043.41) @ focal2026-05-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1013.14.1) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1072.81~20.04.1.49) @ focal2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1011.12) @ noble2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-45.45~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1072.70) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1116.146) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1067.73~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.121.110) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1116.128~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-44.44.1~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1013.14~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.266.272) @ xenial2026-05-23ubuntu
ubuntulinux-tools-oracle (4.15.0.1140.151~16.04.1) @ xenial2026-05-23ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.235.247~16.04.1) @ xenial2026-05-23ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.266.300~14.04.1) @ trusty2026-05-23ubuntu
ubuntulinux-tools-kvm (4.4.0.1142.139) @ xenial2026-05-23ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1186.201~16.04.1) @ xenial2026-05-23ubuntu
linuxKernel @ 4.19.317—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.

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

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

Frequently asked(5)

What is CVE-2024-40943?
CVE-2024-40943 is a medium vulnerability published on July 12, 2024. In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix races between hole punching and AIO+DIO After commit "ocfs2: return real error code in ocfs2diowrgetblock", fstests/generic/300 become from always failed to sometimes failed:…
When was CVE-2024-40943 disclosed?
CVE-2024-40943 was first published in the National Vulnerability Database on July 12, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-40943 actively exploited?
CVE-2024-40943 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-40943?
CVE-2024-40943 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2024-40943?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-40943, 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-2024-40943

Explore →

Is Your Infrastructure Affected by CVE-2024-40943?

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

Start Free Scan →Browse All CVEs