{"vulnerability": "CVE-2024-5793", "sightings": [{"uuid": "143e0070-9960-4bbd-8fde-ad4816f015e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57931", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866248257509687", "content": "", "creation_timestamp": "2025-01-21T12:04:24.022420Z"}, {"uuid": "a430ef56-0864-4eb4-8be1-ccdca9d1ac44", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57932", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866248271940250", "content": "", "creation_timestamp": "2025-01-21T12:04:24.259788Z"}, {"uuid": "36fe8413-05a1-4111-9bf4-513dacc43cb2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57933", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatfv3xhe2t", "content": "", "creation_timestamp": "2025-01-21T12:16:12.021073Z"}, {"uuid": "a3f88e38-e8a3-4ce3-8f9e-cf8f44f7969c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57937", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatg6kq4h2j", "content": "", "creation_timestamp": "2025-01-21T12:16:21.853933Z"}, {"uuid": "eeeb70eb-be69-4de4-bf62-f1cdf66ca067", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57938", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatgas2cn2j", "content": "", "creation_timestamp": "2025-01-21T12:16:24.255191Z"}, {"uuid": "11732a3f-18ea-49c9-a6cc-ff3841aac4cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57934", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866307303997674", "content": "", "creation_timestamp": "2025-01-21T12:19:24.976200Z"}, {"uuid": "4999e3e9-61ab-4519-8305-b70d16c47f5c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57931", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtarh6d2h", "content": "", "creation_timestamp": "2025-01-21T12:59:28.689724Z"}, {"uuid": "860efe57-9fd3-4b41-aa58-147190cc4c3a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57939", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgawqcdubk2p", "content": "", "creation_timestamp": "2025-01-21T13:15:42.934575Z"}, {"uuid": "825d953b-2654-49d5-9772-3c572eaea1cb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57933", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866248305930881", "content": "", "creation_timestamp": "2025-01-21T12:04:24.645070Z"}, {"uuid": "97eb29ae-3177-48f3-ac86-e4ae985371da", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57935", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatfzjxfm2t", "content": "", "creation_timestamp": "2025-01-21T12:16:16.692604Z"}, {"uuid": "87e9d52a-356a-4f52-b93f-850710911f3b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57935", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866307317944200", "content": "", "creation_timestamp": "2025-01-21T12:19:25.435155Z"}, {"uuid": "1cd4dc61-628f-4735-9f0c-8b272ca2d280", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57933", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtan6gj2g", "content": "", "creation_timestamp": "2025-01-21T12:59:28.142522Z"}, {"uuid": "192c3bec-ed80-45f9-8afb-3989484bc6a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57932", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtblwkx2b", "content": "", "creation_timestamp": "2025-01-21T12:59:32.549904Z"}, {"uuid": "3f03e374-0a45-4b10-96ea-c0dc525908a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57930", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatfncnv32e", "content": "", "creation_timestamp": "2025-01-21T12:16:04.209355Z"}, {"uuid": "933a5d88-6941-4d72-b767-cf426b5c9f5a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57934", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatfxddsa2p", "content": "", "creation_timestamp": "2025-01-21T12:16:14.353461Z"}, {"uuid": "99f2873f-12f7-412a-af66-ca0d03820600", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57936", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatg3wgki2f", "content": "", "creation_timestamp": "2025-01-21T12:16:19.235956Z"}, {"uuid": "bbbdb131-d427-439a-be46-11407b0b216d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57936", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866307332160636", "content": "", "creation_timestamp": "2025-01-21T12:19:25.582102Z"}, {"uuid": "38a6f7d4-13fe-4d22-8144-7bf08f3d74d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57939", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgay2shdfz2e", "content": "", "creation_timestamp": "2025-01-21T13:39:29.104225Z"}, {"uuid": "076fcfe0-109b-4b3d-aecf-66fde2e744ce", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57931", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatfqd7mm2n", "content": "", "creation_timestamp": "2025-01-21T12:16:06.953521Z"}, {"uuid": "8f8bc1cf-283f-4517-9aa5-b6ac9654fadb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57939", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866341963235598", "content": "", "creation_timestamp": "2025-01-21T12:28:13.921944Z"}, {"uuid": "a0a15b7b-d975-4e1f-9351-989b6fd2c448", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57934", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtav4t32w", "content": "", "creation_timestamp": "2025-01-21T12:59:29.294405Z"}, {"uuid": "067fc916-88f9-4374-b69b-b80815bdb92b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57937", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtaylgh2b", "content": "", "creation_timestamp": "2025-01-21T12:59:29.813688Z"}, {"uuid": "9168e5f1-7f8d-4242-8a0a-3d4e34a7f665", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57935", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtb4pir2g", "content": "", "creation_timestamp": "2025-01-21T12:59:30.374254Z"}, {"uuid": "3b6ced0a-6021-4e3c-a11c-5d0a658bc156", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57938", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtbdxx32h", "content": "", "creation_timestamp": "2025-01-21T12:59:31.503616Z"}, {"uuid": "24f0c5b9-813c-4b90-9d4d-3a3997d84bd2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57930", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866248242945246", "content": "", "creation_timestamp": "2025-01-21T12:04:23.882592Z"}, {"uuid": "d0d0a83b-4b15-417d-a58e-889d551b62a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57932", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgatfsnlt72j", "content": "", "creation_timestamp": "2025-01-21T12:16:09.476540Z"}, {"uuid": "b91bc114-0c07-49e2-a824-f95ae64d3078", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57930", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtad6kh2r", "content": "", "creation_timestamp": "2025-01-21T12:59:27.421272Z"}, {"uuid": "40a28979-daa6-4014-b806-04fb40ab00bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57936", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgavtbphk72r", "content": "", "creation_timestamp": "2025-01-21T12:59:33.099730Z"}, {"uuid": "66299ded-263a-43c8-9f71-a8ba142c1559", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57939", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113866581148390646", "content": "", "creation_timestamp": "2025-01-21T13:29:03.380872Z"}, {"uuid": "d133ca53-d0a2-4a4e-870e-b600b1af464b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57931", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113866636248516929", "content": "", "creation_timestamp": "2025-01-21T13:43:04.205677Z"}, {"uuid": "33b78c0a-4bfc-4b63-ba2e-0bf98de48e8d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57936", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113866740466951809", "content": "", "creation_timestamp": "2025-01-21T14:09:34.830463Z"}, {"uuid": "8de5b4a4-d30f-4086-9dba-92651ebac8bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-57939", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "d6524a01-15c1-4e07-ae23-710cb62bfa8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57938", "type": "seen", "source": "https://t.me/cvedetector/15927", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57938 - Linux SCTP Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57938 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet/sctp: Prevent autoclose integer overflow in sctp_association_init()  \n  \nWhile by default max_autoclose equals to INT_MAX / HZ, one may set  \nnet.sctp.max_autoclose to UINT_MAX. There is code in  \nsctp_association_init() that can consequently trigger overflow. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:36:55.000000Z"}, {"uuid": "0272f08f-4511-4c9e-8cbb-8b53d8ce41b3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57933", "type": "seen", "source": "https://t.me/cvedetector/15933", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57933 - Linux Kernel GVE XSK Queue Guard\", \n  \"Content\": \"CVE ID : CVE-2024-57933 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ngve: guard XSK operations on the existence of queues  \n  \nThis patch predicates the enabling and disabling of XSK pools on the  \nexistence of queues. As it stands, if the interface is down, disabling  \nor enabling XSK pools would result in a crash, as the RX queue pointer  \nwould be NULL. XSK pool registration will occur as part of the next  \ninterface up.  \n  \nSimilarly, xsk_wakeup needs be guarded against queues disappearing  \nwhile the function is executing, so a check against the  \nGVE_PRIV_FLAGS_NAPI_ENABLED flag is added to synchronize with the  \ndisabling of the bit and the synchronize_net() in gve_turndown. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:37:05.000000Z"}, {"uuid": "27994e53-2067-4f1f-be51-8d0633b38c68", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57936", "type": "seen", "source": "https://t.me/cvedetector/15925", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57936 - NetXtreme RDMA Linux Kernel Buffer Overflowulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57936 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nRDMA/bnxt_re: Fix max SGEs for the Work Request  \n  \nGen P7 supports up to 13 SGEs for now. WQE software structure  \ncan hold only 6 now. Since the max send sge is reported as  \n13, the stack can give requests up to 13 SGEs. This is causing  \ntraffic failures and system crashes.  \n  \nUse the define for max SGE supported for variable size. This  \nwill work for both static and variable WQEs. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:36:53.000000Z"}, {"uuid": "bb04e22b-a3f6-4236-a831-6672e9799cf1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57934", "type": "seen", "source": "https://t.me/cvedetector/15924", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57934 - \"Linux_kernel fgraph_array READ_ONCE NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-57934 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfgraph: Add READ_ONCE() when accessing fgraph_array[]  \n  \nIn __ftrace_return_to_handler(), a loop iterates over the fgraph_array[]  \nelements, which are fgraph_ops. The loop checks if an element is a  \nfgraph_stub to prevent using a fgraph_stub afterward.  \n  \nHowever, if the compiler reloads fgraph_array[] after this check, it might  \nrace with an update to fgraph_array[] that introduces a fgraph_stub. This  \ncould result in the stub being processed, but the stub contains a null  \n\"func_hash\" field, leading to a NULL pointer dereference.  \n  \nTo ensure that the gops compared against the fgraph_stub matches the gops  \nprocessed later, add a READ_ONCE(). A similar patch appears in commit  \n63a8dfb (\"function_graph: Add READ_ONCE() when accessing fgraph_array[]\"). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:36:52.000000Z"}, {"uuid": "16b13a49-b590-42d1-8d53-312a146e2c61", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57935", "type": "seen", "source": "https://t.me/cvedetector/15923", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57935 - Intel RDMA HNS Invalid Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2024-57935 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nRDMA/hns: Fix accessing invalid dip_ctx during destroying QP  \n  \nIf it fails to modify QP to RTR, dip_ctx will not be attached. And  \nduring detroying QP, the invalid dip_ctx pointer will be accessed. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:36:52.000000Z"}, {"uuid": "85a13528-1474-4895-b808-c5673405876a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57932", "type": "seen", "source": "https://t.me/cvedetector/15932", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57932 - Apache Linux Kernel Divide By Zero and Null Pointer Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57932 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ngve: guard XDP xmit NDO on existence of xdp queues  \n  \nIn GVE, dedicated XDP queues only exist when an XDP program is installed  \nand the interface is up. As such, the NDO XDP XMIT callback should  \nreturn early if either of these conditions are false.  \n  \nIn the case of no loaded XDP program, priv->num_xdp_queues=0 which can  \ncause a divide-by-zero error, and in the case of interface down,  \nnum_xdp_queues remains untouched to persist XDP queue count for the next  \ninterface up, but the TX pointer itself would be NULL.  \n  \nThe XDP xmit callback also needs to synchronize with a device  \ntransitioning from open to close. This synchronization will happen via  \nthe GVE_PRIV_FLAGS_NAPI_ENABLED bit along with a synchronize_net() call,  \nwhich waits for any RCU critical sections at call-time to complete. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:37:01.000000Z"}, {"uuid": "f6d7f2b8-c434-498f-9b4b-01041bea72e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57931", "type": "seen", "source": "https://t.me/cvedetector/15931", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57931 - Linux SELinux Unknown Extended Permissions Ignorance Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57931 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nselinux: ignore unknown extended permissions  \n  \nWhen evaluating extended permissions, ignore unknown permissions instead  \nof calling BUG(). This commit ensures that future permissions can be  \nadded without interfering with older kernels. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:37:00.000000Z"}, {"uuid": "21c3887e-ff3d-4d5f-8cad-62fe4c6eb629", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57930", "type": "seen", "source": "https://t.me/cvedetector/15930", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57930 - Linux Kernel Array Dereference Vulnerability in Tracing\", \n  \"Content\": \"CVE ID : CVE-2024-57930 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntracing: Have process_string() also allow arrays  \n  \nIn order to catch a common bug where a TRACE_EVENT() TP_fast_assign()  \nassigns an address of an allocated string to the ring buffer and then  \nreferences it in TP_printk(), which can be executed hours later when the  \nstring is free, the function test_event_printk() runs on all events as  \nthey are registered to make sure there's no unwanted dereferencing.  \n  \nIt calls process_string() to handle cases in TP_printk() format that has  \n\"%s\". It returns whether or not the string is safe. But it can have some  \nfalse positives.  \n  \nFor instance, xe_bo_move() has:  \n  \n TP_printk(\"move_lacks_source:%s, migrate object %p [size %zu] from %s to %s device_id:%s\",  \n            __entry->move_lacks_source ? \"yes\" : \"no\", __entry->bo, __entry->size,  \n            xe_mem_type_to_name[__entry->old_placement],  \n            xe_mem_type_to_name[__entry->new_placement], __get_str(device_id))  \n  \nWhere the \"%s\" references into xe_mem_type_to_name[]. This is an array of  \npointers that should be safe for the event to access. Instead of flagging  \nthis as a bad reference, if a reference points to an array, where the  \nrecord field is the index, consider it safe. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:37:00.000000Z"}, {"uuid": "ec954798-3a4f-4298-9d0c-7efce7dc847c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57937", "type": "seen", "source": "https://t.me/cvedetector/15926", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57937 - \"Linux Kernel Memfd F_SEAL_WRITE Read-Only Mapping Reinstatement\"\", \n  \"Content\": \"CVE ID : CVE-2024-57937 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmm: reinstate ability to map write-sealed memfd mappings read-only  \n  \nPatch series \"mm: reinstate ability to map write-sealed memfd mappings  \nread-only\".  \n  \nIn commit 158978945f31 (\"mm: perform the mapping_map_writable() check  \nafter call_mmap()\") (and preceding changes in the same series) it became  \npossible to mmap() F_SEAL_WRITE sealed memfd mappings read-only.  \n  \nCommit 5de195060b2e (\"mm: resolve faulty mmap_region() error path  \nbehaviour\") unintentionally undid this logic by moving the  \nmapping_map_writable() check before the shmem_mmap() hook is invoked,  \nthereby regressing this change.  \n  \nThis series reworks how we both permit write-sealed mappings being mapped  \nread-only and disallow mprotect() from undoing the write-seal, fixing this  \nregression.  \n  \nWe also add a regression test to ensure that we do not accidentally  \nregress this in future.  \n  \nThanks to Julian Orth for reporting this regression.  \n  \n  \nThis patch (of 2):  \n  \nIn commit 158978945f31 (\"mm: perform the mapping_map_writable() check  \nafter call_mmap()\") (and preceding changes in the same series) it became  \npossible to mmap() F_SEAL_WRITE sealed memfd mappings read-only.  \n  \nThis was previously unnecessarily disallowed, despite the man page  \ndocumentation indicating that it would be, thereby limiting the usefulness  \nof F_SEAL_WRITE logic.  \n  \nWe fixed this by adapting logic that existed for the F_SEAL_FUTURE_WRITE  \nseal (one which disallows future writes to the memfd) to also be used for  \nF_SEAL_WRITE.  \n  \nFor background - the F_SEAL_FUTURE_WRITE seal clears VM_MAYWRITE for a  \nread-only mapping to disallow mprotect() from overriding the seal - an  \noperation performed by seal_check_write(), invoked from shmem_mmap(), the  \nf_op->mmap() hook used by shmem mappings.  \n  \nBy extending this to F_SEAL_WRITE and critically - checking  \nmapping_map_writable() to determine if we may map the memfd AFTER we  \ninvoke shmem_mmap() - the desired logic becomes possible.  This is because  \nmapping_map_writable() explicitly checks for VM_MAYWRITE, which we will  \nhave cleared.  \n  \nCommit 5de195060b2e (\"mm: resolve faulty mmap_region() error path  \nbehaviour\") unintentionally undid this logic by moving the  \nmapping_map_writable() check before the shmem_mmap() hook is invoked,  \nthereby regressing this change.  \n  \nWe reinstate this functionality by moving the check out of shmem_mmap()  \nand instead performing it in do_mmap() at the point at which VMA flags are  \nbeing determined, which seems in any case to be a more appropriate place  \nin which to make this determination.  \n  \nIn order to achieve this we rework memfd seal logic to allow us access to  \nthis information using existing logic and eliminate the clearing of  \nVM_MAYWRITE from seal_check_write() which we are performing in do_mmap()  \ninstead. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:36:54.000000Z"}, {"uuid": "f68a18a0-cf1f-4507-b138-2a5688f6d0ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57939", "type": "seen", "source": "https://t.me/cvedetector/15951", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57939 - RISC-V Linux Sleeping in Invalid Context Memory Corruption\", \n  \"Content\": \"CVE ID : CVE-2024-57939 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nriscv: Fix sleeping in invalid context in die()  \n  \ndie() can be called in exception handler, and therefore cannot sleep.  \nHowever, die() takes spinlock_t which can sleep with PREEMPT_RT enabled.  \nThat causes the following warning:  \n  \nBUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48  \nin_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 285, name: mutex  \npreempt_count: 110001, expected: 0  \nRCU nest depth: 0, expected: 0  \nCPU: 0 UID: 0 PID: 285 Comm: mutex Not tainted 6.12.0-rc7-00022-ge19049cf7d56-dirty #234  \nHardware name: riscv-virtio,qemu (DT)  \nCall Trace:  \n    dump_backtrace+0x1c/0x24  \n    show_stack+0x2c/0x38  \n    dump_stack_lvl+0x5a/0x72  \n    dump_stack+0x14/0x1c  \n    __might_resched+0x130/0x13a  \n    rt_spin_lock+0x2a/0x5c  \n    die+0x24/0x112  \n    do_trap_insn_illegal+0xa0/0xea  \n    _new_vmalloc_restore_context_a0+0xcc/0xd8  \nOops - illegal instruction [#1]  \n  \nSwitch to use raw_spinlock_t, which does not sleep even with PREEMPT_RT  \nenabled. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T15:17:35.000000Z"}, {"uuid": "400a72f5-9cec-4da2-aebb-aca200ea8142", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-5793", "type": "seen", "source": "https://t.me/cvedetector/223", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-5793 - The Houzez Theme - Functionality plugin for WordPr\", \n  \"Content\": \"CVE ID : CVE-2024-5793 \nPublished : July 9, 2024, 2:15 a.m. | 25\u00a0minutes ago \nDescription : The Houzez Theme - Functionality plugin for WordPress is vulnerable to SQL Injection via the \u2018currency_code\u2019 parameter in all versions up to, and including, 3.2.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Custom-level (seller) access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. \nSeverity: 8.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-09T04:42:36.000000Z"}]}