<?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-04T11:14:46.235712+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/3f2e6d15-cc10-4800-a239-b462547b707f/export</id>
    <title>3f2e6d15-cc10-4800-a239-b462547b707f</title>
    <updated>2026-05-04T11:14:46.490062+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://vulnerability.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "3f2e6d15-cc10-4800-a239-b462547b707f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56777", "type": "seen", "source": "https://t.me/cvedetector/14719", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56777 - \"Linux kernel Deref Dereference Error in drm/sti\"\", \n  \"Content\": \"CVE ID : CVE-2024-56777 \nPublished : Jan. 8, 2025, 6:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/sti: avoid potential dereference of error pointers in sti_gdp_atomic_check  \n  \nThe return value of drm_atomic_get_crtc_state() needs to be  \nchecked. To avoid use of error pointer 'crtc_state' in case  \nof the failure. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-08T20:00:04.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/3f2e6d15-cc10-4800-a239-b462547b707f/export"/>
    <published>2025-01-08T20:00:04+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/eb55b45a-3380-429d-9887-f02ed229f9c6/export</id>
    <title>eb55b45a-3380-429d-9887-f02ed229f9c6</title>
    <updated>2026-05-04T11:14:46.489975+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://vulnerability.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "eb55b45a-3380-429d-9887-f02ed229f9c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56773", "type": "seen", "source": "https://t.me/cvedetector/14718", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56773 - Linux Kernel kunit Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56773 \nPublished : Jan. 8, 2025, 6:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nkunit: Fix potential null dereference in kunit_device_driver_test()  \n  \nkunit_kzalloc() may return a NULL pointer, dereferencing it without  \nNULL check may lead to NULL dereference.  \nAdd a NULL check for test_state. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-08T20:00:04.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/eb55b45a-3380-429d-9887-f02ed229f9c6/export"/>
    <published>2025-01-08T20:00:04+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/4e714412-1cd9-4096-87da-952780a919e4/export</id>
    <title>4e714412-1cd9-4096-87da-952780a919e4</title>
    <updated>2026-05-04T11:14:46.489887+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://vulnerability.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "4e714412-1cd9-4096-87da-952780a919e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56771", "type": "seen", "source": "https://t.me/cvedetector/14720", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56771 - \"Winvic Spinand Linux Kernel ECC Information Faking\"\", \n  \"Content\": \"CVE ID : CVE-2024-56771 \nPublished : Jan. 8, 2025, 6:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmtd: spinand: winbond: Fix 512GW, 01GW, 01JW and 02JW ECC information  \n  \nThese four chips:  \n* W25N512GW  \n* W25N01GW  \n* W25N01JW  \n* W25N02JW  \nall require a single bit of ECC strength and thus feature an on-die  \nHamming-like ECC engine. There is no point in filling a -&amp;gt;get_status()  \ncallback for them because the main ECC status bytes are located in  \nstandard places, and retrieving the number of bitflips in case of  \ncorrected chunk is both useless and unsupported (if there are bitflips,  \nthen there is 1 at most, so no need to query the chip for that).  \n  \nWithout this change, a kernel warning triggers every time a bit flips. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-08T20:00:05.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/4e714412-1cd9-4096-87da-952780a919e4/export"/>
    <published>2025-01-08T20:00:05+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/17617fd1-9c5f-4710-aa07-f9e5e4172c9f/export</id>
    <title>17617fd1-9c5f-4710-aa07-f9e5e4172c9f</title>
    <updated>2026-05-04T11:14:46.489770+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://vulnerability.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "17617fd1-9c5f-4710-aa07-f9e5e4172c9f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56772", "type": "seen", "source": "https://t.me/cvedetector/14721", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56772 - Linux kernel: Uninitialized Free Pointer (UAF) vulnerability in kunit string-stream module.\", \n  \"Content\": \"CVE ID : CVE-2024-56772 \nPublished : Jan. 8, 2025, 6:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nkunit: string-stream: Fix a UAF bug in kunit_init_suite()  \n  \nIn kunit_debugfs_create_suite(), if alloc_string_stream() fails in the  \nkunit_suite_for_each_test_case() loop, the \"suite-&amp;gt;log = stream\"  \nhas assigned before, and the error path only free the suite-&amp;gt;log's stream  \nmemory but not set it to NULL, so the later string_stream_clear() of  \nsuite-&amp;gt;log in kunit_init_suite() will cause below UAF bug.  \n  \nSet stream pointer to NULL after free to fix it.  \n  \n Unable to handle kernel paging request at virtual address 006440150000030d  \n Mem abort info:  \n   ESR = 0x0000000096000004  \n   EC = 0x25: DABT (current EL), IL = 32 bits  \n   SET = 0, FnV = 0  \n   EA = 0, S1PTW = 0  \n   FSC = 0x04: level 0 translation fault  \n Data abort info:  \n   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000  \n   CM = 0, WnR = 0, TnD = 0, TagAccess = 0  \n   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0  \n [006440150000030d] address between user and kernel address ranges  \n Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP  \n Dumping ftrace buffer:  \n    (ftrace buffer empty)  \n Modules linked in: iio_test_gts industrialio_gts_helper cfg80211 rfkill ipv6 [last unloaded: iio_test_gts]  \n CPU: 5 UID: 0 PID: 6253 Comm: modprobe Tainted: G    B   W        N 6.12.0-rc4+ #458  \n Tainted: [B]=BAD_PAGE, [W]=WARN, [N]=TEST  \n Hardware name: linux,dummy-virt (DT)  \n pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)  \n pc : string_stream_clear+0x54/0x1ac  \n lr : string_stream_clear+0x1a8/0x1ac  \n sp : ffffffc080b47410  \n x29: ffffffc080b47410 x28: 006440550000030d x27: ffffff80c96b5e98  \n x26: ffffff80c96b5e80 x25: ffffffe461b3f6c0 x24: 0000000000000003  \n x23: ffffff80c96b5e88 x22: 1ffffff019cdf4fc x21: dfffffc000000000  \n x20: ffffff80ce6fa7e0 x19: 032202a80000186d x18: 0000000000001840  \n x17: 0000000000000000 x16: 0000000000000000 x15: ffffffe45c355cb4  \n x14: ffffffe45c35589c x13: ffffffe45c03da78 x12: ffffffb810168e75  \n x11: 1ffffff810168e74 x10: ffffffb810168e74 x9 : dfffffc000000000  \n x8 : 0000000000000004 x7 : 0000000000000003 x6 : 0000000000000001  \n x5 : ffffffc080b473a0 x4 : 0000000000000000 x3 : 0000000000000000  \n x2 : 0000000000000001 x1 : ffffffe462fbf620 x0 : dfffffc000000000  \n Call trace:  \n  string_stream_clear+0x54/0x1ac  \n  __kunit_test_suites_init+0x108/0x1d8  \n  kunit_exec_run_tests+0xb8/0x100  \n  kunit_module_notify+0x400/0x55c  \n  notifier_call_chain+0xfc/0x3b4  \n  blocking_notifier_call_chain+0x68/0x9c  \n  do_init_module+0x24c/0x5c8  \n  load_module+0x4acc/0x4e90  \n  init_module_from_file+0xd4/0x128  \n  idempotent_init_module+0x2d4/0x57c  \n  __arm64_sys_finit_module+0xac/0x100  \n  invoke_syscall+0x6c/0x258  \n  el0_svc_common.constprop.0+0x160/0x22c  \n  do_el0_svc+0x44/0x5c  \n  el0_svc+0x48/0xb8  \n  el0t_64_sync_handler+0x13c/0x158  \n  el0t_64_sync+0x190/0x194  \n Code: f9400753 d2dff800 f2fbffe0 d343fe7c (38e06b80)  \n ---[ end trace 0000000000000000 ]---  \n Kernel panic - not syncing: Oops: Fatal exception \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-08T20:00:06.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/17617fd1-9c5f-4710-aa07-f9e5e4172c9f/export"/>
    <published>2025-01-08T20:00:06+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/3bbae7bd-e823-49e2-b8c8-45947d91f1e8/export</id>
    <title>3bbae7bd-e823-49e2-b8c8-45947d91f1e8</title>
    <updated>2026-05-04T11:14:46.489670+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://vulnerability.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "3bbae7bd-e823-49e2-b8c8-45947d91f1e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56779", "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>
    <link href="https://vulnerability.circl.lu/sighting/3bbae7bd-e823-49e2-b8c8-45947d91f1e8/export"/>
    <published>2025-08-14T10:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/548cf7dc-fd39-4337-a5eb-01092679e86f/export</id>
    <title>548cf7dc-fd39-4337-a5eb-01092679e86f</title>
    <updated>2026-05-04T11:14:46.488658+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>http://vulnerability.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "548cf7dc-fd39-4337-a5eb-01092679e86f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56770", "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>
    <link href="https://vulnerability.circl.lu/sighting/548cf7dc-fd39-4337-a5eb-01092679e86f/export"/>
    <published>2025-08-14T10:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/b8b1cbdd-6993-4c31-9805-0d9916044b44/export</id>
    <title>b8b1cbdd-6993-4c31-9805-0d9916044b44</title>
    <updated>2026-05-04T11:14:46.488576+00:00</updated>
    <author>
      <name>Alexandre Dulaunoy</name>
      <uri>http://vulnerability.circl.lu/user/adulau</uri>
    </author>
    <content>{"uuid": "b8b1cbdd-6993-4c31-9805-0d9916044b44", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56775", "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/b8b1cbdd-6993-4c31-9805-0d9916044b44/export"/>
    <published>2025-12-03T14:14:49.267740+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/01bd8e6e-538e-49b1-a351-6ce6d36a9c27/export</id>
    <title>01bd8e6e-538e-49b1-a351-6ce6d36a9c27</title>
    <updated>2026-05-04T11:14:46.488485+00:00</updated>
    <author>
      <name>Alexandre Dulaunoy</name>
      <uri>http://vulnerability.circl.lu/user/adulau</uri>
    </author>
    <content>{"uuid": "01bd8e6e-538e-49b1-a351-6ce6d36a9c27", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56778", "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/01bd8e6e-538e-49b1-a351-6ce6d36a9c27/export"/>
    <published>2025-12-03T14:14:49.267740+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/d360e6cb-0e94-4f02-a559-97a3b752b38e/export</id>
    <title>d360e6cb-0e94-4f02-a559-97a3b752b38e</title>
    <updated>2026-05-04T11:14:46.488372+00:00</updated>
    <author>
      <name>Alexandre Dulaunoy</name>
      <uri>http://vulnerability.circl.lu/user/adulau</uri>
    </author>
    <content>{"uuid": "d360e6cb-0e94-4f02-a559-97a3b752b38e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56776", "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/d360e6cb-0e94-4f02-a559-97a3b752b38e/export"/>
    <published>2025-12-03T14:14:49.267740+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/2be681cc-a7a6-40b8-baa3-9986a0f6a9e8/export</id>
    <title>2be681cc-a7a6-40b8-baa3-9986a0f6a9e8</title>
    <updated>2026-05-04T11:14:46.485393+00:00</updated>
    <author>
      <name>Alexandre Dulaunoy</name>
      <uri>http://vulnerability.circl.lu/user/adulau</uri>
    </author>
    <content>{"uuid": "2be681cc-a7a6-40b8-baa3-9986a0f6a9e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56777", "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/2be681cc-a7a6-40b8-baa3-9986a0f6a9e8/export"/>
    <published>2025-12-03T14:14:49.267740+00:00</published>
  </entry>
</feed>
