<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 06 May 2026 03:43:24 +0000</lastBuildDate>
    <item>
      <title>51bf1634-6f20-474a-a2f7-48ae0072ee8a</title>
      <link>https://vulnerability.circl.lu/sighting/51bf1634-6f20-474a-a2f7-48ae0072ee8a/export</link>
      <description>{"uuid": "51bf1634-6f20-474a-a2f7-48ae0072ee8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-43859", "type": "seen", "source": "https://t.me/cvedetector/3412", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43859 - \"F2FS Linux Kernel FSCrypt NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-43859 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nf2fs: fix to truncate preallocated blocks in f2fs_file_open()  \n  \nchenyuwen reports a f2fs bug as below:  \n  \nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000011  \n fscrypt_set_bio_crypt_ctx+0x78/0x1e8  \n f2fs_grab_read_bio+0x78/0x208  \n f2fs_submit_page_read+0x44/0x154  \n f2fs_get_read_data_page+0x288/0x5f4  \n f2fs_get_lock_data_page+0x60/0x190  \n truncate_partial_data_page+0x108/0x4fc  \n f2fs_do_truncate_blocks+0x344/0x5f0  \n f2fs_truncate_blocks+0x6c/0x134  \n f2fs_truncate+0xd8/0x200  \n f2fs_iget+0x20c/0x5ac  \n do_garbage_collect+0x5d0/0xf6c  \n f2fs_gc+0x22c/0x6a4  \n f2fs_disable_checkpoint+0xc8/0x310  \n f2fs_fill_super+0x14bc/0x1764  \n mount_bdev+0x1b4/0x21c  \n f2fs_mount+0x20/0x30  \n legacy_get_tree+0x50/0xbc  \n vfs_get_tree+0x5c/0x1b0  \n do_new_mount+0x298/0x4cc  \n path_mount+0x33c/0x5fc  \n __arm64_sys_mount+0xcc/0x15c  \n invoke_syscall+0x60/0x150  \n el0_svc_common+0xb8/0xf8  \n do_el0_svc+0x28/0xa0  \n el0_svc+0x24/0x84  \n el0t_64_sync_handler+0x88/0xec  \n  \nIt is because inode.i_crypt_info is not initialized during below path:  \n- mount  \n - f2fs_fill_super  \n  - f2fs_disable_checkpoint  \n   - f2fs_gc  \n    - f2fs_iget  \n     - f2fs_truncate  \n  \nSo, let's relocate truncation of preallocated blocks to f2fs_file_open(),  \nafter fscrypt_file_open(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:01.000000Z"}</description>
      <content:encoded>{"uuid": "51bf1634-6f20-474a-a2f7-48ae0072ee8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-43859", "type": "seen", "source": "https://t.me/cvedetector/3412", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43859 - \"F2FS Linux Kernel FSCrypt NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-43859 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nf2fs: fix to truncate preallocated blocks in f2fs_file_open()  \n  \nchenyuwen reports a f2fs bug as below:  \n  \nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000011  \n fscrypt_set_bio_crypt_ctx+0x78/0x1e8  \n f2fs_grab_read_bio+0x78/0x208  \n f2fs_submit_page_read+0x44/0x154  \n f2fs_get_read_data_page+0x288/0x5f4  \n f2fs_get_lock_data_page+0x60/0x190  \n truncate_partial_data_page+0x108/0x4fc  \n f2fs_do_truncate_blocks+0x344/0x5f0  \n f2fs_truncate_blocks+0x6c/0x134  \n f2fs_truncate+0xd8/0x200  \n f2fs_iget+0x20c/0x5ac  \n do_garbage_collect+0x5d0/0xf6c  \n f2fs_gc+0x22c/0x6a4  \n f2fs_disable_checkpoint+0xc8/0x310  \n f2fs_fill_super+0x14bc/0x1764  \n mount_bdev+0x1b4/0x21c  \n f2fs_mount+0x20/0x30  \n legacy_get_tree+0x50/0xbc  \n vfs_get_tree+0x5c/0x1b0  \n do_new_mount+0x298/0x4cc  \n path_mount+0x33c/0x5fc  \n __arm64_sys_mount+0xcc/0x15c  \n invoke_syscall+0x60/0x150  \n el0_svc_common+0xb8/0xf8  \n do_el0_svc+0x28/0xa0  \n el0_svc+0x24/0x84  \n el0t_64_sync_handler+0x88/0xec  \n  \nIt is because inode.i_crypt_info is not initialized during below path:  \n- mount  \n - f2fs_fill_super  \n  - f2fs_disable_checkpoint  \n   - f2fs_gc  \n    - f2fs_iget  \n     - f2fs_truncate  \n  \nSo, let's relocate truncation of preallocated blocks to f2fs_file_open(),  \nafter fscrypt_file_open(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:01.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/51bf1634-6f20-474a-a2f7-48ae0072ee8a/export</guid>
      <pubDate>Sat, 17 Aug 2024 13:09:01 +0000</pubDate>
    </item>
  </channel>
</rss>
