{"vulnerability": "CVE-2023-5313", "sightings": [{"uuid": "0b609366-3275-4f3c-a649-ddd72a57f45b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53137", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lo7c2no25432", "content": "", "creation_timestamp": "2025-05-02T17:34:20.271427Z"}, {"uuid": "1eaa6cc4-3264-4cd3-84b5-e7fc2ec5939f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53138", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lo7c2ovetek2", "content": "", "creation_timestamp": "2025-05-02T17:34:20.863033Z"}, {"uuid": "addb4328-af1c-41f3-9b9c-df3dc551a5b0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53136", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lo7c2rn4lv72", "content": "", "creation_timestamp": "2025-05-02T17:34:23.901336Z"}, {"uuid": "36636697-802c-4a7b-9080-70f473995996", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53139", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lo7c2vwq5od2", "content": "", "creation_timestamp": "2025-05-02T17:34:25.416098Z"}, {"uuid": "321ceeb9-9d48-4ac3-a116-bd19fb846f21", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53131", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr42jan2o", "content": "", "creation_timestamp": "2025-05-02T20:06:06.162452Z"}, {"uuid": "f9b6dde1-8465-4cdf-b62d-014ec50b47d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53132", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr4gpun2o", "content": "", "creation_timestamp": "2025-05-02T20:06:07.206180Z"}, {"uuid": "e4061243-2df3-4b49-8023-338407b9f950", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53134", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr4jybe2w", "content": "", "creation_timestamp": "2025-05-02T20:06:07.814472Z"}, {"uuid": "87e636c7-f324-49ea-95e5-1a5db62561e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53137", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr4nbew24", "content": "", "creation_timestamp": "2025-05-02T20:06:08.369497Z"}, {"uuid": "41ede468-e5fe-44be-a078-1e8ceb8a221e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53130", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr4tqef2p", "content": "", "creation_timestamp": "2025-05-02T20:06:09.754969Z"}, {"uuid": "66c2d78d-4e85-4176-a2bc-7a873def019c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53133", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr52jgp2t", "content": "", "creation_timestamp": "2025-05-02T20:06:11.001210Z"}, {"uuid": "a235bb13-118e-42a4-8e91-5b2c1b788412", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53136", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr5bgbu2n", "content": "", "creation_timestamp": "2025-05-02T20:06:12.283546Z"}, {"uuid": "237b6b7a-5c76-4431-b8d7-a45839eee021", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53135", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr5i4pf2p", "content": "", "creation_timestamp": "2025-05-02T20:06:13.471408Z"}, {"uuid": "442d1375-003a-4813-a846-9a13f6822e6e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53138", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr5ypde2h", "content": "", "creation_timestamp": "2025-05-02T20:06:16.567521Z"}, {"uuid": "2f2aaf64-d194-4083-94b9-4e30c9cb5c0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53139", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7mr645ew24", "content": "", "creation_timestamp": "2025-05-02T20:06:17.175465Z"}, {"uuid": "513e4539-8efc-4aaa-81c0-35df79df440b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2023-53131", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "f4c431ad-a95f-4816-b05c-a0143e0804a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2023-53133", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "f3010cba-672e-4d76-9b6c-d95a02252c02", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53130", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14516", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53130\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nblock: fix wrong mode for blkdev_put() from disk_scan_partitions()\n\nIf disk_scan_partitions() is called with 'FMODE_EXCL',\nblkdev_get_by_dev() will be called without 'FMODE_EXCL', however, follow\nblkdev_put() is still called with 'FMODE_EXCL', which will cause\n'bd_holders' counter to leak.\n\nFix the problem by using the right mode for blkdev_put().\n\ud83d\udccf Published: 2025-05-02T15:56:04.996Z\n\ud83d\udccf Modified: 2025-05-02T15:56:04.996Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e5febcfbae9396fb3f064a2a14368c3d77d73ad4\n2. https://git.kernel.org/stable/c/d81c6c98d45311a7f3abff4bd5e1eb8e5089972e\n3. https://git.kernel.org/stable/c/428913bce1e67ccb4dae317fd0332545bf8c9233", "creation_timestamp": "2025-05-02T16:16:13.000000Z"}, {"uuid": "f0840d11-acbc-4cc2-b18d-4a4bfc089f78", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53131", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14515", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53131\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: Fix a server shutdown leak\n\nFix a race where kthread_stop() may prevent the threadfn from ever getting\ncalled.  If that happens the svc_rqst will not be cleaned up.\n\ud83d\udccf Published: 2025-05-02T15:56:05.646Z\n\ud83d\udccf Modified: 2025-05-02T15:56:05.646Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ce7dd61e004002bc1c48d1ca47c887f3f3cc7370\n2. https://git.kernel.org/stable/c/ad7e40ee157ba33950a4ccdc284334580da3638d\n3. https://git.kernel.org/stable/c/7a3720361068ab520aed4608bad31ea9a6cc7fe7\n4. https://git.kernel.org/stable/c/f74b3286859463cd63cc9d4aeaabd8b0c640182a\n5. https://git.kernel.org/stable/c/9ca6705d9d609441d34f8b853e1e4a6369b3b171", "creation_timestamp": "2025-05-02T16:16:12.000000Z"}, {"uuid": "c7a23977-c50c-44e5-a6f3-f1c5a197ecec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53132", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14514", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53132\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove()\n\nFree mpi3mr_hba_port at .remove.\n\ud83d\udccf Published: 2025-05-02T15:56:06.341Z\n\ud83d\udccf Modified: 2025-05-02T15:56:06.341Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/f28bdab9e208792212c52b0c232a13bba84cf048\n2. https://git.kernel.org/stable/c/6322569273071745f2dd0c541b154b9666ae7767\n3. https://git.kernel.org/stable/c/d0f3c3728da8af76dfe435f7f0cfa2b9d9e43ef0", "creation_timestamp": "2025-05-02T16:16:11.000000Z"}, {"uuid": "28b71118-24d1-4ae2-881f-8db1b8a4b618", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53134", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14513", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53134\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nbnxt_en: Avoid order-5 memory allocation for TPA data\n\nThe driver needs to keep track of all the possible concurrent TPA (GRO/LRO)\ncompletions on the aggregation ring.  On P5 chips, the maximum number\nof concurrent TPA is 256 and the amount of memory we allocate is order-5\non systems using 4K pages.  Memory allocation failure has been reported:\n\nNetworkManager: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0-1\nCPU: 15 PID: 2995 Comm: NetworkManager Kdump: loaded Not tainted 5.10.156 #1\nHardware name: Dell Inc. PowerEdge R660/0M1CC5, BIOS 0.2.25 08/12/2022\nCall Trace:\n dump_stack+0x57/0x6e\n warn_alloc.cold.120+0x7b/0xdd\n ? _cond_resched+0x15/0x30\n ? __alloc_pages_direct_compact+0x15f/0x170\n __alloc_pages_slowpath.constprop.108+0xc58/0xc70\n __alloc_pages_nodemask+0x2d0/0x300\n kmalloc_order+0x24/0xe0\n kmalloc_order_trace+0x19/0x80\n bnxt_alloc_mem+0x1150/0x15c0 [bnxt_en]\n ? bnxt_get_func_stat_ctxs+0x13/0x60 [bnxt_en]\n __bnxt_open_nic+0x12e/0x780 [bnxt_en]\n bnxt_open+0x10b/0x240 [bnxt_en]\n __dev_open+0xe9/0x180\n __dev_change_flags+0x1af/0x220\n dev_change_flags+0x21/0x60\n do_setlink+0x35c/0x1100\n\nInstead of allocating this big chunk of memory and dividing it up for the\nconcurrent TPA instances, allocate each small chunk separately for each\nTPA instance.  This will reduce it to order-0 allocations.\n\ud83d\udccf Published: 2025-05-02T15:56:07.666Z\n\ud83d\udccf Modified: 2025-05-02T15:56:07.666Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/16f3aae1aa2dd89bc8d073a67f190af580386ae9\n2. https://git.kernel.org/stable/c/d16701a385b54f44bf41ff1d7485e7a11080deb3\n3. https://git.kernel.org/stable/c/20fd0607acbf9770db9b99e3418dd75614f80b6c\n4. https://git.kernel.org/stable/c/fcae40e65802547def39b4deaa2ae38a29864d81\n5. https://git.kernel.org/stable/c/ad529d1fae1565d38f929479d4ea8aea90054bd2\n6. https://git.kernel.org/stable/c/accd7e23693aaaa9aa0d3e9eca0ae77d1be80ab3", "creation_timestamp": "2025-05-02T16:16:10.000000Z"}, {"uuid": "fe555b72-e26e-4b70-be66-2804afa26ec0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53132", "type": "seen", "source": "https://t.me/cvedetector/24355", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53132 - \"Mellanox MPI3MR Linux Kernel Memory Leak\"\", \n  \"Content\": \"CVE ID : CVE-2023-53132 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove()  \n  \nFree mpi3mr_hba_port at .remove. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:40.000000Z"}, {"uuid": "c9b9d8d1-9625-4dcf-a5cb-3a5720d11d01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53134", "type": "seen", "source": "https://t.me/cvedetector/24356", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53134 - \"Broadcom bnxt_en Linux kernel Memory Allocation Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2023-53134 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbnxt_en: Avoid order-5 memory allocation for TPA data  \n  \nThe driver needs to keep track of all the possible concurrent TPA (GRO/LRO)  \ncompletions on the aggregation ring.  On P5 chips, the maximum number  \nof concurrent TPA is 256 and the amount of memory we allocate is order-5  \non systems using 4K pages.  Memory allocation failure has been reported:  \n  \nNetworkManager: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0-1  \nCPU: 15 PID: 2995 Comm: NetworkManager Kdump: loaded Not tainted 5.10.156 #1  \nHardware name: Dell Inc. PowerEdge R660/0M1CC5, BIOS 0.2.25 08/12/2022  \nCall Trace:  \n dump_stack+0x57/0x6e  \n warn_alloc.cold.120+0x7b/0xdd  \n ? _cond_resched+0x15/0x30  \n ? __alloc_pages_direct_compact+0x15f/0x170  \n __alloc_pages_slowpath.constprop.108+0xc58/0xc70  \n __alloc_pages_nodemask+0x2d0/0x300  \n kmalloc_order+0x24/0xe0  \n kmalloc_order_trace+0x19/0x80  \n bnxt_alloc_mem+0x1150/0x15c0 [bnxt_en]  \n ? bnxt_get_func_stat_ctxs+0x13/0x60 [bnxt_en]  \n __bnxt_open_nic+0x12e/0x780 [bnxt_en]  \n bnxt_open+0x10b/0x240 [bnxt_en]  \n __dev_open+0xe9/0x180  \n __dev_change_flags+0x1af/0x220  \n dev_change_flags+0x21/0x60  \n do_setlink+0x35c/0x1100  \n  \nInstead of allocating this big chunk of memory and dividing it up for the  \nconcurrent TPA instances, allocate each small chunk separately for each  \nTPA instance.  This will reduce it to order-0 allocations. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:41.000000Z"}, {"uuid": "292c6d07-4f06-4242-9d2c-a4e0c32fd011", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53137", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14512", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53137\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\next4: Fix possible corruption when moving a directory\n\nWhen we are renaming a directory to a different directory, we need to\nupdate '..' entry in the moved directory. However nothing prevents moved\ndirectory from being modified and even converted from the inline format\nto the normal format. When such race happens the rename code gets\nconfused and we crash. Fix the problem by locking the moved directory.\n\ud83d\udccf Published: 2025-05-02T15:56:09.582Z\n\ud83d\udccf Modified: 2025-05-02T15:56:09.582Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/8dac5a63cf79707b547ea3d425fead5f4482198f\n2. https://git.kernel.org/stable/c/0c440f14558bfacd22c6935ae1fd4b2a09e96b5d\n3. https://git.kernel.org/stable/c/c50fc503ee1b97f12c98e26afc39fdaebebcf04f\n4. https://git.kernel.org/stable/c/b0bb13612292ca90fa4c2a7e425375649bc50d3e\n5. https://git.kernel.org/stable/c/291cd19d107e197306869cb3237c1bba62d13182\n6. https://git.kernel.org/stable/c/0813299c586b175d7edb25f56412c54b812d0379", "creation_timestamp": "2025-05-02T16:16:08.000000Z"}, {"uuid": "f54e92df-3a73-4811-a5ec-d322dd8387a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53139", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14511", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53139\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnfc: fdp: add null check of devm_kmalloc_array in fdp_nci_i2c_read_device_properties\n\ndevm_kmalloc_array may fails, *fw_vsc_cfg might be null and cause\nout-of-bounds write in device_property_read_u8_array later.\n\ud83d\udccf Published: 2025-05-02T15:56:11.007Z\n\ud83d\udccf Modified: 2025-05-02T15:56:11.007Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ad11b872bc9b5d27e56183c6b01f9218c85395d2\n2. https://git.kernel.org/stable/c/98f49e693e02c1dafd5786be3468657840dd6f06\n3. https://git.kernel.org/stable/c/0a3664a1058d4b2b1ea2112cc275ca47fba7fc08\n4. https://git.kernel.org/stable/c/80be62358fa5507cefbaa067c7e6648401f2c3da\n5. https://git.kernel.org/stable/c/4357bbb921fe9e81d0fd9f70d669d1f177d8380e\n6. https://git.kernel.org/stable/c/ce93f1afc05941a572f5a69e2ed4012af905a693\n7. https://git.kernel.org/stable/c/27824b2f98818215adc9661e563252c48dab1a13\n8. https://git.kernel.org/stable/c/11f180a5d62a51b484e9648f9b310e1bd50b1a57", "creation_timestamp": "2025-05-02T16:16:07.000000Z"}, {"uuid": "cd937607-7ad1-4484-96b3-6073d589eabc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53135", "type": "seen", "source": "https://t.me/cvedetector/24357", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53135 - Riscv Linux Kernel Stack Out-of-Bounds Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53135 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nriscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode  \n  \nWhen CONFIG_FRAME_POINTER is unset, the stack unwinding function  \nwalk_stackframe randomly reads the stack and then, when KASAN is enabled,  \nit can lead to the following backtrace:  \n  \n[    0.000000] ==================================================================  \n[    0.000000] BUG: KASAN: stack-out-of-bounds in walk_stackframe+0xa6/0x11a  \n[    0.000000] Read of size 8 at addr ffffffff81807c40 by task swapper/0  \n[    0.000000]  \n[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 6.2.0-12919-g24203e6db61f #43  \n[    0.000000] Hardware name: riscv-virtio,qemu (DT)  \n[    0.000000] Call Trace:  \n[    0.000000] [] walk_stackframe+0x0/0x11a  \n[    0.000000] [] init_param_lock+0x26/0x2a  \n[    0.000000] [] walk_stackframe+0xa2/0x11a  \n[    0.000000] [] dump_stack_lvl+0x22/0x36  \n[    0.000000] [] print_report+0x198/0x4a8  \n[    0.000000] [] init_param_lock+0x26/0x2a  \n[    0.000000] [] walk_stackframe+0xa2/0x11a  \n[    0.000000] [] kasan_report+0x9a/0xc8  \n[    0.000000] [] walk_stackframe+0xa2/0x11a  \n[    0.000000] [] walk_stackframe+0xa2/0x11a  \n[    0.000000] [] desc_make_final+0x80/0x84  \n[    0.000000] [] stack_trace_save+0x88/0xa6  \n[    0.000000] [] filter_irq_stacks+0x72/0x76  \n[    0.000000] [] devkmsg_read+0x32a/0x32e  \n[    0.000000] [] kasan_save_stack+0x28/0x52  \n[    0.000000] [] desc_make_final+0x7c/0x84  \n[    0.000000] [] stack_trace_save+0x84/0xa6  \n[    0.000000] [] kasan_set_track+0x12/0x20  \n[    0.000000] [] __kasan_slab_alloc+0x58/0x5e  \n[    0.000000] [] __kmem_cache_create+0x21e/0x39a  \n[    0.000000] [] create_boot_cache+0x70/0x9c  \n[    0.000000] [] kmem_cache_init+0x6c/0x11e  \n[    0.000000] [] mm_init+0xd8/0xfe  \n[    0.000000] [] start_kernel+0x190/0x3ca  \n[    0.000000]  \n[    0.000000] The buggy address belongs to stack of task swapper/0  \n[    0.000000]  and is located at offset 0 in frame:  \n[    0.000000]  stack_trace_save+0x0/0xa6  \n[    0.000000]  \n[    0.000000] This frame has 1 object:  \n[    0.000000]  [32, 56) 'c'  \n[    0.000000]  \n[    0.000000] The buggy address belongs to the physical page:  \n[    0.000000] page:(____ptrval____) refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x81a07  \n[    0.000000] flags: 0x1000(reserved|zone=0)  \n[    0.000000] raw: 0000000000001000 ff600003f1e3d150 ff600003f1e3d150 0000000000000000  \n[    0.000000] raw: 0000000000000000 0000000000000000 00000001ffffffff  \n[    0.000000] page dumped because: kasan: bad access detected  \n[    0.000000]  \n[    0.000000] Memory state around the buggy address:  \n[    0.000000]  ffffffff81807b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  \n[    0.000000]  ffffffff81807b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  \n[    0.000000] >ffffffff81807c00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 f3  \n[    0.000000]                                            ^  \n[    0.000000]  ffffffff81807c80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00  \n[    0.000000]  ffffffff81807d00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  \n[    0.000000] ==================================================================  \n  \nFix that by using READ_ONCE_NOCHECK when reading the stack in imprecise  \nmode. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:42.000000Z"}, {"uuid": "5251edb4-d082-49a6-bda0-f2aca0b26ceb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53136", "type": "seen", "source": "https://t.me/cvedetector/24358", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53136 - Linux af_unix Struct PID Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53136 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \naf_unix: fix struct pid leaks in OOB support  \n  \nsyzbot reported struct pid leak [1].  \n  \nIssue is that queue_oob() calls maybe_add_creds() which potentially  \nholds a reference on a pid.  \n  \nBut skb->destructor is not set (either directly or by calling  \nunix_scm_to_skb())  \n  \nThis means that subsequent kfree_skb() or consume_skb() would leak  \nthis reference.  \n  \nIn this fix, I chose to fully support scm even for the OOB message.  \n  \n[1]  \nBUG: memory leak  \nunreferenced object 0xffff8881053e7f80 (size 128):  \ncomm \"syz-executor242\", pid 5066, jiffies 4294946079 (age 13.220s)  \nhex dump (first 32 bytes):  \n01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................  \n00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................  \nbacktrace:  \n[] alloc_pid+0x6a/0x560 kernel/pid.c:180  \n[] copy_process+0x169f/0x26c0 kernel/fork.c:2285  \n[] kernel_clone+0xf7/0x610 kernel/fork.c:2684  \n[] __do_sys_clone+0x7c/0xb0 kernel/fork.c:2825  \n[] do_syscall_x64 arch/x86/entry/common.c:50 [inline]  \n[] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80  \n[] 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\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:46.000000Z"}, {"uuid": "f19abd82-2a86-40bd-9055-ad7178aba184", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53137", "type": "seen", "source": "https://t.me/cvedetector/24359", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53137 - Linux Kernel Ext4 Directory Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53137 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \next4: Fix possible corruption when moving a directory  \n  \nWhen we are renaming a directory to a different directory, we need to  \nupdate '..' entry in the moved directory. However nothing prevents moved  \ndirectory from being modified and even converted from the inline format  \nto the normal format. When such race happens the rename code gets  \nconfused and we crash. Fix the problem by locking the moved directory. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:46.000000Z"}, {"uuid": "5d83c7bc-7409-47cc-b569-84fa25aa5818", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53138", "type": "seen", "source": "https://t.me/cvedetector/24360", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53138 - Cisco CAIF Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53138 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: caif: Fix use-after-free in cfusbl_device_notify()  \n  \nsyzbot reported use-after-free in cfusbl_device_notify() [1].  This  \ncauses a stack trace like below:  \n  \nBUG: KASAN: use-after-free in cfusbl_device_notify+0x7c9/0x870 net/caif/caif_usb.c:138  \nRead of size 8 at addr ffff88807ac4e6f0 by task kworker/u4:6/1214  \n  \nCPU: 0 PID: 1214 Comm: kworker/u4:6 Not tainted 5.19.0-rc3-syzkaller-00146-g92f20ff72066 #0  \nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011  \nWorkqueue: netns cleanup_net  \nCall Trace:  \n   \n __dump_stack lib/dump_stack.c:88 [inline]  \n dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106  \n print_address_description.constprop.0.cold+0xeb/0x467 mm/kasan/report.c:313  \n print_report mm/kasan/report.c:429 [inline]  \n kasan_report.cold+0xf4/0x1c6 mm/kasan/report.c:491  \n cfusbl_device_notify+0x7c9/0x870 net/caif/caif_usb.c:138  \n notifier_call_chain+0xb5/0x200 kernel/notifier.c:87  \n call_netdevice_notifiers_info+0xb5/0x130 net/core/dev.c:1945  \n call_netdevice_notifiers_extack net/core/dev.c:1983 [inline]  \n call_netdevice_notifiers net/core/dev.c:1997 [inline]  \n netdev_wait_allrefs_any net/core/dev.c:10227 [inline]  \n netdev_run_todo+0xbc0/0x10f0 net/core/dev.c:10341  \n default_device_exit_batch+0x44e/0x590 net/core/dev.c:11334  \n ops_exit_list+0x125/0x170 net/core/net_namespace.c:167  \n cleanup_net+0x4ea/0xb00 net/core/net_namespace.c:594  \n process_one_work+0x996/0x1610 kernel/workqueue.c:2289  \n worker_thread+0x665/0x1080 kernel/workqueue.c:2436  \n kthread+0x2e9/0x3a0 kernel/kthread.c:376  \n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302  \n   \n  \nWhen unregistering a net device, unregister_netdevice_many_notify()  \nsets the device's reg_state to NETREG_UNREGISTERING, calls notifiers  \nwith NETDEV_UNREGISTER, and adds the device to the todo list.  \n  \nLater on, devices in the todo list are processed by netdev_run_todo().  \nnetdev_run_todo() waits devices' reference count become 1 while  \nrebdoadcasting NETDEV_UNREGISTER notification.  \n  \nWhen cfusbl_device_notify() is called with NETDEV_UNREGISTER multiple  \ntimes, the parent device might be freed.  This could cause UAF.  \nProcessing NETDEV_UNREGISTER multiple times also causes inbalance of  \nreference count for the module.  \n  \nThis patch fixes the issue by accepting only first NETDEV_UNREGISTER  \nnotification. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:47.000000Z"}, {"uuid": "fc88a672-b24e-48d5-a51c-e398fa50044c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53139", "type": "seen", "source": "https://t.me/cvedetector/24361", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53139 - Linux Kernel NFC fdp Null Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2023-53139 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfc: fdp: add null check of devm_kmalloc_array in fdp_nci_i2c_read_device_properties  \n  \ndevm_kmalloc_array may fails, *fw_vsc_cfg might be null and cause  \nout-of-bounds write in device_property_read_u8_array later. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:48.000000Z"}, {"uuid": "480fa9de-cd57-4c71-a8ce-3c39218f078b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53131", "type": "seen", "source": "https://t.me/cvedetector/24363", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53131 - SunRPC Thread Shutdown Leak\", \n  \"Content\": \"CVE ID : CVE-2023-53131 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nSUNRPC: Fix a server shutdown leak  \n  \nFix a race where kthread_stop() may prevent the threadfn from ever getting  \ncalled.  If that happens the svc_rqst will not be cleaned up. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:53.000000Z"}, {"uuid": "b251ea8c-f604-4f65-bfc2-510bc70323e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53133", "type": "seen", "source": "https://t.me/cvedetector/24364", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53133 - Apache Linux bpf Infinite Loop Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53133 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()  \n  \nWhen the buffer length of the recvmsg system call is 0, we got the  \nflollowing soft lockup problem:  \n  \nwatchdog: BUG: soft lockup - CPU#3 stuck for 27s! [a.out:6149]  \nCPU: 3 PID: 6149 Comm: a.out Kdump: loaded Not tainted 6.2.0+ #30  \nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014  \nRIP: 0010:remove_wait_queue+0xb/0xc0  \nCode: 5e 41 5f c3 cc cc cc cc 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 57 <4156 41 55 41 54 55 48 89 fd 53 48 89 f3 4c 8d 6b 18 4c 8d 73 20  \nRSP: 0018:ffff88811b5978b8 EFLAGS: 00000246  \nRAX: 0000000000000000 RBX: ffff88811a7d3780 RCX: ffffffffb7a4d768  \nRDX: dffffc0000000000 RSI: ffff88811b597908 RDI: ffff888115408040  \nRBP: 1ffff110236b2f1b R08: 0000000000000000 R09: ffff88811a7d37e7  \nR10: ffffed10234fa6fc R11: 0000000000000001 R12: ffff88811179b800  \nR13: 0000000000000001 R14: ffff88811a7d38a8 R15: ffff88811a7d37e0  \nFS:  00007f6fb5398740(0000) GS:ffff888237180000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 0000000020000000 CR3: 000000010b6ba002 CR4: 0000000000370ee0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \nCall Trace:  \n   \n tcp_msg_wait_data+0x279/0x2f0  \n tcp_bpf_recvmsg_parser+0x3c6/0x490  \n inet_recvmsg+0x280/0x290  \n sock_recvmsg+0xfc/0x120  \n ____sys_recvmsg+0x160/0x3d0  \n ___sys_recvmsg+0xf0/0x180  \n __sys_recvmsg+0xea/0x1a0  \n do_syscall_64+0x3f/0x90  \n entry_SYSCALL_64_after_hwframe+0x72/0xdc  \n  \nThe logic in tcp_bpf_recvmsg_parser is as follows:  \n  \nmsg_bytes_ready:  \n copied = sk_msg_recvmsg(sk, psock, msg, len, flags);  \n if (!copied) {  \n  wait data;  \n  goto msg_bytes_ready;  \n }  \n  \nIn this case, \"copied\" always is 0, the infinite loop occurs.  \n  \nAccording to the Linux system call man page, 0 should be returned in this  \ncase. Therefore, in tcp_bpf_recvmsg_parser(), if the length is 0, directly  \nreturn. Also modify several other functions with the same problem. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:07:53.000000Z"}]}