{"vulnerability": "cve-2025-3798", "sightings": [{"uuid": "b46a8287-6058-4e0d-aaca-d0a3757c6960", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37980", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/17036", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37980\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nblock: fix resource leak in blk_register_queue() error path\n\nWhen registering a queue fails after blk_mq_sysfs_register() is\nsuccessful but the function later encounters an error, we need\nto clean up the blk_mq_sysfs resources.\n\nAdd the missing blk_mq_sysfs_unregister() call in the error path\nto properly clean up these resources and prevent a memory leak.\n\ud83d\udccf Published: 2025-05-20T16:58:22.720Z\n\ud83d\udccf Modified: 2025-05-20T16:58:22.720Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/549cbbd14bbec12469ceb279b79c763c8a24224e\n2. https://git.kernel.org/stable/c/41e43134ddda35949974be40520460a12dda3502\n3. https://git.kernel.org/stable/c/55a7bb2708f7c7c5b366d4e40916113168a3824c\n4. https://git.kernel.org/stable/c/40f2eb9b531475dd01b683fdaf61ca3cfd03a51e", "creation_timestamp": "2025-05-20T17:45:52.000000Z"}, {"uuid": "34063cd9-6867-4b22-9558-3c2f931b7f47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37982", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/17034", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37982\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wl1251: fix memory leak in wl1251_tx_work\n\nThe skb dequeued from tx_queue is lost when wl1251_ps_elp_wakeup fails\nwith a -ETIMEDOUT error. Fix that by queueing the skb back to tx_queue.\n\ud83d\udccf Published: 2025-05-20T16:58:23.861Z\n\ud83d\udccf Modified: 2025-05-20T16:58:23.861Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/13c9744c1bcdb5de4e7dc1a78784788ecec52add\n2. https://git.kernel.org/stable/c/f08448a885403722c5c77dae51964badfcb69495\n3. https://git.kernel.org/stable/c/2996144be660d930d5e394652abe08fe89dbe00e\n4. https://git.kernel.org/stable/c/8fd4b9551af214d037fbc9d8e179840b8b917841\n5. https://git.kernel.org/stable/c/4a43fd36710669d67dbb5c16287a58412582ca26\n6. https://git.kernel.org/stable/c/52f224009ce1e44805e6ff3ffc2a06af9c1c3c5b\n7. https://git.kernel.org/stable/c/5a90c29d0204c5ffc45b43b4eced6eef0e19a33a\n8. https://git.kernel.org/stable/c/a0f0dc96de03ffeefc2a177b7f8acde565cb77f4", "creation_timestamp": "2025-05-20T17:45:45.000000Z"}, {"uuid": "d889df41-5c1d-4acd-a561-a4ec265512ce", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37983", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/17032", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37983\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nqibfs: fix _another_ leak\n\nfailure to allocate inode => leaked dentry...\n\nthis one had been there since the initial merge; to be fair,\nif we are that far OOM, the odds of failing at that particular\nallocation are low...\n\ud83d\udccf Published: 2025-05-20T17:09:17.666Z\n\ud83d\udccf Modified: 2025-05-20T17:09:17.666Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/5e280cce3a29b7fe7b828c6ccd5aa5ba87ceb6b6\n2. https://git.kernel.org/stable/c/3c2fde33e3e505dfd1a895d1f24bad650c655e14\n3. https://git.kernel.org/stable/c/5fe708c5e3c8b2152c6caaa67243e431a5d6cca3\n4. https://git.kernel.org/stable/c/545defa656568c74590317cd30068f85134a8216\n5. https://git.kernel.org/stable/c/5d53e88d8370b9ab14dd830abb410d9a2671edb6\n6. https://git.kernel.org/stable/c/47ab2caba495c1d6a899d284e541a8df656dcfe9\n7. https://git.kernel.org/stable/c/24faa6ea274a2b96d0a78a0996c3137c2b2a65f0\n8. https://git.kernel.org/stable/c/bdb43af4fdb39f844ede401bdb1258f67a580a27", "creation_timestamp": "2025-05-20T17:45:43.000000Z"}, {"uuid": "170b38c2-6c8d-4830-ab95-7bd7c2f1062e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37987", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17029", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37987\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\npds_core: Prevent possible adminq overflow/stuck condition\n\nThe pds_core's adminq is protected by the adminq_lock, which prevents\nmore than 1 command to be posted onto it at any one time. This makes it\nso the client drivers cannot simultaneously post adminq commands.\nHowever, the completions happen in a different context, which means\nmultiple adminq commands can be posted sequentially and all waiting\non completion.\n\nOn the FW side, the backing adminq request queue is only 16 entries\nlong and the retry mechanism and/or overflow/stuck prevention is\nlacking. This can cause the adminq to get stuck, so commands are no\nlonger processed and completions are no longer sent by the FW.\n\nAs an initial fix, prevent more than 16 outstanding adminq commands so\nthere's no way to cause the adminq from getting stuck. This works\nbecause the backing adminq request queue will never have more than 16\npending adminq commands, so it will never overflow. This is done by\nreducing the adminq depth to 16.\n\ud83d\udccf Published: 2025-05-20T17:09:20.166Z\n\ud83d\udccf Modified: 2025-05-20T17:09:20.166Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2982e07ad72b48eb12c29a87a3f2126ea552688c\n2. https://git.kernel.org/stable/c/5e3dc65675faad846420d24762e4faadc12d9392\n3. https://git.kernel.org/stable/c/d9e2f070d8af60f2c8c02b2ddf0a9e90b4e9220c", "creation_timestamp": "2025-05-20T17:45:15.000000Z"}, {"uuid": "3ae69017-8280-40d1-8c49-00e19a91a8d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37988", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17028", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37988\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nfix a couple of races in MNT_TREE_BENEATH handling by do_move_mount()\n\nNormally do_lock_mount(path, _) is locking a mountpoint pinned by\n*path and at the time when matching unlock_mount() unlocks that\nlocation it is still pinned by the same thing.\n\nUnfortunately, for 'beneath' case it's no longer that simple -\nthe object being locked is not the one *path points to.  It's the\nmountpoint of path->mnt.  The thing is, without sufficient locking\n->mnt_parent may change under us and none of the locks are held\nat that point.  The rules are\n * mount_lock stabilizes m->mnt_parent for any mount m.\n * namespace_sem stabilizes m->mnt_parent, provided that\nm is mounted.\n * if either of the above holds and refcount of m is positive,\nwe are guaranteed the same for refcount of m->mnt_parent.\n\nnamespace_sem nests inside inode_lock(), so do_lock_mount() has\nto take inode_lock() before grabbing namespace_sem.  It does\nrecheck that path->mnt is still mounted in the same place after\ngetting namespace_sem, and it does take care to pin the dentry.\nIt is needed, since otherwise we might end up with racing mount --move\n(or umount) happening while we were getting locks; in that case\ndentry would no longer be a mountpoint and could've been evicted\non memory pressure along with its inode - not something you want\nwhen grabbing lock on that inode.\n\nHowever, pinning a dentry is not enough - the matching mount is\nalso pinned only by the fact that path->mnt is mounted on top it\nand at that point we are not holding any locks whatsoever, so\nthe same kind of races could end up with all references to\nthat mount gone just as we are about to enter inode_lock().\nIf that happens, we are left with filesystem being shut down while\nwe are holding a dentry reference on it; results are not pretty.\n\nWhat we need to do is grab both dentry and mount at the same time;\nthat makes inode_lock() safe *and* avoids the problem with fs getting\nshut down under us.  After taking namespace_sem we verify that\npath->mnt is still mounted (which stabilizes its ->mnt_parent) and\ncheck that it's still mounted at the same place.  From that point\non to the matching namespace_unlock() we are guaranteed that\nmount/dentry pair we'd grabbed are also pinned by being the mountpoint\nof path->mnt, so we can quietly drop both the dentry reference (as\nthe current code does) and mnt one - it's OK to do under namespace_sem,\nsince we are not dropping the final refs.\n\nThat solves the problem on do_lock_mount() side; unlock_mount()\nalso has one, since dentry is guaranteed to stay pinned only until\nthe namespace_unlock().  That's easy to fix - just have inode_unlock()\ndone earlier, while it's still pinned by mp->m_dentry.\n\ud83d\udccf Published: 2025-05-20T17:09:20.765Z\n\ud83d\udccf Modified: 2025-05-20T17:09:20.765Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4f435c1f4c48ff84968e2d9159f6fa41f46cf998\n2. https://git.kernel.org/stable/c/a61afd54826ac24c2c93845c4f441dbc344875b1\n3. https://git.kernel.org/stable/c/d4b21e8cd3d7efa2deb9cff534f0133e84f35086\n4. https://git.kernel.org/stable/c/0d039eac6e5950f9d1ecc9e410c2fd1feaeab3b6", "creation_timestamp": "2025-05-20T17:44:48.000000Z"}, {"uuid": "5aa478f2-13bf-4d2c-a6d7-3804d42c1045", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37989", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17027", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37989\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: leds: fix memory leak\n\nA network restart test on a router led to an out-of-memory condition,\nwhich was traced to a memory leak in the PHY LED trigger code.\n\nThe root cause is misuse of the devm API. The registration function\n(phy_led_triggers_register) is called from phy_attach_direct, not\nphy_probe, and the unregister function (phy_led_triggers_unregister)\nis called from phy_detach, not phy_remove. This means the register and\nunregister functions can be called multiple times for the same PHY\ndevice, but devm-allocated memory is not freed until the driver is\nunbound.\n\nThis also prevents kmemleak from detecting the leak, as the devm API\ninternally stores the allocated pointer.\n\nFix this by replacing devm_kzalloc/devm_kcalloc with standard\nkzalloc/kcalloc, and add the corresponding kfree calls in the unregister\npath.\n\ud83d\udccf Published: 2025-05-20T17:09:21.419Z\n\ud83d\udccf Modified: 2025-05-20T17:09:21.419Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/966d6494e2ed9be9052fcd9815afba830896aaf8\n2. https://git.kernel.org/stable/c/95bed65cc0eb2a610550abf849a8b94374da80a7\n3. https://git.kernel.org/stable/c/663c3da86e807c6c07ed48f911c7526fad6fe1ff\n4. https://git.kernel.org/stable/c/f41f097f68a33d392579885426d0734a81219501\n5. https://git.kernel.org/stable/c/618541a6cc1511064dfa58c89b3445e21844092f\n6. https://git.kernel.org/stable/c/41143e71052a00d654c15dc924fda50c1e7357d0\n7. https://git.kernel.org/stable/c/7f3d5880800f962c347777c4f8358f29f5fc403c\n8. https://git.kernel.org/stable/c/b7f0ee992adf601aa00c252418266177eb7ac2bc", "creation_timestamp": "2025-05-20T17:44:42.000000Z"}, {"uuid": "4ec2afc5-9912-4b65-8768-672e268ba443", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3798", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln65qeca422v", "content": "", "creation_timestamp": "2025-04-19T12:39:24.035306Z"}, {"uuid": "f1b3e3d4-18c3-4912-9d32-227ac59b1a4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37980", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "92407acf-358f-4224-a2b0-372151fcb5c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3798", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12581", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3798\n\ud83d\udd25 CVSS Score: 5.1 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminController.php of the component Advertisement Image Handler. The manipulation leads to unrestricted upload. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-19T10:00:07.289Z\n\ud83d\udccf Modified: 2025-04-19T10:00:07.289Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305651\n2. https://vuldb.com/?ctiid.305651\n3. https://vuldb.com/?submit.554696\n4. https://github.com/IceFoxH/VULN/issues/16", "creation_timestamp": "2025-04-19T11:02:06.000000Z"}, {"uuid": "90dfcb75-25dc-4222-a6d4-00fae1b19e7e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37981", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17035", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37981\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Use is_kdump_kernel() to check for kdump\n\nThe smartpqi driver checks the reset_devices variable to determine\nwhether special adjustments need to be made for kdump. This has the\neffect that after a regular kexec reboot, some driver parameters such as\nmax_transfer_size are much lower than usual. More importantly, kexec\nreboot tests have revealed memory corruption caused by the driver log\nbeing written to system memory after a kexec.\n\nFix this by testing is_kdump_kernel() rather than reset_devices where\nappropriate.\n\ud83d\udccf Published: 2025-05-20T16:58:23.299Z\n\ud83d\udccf Modified: 2025-05-20T16:58:23.299Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7cc670e8ebaa5241dd99c0ad75eceb8f8f64f607\n2. https://git.kernel.org/stable/c/ebf673c76ce91e612a882dfaa9a3824962994aae\n3. https://git.kernel.org/stable/c/a2d5a0072235a69749ceb04c1a26dc75df66a31a", "creation_timestamp": "2025-05-20T17:45:46.000000Z"}, {"uuid": "e987179b-fa00-419a-a19f-5de73ff0f27b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3798", "type": "seen", "source": "https://t.me/cvedetector/23379", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3798 - Apache WCMS Unrestricted File Upload Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3798 \nPublished : April 19, 2025, 10:15 a.m. | 35\u00a0minutes ago \nDescription : A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminController.php of the component Advertisement Image Handler. The manipulation leads to unrestricted upload. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 4.7 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-19T13:28:48.000000Z"}, {"uuid": "cec63ccd-64e4-4386-ac67-32f875194383", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37981", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114541968902367001", "content": "", "creation_timestamp": "2025-05-20T20:09:02.679016Z"}, {"uuid": "f55e6ac8-0765-4216-813a-7b645dc4369c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37980", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "01dd36b4-287b-4b71-b52f-8ffea2fe1048", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37984", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "3b120a0e-2c73-4ad6-b95f-fab3d19a91cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37984", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17031", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37984\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP()\n\nHerbert notes that DIV_ROUND_UP() may overflow unnecessarily if an ecdsa\nimplementation's ->key_size() callback returns an unusually large value.\nHerbert instead suggests (for a division by 8):\n\n  X / 8 + !!(X & 7)\n\nBased on this formula, introduce a generic DIV_ROUND_UP_POW2() macro and\nuse it in lieu of DIV_ROUND_UP() for ->key_size() return values.\n\nAdditionally, use the macro in ecc_digits_from_bytes(), whose \"nbytes\"\nparameter is a ->key_size() return value in some instances, or a\nuser-specified ASN.1 length in the case of ecdsa_get_signature_rs().\n\ud83d\udccf Published: 2025-05-20T17:09:18.321Z\n\ud83d\udccf Modified: 2025-05-20T17:09:18.321Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/921b8167f10708e38080f84e195cdc68a7a561f1\n2. https://git.kernel.org/stable/c/b16510a530d1e6ab9683f04f8fb34f2e0f538275", "creation_timestamp": "2025-05-20T17:45:42.000000Z"}, {"uuid": "f6752a6f-892b-4def-ae7d-ae39b7498c45", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37985", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17030", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37985\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nUSB: wdm: close race between wdm_open and wdm_wwan_port_stop\n\nClearing WDM_WWAN_IN_USE must be the last action or\nwe can open a chardev whose URBs are still poisoned\n\ud83d\udccf Published: 2025-05-20T17:09:18.963Z\n\ud83d\udccf Modified: 2025-05-20T17:09:18.963Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b02a3fef3e8c8fe5a0a266f7a14f38cc608fb167\n2. https://git.kernel.org/stable/c/217fe1fc7d112595a793e02b306710e702eac492\n3. https://git.kernel.org/stable/c/54f7f8978af19f899dec80bcc71c8d4855dfbd72\n4. https://git.kernel.org/stable/c/52ae15c665b5fe5876655aaccc3ef70560b0e314\n5. https://git.kernel.org/stable/c/e3c9adc69357fcbe6253a2bc2588ee4bbaaedbe9\n6. https://git.kernel.org/stable/c/c1846ed4eb527bdfe6b3b7dd2c78e2af4bf98f4f", "creation_timestamp": "2025-05-20T17:45:41.000000Z"}]}