{"vulnerability": "cve-2024-4494", "sightings": [{"uuid": "7a10bdbb-acff-47f6-a1b9-55ad8a99b867", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-44941", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "dbb91606-23c8-4c07-acc3-49f3a56fa06e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44949", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}, {"uuid": "b327fa58-71bc-4809-b50e-870fd7810a9d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44944", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}, {"uuid": "c83cbb24-94de-438f-b0cf-5868b854f0a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-44940", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "b3935449-103d-45c8-8553-7ee7043ce583", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-44942", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "32c0f38b-b2b7-4630-8a12-f839d857287b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-44949", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "e6c29476-1d6f-4150-b65c-be5529aa027c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44943", "type": "seen", "source": "https://t.me/cvedetector/4320", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44943 - KVM AMD Try Grab Folio Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-44943 \nPublished : Aug. 28, 2024, 8:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmm: gup: stop abusing try_grab_folio  \n  \nA kernel warning was reported when pinning folio in CMA memory when  \nlaunching SEV virtual machine.  The splat looks like:  \n  \n[  464.325306] WARNING: CPU: 13 PID: 6734 at mm/gup.c:1313 __get_user_pages+0x423/0x520  \n[  464.325464] CPU: 13 PID: 6734 Comm: qemu-kvm Kdump: loaded Not tainted 6.6.33+ #6  \n[  464.325477] RIP: 0010:__get_user_pages+0x423/0x520  \n[  464.325515] Call Trace:  \n[  464.325520]    \n[  464.325523]  ? __get_user_pages+0x423/0x520  \n[  464.325528]  ? __warn+0x81/0x130  \n[  464.325536]  ? __get_user_pages+0x423/0x520  \n[  464.325541]  ? report_bug+0x171/0x1a0  \n[  464.325549]  ? handle_bug+0x3c/0x70  \n[  464.325554]  ? exc_invalid_op+0x17/0x70  \n[  464.325558]  ? asm_exc_invalid_op+0x1a/0x20  \n[  464.325567]  ? __get_user_pages+0x423/0x520  \n[  464.325575]  __gup_longterm_locked+0x212/0x7a0  \n[  464.325583]  internal_get_user_pages_fast+0xfb/0x190  \n[  464.325590]  pin_user_pages_fast+0x47/0x60  \n[  464.325598]  sev_pin_memory+0xca/0x170 [kvm_amd]  \n[  464.325616]  sev_mem_enc_register_region+0x81/0x130 [kvm_amd]  \n  \nPer the analysis done by yangge, when starting the SEV virtual machine, it  \nwill call pin_user_pages_fast(..., FOLL_LONGTERM, ...) to pin the memory.   \nBut the page is in CMA area, so fast GUP will fail then fallback to the  \nslow path due to the longterm pinnalbe check in try_grab_folio().  \n  \nThe slow path will try to pin the pages then migrate them out of CMA area.  \nBut the slow path also uses try_grab_folio() to pin the page, it will  \nalso fail due to the same check then the above warning is triggered.  \n  \nIn addition, the try_grab_folio() is supposed to be used in fast path and  \nit elevates folio refcount by using add ref unless zero.  We are guaranteed  \nto have at least one stable reference in slow path, so the simple atomic add  \ncould be used.  The performance difference should be trivial, but the  \nmisuse may be confusing and misleading.  \n  \nRedefined try_grab_folio() to try_grab_folio_fast(), and try_grab_page()  \nto try_grab_folio(), and use them in the proper paths.  This solves both  \nthe abuse and the kernel warning.  \n  \nThe proper naming makes their usecase more clear and should prevent from  \nabusing in the future.  \n  \npeterx said:  \n  \n: The user will see the pin fails, for gpu-slow it further triggers the WARN  \n: right below that failure (as in the original report):  \n:   \n:         folio = try_grab_folio(page, page_increm - 1,  \n:                                 foll_flags);  \n:         if (WARN_ON_ONCE(!folio)) { Severity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-28T10:57:17.000000Z"}, {"uuid": "806c89b5-f401-42a3-add4-03e593f0de08", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44944", "type": "seen", "source": "https://t.me/cvedetector/4509", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44944 - Netfilter Ctnetlink Expectation ID Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-44944 \nPublished : Aug. 30, 2024, 8:15 a.m. | 23\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnetfilter: ctnetlink: use helper function to calculate expect ID \n \nDelete expectation path is missing a call to the nf_expect_get_id() \nhelper function to calculate the expectation ID, otherwise LSB of the \nexpectation object address is leaked to userspace. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"30 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-30T10:38:13.000000Z"}, {"uuid": "4731c0c2-1601-4ead-b135-2ee8e1f47b38", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44945", "type": "seen", "source": "https://t.me/cvedetector/4565", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44945 - Netfilter Linux Kernel Initialization Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-44945 \nPublished : Aug. 31, 2024, 7:15 a.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: nfnetlink: Initialise extack before use in ACKs  \n  \nAdd missing extack initialisation when ACKing BATCH_BEGIN and BATCH_END. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"31 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-31T10:02:33.000000Z"}, {"uuid": "935c5d80-21d3-469d-bb51-efe457ba581e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44947", "type": "seen", "source": "https://t.me/cvedetector/4648", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44947 - FUSE Linux Kernel Uninitialized Information Leak\", \n  \"Content\": \"CVE ID : CVE-2024-44947 \nPublished : Sept. 2, 2024, 6:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfuse: Initialize beyond-EOF page contents before setting uptodate  \n  \nfuse_notify_store(), unlike fuse_do_readpage(), does not enable page  \nzeroing (because it can be used to change partial page contents).  \n  \nSo fuse_notify_store() must be more careful to fully initialize page  \ncontents (including parts of the page that are beyond end-of-file)  \nbefore marking the page uptodate.  \n  \nThe current code can leave beyond-EOF page contents uninitialized, which  \nmakes these uninitialized page contents visible to userspace via mmap().  \n  \nThis is an information leak, but only affects systems which do not  \nenable init-on-alloc (via CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y or the  \ncorresponding kernel command line parameter). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-02T21:24:20.000000Z"}, {"uuid": "38b2aec7-ac8c-4199-9787-e83212d5bb96", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44946", "type": "seen", "source": "https://t.me/cvedetector/4577", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44946 - Linux KCM kcm_sendmsg() UAF\", \n  \"Content\": \"CVE ID : CVE-2024-44946 \nPublished : Aug. 31, 2024, 2:15 p.m. | 25\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nkcm: Serialise kcm_sendmsg() for the same socket.  \n  \nsyzkaller reported UAF in kcm_release(). [0]  \n  \nThe scenario is  \n  \n  1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb.  \n  \n  2. Thread A resumes building skb from kcm->seq_skb but is blocked  \n     by sk_stream_wait_memory()  \n  \n  3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb  \n     and puts the skb to the write queue  \n  \n  4. Thread A faces an error and finally frees skb that is already in the  \n     write queue  \n  \n  5. kcm_release() does double-free the skb in the write queue  \n  \nWhen a thread is building a MSG_MORE skb, another thread must not touch it.  \n  \nLet's add a per-sk mutex and serialise kcm_sendmsg().  \n  \n[0]:  \nBUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline]  \nBUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline]  \nBUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline]  \nBUG: KASAN: slab-use-after-free in __skb_queue_purge include/linux/skbuff.h:3181 [inline]  \nBUG: KASAN: slab-use-after-free in kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691  \nRead of size 8 at addr ffff0000ced0fc80 by task syz-executor329/6167  \n  \nCPU: 1 PID: 6167 Comm: syz-executor329 Tainted: G    B              6.8.0-rc5-syzkaller-g9abbc24128bc #0  \nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024  \nCall trace:  \n dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291  \n show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298  \n __dump_stack lib/dump_stack.c:88 [inline]  \n dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106  \n print_address_description mm/kasan/report.c:377 [inline]  \n print_report+0x178/0x518 mm/kasan/report.c:488  \n kasan_report+0xd8/0x138 mm/kasan/report.c:601  \n __asan_report_load8_noabort+0x20/0x2c mm/kasan/report_generic.c:381  \n __skb_unlink include/linux/skbuff.h:2366 [inline]  \n __skb_dequeue include/linux/skbuff.h:2385 [inline]  \n __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline]  \n __skb_queue_purge include/linux/skbuff.h:3181 [inline]  \n kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691  \n __sock_release net/socket.c:659 [inline]  \n sock_close+0xa4/0x1e8 net/socket.c:1421  \n __fput+0x30c/0x738 fs/file_table.c:376  \n ____fput+0x20/0x30 fs/file_table.c:404  \n task_work_run+0x230/0x2e0 kernel/task_work.c:180  \n exit_task_work include/linux/task_work.h:38 [inline]  \n do_exit+0x618/0x1f64 kernel/exit.c:871  \n do_group_exit+0x194/0x22c kernel/exit.c:1020  \n get_signal+0x1500/0x15ec kernel/signal.c:2893  \n do_signal+0x23c/0x3b44 arch/arm64/kernel/signal.c:1249  \n do_notify_resume+0x74/0x1f4 arch/arm64/kernel/entry-common.c:148  \n exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline]  \n exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline]  \n el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:713  \n el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730  \n el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598  \n  \nAllocated by task 6166:  \n kasan_save_stack mm/kasan/common.c:47 [inline]  \n kasan_save_track+0x40/0x78 mm/kasan/common.c:68  \n kasan_save_alloc_info+0x70/0x84 mm/kasan/generic.c:626  \n unpoison_slab_object mm/kasan/common.c:314 [inline]  \n __kasan_slab_alloc+0x74/0x8c mm/kasan/common.c:340  \n kasan_slab_alloc include/linux/kasan.h:201 [inline]  \n slab_post_alloc_hook mm/slub.c:3813 [inline]  \n slab_alloc_node mm/slub.c:3860 [inline]  \n kmem_cache_alloc_node+0x204/0x4c0 mm/slub.c:3903  \n __alloc_skb+0x19c/0x3d8 net/core/skbuff.c:641  \n alloc_skb include/linux/skbuff.h:1296 [inline]  \n kcm_sendmsg+0x1d3c/0x2124 net/kcm/kcmsock.c:783  \n sock_sendmsg_nosec net/socket.c:730 [inline]  \n __sock_se[...]", "creation_timestamp": "2024-08-31T16:43:34.000000Z"}, {"uuid": "912ceba3-c8ec-4922-a563-816193e21ebe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44941", "type": "seen", "source": "https://t.me/cvedetector/4132", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44941 - Linux F2FS Slab-Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-44941 \nPublished : Aug. 26, 2024, 12:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nf2fs: fix to cover read extent cache access with lock  \n  \nsyzbot reports a f2fs bug as below:  \n  \nBUG: KASAN: slab-use-after-free in sanity_check_extent_cache+0x370/0x410 fs/f2fs/extent_cache.c:46  \nRead of size 4 at addr ffff8880739ab220 by task syz-executor200/5097  \n  \nCPU: 0 PID: 5097 Comm: syz-executor200 Not tainted 6.9.0-rc6-syzkaller #0  \nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024  \nCall Trace:  \n   \n __dump_stack lib/dump_stack.c:88 [inline]  \n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114  \n print_address_description mm/kasan/report.c:377 [inline]  \n print_report+0x169/0x550 mm/kasan/report.c:488  \n kasan_report+0x143/0x180 mm/kasan/report.c:601  \n sanity_check_extent_cache+0x370/0x410 fs/f2fs/extent_cache.c:46  \n do_read_inode fs/f2fs/inode.c:509 [inline]  \n f2fs_iget+0x33e1/0x46e0 fs/f2fs/inode.c:560  \n f2fs_nfs_get_inode+0x74/0x100 fs/f2fs/super.c:3237  \n generic_fh_to_dentry+0x9f/0xf0 fs/libfs.c:1413  \n exportfs_decode_fh_raw+0x152/0x5f0 fs/exportfs/expfs.c:444  \n exportfs_decode_fh+0x3c/0x80 fs/exportfs/expfs.c:584  \n do_handle_to_path fs/fhandle.c:155 [inline]  \n handle_to_path fs/fhandle.c:210 [inline]  \n do_handle_open+0x495/0x650 fs/fhandle.c:226  \n do_syscall_x64 arch/x86/entry/common.c:52 [inline]  \n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f  \n  \nWe missed to cover sanity_check_extent_cache() w/ extent cache lock,  \nso, below race case may happen, result in use after free issue.  \n  \n- f2fs_iget  \n - do_read_inode  \n  - f2fs_init_read_extent_tree  \n  : add largest extent entry in to cache  \n     - shrink  \n      - f2fs_shrink_read_extent_tree  \n       - __shrink_extent_tree  \n        - __detach_extent_node  \n        : drop largest extent entry  \n  - sanity_check_extent_cache  \n  : access et->largest w/o lock  \n  \nlet's refactor sanity_check_extent_cache() to avoid extent cache access  \nand call it before f2fs_init_read_extent_tree() to fix this issue. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-26T15:23:50.000000Z"}, {"uuid": "b9b71aac-e5ec-4815-9be5-8ca2e04c00e9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44942", "type": "seen", "source": "https://t.me/cvedetector/4131", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44942 - \"F2FS Linux Kernel BUG in f2fs_write_inline_data\"\", \n  \"Content\": \"CVE ID : CVE-2024-44942 \nPublished : Aug. 26, 2024, 12:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nf2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC  \n  \nsyzbot reports a f2fs bug as below:  \n  \n------------[ cut here ]------------  \nkernel BUG at fs/f2fs/inline.c:258!  \nCPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0  \nRIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258  \nCall Trace:  \n f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834  \n f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline]  \n __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline]  \n f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315  \n do_writepages+0x35b/0x870 mm/page-writeback.c:2612  \n __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650  \n writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941  \n wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117  \n wb_do_writeback fs/fs-writeback.c:2264 [inline]  \n wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304  \n process_one_work kernel/workqueue.c:3254 [inline]  \n process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335  \n worker_thread+0x86d/0xd70 kernel/workqueue.c:3416  \n kthread+0x2f2/0x390 kernel/kthread.c:388  \n ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147  \n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244  \n  \nThe root cause is: inline_data inode can be fuzzed, so that there may  \nbe valid blkaddr in its direct node, once f2fs triggers background GC  \nto migrate the block, it will hit f2fs_bug_on() during dirty page  \nwriteback.  \n  \nLet's add sanity check on F2FS_INLINE_DATA flag in inode during GC,  \nso that, it can forbid migrating inline_data inode's data block for  \nfixing. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-26T15:23:49.000000Z"}, {"uuid": "323f4f9d-a47c-4f21-b8ed-38345aa67fdb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44940", "type": "seen", "source": "https://t.me/cvedetector/4133", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44940 - Linux kernel Fou GRO Receive Buffer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-44940 \nPublished : Aug. 26, 2024, 12:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfou: remove warn in gue_gro_receive on unsupported protocol  \n  \nDrop the WARN_ON_ONCE inn gue_gro_receive if the encapsulated type is  \nnot known or does not have a GRO handler.  \n  \nSuch a packet is easily constructed. Syzbot generates them and sets  \noff this warning.  \n  \nRemove the warning as it is expected and not actionable.  \n  \nThe warning was previously reduced from WARN_ON to WARN_ON_ONCE in  \ncommit 270136613bf7 (\"fou: Do WARN_ON_ONCE in gue_gro_receive for bad  \nproto callbacks\"). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-26T15:23:51.000000Z"}]}