<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/sightings/feed</id>
  <title>Most recent sightings.</title>
  <updated>2026-05-08T11:25:13.934859+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent sightings.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/6e6867e9-4d3a-49ea-ac10-08d8cad4d90e/export</id>
    <title>6e6867e9-4d3a-49ea-ac10-08d8cad4d90e</title>
    <updated>2026-05-08T11:25:14.223740+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "6e6867e9-4d3a-49ea-ac10-08d8cad4d90e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50120", "type": "seen", "source": "https://t.me/cvedetector/9924", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50120 - Samba kernel Memory Allocationassi\", \n  \"Content\": \"CVE ID : CVE-2024-50120 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsmb: client: Handle kstrdup failures for passwords  \n  \nIn smb3_reconfigure(), after duplicating ctx-&amp;gt;password and  \nctx-&amp;gt;password2 with kstrdup(), we need to check for allocation  \nfailures.  \n  \nIf ses-&amp;gt;password allocation fails, return -ENOMEM.  \nIf ses-&amp;gt;password2 allocation fails, free ses-&amp;gt;password, set it  \nto NULL, and return -ENOMEM. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:28.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/6e6867e9-4d3a-49ea-ac10-08d8cad4d90e/export"/>
    <published>2024-11-05T19:44:28+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/3524a530-e8dc-483e-b128-b6df80925a2c/export</id>
    <title>3524a530-e8dc-483e-b128-b6df80925a2c</title>
    <updated>2026-05-08T11:25:14.223570+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "3524a530-e8dc-483e-b128-b6df80925a2c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50122", "type": "seen", "source": "https://t.me/cvedetector/9925", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50122 - PCIe Linux Kernel Sysfs Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50122 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI: Hold rescan lock while adding devices during host probe  \n  \nSince adding the PCI power control code, we may end up with a race between  \nthe pwrctl platform device rescanning the bus and host controller probe  \nfunctions. The latter need to take the rescan lock when adding devices or  \nwe may end up in an undefined state having two incompletely added devices  \nand hit the following crash when trying to remove the device over sysfs:  \n  \n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000  \n  Internal error: Oops: 0000000096000004 [#1] SMP  \n  Call trace:  \n    __pi_strlen+0x14/0x150  \n    kernfs_find_ns+0x80/0x13c  \n    kernfs_remove_by_name_ns+0x54/0xf0  \n    sysfs_remove_bin_file+0x24/0x34  \n    pci_remove_resource_files+0x3c/0x84  \n    pci_remove_sysfs_dev_files+0x28/0x38  \n    pci_stop_bus_device+0x8c/0xd8  \n    pci_stop_bus_device+0x40/0xd8  \n    pci_stop_and_remove_bus_device_locked+0x28/0x48  \n    remove_store+0x70/0xb0  \n    dev_attr_store+0x20/0x38  \n    sysfs_kf_write+0x58/0x78  \n    kernfs_fop_write_iter+0xe8/0x184  \n    vfs_write+0x2dc/0x308  \n    ksys_write+0x7c/0xec \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:28.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/3524a530-e8dc-483e-b128-b6df80925a2c/export"/>
    <published>2024-11-05T19:44:28+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/496cebd5-020c-4a62-ad92-1f4218b82491/export</id>
    <title>496cebd5-020c-4a62-ad92-1f4218b82491</title>
    <updated>2026-05-08T11:25:14.223411+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "496cebd5-020c-4a62-ad92-1f4218b82491", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50124", "type": "seen", "source": "https://t.me/cvedetector/9927", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50124 - Linux Bluetooth ISO Use-After-Free\", \n  \"Content\": \"CVE ID : CVE-2024-50124 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: ISO: Fix UAF on iso_sock_timeout  \n  \nconn-&amp;gt;sk maybe have been unlinked/freed while waiting for iso_conn_lock  \nso this checks if the conn-&amp;gt;sk is still valid by checking if it part of  \niso_sk_list. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:33.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/496cebd5-020c-4a62-ad92-1f4218b82491/export"/>
    <published>2024-11-05T19:44:33+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/7f0e586d-201d-4d9d-9c57-7837bc5aa279/export</id>
    <title>7f0e586d-201d-4d9d-9c57-7837bc5aa279</title>
    <updated>2026-05-08T11:25:14.223241+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "7f0e586d-201d-4d9d-9c57-7837bc5aa279", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50123", "type": "seen", "source": "https://t.me/cvedetector/9928", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50123 - Linux Kernel BPF Sockmap Out-of-Bounds Read (Information Disclosure)\", \n  \"Content\": \"CVE ID : CVE-2024-50123 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Add the missing BPF_LINK_TYPE invocation for sockmap  \n  \nThere is an out-of-bounds read in bpf_link_show_fdinfo() for the sockmap  \nlink fd. Fix it by adding the missing BPF_LINK_TYPE invocation for  \nsockmap link  \n  \nAlso add comments for bpf_link_type to prevent missing updates in the  \nfuture. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:34.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/7f0e586d-201d-4d9d-9c57-7837bc5aa279/export"/>
    <published>2024-11-05T19:44:34+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/549f6348-5bd9-4dbd-94b4-19c09c32162f/export</id>
    <title>549f6348-5bd9-4dbd-94b4-19c09c32162f</title>
    <updated>2026-05-08T11:25:14.223033+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "549f6348-5bd9-4dbd-94b4-19c09c32162f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50121", "type": "seen", "source": "https://t.me/cvedetector/9930", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50121 - Linux NFSd Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50121 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfsd: cancel nfsd_shrinker_work using sync mode in nfs4_state_shutdown_net  \n  \nIn the normal case, when we excute `echo 0 &amp;gt; /proc/fs/nfsd/threads`, the  \nfunction `nfs4_state_destroy_net` in `nfs4_state_shutdown_net` will  \nrelease all resources related to the hashed `nfs4_client`. If the  \n`nfsd_client_shrinker` is running concurrently, the `expire_client`  \nfunction will first unhash this client and then destroy it. This can  \nlead to the following warning. Additionally, numerous use-after-free  \nerrors may occur as well.  \n  \nnfsd_client_shrinker         echo 0 &amp;gt; /proc/fs/nfsd/threads  \n  \nexpire_client                nfsd_shutdown_net  \n  unhash_client                ...  \n                               nfs4_state_shutdown_net  \n                                 /* won't wait shrinker exit */  \n  /*                             cancel_work(&amp;amp;nn-&amp;gt;nfsd_shrinker_work)  \n   * nfsd_file for this          /* won't destroy unhashed client1 */  \n   * client1 still alive         nfs4_state_destroy_net  \n   */  \n  \n                               nfsd_file_cache_shutdown  \n                                 /* trigger warning */  \n                                 kmem_cache_destroy(nfsd_file_slab)  \n                                 kmem_cache_destroy(nfsd_file_mark_slab)  \n  /* release nfsd_file and mark */  \n  __destroy_client  \n  \n====================================================================  \nBUG nfsd_file (Not tainted): Objects remaining in nfsd_file on  \n__kmem_cache_shutdown()  \n--------------------------------------------------------------------  \nCPU: 4 UID: 0 PID: 764 Comm: sh Not tainted 6.12.0-rc3+ #1  \n  \n dump_stack_lvl+0x53/0x70  \n slab_err+0xb0/0xf0  \n __kmem_cache_shutdown+0x15c/0x310  \n kmem_cache_destroy+0x66/0x160  \n nfsd_file_cache_shutdown+0xac/0x210 [nfsd]  \n nfsd_destroy_serv+0x251/0x2a0 [nfsd]  \n nfsd_svc+0x125/0x1e0 [nfsd]  \n write_threads+0x16a/0x2a0 [nfsd]  \n nfsctl_transaction_write+0x74/0xa0 [nfsd]  \n vfs_write+0x1a5/0x6d0  \n ksys_write+0xc1/0x160  \n do_syscall_64+0x5f/0x170  \n entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n  \n====================================================================  \nBUG nfsd_file_mark (Tainted: G    B   W         ): Objects remaining  \nnfsd_file_mark on __kmem_cache_shutdown()  \n--------------------------------------------------------------------  \n  \n dump_stack_lvl+0x53/0x70  \n slab_err+0xb0/0xf0  \n __kmem_cache_shutdown+0x15c/0x310  \n kmem_cache_destroy+0x66/0x160  \n nfsd_file_cache_shutdown+0xc8/0x210 [nfsd]  \n nfsd_destroy_serv+0x251/0x2a0 [nfsd]  \n nfsd_svc+0x125/0x1e0 [nfsd]  \n write_threads+0x16a/0x2a0 [nfsd]  \n nfsctl_transaction_write+0x74/0xa0 [nfsd]  \n vfs_write+0x1a5/0x6d0  \n ksys_write+0xc1/0x160  \n do_syscall_64+0x5f/0x170  \n entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n  \nTo resolve this issue, cancel `nfsd_shrinker_work` using synchronous  \nmode in nfs4_state_shutdown_net. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:35.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/549f6348-5bd9-4dbd-94b4-19c09c32162f/export"/>
    <published>2024-11-05T19:44:35+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/b3209cad-9c41-45c0-b333-e2a05c263c12/export</id>
    <title>b3209cad-9c41-45c0-b333-e2a05c263c12</title>
    <updated>2026-05-08T11:25:14.222873+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "b3209cad-9c41-45c0-b333-e2a05c263c12", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50127", "type": "seen", "source": "https://t.me/cvedetector/9932", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50127 - Netgear Linux Kernel Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50127 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: sched: fix use-after-free in taprio_change()  \n  \nIn 'taprio_change()', 'admin' pointer may become dangling due to sched  \nswitch / removal caused by 'advance_sched()', and critical section  \nprotected by 'q-&amp;gt;current_entry_lock' is too small to prevent from such  \na scenario (which causes use-after-free detected by KASAN). Fix this  \nby prefer 'rcu_replace_pointer()' over 'rcu_assign_pointer()' to update  \n'admin' immediately before an attempt to schedule freeing. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:45:12.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/b3209cad-9c41-45c0-b333-e2a05c263c12/export"/>
    <published>2024-11-05T19:45:12+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/7b594eba-b92f-4bfe-ae70-e792faf19e11/export</id>
    <title>7b594eba-b92f-4bfe-ae70-e792faf19e11</title>
    <updated>2026-05-08T11:25:14.222717+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "7b594eba-b92f-4bfe-ae70-e792faf19e11", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50127", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lska34c7x22r", "content": "", "creation_timestamp": "2025-06-26T22:59:08.044509Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/7b594eba-b92f-4bfe-ae70-e792faf19e11/export"/>
    <published>2025-06-26T22:59:08.044509+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/7a1eb07b-53f5-44f4-a804-18e5217a96fb/export</id>
    <title>7a1eb07b-53f5-44f4-a804-18e5217a96fb</title>
    <updated>2026-05-08T11:25:14.222521+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "7a1eb07b-53f5-44f4-a804-18e5217a96fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50125", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lsmfkxk22k2c", "content": "", "creation_timestamp": "2025-06-27T19:42:47.606620Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/7a1eb07b-53f5-44f4-a804-18e5217a96fb/export"/>
    <published>2025-06-27T19:42:47.606620+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/d8487cbc-c077-4861-b533-7e050a02327f/export</id>
    <title>d8487cbc-c077-4861-b533-7e050a02327f</title>
    <updated>2026-05-08T11:25:14.221302+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "d8487cbc-c077-4861-b533-7e050a02327f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50126", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-729/", "content": "", "creation_timestamp": "2025-07-30T03:00:00.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/d8487cbc-c077-4861-b533-7e050a02327f/export"/>
    <published>2025-07-30T03:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/1fca528c-88cc-46c0-9fc2-9161045e3867/export</id>
    <title>1fca528c-88cc-46c0-9fc2-9161045e3867</title>
    <updated>2026-05-08T11:25:14.219502+00:00</updated>
    <author>
      <name>Alexandre Dulaunoy</name>
      <uri>http://cve.circl.lu/user/adulau</uri>
    </author>
    <content>{"uuid": "1fca528c-88cc-46c0-9fc2-9161045e3867", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-50125", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/1fca528c-88cc-46c0-9fc2-9161045e3867/export"/>
    <published>2025-12-03T14:14:49.267740+00:00</published>
  </entry>
</feed>
