CVE-2024-40943

一、漏洞信息
 漏洞编号：[CVE-2024-40943](https://nvd.nist.gov/vuln/detail/CVE-2024-40943)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0
 CVSS V2.0分值：
  BaseScore：0.0 Medium
  Vector：CVSS：2.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:ocfs2: fix races between hole punching and AIO+DIOAfter 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 = -3fio: 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 unwrittenextents to a list.  extents are also inserted into extent tree inocfs2_write_begin_nolock.  Then another thread call fallocate to puch ahole at one of the unwritten extent.  The extent at cpos was removed byocfs2_remove_extent().  At end io worker thread, ocfs2_search_extent_listfound there is no such extent at the cpos.    T1                        T2                T3                              inode lock                                ...                                insert extents                                ...                              inode unlockocfs2_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_semIn 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 likeext4.
 漏洞公开时间：2024-07-12 21:15:16
 漏洞创建时间：2024-07-15 14:15:33
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-40943
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/050ce8af6838c71e872e982b50d3f1bec21da40e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/117b9c009b72a6c2ebfd23484354dfee2d9570d2 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/38825ff9da91d2854dcf6d9ac320a7e641e10f25 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3c26b5d21b1239e9c7fd31ba7d9b2d7bdbaa68d9 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3c361f313d696df72f9bccf058510e9ec737b9b1 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/952b023f06a24b2ad6ba67304c4c84d45bea2f18 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e8e2db1adac47970a6a9225f3858e9aa0e86287f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ea042dc2bea19d72e37c298bf65a9c341ef3fff3 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-40943 | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-40943 | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/stable/c/050ce8af6838c71e872e982b50d3f1bec21da40e | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/stable/c/117b9c009b72a6c2ebfd23484354dfee2d9570d2 | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/stable/c/38825ff9da91d2854dcf6d9ac320a7e641e10f25 | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/stable/c/3c26b5d21b1239e9c7fd31ba7d9b2d7bdbaa68d9 | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/stable/c/3c361f313d696df72f9bccf058510e9ec737b9b1 | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/stable/c/952b023f06a24b2ad6ba67304c4c84d45bea2f18 | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/stable/c/e8e2db1adac47970a6a9225f3858e9aa0e86287f | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/stable/c/ea042dc2bea19d72e37c298bf65a9c341ef3fff3 | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-40943.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1227849 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-40943 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/linus/952b023f06a24b2ad6ba67304c4c84d45bea2f18 (6.10-rc1) | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/stable/c/3c26b5d21b1239e9c7fd31ba7d9b2d7bdbaa68d9 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/stable/c/e8e2db1adac47970a6a9225f3858e9aa0e86287f | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/stable/c/050ce8af6838c71e872e982b50d3f1bec21da40e | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/stable/c/38825ff9da91d2854dcf6d9ac320a7e641e10f25 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/stable/c/ea042dc2bea19d72e37c298bf65a9c341ef3fff3 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/stable/c/3c361f313d696df72f9bccf058510e9ec737b9b1 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/stable/c/117b9c009b72a6c2ebfd23484354dfee2d9570d2 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://git.kernel.org/stable/c/952b023f06a24b2ad6ba67304c4c84d45bea2f18 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-40943 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-40943 | https://ubuntu.com/security/CVE-2024-40943 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-40943 | https://ubuntu.com/security/CVE-2024-40943 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-40943 |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux |  | https://git.kernel.org/linus/952b023f06a24b2ad6ba67304c4c84d45bea2f18 | https://git.kernel.org/linus/b25801038da5823bba1b5440a57ca68afc51b6bd | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
        In the Linux kernel, the following vulnerability has been resolved:ocfs2: fix races between hole punching and AIO+DIOAfter commit &#34;ocfs2: return real error code in ocfs2_dio_wr_get_block&#34;,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 = -3fio: 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 unwrittenextents to a list.  extents are also inserted into extent tree inocfs2_write_begin_nolock.  Then another thread call fallocate to puch ahole at one of the unwritten extent.  The extent at cpos was removed byocfs2_remove_extent().  At end io worker thread, ocfs2_search_extent_listfound there is no such extent at the cpos.    T1                        T2                T3                              inode lock                                ...                                insert extents                                ...                              inode unlockocfs2_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_semIn 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 likeext4.The Linux kernel CVE team has assigned CVE-2024-40943 to this issue.   
 openEuler评分：
  5.5
 Vector：CVSS：2.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP1(5.10.0):受影响
3.openEuler-22.03-LTS-SP3(5.10.0):受影响
4.openEuler-24.03-LTS(6.6.0):受影响
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响
6.master(6.1.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP1(5.10.0):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.master(6.1.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-22.03-LTS-SP4(5.10.0):否

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1897

src-openEuler/kernel

内容风险标识

评论 (17)

src-openEuler/kernel .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2024-40943

评论 (17)

搜索帮助

src-openEuler/kernel