{"vulnerability": "CVE-2024-4230", "sightings": [{"uuid": "f2ea87de-375d-43dc-8e81-eb4e62e0efbd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-4230", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113678313763260774", "content": "", "creation_timestamp": "2024-12-19T07:30:11.292956Z"}, {"uuid": "838f9be7-2e6b-4d7b-a4ec-c3e736bb16ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42307", "type": "seen", "source": "https://t.me/cvedetector/3407", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42307 - \"Cisco Linux Smack Null Pointer Denial of Service\"\", \n  \"Content\": \"CVE ID : CVE-2024-42307 \nPublished : Aug. 17, 2024, 9:15 a.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncifs: fix potential null pointer use in destroy_workqueue in init_cifs error path  \n  \nDan Carpenter reported a Smack static checker warning:  \n   fs/smb/client/cifsfs.c:1981 init_cifs()  \n   error: we previously assumed 'serverclose_wq' could be null (see line 1895)  \n  \nThe patch which introduced the serverclose workqueue used the wrong  \noredering in error paths in init_cifs() for freeing it on errors. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T12:18:10.000000Z"}, {"uuid": "c56b6646-8691-4260-a084-1395ef0767f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42306", "type": "seen", "source": "https://t.me/cvedetector/3409", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42306 - Linux Kernel UDF Corruption Denial of Service Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42306 \nPublished : Aug. 17, 2024, 9:15 a.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nudf: Avoid using corrupted block bitmap buffer  \n  \nWhen the filesystem block bitmap is corrupted, we detect the corruption  \nwhile loading the bitmap and fail the allocation with error. However the  \nnext allocation from the same bitmap will notice the bitmap buffer is  \nalready loaded and tries to allocate from the bitmap with mixed results  \n(depending on the exact nature of the bitmap corruption). Fix the  \nproblem by using BH_verified bit to indicate whether the bitmap is valid  \nor not. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T12:18:50.000000Z"}, {"uuid": "b70951ce-1972-427a-8098-7e43451a5ab6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42300", "type": "seen", "source": "https://t.me/cvedetector/3408", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42300 - Alibaba Cloud ECS Erofs Kernel Race Condition Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42300 \nPublished : Aug. 17, 2024, 9:15 a.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nerofs: fix race in z_erofs_get_gbuf()  \n  \nIn z_erofs_get_gbuf(), the current task may be migrated to another  \nCPU between `z_erofs_gbuf_id()` and `spin_lock(&gbuf->lock)`.  \n  \nTherefore, z_erofs_put_gbuf() will trigger the following issue  \nwhich was found by stress test:  \n  \n[772156.434168] kernel BUG at fs/erofs/zutil.c:58!  \n..  \n[772156.435007]  \n[772156.439237] CPU: 0 PID: 3078 Comm: stress Kdump: loaded Tainted: G            E      6.10.0-rc7+ #2  \n[772156.439239] Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 1.0.0 01/01/2017  \n[772156.439241] pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)  \n[772156.439243] pc : z_erofs_put_gbuf+0x64/0x70 [erofs]  \n[772156.439252] lr : z_erofs_lz4_decompress+0x600/0x6a0 [erofs]  \n..  \n[772156.445958] stress (3127): drop_caches: 1  \n[772156.446120] Call trace:  \n[772156.446121]  z_erofs_put_gbuf+0x64/0x70 [erofs]  \n[772156.446761]  z_erofs_lz4_decompress+0x600/0x6a0 [erofs]  \n[772156.446897]  z_erofs_decompress_queue+0x740/0xa10 [erofs]  \n[772156.447036]  z_erofs_runqueue+0x428/0x8c0 [erofs]  \n[772156.447160]  z_erofs_readahead+0x224/0x390 [erofs]  \n.. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T12:18:49.000000Z"}, {"uuid": "253bcf73-8d4c-4bcf-8205-8a69a99da40e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42308", "type": "seen", "source": "https://t.me/cvedetector/3405", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42308 - \"AUDIT: AMD Display Linux Kernel NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-42308 \nPublished : Aug. 17, 2024, 9:15 a.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Check for NULL pointer  \n  \n[why & how]  \nNeed to make sure plane_state is initialized  \nbefore accessing its members.  \n  \n(cherry picked from commit 295d91cbc700651782a60572f83c24861607b648) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T12:18:08.000000Z"}, {"uuid": "2fac93bd-4426-491e-a207-97bf95040299", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42302", "type": "seen", "source": "https://t.me/cvedetector/3404", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42302 - \"Linux PCI DPC Use-After-Free Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-42302 \nPublished : Aug. 17, 2024, 9:15 a.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI/DPC: Fix use-after-free on concurrent DPC and hot-removal  \n  \nKeith reports a use-after-free when a DPC event occurs concurrently to  \nhot-removal of the same portion of the hierarchy:  \n  \nThe dpc_handler() awaits readiness of the secondary bus below the  \nDownstream Port where the DPC event occurred.  To do so, it polls the  \nconfig space of the first child device on the secondary bus.  If that  \nchild device is concurrently removed, accesses to its struct pci_dev  \ncause the kernel to oops.  \n  \nThat's because pci_bridge_wait_for_secondary_bus() neglects to hold a  \nreference on the child device.  Before v6.3, the function was only  \ncalled on resume from system sleep or on runtime resume.  Holding a  \nreference wasn't necessary back then because the pciehp IRQ thread  \ncould never run concurrently.  (On resume from system sleep, IRQs are  \nnot enabled until after the resume_noirq phase.  And runtime resume is  \nalways awaited before a PCI device is removed.)  \n  \nHowever starting with v6.3, pci_bridge_wait_for_secondary_bus() is also  \ncalled on a DPC event.  Commit 53b54ad074de (\"PCI/DPC: Await readiness  \nof secondary bus after reset\"), which introduced that, failed to  \nappreciate that pci_bridge_wait_for_secondary_bus() now needs to hold a  \nreference on the child device because dpc_handler() and pciehp may  \nindeed run concurrently.  The commit was backported to v5.10+ stable  \nkernels, so that's the oldest one affected.  \n  \nAdd the missing reference acquisition.  \n  \nAbridged stack trace:  \n  \n  BUG: unable to handle page fault for address: 00000000091400c0  \n  CPU: 15 PID: 2464 Comm: irq/53-pcie-dpc 6.9.0  \n  RIP: pci_bus_read_config_dword+0x17/0x50  \n  pci_dev_wait()  \n  pci_bridge_wait_for_secondary_bus()  \n  dpc_reset_link()  \n  pcie_do_recovery()  \n  dpc_handler() \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T12:18:07.000000Z"}, {"uuid": "abfe5034-46f1-4b23-8e22-64545ac2d901", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42301", "type": "seen", "source": "https://bsky.app/profile/gcpweekly.bsky.social/post/3lndbn7ih6n2z", "content": "", "creation_timestamp": "2025-04-21T13:32:31.147831Z"}, {"uuid": "3559d0f4-212d-41ab-bfdc-274fbadfda57", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-4230", "type": "seen", "source": "https://t.me/cvedetector/13311", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-4230 - Edgecross Basic Software for Windows/Path Traversal Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-4230 \nPublished : Dec. 19, 2024, 8:17 a.m. | 27\u00a0minutes ago \nDescription : External Control of File Name or Path vulnerability in Edgecross Basic Software for Windows versions 1.00 and later and Edgecross Basic Software for Developers versions 1.00 and later allows a malicious local attacker to execute an arbitrary malicious code, resulting in information disclosure, tampering with and deletion, or a denial-of-service (DoS) condition. \nSeverity: 7.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-19T09:48:05.000000Z"}, {"uuid": "7526e4b3-a4e7-4b4f-b079-1f1b834a2bf1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42309", "type": "seen", "source": "https://t.me/cvedetector/3406", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42309 - Intel DRM Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42309 \nPublished : Aug. 17, 2024, 9:15 a.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/gma500: fix null pointer dereference in psb_intel_lvds_get_modes  \n  \nIn psb_intel_lvds_get_modes(), the return value of drm_mode_duplicate() is  \nassigned to mode, which will lead to a possible NULL pointer dereference  \non failure of drm_mode_duplicate(). Add a check to avoid npd. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T12:18:09.000000Z"}]}