<?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>Sat, 04 Jul 2026 09:00:41 +0000</lastBuildDate>
    <item>
      <title>7a10bdbb-acff-47f6-a1b9-55ad8a99b867</title>
      <link>https://vulnerability.circl.lu/sighting/7a10bdbb-acff-47f6-a1b9-55ad8a99b867/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/7a10bdbb-acff-47f6-a1b9-55ad8a99b867/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
    <item>
      <title>c83cbb24-94de-438f-b0cf-5868b854f0a2</title>
      <link>https://vulnerability.circl.lu/sighting/c83cbb24-94de-438f-b0cf-5868b854f0a2/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/c83cbb24-94de-438f-b0cf-5868b854f0a2/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
    <item>
      <title>b3935449-103d-45c8-8553-7ee7043ce583</title>
      <link>https://vulnerability.circl.lu/sighting/b3935449-103d-45c8-8553-7ee7043ce583/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/b3935449-103d-45c8-8553-7ee7043ce583/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
    <item>
      <title>32c0f38b-b2b7-4630-8a12-f839d857287b</title>
      <link>https://vulnerability.circl.lu/sighting/32c0f38b-b2b7-4630-8a12-f839d857287b/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/32c0f38b-b2b7-4630-8a12-f839d857287b/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
    <item>
      <title>dbb91606-23c8-4c07-acc3-49f3a56fa06e</title>
      <link>https://vulnerability.circl.lu/sighting/dbb91606-23c8-4c07-acc3-49f3a56fa06e/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/dbb91606-23c8-4c07-acc3-49f3a56fa06e/export</guid>
      <pubDate>Thu, 14 Aug 2025 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>b327fa58-71bc-4809-b50e-870fd7810a9d</title>
      <link>https://vulnerability.circl.lu/sighting/b327fa58-71bc-4809-b50e-870fd7810a9d/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/b327fa58-71bc-4809-b50e-870fd7810a9d/export</guid>
      <pubDate>Thu, 14 Aug 2025 10:00:00 +0000</pubDate>
    </item>
    <item>
      <title>935c5d80-21d3-469d-bb51-efe457ba581e</title>
      <link>https://vulnerability.circl.lu/sighting/935c5d80-21d3-469d-bb51-efe457ba581e/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/935c5d80-21d3-469d-bb51-efe457ba581e/export</guid>
      <pubDate>Mon, 02 Sep 2024 21:24:20 +0000</pubDate>
    </item>
    <item>
      <title>38b2aec7-ac8c-4199-9787-e83212d5bb96</title>
      <link>https://vulnerability.circl.lu/sighting/38b2aec7-ac8c-4199-9787-e83212d5bb96/export</link>
      <description>{"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-&amp;gt;seq_skb.  \n  \n  2. Thread A resumes building skb from kcm-&amp;gt;seq_skb but is blocked  \n     by sk_stream_wait_memory()  \n  \n  3. Thread B calls sendmsg() concurrently, finishes building kcm-&amp;gt;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"}</description>
      <content:encoded>{"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-&amp;gt;seq_skb.  \n  \n  2. Thread A resumes building skb from kcm-&amp;gt;seq_skb but is blocked  \n     by sk_stream_wait_memory()  \n  \n  3. Thread B calls sendmsg() concurrently, finishes building kcm-&amp;gt;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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/38b2aec7-ac8c-4199-9787-e83212d5bb96/export</guid>
      <pubDate>Sat, 31 Aug 2024 16:43:34 +0000</pubDate>
    </item>
    <item>
      <title>4731c0c2-1601-4ead-b135-2ee8e1f47b38</title>
      <link>https://vulnerability.circl.lu/sighting/4731c0c2-1601-4ead-b135-2ee8e1f47b38/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/4731c0c2-1601-4ead-b135-2ee8e1f47b38/export</guid>
      <pubDate>Sat, 31 Aug 2024 10:02:33 +0000</pubDate>
    </item>
    <item>
      <title>806c89b5-f401-42a3-add4-03e593f0de08</title>
      <link>https://vulnerability.circl.lu/sighting/806c89b5-f401-42a3-add4-03e593f0de08/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/806c89b5-f401-42a3-add4-03e593f0de08/export</guid>
      <pubDate>Fri, 30 Aug 2024 10:38:13 +0000</pubDate>
    </item>
  </channel>
</rss>
