{"vulnerability": "CVE-2023-5291", "sightings": [{"uuid": "e3264fe0-fe57-405e-b724-3ce0a183fe0d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52917", "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": "0fcc809e-928c-4900-a598-914c30be9d76", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2023-52916", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "824ce71f-38de-471d-a5fd-a61b18cfe443", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52919", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-15", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}, {"uuid": "cd8d4827-1726-4a23-8ced-e4d1908444fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2023-52916", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "6e91ff54-29dc-4904-9bb3-68ba34014029", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52919", "type": "seen", "source": "https://t.me/cvedetector/8602", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52919 - Linux Kernel nfc nci Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-52919 \nPublished : Oct. 22, 2024, 8:15 a.m. | 1\u00a0hour, 46\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfc: nci: fix possible NULL pointer dereference in send_acknowledge()  \n  \nHandle memory allocation failure from nci_skb_alloc() (calling  \nalloc_skb()) to avoid possible NULL pointer dereference. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"22 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-22T12:06:39.000000Z"}, {"uuid": "6838c0ae-1484-45aa-b7df-65e0d0105c9e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52918", "type": "seen", "source": "https://t.me/cvedetector/8601", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52918 - Linux Kernel CX23885 NULL Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2023-52918 \nPublished : Oct. 22, 2024, 8:15 a.m. | 1\u00a0hour, 46\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmedia: pci: cx23885: check cx23885_vdev_init() return  \n  \ncx23885_vdev_init() can return a NULL pointer, but that pointer  \nis used in the next line without a check.  \n  \nAdd a NULL pointer check and go to the error unwind if it is NULL. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"22 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-22T12:06:39.000000Z"}, {"uuid": "d6e03b87-f1b2-4223-9a41-328db138bee9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52913", "type": "seen", "source": "https://t.me/cvedetector/3739", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52913 - Intel Linux DRM UAF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-52913 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/i915: Fix potential context UAFs  \n  \ngem_context_register() makes the context visible to userspace, and which  \npoint a separate thread can trigger the I915_GEM_CONTEXT_DESTROY ioctl.  \nSo we need to ensure that nothing uses the ctx ptr after this.  And we  \nneed to ensure that adding the ctx to the xarray is the *last* thing  \nthat gem_context_register() does with the ctx pointer.  \n  \n[tursulin: Stable and fixes tags add/tidy.]  \n(cherry picked from commit bed4b455cf5374e68879be56971c1da563bcd90c) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:00.000000Z"}, {"uuid": "cf5aa9ab-854c-47f0-8705-579b506c8602", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52914", "type": "seen", "source": "https://t.me/cvedetector/3741", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52914 - Linux kernel io_uring Poll Request Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-52914 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring/poll: add hash if ready poll request can't complete inline  \n  \nIf we don't, then we may lose access to it completely, leading to a  \nrequest leak. This will eventually stall the ring exit process as  \nwell. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:01.000000Z"}, {"uuid": "e4685baa-aff4-4551-8ea8-96055053f4eb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52912", "type": "seen", "source": "https://t.me/cvedetector/3740", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52912 - AMD Radeon amdgpu Bugs in Error Handling\", \n  \"Content\": \"CVE ID : CVE-2023-52912 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amdgpu: Fixed bug on error when unloading amdgpu  \n  \nFixed bug on error when unloading amdgpu.  \n  \nThe error message is as follows:  \n[  377.706202] kernel BUG at drivers/gpu/drm/drm_buddy.c:278!  \n[  377.706215] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI  \n[  377.706222] CPU: 4 PID: 8610 Comm: modprobe Tainted: G          IOE      6.0.0-thomas #1  \n[  377.706231] Hardware name: ASUS System Product Name/PRIME Z390-A, BIOS 2004 11/02/2021  \n[  377.706238] RIP: 0010:drm_buddy_free_block+0x26/0x30 [drm_buddy]  \n[  377.706264] Code: 00 00 00 90 0f 1f 44 00 00 48 8b 0e 89 c8 25 00 0c 00 00 3d 00 04 00 00 75 10 48 8b 47 18 48 d3 e0 48 01 47 28 e9 fa fe ff ff  0b 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 41 54 55 48 89 f5 53  \n[  377.706282] RSP: 0018:ffffad2dc4683cb8 EFLAGS: 00010287  \n[  377.706289] RAX: 0000000000000000 RBX: ffff8b1743bd5138 RCX: 0000000000000000  \n[  377.706297] RDX: ffff8b1743bd5160 RSI: ffff8b1743bd5c78 RDI: ffff8b16d1b25f70  \n[  377.706304] RBP: ffff8b1743bd59e0 R08: 0000000000000001 R09: 0000000000000001  \n[  377.706311] R10: ffff8b16c8572400 R11: ffffad2dc4683cf0 R12: ffff8b16d1b25f70  \n[  377.706318] R13: ffff8b16d1b25fd0 R14: ffff8b1743bd59c0 R15: ffff8b16d1b25f70  \n[  377.706325] FS:  00007fec56c72c40(0000) GS:ffff8b1836500000(0000) knlGS:0000000000000000  \n[  377.706334] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n[  377.706340] CR2: 00007f9b88c1ba50 CR3: 0000000110450004 CR4: 00000000003706e0  \n[  377.706347] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \n[  377.706354] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \n[  377.706361] Call Trace:  \n[  377.706365]    \n[  377.706369]  drm_buddy_free_list+0x2a/0x60 [drm_buddy]  \n[  377.706376]  amdgpu_vram_mgr_fini+0xea/0x180 [amdgpu]  \n[  377.706572]  amdgpu_ttm_fini+0x12e/0x1a0 [amdgpu]  \n[  377.706650]  amdgpu_bo_fini+0x22/0x90 [amdgpu]  \n[  377.706727]  gmc_v11_0_sw_fini+0x26/0x30 [amdgpu]  \n[  377.706821]  amdgpu_device_fini_sw+0xa1/0x3c0 [amdgpu]  \n[  377.706897]  amdgpu_driver_release_kms+0x12/0x30 [amdgpu]  \n[  377.706975]  drm_dev_release+0x20/0x40 [drm]  \n[  377.707006]  release_nodes+0x35/0xb0  \n[  377.707014]  devres_release_all+0x8b/0xc0  \n[  377.707020]  device_unbind_cleanup+0xe/0x70  \n[  377.707027]  device_release_driver_internal+0xee/0x160  \n[  377.707033]  driver_detach+0x44/0x90  \n[  377.707039]  bus_remove_driver+0x55/0xe0  \n[  377.707045]  pci_unregister_driver+0x3b/0x90  \n[  377.707052]  amdgpu_exit+0x11/0x6c [amdgpu]  \n[  377.707194]  __x64_sys_delete_module+0x142/0x2b0  \n[  377.707201]  ? fpregs_assert_state_consistent+0x22/0x50  \n[  377.707208]  ? exit_to_user_mode_prepare+0x3e/0x190  \n[  377.707215]  do_syscall_64+0x38/0x90  \n[  377.707221]  entry_SYSCALL_64_after_hwframe+0x63/0xcd \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:01.000000Z"}, {"uuid": "75f79947-b464-47b2-aeeb-9a389c26fe0d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52911", "type": "seen", "source": "https://t.me/cvedetector/3745", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52911 - Qualcomm MSM Linux Kernel NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-52911 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/msm: another fix for the headless Adreno GPU  \n  \nFix another oops reproducible when rebooting the board with the Adreno  \nGPU working in the headless mode (e.g. iMX platforms).  \n  \nUnable to handle kernel NULL pointer dereference at virtual address 00000000 when read  \n[00000000] *pgd=74936831, *pte=00000000, *ppte=00000000  \nInternal error: Oops: 17 [#1] ARM  \nCPU: 0 PID: 51 Comm: reboot Not tainted 6.2.0-rc1-dirty #11  \nHardware name: Freescale i.MX53 (Device Tree Support)  \nPC is at msm_atomic_commit_tail+0x50/0x970  \nLR is at commit_tail+0x9c/0x188  \npc : []    lr : []    psr: 600e0013  \nsp : e0851d30  ip : ee4eb7eb  fp : 00090acc  \nr10: 00000058  r9 : c2193014  r8 : c4310000  \nr7 : c4759380  r6 : 07bef61d  r5 : 00000000  r4 : 00000000  \nr3 : c44cc440  r2 : 00000000  r1 : 00000000  r0 : 00000000  \nFlags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none  \nControl: 10c5387d  Table: 74910019  DAC: 00000051  \nRegister r0 information: NULL pointer  \nRegister r1 information: NULL pointer  \nRegister r2 information: NULL pointer  \nRegister r3 information: slab kmalloc-1k start c44cc400 pointer offset 64 size 1024  \nRegister r4 information: NULL pointer  \nRegister r5 information: NULL pointer  \nRegister r6 information: non-paged memory  \nRegister r7 information: slab kmalloc-128 start c4759380 pointer offset 0 size 128  \nRegister r8 information: slab kmalloc-2k start c4310000 pointer offset 0 size 2048  \nRegister r9 information: non-slab/vmalloc memory  \nRegister r10 information: non-paged memory  \nRegister r11 information: non-paged memory  \nRegister r12 information: non-paged memory  \nProcess reboot (pid: 51, stack limit = 0xc80046d9)  \nStack: (0xe0851d30 to 0xe0852000)  \n1d20:                                     c4759380 fbd77200 000005ff 002b9c70  \n1d40: c4759380 c4759380 00000000 07bef61d 00000600 c0d6fe7c c2193014 00000058  \n1d60: 00090acc c067a214 00000000 c4759380 c4310000 00000000 c44cc854 c067a89c  \n1d80: 00000000 00000000 00000000 c4310468 00000000 c4759380 c4310000 c4310468  \n1da0: c4310470 c0643258 c4759380 00000000 00000000 c0c4ee24 00000000 c44cc810  \n1dc0: 00000000 c0c4ee24 00000000 c44cc810 00000000 0347d2a8 e0851e00 e0851e00  \n1de0: c4759380 c067ad20 c4310000 00000000 c44cc810 c27f8718 c44cc854 c067adb8  \n1e00: c4933000 00000002 00000001 00000000 00000000 c2130850 00000000 c2130854  \n1e20: c25fc488 00000000 c0ff162c 00000000 00000001 00000002 00000000 00000000  \n1e40: c43102c0 c43102c0 00000000 0347d2a8 c44cc810 c44cc814 c2133da8 c06d1a60  \n1e60: 00000000 00000000 00079028 c2012f24 fee1dead c4933000 00000058 c01431e4  \n1e80: 01234567 c0143a20 00000000 00000000 00000000 00000000 00000000 00000000  \n1ea0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000  \n1ec0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000  \n1ee0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000  \n1f00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000  \n1f20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000  \n1f40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000  \n1f60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000  \n1f80: 00000000 00000000 00000000 0347d2a8 00000002 00000004 00000078 00000058  \n1fa0: c010028c c0100060 00000002 00000004 fee1dead 28121969 01234567 00079028  \n1fc0: 00000002 00000004 00000078 00000058 0002fdc5 00000000 00000000 00090acc  \n1fe0: 00000058 becc9c64 b6e97e05 b6e0e5f6 600e0030 fee1dead 00000000 00000000  \n msm_atomic_commit_tail from commit_tail+0x9c/0x188  \n commit_tail from drm_atomic_helper_commit+0x160/0x188  \n drm_atomic_helper_commit from drm_atomic_commit+0xac/0xe0  \n drm_atomic_commit[...]", "creation_timestamp": "2024-08-21T09:52:10.000000Z"}, {"uuid": "a19cbbe1-5be2-4fad-b9a1-6c7ad6f902b9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52910", "type": "seen", "source": "https://t.me/cvedetector/3748", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52910 - \"Linux kernel IOMMU iova: Allocation Size Overflow Vulnerability in `__alloc_and_insert_iova_range`\"\", \n  \"Content\": \"CVE ID : CVE-2023-52910 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \niommu/iova: Fix alloc iova overflows issue  \n  \nIn __alloc_and_insert_iova_range, there is an issue that retry_pfn  \noverflows. The value of iovad->anchor.pfn_hi is ~0UL, then when  \niovad->cached_node is iovad->anchor, curr_iova->pfn_hi + 1 will  \noverflow. As a result, if the retry logic is executed, low_pfn is  \nupdated to 0, and then new_pfn cached_node is assigned as iovad->anchor. For  \nexample, the iova domain size is 10M, start_pfn is 0x1_F000_0000,  \nand the iova size allocated for the first time is 11M. The  \nfollowing is the log information, new->pfn_lo is smaller than  \niovad->cached_node.  \n  \nExample log as follows:  \n[  223.798112][T1705487] sh: [name:iova&]__alloc_and_insert_iova_range  \nstart_pfn:0x1f0000,retry_pfn:0x0,size:0xb00,limit_pfn:0x1f0a00  \n[  223.799590][T1705487] sh: [name:iova&]__alloc_and_insert_iova_range  \nsuccess start_pfn:0x1f0000,new->pfn_lo:0x1efe00,new->pfn_hi:0x1f08ff  \n  \n2. The node with the largest iova->pfn_lo value in the iova domain  \nis deleted, iovad->cached_node will be updated to iovad->anchor,  \nand then the alloc iova size exceeds the maximum iova size that can  \nbe allocated in the domain.  \n  \nAfter judging that retry_pfn is less than limit_pfn, call retry_pfn+1  \nto fix the overflow issue. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:13.000000Z"}, {"uuid": "110dbcf8-6e39-41d5-8581-8ac74506c6e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52915", "type": "seen", "source": "https://t.me/cvedetector/4959", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52915 - DVB-USB af9035 Null Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2023-52915 \nPublished : Sept. 6, 2024, 9:15 a.m. | 18\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmedia: dvb-usb-v2: af9035: Fix null-ptr-deref in af9035_i2c_master_xfer  \n  \nIn af9035_i2c_master_xfer, msg is controlled by user. When msg[i].buf  \nis null and msg[i].len is zero, former checks on msg[i].buf would be  \npassed. Malicious data finally reach af9035_i2c_master_xfer. If accessing  \nmsg[i].buf[0] without sanity check, null ptr deref would happen.  \nWe add check on msg[i].len to prevent crash.  \n  \nSimilar commit:  \ncommit 0ed554fd769a  \n(\"media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()\") \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-06T11:35:25.000000Z"}, {"uuid": "1f3650c3-ff73-4f17-8943-562291ea96b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52916", "type": "published-proof-of-concept", "source": "https://t.me/cvedetector/4958", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52916 - ASpeed Video Capture Memory Overwrite Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-52916 \nPublished : Sept. 6, 2024, 9:15 a.m. | 18\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmedia: aspeed: Fix memory overwrite if timing is 1600x900  \n  \nWhen capturing 1600x900, system could crash when system memory usage is  \ntight.  \n  \nThe way to reproduce this issue:  \n1. Use 1600x900 to display on host  \n2. Mount ISO through 'Virtual media' on OpenBMC's web  \n3. Run script as below on host to do sha continuously  \n  #!/bin/bash  \n  while [ [1] ];  \n  do  \n find /media -type f -printf '\"%h/%f\"\\n' | xargs sha256sum  \n  done  \n4. Open KVM on OpenBMC's web  \n  \nThe size of macro block captured is 8x8. Therefore, we should make sure  \nthe height of src-buf is 8 aligned 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\": \"06 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-06T11:35:24.000000Z"}]}