Description
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.
Published: 2024-07-12
Score: 4.7 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4008-1 linux-6.1 security update
Debian DSA Debian DSA DSA-5730-1 linux security update
Debian DSA Debian DSA DSA-5731-1 linux security update
Ubuntu USN Ubuntu USN USN-6999-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-6999-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7003-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7003-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7003-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7003-4 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7003-5 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7004-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7005-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7005-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7006-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7007-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7007-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7007-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7008-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7009-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7009-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7019-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7029-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7332-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7332-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7332-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7342-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7344-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-7344-2 Linux kernel vulnerabilities
History

Mon, 03 Nov 2025 22:30:00 +0000

Type Values Removed Values Added
References

Wed, 17 Sep 2025 15:15:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

Wed, 06 Nov 2024 08:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 12 Sep 2024 08:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 11 Sep 2024 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-11T20:22:50.641Z

Reserved: 2024-07-12T12:17:45.588Z

Link: CVE-2024-40943

cve-icon Vulnrichment

Updated: 2025-11-03T21:58:12.745Z

cve-icon NVD

Status : Modified

Published: 2024-07-12T13:15:16.670

Modified: 2025-11-03T22:17:16.550

Link: CVE-2024-40943

cve-icon Redhat

Severity : Low

Publid Date: 2024-07-12T00:00:00Z

Links: CVE-2024-40943 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2025-07-12T22:16:20Z

Weaknesses