diff --git a/CVE-2020/CVE-2020-275xx/CVE-2020-27507.json b/CVE-2020/CVE-2020-275xx/CVE-2020-27507.json
index 855fccd2b1b..4e6f01e321a 100644
--- a/CVE-2020/CVE-2020-275xx/CVE-2020-27507.json
+++ b/CVE-2020/CVE-2020-275xx/CVE-2020-27507.json
@@ -2,7 +2,7 @@
"id": "CVE-2020-27507",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-15T20:15:10.283",
- "lastModified": "2024-11-21T05:21:16.647",
+ "lastModified": "2025-02-27T19:15:39.567",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 3.9,
"impactScore": 5.9
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 9.8,
+ "baseSeverity": "CRITICAL",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 5.9
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-120"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-120"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2020/CVE-2020-368xx/CVE-2020-36835.json b/CVE-2020/CVE-2020-368xx/CVE-2020-36835.json
index 819bf47f96f..a75b05d50eb 100644
--- a/CVE-2020/CVE-2020-368xx/CVE-2020-36835.json
+++ b/CVE-2020/CVE-2020-368xx/CVE-2020-36835.json
@@ -2,8 +2,8 @@
"id": "CVE-2020-36835",
"sourceIdentifier": "security@wordfence.com",
"published": "2024-10-16T07:15:08.387",
- "lastModified": "2024-10-16T16:38:14.557",
- "vulnStatus": "Awaiting Analysis",
+ "lastModified": "2025-02-27T18:47:11.020",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -19,7 +19,7 @@
"cvssMetricV31": [
{
"source": "security@wordfence.com",
- "type": "Primary",
+ "type": "Secondary",
"cvssData": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
@@ -36,33 +36,90 @@
},
"exploitabilityScore": 1.2,
"impactScore": 3.6
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
+ "baseScore": 6.5,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 3.6
}
]
},
"weaknesses": [
{
"source": "security@wordfence.com",
- "type": "Primary",
+ "type": "Secondary",
"description": [
{
"lang": "en",
"value": "CWE-200"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-862"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:wpvivid:migration\\,_backup\\,_staging:*:*:*:*:*:wordpress:*:*",
+ "versionEndExcluding": "0.9.36",
+ "matchCriteriaId": "1668EF1F-FF6F-4AC2-8B4C-DEDB7AD2F589"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=2261665%40wpvivid-backuprestore%2Ftrunk&old=2252870%40wpvivid-backuprestore%2Ftrunk&sfp_email=&sfph_mail=",
- "source": "security@wordfence.com"
+ "source": "security@wordfence.com",
+ "tags": [
+ "Patch"
+ ]
},
{
"url": "https://www.webarxsecurity.com/vulnerability-in-wpvivid-backup-plugin-can-lead-to-database-leak/?fbclid=IwAR3Ve74ZIvmx-aC0OssIWYwcWEjGq6yU16DcyVGHD1XUT3uYaZ3QyVu_Eos&utm_content=buffer4435b&utm_medium=social&utm_source=facebook.com&utm_campaign=buffer",
- "source": "security@wordfence.com"
+ "source": "security@wordfence.com",
+ "tags": [
+ "Broken Link"
+ ]
},
{
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/90c3f8bc-fc41-4ba7-b9f2-8873203d5794?source=cve",
- "source": "security@wordfence.com"
+ "source": "security@wordfence.com",
+ "tags": [
+ "Third Party Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47634.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47634.json
index 4eadbf48e87..e3d7fdb8202 100644
--- a/CVE-2021/CVE-2021-476xx/CVE-2021-47634.json
+++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47634.json
@@ -2,16 +2,55 @@
"id": "CVE-2021-47634",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T06:37:05.173",
- "lastModified": "2025-02-26T06:37:05.173",
+ "lastModified": "2025-02-27T19:15:40.623",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl\n\nHulk Robot reported a KASAN report about use-after-free:\n ==================================================================\n BUG: KASAN: use-after-free in __list_del_entry_valid+0x13d/0x160\n Read of size 8 at addr ffff888035e37d98 by task ubiattach/1385\n [...]\n Call Trace:\n klist_dec_and_del+0xa7/0x4a0\n klist_put+0xc7/0x1a0\n device_del+0x4d4/0xed0\n cdev_device_del+0x1a/0x80\n ubi_attach_mtd_dev+0x2951/0x34b0 [ubi]\n ctrl_cdev_ioctl+0x286/0x2f0 [ubi]\n\n Allocated by task 1414:\n device_add+0x60a/0x18b0\n cdev_device_add+0x103/0x170\n ubi_create_volume+0x1118/0x1a10 [ubi]\n ubi_cdev_ioctl+0xb7f/0x1ba0 [ubi]\n\n Freed by task 1385:\n cdev_device_del+0x1a/0x80\n ubi_remove_volume+0x438/0x6c0 [ubi]\n ubi_cdev_ioctl+0xbf4/0x1ba0 [ubi]\n [...]\n ==================================================================\n\nThe lock held by ctrl_cdev_ioctl is ubi_devices_mutex, but the lock held\nby ubi_cdev_ioctl is ubi->device_mutex. Therefore, the two locks can be\nconcurrent.\n\nctrl_cdev_ioctl contains two operations: ubi_attach and ubi_detach.\nubi_detach is bug-free because it uses reference counting to prevent\nconcurrency. However, uif_init and uif_close in ubi_attach may race with\nubi_cdev_ioctl.\n\nuif_init will race with ubi_cdev_ioctl as in the following stack.\n cpu1 cpu2 cpu3\n_______________________|________________________|______________________\nctrl_cdev_ioctl\n ubi_attach_mtd_dev\n uif_init\n ubi_cdev_ioctl\n ubi_create_volume\n cdev_device_add\n ubi_add_volume\n // sysfs exist\n kill_volumes\n ubi_cdev_ioctl\n ubi_remove_volume\n cdev_device_del\n // first free\n ubi_free_volume\n cdev_del\n // double free\n cdev_device_del\n\nAnd uif_close will race with ubi_cdev_ioctl as in the following stack.\n cpu1 cpu2 cpu3\n_______________________|________________________|______________________\nctrl_cdev_ioctl\n ubi_attach_mtd_dev\n uif_init\n ubi_cdev_ioctl\n ubi_create_volume\n cdev_device_add\n ubi_debugfs_init_dev\n //error goto out_uif;\n uif_close\n kill_volumes\n ubi_cdev_ioctl\n ubi_remove_volume\n cdev_device_del\n // first free\n ubi_free_volume\n // double free\n\nThe cause of this problem is that commit 714fb87e8bc0 make device\n\"available\" before it becomes accessible via sysfs. Therefore, we\nroll back the modification. We will fix the race condition between\nubi device creation and udev by removing ubi_get_device in\nvol_attribute_show and dev_attribute_show.This avoids accessing\nuninitialized ubi_devices[ubi_num].\n\nubi_get_device is used to prevent devices from being deleted during\nsysfs execution. However, now kernfs ensures that devices will not\nbe deleted before all reference counting are released.\nThe key process is shown in the following stack.\n\ndevice_del\n device_remove_attrs\n device_remove_groups\n sysfs_remove_groups\n sysfs_remove_group\n remove_files\n kernfs_remove_by_name\n kernfs_remove_by_name_ns\n __kernfs_remove\n kernfs_drain"
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ubi: Se corrige la condici\u00f3n de ejecuci\u00f3n entre ctrl_cdev_ioctl y ubi_cdev_ioctl Hulk Robot inform\u00f3 un informe de KASAN sobre use-after-free: ====================================================================== ERROR: KASAN: use-after-free en __list_del_entry_valid+0x13d/0x160 Lectura de tama\u00f1o 8 en la direcci\u00f3n ffff888035e37d98 por la tarea ubiattach/1385 [...] Seguimiento de llamadas: klist_dec_and_del+0xa7/0x4a0 klist_put+0xc7/0x1a0 device_del+0x4d4/0xed0 cdev_device_del+0x1a/0x80 ubi_attach_mtd_dev+0x2951/0x34b0 [ubi] ctrl_cdev_ioctl+0x286/0x2f0 [ubi] Asignado por la tarea 1414: device_add+0x60a/0x18b0 cdev_device_add+0x103/0x170 ubi_create_volume+0x1118/0x1a10 [ubi] ubi_cdev_ioctl+0xb7f/0x1ba0 [ubi] Liberado por la tarea 1385: cdev_device_del+0x1a/0x80 ubi_remove_volume+0x438/0x6c0 [ubi] ubi_cdev_ioctl+0xbf4/0x1ba0 [ubi] [...] ===================================================================== El bloqueo retenido por ctrl_cdev_ioctl es ubi_devices_mutex, pero el bloqueo retenido por ubi_cdev_ioctl es ubi->device_mutex. Por lo tanto, los dos bloqueos pueden ser concurrentes. ctrl_cdev_ioctl contiene dos operaciones: ubi_attach y ubi_detach. ubi_detach est\u00e1 libre de errores porque utiliza el conteo de referencias para evitar la concurrencia. Sin embargo, uif_init y uif_close en ubi_attach pueden competir con ubi_cdev_ioctl. uif_init competir\u00e1 con ubi_cdev_ioctl como en la siguiente pila. cpu1 cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_add_volume // sysfs existen kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // primer ubi_free_volume libre cdev_del // doble liberaci\u00f3n cdev_device_del Y uif_close competir\u00e1 con ubi_cdev_ioctl como en la siguiente pila. cpu1 cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_debugfs_init_dev //error goto out_uif; uif_close kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // primera liberaci\u00f3n ubi_free_volume // doble liberaci\u00f3n La causa de este problema es que la confirmaci\u00f3n 714fb87e8bc0 hace que el dispositivo est\u00e9 \"disponible\" antes de que se pueda acceder a \u00e9l a trav\u00e9s de sysfs. Por lo tanto, revertimos la modificaci\u00f3n. Solucionaremos la condici\u00f3n de ejecuci\u00f3n entre la creaci\u00f3n del dispositivo ubi y udev eliminando ubi_get_device en vol_attribute_show y dev_attribute_show. Esto evita el acceso a ubi_devices[ubi_num] no inicializados. ubi_get_device se utiliza para evitar que se eliminen los dispositivos durante la ejecuci\u00f3n de sysfs. Sin embargo, ahora kernfs garantiza que los dispositivos no se eliminar\u00e1n antes de que se liberen todos los recuentos de referencias. El proceso clave se muestra en la siguiente pila. device_del device_remove_attrs device_remove_groups sysfs_remove_groups sysfs_remove_group remove_files kernfs_remove_by_name kernfs_remove_by_name_ns __kernfs_remove kernfs_drain"
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/1a3f1cf87054833242fcd0218de0481cf855f888",
diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47639.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47639.json
index a078323a61c..7b62f3d04b9 100644
--- a/CVE-2021/CVE-2021-476xx/CVE-2021-47639.json
+++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47639.json
@@ -2,16 +2,55 @@
"id": "CVE-2021-47639",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T06:37:05.677",
- "lastModified": "2025-02-26T06:37:05.677",
+ "lastModified": "2025-02-27T19:15:40.773",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU\n\nZap both valid and invalid roots when zapping/unmapping a gfn range, as\nKVM must ensure it holds no references to the freed page after returning\nfrom the unmap operation. Most notably, the TDP MMU doesn't zap invalid\nroots in mmu_notifier callbacks. This leads to use-after-free and other\nissues if the mmu_notifier runs to completion while an invalid root\nzapper yields as KVM fails to honor the requirement that there must be\n_no_ references to the page after the mmu_notifier returns.\n\nThe bug is most easily reproduced by hacking KVM to cause a collision\nbetween set_nx_huge_pages() and kvm_mmu_notifier_release(), but the bug\nexists between kvm_mmu_notifier_invalidate_range_start() and memslot\nupdates as well. Invalidating a root ensures pages aren't accessible by\nthe guest, and KVM won't read or write page data itself, but KVM will\ntrigger e.g. kvm_set_pfn_dirty() when zapping SPTEs, and thus completing\na zap of an invalid root _after_ the mmu_notifier returns is fatal.\n\n WARNING: CPU: 24 PID: 1496 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:173 [kvm]\n RIP: 0010:kvm_is_zone_device_pfn+0x96/0xa0 [kvm]\n Call Trace:\n \n kvm_set_pfn_dirty+0xa8/0xe0 [kvm]\n __handle_changed_spte+0x2ab/0x5e0 [kvm]\n __handle_changed_spte+0x2ab/0x5e0 [kvm]\n __handle_changed_spte+0x2ab/0x5e0 [kvm]\n zap_gfn_range+0x1f3/0x310 [kvm]\n kvm_tdp_mmu_zap_invalidated_roots+0x50/0x90 [kvm]\n kvm_mmu_zap_all_fast+0x177/0x1a0 [kvm]\n set_nx_huge_pages+0xb4/0x190 [kvm]\n param_attr_store+0x70/0x100\n module_attr_store+0x19/0x30\n kernfs_fop_write_iter+0x119/0x1b0\n new_sync_write+0x11c/0x1b0\n vfs_write+0x1cc/0x270\n ksys_write+0x5f/0xe0\n do_syscall_64+0x38/0xc0\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n "
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: KVM: x86/mmu: Se eliminan _todos_ las ra\u00edces al anular la asignaci\u00f3n del rango gfn en TDP MMU Se eliminan las ra\u00edces v\u00e1lidas e inv\u00e1lidas al hacer zapping/anular la asignaci\u00f3n de un rango gfn, ya que KVM debe asegurarse de que no contiene referencias a la p\u00e1gina liberada despu\u00e9s de regresar de la operaci\u00f3n de anulaci\u00f3n de la asignaci\u00f3n. En particular, TDP MMU no elimina las ra\u00edces inv\u00e1lidas en las devoluciones de llamadas mmu_notifier. Esto conduce a problemas de use-after-free y otros problemas si mmu_notifier se ejecuta hasta el final mientras que un zapper de ra\u00edz inv\u00e1lida cede, ya que KVM no cumple con el requisito de que no debe haber _ninguna_ referencia a la p\u00e1gina despu\u00e9s de que mmu_notifier regrese. El error se reproduce m\u00e1s f\u00e1cilmente pirateando KVM para provocar una colisi\u00f3n entre set_nx_huge_pages() y kvm_mmu_notifier_release(), pero el error tambi\u00e9n existe entre kvm_mmu_notifier_invalidate_range_start() y las actualizaciones de memslot. Invalidar una ra\u00edz garantiza que el invitado no pueda acceder a las p\u00e1ginas, y KVM no leer\u00e1 ni escribir\u00e1 datos de p\u00e1gina por s\u00ed mismo, pero KVM activar\u00e1, por ejemplo, kvm_set_pfn_dirty() al hacer zapping de SPTE, y por lo tanto, completar un zapping de una ra\u00edz no v\u00e1lida _despu\u00e9s_ de que mmu_notifier regrese es fatal. ADVERTENCIA: CPU: 24 PID: 1496 en arch/x86/kvm/../../../virt/kvm/kvm_main.c:173 [kvm] RIP: 0010:kvm_is_zone_device_pfn+0x96/0xa0 [kvm] Rastreo de llamadas: kvm_set_pfn_dirty+0xa8/0xe0 [kvm] __handle_changed_spte+0x2ab/0x5e0 [kvm] __handle_changed_spte+0x2ab/0x5e0 [kvm] __handle_changed_spte+0x2ab/0x5e0 [kvm] zap_gfn_range+0x1f3/0x310 [kvm] kvm_tdp_mmu_zap_ra\u00edces_invalidadas+0x50/0x90 [kvm] kvm_mmu_zap_all_fast+0x177/0x1a0 [kvm] set_nx_huge_pages+0xb4/0x190 [kvm] param_attr_store+0x70/0x100 module_attr_store+0x19/0x30 kernfs_fop_write_iter+0x119/0x1b0 new_sync_write+0x11c/0x1b0 vfs_write+0x1cc/0x270 ksys_write+0x5f/0xe0 do_syscall_64+0x38/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae "
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/0c8a8da182d4333d9bbb9131d765145568c847b2",
diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47653.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47653.json
index f6496bdb481..2a8fd78a549 100644
--- a/CVE-2021/CVE-2021-476xx/CVE-2021-47653.json
+++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47653.json
@@ -2,16 +2,55 @@
"id": "CVE-2021-47653",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T06:37:07.080",
- "lastModified": "2025-02-26T06:37:07.080",
+ "lastModified": "2025-02-27T19:15:40.917",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: davinci: vpif: fix use-after-free on driver unbind\n\nThe driver allocates and registers two platform device structures during\nprobe, but the devices were never deregistered on driver unbind.\n\nThis results in a use-after-free on driver unbind as the device\nstructures were allocated using devres and would be freed by driver\ncore when remove() returns.\n\nFix this by adding the missing deregistration calls to the remove()\ncallback and failing probe on registration errors.\n\nNote that the platform device structures must be freed using a proper\nrelease callback to avoid leaking associated resources like device\nnames."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: media: davinci: vpif: fix use-after-free on driver unbind El controlador asigna y registra dos estructuras de dispositivos de plataforma durante la sonda, pero los dispositivos nunca se anularon el registro en la anulaci\u00f3n del enlace del controlador. Esto da como resultado un use-after-free en la anulaci\u00f3n del enlace del controlador, ya que las estructuras de dispositivos se asignaron utilizando devres y ser\u00edan liberadas por el n\u00facleo del controlador cuando remove() regrese. Solucione esto agregando las llamadas de anulaci\u00f3n de registro faltantes a la devoluci\u00f3n de llamada remove() y haciendo que la sonda falle en los errores de registro. Tenga en cuenta que las estructuras de dispositivos de plataforma se deben liberar utilizando una devoluci\u00f3n de llamada de liberaci\u00f3n adecuada para evitar filtrar recursos asociados, como nombres de dispositivos."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/43acb728bbc40169d2e2425e84a80068270974be",
diff --git a/CVE-2022/CVE-2022-257xx/CVE-2022-25768.json b/CVE-2022/CVE-2022-257xx/CVE-2022-25768.json
index a93c9c22cc2..981088f35da 100644
--- a/CVE-2022/CVE-2022-257xx/CVE-2022-25768.json
+++ b/CVE-2022/CVE-2022-257xx/CVE-2022-25768.json
@@ -2,8 +2,8 @@
"id": "CVE-2022-25768",
"sourceIdentifier": "security@mautic.org",
"published": "2024-09-18T21:15:12.860",
- "lastModified": "2024-09-20T12:30:17.483",
- "vulnStatus": "Undergoing Analysis",
+ "lastModified": "2025-02-27T19:30:33.180",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 2.2,
"impactScore": 4.7
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
+ "baseScore": 6.5,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 2.5
}
]
},
@@ -49,12 +69,51 @@
"value": "CWE-287"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-862"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "1.1.3",
+ "versionEndExcluding": "4.4.13",
+ "matchCriteriaId": "96CCF98E-6E23-4EB5-836C-F9ADFC60AA65"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "5.0.0",
+ "versionEndExcluding": "5.1.1",
+ "matchCriteriaId": "FC060988-1D0C-4CB2-A052-A0BCCD236381"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://github.com/mautic/mautic/security/advisories/GHSA-x3jx-5w6m-q2fc",
- "source": "security@mautic.org"
+ "source": "security@mautic.org",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2022/CVE-2022-257xx/CVE-2022-25770.json b/CVE-2022/CVE-2022-257xx/CVE-2022-25770.json
index af66ee1bfa0..e10d58b7d81 100644
--- a/CVE-2022/CVE-2022-257xx/CVE-2022-25770.json
+++ b/CVE-2022/CVE-2022-257xx/CVE-2022-25770.json
@@ -2,8 +2,8 @@
"id": "CVE-2022-25770",
"sourceIdentifier": "security@mautic.org",
"published": "2024-09-18T22:15:03.827",
- "lastModified": "2024-09-20T12:30:17.483",
- "vulnStatus": "Undergoing Analysis",
+ "lastModified": "2025-02-27T19:30:33.180",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 1.4,
"impactScore": 5.8
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
}
]
},
@@ -49,12 +69,86 @@
"value": "CWE-306"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-306"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "1.0.1",
+ "versionEndExcluding": "4.4.13",
+ "matchCriteriaId": "496E995E-E33A-4481-83A6-38172DA11763"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "5.0.0",
+ "versionEndExcluding": "5.1.1",
+ "matchCriteriaId": "FC060988-1D0C-4CB2-A052-A0BCCD236381"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:-:*:*:*:*:*:*",
+ "matchCriteriaId": "99718D48-5C19-41C5-84E1-52E95F012830"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:beta3:*:*:*:*:*:*",
+ "matchCriteriaId": "9C1C106B-1B3D-427D-8147-5527E610F569"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:beta4:*:*:*:*:*:*",
+ "matchCriteriaId": "4E35B0F0-9BF1-45FA-8954-B8BFB7389C4D"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:rc1:*:*:*:*:*:*",
+ "matchCriteriaId": "213A9276-B9D1-4B4D-BBE9-FC42B6D63DE1"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:rc2:*:*:*:*:*:*",
+ "matchCriteriaId": "F366E4D8-1515-4E5F-8551-4C8D9E00D0D9"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:rc3:*:*:*:*:*:*",
+ "matchCriteriaId": "B4234B41-F219-45B7-83A1-8F0F652F2A8B"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:rc4:*:*:*:*:*:*",
+ "matchCriteriaId": "DA028F70-6020-47D6-BEC0-6FC0C7E18420"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://github.com/mautic/mautic/security/advisories/GHSA-qf6m-6m4g-rmrc",
- "source": "security@mautic.org"
+ "source": "security@mautic.org",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2022/CVE-2022-257xx/CVE-2022-25777.json b/CVE-2022/CVE-2022-257xx/CVE-2022-25777.json
index 6f3add81c4c..88ff3a2b4e2 100644
--- a/CVE-2022/CVE-2022-257xx/CVE-2022-25777.json
+++ b/CVE-2022/CVE-2022-257xx/CVE-2022-25777.json
@@ -2,8 +2,8 @@
"id": "CVE-2022-25777",
"sourceIdentifier": "security@mautic.org",
"published": "2024-09-18T16:15:04.980",
- "lastModified": "2024-09-20T12:30:17.483",
- "vulnStatus": "Undergoing Analysis",
+ "lastModified": "2025-02-27T19:30:33.180",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 1.2,
"impactScore": 5.2
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
+ "baseScore": 6.5,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 3.6
}
]
},
@@ -49,12 +69,81 @@
"value": "CWE-918"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-918"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "1.0.1",
+ "versionEndExcluding": "4.4.12",
+ "matchCriteriaId": "7418A276-A3A8-4D0E-AA86-92E1EED6006A"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "5.0.0",
+ "versionEndExcluding": "5.0.4",
+ "matchCriteriaId": "3123A79D-F360-44BE-85BA-34304F3E1B40"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:-:*:*:*:*:*:*",
+ "matchCriteriaId": "99718D48-5C19-41C5-84E1-52E95F012830"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:beta4:*:*:*:*:*:*",
+ "matchCriteriaId": "4E35B0F0-9BF1-45FA-8954-B8BFB7389C4D"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:rc1:*:*:*:*:*:*",
+ "matchCriteriaId": "213A9276-B9D1-4B4D-BBE9-FC42B6D63DE1"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:rc2:*:*:*:*:*:*",
+ "matchCriteriaId": "F366E4D8-1515-4E5F-8551-4C8D9E00D0D9"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:rc3:*:*:*:*:*:*",
+ "matchCriteriaId": "B4234B41-F219-45B7-83A1-8F0F652F2A8B"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:1.0.0:rc4:*:*:*:*:*:*",
+ "matchCriteriaId": "DA028F70-6020-47D6-BEC0-6FC0C7E18420"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://github.com/mautic/mautic/security/advisories/GHSA-mgv8-w49f-822w",
- "source": "security@mautic.org"
+ "source": "security@mautic.org",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2022/CVE-2022-43xx/CVE-2022-4313.json b/CVE-2022/CVE-2022-43xx/CVE-2022-4313.json
index b40e56fba58..2cad4656bd5 100644
--- a/CVE-2022/CVE-2022-43xx/CVE-2022-4313.json
+++ b/CVE-2022/CVE-2022-43xx/CVE-2022-4313.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-4313",
"sourceIdentifier": "vulnreport@tenable.com",
"published": "2023-03-15T23:15:09.337",
- "lastModified": "2024-11-21T07:35:00.820",
+ "lastModified": "2025-02-27T19:15:47.290",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 2.8,
"impactScore": 5.9
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 8.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 5.9
}
]
},
@@ -45,6 +65,16 @@
"value": "NVD-CWE-noinfo"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-427"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2022/CVE-2022-481xx/CVE-2022-48111.json b/CVE-2022/CVE-2022-481xx/CVE-2022-48111.json
index 6c07db1654d..893a6584cd3 100644
--- a/CVE-2022/CVE-2022-481xx/CVE-2022-48111.json
+++ b/CVE-2022/CVE-2022-481xx/CVE-2022-48111.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-48111",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-10T15:15:10.217",
- "lastModified": "2024-11-21T07:32:50.970",
+ "lastModified": "2025-02-27T20:15:34.833",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 2.8,
"impactScore": 2.7
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
+ "baseScore": 6.1,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "REQUIRED",
+ "scope": "CHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 2.7
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-79"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-79"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2022/CVE-2022-490xx/CVE-2022-49063.json b/CVE-2022/CVE-2022-490xx/CVE-2022-49063.json
index ccc56709eef..ea61ef5a7e9 100644
--- a/CVE-2022/CVE-2022-490xx/CVE-2022-49063.json
+++ b/CVE-2022/CVE-2022-490xx/CVE-2022-49063.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49063",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:43.547",
- "lastModified": "2025-02-26T07:00:43.547",
+ "lastModified": "2025-02-27T19:15:41.070",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nice: arfs: fix use-after-free when freeing @rx_cpu_rmap\n\nThe CI testing bots triggered the following splat:\n\n[ 718.203054] BUG: KASAN: use-after-free in free_irq_cpu_rmap+0x53/0x80\n[ 718.206349] Read of size 4 at addr ffff8881bd127e00 by task sh/20834\n[ 718.212852] CPU: 28 PID: 20834 Comm: sh Kdump: loaded Tainted: G S W IOE 5.17.0-rc8_nextqueue-devqueue-02643-g23f3121aca93 #1\n[ 718.219695] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0012.070720200218 07/07/2020\n[ 718.223418] Call Trace:\n[ 718.227139]\n[ 718.230783] dump_stack_lvl+0x33/0x42\n[ 718.234431] print_address_description.constprop.9+0x21/0x170\n[ 718.238177] ? free_irq_cpu_rmap+0x53/0x80\n[ 718.241885] ? free_irq_cpu_rmap+0x53/0x80\n[ 718.245539] kasan_report.cold.18+0x7f/0x11b\n[ 718.249197] ? free_irq_cpu_rmap+0x53/0x80\n[ 718.252852] free_irq_cpu_rmap+0x53/0x80\n[ 718.256471] ice_free_cpu_rx_rmap.part.11+0x37/0x50 [ice]\n[ 718.260174] ice_remove_arfs+0x5f/0x70 [ice]\n[ 718.263810] ice_rebuild_arfs+0x3b/0x70 [ice]\n[ 718.267419] ice_rebuild+0x39c/0xb60 [ice]\n[ 718.270974] ? asm_sysvec_apic_timer_interrupt+0x12/0x20\n[ 718.274472] ? ice_init_phy_user_cfg+0x360/0x360 [ice]\n[ 718.278033] ? delay_tsc+0x4a/0xb0\n[ 718.281513] ? preempt_count_sub+0x14/0xc0\n[ 718.284984] ? delay_tsc+0x8f/0xb0\n[ 718.288463] ice_do_reset+0x92/0xf0 [ice]\n[ 718.292014] ice_pci_err_resume+0x91/0xf0 [ice]\n[ 718.295561] pci_reset_function+0x53/0x80\n<...>\n[ 718.393035] Allocated by task 690:\n[ 718.433497] Freed by task 20834:\n[ 718.495688] Last potentially related work creation:\n[ 718.568966] The buggy address belongs to the object at ffff8881bd127e00\n which belongs to the cache kmalloc-96 of size 96\n[ 718.574085] The buggy address is located 0 bytes inside of\n 96-byte region [ffff8881bd127e00, ffff8881bd127e60)\n[ 718.579265] The buggy address belongs to the page:\n[ 718.598905] Memory state around the buggy address:\n[ 718.601809] ffff8881bd127d00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc\n[ 718.604796] ffff8881bd127d80: 00 00 00 00 00 00 00 00 00 00 fc fc fc fc fc fc\n[ 718.607794] >ffff8881bd127e00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc\n[ 718.610811] ^\n[ 718.613819] ffff8881bd127e80: 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc\n[ 718.617107] ffff8881bd127f00: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc\n\nThis is due to that free_irq_cpu_rmap() is always being called\n*after* (devm_)free_irq() and thus it tries to work with IRQ descs\nalready freed. For example, on device reset the driver frees the\nrmap right before allocating a new one (the splat above).\nMake rmap creation and freeing function symmetrical with\n{request,free}_irq() calls i.e. do that on ifup/ifdown instead\nof device probe/remove/resume. These operations can be performed\nindependently from the actual device aRFS configuration.\nAlso, make sure ice_vsi_free_irq() clears IRQ affinity notifiers\nonly when aRFS is disabled -- otherwise, CPU rmap sets and clears\nits own and they must not be touched manually."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ice: arfs: corregir use-after-free al liberar @rx_cpu_rmap Los bots de prueba de CI activaron el siguiente splat: [ 718.203054] ERROR: KASAN: use-after-free en free_irq_cpu_rmap+0x53/0x80 [ 718.206349] Lectura de tama\u00f1o 4 en la direcci\u00f3n ffff8881bd127e00 por la tarea sh/20834 [ 718.212852] CPU: 28 PID: 20834 Comm: sh Kdump: cargado Tainted: GSW IOE 5.17.0-rc8_nextqueue-devqueue-02643-g23f3121aca93 #1 [ 718.219695] Hardware nombre: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0012.070720200218 07/07/2020 [ 718.223418] Seguimiento de llamadas: [ 718.227139] [ 718.230783] dump_stack_lvl+0x33/0x42 [ 718.234431] print_address_description.constprop.9+0x21/0x170 [ 718.238177] ? free_irq_cpu_rmap+0x53/0x80 [ 718.241885] ? informe_kasan.cold.18+0x7f/0x11b [ 718.249197] ? free_irq_cpu_rmap+0x53/0x80 [ 718.252852] free_irq_cpu_rmap+0x53/0x80 [ 718.256471] ice_free_cpu_rx_rmap.part.11+0x37/0x50 [hielo] [ 718.260174] ice_remove_arfs+0x5f/0x70 [hielo] [ 718.263810] ice_rebuild_arfs+0x3b/0x70 [hielo] [ 718.267419] ice_rebuild+0x39c/0xb60 [hielo] [ 718.270974] ? preempt_count_sub+0x14/0xc0 [ 718.284984] ? delay_tsc+0x8f/0xb0 [ 718.288463] ice_do_reset+0x92/0xf0 [ice] [ 718.292014] ice_pci_err_resume+0x91/0xf0 [ice] [ 718.295561] pci_reset_function+0x53/0x80 <...> [ 718.393035] Asignado por la tarea 690: [ 718.433497] Liberado por la tarea 20834: [ 718.495688] \u00daltima creaci\u00f3n de trabajo potencialmente relacionada: [ 718.568966] La direcci\u00f3n con errores pertenece al objeto en ffff8881bd127e00 que pertenece a la cach\u00e9 kmalloc-96 de tama\u00f1o 96 [ 718.574085] La direcci\u00f3n con errores se encuentra a 0 bytes dentro de la regi\u00f3n de 96 bytes [ffff8881bd127e00, ffff8881bd127e60) [ 718.579265] La direcci\u00f3n con errores pertenece a la p\u00e1gina: [ 718.598905] Estado de la memoria alrededor de la direcci\u00f3n con errores: [ 718.601809] ffff8881bd127d00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc [ 718.604796] ffff8881bd127d80: 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc fc fc [ 718.607794] >ffff8881bd127e00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc [ 718.610811] ^ [ 718.613819] ffff8881bd127e80: 00 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc [ 718.617107] ffff8881bd127f00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc Esto se debe a que free_irq_cpu_rmap() siempre se llama *despu\u00e9s* de (devm_)free_irq() y, por lo tanto, intenta funcionar. con descripciones IRQ ya liberadas. Por ejemplo, al reiniciar el dispositivo, el controlador libera el rmap justo antes de asignar uno nuevo (el s\u00edmbolo de arriba). Haga que la creaci\u00f3n y liberaci\u00f3n de rmap sean sim\u00e9tricas con las llamadas {request,free}_irq(), es decir, h\u00e1galo en ifup/ifdown en lugar de en la prueba/eliminaci\u00f3n/reanudaci\u00f3n del dispositivo. Estas operaciones se pueden realizar independientemente de la configuraci\u00f3n aRFS del dispositivo real. Adem\u00e1s, aseg\u00farese de que ice_vsi_free_irq() borre los notificadores de afinidad IRQ solo cuando aRFS est\u00e9 deshabilitado; de lo contrario, el rmap de la CPU establece y borra los suyos propios y no se deben tocar manualmente."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/d08d2fb6d99d82da1c63aba5c0d1c6f237e150f3",
diff --git a/CVE-2022/CVE-2022-490xx/CVE-2022-49076.json b/CVE-2022/CVE-2022-490xx/CVE-2022-49076.json
index d623b96bdb9..956ad98fc9b 100644
--- a/CVE-2022/CVE-2022-490xx/CVE-2022-49076.json
+++ b/CVE-2022/CVE-2022-490xx/CVE-2022-49076.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49076",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:44.943",
- "lastModified": "2025-02-26T07:00:44.943",
+ "lastModified": "2025-02-27T19:15:41.213",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hfi1: Fix use-after-free bug for mm struct\n\nUnder certain conditions, such as MPI_Abort, the hfi1 cleanup code may\nrepresent the last reference held on the task mm.\nhfi1_mmu_rb_unregister() then drops the last reference and the mm is freed\nbefore the final use in hfi1_release_user_pages(). A new task may\nallocate the mm structure while it is still being used, resulting in\nproblems. One manifestation is corruption of the mmap_sem counter leading\nto a hang in down_write(). Another is corruption of an mm struct that is\nin use by another task."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: RDMA/hfi1: Se corrige el error de use-after-free para la estructura mm En determinadas condiciones, como MPI_Abort, el c\u00f3digo de limpieza hfi1 puede representar la \u00faltima referencia retenida en la tarea mm. Luego, hfi1_mmu_rb_unregister() elimina la \u00faltima referencia y la mm se libera antes del uso final en hfi1_release_user_pages(). Una nueva tarea puede asignar la estructura mm mientras a\u00fan se est\u00e1 utilizando, lo que genera problemas. Una manifestaci\u00f3n es la corrupci\u00f3n del contador mmap_sem que provoca un bloqueo en down_write(). Otra es la corrupci\u00f3n de una estructura mm que est\u00e1 en uso por otra tarea."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/0b7186d657ee55e2cdefae498f07d5c1961e8023",
diff --git a/CVE-2022/CVE-2022-490xx/CVE-2022-49082.json b/CVE-2022/CVE-2022-490xx/CVE-2022-49082.json
index 10d1d51ce12..85598c38afa 100644
--- a/CVE-2022/CVE-2022-490xx/CVE-2022-49082.json
+++ b/CVE-2022/CVE-2022-490xx/CVE-2022-49082.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49082",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:45.540",
- "lastModified": "2025-02-26T07:00:45.540",
+ "lastModified": "2025-02-27T19:15:41.353",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpt3sas: Fix use after free in _scsih_expander_node_remove()\n\nThe function mpt3sas_transport_port_remove() called in\n_scsih_expander_node_remove() frees the port field of the sas_expander\nstructure, leading to the following use-after-free splat from KASAN when\nthe ioc_info() call following that function is executed (e.g. when doing\nrmmod of the driver module):\n\n[ 3479.371167] ==================================================================\n[ 3479.378496] BUG: KASAN: use-after-free in _scsih_expander_node_remove+0x710/0x750 [mpt3sas]\n[ 3479.386936] Read of size 1 at addr ffff8881c037691c by task rmmod/1531\n[ 3479.393524]\n[ 3479.395035] CPU: 18 PID: 1531 Comm: rmmod Not tainted 5.17.0-rc8+ #1436\n[ 3479.401712] Hardware name: Supermicro Super Server/H12SSL-NT, BIOS 2.1 06/02/2021\n[ 3479.409263] Call Trace:\n[ 3479.411743] \n[ 3479.413875] dump_stack_lvl+0x45/0x59\n[ 3479.417582] print_address_description.constprop.0+0x1f/0x120\n[ 3479.423389] ? _scsih_expander_node_remove+0x710/0x750 [mpt3sas]\n[ 3479.429469] kasan_report.cold+0x83/0xdf\n[ 3479.433438] ? _scsih_expander_node_remove+0x710/0x750 [mpt3sas]\n[ 3479.439514] _scsih_expander_node_remove+0x710/0x750 [mpt3sas]\n[ 3479.445411] ? _raw_spin_unlock_irqrestore+0x2d/0x40\n[ 3479.452032] scsih_remove+0x525/0xc90 [mpt3sas]\n[ 3479.458212] ? mpt3sas_expander_remove+0x1d0/0x1d0 [mpt3sas]\n[ 3479.465529] ? down_write+0xde/0x150\n[ 3479.470746] ? up_write+0x14d/0x460\n[ 3479.475840] ? kernfs_find_ns+0x137/0x310\n[ 3479.481438] pci_device_remove+0x65/0x110\n[ 3479.487013] __device_release_driver+0x316/0x680\n[ 3479.493180] driver_detach+0x1ec/0x2d0\n[ 3479.498499] bus_remove_driver+0xe7/0x2d0\n[ 3479.504081] pci_unregister_driver+0x26/0x250\n[ 3479.510033] _mpt3sas_exit+0x2b/0x6cf [mpt3sas]\n[ 3479.516144] __x64_sys_delete_module+0x2fd/0x510\n[ 3479.522315] ? free_module+0xaa0/0xaa0\n[ 3479.527593] ? __cond_resched+0x1c/0x90\n[ 3479.532951] ? lockdep_hardirqs_on_prepare+0x273/0x3e0\n[ 3479.539607] ? syscall_enter_from_user_mode+0x21/0x70\n[ 3479.546161] ? trace_hardirqs_on+0x1c/0x110\n[ 3479.551828] do_syscall_64+0x35/0x80\n[ 3479.556884] entry_SYSCALL_64_after_hwframe+0x44/0xae\n[ 3479.563402] RIP: 0033:0x7f1fc482483b\n...\n[ 3479.943087] ==================================================================\n\nFix this by introducing the local variable port_id to store the port ID\nvalue before executing mpt3sas_transport_port_remove(). This local variable\nis then used in the call to ioc_info() instead of dereferencing the freed\nport structure."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: scsi: mpt3sas: Se corrige el use-after-free en _scsih_expander_node_remove() La funci\u00f3n mpt3sas_transport_port_remove() llamada en _scsih_expander_node_remove() libera el campo de puerto de la estructura sas_expander, lo que lleva al siguiente splat de use-after-free de KASAN cuando se ejecuta la llamada ioc_info() despu\u00e9s de esa funci\u00f3n (por ejemplo, al realizar rmmod del m\u00f3dulo del controlador): [ 3479.371167] ===================================================================== [ 3479.378496] ERROR: KASAN: use-after-free en _scsih_expander_node_remove+0x710/0x750 [mpt3sas] [ 3479.386936] Lectura de tama\u00f1o 1 en la direcci\u00f3n ffff8881c037691c por la tarea rmmod/1531 [ 3479.393524] [ 3479.395035] CPU: 18 PID: 1531 Comm: rmmod No contaminado 5.17.0-rc8+ #1436 [ 3479.401712] Nombre del hardware: Supermicro Super Server/H12SSL-NT, BIOS 2.1 06/02/2021 [ 3479.409263] Call Trace: [ 3479.411743] [ 3479.413875] dump_stack_lvl+0x45/0x59 [ 3479.417582] print_address_description.constprop.0+0x1f/0x120 [ 3479.423389] ? _scsih_expander_node_remove+0x710/0x750 [mpt3sas] [ 3479.429469] kasan_report.cold+0x83/0xdf [ 3479.433438] ? _scsih_expander_node_remove+0x710/0x750 [mpt3sas] [ 3479.439514] _scsih_expander_node_remove+0x710/0x750 [mpt3sas] [ 3479.445411] ? _raw_spin_unlock_irqrestore+0x2d/0x40 [ 3479.452032] scsih_remove+0x525/0xc90 [mpt3sas] [ 3479.458212] ? mpt3sas_expander_remove+0x1d0/0x1d0 [mpt3sas] [ 3479.465529] ? down_write+0xde/0x150 [ 3479.470746] ? up_write+0x14d/0x460 [ 3479.475840] ? kernfs_find_ns+0x137/0x310 [ 3479.481438] pci_device_remove+0x65/0x110 [ 3479.487013] __device_release_driver+0x316/0x680 [ 3479.493180] driver_detach+0x1ec/0x2d0 [ 3479.498499] bus_remove_driver+0xe7/0x2d0 [ 3479.504081] pci_unregister_driver+0x26/0x250 [ 3479.510033] _mpt3sas_exit+0x2b/0x6cf [mpt3sas] [ 3479.516144] __x64_sys_delete_module+0x2fd/0x510 [ 3479.522315] ? free_module+0xaa0/0xaa0 [ 3479.527593] ? __cond_resched+0x1c/0x90 [ 3479.532951] ? lockdep_hardirqs_on_prepare+0x273/0x3e0 [ 3479.539607] ? syscall_enter_from_user_mode+0x21/0x70 [ 3479.546161] ? trace_hardirqs_on+0x1c/0x110 [ 3479.551828] do_syscall_64+0x35/0x80 [ 3479.556884] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 3479.563402] RIP: 0033:0x7f1fc482483b ... [ 3479.943087] ======================================================================== Solucione esto introduciendo la variable local port_id para almacenar el valor del ID del puerto antes de ejecutar mpt3sas_transport_port_remove(). Luego, esta variable local se utiliza en la llamada a ioc_info() en lugar de desreferenciar la estructura del puerto liberado."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/17d66b1c92bcb41e72271ec60069d3684aaa1c9c",
diff --git a/CVE-2022/CVE-2022-490xx/CVE-2022-49087.json b/CVE-2022/CVE-2022-490xx/CVE-2022-49087.json
index 001af1741e3..1d8003d1c28 100644
--- a/CVE-2022/CVE-2022-490xx/CVE-2022-49087.json
+++ b/CVE-2022/CVE-2022-490xx/CVE-2022-49087.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49087",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:46.043",
- "lastModified": "2025-02-26T07:00:46.043",
+ "lastModified": "2025-02-27T19:15:41.493",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: fix a race in rxrpc_exit_net()\n\nCurrent code can lead to the following race:\n\nCPU0 CPU1\n\nrxrpc_exit_net()\n rxrpc_peer_keepalive_worker()\n if (rxnet->live)\n\n rxnet->live = false;\n del_timer_sync(&rxnet->peer_keepalive_timer);\n\n timer_reduce(&rxnet->peer_keepalive_timer, jiffies + delay);\n\n cancel_work_sync(&rxnet->peer_keepalive_work);\n\nrxrpc_exit_net() exits while peer_keepalive_timer is still armed,\nleading to use-after-free.\n\nsyzbot report was:\n\nODEBUG: free active (active state 0) object type: timer_list hint: rxrpc_peer_keepalive_timeout+0x0/0xb0\nWARNING: CPU: 0 PID: 3660 at lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505\nModules linked in:\nCPU: 0 PID: 3660 Comm: kworker/u4:6 Not tainted 5.17.0-syzkaller-13993-g88e6c0207623 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nWorkqueue: netns cleanup_net\nRIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505\nCode: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd 00 1c 26 8a 4c 89 ee 48 c7 c7 00 10 26 8a e8 b1 e7 28 05 <0f> 0b 83 05 15 eb c5 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3\nRSP: 0018:ffffc9000353fb00 EFLAGS: 00010082\nRAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000\nRDX: ffff888029196140 RSI: ffffffff815efad8 RDI: fffff520006a7f52\nRBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000\nR10: ffffffff815ea4ae R11: 0000000000000000 R12: ffffffff89ce23e0\nR13: ffffffff8a2614e0 R14: ffffffff816628c0 R15: dffffc0000000000\nFS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fe1f2908924 CR3: 0000000043720000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \n __debug_check_no_obj_freed lib/debugobjects.c:992 [inline]\n debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1023\n kfree+0xd6/0x310 mm/slab.c:3809\n ops_free_list.part.0+0x119/0x370 net/core/net_namespace.c:176\n ops_free_list net/core/net_namespace.c:174 [inline]\n cleanup_net+0x591/0xb00 net/core/net_namespace.c:598\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:298\n "
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: rxrpc: se corrige una ejecuci\u00f3n en rxrpc_exit_net() El c\u00f3digo actual puede llevar a la siguiente ejecuci\u00f3n: CPU0 CPU1 rxrpc_exit_net() rxrpc_peer_keepalive_worker() if (rxnet->live) rxnet->live = false; del_timer_sync(&rxnet->peer_keepalive_timer); timer_reduce(&rxnet->peer_keepalive_timer, jiffies + delay); cancel_work_sync(&rxnet->peer_keepalive_work); rxrpc_exit_net() sale mientras peer_keepalive_timer todav\u00eda est\u00e1 armado, lo que lleva a un use-after-free. El informe de syzbot fue: ODEBUG: activo libre (estado activo 0) tipo de objeto: timer_list sugerencia: rxrpc_peer_keepalive_timeout+0x0/0xb0 ADVERTENCIA: CPU: 0 PID: 3660 en lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505 M\u00f3dulos vinculados en: CPU: 0 PID: 3660 Comm: kworker/u4:6 No contaminado 5.17.0-syzkaller-13993-g88e6c0207623 #0 Nombre del hardware: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Cola de trabajo: netns cleanup_net RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505 C\u00f3digo: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd 00 1c 26 8a 4c 89 ee 48 c7 c7 00 10 26 8a e8 b1 e7 28 05 <0f> 0b 83 05 15 eb c5 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3 RSP: 0018:ffffc9000353fb00 EFLAGS: 00010082 RAX: 0000000000000000 RBX: 00000000000000003 RCX: 0000000000000000 RDX: ffff888029196140 RSI: ffffffff815efad8 RDI: fffff520006a7f52 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815ea4ae R11: 0000000000000000 R12: ffffffff89ce23e0 R13: ffffffff8a2614e0 R14: ffffffff816628c0 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe1f2908924 CR3: 0000000043720000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 00000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Seguimiento de llamadas: __debug_check_no_obj_freed lib/debugobjects.c:992 [en l\u00ednea] debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1023 kfree+0xd6/0x310 mm/slab.c:3809 ops_free_list.part.0+0x119/0x370 net/core/net_namespace.c:176 ops_free_list net/core/net_namespace.c:174 [en l\u00ednea] cleanup_net+0x591/0xb00 net/core/net_namespace.c:598 process_one_work+0x996/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 "
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/08ff0e74fab517dbc44e11b8bc683dd4ecc65950",
diff --git a/CVE-2022/CVE-2022-490xx/CVE-2022-49093.json b/CVE-2022/CVE-2022-490xx/CVE-2022-49093.json
index c401de6358a..984393d98b9 100644
--- a/CVE-2022/CVE-2022-490xx/CVE-2022-49093.json
+++ b/CVE-2022/CVE-2022-490xx/CVE-2022-49093.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49093",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:46.633",
- "lastModified": "2025-02-26T07:00:46.633",
+ "lastModified": "2025-02-27T19:15:41.640",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nskbuff: fix coalescing for page_pool fragment recycling\n\nFix a use-after-free when using page_pool with page fragments. We\nencountered this problem during normal RX in the hns3 driver:\n\n(1) Initially we have three descriptors in the RX queue. The first one\n allocates PAGE1 through page_pool, and the other two allocate one\n half of PAGE2 each. Page references look like this:\n\n RX_BD1 _______ PAGE1\n RX_BD2 _______ PAGE2\n RX_BD3 _________/\n\n(2) Handle RX on the first descriptor. Allocate SKB1, eventually added\n to the receive queue by tcp_queue_rcv().\n\n(3) Handle RX on the second descriptor. Allocate SKB2 and pass it to\n netif_receive_skb():\n\n netif_receive_skb(SKB2)\n ip_rcv(SKB2)\n SKB3 = skb_clone(SKB2)\n\n SKB2 and SKB3 share a reference to PAGE2 through\n skb_shinfo()->dataref. The other ref to PAGE2 is still held by\n RX_BD3:\n\n SKB2 ---+- PAGE2\n SKB3 __/ /\n RX_BD3 _________/\n\n (3b) Now while handling TCP, coalesce SKB3 with SKB1:\n\n tcp_v4_rcv(SKB3)\n tcp_try_coalesce(to=SKB1, from=SKB3) // succeeds\n kfree_skb_partial(SKB3)\n skb_release_data(SKB3) // drops one dataref\n\n SKB1 _____ PAGE1\n \\____\n SKB2 _____ PAGE2\n /\n RX_BD3 _________/\n\n In skb_try_coalesce(), __skb_frag_ref() takes a page reference to\n PAGE2, where it should instead have increased the page_pool frag\n reference, pp_frag_count. Without coalescing, when releasing both\n SKB2 and SKB3, a single reference to PAGE2 would be dropped. Now\n when releasing SKB1 and SKB2, two references to PAGE2 will be\n dropped, resulting in underflow.\n\n (3c) Drop SKB2:\n\n af_packet_rcv(SKB2)\n consume_skb(SKB2)\n skb_release_data(SKB2) // drops second dataref\n page_pool_return_skb_page(PAGE2) // drops one pp_frag_count\n\n SKB1 _____ PAGE1\n \\____\n PAGE2\n /\n RX_BD3 _________/\n\n(4) Userspace calls recvmsg()\n Copies SKB1 and releases it. Since SKB3 was coalesced with SKB1, we\n release the SKB3 page as well:\n\n tcp_eat_recv_skb(SKB1)\n skb_release_data(SKB1)\n page_pool_return_skb_page(PAGE1)\n page_pool_return_skb_page(PAGE2) // drops second pp_frag_count\n\n(5) PAGE2 is freed, but the third RX descriptor was still using it!\n In our case this causes IOMMU faults, but it would silently corrupt\n memory if the IOMMU was disabled.\n\nChange the logic that checks whether pp_recycle SKBs can be coalesced.\nWe still reject differing pp_recycle between 'from' and 'to' SKBs, but\nin order to avoid the situation described above, we also reject\ncoalescing when both 'from' and 'to' are pp_recycled and 'from' is\ncloned.\n\nThe new logic allows coalescing a cloned pp_recycle SKB into a page\nrefcounted one, because in this case the release (4) will drop the right\nreference, the one taken by skb_try_coalesce()."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: skbuff: correcci\u00f3n de coalescencia para reciclaje de fragmentos de page_pool Corrige un use-after-free al usar page_pool con fragmentos de p\u00e1gina. Encontramos este problema durante RX normal en el controlador hns3: (1) Inicialmente tenemos tres descriptores en la cola RX. El primero asigna PAGE1 a trav\u00e9s de page_pool, y los otros dos asignan la mitad de PAGE2 cada uno. Las referencias de p\u00e1gina se ven as\u00ed: RX_BD1 _______ PAGE1 RX_BD2 _______ PAGE2 RX_BD3 _________/ (2) Manejar RX en el primer descriptor. Asignar SKB1, eventualmente agregado a la cola de recepci\u00f3n por tcp_queue_rcv(). (3) Manejar RX en el segundo descriptor. Asigne SKB2 y p\u00e1selo a netif_receive_skb(): netif_receive_skb(SKB2) ip_rcv(SKB2) SKB3 = skb_clone(SKB2) SKB2 y SKB3 comparten una referencia a PAGE2 a trav\u00e9s de skb_shinfo()->dataref. La otra referencia a PAGE2 todav\u00eda la mantiene RX_BD3: SKB2 ---+- PAGE2 SKB3 __/ / RX_BD3 _________/ (3b) Ahora, mientras maneja TCP, fusione SKB3 con SKB1: tcp_v4_rcv(SKB3) tcp_try_coalesce(to=SKB1, from=SKB3) // tiene \u00e9xito kfree_skb_partial(SKB3) skb_release_data(SKB3) // elimina una referencia de datos SKB1 _____ PAGE1 \\____ SKB2 _____ PAGE2 / RX_BD3 _________/ En skb_try_coalesce(), __skb_frag_ref() toma una referencia de p\u00e1gina a PAGE2, donde en cambio deber\u00eda haber aumentado la referencia de fragmento de page_pool, pp_frag_count. Sin la fusi\u00f3n, al liberar SKB2 y SKB3, se eliminar\u00eda una \u00fanica referencia a PAGE2. Ahora, al liberar SKB1 y SKB2, se descartar\u00e1n dos referencias a PAGE2, lo que provocar\u00e1 un desbordamiento. (3c) Descartar SKB2: af_packet_rcv(SKB2) consume_skb(SKB2) skb_release_data(SKB2) // descarta la segunda referencia de datos page_pool_return_skb_page(PAGE2) // descarta una pp_frag_count SKB1 _____ PAGE1 \\____ PAGE2 / RX_BD3 _________/ (4) El espacio de usuario llama a recvmsg() Copia SKB1 y lo libera. Dado que SKB3 se fusion\u00f3 con SKB1, tambi\u00e9n liberamos la p\u00e1gina SKB3: tcp_eat_recv_skb(SKB1) skb_release_data(SKB1) page_pool_return_skb_page(PAGE1) page_pool_return_skb_page(PAGE2) // elimina el segundo pp_frag_count (5) PAGE2 se libera, \u00a1pero el tercer descriptor RX todav\u00eda lo estaba usando! En nuestro caso, esto causa fallas de IOMMU, pero corromper\u00eda silenciosamente la memoria si IOMMU estuviera deshabilitado. Cambie la l\u00f3gica que verifica si los SKB pp_recycle se pueden fusionar. A\u00fan rechazamos diferentes pp_recycle entre SKB 'from' y 'to', pero para evitar la situaci\u00f3n descrita anteriormente, tambi\u00e9n rechazamos la fusi\u00f3n cuando tanto 'from' como 'to' son pp_recycled y 'from' es clonado. La nueva l\u00f3gica permite fusionar un SKB pp_recycle clonado en uno con referencia de p\u00e1gina, porque en este caso la versi\u00f3n (4) eliminar\u00e1 la referencia correcta, la tomada por skb_try_coalesce()."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/1effe8ca4e34c34cdd9318436a4232dcb582ebf4",
diff --git a/CVE-2022/CVE-2022-491xx/CVE-2022-49111.json b/CVE-2022/CVE-2022-491xx/CVE-2022-49111.json
index e8c2326881d..509fb41e1e2 100644
--- a/CVE-2022/CVE-2022-491xx/CVE-2022-49111.json
+++ b/CVE-2022/CVE-2022-491xx/CVE-2022-49111.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49111",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:48.470",
- "lastModified": "2025-02-26T07:00:48.470",
+ "lastModified": "2025-02-27T19:15:41.783",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix use after free in hci_send_acl\n\nThis fixes the following trace caused by receiving\nHCI_EV_DISCONN_PHY_LINK_COMPLETE which does call hci_conn_del without\nfirst checking if conn->type is in fact AMP_LINK and in case it is\ndo properly cleanup upper layers with hci_disconn_cfm:\n\n ==================================================================\n BUG: KASAN: use-after-free in hci_send_acl+0xaba/0xc50\n Read of size 8 at addr ffff88800e404818 by task bluetoothd/142\n\n CPU: 0 PID: 142 Comm: bluetoothd Not tainted\n 5.17.0-rc5-00006-gda4022eeac1a #7\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014\n Call Trace:\n \n dump_stack_lvl+0x45/0x59\n print_address_description.constprop.0+0x1f/0x150\n kasan_report.cold+0x7f/0x11b\n hci_send_acl+0xaba/0xc50\n l2cap_do_send+0x23f/0x3d0\n l2cap_chan_send+0xc06/0x2cc0\n l2cap_sock_sendmsg+0x201/0x2b0\n sock_sendmsg+0xdc/0x110\n sock_write_iter+0x20f/0x370\n do_iter_readv_writev+0x343/0x690\n do_iter_write+0x132/0x640\n vfs_writev+0x198/0x570\n do_writev+0x202/0x280\n do_syscall_64+0x38/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n RSP: 002b:00007ffce8a099b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014\n Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3\n 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 14 00 00 00 0f 05\n <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10\n RDX: 0000000000000001 RSI: 00007ffce8a099e0 RDI: 0000000000000015\n RAX: ffffffffffffffda RBX: 00007ffce8a099e0 RCX: 00007f788fc3cf77\n R10: 00007ffce8af7080 R11: 0000000000000246 R12: 000055e4ccf75580\n RBP: 0000000000000015 R08: 0000000000000002 R09: 0000000000000001\n \n R13: 000055e4ccf754a0 R14: 000055e4ccf75cd0 R15: 000055e4ccf4a6b0\n\n Allocated by task 45:\n kasan_save_stack+0x1e/0x40\n __kasan_kmalloc+0x81/0xa0\n hci_chan_create+0x9a/0x2f0\n l2cap_conn_add.part.0+0x1a/0xdc0\n l2cap_connect_cfm+0x236/0x1000\n le_conn_complete_evt+0x15a7/0x1db0\n hci_le_conn_complete_evt+0x226/0x2c0\n hci_le_meta_evt+0x247/0x450\n hci_event_packet+0x61b/0xe90\n hci_rx_work+0x4d5/0xc50\n process_one_work+0x8fb/0x15a0\n worker_thread+0x576/0x1240\n kthread+0x29d/0x340\n ret_from_fork+0x1f/0x30\n\n Freed by task 45:\n kasan_save_stack+0x1e/0x40\n kasan_set_track+0x21/0x30\n kasan_set_free_info+0x20/0x30\n __kasan_slab_free+0xfb/0x130\n kfree+0xac/0x350\n hci_conn_cleanup+0x101/0x6a0\n hci_conn_del+0x27e/0x6c0\n hci_disconn_phylink_complete_evt+0xe0/0x120\n hci_event_packet+0x812/0xe90\n hci_rx_work+0x4d5/0xc50\n process_one_work+0x8fb/0x15a0\n worker_thread+0x576/0x1240\n kthread+0x29d/0x340\n ret_from_fork+0x1f/0x30\n\n The buggy address belongs to the object at ffff88800c0f0500\n The buggy address is located 24 bytes inside of\n which belongs to the cache kmalloc-128 of size 128\n The buggy address belongs to the page:\n 128-byte region [ffff88800c0f0500, ffff88800c0f0580)\n flags: 0x100000000000200(slab|node=0|zone=1)\n page:00000000fe45cd86 refcount:1 mapcount:0\n mapping:0000000000000000 index:0x0 pfn:0xc0f0\n raw: 0000000000000000 0000000080100010 00000001ffffffff\n 0000000000000000\n raw: 0100000000000200 ffffea00003a2c80 dead000000000004\n ffff8880078418c0\n page dumped because: kasan: bad access detected\n ffff88800c0f0400: 00 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc\n Memory state around the buggy address:\n >ffff88800c0f0500: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n ffff88800c0f0480: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n ffff88800c0f0580: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n \n---truncated---"
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: Bluetooth: Arreglar use-after-free en hci_send_acl Esto corrige el siguiente rastro causado por recibir HCI_EV_DISCONN_PHY_LINK_COMPLETE que llama a hci_conn_del sin verificar primero si conn->type es de hecho AMP_LINK y en caso de que lo sea, limpia adecuadamente las capas superiores con hci_disconn_cfm: ===================================================================== ERROR: KASAN: use-after-free en hci_send_acl+0xaba/0xc50 Lectura de tama\u00f1o 8 en la direcci\u00f3n ffff88800e404818 por la tarea bluetoothd/142 CPU: 0 PID: 142 Comm: bluetoothd No contaminado 5.17.0-rc5-00006-gda4022eeac1a #7 Nombre del hardware: PC est\u00e1ndar QEMU (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 01/04/2014 Seguimiento de llamadas: dump_stack_lvl+0x45/0x59 print_address_description.constprop.0+0x1f/0x150 kasan_report.cold+0x7f/0x11b hci_send_acl+0xaba/0xc50 l2cap_do_send+0x23f/0x3d0 l2cap_chan_send+0xc06/0x2cc0 l2cap_sock_sendmsg+0x201/0x2b0 sock_sendmsg+0xdc/0x110 sock_write_iter+0x20f/0x370 do_iter_readv_writev+0x343/0x690 do_iter_write+0x132/0x640 vfs_writev+0x198/0x570 do_writev+0x202/0x280 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RSP: 002b:00007ffce8a099b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014 C\u00f3digo: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 14 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 RDX: 0000000000000001 RSI: 00007ffce8a099e0 RDI: 0000000000000015 RAX: ffffffffffffffda RBX: 00007ffce8a099e0 RCX: 00007f788fc3cf77 R10: 00007ffce8af7080 R11: 0000000000000246 R12: 000055e4ccf75580 RBP: 0000000000000015 R08: 0000000000000002 R09: 0000000000000001 R13: 000055e4ccf754a0 R14: 000055e4ccf75cd0 R15: 000055e4ccf4a6b0 Asignado por la tarea 45: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x81/0xa0 hci_chan_create+0x9a/0x2f0 l2cap_conn_add.part.0+0x1a/0xdc0 l2cap_connect_cfm+0x236/0x1000 le_conn_complete_evt+0x15a7/0x1db0 hci_le_conn_complete_evt+0x226/0x2c0 hci_le_meta_evt+0x247/0x450 hci_event_packet+0x61b/0xe90 hci_rx_work+0x4d5/0xc50 process_one_work+0x8fb/0x15a0 worker_thread+0x576/0x1240 kthread+0x29d/0x340 ret_from_fork+0x1f/0x30 Liberado por la tarea 45: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 kasan_set_free_info+0x20/0x30 __kasan_slab_free+0xfb/0x130 kfree+0xac/0x350 hci_conn_cleanup+0x101/0x6a0 hci_conn_del+0x27e/0x6c0 hci_disconn_phylink_complete_evt+0xe0/0x120 hci_event_packet+0x812/0xe90 hci_rx_work+0x4d5/0xc50 process_one_work+0x8fb/0x15a0 worker_thread+0x576/0x1240 kthread+0x29d/0x340 ret_from_fork+0x1f/0x30 La direcci\u00f3n con errores pertenece al objeto en ffff88800c0f0500 La direcci\u00f3n con errores se encuentra a 24 bytes dentro del cual pertenece al cach\u00e9 kmalloc-128 de tama\u00f1o 128 La direcci\u00f3n con errores pertenece a la p\u00e1gina: regi\u00f3n de 128 bytes [ffff88800c0f0500, ffff88800c0f0580) flags: 0x100000000000200(slab|node=0|zone=1) page:00000000fe45cd86 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xc0f0 raw: 000000000000000 0000000080100010 00000001ffffffff 0000000000000000 sin procesar: 01000000000000200 ffffea00003a2c80 muerto000000000004 ffff8880078418c0 p\u00e1gina volcada porque: kasan: acceso incorrecto detectado ffff88800c0f0400: 00 00 00 00 00 00 00 00 00 00 00 00 00 fc fc fc Estado de la memoria alrededor de la direcci\u00f3n con errores: >ffff88800c0f0500: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88800c0f0480: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88800c0f0580: fc fc fc fc fc fc fc fc fc fc fc fc ---truncado---"
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2cc803804ec9a296b3156855d6c8c4ca1c6b84be",
diff --git a/CVE-2022/CVE-2022-491xx/CVE-2022-49127.json b/CVE-2022/CVE-2022-491xx/CVE-2022-49127.json
index 1bfbf7518e8..4954831e6ac 100644
--- a/CVE-2022/CVE-2022-491xx/CVE-2022-49127.json
+++ b/CVE-2022/CVE-2022-491xx/CVE-2022-49127.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49127",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:50.023",
- "lastModified": "2025-02-26T07:00:50.023",
+ "lastModified": "2025-02-27T19:15:41.930",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nref_tracker: implement use-after-free detection\n\nWhenever ref_tracker_dir_init() is called, mark the struct ref_tracker_dir\nas dead.\n\nTest the dead status from ref_tracker_alloc() and ref_tracker_free()\n\nThis should detect buggy dev_put()/dev_hold() happening too late\nin netdevice dismantle process."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/3743c9de303fa36c2e2ca2522ab280c52bcafbd2",
diff --git a/CVE-2022/CVE-2022-491xx/CVE-2022-49129.json b/CVE-2022/CVE-2022-491xx/CVE-2022-49129.json
index a262a0037c8..c26ef6f99e1 100644
--- a/CVE-2022/CVE-2022-491xx/CVE-2022-49129.json
+++ b/CVE-2022/CVE-2022-491xx/CVE-2022-49129.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49129",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:50.203",
- "lastModified": "2025-02-26T07:00:50.203",
+ "lastModified": "2025-02-27T19:15:42.063",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmt76: mt7921: fix crash when startup fails.\n\nIf the nic fails to start, it is possible that the\nreset_work has already been scheduled. Ensure the\nwork item is canceled so we do not have use-after-free\ncrash in case cleanup is called before the work item\nis executed.\n\nThis fixes crash on my x86_64 apu2 when mt7921k radio\nfails to work. Radio still fails, but OS does not\ncrash."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/38fbe806645090c07aa97171f20fc62c3d7d3a98",
diff --git a/CVE-2022/CVE-2022-491xx/CVE-2022-49168.json b/CVE-2022/CVE-2022-491xx/CVE-2022-49168.json
index 8bfe94ac0b2..fc472e5d70d 100644
--- a/CVE-2022/CVE-2022-491xx/CVE-2022-49168.json
+++ b/CVE-2022/CVE-2022-491xx/CVE-2022-49168.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49168",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:53.927",
- "lastModified": "2025-02-26T07:00:53.927",
+ "lastModified": "2025-02-27T19:15:42.200",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: do not clean up repair bio if submit fails\n\nThe submit helper will always run bio_endio() on the bio if it fails to\nsubmit, so cleaning up the bio just leads to a variety of use-after-free\nand NULL pointer dereference bugs because we race with the endio\nfunction that is cleaning up the bio. Instead just return BLK_STS_OK as\nthe repair function has to continue to process the rest of the pages,\nand the endio for the repair bio will do the appropriate cleanup for the\npage that it was given."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/8cbc3001a3264d998d6b6db3e23f935c158abd4d",
diff --git a/CVE-2022/CVE-2022-491xx/CVE-2022-49176.json b/CVE-2022/CVE-2022-491xx/CVE-2022-49176.json
index 448f66ac571..a68599b97de 100644
--- a/CVE-2022/CVE-2022-491xx/CVE-2022-49176.json
+++ b/CVE-2022/CVE-2022-491xx/CVE-2022-49176.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49176",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:54.717",
- "lastModified": "2025-02-26T07:00:54.717",
+ "lastModified": "2025-02-27T19:15:42.333",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbfq: fix use-after-free in bfq_dispatch_request\n\nKASAN reports a use-after-free report when doing normal scsi-mq test\n\n[69832.239032] ==================================================================\n[69832.241810] BUG: KASAN: use-after-free in bfq_dispatch_request+0x1045/0x44b0\n[69832.243267] Read of size 8 at addr ffff88802622ba88 by task kworker/3:1H/155\n[69832.244656]\n[69832.245007] CPU: 3 PID: 155 Comm: kworker/3:1H Not tainted 5.10.0-10295-g576c6382529e #8\n[69832.246626] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014\n[69832.249069] Workqueue: kblockd blk_mq_run_work_fn\n[69832.250022] Call Trace:\n[69832.250541] dump_stack+0x9b/0xce\n[69832.251232] ? bfq_dispatch_request+0x1045/0x44b0\n[69832.252243] print_address_description.constprop.6+0x3e/0x60\n[69832.253381] ? __cpuidle_text_end+0x5/0x5\n[69832.254211] ? vprintk_func+0x6b/0x120\n[69832.254994] ? bfq_dispatch_request+0x1045/0x44b0\n[69832.255952] ? bfq_dispatch_request+0x1045/0x44b0\n[69832.256914] kasan_report.cold.9+0x22/0x3a\n[69832.257753] ? bfq_dispatch_request+0x1045/0x44b0\n[69832.258755] check_memory_region+0x1c1/0x1e0\n[69832.260248] bfq_dispatch_request+0x1045/0x44b0\n[69832.261181] ? bfq_bfqq_expire+0x2440/0x2440\n[69832.262032] ? blk_mq_delay_run_hw_queues+0xf9/0x170\n[69832.263022] __blk_mq_do_dispatch_sched+0x52f/0x830\n[69832.264011] ? blk_mq_sched_request_inserted+0x100/0x100\n[69832.265101] __blk_mq_sched_dispatch_requests+0x398/0x4f0\n[69832.266206] ? blk_mq_do_dispatch_ctx+0x570/0x570\n[69832.267147] ? __switch_to+0x5f4/0xee0\n[69832.267898] blk_mq_sched_dispatch_requests+0xdf/0x140\n[69832.268946] __blk_mq_run_hw_queue+0xc0/0x270\n[69832.269840] blk_mq_run_work_fn+0x51/0x60\n[69832.278170] process_one_work+0x6d4/0xfe0\n[69832.278984] worker_thread+0x91/0xc80\n[69832.279726] ? __kthread_parkme+0xb0/0x110\n[69832.280554] ? process_one_work+0xfe0/0xfe0\n[69832.281414] kthread+0x32d/0x3f0\n[69832.282082] ? kthread_park+0x170/0x170\n[69832.282849] ret_from_fork+0x1f/0x30\n[69832.283573]\n[69832.283886] Allocated by task 7725:\n[69832.284599] kasan_save_stack+0x19/0x40\n[69832.285385] __kasan_kmalloc.constprop.2+0xc1/0xd0\n[69832.286350] kmem_cache_alloc_node+0x13f/0x460\n[69832.287237] bfq_get_queue+0x3d4/0x1140\n[69832.287993] bfq_get_bfqq_handle_split+0x103/0x510\n[69832.289015] bfq_init_rq+0x337/0x2d50\n[69832.289749] bfq_insert_requests+0x304/0x4e10\n[69832.290634] blk_mq_sched_insert_requests+0x13e/0x390\n[69832.291629] blk_mq_flush_plug_list+0x4b4/0x760\n[69832.292538] blk_flush_plug_list+0x2c5/0x480\n[69832.293392] io_schedule_prepare+0xb2/0xd0\n[69832.294209] io_schedule_timeout+0x13/0x80\n[69832.295014] wait_for_common_io.constprop.1+0x13c/0x270\n[69832.296137] submit_bio_wait+0x103/0x1a0\n[69832.296932] blkdev_issue_discard+0xe6/0x160\n[69832.297794] blk_ioctl_discard+0x219/0x290\n[69832.298614] blkdev_common_ioctl+0x50a/0x1750\n[69832.304715] blkdev_ioctl+0x470/0x600\n[69832.305474] block_ioctl+0xde/0x120\n[69832.306232] vfs_ioctl+0x6c/0xc0\n[69832.306877] __se_sys_ioctl+0x90/0xa0\n[69832.307629] do_syscall_64+0x2d/0x40\n[69832.308362] entry_SYSCALL_64_after_hwframe+0x44/0xa9\n[69832.309382]\n[69832.309701] Freed by task 155:\n[69832.310328] kasan_save_stack+0x19/0x40\n[69832.311121] kasan_set_track+0x1c/0x30\n[69832.311868] kasan_set_free_info+0x1b/0x30\n[69832.312699] __kasan_slab_free+0x111/0x160\n[69832.313524] kmem_cache_free+0x94/0x460\n[69832.314367] bfq_put_queue+0x582/0x940\n[69832.315112] __bfq_bfqd_reset_in_service+0x166/0x1d0\n[69832.317275] bfq_bfqq_expire+0xb27/0x2440\n[69832.318084] bfq_dispatch_request+0x697/0x44b0\n[69832.318991] __blk_mq_do_dispatch_sched+0x52f/0x830\n[69832.319984] __blk_mq_sched_dispatch_requests+0x398/0x4f0\n[69832.321087] blk_mq_sched_dispatch_requests+0xdf/0x140\n[69832.322225] __blk_mq_run_hw_queue+0xc0/0x270\n[69832.323114] blk_mq_run_work_fn+0x51/0x6\n---truncated---"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/080665e2c3cbfc68359b9a348a3546ed9b908e7a",
diff --git a/CVE-2022/CVE-2022-492xx/CVE-2022-49223.json b/CVE-2022/CVE-2022-492xx/CVE-2022-49223.json
index 7ed3d3e4ce8..68c8fc785f0 100644
--- a/CVE-2022/CVE-2022-492xx/CVE-2022-49223.json
+++ b/CVE-2022/CVE-2022-492xx/CVE-2022-49223.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49223",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:00:59.363",
- "lastModified": "2025-02-26T07:00:59.363",
+ "lastModified": "2025-02-27T19:15:42.473",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/port: Hold port reference until decoder release\n\nKASAN + DEBUG_KOBJECT_RELEASE reports a potential use-after-free in\ncxl_decoder_release() where it goes to reference its parent, a cxl_port,\nto free its id back to port->decoder_ida.\n\n BUG: KASAN: use-after-free in to_cxl_port+0x18/0x90 [cxl_core]\n Read of size 8 at addr ffff888119270908 by task kworker/35:2/379\n\n CPU: 35 PID: 379 Comm: kworker/35:2 Tainted: G OE 5.17.0-rc2+ #198\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Workqueue: events kobject_delayed_cleanup\n Call Trace:\n \n dump_stack_lvl+0x59/0x73\n print_address_description.constprop.0+0x1f/0x150\n ? to_cxl_port+0x18/0x90 [cxl_core]\n kasan_report.cold+0x83/0xdf\n ? to_cxl_port+0x18/0x90 [cxl_core]\n to_cxl_port+0x18/0x90 [cxl_core]\n cxl_decoder_release+0x2a/0x60 [cxl_core]\n device_release+0x5f/0x100\n kobject_cleanup+0x80/0x1c0\n\nThe device core only guarantees parent lifetime until all children are\nunregistered. If a child needs a parent to complete its ->release()\ncallback that child needs to hold a reference to extend the lifetime of\nthe parent."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/49f2dab77a5e1354f5da6ccdc9346a8212697be2",
diff --git a/CVE-2022/CVE-2022-492xx/CVE-2022-49238.json b/CVE-2022/CVE-2022-492xx/CVE-2022-49238.json
index 70377030ede..95d664e0a67 100644
--- a/CVE-2022/CVE-2022-492xx/CVE-2022-49238.json
+++ b/CVE-2022/CVE-2022-492xx/CVE-2022-49238.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49238",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:00.790",
- "lastModified": "2025-02-26T07:01:00.790",
+ "lastModified": "2025-02-27T19:15:42.610",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nath11k: free peer for station when disconnect from AP for QCA6390/WCN6855\n\nCommit b4a0f54156ac (\"ath11k: move peer delete after vdev stop of station\nfor QCA6390 and WCN6855\") is to fix firmware crash by changing the WMI\ncommand sequence, but actually skip all the peer delete operation, then\nit lead commit 58595c9874c6 (\"ath11k: Fixing dangling pointer issue upon\npeer delete failure\") not take effect, and then happened a use-after-free\nwarning from KASAN. because the peer->sta is not set to NULL and then used\nlater.\n\nChange to only skip the WMI_PEER_DELETE_CMDID for QCA6390/WCN6855.\n\nlog of user-after-free:\n\n[ 534.888665] BUG: KASAN: use-after-free in ath11k_dp_rx_update_peer_stats+0x912/0xc10 [ath11k]\n[ 534.888696] Read of size 8 at addr ffff8881396bb1b8 by task rtcwake/2860\n\n[ 534.888705] CPU: 4 PID: 2860 Comm: rtcwake Kdump: loaded Tainted: G W 5.15.0-wt-ath+ #523\n[ 534.888712] Hardware name: Intel(R) Client Systems NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0067.2021.0528.1339 05/28/2021\n[ 534.888716] Call Trace:\n[ 534.888720] \n[ 534.888726] dump_stack_lvl+0x57/0x7d\n[ 534.888736] print_address_description.constprop.0+0x1f/0x170\n[ 534.888745] ? ath11k_dp_rx_update_peer_stats+0x912/0xc10 [ath11k]\n[ 534.888771] kasan_report.cold+0x83/0xdf\n[ 534.888783] ? ath11k_dp_rx_update_peer_stats+0x912/0xc10 [ath11k]\n[ 534.888810] ath11k_dp_rx_update_peer_stats+0x912/0xc10 [ath11k]\n[ 534.888840] ath11k_dp_rx_process_mon_status+0x529/0xa70 [ath11k]\n[ 534.888874] ? ath11k_dp_rx_mon_status_bufs_replenish+0x3f0/0x3f0 [ath11k]\n[ 534.888897] ? check_prev_add+0x20f0/0x20f0\n[ 534.888922] ? __lock_acquire+0xb72/0x1870\n[ 534.888937] ? find_held_lock+0x33/0x110\n[ 534.888954] ath11k_dp_rx_process_mon_rings+0x297/0x520 [ath11k]\n[ 534.888981] ? rcu_read_unlock+0x40/0x40\n[ 534.888990] ? ath11k_dp_rx_pdev_alloc+0xd90/0xd90 [ath11k]\n[ 534.889026] ath11k_dp_service_mon_ring+0x67/0xe0 [ath11k]\n[ 534.889053] ? ath11k_dp_rx_process_mon_rings+0x520/0x520 [ath11k]\n[ 534.889075] call_timer_fn+0x167/0x4a0\n[ 534.889084] ? add_timer_on+0x3b0/0x3b0\n[ 534.889103] ? lockdep_hardirqs_on_prepare.part.0+0x18c/0x370\n[ 534.889117] __run_timers.part.0+0x539/0x8b0\n[ 534.889123] ? ath11k_dp_rx_process_mon_rings+0x520/0x520 [ath11k]\n[ 534.889157] ? call_timer_fn+0x4a0/0x4a0\n[ 534.889164] ? mark_lock_irq+0x1c30/0x1c30\n[ 534.889173] ? clockevents_program_event+0xdd/0x280\n[ 534.889189] ? mark_held_locks+0xa5/0xe0\n[ 534.889203] run_timer_softirq+0x97/0x180\n[ 534.889213] __do_softirq+0x276/0x86a\n[ 534.889230] __irq_exit_rcu+0x11c/0x180\n[ 534.889238] irq_exit_rcu+0x5/0x20\n[ 534.889244] sysvec_apic_timer_interrupt+0x8e/0xc0\n[ 534.889251] \n[ 534.889254] \n[ 534.889259] asm_sysvec_apic_timer_interrupt+0x12/0x20\n[ 534.889265] RIP: 0010:_raw_spin_unlock_irqrestore+0x38/0x70\n[ 534.889271] Code: 74 24 10 e8 ea c2 bf fd 48 89 ef e8 12 53 c0 fd 81 e3 00 02 00 00 75 25 9c 58 f6 c4 02 75 2d 48 85 db 74 01 fb bf 01 00 00 00 13 a7 b5 fd 65 8b 05 cc d9 9c 5e 85 c0 74 0a 5b 5d c3 e8 a0 ee\n[ 534.889276] RSP: 0018:ffffc90002e5f880 EFLAGS: 00000206\n[ 534.889284] RAX: 0000000000000006 RBX: 0000000000000200 RCX: ffffffff9f256f10\n[ 534.889289] RDX: 0000000000000000 RSI: ffffffffa1c6e420 RDI: 0000000000000001\n[ 534.889293] RBP: ffff8881095e6200 R08: 0000000000000001 R09: ffffffffa40d2b8f\n[ 534.889298] R10: fffffbfff481a571 R11: 0000000000000001 R12: ffff8881095e6e68\n[ 534.889302] R13: ffffc90002e5f908 R14: 0000000000000246 R15: 0000000000000000\n[ 534.889316] ? mark_lock+0xd0/0x14a0\n[ 534.889332] klist_next+0x1d4/0x450\n[ 534.889340] ? dpm_wait_for_subordinate+0x2d0/0x2d0\n[ 534.889350] device_for_each_child+0xa8/0x140\n[ 534.889360] ? device_remove_class_symlinks+0x1b0/0x1b0\n[ 534.889370] ? __lock_release+0x4bd/0x9f0\n[ 534.889378] ? dpm_suspend+0x26b/0x3f0\n[ 534.889390] dpm_wait_for_subordinate+\n---truncated---"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/212ad7cb7d7592669c067125949e0a8e31ce6a0b",
diff --git a/CVE-2022/CVE-2022-492xx/CVE-2022-49270.json b/CVE-2022/CVE-2022-492xx/CVE-2022-49270.json
index 88bb9986a32..8e3fad46a41 100644
--- a/CVE-2022/CVE-2022-492xx/CVE-2022-49270.json
+++ b/CVE-2022/CVE-2022-492xx/CVE-2022-49270.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49270",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:03.907",
- "lastModified": "2025-02-26T07:01:03.907",
+ "lastModified": "2025-02-27T19:15:42.757",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm: fix use-after-free in dm_cleanup_zoned_dev()\n\ndm_cleanup_zoned_dev() uses queue, so it must be called\nbefore blk_cleanup_disk() starts its killing:\n\nblk_cleanup_disk->blk_cleanup_queue()->kobject_put()->blk_release_queue()->\n->...RCU...->blk_free_queue_rcu()->kmem_cache_free()\n\nOtherwise, RCU callback may be executed first and\ndm_cleanup_zoned_dev() will touch free'd memory:\n\n BUG: KASAN: use-after-free in dm_cleanup_zoned_dev+0x33/0xd0\n Read of size 8 at addr ffff88805ac6e430 by task dmsetup/681\n\n CPU: 4 PID: 681 Comm: dmsetup Not tainted 5.17.0-rc2+ #6\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014\n Call Trace:\n \n dump_stack_lvl+0x57/0x7d\n print_address_description.constprop.0+0x1f/0x150\n ? dm_cleanup_zoned_dev+0x33/0xd0\n kasan_report.cold+0x7f/0x11b\n ? dm_cleanup_zoned_dev+0x33/0xd0\n dm_cleanup_zoned_dev+0x33/0xd0\n __dm_destroy+0x26a/0x400\n ? dm_blk_ioctl+0x230/0x230\n ? up_write+0xd8/0x270\n dev_remove+0x156/0x1d0\n ctl_ioctl+0x269/0x530\n ? table_clear+0x140/0x140\n ? lock_release+0xb2/0x750\n ? remove_all+0x40/0x40\n ? rcu_read_lock_sched_held+0x12/0x70\n ? lock_downgrade+0x3c0/0x3c0\n ? rcu_read_lock_sched_held+0x12/0x70\n dm_ctl_ioctl+0xa/0x10\n __x64_sys_ioctl+0xb9/0xf0\n do_syscall_64+0x3b/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n RIP: 0033:0x7fb6dfa95c27"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/0987f00a76a17aa7213da492c00ed9e5a6210c73",
diff --git a/CVE-2022/CVE-2022-492xx/CVE-2022-49287.json b/CVE-2022/CVE-2022-492xx/CVE-2022-49287.json
index 791d6330c1e..dbcb02734a2 100644
--- a/CVE-2022/CVE-2022-492xx/CVE-2022-49287.json
+++ b/CVE-2022/CVE-2022-492xx/CVE-2022-49287.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49287",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:05.557",
- "lastModified": "2025-02-26T07:01:05.557",
+ "lastModified": "2025-02-27T19:15:42.893",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntpm: fix reference counting for struct tpm_chip\n\nThe following sequence of operations results in a refcount warning:\n\n1. Open device /dev/tpmrm.\n2. Remove module tpm_tis_spi.\n3. Write a TPM command to the file descriptor opened at step 1.\n\n------------[ cut here ]------------\nWARNING: CPU: 3 PID: 1161 at lib/refcount.c:25 kobject_get+0xa0/0xa4\nrefcount_t: addition on 0; use-after-free.\nModules linked in: tpm_tis_spi tpm_tis_core tpm mdio_bcm_unimac brcmfmac\nsha256_generic libsha256 sha256_arm hci_uart btbcm bluetooth cfg80211 vc4\nbrcmutil ecdh_generic ecc snd_soc_core crc32_arm_ce libaes\nraspberrypi_hwmon ac97_bus snd_pcm_dmaengine bcm2711_thermal snd_pcm\nsnd_timer genet snd phy_generic soundcore [last unloaded: spi_bcm2835]\nCPU: 3 PID: 1161 Comm: hold_open Not tainted 5.10.0ls-main-dirty #2\nHardware name: BCM2711\n[] (unwind_backtrace) from [] (show_stack+0x10/0x14)\n[] (show_stack) from [] (dump_stack+0xc4/0xd8)\n[] (dump_stack) from [] (__warn+0x104/0x108)\n[] (__warn) from [] (warn_slowpath_fmt+0x74/0xb8)\n[] (warn_slowpath_fmt) from [] (kobject_get+0xa0/0xa4)\n[] (kobject_get) from [] (tpm_try_get_ops+0x14/0x54 [tpm])\n[] (tpm_try_get_ops [tpm]) from [] (tpm_common_write+0x38/0x60 [tpm])\n[] (tpm_common_write [tpm]) from [] (vfs_write+0xc4/0x3c0)\n[] (vfs_write) from [] (ksys_write+0x58/0xcc)\n[] (ksys_write) from [] (ret_fast_syscall+0x0/0x4c)\nException stack(0xc226bfa8 to 0xc226bff0)\nbfa0: 00000000 000105b4 00000003 beafe664 00000014 00000000\nbfc0: 00000000 000105b4 000103f8 00000004 00000000 00000000 b6f9c000 beafe684\nbfe0: 0000006c beafe648 0001056c b6eb6944\n---[ end trace d4b8409def9b8b1f ]---\n\nThe reason for this warning is the attempt to get the chip->dev reference\nin tpm_common_write() although the reference counter is already zero.\n\nSince commit 8979b02aaf1d (\"tpm: Fix reference count to main device\") the\nextra reference used to prevent a premature zero counter is never taken,\nbecause the required TPM_CHIP_FLAG_TPM2 flag is never set.\n\nFix this by moving the TPM 2 character device handling from\ntpm_chip_alloc() to tpm_add_char_device() which is called at a later point\nin time when the flag has been set in case of TPM2.\n\nCommit fdc915f7f719 (\"tpm: expose spaces via a device link /dev/tpmrm\")\nalready introduced function tpm_devs_release() to release the extra\nreference but did not implement the required put on chip->devs that results\nin the call of this function.\n\nFix this by putting chip->devs in tpm_chip_unregister().\n\nFinally move the new implementation for the TPM 2 handling into a new\nfunction to avoid multiple checks for the TPM_CHIP_FLAG_TPM2 flag in the\ngood case and error cases."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/290e05f346d1829e849662c97e42d5ad984f5258",
diff --git a/CVE-2022/CVE-2022-493xx/CVE-2022-49328.json b/CVE-2022/CVE-2022-493xx/CVE-2022-49328.json
index f2c85afc5b5..a5b7228ea90 100644
--- a/CVE-2022/CVE-2022-493xx/CVE-2022-49328.json
+++ b/CVE-2022/CVE-2022-493xx/CVE-2022-49328.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49328",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:09.610",
- "lastModified": "2025-02-26T07:01:09.610",
+ "lastModified": "2025-02-27T19:15:43.047",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmt76: fix use-after-free by removing a non-RCU wcid pointer\n\nFixes an issue caught by KASAN about use-after-free in mt76_txq_schedule\nby protecting mtxq->wcid with rcu_lock between mt76_txq_schedule and\nsta_info_[alloc, free].\n\n[18853.876689] ==================================================================\n[18853.876751] BUG: KASAN: use-after-free in mt76_txq_schedule+0x204/0xaf8 [mt76]\n[18853.876773] Read of size 8 at addr ffffffaf989a2138 by task mt76-tx phy0/883\n[18853.876786]\n[18853.876810] CPU: 5 PID: 883 Comm: mt76-tx phy0 Not tainted 5.10.100-fix-510-56778d365941-kasan #5 0b01fbbcf41a530f52043508fec2e31a4215\n\n[18853.876840] Call trace:\n[18853.876861] dump_backtrace+0x0/0x3ec\n[18853.876878] show_stack+0x20/0x2c\n[18853.876899] dump_stack+0x11c/0x1ac\n[18853.876918] print_address_description+0x74/0x514\n[18853.876934] kasan_report+0x134/0x174\n[18853.876948] __asan_report_load8_noabort+0x44/0x50\n[18853.876976] mt76_txq_schedule+0x204/0xaf8 [mt76 074e03e4640e97fe7405ee1fab547b81c4fa45d2]\n[18853.877002] mt76_txq_schedule_all+0x2c/0x48 [mt76 074e03e4640e97fe7405ee1fab547b81c4fa45d2]\n[18853.877030] mt7921_tx_worker+0xa0/0x1cc [mt7921_common f0875ebac9d7b4754e1010549e7db50fbd90a047]\n[18853.877054] __mt76_worker_fn+0x190/0x22c [mt76 074e03e4640e97fe7405ee1fab547b81c4fa45d2]\n[18853.877071] kthread+0x2f8/0x3b8\n[18853.877087] ret_from_fork+0x10/0x30\n[18853.877098]\n[18853.877112] Allocated by task 941:\n[18853.877131] kasan_save_stack+0x38/0x68\n[18853.877147] __kasan_kmalloc+0xd4/0xfc\n[18853.877163] kasan_kmalloc+0x10/0x1c\n[18853.877177] __kmalloc+0x264/0x3c4\n[18853.877294] sta_info_alloc+0x460/0xf88 [mac80211]\n[18853.877410] ieee80211_prep_connection+0x204/0x1ee0 [mac80211]\n[18853.877523] ieee80211_mgd_auth+0x6c4/0xa4c [mac80211]\n[18853.877635] ieee80211_auth+0x20/0x2c [mac80211]\n[18853.877733] rdev_auth+0x7c/0x438 [cfg80211]\n[18853.877826] cfg80211_mlme_auth+0x26c/0x390 [cfg80211]\n[18853.877919] nl80211_authenticate+0x6d4/0x904 [cfg80211]\n[18853.877938] genl_rcv_msg+0x748/0x93c\n[18853.877954] netlink_rcv_skb+0x160/0x2a8\n[18853.877969] genl_rcv+0x3c/0x54\n[18853.877985] netlink_unicast_kernel+0x104/0x1ec\n[18853.877999] netlink_unicast+0x178/0x268\n[18853.878015] netlink_sendmsg+0x3cc/0x5f0\n[18853.878030] sock_sendmsg+0xb4/0xd8\n[18853.878043] ____sys_sendmsg+0x2f8/0x53c\n[18853.878058] ___sys_sendmsg+0xe8/0x150\n[18853.878071] __sys_sendmsg+0xc4/0x1f4\n[18853.878087] __arm64_compat_sys_sendmsg+0x88/0x9c\n[18853.878101] el0_svc_common+0x1b4/0x390\n[18853.878115] do_el0_svc_compat+0x8c/0xdc\n[18853.878131] el0_svc_compat+0x10/0x1c\n[18853.878146] el0_sync_compat_handler+0xa8/0xcc\n[18853.878161] el0_sync_compat+0x188/0x1c0\n[18853.878171]\n[18853.878183] Freed by task 10927:\n[18853.878200] kasan_save_stack+0x38/0x68\n[18853.878215] kasan_set_track+0x28/0x3c\n[18853.878228] kasan_set_free_info+0x24/0x48\n[18853.878244] __kasan_slab_free+0x11c/0x154\n[18853.878259] kasan_slab_free+0x14/0x24\n[18853.878273] slab_free_freelist_hook+0xac/0x1b0\n[18853.878287] kfree+0x104/0x390\n[18853.878402] sta_info_free+0x198/0x210 [mac80211]\n[18853.878515] __sta_info_destroy_part2+0x230/0x2d4 [mac80211]\n[18853.878628] __sta_info_flush+0x300/0x37c [mac80211]\n[18853.878740] ieee80211_set_disassoc+0x2cc/0xa7c [mac80211]\n[18853.878851] ieee80211_mgd_deauth+0x4a4/0x10a0 [mac80211]\n[18853.878962] ieee80211_deauth+0x20/0x2c [mac80211]\n[18853.879057] rdev_deauth+0x7c/0x438 [cfg80211]\n[18853.879150] cfg80211_mlme_deauth+0x274/0x414 [cfg80211]\n[18853.879243] cfg80211_mlme_down+0xe4/0x118 [cfg80211]\n[18853.879335] cfg80211_disconnect+0x218/0x2d8 [cfg80211]\n[18853.879427] __cfg80211_leave+0x17c/0x240 [cfg80211]\n[18853.879519] cfg80211_leave+0x3c/0x58 [cfg80211]\n[18853.879611] wiphy_suspend+0xdc/0x200 [cfg80211]\n[18853.879628] dpm_run_callback+0x58/0x408\n[18853.879642] __device_suspend+0x4cc/0x864\n[18853.879658] async_suspend+0x34/0xf4\n[18\n---truncated---"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/4448327b41738dbfcda680eb4935ff835568f468",
diff --git a/CVE-2022/CVE-2022-493xx/CVE-2022-49349.json b/CVE-2022/CVE-2022-493xx/CVE-2022-49349.json
index 4e8cf325e0c..38955ac7ab6 100644
--- a/CVE-2022/CVE-2022-493xx/CVE-2022-49349.json
+++ b/CVE-2022/CVE-2022-493xx/CVE-2022-49349.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49349",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:11.623",
- "lastModified": "2025-02-26T07:01:11.623",
+ "lastModified": "2025-02-27T19:15:43.190",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: fix use-after-free in ext4_rename_dir_prepare\n\nWe got issue as follows:\nEXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue\next4_get_first_dir_block: bh->b_data=0xffff88810bee6000 len=34478\next4_get_first_dir_block: *parent_de=0xffff88810beee6ae bh->b_data=0xffff88810bee6000\next4_rename_dir_prepare: [1] parent_de=0xffff88810beee6ae\n==================================================================\nBUG: KASAN: use-after-free in ext4_rename_dir_prepare+0x152/0x220\nRead of size 4 at addr ffff88810beee6ae by task rep/1895\n\nCPU: 13 PID: 1895 Comm: rep Not tainted 5.10.0+ #241\nCall Trace:\n dump_stack+0xbe/0xf9\n print_address_description.constprop.0+0x1e/0x220\n kasan_report.cold+0x37/0x7f\n ext4_rename_dir_prepare+0x152/0x220\n ext4_rename+0xf44/0x1ad0\n ext4_rename2+0x11c/0x170\n vfs_rename+0xa84/0x1440\n do_renameat2+0x683/0x8f0\n __x64_sys_renameat+0x53/0x60\n do_syscall_64+0x33/0x40\n entry_SYSCALL_64_after_hwframe+0x44/0xa9\nRIP: 0033:0x7f45a6fc41c9\nRSP: 002b:00007ffc5a470218 EFLAGS: 00000246 ORIG_RAX: 0000000000000108\nRAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f45a6fc41c9\nRDX: 0000000000000005 RSI: 0000000020000180 RDI: 0000000000000005\nRBP: 00007ffc5a470240 R08: 00007ffc5a470160 R09: 0000000020000080\nR10: 00000000200001c0 R11: 0000000000000246 R12: 0000000000400bb0\nR13: 00007ffc5a470320 R14: 0000000000000000 R15: 0000000000000000\n\nThe buggy address belongs to the page:\npage:00000000440015ce refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x10beee\nflags: 0x200000000000000()\nraw: 0200000000000000 ffffea00043ff4c8 ffffea0004325608 0000000000000000\nraw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000\npage dumped because: kasan: bad access detected\n\nMemory state around the buggy address:\n ffff88810beee580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n ffff88810beee600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n>ffff88810beee680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n ^\n ffff88810beee700: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n ffff88810beee780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n==================================================================\nDisabling lock debugging due to kernel taint\next4_rename_dir_prepare: [2] parent_de->inode=3537895424\next4_rename_dir_prepare: [3] dir=0xffff888124170140\next4_rename_dir_prepare: [4] ino=2\next4_rename_dir_prepare: ent->dir->i_ino=2 parent=-757071872\n\nReason is first directory entry which 'rec_len' is 34478, then will get illegal\nparent entry. Now, we do not check directory entry after read directory block\nin 'ext4_get_first_dir_block'.\nTo solve this issue, check directory entry in 'ext4_get_first_dir_block'.\n\n[ Trigger an ext4_error() instead of just warning if the directory is\n missing a '.' or '..' entry. Also make sure we return an error code\n if the file system is corrupted. -TYT ]"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/0be698ecbe4471fcad80e81ec6a05001421041b3",
diff --git a/CVE-2022/CVE-2022-493xx/CVE-2022-49359.json b/CVE-2022/CVE-2022-493xx/CVE-2022-49359.json
index 8a5e3e31b4a..d33b14ca2b3 100644
--- a/CVE-2022/CVE-2022-493xx/CVE-2022-49359.json
+++ b/CVE-2022/CVE-2022-493xx/CVE-2022-49359.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49359",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:12.583",
- "lastModified": "2025-02-26T07:01:12.583",
+ "lastModified": "2025-02-27T19:15:43.347",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/panfrost: Job should reference MMU not file_priv\n\nFor a while now it's been allowed for a MMU context to outlive it's\ncorresponding panfrost_priv, however the job structure still references\npanfrost_priv to get hold of the MMU context. If panfrost_priv has been\nfreed this is a use-after-free which I've been able to trigger resulting\nin a splat.\n\nTo fix this, drop the reference to panfrost_priv in the job structure\nand add a direct reference to the MMU structure which is what's actually\nneeded."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/472dd7ea5e19a1aeabf1711ddc756777e05ee7c2",
diff --git a/CVE-2022/CVE-2022-493xx/CVE-2022-49362.json b/CVE-2022/CVE-2022-493xx/CVE-2022-49362.json
index 891df252312..d59f4fa2503 100644
--- a/CVE-2022/CVE-2022-493xx/CVE-2022-49362.json
+++ b/CVE-2022/CVE-2022-493xx/CVE-2022-49362.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49362",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:12.860",
- "lastModified": "2025-02-26T07:01:12.860",
+ "lastModified": "2025-02-27T19:15:43.487",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Fix potential use-after-free in nfsd_file_put()\n\nnfsd_file_put_noref() can free @nf, so don't dereference @nf\nimmediately upon return from nfsd_file_put_noref()."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/261eabe19cb28e4a8587a4442d257b543d7c2d57",
diff --git a/CVE-2022/CVE-2022-493xx/CVE-2022-49377.json b/CVE-2022/CVE-2022-493xx/CVE-2022-49377.json
index f9a3cad24bc..006f211e33b 100644
--- a/CVE-2022/CVE-2022-493xx/CVE-2022-49377.json
+++ b/CVE-2022/CVE-2022-493xx/CVE-2022-49377.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49377",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:14.357",
- "lastModified": "2025-02-26T07:01:14.357",
+ "lastModified": "2025-02-27T19:15:43.623",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: don't touch ->tagset in blk_mq_get_sq_hctx\n\nblk_mq_run_hw_queues() could be run when there isn't queued request and\nafter queue is cleaned up, at that time tagset is freed, because tagset\nlifetime is covered by driver, and often freed after blk_cleanup_queue()\nreturns.\n\nSo don't touch ->tagset for figuring out current default hctx by the mapping\nbuilt in request queue, so use-after-free on tagset can be avoided. Meantime\nthis way should be fast than retrieving mapping from tagset."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/460aa288c5cd0544dcf933a2f0ad0e8c6d2d35ff",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49412.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49412.json
index 654e483e908..4862d985da7 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49412.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49412.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49412",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:17.703",
- "lastModified": "2025-02-26T07:01:17.703",
+ "lastModified": "2025-02-27T19:15:43.770",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbfq: Avoid merging queues with different parents\n\nIt can happen that the parent of a bfqq changes between the moment we\ndecide two queues are worth to merge (and set bic->stable_merge_bfqq)\nand the moment bfq_setup_merge() is called. This can happen e.g. because\nthe process submitted IO for a different cgroup and thus bfqq got\nreparented. It can even happen that the bfqq we are merging with has\nparent cgroup that is already offline and going to be destroyed in which\ncase the merge can lead to use-after-free issues such as:\n\nBUG: KASAN: use-after-free in __bfq_deactivate_entity+0x9cb/0xa50\nRead of size 8 at addr ffff88800693c0c0 by task runc:[2:INIT]/10544\n\nCPU: 0 PID: 10544 Comm: runc:[2:INIT] Tainted: G E 5.15.2-0.g5fb85fd-default #1 openSUSE Tumbleweed (unreleased) f1f3b891c72369aebecd2e43e4641a6358867c70\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014\nCall Trace:\n \n dump_stack_lvl+0x46/0x5a\n print_address_description.constprop.0+0x1f/0x140\n ? __bfq_deactivate_entity+0x9cb/0xa50\n kasan_report.cold+0x7f/0x11b\n ? __bfq_deactivate_entity+0x9cb/0xa50\n __bfq_deactivate_entity+0x9cb/0xa50\n ? update_curr+0x32f/0x5d0\n bfq_deactivate_entity+0xa0/0x1d0\n bfq_del_bfqq_busy+0x28a/0x420\n ? resched_curr+0x116/0x1d0\n ? bfq_requeue_bfqq+0x70/0x70\n ? check_preempt_wakeup+0x52b/0xbc0\n __bfq_bfqq_expire+0x1a2/0x270\n bfq_bfqq_expire+0xd16/0x2160\n ? try_to_wake_up+0x4ee/0x1260\n ? bfq_end_wr_async_queues+0xe0/0xe0\n ? _raw_write_unlock_bh+0x60/0x60\n ? _raw_spin_lock_irq+0x81/0xe0\n bfq_idle_slice_timer+0x109/0x280\n ? bfq_dispatch_request+0x4870/0x4870\n __hrtimer_run_queues+0x37d/0x700\n ? enqueue_hrtimer+0x1b0/0x1b0\n ? kvm_clock_get_cycles+0xd/0x10\n ? ktime_get_update_offsets_now+0x6f/0x280\n hrtimer_interrupt+0x2c8/0x740\n\nFix the problem by checking that the parent of the two bfqqs we are\nmerging in bfq_setup_merge() is the same."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/5ee21edaed09e6b25f2c007b3f326752bc89bacf",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49413.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49413.json
index 5f1ac9c9ff3..11edf787662 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49413.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49413.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49413",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:17.800",
- "lastModified": "2025-02-26T07:01:17.800",
+ "lastModified": "2025-02-27T19:15:43.910",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbfq: Update cgroup information before merging bio\n\nWhen the process is migrated to a different cgroup (or in case of\nwriteback just starts submitting bios associated with a different\ncgroup) bfq_merge_bio() can operate with stale cgroup information in\nbic. Thus the bio can be merged to a request from a different cgroup or\nit can result in merging of bfqqs for different cgroups or bfqqs of\nalready dead cgroups and causing possible use-after-free issues. Fix the\nproblem by updating cgroup information in bfq_merge_bio()."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/2a1077f17169a6059992a0bbdb330e0abad1e6d9",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49416.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49416.json
index bbee689126f..b5483f19fab 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49416.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49416.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49416",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:18.073",
- "lastModified": "2025-02-26T07:01:18.073",
+ "lastModified": "2025-02-27T19:15:44.047",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: fix use-after-free in chanctx code\n\nIn ieee80211_vif_use_reserved_context(), when we have an\nold context and the new context's replace_state is set to\nIEEE80211_CHANCTX_REPLACE_NONE, we free the old context\nin ieee80211_vif_use_reserved_reassign(). Therefore, we\ncannot check the old_ctx anymore, so we should set it to\nNULL after this point.\n\nHowever, since the new_ctx replace state is clearly not\nIEEE80211_CHANCTX_REPLACES_OTHER, we're not going to do\nanything else in this function and can just return to\navoid accessing the freed old_ctx."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/265bec4779a38b65e86a25120370f200822dfa76",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49419.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49419.json
index 1f21d1a0913..541c6402ff0 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49419.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49419.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49419",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:18.350",
- "lastModified": "2025-02-26T07:01:18.350",
+ "lastModified": "2025-02-27T19:15:44.190",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nvideo: fbdev: vesafb: Fix a use-after-free due early fb_info cleanup\n\nCommit b3c9a924aab6 (\"fbdev: vesafb: Cleanup fb_info in .fb_destroy rather\nthan .remove\") fixed a use-after-free error due the vesafb driver freeing\nthe fb_info in the .remove handler instead of doing it in .fb_destroy.\n\nThis can happen if the .fb_destroy callback is executed after the .remove\ncallback, since the former tries to access a pointer freed by the latter.\n\nBut that change didn't take into account that another possible scenario is\nthat .fb_destroy is called before the .remove callback. For example, if no\nprocess has the fbdev chardev opened by the time the driver is removed.\n\nIf that's the case, fb_info will be freed when unregister_framebuffer() is\ncalled, making the fb_info pointer accessed in vesafb_remove() after that\nto no longer be valid.\n\nTo prevent that, move the expression containing the info->par to happen\nbefore the unregister_framebuffer() function call."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/0fac5f8fb1bc2fc4f8714bf5e743c9cc3f547c63",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49426.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49426.json
index 990854fafc3..f10cb19e428 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49426.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49426.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49426",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:19.073",
- "lastModified": "2025-02-26T07:01:19.073",
+ "lastModified": "2025-02-27T19:15:44.333",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/arm-smmu-v3-sva: Fix mm use-after-free\n\nWe currently call arm64_mm_context_put() without holding a reference to\nthe mm, which can result in use-after-free. Call mmgrab()/mmdrop() to\nensure the mm only gets freed after we unpinned the ASID."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/9aa215450888cf29af0c479e14a712dc6b0c506c",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49464.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49464.json
index cb6046bb05f..77a96263ab1 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49464.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49464.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49464",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:22.697",
- "lastModified": "2025-02-26T07:01:22.697",
+ "lastModified": "2025-02-27T19:15:44.470",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nerofs: fix buffer copy overflow of ztailpacking feature\n\nI got some KASAN report as below:\n\n[ 46.959738] ==================================================================\n[ 46.960430] BUG: KASAN: use-after-free in z_erofs_shifted_transform+0x2bd/0x370\n[ 46.960430] Read of size 4074 at addr ffff8880300c2f8e by task fssum/188\n...\n[ 46.960430] Call Trace:\n[ 46.960430] \n[ 46.960430] dump_stack_lvl+0x41/0x5e\n[ 46.960430] print_report.cold+0xb2/0x6b7\n[ 46.960430] ? z_erofs_shifted_transform+0x2bd/0x370\n[ 46.960430] kasan_report+0x8a/0x140\n[ 46.960430] ? z_erofs_shifted_transform+0x2bd/0x370\n[ 46.960430] kasan_check_range+0x14d/0x1d0\n[ 46.960430] memcpy+0x20/0x60\n[ 46.960430] z_erofs_shifted_transform+0x2bd/0x370\n[ 46.960430] z_erofs_decompress_pcluster+0xaae/0x1080\n\nThe root cause is that the tail pcluster won't be a complete filesystem\nblock anymore. So if ztailpacking is used, the second part of an\nuncompressed tail pcluster may not be ``rq->pageofs_out``."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/4d53a625f29074e7b8236c2c0e0922edb7608df9",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49465.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49465.json
index fd3fffe5773..27720ebfed0 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49465.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49465.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49465",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:22.787",
- "lastModified": "2025-02-26T07:01:22.787",
+ "lastModified": "2025-02-27T19:15:44.603",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-throttle: Set BIO_THROTTLED when bio has been throttled\n\n1.In current process, all bio will set the BIO_THROTTLED flag\nafter __blk_throtl_bio().\n\n2.If bio needs to be throttled, it will start the timer and\nstop submit bio directly. Bio will submit in\nblk_throtl_dispatch_work_fn() when the timer expires.But in\nthe current process, if bio is throttled. The BIO_THROTTLED\nwill be set to bio after timer start. If the bio has been\ncompleted, it may cause use-after-free blow.\n\nBUG: KASAN: use-after-free in blk_throtl_bio+0x12f0/0x2c70\nRead of size 2 at addr ffff88801b8902d4 by task fio/26380\n\n dump_stack+0x9b/0xce\n print_address_description.constprop.6+0x3e/0x60\n kasan_report.cold.9+0x22/0x3a\n blk_throtl_bio+0x12f0/0x2c70\n submit_bio_checks+0x701/0x1550\n submit_bio_noacct+0x83/0xc80\n submit_bio+0xa7/0x330\n mpage_readahead+0x380/0x500\n read_pages+0x1c1/0xbf0\n page_cache_ra_unbounded+0x471/0x6f0\n do_page_cache_ra+0xda/0x110\n ondemand_readahead+0x442/0xae0\n page_cache_async_ra+0x210/0x300\n generic_file_buffered_read+0x4d9/0x2130\n generic_file_read_iter+0x315/0x490\n blkdev_read_iter+0x113/0x1b0\n aio_read+0x2ad/0x450\n io_submit_one+0xc8e/0x1d60\n __se_sys_io_submit+0x125/0x350\n do_syscall_64+0x2d/0x40\n entry_SYSCALL_64_after_hwframe+0x44/0xa9\n\nAllocated by task 26380:\n kasan_save_stack+0x19/0x40\n __kasan_kmalloc.constprop.2+0xc1/0xd0\n kmem_cache_alloc+0x146/0x440\n mempool_alloc+0x125/0x2f0\n bio_alloc_bioset+0x353/0x590\n mpage_alloc+0x3b/0x240\n do_mpage_readpage+0xddf/0x1ef0\n mpage_readahead+0x264/0x500\n read_pages+0x1c1/0xbf0\n page_cache_ra_unbounded+0x471/0x6f0\n do_page_cache_ra+0xda/0x110\n ondemand_readahead+0x442/0xae0\n page_cache_async_ra+0x210/0x300\n generic_file_buffered_read+0x4d9/0x2130\n generic_file_read_iter+0x315/0x490\n blkdev_read_iter+0x113/0x1b0\n aio_read+0x2ad/0x450\n io_submit_one+0xc8e/0x1d60\n __se_sys_io_submit+0x125/0x350\n do_syscall_64+0x2d/0x40\n entry_SYSCALL_64_after_hwframe+0x44/0xa9\n\nFreed by task 0:\n kasan_save_stack+0x19/0x40\n kasan_set_track+0x1c/0x30\n kasan_set_free_info+0x1b/0x30\n __kasan_slab_free+0x111/0x160\n kmem_cache_free+0x94/0x460\n mempool_free+0xd6/0x320\n bio_free+0xe0/0x130\n bio_put+0xab/0xe0\n bio_endio+0x3a6/0x5d0\n blk_update_request+0x590/0x1370\n scsi_end_request+0x7d/0x400\n scsi_io_completion+0x1aa/0xe50\n scsi_softirq_done+0x11b/0x240\n blk_mq_complete_request+0xd4/0x120\n scsi_mq_done+0xf0/0x200\n virtscsi_vq_done+0xbc/0x150\n vring_interrupt+0x179/0x390\n __handle_irq_event_percpu+0xf7/0x490\n handle_irq_event_percpu+0x7b/0x160\n handle_irq_event+0xcc/0x170\n handle_edge_irq+0x215/0xb20\n common_interrupt+0x60/0x120\n asm_common_interrupt+0x1e/0x40\n\nFix this by move BIO_THROTTLED set into the queue_lock."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/0cfc8a0fb07cde61915e4a77c4794c47de3114a4",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49470.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49470.json
index 521340645a0..52b43621ab4 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49470.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49470.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49470",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:23.240",
- "lastModified": "2025-02-26T07:01:23.240",
+ "lastModified": "2025-02-27T19:15:44.743",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event\n\nWe should not access skb buffer data anymore after hci_recv_frame was\ncalled.\n\n[ 39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0\n[ 39.634855] Read of size 1 at addr ffffff80cf28a60d by task kworker\n[ 39.634962] Call trace:\n[ 39.634974] dump_backtrace+0x0/0x3b8\n[ 39.634999] show_stack+0x20/0x2c\n[ 39.635016] dump_stack_lvl+0x60/0x78\n[ 39.635040] print_address_description+0x70/0x2f0\n[ 39.635062] kasan_report+0x154/0x194\n[ 39.635079] __asan_report_load1_noabort+0x44/0x50\n[ 39.635099] btmtksdio_recv_event+0x1b0/0x1c4\n[ 39.635129] btmtksdio_txrx_work+0x6cc/0xac4\n[ 39.635157] process_one_work+0x560/0xc5c\n[ 39.635177] worker_thread+0x7ec/0xcc0\n[ 39.635195] kthread+0x2d0/0x3d0\n[ 39.635215] ret_from_fork+0x10/0x20\n[ 39.635247] Allocated by task 0:\n[ 39.635260] (stack is not available)\n[ 39.635281] Freed by task 2392:\n[ 39.635295] kasan_save_stack+0x38/0x68\n[ 39.635319] kasan_set_track+0x28/0x3c\n[ 39.635338] kasan_set_free_info+0x28/0x4c\n[ 39.635357] ____kasan_slab_free+0x104/0x150\n[ 39.635374] __kasan_slab_free+0x18/0x28\n[ 39.635391] slab_free_freelist_hook+0x114/0x248\n[ 39.635410] kfree+0xf8/0x2b4\n[ 39.635427] skb_free_head+0x58/0x98\n[ 39.635447] skb_release_data+0x2f4/0x410\n[ 39.635464] skb_release_all+0x50/0x60\n[ 39.635481] kfree_skb+0xc8/0x25c\n[ 39.635498] hci_event_packet+0x894/0xca4 [bluetooth]\n[ 39.635721] hci_rx_work+0x1c8/0x68c [bluetooth]\n[ 39.635925] process_one_work+0x560/0xc5c\n[ 39.635951] worker_thread+0x7ec/0xcc0\n[ 39.635970] kthread+0x2d0/0x3d0\n[ 39.635990] ret_from_fork+0x10/0x20\n[ 39.636021] The buggy address belongs to the object at ffffff80cf28a600\n which belongs to the cache kmalloc-512 of size 512\n[ 39.636039] The buggy address is located 13 bytes inside of\n 512-byte region [ffffff80cf28a600, ffffff80cf28a800)"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/01c6a899fa6be4f4cbf60c4f44f0f6691155415f",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49474.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49474.json
index dc1c472a8c9..1d3a38a07c3 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49474.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49474.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49474",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:23.613",
- "lastModified": "2025-02-26T07:01:23.613",
+ "lastModified": "2025-02-27T19:15:44.880",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout\n\nConnecting the same socket twice consecutively in sco_sock_connect()\ncould lead to a race condition where two sco_conn objects are created\nbut only one is associated with the socket. If the socket is closed\nbefore the SCO connection is established, the timer associated with the\ndangling sco_conn object won't be canceled. As the sock object is being\nfreed, the use-after-free problem happens when the timer callback\nfunction sco_sock_timeout() accesses the socket. Here's the call trace:\n\ndump_stack+0x107/0x163\n? refcount_inc+0x1c/\nprint_address_description.constprop.0+0x1c/0x47e\n? refcount_inc+0x1c/0x7b\nkasan_report+0x13a/0x173\n? refcount_inc+0x1c/0x7b\ncheck_memory_region+0x132/0x139\nrefcount_inc+0x1c/0x7b\nsco_sock_timeout+0xb2/0x1ba\nprocess_one_work+0x739/0xbd1\n? cancel_delayed_work+0x13f/0x13f\n? __raw_spin_lock_init+0xf0/0xf0\n? to_kthread+0x59/0x85\nworker_thread+0x593/0x70e\nkthread+0x346/0x35a\n? drain_workqueue+0x31a/0x31a\n? kthread_bind+0x4b/0x4b\nret_from_fork+0x1f/0x30"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/36c644c63bfcaee2d3a426f45e89a9cd09799318",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49479.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49479.json
index 56698c7fd19..eb45c8f57d5 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49479.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49479.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49479",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:24.153",
- "lastModified": "2025-02-26T07:01:24.153",
+ "lastModified": "2025-02-27T19:15:45.023",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmt76: fix tx status related use-after-free race on station removal\n\nThere is a small race window where ongoing tx activity can lead to a skb\ngetting added to the status tracking idr after that idr has already been\ncleaned up, which will keep the wcid linked in the status poll list.\nFix this by only adding status skbs if the wcid pointer is still assigned\nin dev->wcid, which gets cleared early by mt76_sta_pre_rcu_remove"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/ddd426d72aca4054045a9bd3b80a4ce1d398f11f",
diff --git a/CVE-2022/CVE-2022-494xx/CVE-2022-49493.json b/CVE-2022/CVE-2022-494xx/CVE-2022-49493.json
index eaf328d4e00..7559750920f 100644
--- a/CVE-2022/CVE-2022-494xx/CVE-2022-49493.json
+++ b/CVE-2022/CVE-2022-494xx/CVE-2022-49493.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49493",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:25.520",
- "lastModified": "2025-02-26T07:01:25.520",
+ "lastModified": "2025-02-27T19:15:45.153",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: rt5645: Fix errorenous cleanup order\n\nThere is a logic error when removing rt5645 device as the function\nrt5645_i2c_remove() first cancel the &rt5645->jack_detect_work and\ndelete the &rt5645->btn_check_timer latter. However, since the timer\nhandler rt5645_btn_check_callback() will re-queue the jack_detect_work,\nthis cleanup order is buggy.\n\nThat is, once the del_timer_sync in rt5645_i2c_remove is concurrently\nrun with the rt5645_btn_check_callback, the canceled jack_detect_work\nwill be rescheduled again, leading to possible use-after-free.\n\nThis patch fix the issue by placing the del_timer_sync function before\nthe cancel_delayed_work_sync."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/061a6159cea583f1155f67d1915917a6b9282662",
diff --git a/CVE-2022/CVE-2022-495xx/CVE-2022-49501.json b/CVE-2022/CVE-2022-495xx/CVE-2022-49501.json
index 818da5f6ab2..7ee321bd640 100644
--- a/CVE-2022/CVE-2022-495xx/CVE-2022-49501.json
+++ b/CVE-2022/CVE-2022-495xx/CVE-2022-49501.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49501",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:26.257",
- "lastModified": "2025-02-26T07:01:26.257",
+ "lastModified": "2025-02-27T19:15:45.300",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nusbnet: Run unregister_netdev() before unbind() again\n\nCommit 2c9d6c2b871d (\"usbnet: run unbind() before unregister_netdev()\")\nsought to fix a use-after-free on disconnect of USB Ethernet adapters.\n\nIt turns out that a different fix is necessary to address the issue:\nhttps://lore.kernel.org/netdev/18b3541e5372bc9b9fc733d422f4e698c089077c.1650177997.git.lukas@wunner.de/\n\nSo the commit was not necessary.\n\nThe commit made binding and unbinding of USB Ethernet asymmetrical:\nBefore, usbnet_probe() first invoked the ->bind() callback and then\nregister_netdev(). usbnet_disconnect() mirrored that by first invoking\nunregister_netdev() and then ->unbind().\n\nSince the commit, the order in usbnet_disconnect() is reversed and no\nlonger mirrors usbnet_probe().\n\nOne consequence is that a PHY disconnected (and stopped) in ->unbind()\nis afterwards stopped once more by unregister_netdev() as it closes the\nnetdev before unregistering. That necessitates a contortion in ->stop()\nbecause the PHY may only be stopped if it hasn't already been\ndisconnected.\n\nReverting the commit allows making the call to phy_stop() unconditional\nin ->stop()."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/6d5deb242874d924beccf7eb3cef04c1c3b0da79",
diff --git a/CVE-2022/CVE-2022-495xx/CVE-2022-49524.json b/CVE-2022/CVE-2022-495xx/CVE-2022-49524.json
index 3e6a9ee3a86..ae79c8423ac 100644
--- a/CVE-2022/CVE-2022-495xx/CVE-2022-49524.json
+++ b/CVE-2022/CVE-2022-495xx/CVE-2022-49524.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49524",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:28.407",
- "lastModified": "2025-02-26T07:01:28.407",
+ "lastModified": "2025-02-27T19:15:45.433",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: pci: cx23885: Fix the error handling in cx23885_initdev()\n\nWhen the driver fails to call the dma_set_mask(), the driver will get\nthe following splat:\n\n[ 55.853884] BUG: KASAN: use-after-free in __process_removed_driver+0x3c/0x240\n[ 55.854486] Read of size 8 at addr ffff88810de60408 by task modprobe/590\n[ 55.856822] Call Trace:\n[ 55.860327] __process_removed_driver+0x3c/0x240\n[ 55.861347] bus_for_each_dev+0x102/0x160\n[ 55.861681] i2c_del_driver+0x2f/0x50\n\nThis is because the driver has initialized the i2c related resources\nin cx23885_dev_setup() but not released them in error handling, fix this\nbug by modifying the error path that jumps after failing to call the\ndma_set_mask()."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/453514a874c78df1e7804e6e3aaa60c8d8deb6a8",
diff --git a/CVE-2022/CVE-2022-495xx/CVE-2022-49535.json b/CVE-2022/CVE-2022-495xx/CVE-2022-49535.json
index c979a489c93..89bc6af60f1 100644
--- a/CVE-2022/CVE-2022-495xx/CVE-2022-49535.json
+++ b/CVE-2022/CVE-2022-495xx/CVE-2022-49535.json
@@ -2,7 +2,7 @@
"id": "CVE-2022-49535",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:29.490",
- "lastModified": "2025-02-26T07:01:29.490",
+ "lastModified": "2025-02-27T19:15:45.573",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI\n\nIf lpfc_issue_els_flogi() fails and returns non-zero status, the node\nreference count is decremented to trigger the release of the nodelist\nstructure. However, if there is a prior registration or dev-loss-evt work\npending, the node may be released prematurely. When dev-loss-evt\ncompletes, the released node is referenced causing a use-after-free null\npointer dereference.\n\nSimilarly, when processing non-zero ELS PLOGI completion status in\nlpfc_cmpl_els_plogi(), the ndlp flags are checked for a transport\nregistration before triggering node removal. If dev-loss-evt work is\npending, the node may be released prematurely and a subsequent call to\nlpfc_dev_loss_tmo_handler() results in a use after free ndlp dereference.\n\nAdd test for pending dev-loss before decrementing the node reference count\nfor FLOGI, PLOGI, PRLI, and ADISC handling."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/10663ebec0ad5c78493a0dd34c9ee4d73d7ca0df",
diff --git a/CVE-2022/CVE-2022-496xx/CVE-2022-49622.json b/CVE-2022/CVE-2022-496xx/CVE-2022-49622.json
index b39f3b238e1..2660cbfa1a2 100644
--- a/CVE-2022/CVE-2022-496xx/CVE-2022-49622.json
+++ b/CVE-2022/CVE-2022-496xx/CVE-2022-49622.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49622",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:37.580",
- "lastModified": "2025-02-26T07:01:37.580",
+ "lastModified": "2025-02-27T19:15:45.707",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: avoid skb access on nf_stolen\n\nWhen verdict is NF_STOLEN, the skb might have been freed.\n\nWhen tracing is enabled, this can result in a use-after-free:\n1. access to skb->nf_trace\n2. access to skb->mark\n3. computation of trace id\n4. dump of packet payload\n\nTo avoid 1, keep a cached copy of skb->nf_trace in the\ntrace state struct.\nRefresh this copy whenever verdict is != STOLEN.\n\nAvoid 2 by skipping skb->mark access if verdict is STOLEN.\n\n3 is avoided by precomputing the trace id.\n\nOnly dump the packet when verdict is not \"STOLEN\"."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: netfilter: nf_tables: evitar el acceso a skb en nf_stolen Cuando el veredicto es NF_STOLEN, es posible que se haya liberado el skb. Cuando el rastreo est\u00e1 habilitado, esto puede dar como resultado un use-after-free: 1. acceso a skb->nf_trace 2. acceso a skb->mark 3. c\u00e1lculo del identificador de rastreo 4. volcado de el payload del paquete Para evitar 1, mantenga una copia en cach\u00e9 de skb->nf_trace en la estructura de estado de rastreo. Actualice esta copia siempre que el veredicto sea != STOLEN. Evite 2 omitiendo el acceso a skb->mark si el veredicto es STOLEN. 3 se evita precalculando el identificador de rastreo. Solo vuelque el paquete cuando el veredicto no sea \"STOLEN\"."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/0016d5d46d7440729a3132f61a8da3bf7f84e2ba",
diff --git a/CVE-2022/CVE-2022-496xx/CVE-2022-49626.json b/CVE-2022/CVE-2022-496xx/CVE-2022-49626.json
index 15e1ad61fdc..356ed3f9d2d 100644
--- a/CVE-2022/CVE-2022-496xx/CVE-2022-49626.json
+++ b/CVE-2022/CVE-2022-496xx/CVE-2022-49626.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49626",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:37.937",
- "lastModified": "2025-02-26T07:01:37.937",
+ "lastModified": "2025-02-27T19:15:45.850",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsfc: fix use after free when disabling sriov\n\nUse after free is detected by kfence when disabling sriov. What was read\nafter being freed was vf->pci_dev: it was freed from pci_disable_sriov\nand later read in efx_ef10_sriov_free_vf_vports, called from\nefx_ef10_sriov_free_vf_vswitching.\n\nSet the pointer to NULL at release time to not trying to read it later.\n\nReproducer and dmesg log (note that kfence doesn't detect it every time):\n$ echo 1 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs\n$ echo 0 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs\n\n BUG: KFENCE: use-after-free read in efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc]\n\n Use-after-free read at 0x00000000ff3c1ba5 (in kfence-#224):\n efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc]\n efx_ef10_pci_sriov_disable+0x38/0x70 [sfc]\n efx_pci_sriov_configure+0x24/0x40 [sfc]\n sriov_numvfs_store+0xfe/0x140\n kernfs_fop_write_iter+0x11c/0x1b0\n new_sync_write+0x11f/0x1b0\n vfs_write+0x1eb/0x280\n ksys_write+0x5f/0xe0\n do_syscall_64+0x5c/0x80\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n\n kfence-#224: 0x00000000edb8ef95-0x00000000671f5ce1, size=2792, cache=kmalloc-4k\n\n allocated by task 6771 on cpu 10 at 3137.860196s:\n pci_alloc_dev+0x21/0x60\n pci_iov_add_virtfn+0x2a2/0x320\n sriov_enable+0x212/0x3e0\n efx_ef10_sriov_configure+0x67/0x80 [sfc]\n efx_pci_sriov_configure+0x24/0x40 [sfc]\n sriov_numvfs_store+0xba/0x140\n kernfs_fop_write_iter+0x11c/0x1b0\n new_sync_write+0x11f/0x1b0\n vfs_write+0x1eb/0x280\n ksys_write+0x5f/0xe0\n do_syscall_64+0x5c/0x80\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n\n freed by task 6771 on cpu 12 at 3170.991309s:\n device_release+0x34/0x90\n kobject_cleanup+0x3a/0x130\n pci_iov_remove_virtfn+0xd9/0x120\n sriov_disable+0x30/0xe0\n efx_ef10_pci_sriov_disable+0x57/0x70 [sfc]\n efx_pci_sriov_configure+0x24/0x40 [sfc]\n sriov_numvfs_store+0xfe/0x140\n kernfs_fop_write_iter+0x11c/0x1b0\n new_sync_write+0x11f/0x1b0\n vfs_write+0x1eb/0x280\n ksys_write+0x5f/0xe0\n do_syscall_64+0x5c/0x80\n entry_SYSCALL_64_after_hwframe+0x44/0xae"
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sfc: se corrige el use-after-free al deshabilitar sriov. El use-after-free es detectado por kfence al deshabilitar sriov. Lo que se ley\u00f3 despu\u00e9s de ser liberado fue vf->pci_dev: se liber\u00f3 de pci_disable_sriov y luego se ley\u00f3 en efx_ef10_sriov_free_vf_vports, llamado desde efx_ef10_sriov_free_vf_vswitching. Establezca el puntero en NULL en el momento de la liberaci\u00f3n para no intentar leerlo m\u00e1s tarde. Registro del reproductor y dmesg (tenga en cuenta que kfence no lo detecta cada vez): $ echo 1 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs $ echo 0 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs BUG: KFENCE: use-after-free read in efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc] Use-after-free read at 0x00000000ff3c1ba5 (in kfence-#224): efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc] efx_ef10_pci_sriov_disable+0x38/0x70 [sfc] efx_pci_sriov_configure+0x24/0x40 [sfc] sriov_numvfs_store+0xfe/0x140 kernfs_fop_write_iter+0x11c/0x1b0 new_sync_write+0x11f/0x1b0 vfs_write+0x1eb/0x280 ksys_write+0x5f/0xe0 do_syscall_64+0x5c/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae kfence-#224: 0x00000000edb8ef95-0x00000000671f5ce1, size=2792, cache=kmalloc-4k allocated by task 6771 on cpu 10 at 3137.860196s: pci_alloc_dev+0x21/0x60 pci_iov_add_virtfn+0x2a2/0x320 sriov_enable+0x212/0x3e0 efx_ef10_sriov_configure+0x67/0x80 [sfc] efx_pci_sriov_configure+0x24/0x40 [sfc] sriov_numvfs_store+0xba/0x140 kernfs_fop_write_iter+0x11c/0x1b0 new_sync_write+0x11f/0x1b0 vfs_write+0x1eb/0x280 ksys_write+0x5f/0xe0 do_syscall_64+0x5c/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae freed by task 6771 on cpu 12 at 3170.991309s: device_release+0x34/0x90 kobject_cleanup+0x3a/0x130 pci_iov_remove_virtfn+0xd9/0x120 sriov_disable+0x30/0xe0 efx_ef10_pci_sriov_disable+0x57/0x70 [sfc] efx_pci_sriov_configure+0x24/0x40 [sfc] sriov_numvfs_store+0xfe/0x140 kernfs_fop_write_iter+0x11c/0x1b0 new_sync_write+0x11f/0x1b0 vfs_write+0x1eb/0x280 ksys_write+0x5f/0xe0 do_syscall_64+0x5c/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae "
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/3199e34912d84cdfb8a93a984c5ae5c73fb13e84",
diff --git a/CVE-2022/CVE-2022-496xx/CVE-2022-49647.json b/CVE-2022/CVE-2022-496xx/CVE-2022-49647.json
index dcedef8ef33..4a372861635 100644
--- a/CVE-2022/CVE-2022-496xx/CVE-2022-49647.json
+++ b/CVE-2022/CVE-2022-496xx/CVE-2022-49647.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49647",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:39.863",
- "lastModified": "2025-02-26T07:01:39.863",
+ "lastModified": "2025-02-27T19:15:45.990",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup: Use separate src/dst nodes when preloading css_sets for migration\n\nEach cset (css_set) is pinned by its tasks. When we're moving tasks around\nacross csets for a migration, we need to hold the source and destination\ncsets to ensure that they don't go away while we're moving tasks about. This\nis done by linking cset->mg_preload_node on either the\nmgctx->preloaded_src_csets or mgctx->preloaded_dst_csets list. Using the\nsame cset->mg_preload_node for both the src and dst lists was deemed okay as\na cset can't be both the source and destination at the same time.\n\nUnfortunately, this overloading becomes problematic when multiple tasks are\ninvolved in a migration and some of them are identity noop migrations while\nothers are actually moving across cgroups. For example, this can happen with\nthe following sequence on cgroup1:\n\n #1> mkdir -p /sys/fs/cgroup/misc/a/b\n #2> echo $$ > /sys/fs/cgroup/misc/a/cgroup.procs\n #3> RUN_A_COMMAND_WHICH_CREATES_MULTIPLE_THREADS &\n #4> PID=$!\n #5> echo $PID > /sys/fs/cgroup/misc/a/b/tasks\n #6> echo $PID > /sys/fs/cgroup/misc/a/cgroup.procs\n\nthe process including the group leader back into a. In this final migration,\nnon-leader threads would be doing identity migration while the group leader\nis doing an actual one.\n\nAfter #3, let's say the whole process was in cset A, and that after #4, the\nleader moves to cset B. Then, during #6, the following happens:\n\n 1. cgroup_migrate_add_src() is called on B for the leader.\n\n 2. cgroup_migrate_add_src() is called on A for the other threads.\n\n 3. cgroup_migrate_prepare_dst() is called. It scans the src list.\n\n 4. It notices that B wants to migrate to A, so it tries to A to the dst\n list but realizes that its ->mg_preload_node is already busy.\n\n 5. and then it notices A wants to migrate to A as it's an identity\n migration, it culls it by list_del_init()'ing its ->mg_preload_node and\n putting references accordingly.\n\n 6. The rest of migration takes place with B on the src list but nothing on\n the dst list.\n\nThis means that A isn't held while migration is in progress. If all tasks\nleave A before the migration finishes and the incoming task pins it, the\ncset will be destroyed leading to use-after-free.\n\nThis is caused by overloading cset->mg_preload_node for both src and dst\npreload lists. We wanted to exclude the cset from the src list but ended up\ninadvertently excluding it from the dst list too.\n\nThis patch fixes the issue by separating out cset->mg_preload_node into\n->mg_src_preload_node and ->mg_dst_preload_node, so that the src and dst\npreloadings don't interfere with each other."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: cgroup: usar nodos src/dst separados al precargar css_sets para la migraci\u00f3n Cada cset (css_set) est\u00e1 fijado por sus tareas. Cuando estamos moviendo tareas entre csets para una migraci\u00f3n, necesitamos mantener los csets de origen y destino para asegurarnos de que no desaparezcan mientras movemos tareas. Esto se hace vinculando cset->mg_preload_node en la lista mgctx->preloaded_src_csets o mgctx->preloaded_dst_csets. Se consider\u00f3 correcto usar el mismo cset->mg_preload_node para las listas src y dst, ya que un cset no puede ser el origen y el destino al mismo tiempo. Desafortunadamente, esta sobrecarga se vuelve problem\u00e1tica cuando hay varias tareas involucradas en una migraci\u00f3n y algunas de ellas son migraciones de noop de identidad mientras que otras en realidad se est\u00e1n moviendo entre cgroup1: #1> mkdir -p /sys/fs/cgroup/misc/a/b #2> echo $$ > /sys/fs/cgroup/misc/a/cgroup.procs #3> RUN_A_COMMAND_WHICH_CREATES_MULTIPLE_THREADS & #4> PID=$! #5> echo $PID > /sys/fs/cgroup/misc/a/b/tasks #6> echo $PID > /sys/fs/cgroup/misc/a/cgroup.procs el proceso que incluye al l\u00edder del grupo de nuevo en a. En esta migraci\u00f3n final, los subprocesos que no son l\u00edderes estar\u00edan realizando la migraci\u00f3n de identidad mientras que el l\u00edder del grupo est\u00e1 realizando una real. Despu\u00e9s del n.\u00b0 3, digamos que todo el proceso estaba en cset A, y que despu\u00e9s del n.\u00b0 4, el l\u00edder se mueve al cset B. Luego, durante el n.\u00b0 6, sucede lo siguiente: 1. se llama a cgroup_migrate_add_src() en B para el l\u00edder. 2. se llama a cgroup_migrate_add_src() en A para los otros subprocesos. 3. se llama a cgroup_migrate_prepare_dst(). Escanea la lista src. 4. Se da cuenta de que B quiere migrar a A, por lo que intenta llevar A a la lista dst pero se da cuenta de que su ->mg_preload_node ya est\u00e1 ocupado. 5. y luego se da cuenta de que A quiere migrar a A como es una migraci\u00f3n de identidad, lo descarta haciendo list_del_init()'ing su ->mg_preload_node y poniendo referencias en consecuencia. 6. El resto de la migraci\u00f3n se lleva a cabo con B en la lista src pero nada en la lista dst. Esto significa que A no se mantiene mientras la migraci\u00f3n est\u00e1 en progreso. Si todas las tareas abandonan A antes de que finalice la migraci\u00f3n y la tarea entrante lo fija, el cset se destruir\u00e1, lo que provocar\u00e1 un use-after-free. Esto se debe a la sobrecarga de cset->mg_preload_node para las listas de precarga de src y dst. Quer\u00edamos excluir el cset de la lista de src, pero terminamos excluy\u00e9ndolo inadvertidamente tambi\u00e9n de la lista de dst. Este parche soluciona el problema al separar cset->mg_preload_node en ->mg_src_preload_node y ->mg_dst_preload_node, de modo que las precargas de src y dst no interfieran entre s\u00ed."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/05f7658210d1d331e8dd4cb6e7bbbe3df5f5ac27",
diff --git a/CVE-2022/CVE-2022-496xx/CVE-2022-49651.json b/CVE-2022/CVE-2022-496xx/CVE-2022-49651.json
index 3552ce33d31..660ac650ad3 100644
--- a/CVE-2022/CVE-2022-496xx/CVE-2022-49651.json
+++ b/CVE-2022/CVE-2022-496xx/CVE-2022-49651.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49651",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:40.237",
- "lastModified": "2025-02-26T07:01:40.237",
+ "lastModified": "2025-02-27T19:15:46.143",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsrcu: Tighten cleanup_srcu_struct() GP checks\n\nCurrently, cleanup_srcu_struct() checks for a grace period in progress,\nbut it does not check for a grace period that has not yet started but\nwhich might start at any time. Such a situation could result in a\nuse-after-free bug, so this commit adds a check for a grace period that\nis needed but not yet started to cleanup_srcu_struct()."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: srcu: Reforzar las comprobaciones de GP de cleanup_srcu_struct() Actualmente, cleanup_srcu_struct() comprueba si hay un per\u00edodo de gracia en curso, pero no comprueba si hay un per\u00edodo de gracia que a\u00fan no ha comenzado pero que podr\u00eda comenzar en cualquier momento. Una situaci\u00f3n de este tipo podr\u00eda dar lugar a un error de use-after-free, por lo que esta confirmaci\u00f3n a\u00f1ade una comprobaci\u00f3n de un per\u00edodo de gracia que es necesario pero que a\u00fan no ha comenzado a cleanup_srcu_struct()."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/8ed00760203d8018bee042fbfe8e076579be2c2b",
diff --git a/CVE-2022/CVE-2022-496xx/CVE-2022-49667.json b/CVE-2022/CVE-2022-496xx/CVE-2022-49667.json
index b0a5ec236e4..05aca186429 100644
--- a/CVE-2022/CVE-2022-496xx/CVE-2022-49667.json
+++ b/CVE-2022/CVE-2022-496xx/CVE-2022-49667.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49667",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:41.687",
- "lastModified": "2025-02-26T07:01:41.687",
+ "lastModified": "2025-02-27T19:15:46.277",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: bonding: fix use-after-free after 802.3ad slave unbind\n\ncommit 0622cab0341c (\"bonding: fix 802.3ad aggregator reselection\"),\nresolve case, when there is several aggregation groups in the same bond.\nbond_3ad_unbind_slave will invalidate (clear) aggregator when\n__agg_active_ports return zero. So, ad_clear_agg can be executed even, when\nnum_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for,\npreviously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave\nwill not update slave ports list, because lag_ports==NULL. So, here we\ngot slave ports, pointing to freed aggregator memory.\n\nFix with checking actual number of ports in group (as was before\ncommit 0622cab0341c (\"bonding: fix 802.3ad aggregator reselection\") ),\nbefore ad_clear_agg().\n\nThe KASAN logs are as follows:\n\n[ 767.617392] ==================================================================\n[ 767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470\n[ 767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767\n[ 767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G O 5.15.11 #15\n[ 767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT)\n[ 767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler\n[ 767.666468] Call trace:\n[ 767.668930] dump_backtrace+0x0/0x2d0\n[ 767.672625] show_stack+0x24/0x30\n[ 767.675965] dump_stack_lvl+0x68/0x84\n[ 767.679659] print_address_description.constprop.0+0x74/0x2b8\n[ 767.685451] kasan_report+0x1f0/0x260\n[ 767.689148] __asan_load2+0x94/0xd0\n[ 767.692667] bond_3ad_state_machine_handler+0x13dc/0x1470"
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: bonding: fix use-after-free after 802.3ad slave unbind commit 0622cab0341c (\"bonding: fix 802.3ad gregator reselection\"), resuelve el caso, cuando hay varios grupos de agregaci\u00f3n en el mismo enlace. bond_3ad_unbind_slave invalidar\u00e1 (borrar\u00e1) el agregador cuando __agg_active_ports devuelva cero. Por lo tanto, ad_clear_agg se puede ejecutar incluso, cuando num_of_ports!=0. Luego, bond_3ad_unbind_slave se puede ejecutar nuevamente para el agregador previamente borrado. NOTA: en este momento bond_3ad_unbind_slave no actualizar\u00e1 la lista de puertos esclavos, porque lag_ports==NULL. Entonces, aqu\u00ed tenemos puertos esclavos, apuntando a la memoria liberada del agregador. Correcci\u00f3n con la verificaci\u00f3n del n\u00famero real de puertos en el grupo (como era antes de el commit 0622cab0341c (\"vinculaci\u00f3n: correcci\u00f3n de la reselecci\u00f3n del agregador 802.3ad\")), antes de ad_clear_agg(). Los registros de KASAN son los siguientes: [ 767.617392] ================================================================== [ 767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470 [ 767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767 [ 767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G O 5.15.11 #15 [ 767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT) [ 767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler [ 767.666468] Call trace: [ 767.668930] dump_backtrace+0x0/0x2d0 [ 767.672625] show_stack+0x24/0x30 [ 767.675965] dump_stack_lvl+0x68/0x84 [ 767.679659] print_address_description.constprop.0+0x74/0x2b8 [ 767.685451] kasan_report+0x1f0/0x260 [ 767.689148] __asan_load2+0x94/0xd0 [ 767.692667] bond_3ad_state_machine_handler+0x13dc/0x1470 "
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/050133e1aa2cb49bb17be847d48a4431598ef562",
diff --git a/CVE-2022/CVE-2022-496xx/CVE-2022-49685.json b/CVE-2022/CVE-2022-496xx/CVE-2022-49685.json
index 2432eac630c..f22b015ab83 100644
--- a/CVE-2022/CVE-2022-496xx/CVE-2022-49685.json
+++ b/CVE-2022/CVE-2022-496xx/CVE-2022-49685.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49685",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:43.340",
- "lastModified": "2025-02-26T07:01:43.340",
+ "lastModified": "2025-02-27T19:15:46.427",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\niio: trigger: sysfs: fix use-after-free on remove\n\nEnsure that the irq_work has completed before the trigger is freed.\n\n ==================================================================\n BUG: KASAN: use-after-free in irq_work_run_list\n Read of size 8 at addr 0000000064702248 by task python3/25\n\n Call Trace:\n irq_work_run_list\n irq_work_tick\n update_process_times\n tick_sched_handle\n tick_sched_timer\n __hrtimer_run_queues\n hrtimer_interrupt\n\n Allocated by task 25:\n kmem_cache_alloc_trace\n iio_sysfs_trig_add\n dev_attr_store\n sysfs_kf_write\n kernfs_fop_write_iter\n new_sync_write\n vfs_write\n ksys_write\n sys_write\n\n Freed by task 25:\n kfree\n iio_sysfs_trig_remove\n dev_attr_store\n sysfs_kf_write\n kernfs_fop_write_iter\n new_sync_write\n vfs_write\n ksys_write\n sys_write\n\n =================================================================="
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: iio: trigger: sysfs: fix use-after-free on remove Aseg\u00farese de que irq_work se haya completado antes de que se libere el disparador.================================================================== BUG: KASAN: use-after-free in irq_work_run_list Read of size 8 at addr 0000000064702248 by task python3/25 Call Trace: irq_work_run_list irq_work_tick update_process_times tick_sched_handle tick_sched_timer __hrtimer_run_queues hrtimer_interrupt Allocated by task 25: kmem_cache_alloc_trace iio_sysfs_trig_add dev_attr_store sysfs_kf_write kernfs_fop_write_iter new_sync_write vfs_write ksys_write sys_write Freed by task 25: kfree iio_sysfs_trig_remove dev_attr_store sysfs_kf_write kernfs_fop_write_iter new_sync_write vfs_write ksys_write sys_write ================================================================== "
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/31ff3309b47d98313c61b8301bf595820cc3cc33",
diff --git a/CVE-2022/CVE-2022-496xx/CVE-2022-49695.json b/CVE-2022/CVE-2022-496xx/CVE-2022-49695.json
index 9a6124f9d9f..c750a0db777 100644
--- a/CVE-2022/CVE-2022-496xx/CVE-2022-49695.json
+++ b/CVE-2022/CVE-2022-496xx/CVE-2022-49695.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49695",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:44.260",
- "lastModified": "2025-02-26T07:01:44.260",
+ "lastModified": "2025-02-27T19:15:46.573",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nigb: fix a use-after-free issue in igb_clean_tx_ring\n\nFix the following use-after-free bug in igb_clean_tx_ring routine when\nthe NIC is running in XDP mode. The issue can be triggered redirecting\ntraffic into the igb NIC and then closing the device while the traffic\nis flowing.\n\n[ 73.322719] CPU: 1 PID: 487 Comm: xdp_redirect Not tainted 5.18.3-apu2 #9\n[ 73.330639] Hardware name: PC Engines APU2/APU2, BIOS 4.0.7 02/28/2017\n[ 73.337434] RIP: 0010:refcount_warn_saturate+0xa7/0xf0\n[ 73.362283] RSP: 0018:ffffc9000081f798 EFLAGS: 00010282\n[ 73.367761] RAX: 0000000000000000 RBX: ffffc90000420f80 RCX: 0000000000000000\n[ 73.375200] RDX: ffff88811ad22d00 RSI: ffff88811ad171e0 RDI: ffff88811ad171e0\n[ 73.382590] RBP: 0000000000000900 R08: ffffffff82298f28 R09: 0000000000000058\n[ 73.390008] R10: 0000000000000219 R11: ffffffff82280f40 R12: 0000000000000090\n[ 73.397356] R13: ffff888102343a40 R14: ffff88810359e0e4 R15: 0000000000000000\n[ 73.404806] FS: 00007ff38d31d740(0000) GS:ffff88811ad00000(0000) knlGS:0000000000000000\n[ 73.413129] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 73.419096] CR2: 000055cff35f13f8 CR3: 0000000106391000 CR4: 00000000000406e0\n[ 73.426565] Call Trace:\n[ 73.429087] \n[ 73.431314] igb_clean_tx_ring+0x43/0x140 [igb]\n[ 73.436002] igb_down+0x1d7/0x220 [igb]\n[ 73.439974] __igb_close+0x3c/0x120 [igb]\n[ 73.444118] igb_xdp+0x10c/0x150 [igb]\n[ 73.447983] ? igb_pci_sriov_configure+0x70/0x70 [igb]\n[ 73.453362] dev_xdp_install+0xda/0x110\n[ 73.457371] dev_xdp_attach+0x1da/0x550\n[ 73.461369] do_setlink+0xfd0/0x10f0\n[ 73.465166] ? __nla_validate_parse+0x89/0xc70\n[ 73.469714] rtnl_setlink+0x11a/0x1e0\n[ 73.473547] rtnetlink_rcv_msg+0x145/0x3d0\n[ 73.477709] ? rtnl_calcit.isra.0+0x130/0x130\n[ 73.482258] netlink_rcv_skb+0x8d/0x110\n[ 73.486229] netlink_unicast+0x230/0x340\n[ 73.490317] netlink_sendmsg+0x215/0x470\n[ 73.494395] __sys_sendto+0x179/0x190\n[ 73.498268] ? move_addr_to_user+0x37/0x70\n[ 73.502547] ? __sys_getsockname+0x84/0xe0\n[ 73.506853] ? netlink_setsockopt+0x1c1/0x4a0\n[ 73.511349] ? __sys_setsockopt+0xc8/0x1d0\n[ 73.515636] __x64_sys_sendto+0x20/0x30\n[ 73.519603] do_syscall_64+0x3b/0x80\n[ 73.523399] entry_SYSCALL_64_after_hwframe+0x44/0xae\n[ 73.528712] RIP: 0033:0x7ff38d41f20c\n[ 73.551866] RSP: 002b:00007fff3b945a68 EFLAGS: 00000246 ORIG_RAX: 000000000000002c\n[ 73.559640] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff38d41f20c\n[ 73.567066] RDX: 0000000000000034 RSI: 00007fff3b945b30 RDI: 0000000000000003\n[ 73.574457] RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000\n[ 73.581852] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff3b945ab0\n[ 73.589179] R13: 0000000000000000 R14: 0000000000000003 R15: 00007fff3b945b30\n[ 73.596545] \n[ 73.598842] ---[ end trace 0000000000000000 ]---"
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: igb: se soluciona un problema de use-after-free en igb_clean_tx_ring Se soluciona el siguiente error de use-after-free en la rutina igb_clean_tx_ring cuando la NIC se ejecuta en modo XDP. El problema se puede desencadenar al redirigir el tr\u00e1fico a la NIC igb y luego cerrar el dispositivo mientras fluye el tr\u00e1fico. [ 73.322719] CPU: 1 PID: 487 Comm: xdp_redirect Not tainted 5.18.3-apu2 #9 [ 73.330639] Hardware name: PC Engines APU2/APU2, BIOS 4.0.7 02/28/2017 [ 73.337434] RIP: 0010:refcount_warn_saturate+0xa7/0xf0 [ 73.362283] RSP: 0018:ffffc9000081f798 EFLAGS: 00010282 [ 73.367761] RAX: 0000000000000000 RBX: ffffc90000420f80 RCX: 0000000000000000 [ 73.375200] RDX: ffff88811ad22d00 RSI: ffff88811ad171e0 RDI: ffff88811ad171e0 [ 73.382590] RBP: 0000000000000900 R08: ffffffff82298f28 R09: 0000000000000058 [ 73.390008] R10: 0000000000000219 R11: ffffffff82280f40 R12: 0000000000000090 [ 73.397356] R13: ffff888102343a40 R14: ffff88810359e0e4 R15: 0000000000000000 [ 73.404806] FS: 00007ff38d31d740(0000) GS:ffff88811ad00000(0000) knlGS:0000000000000000 [ 73.413129] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 73.419096] CR2: 000055cff35f13f8 CR3: 0000000106391000 CR4: 00000000000406e0 [ 73.426565] Call Trace: [ 73.429087] [ 73.431314] igb_clean_tx_ring+0x43/0x140 [igb] [ 73.436002] igb_down+0x1d7/0x220 [igb] [ 73.439974] __igb_close+0x3c/0x120 [igb] [ 73.444118] igb_xdp+0x10c/0x150 [igb] [ 73.447983] ? igb_pci_sriov_configure+0x70/0x70 [igb] [ 73.453362] dev_xdp_install+0xda/0x110 [ 73.457371] dev_xdp_attach+0x1da/0x550 [ 73.461369] do_setlink+0xfd0/0x10f0 [ 73.465166] ? __nla_validate_parse+0x89/0xc70 [ 73.469714] rtnl_setlink+0x11a/0x1e0 [ 73.473547] rtnetlink_rcv_msg+0x145/0x3d0 [ 73.477709] ? rtnl_calcit.isra.0+0x130/0x130 [ 73.482258] netlink_rcv_skb+0x8d/0x110 [ 73.486229] netlink_unicast+0x230/0x340 [ 73.490317] netlink_sendmsg+0x215/0x470 [ 73.494395] __sys_sendto+0x179/0x190 [ 73.498268] ? move_addr_to_user+0x37/0x70 [ 73.502547] ? __sys_getsockname+0x84/0xe0 [ 73.506853] ? netlink_setsockopt+0x1c1/0x4a0 [ 73.511349] ? __sys_setsockopt+0xc8/0x1d0 [ 73.515636] __x64_sys_sendto+0x20/0x30 [ 73.519603] do_syscall_64+0x3b/0x80 [ 73.523399] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 73.528712] RIP: 0033:0x7ff38d41f20c [ 73.551866] RSP: 002b:00007fff3b945a68 EFLAGS: 00000246 ORIG_RAX: 000000000000002c [ 73.559640] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff38d41f20c [ 73.567066] RDX: 0000000000000034 RSI: 00007fff3b945b30 RDI: 0000000000000003 [ 73.574457] RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000 [ 73.581852] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff3b945ab0 [ 73.589179] R13: 0000000000000000 R14: 0000000000000003 R15: 00007fff3b945b30 [ 73.596545] [ 73.598842] ---[ end trace 0000000000000000 ]--- "
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2af944210dc23d43d8208dafac4df7be7e3c168b",
diff --git a/CVE-2022/CVE-2022-496xx/CVE-2022-49696.json b/CVE-2022/CVE-2022-496xx/CVE-2022-49696.json
index e4a05b01d1e..a068aa4ea70 100644
--- a/CVE-2022/CVE-2022-496xx/CVE-2022-49696.json
+++ b/CVE-2022/CVE-2022-496xx/CVE-2022-49696.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49696",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:44.357",
- "lastModified": "2025-02-26T07:01:44.357",
+ "lastModified": "2025-02-27T19:15:46.720",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntipc: fix use-after-free Read in tipc_named_reinit\n\nsyzbot found the following issue on:\n==================================================================\nBUG: KASAN: use-after-free in tipc_named_reinit+0x94f/0x9b0\nnet/tipc/name_distr.c:413\nRead of size 8 at addr ffff88805299a000 by task kworker/1:9/23764\n\nCPU: 1 PID: 23764 Comm: kworker/1:9 Not tainted\n5.18.0-rc4-syzkaller-00878-g17d49e6e8012 #0\nHardware name: Google Compute Engine/Google Compute Engine,\nBIOS Google 01/01/2011\nWorkqueue: events tipc_net_finalize_work\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/0x495\nmm/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 tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413\n tipc_net_finalize+0x234/0x3d0 net/tipc/net.c:138\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:298\n \n[...]\n==================================================================\n\nIn the commit\nd966ddcc3821 (\"tipc: fix a deadlock when flushing scheduled work\"),\nthe cancel_work_sync() function just to make sure ONLY the work\ntipc_net_finalize_work() is executing/pending on any CPU completed before\ntipc namespace is destroyed through tipc_exit_net(). But this function\nis not guaranteed the work is the last queued. So, the destroyed instance\nmay be accessed in the work which will try to enqueue later.\n\nIn order to completely fix, we re-order the calling of cancel_work_sync()\nto make sure the work tipc_net_finalize_work() was last queued and it\nmust be completed by calling cancel_work_sync()."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tipc: correcci\u00f3n de lectura use-after-free en tipc_named_reinit syzbot encontr\u00f3 el siguiente problema en: ================================================================== BUG: KASAN: use-after-free in tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 Read of size 8 at addr ffff88805299a000 by task kworker/1:9/23764 CPU: 1 PID: 23764 Comm: kworker/1:9 Not tainted 5.18.0-rc4-syzkaller-00878-g17d49e6e8012 #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events tipc_net_finalize_work Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0xeb/0x495 mm/kasan/report.c:313 print_report mm/kasan/report.c:429 [inline] kasan_report.cold+0xf4/0x1c6 mm/kasan/report.c:491 tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 tipc_net_finalize+0x234/0x3d0 net/tipc/net.c:138 process_one_work+0x996/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 [...] ================================================================== En el commit d966ddcc3821 (\"tipc: corregir un bloqueo al vaciar el trabajo programado\"), la funci\u00f3n cancel_work_sync() solo se asegura de que SOLO el trabajo tipc_net_finalize_work() se est\u00e9 ejecutando/pendiente en cualquier CPU que se haya completado antes de que el espacio de nombres tipc se destruya mediante tipc_exit_net(). Pero esta funci\u00f3n no garantiza que el trabajo sea el \u00faltimo en cola. Por lo tanto, se puede acceder a la instancia destruida en el trabajo que intentar\u00e1 ponerse en cola m\u00e1s tarde. Para solucionarlo por completo, reordenamos la llamada de cancel_work_sync() para asegurarnos de que el trabajo tipc_net_finalize_work() se haya puesto en cola por \u00faltima vez y se deba completar llamando a cancel_work_sync()."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/361c5521c1e49843b710f455cae3c0a50b714323",
diff --git a/CVE-2022/CVE-2022-497xx/CVE-2022-49700.json b/CVE-2022/CVE-2022-497xx/CVE-2022-49700.json
index 9fec8828441..00cf6eac03e 100644
--- a/CVE-2022/CVE-2022-497xx/CVE-2022-49700.json
+++ b/CVE-2022/CVE-2022-497xx/CVE-2022-49700.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49700",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:44.740",
- "lastModified": "2025-02-26T07:01:44.740",
+ "lastModified": "2025-02-27T19:15:46.863",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: add missing TID updates on slab deactivation\n\nThe fastpath in slab_alloc_node() assumes that c->slab is stable as long as\nthe TID stays the same. However, two places in __slab_alloc() currently\ndon't update the TID when deactivating the CPU slab.\n\nIf multiple operations race the right way, this could lead to an object\ngetting lost; or, in an even more unlikely situation, it could even lead to\nan object being freed onto the wrong slab's freelist, messing up the\n`inuse` counter and eventually causing a page to be freed to the page\nallocator while it still contains slab objects.\n\n(I haven't actually tested these cases though, this is just based on\nlooking at the code. Writing testcases for this stuff seems like it'd be\na pain...)\n\nThe race leading to state inconsistency is (all operations on the same CPU\nand kmem_cache):\n\n - task A: begin do_slab_free():\n - read TID\n - read pcpu freelist (==NULL)\n - check `slab == c->slab` (true)\n - [PREEMPT A->B]\n - task B: begin slab_alloc_node():\n - fastpath fails (`c->freelist` is NULL)\n - enter __slab_alloc()\n - slub_get_cpu_ptr() (disables preemption)\n - enter ___slab_alloc()\n - take local_lock_irqsave()\n - read c->freelist as NULL\n - get_freelist() returns NULL\n - write `c->slab = NULL`\n - drop local_unlock_irqrestore()\n - goto new_slab\n - slub_percpu_partial() is NULL\n - get_partial() returns NULL\n - slub_put_cpu_ptr() (enables preemption)\n - [PREEMPT B->A]\n - task A: finish do_slab_free():\n - this_cpu_cmpxchg_double() succeeds()\n - [CORRUPT STATE: c->slab==NULL, c->freelist!=NULL]\n\nFrom there, the object on c->freelist will get lost if task B is allowed to\ncontinue from here: It will proceed to the retry_load_slab label,\nset c->slab, then jump to load_freelist, which clobbers c->freelist.\n\nBut if we instead continue as follows, we get worse corruption:\n\n - task A: run __slab_free() on object from other struct slab:\n - CPU_PARTIAL_FREE case (slab was on no list, is now on pcpu partial)\n - task A: run slab_alloc_node() with NUMA node constraint:\n - fastpath fails (c->slab is NULL)\n - call __slab_alloc()\n - slub_get_cpu_ptr() (disables preemption)\n - enter ___slab_alloc()\n - c->slab is NULL: goto new_slab\n - slub_percpu_partial() is non-NULL\n - set c->slab to slub_percpu_partial(c)\n - [CORRUPT STATE: c->slab points to slab-1, c->freelist has objects\n from slab-2]\n - goto redo\n - node_match() fails\n - goto deactivate_slab\n - existing c->freelist is passed into deactivate_slab()\n - inuse count of slab-1 is decremented to account for object from\n slab-2\n\nAt this point, the inuse count of slab-1 is 1 lower than it should be.\nThis means that if we free all allocated objects in slab-1 except for one,\nSLUB will think that slab-1 is completely unused, and may free its page,\nleading to use-after-free."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mm/slub: a\u00f1adir actualizaciones de TID faltantes en la desactivaci\u00f3n de slab La ruta r\u00e1pida en slab_alloc_node() asume que c->slab es estable siempre que el TID permanezca igual. Sin embargo, dos lugares en __slab_alloc() actualmente no actualizan el TID al desactivar el slab de la CPU. Si varias operaciones se ejecutan en la direcci\u00f3n correcta, esto podr\u00eda provocar que se pierda un objeto; o, en una situaci\u00f3n a\u00fan m\u00e1s improbable, incluso podr\u00eda provocar que se libere un objeto en la lista libre del slab incorrecto, lo que arruina el contador `inuse` y eventualmente provoca que se libere una p\u00e1gina al asignador de p\u00e1ginas mientras a\u00fan contiene objetos slab. (En realidad no he probado estos casos, esto se basa simplemente en mirar el c\u00f3digo. Escribir casos de prueba para estas cosas parece que ser\u00eda una molestia...) La ejecuci\u00f3n que lleva a la inconsistencia de estado es (todas las operaciones en la misma CPU y kmem_cache): - task A: begin do_slab_free(): - read TID - read pcpu freelist (==NULL) - check `slab == c->slab` (true) - [PREEMPT A->B] - task B: begin slab_alloc_node(): - fastpath fails (`c->freelist` is NULL) - enter __slab_alloc() - slub_get_cpu_ptr() (disables preemption) - enter ___slab_alloc() - take local_lock_irqsave() - read c->freelist as NULL - get_freelist() returns NULL - write `c->slab = NULL` - drop local_unlock_irqrestore() - goto new_slab - slub_percpu_partial() is NULL - get_partial() returns NULL - slub_put_cpu_ptr() (enables preemption) - [PREEMPT B->A] - task A: finish do_slab_free(): - this_cpu_cmpxchg_double() succeeds() - [CORRUPT STATE: c->slab==NULL, c->freelist!=NULL] From there, the object on c->freelist will get lost if task B is allowed to continue from here: It will proceed to the retry_load_slab label, set c->slab, then jump to load_freelist, which clobbers c->freelist. But if we instead continue as follows, we get worse corruption: - task A: run __slab_free() on object from other struct slab: - CPU_PARTIAL_FREE case (slab was on no list, is now on pcpu partial) - task A: run slab_alloc_node() with NUMA node constraint: - fastpath fails (c->slab is NULL) - call __slab_alloc() - slub_get_cpu_ptr() (disables preemption) - enter ___slab_alloc() - c->slab is NULL: goto new_slab - slub_percpu_partial() is non-NULL - set c->slab to slub_percpu_partial(c) - [CORRUPT STATE: c->slab points to slab-1, c->freelist has objects from slab-2] - goto redo - node_match() fails - goto deactivate_slab - existing c->freelist is passed into deactivate_slab() - inuse count of slab-1 se decrementa para tener en cuenta el objeto de slab-2 En este punto, el conteo de objetos en uso de slab-1 es 1 menos de lo que deber\u00eda ser. Esto significa que si liberamos todos los objetos asignados en slab-1 excepto uno, SLUB pensar\u00e1 que slab-1 est\u00e1 completamente sin usar y puede liberar su p\u00e1gina, lo que lleva a un use-after-free."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/0515cc9b6b24877f59b222ade704bfaa42caa2a6",
diff --git a/CVE-2022/CVE-2022-497xx/CVE-2022-49711.json b/CVE-2022/CVE-2022-497xx/CVE-2022-49711.json
index 160a9d24374..001295d79b5 100644
--- a/CVE-2022/CVE-2022-497xx/CVE-2022-49711.json
+++ b/CVE-2022/CVE-2022-497xx/CVE-2022-49711.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49711",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:46.893",
- "lastModified": "2025-02-26T07:01:46.893",
+ "lastModified": "2025-02-27T19:15:47.010",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbus: fsl-mc-bus: fix KASAN use-after-free in fsl_mc_bus_remove()\n\nIn fsl_mc_bus_remove(), mc->root_mc_bus_dev->mc_io is passed to\nfsl_destroy_mc_io(). However, mc->root_mc_bus_dev is already freed in\nfsl_mc_device_remove(). Then reference to mc->root_mc_bus_dev->mc_io\ntriggers KASAN use-after-free. To avoid the use-after-free, keep the\nreference to mc->root_mc_bus_dev->mc_io in a local variable and pass to\nfsl_destroy_mc_io().\n\nThis patch needs rework to apply to kernels older than v5.15."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bus: fsl-mc-bus: arregla el use-after-free de KASAN en fsl_mc_bus_remove() En fsl_mc_bus_remove(), mc->root_mc_bus_dev->mc_io se pasa a fsl_destroy_mc_io(). Sin embargo, mc->root_mc_bus_dev ya est\u00e1 liberado en fsl_mc_device_remove(). Entonces, la referencia a mc->root_mc_bus_dev->mc_io activa el use-after-free de KASAN. Para evitar el use-after-free, mant\u00e9n la referencia a mc->root_mc_bus_dev->mc_io en una variable local y p\u00e1sala a fsl_destroy_mc_io(). Este parche necesita ser redise\u00f1ado para que se aplique a kernels anteriores a la v5.15."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/161b68b0a728377aaa10a8e14c70e7734f3c9ff7",
diff --git a/CVE-2022/CVE-2022-497xx/CVE-2022-49730.json b/CVE-2022/CVE-2022-497xx/CVE-2022-49730.json
index 6de283402f7..c6c429d915b 100644
--- a/CVE-2022/CVE-2022-497xx/CVE-2022-49730.json
+++ b/CVE-2022/CVE-2022-497xx/CVE-2022-49730.json
@@ -2,16 +2,55 @@
"id": "CVE-2022-49730",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-26T07:01:48.620",
- "lastModified": "2025-02-26T07:01:48.620",
+ "lastModified": "2025-02-27T19:15:47.153",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted\n\nA use-after-free crash can occur after an ELS LOGO is aborted.\n\nSpecifically, a nodelist structure is freed and then\nndlp->vport->cfg_log_verbose is dereferenced in lpfc_nlp_get() when the\ndiscovery state machine is mistakenly called a second time with\nNLP_EVT_DEVICE_RM argument.\n\nRework lpfc_cmpl_els_logo() to prevent the duplicate calls to release a\nnodelist structure."
+ },
+ {
+ "lang": "es",
+ "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: scsi: lpfc: Resolver la desreferencia de ptr NULL despu\u00e9s de que se cancele un LOGOTIPO ELS Se puede producir un fallo de use-after-free despu\u00e9s de que se cancele un LOGOTIPO ELS. Espec\u00edficamente, se libera una estructura de lista de nodos y luego se desreferencia ndlp->vport->cfg_log_verbose en lpfc_nlp_get() cuando se llama por error a la m\u00e1quina de estado de descubrimiento una segunda vez con el argumento NLP_EVT_DEVICE_RM. Reelabore lpfc_cmpl_els_logo() para evitar las llamadas duplicadas para liberar una estructura de lista de nodos."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
}
],
- "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/5e83869e29448958f8ae2c6911f350318f75e4fc",
diff --git a/CVE-2023/CVE-2023-233xx/CVE-2023-23326.json b/CVE-2023/CVE-2023-233xx/CVE-2023-23326.json
index 330a70bb58f..377d627b446 100644
--- a/CVE-2023/CVE-2023-233xx/CVE-2023-23326.json
+++ b/CVE-2023/CVE-2023-233xx/CVE-2023-23326.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-23326",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-10T22:15:10.277",
- "lastModified": "2024-11-21T07:45:59.787",
+ "lastModified": "2025-02-27T19:15:47.783",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 2.3,
"impactScore": 2.7
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
+ "baseScore": 5.4,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "REQUIRED",
+ "scope": "CHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.3,
+ "impactScore": 2.7
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-79"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-79"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2023/CVE-2023-252xx/CVE-2023-25283.json b/CVE-2023/CVE-2023-252xx/CVE-2023-25283.json
index 8a36034f6a7..fccb4fa3a2f 100644
--- a/CVE-2023/CVE-2023-252xx/CVE-2023-25283.json
+++ b/CVE-2023/CVE-2023-252xx/CVE-2023-25283.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-25283",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-13T12:15:11.247",
- "lastModified": "2024-11-21T07:49:23.347",
+ "lastModified": "2025-02-27T20:15:36.397",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 3.9,
"impactScore": 3.6
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-787"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-787"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2023/CVE-2023-253xx/CVE-2023-25345.json b/CVE-2023/CVE-2023-253xx/CVE-2023-25345.json
index 7a094b90df6..f188f7bef44 100644
--- a/CVE-2023/CVE-2023-253xx/CVE-2023-25345.json
+++ b/CVE-2023/CVE-2023-253xx/CVE-2023-25345.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-25345",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-15T20:15:10.533",
- "lastModified": "2024-11-21T07:49:25.413",
+ "lastModified": "2025-02-27T19:15:48.070",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 3.9,
"impactScore": 3.6
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-22"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-22"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2023/CVE-2023-255xx/CVE-2023-25595.json b/CVE-2023/CVE-2023-255xx/CVE-2023-25595.json
index 53e79740dfe..ae31adea0e0 100644
--- a/CVE-2023/CVE-2023-255xx/CVE-2023-25595.json
+++ b/CVE-2023/CVE-2023-255xx/CVE-2023-25595.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-25595",
"sourceIdentifier": "security-alert@hpe.com",
"published": "2023-03-22T06:15:10.430",
- "lastModified": "2024-11-21T07:49:47.773",
+ "lastModified": "2025-02-27T19:15:48.220",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -65,6 +65,16 @@
"value": "NVD-CWE-noinfo"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-284"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2023/CVE-2023-269xx/CVE-2023-26912.json b/CVE-2023/CVE-2023-269xx/CVE-2023-26912.json
index 7b257d49a69..52f51c8dd1f 100644
--- a/CVE-2023/CVE-2023-269xx/CVE-2023-26912.json
+++ b/CVE-2023/CVE-2023-269xx/CVE-2023-26912.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-26912",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-15T20:15:10.683",
- "lastModified": "2024-11-21T07:52:03.133",
+ "lastModified": "2025-02-27T20:15:36.577",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 1.7,
"impactScore": 2.7
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
+ "baseScore": 4.8,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "HIGH",
+ "userInteraction": "REQUIRED",
+ "scope": "CHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 1.7,
+ "impactScore": 2.7
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-79"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-79"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2023/CVE-2023-270xx/CVE-2023-27070.json b/CVE-2023/CVE-2023-270xx/CVE-2023-27070.json
index 01b25f214de..3dc9bb70f51 100644
--- a/CVE-2023/CVE-2023-270xx/CVE-2023-27070.json
+++ b/CVE-2023/CVE-2023-270xx/CVE-2023-27070.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-27070",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-14T16:15:10.553",
- "lastModified": "2024-11-21T07:52:16.097",
+ "lastModified": "2025-02-27T20:15:36.750",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 2.3,
"impactScore": 2.7
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
+ "baseScore": 5.4,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "REQUIRED",
+ "scope": "CHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.3,
+ "impactScore": 2.7
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-79"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-79"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2023/CVE-2023-270xx/CVE-2023-27073.json b/CVE-2023/CVE-2023-270xx/CVE-2023-27073.json
index 7a2956c2311..48287778e17 100644
--- a/CVE-2023/CVE-2023-270xx/CVE-2023-27073.json
+++ b/CVE-2023/CVE-2023-270xx/CVE-2023-27073.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-27073",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-14T15:15:12.313",
- "lastModified": "2024-11-21T07:52:16.240",
+ "lastModified": "2025-02-27T20:15:36.933",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 2.8,
"impactScore": 3.6
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
+ "baseScore": 6.5,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "REQUIRED",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 3.6
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-352"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-352"
+ }
+ ]
}
],
"configurations": [
@@ -86,6 +116,10 @@
"tags": [
"Product"
]
+ },
+ {
+ "url": "https://github.com/bhaveshkush007/CVEs/blob/main/CVE-2023-27073.txt",
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
}
]
}
\ No newline at end of file
diff --git a/CVE-2023/CVE-2023-272xx/CVE-2023-27234.json b/CVE-2023/CVE-2023-272xx/CVE-2023-27234.json
index 3b5a50d0232..a3073822e85 100644
--- a/CVE-2023/CVE-2023-272xx/CVE-2023-27234.json
+++ b/CVE-2023/CVE-2023-272xx/CVE-2023-27234.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-27234",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-15T05:15:42.897",
- "lastModified": "2024-11-21T07:52:29.960",
+ "lastModified": "2025-02-27T20:15:37.103",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 2.8,
"impactScore": 3.6
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
+ "baseScore": 6.5,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "REQUIRED",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 3.6
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-352"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-352"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2023/CVE-2023-281xx/CVE-2023-28144.json b/CVE-2023/CVE-2023-281xx/CVE-2023-28144.json
index e6cf8430849..2af9ce9f4be 100644
--- a/CVE-2023/CVE-2023-281xx/CVE-2023-28144.json
+++ b/CVE-2023/CVE-2023-281xx/CVE-2023-28144.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-28144",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-14T19:15:10.643",
- "lastModified": "2024-11-21T07:54:29.017",
+ "lastModified": "2025-02-27T20:15:37.270",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 1.0,
"impactScore": 5.9
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.0,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "HIGH",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.0,
+ "impactScore": 5.9
}
]
},
@@ -45,6 +65,16 @@
"value": "CWE-362"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-362"
+ }
+ ]
}
],
"configurations": [
diff --git a/CVE-2023/CVE-2023-281xx/CVE-2023-28154.json b/CVE-2023/CVE-2023-281xx/CVE-2023-28154.json
index 5b58cb04088..7823149be21 100644
--- a/CVE-2023/CVE-2023-281xx/CVE-2023-28154.json
+++ b/CVE-2023/CVE-2023-281xx/CVE-2023-28154.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-28154",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-13T01:15:10.053",
- "lastModified": "2024-11-21T07:54:30.030",
+ "lastModified": "2025-02-27T20:15:37.440",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 3.9,
"impactScore": 5.9
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 9.8,
+ "baseSeverity": "CRITICAL",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 5.9
}
]
},
diff --git a/CVE-2023/CVE-2023-283xx/CVE-2023-28339.json b/CVE-2023/CVE-2023-283xx/CVE-2023-28339.json
index 82325ca678e..142e5a18e5c 100644
--- a/CVE-2023/CVE-2023-283xx/CVE-2023-28339.json
+++ b/CVE-2023/CVE-2023-283xx/CVE-2023-28339.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-28339",
"sourceIdentifier": "cve@mitre.org",
"published": "2023-03-14T19:15:10.717",
- "lastModified": "2024-11-21T07:54:52.773",
+ "lastModified": "2025-02-27T20:15:37.613",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -32,6 +32,26 @@
},
"exploitabilityScore": 2.8,
"impactScore": 5.9
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 8.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 5.9
}
]
},
@@ -45,6 +65,16 @@
"value": "NVD-CWE-noinfo"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-269"
+ }
+ ]
}
],
"configurations": [
@@ -79,6 +109,13 @@
"tags": [
"Issue Tracking"
]
+ },
+ {
+ "url": "https://github.com/Duncaen/OpenDoas/issues/106",
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "tags": [
+ "Issue Tracking"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2023/CVE-2023-308xx/CVE-2023-30873.json b/CVE-2023/CVE-2023-308xx/CVE-2023-30873.json
index 525c94e4030..da4bdc4ccbd 100644
--- a/CVE-2023/CVE-2023-308xx/CVE-2023-30873.json
+++ b/CVE-2023/CVE-2023-308xx/CVE-2023-30873.json
@@ -2,8 +2,8 @@
"id": "CVE-2023-30873",
"sourceIdentifier": "audit@patchstack.com",
"published": "2024-12-09T13:15:28.413",
- "lastModified": "2024-12-09T13:15:28.413",
- "vulnStatus": "Awaiting Analysis",
+ "lastModified": "2025-02-27T20:54:25.290",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 2.8,
"impactScore": 2.5
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 8.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 5.9
}
]
},
@@ -51,10 +71,31 @@
]
}
],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:androidbubble:wp_docs:*:*:*:*:*:wordpress:*:*",
+ "versionEndExcluding": "1.9.9",
+ "matchCriteriaId": "ACE07067-B4AC-4D89-9828-9802FE5A1DA3"
+ }
+ ]
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://patchstack.com/database/wordpress/plugin/wp-docs/vulnerability/wordpress-wp-docs-plugin-1-9-8-broken-access-control?_s_id=cve",
- "source": "audit@patchstack.com"
+ "source": "audit@patchstack.com",
+ "tags": [
+ "Third Party Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2023/CVE-2023-522xx/CVE-2023-52235.json b/CVE-2023/CVE-2023-522xx/CVE-2023-52235.json
index 4653b9a5c5b..5217eeeb27a 100644
--- a/CVE-2023/CVE-2023-522xx/CVE-2023-52235.json
+++ b/CVE-2023/CVE-2023-522xx/CVE-2023-52235.json
@@ -2,7 +2,7 @@
"id": "CVE-2023-52235",
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-05T06:15:10.060",
- "lastModified": "2024-11-21T08:39:27.413",
+ "lastModified": "2025-02-27T20:15:37.787",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -15,42 +15,7 @@
"value": "El router Wi-Fi SpaceX Starlink GEN 2 anterior a 2023.53.0 y Starlink Dish anterior a 07dd2798-ff15-4722-a9ee-de28928aed34 permiten CSRF (por ejemplo, para un reinicio) a trav\u00e9s de un ataque de reenlace de DNS."
}
],
- "metrics": {
- "cvssMetricV31": [
- {
- "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
- "type": "Secondary",
- "cvssData": {
- "version": "3.1",
- "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
- "baseScore": 8.8,
- "baseSeverity": "HIGH",
- "attackVector": "NETWORK",
- "attackComplexity": "LOW",
- "privilegesRequired": "NONE",
- "userInteraction": "REQUIRED",
- "scope": "UNCHANGED",
- "confidentialityImpact": "HIGH",
- "integrityImpact": "HIGH",
- "availabilityImpact": "HIGH"
- },
- "exploitabilityScore": 2.8,
- "impactScore": 5.9
- }
- ]
- },
- "weaknesses": [
- {
- "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
- "type": "Secondary",
- "description": [
- {
- "lang": "en",
- "value": "CWE-350"
- }
- ]
- }
- ],
+ "metrics": {},
"references": [
{
"url": "https://bugcrowd.com/disclosures/f529009b-90eb-4bf9-957d-6fe7ea890fa2/starlink-dishy-is-vulnerable-to-csrf-via-dns-rebinding",
diff --git a/CVE-2024/CVE-2024-267xx/CVE-2024-26735.json b/CVE-2024/CVE-2024-267xx/CVE-2024-26735.json
index 89ebef20ad3..666d97fc050 100644
--- a/CVE-2024/CVE-2024-267xx/CVE-2024-26735.json
+++ b/CVE-2024/CVE-2024-267xx/CVE-2024-26735.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-26735",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-04-03T17:15:51.147",
- "lastModified": "2024-11-21T09:02:56.883",
+ "lastModified": "2025-02-27T20:15:38.000",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -15,42 +15,7 @@
"value": "En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: ipv6:sr: corrige posible use-after-free y null-ptr-deref La estructura de operaciones pernet para el subsystem debe registrarse antes de registrar la familia netlink gen\u00e9rica."
}
],
- "metrics": {
- "cvssMetricV31": [
- {
- "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
- "type": "Secondary",
- "cvssData": {
- "version": "3.1",
- "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
- "baseScore": 5.5,
- "baseSeverity": "MEDIUM",
- "attackVector": "LOCAL",
- "attackComplexity": "LOW",
- "privilegesRequired": "LOW",
- "userInteraction": "NONE",
- "scope": "UNCHANGED",
- "confidentialityImpact": "NONE",
- "integrityImpact": "NONE",
- "availabilityImpact": "HIGH"
- },
- "exploitabilityScore": 1.8,
- "impactScore": 3.6
- }
- ]
- },
- "weaknesses": [
- {
- "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
- "type": "Secondary",
- "description": [
- {
- "lang": "en",
- "value": "CWE-416"
- }
- ]
- }
- ],
+ "metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/02b08db594e8218cfbc0e4680d4331b457968a9b",
diff --git a/CVE-2024/CVE-2024-26xx/CVE-2024-2689.json b/CVE-2024/CVE-2024-26xx/CVE-2024-2689.json
index 90a45260f28..baa240dadfb 100644
--- a/CVE-2024/CVE-2024-26xx/CVE-2024-2689.json
+++ b/CVE-2024/CVE-2024-26xx/CVE-2024-2689.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-2689",
"sourceIdentifier": "security@temporal.io",
"published": "2024-04-03T22:15:07.290",
- "lastModified": "2024-11-21T09:10:17.947",
+ "lastModified": "2025-02-27T20:15:38.563",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 0.7,
"impactScore": 3.6
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H",
+ "baseScore": 4.4,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "HIGH",
+ "privilegesRequired": "HIGH",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 0.7,
+ "impactScore": 3.6
}
]
},
@@ -49,6 +69,16 @@
"value": "CWE-20"
}
]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-20"
+ }
+ ]
}
],
"references": [
diff --git a/CVE-2024/CVE-2024-273xx/CVE-2024-27345.json b/CVE-2024/CVE-2024-273xx/CVE-2024-27345.json
index 9b302e88356..8eb9e4dd679 100644
--- a/CVE-2024/CVE-2024-273xx/CVE-2024-27345.json
+++ b/CVE-2024/CVE-2024-273xx/CVE-2024-27345.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-27345",
"sourceIdentifier": "zdi-disclosures@trendmicro.com",
"published": "2024-04-03T17:15:55.353",
- "lastModified": "2024-11-21T09:04:22.933",
+ "lastModified": "2025-02-27T20:15:38.220",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -16,6 +16,28 @@
}
],
"metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N",
+ "baseScore": 3.3,
+ "baseSeverity": "LOW",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "REQUIRED",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 1.4
+ }
+ ],
"cvssMetricV30": [
{
"source": "zdi-disclosures@trendmicro.com",
@@ -42,7 +64,17 @@
"weaknesses": [
{
"source": "zdi-disclosures@trendmicro.com",
- "type": "Secondary",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-125"
+ }
+ ]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Primary",
"description": [
{
"lang": "en",
diff --git a/CVE-2024/CVE-2024-28xx/CVE-2024-2868.json b/CVE-2024/CVE-2024-28xx/CVE-2024-2868.json
index 2913bdb38b0..e982d0ccb54 100644
--- a/CVE-2024/CVE-2024-28xx/CVE-2024-2868.json
+++ b/CVE-2024/CVE-2024-28xx/CVE-2024-2868.json
@@ -2,8 +2,8 @@
"id": "CVE-2024-2868",
"sourceIdentifier": "security@wordfence.com",
"published": "2024-04-04T02:15:07.010",
- "lastModified": "2024-11-21T09:10:43.007",
- "vulnStatus": "Awaiting Analysis",
+ "lastModified": "2025-02-27T20:15:38.733",
+ "vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{
@@ -36,9 +36,41 @@
},
"exploitabilityScore": 3.1,
"impactScore": 2.7
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
+ "baseScore": 6.4,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "CHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.1,
+ "impactScore": 2.7
}
]
},
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-80"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://plugins.trac.wordpress.org/browser/woolentor-addons/tags/2.8.2/includes/addons/universal_product.php#L2548",
diff --git a/CVE-2024/CVE-2024-297xx/CVE-2024-29741.json b/CVE-2024/CVE-2024-297xx/CVE-2024-29741.json
index 8d169aa0b98..a1c1b188f29 100644
--- a/CVE-2024/CVE-2024-297xx/CVE-2024-29741.json
+++ b/CVE-2024/CVE-2024-297xx/CVE-2024-29741.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-29741",
"sourceIdentifier": "dsap-vuln-management@google.com",
"published": "2024-04-05T20:15:08.060",
- "lastModified": "2024-11-21T09:08:13.000",
+ "lastModified": "2025-02-27T20:15:38.403",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -15,7 +15,42 @@
"value": "En pblS2mpuResume de s2mpu.c, existe una posible omisi\u00f3n de mitigaci\u00f3n debido a un error l\u00f3gico en el c\u00f3digo. Esto podr\u00eda conducir a una escalada local de privilegios sin necesidad de permisos de ejecuci\u00f3n adicionales. La interacci\u00f3n del usuario no es necesaria para la explotaci\u00f3n."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-269"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://source.android.com/security/bulletin/pixel/2024-04-01",
diff --git a/CVE-2024/CVE-2024-302xx/CVE-2024-30252.json b/CVE-2024/CVE-2024-302xx/CVE-2024-30252.json
index 2cafb8c8cc9..1adbaf68cee 100644
--- a/CVE-2024/CVE-2024-302xx/CVE-2024-30252.json
+++ b/CVE-2024/CVE-2024-302xx/CVE-2024-30252.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-30252",
"sourceIdentifier": "security-advisories@github.com",
"published": "2024-04-04T19:15:08.547",
- "lastModified": "2024-11-21T09:11:32.780",
+ "lastModified": "2025-02-27T20:15:38.923",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -36,13 +36,43 @@
},
"exploitabilityScore": 1.2,
"impactScore": 1.4
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N",
+ "baseScore": 2.6,
+ "baseSeverity": "LOW",
+ "attackVector": "NETWORK",
+ "attackComplexity": "HIGH",
+ "privilegesRequired": "LOW",
+ "userInteraction": "REQUIRED",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 1.2,
+ "impactScore": 1.4
}
]
},
"weaknesses": [
{
"source": "security-advisories@github.com",
- "type": "Secondary",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-352"
+ }
+ ]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Primary",
"description": [
{
"lang": "en",
diff --git a/CVE-2024/CVE-2024-303xx/CVE-2024-30330.json b/CVE-2024/CVE-2024-303xx/CVE-2024-30330.json
index fa2a84b7e82..0b055f35954 100644
--- a/CVE-2024/CVE-2024-303xx/CVE-2024-30330.json
+++ b/CVE-2024/CVE-2024-303xx/CVE-2024-30330.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-30330",
"sourceIdentifier": "zdi-disclosures@trendmicro.com",
"published": "2024-04-03T17:15:57.450",
- "lastModified": "2024-11-21T09:11:42.297",
+ "lastModified": "2025-02-27T20:15:39.110",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -16,6 +16,28 @@
}
],
"metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "REQUIRED",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ],
"cvssMetricV30": [
{
"source": "zdi-disclosures@trendmicro.com",
@@ -42,7 +64,17 @@
"weaknesses": [
{
"source": "zdi-disclosures@trendmicro.com",
- "type": "Secondary",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ },
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Primary",
"description": [
{
"lang": "en",
diff --git a/CVE-2024/CVE-2024-309xx/CVE-2024-30977.json b/CVE-2024/CVE-2024-309xx/CVE-2024-30977.json
index a98e4e327f9..90e1e49c076 100644
--- a/CVE-2024/CVE-2024-309xx/CVE-2024-30977.json
+++ b/CVE-2024/CVE-2024-309xx/CVE-2024-30977.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-30977",
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-05T21:15:09.740",
- "lastModified": "2024-11-21T09:12:39.107",
+ "lastModified": "2025-02-27T20:15:39.290",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -15,42 +15,7 @@
"value": "Un problema en Secnet Security Network Intelligent AC Management System v.1.02.040 permite a un atacante local escalar privilegios a trav\u00e9s del componente de contrase\u00f1a."
}
],
- "metrics": {
- "cvssMetricV31": [
- {
- "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
- "type": "Secondary",
- "cvssData": {
- "version": "3.1",
- "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
- "baseScore": 7.8,
- "baseSeverity": "HIGH",
- "attackVector": "LOCAL",
- "attackComplexity": "LOW",
- "privilegesRequired": "LOW",
- "userInteraction": "NONE",
- "scope": "UNCHANGED",
- "confidentialityImpact": "HIGH",
- "integrityImpact": "HIGH",
- "availabilityImpact": "HIGH"
- },
- "exploitabilityScore": 1.8,
- "impactScore": 5.9
- }
- ]
- },
- "weaknesses": [
- {
- "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
- "type": "Secondary",
- "description": [
- {
- "lang": "en",
- "value": "CWE-269"
- }
- ]
- }
- ],
+ "metrics": {},
"references": [
{
"url": "http://www.secnet.cn/newsdetail/388.html",
diff --git a/CVE-2024/CVE-2024-369xx/CVE-2024-36942.json b/CVE-2024/CVE-2024-369xx/CVE-2024-36942.json
index 937751d1329..698c0c71d1f 100644
--- a/CVE-2024/CVE-2024-369xx/CVE-2024-36942.json
+++ b/CVE-2024/CVE-2024-369xx/CVE-2024-36942.json
@@ -2,199 +2,15 @@
"id": "CVE-2024-36942",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-05-30T16:15:17.227",
- "lastModified": "2025-02-03T15:51:09.253",
- "vulnStatus": "Analyzed",
+ "lastModified": "2025-02-27T20:15:39.403",
+ "vulnStatus": "Rejected",
"cveTags": [],
"descriptions": [
{
"lang": "en",
- "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: qca: fix firmware check error path\n\nA recent commit fixed the code that parses the firmware files before\ndownloading them to the controller but introduced a memory leak in case\nthe sanity checks ever fail.\n\nMake sure to free the firmware buffer before returning on errors."
- },
- {
- "lang": "es",
- "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: Bluetooth: qca: corregir ruta de error de verificaci\u00f3n de firmware Una confirmaci\u00f3n reciente corrigi\u00f3 el c\u00f3digo que analiza los archivos de firmware antes de descargarlos al controlador, pero introdujo una p\u00e9rdida de memoria en caso de que las comprobaciones de cordura alguna vez fallaran. Aseg\u00farese de liberar el b\u00fafer de firmware antes de regresar con errores."
+ "value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
}
],
- "metrics": {
- "cvssMetricV31": [
- {
- "source": "nvd@nist.gov",
- "type": "Primary",
- "cvssData": {
- "version": "3.1",
- "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
- "baseScore": 5.5,
- "baseSeverity": "MEDIUM",
- "attackVector": "LOCAL",
- "attackComplexity": "LOW",
- "privilegesRequired": "LOW",
- "userInteraction": "NONE",
- "scope": "UNCHANGED",
- "confidentialityImpact": "NONE",
- "integrityImpact": "NONE",
- "availabilityImpact": "HIGH"
- },
- "exploitabilityScore": 1.8,
- "impactScore": 3.6
- }
- ]
- },
- "weaknesses": [
- {
- "source": "nvd@nist.gov",
- "type": "Primary",
- "description": [
- {
- "lang": "en",
- "value": "CWE-401"
- }
- ]
- }
- ],
- "configurations": [
- {
- "nodes": [
- {
- "operator": "OR",
- "negate": false,
- "cpeMatch": [
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
- "versionEndExcluding": "5.15.159",
- "matchCriteriaId": "D196D9AF-1373-46B8-84E1-A62C30A7EA3C"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
- "versionStartIncluding": "5.16",
- "versionEndExcluding": "6.1.91",
- "matchCriteriaId": "4F8C886C-75AA-469B-A6A9-12BF1A29C0D5"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
- "versionStartIncluding": "6.2",
- "versionEndExcluding": "6.6.31",
- "matchCriteriaId": "CDDB1F69-36AC-41C1-9192-E7CCEF5FFC00"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
- "versionStartIncluding": "6.7",
- "versionEndExcluding": "6.8.10",
- "matchCriteriaId": "6A6B920C-8D8F-4130-86B4-AD334F4CF2E3"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*",
- "matchCriteriaId": "22BEDD49-2C6D-402D-9DBF-6646F6ECD10B"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*",
- "matchCriteriaId": "DF73CB2A-DFFD-46FB-9BFE-AA394F27EA37"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*",
- "matchCriteriaId": "52048DDA-FC5A-4363-95A0-A6357B4D7F8C"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*",
- "matchCriteriaId": "A06B2CCF-3F43-4FA9-8773-C83C3F5764B2"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:*",
- "matchCriteriaId": "F850DCEC-E08B-4317-A33B-D2DCF39F601B"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc6:*:*:*:*:*:*",
- "matchCriteriaId": "91326417-E981-482E-A5A3-28BC1327521B"
- },
- {
- "vulnerable": true,
- "criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc7:*:*:*:*:*:*",
- "matchCriteriaId": "DAECDCD8-F556-4606-8D7B-5C6D47A501F2"
- }
- ]
- }
- ]
- }
- ],
- "references": [
- {
- "url": "https://git.kernel.org/stable/c/064688d70c33bb5b49dde6e972b9379a8b045d8a",
- "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/40d442f969fb1e871da6fca73d3f8aef1f888558",
- "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/580bcd6bf24f9975f97d81d5ef1b64cca9240df9",
- "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/7bcba557d5c37cd09ecd5abbe7d50deb86c36d3f",
- "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/d1f768214320852766a60a815a0be8f14fba0cc3",
- "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/064688d70c33bb5b49dde6e972b9379a8b045d8a",
- "source": "af854a3a-2127-422b-91ae-364da2661108",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/40d442f969fb1e871da6fca73d3f8aef1f888558",
- "source": "af854a3a-2127-422b-91ae-364da2661108",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/580bcd6bf24f9975f97d81d5ef1b64cca9240df9",
- "source": "af854a3a-2127-422b-91ae-364da2661108",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/7bcba557d5c37cd09ecd5abbe7d50deb86c36d3f",
- "source": "af854a3a-2127-422b-91ae-364da2661108",
- "tags": [
- "Patch"
- ]
- },
- {
- "url": "https://git.kernel.org/stable/c/d1f768214320852766a60a815a0be8f14fba0cc3",
- "source": "af854a3a-2127-422b-91ae-364da2661108",
- "tags": [
- "Patch"
- ]
- }
- ]
+ "metrics": {},
+ "references": []
}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-440xx/CVE-2024-44042.json b/CVE-2024/CVE-2024-440xx/CVE-2024-44042.json
index 55f793f1a4a..cfa3bb28ecb 100644
--- a/CVE-2024/CVE-2024-440xx/CVE-2024-44042.json
+++ b/CVE-2024/CVE-2024-440xx/CVE-2024-44042.json
@@ -2,8 +2,8 @@
"id": "CVE-2024-44042",
"sourceIdentifier": "audit@patchstack.com",
"published": "2024-10-06T12:15:04.203",
- "lastModified": "2024-10-07T17:47:48.410",
- "vulnStatus": "Awaiting Analysis",
+ "lastModified": "2025-02-27T19:30:33.180",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 1.7,
"impactScore": 3.7
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
+ "baseScore": 4.8,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "HIGH",
+ "userInteraction": "REQUIRED",
+ "scope": "CHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 1.7,
+ "impactScore": 2.7
}
]
},
@@ -51,10 +71,31 @@
]
}
],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:androidbubbles:wp_datepicker:*:*:*:*:*:wordpress:*:*",
+ "versionEndExcluding": "2.1.2",
+ "matchCriteriaId": "902921D1-B15E-43F0-864A-CF1B5E2AB366"
+ }
+ ]
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://patchstack.com/database/vulnerability/wp-datepicker/wordpress-wp-datepicker-plugin-2-1-1-cross-site-scripting-xss-vulnerability?_s_id=cve",
- "source": "audit@patchstack.com"
+ "source": "audit@patchstack.com",
+ "tags": [
+ "Third Party Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-440xx/CVE-2024-44045.json b/CVE-2024/CVE-2024-440xx/CVE-2024-44045.json
index 8deb11d271e..e66c2fe8cc5 100644
--- a/CVE-2024/CVE-2024-440xx/CVE-2024-44045.json
+++ b/CVE-2024/CVE-2024-440xx/CVE-2024-44045.json
@@ -2,8 +2,8 @@
"id": "CVE-2024-44045",
"sourceIdentifier": "audit@patchstack.com",
"published": "2024-10-06T12:15:04.630",
- "lastModified": "2024-10-07T17:47:48.410",
- "vulnStatus": "Awaiting Analysis",
+ "lastModified": "2025-02-27T19:30:33.180",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 1.7,
"impactScore": 3.7
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
+ "baseScore": 4.8,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "HIGH",
+ "userInteraction": "REQUIRED",
+ "scope": "CHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 1.7,
+ "impactScore": 2.7
}
]
},
@@ -51,10 +71,31 @@
]
}
],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:kevonadonis:wp_abstracts:*:*:*:*:free:wordpress:*:*",
+ "versionEndExcluding": "2.7.0",
+ "matchCriteriaId": "48E969BF-7DA0-475F-8F78-277188996CFD"
+ }
+ ]
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://patchstack.com/database/vulnerability/wp-abstracts-manuscripts-manager/wordpress-wp-abstracts-plugin-2-6-5-cross-site-scripting-xss-vulnerability?_s_id=cve",
- "source": "audit@patchstack.com"
+ "source": "audit@patchstack.com",
+ "tags": [
+ "Third Party Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-470xx/CVE-2024-47059.json b/CVE-2024/CVE-2024-470xx/CVE-2024-47059.json
index 4e055197311..4b18d266b27 100644
--- a/CVE-2024/CVE-2024-470xx/CVE-2024-47059.json
+++ b/CVE-2024/CVE-2024-470xx/CVE-2024-47059.json
@@ -2,8 +2,8 @@
"id": "CVE-2024-47059",
"sourceIdentifier": "security@mautic.org",
"published": "2024-09-18T22:15:04.650",
- "lastModified": "2024-09-20T12:30:17.483",
- "vulnStatus": "Undergoing Analysis",
+ "lastModified": "2025-02-27T19:30:33.180",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 2.8,
"impactScore": 1.4
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
+ "baseScore": 4.3,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 1.4
}
]
},
@@ -49,12 +69,42 @@
"value": "CWE-200"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "NVD-CWE-Other"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:acquia:mautic:5.1.0:*:*:*:*:*:*:*",
+ "matchCriteriaId": "218C24B5-AAED-49DE-BD4D-DA7B37D55744"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://github.com/mautic/mautic/security/advisories/GHSA-8vff-35qm-qjvv",
- "source": "security@mautic.org"
+ "source": "security@mautic.org",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-533xx/CVE-2024-53379.json b/CVE-2024/CVE-2024-533xx/CVE-2024-53379.json
index 8bc6abf2691..4566ed29c92 100644
--- a/CVE-2024/CVE-2024-533xx/CVE-2024-53379.json
+++ b/CVE-2024/CVE-2024-533xx/CVE-2024-53379.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-53379",
"sourceIdentifier": "cve@mitre.org",
"published": "2025-01-23T23:15:07.993",
- "lastModified": "2025-01-23T23:15:07.993",
+ "lastModified": "2025-02-27T19:15:48.927",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
@@ -15,11 +15,50 @@
"value": "El desbordamiento del b\u00fafer de mont\u00f3n en la implementaci\u00f3n del protocolo de enlace del sitio del servidor en la versi\u00f3n SharkSSL de Real Time Logic LLC (del 24/05/05), el commit 64808a5e12c83b38f85c943dee0112e428dc2a43 permite que un atacante remoto active una denegaci\u00f3n de servicio a trav\u00e9s de un mensaje Client-Hello mal formado."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-120"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://www.telekom.com/resource/blob/1086326/e6e800ec1e4e675ca0d8fdafab86ea8c/dl-250122-cve-2024-53379-data.pdf",
"source": "cve@mitre.org"
+ },
+ {
+ "url": "https://www.telekom.com/resource/blob/1086326/e6e800ec1e4e675ca0d8fdafab86ea8c/dl-250122-cve-2024-53379-data.pdf",
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
}
]
}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-534xx/CVE-2024-53408.json b/CVE-2024/CVE-2024-534xx/CVE-2024-53408.json
new file mode 100644
index 00000000000..2830099a375
--- /dev/null
+++ b/CVE-2024/CVE-2024-534xx/CVE-2024-53408.json
@@ -0,0 +1,21 @@
+{
+ "id": "CVE-2024-53408",
+ "sourceIdentifier": "cve@mitre.org",
+ "published": "2025-02-27T20:16:01.790",
+ "lastModified": "2025-02-27T20:16:01.790",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "AVE System Web Client v2.1.131.13992 was discovered to contain a cross-site scripting (XSS) vulnerability."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://cosmosofcyberspace.github.io/ave-system-cve.html",
+ "source": "cve@mitre.org"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-539xx/CVE-2024-53944.json b/CVE-2024/CVE-2024-539xx/CVE-2024-53944.json
new file mode 100644
index 00000000000..43254e347a3
--- /dev/null
+++ b/CVE-2024/CVE-2024-539xx/CVE-2024-53944.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2024-53944",
+ "sourceIdentifier": "cve@mitre.org",
+ "published": "2025-02-27T20:16:01.887",
+ "lastModified": "2025-02-27T20:16:01.887",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "An issue was discovered on Tuoshi/Dionlink LT15D 4G Wi-Fi devices through M7628NNxlSPv2xUI_v1.0.1802.10.08_P4 and LT21B devices through M7628xUSAxUIv2_v1.0.1481.15.02_P0. A unauthenticated remote attacker with network access can exploit a command injection vulnerability. The /goform/formJsonAjaxReq endpoint fails to sanitize shell metacharacters sent via JSON parameters, thus allowing attackers to execute arbitrary OS commands with root privileges."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "http://www.tuoshi.net/productview.asp?id=218",
+ "source": "cve@mitre.org"
+ },
+ {
+ "url": "http://www.tuoshi.net/productview.asp?id=226",
+ "source": "cve@mitre.org"
+ },
+ {
+ "url": "https://github.com/actuator/cve/blob/main/Tuoshi/CVE-2024-53944-Whitepaper.pdf",
+ "source": "cve@mitre.org"
+ },
+ {
+ "url": "https://github.com/actuator/cve/blob/main/Tuoshi/CVE-2024-53944.txt",
+ "source": "cve@mitre.org"
+ },
+ {
+ "url": "https://github.com/actuator/cve/blob/main/Tuoshi/Firmware-M7628NNxISPv2xUI_v1.0.1802.10.08_P4-Blind-CMD-Injection-unauth-WAN.gif",
+ "source": "cve@mitre.org"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-549xx/CVE-2024-54957.json b/CVE-2024/CVE-2024-549xx/CVE-2024-54957.json
new file mode 100644
index 00000000000..925338820b3
--- /dev/null
+++ b/CVE-2024/CVE-2024-549xx/CVE-2024-54957.json
@@ -0,0 +1,25 @@
+{
+ "id": "CVE-2024-54957",
+ "sourceIdentifier": "cve@mitre.org",
+ "published": "2025-02-27T20:16:01.980",
+ "lastModified": "2025-02-27T20:16:01.980",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "Nagios XI 2024R1.2.2 is vulnerable to an open redirect flaw on the Tools page, exploitable by users with read-only permissions. This vulnerability allows an attacker to craft a malicious link that redirects users to an arbitrary external URL without their consent."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://github.com/Sharpe-nl/CVEs/tree/main/CVE-2024-54957",
+ "source": "cve@mitre.org"
+ },
+ {
+ "url": "https://www.nagios.com/products/security/",
+ "source": "cve@mitre.org"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-579xx/CVE-2024-57979.json b/CVE-2024/CVE-2024-579xx/CVE-2024-57979.json
index 5127d1671d9..fffbd3f24b9 100644
--- a/CVE-2024/CVE-2024-579xx/CVE-2024-57979.json
+++ b/CVE-2024/CVE-2024-579xx/CVE-2024-57979.json
@@ -2,7 +2,7 @@
"id": "CVE-2024-57979",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T02:15:11.087",
- "lastModified": "2025-02-27T02:15:11.087",
+ "lastModified": "2025-02-27T19:15:49.077",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\npps: Fix a use-after-free\n\nOn a board running ntpd and gpsd, I'm seeing a consistent use-after-free\nin sys_exit() from gpsd when rebooting:\n\n pps pps1: removed\n ------------[ cut here ]------------\n kobject: '(null)' (00000000db4bec24): is not initialized, yet kobject_put() is being called.\n WARNING: CPU: 2 PID: 440 at lib/kobject.c:734 kobject_put+0x120/0x150\n CPU: 2 UID: 299 PID: 440 Comm: gpsd Not tainted 6.11.0-rc6-00308-gb31c44928842 #1\n Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)\n pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : kobject_put+0x120/0x150\n lr : kobject_put+0x120/0x150\n sp : ffffffc0803d3ae0\n x29: ffffffc0803d3ae0 x28: ffffff8042dc9738 x27: 0000000000000001\n x26: 0000000000000000 x25: ffffff8042dc9040 x24: ffffff8042dc9440\n x23: ffffff80402a4620 x22: ffffff8042ef4bd0 x21: ffffff80405cb600\n x20: 000000000008001b x19: ffffff8040b3b6e0 x18: 0000000000000000\n x17: 0000000000000000 x16: 0000000000000000 x15: 696e6920746f6e20\n x14: 7369203a29343263 x13: 205d303434542020 x12: 0000000000000000\n x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000\n x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000\n x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000\n x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000\n Call trace:\n kobject_put+0x120/0x150\n cdev_put+0x20/0x3c\n __fput+0x2c4/0x2d8\n ____fput+0x1c/0x38\n task_work_run+0x70/0xfc\n do_exit+0x2a0/0x924\n do_group_exit+0x34/0x90\n get_signal+0x7fc/0x8c0\n do_signal+0x128/0x13b4\n do_notify_resume+0xdc/0x160\n el0_svc+0xd4/0xf8\n el0t_64_sync_handler+0x140/0x14c\n el0t_64_sync+0x190/0x194\n ---[ end trace 0000000000000000 ]---\n\n...followed by more symptoms of corruption, with similar stacks:\n\n refcount_t: underflow; use-after-free.\n kernel BUG at lib/list_debug.c:62!\n Kernel panic - not syncing: Oops - BUG: Fatal exception\n\nThis happens because pps_device_destruct() frees the pps_device with the\nembedded cdev immediately after calling cdev_del(), but, as the comment\nabove cdev_del() notes, fops for previously opened cdevs are still\ncallable even after cdev_del() returns. I think this bug has always\nbeen there: I can't explain why it suddenly started happening every time\nI reboot this particular board.\n\nIn commit d953e0e837e6 (\"pps: Fix a use-after free bug when\nunregistering a source.\"), George Spelvin suggested removing the\nembedded cdev. That seems like the simplest way to fix this, so I've\nimplemented his suggestion, using __register_chrdev() with pps_idr\nbecoming the source of truth for which minor corresponds to which\ndevice.\n\nBut now that pps_idr defines userspace visibility instead of cdev_add(),\nwe need to be sure the pps->dev refcount can't reach zero while\nuserspace can still find it again. So, the idr_remove() call moves to\npps_unregister_cdev(), and pps_idr now holds a reference to pps->dev.\n\n pps_core: source serial1 got cdev (251:1)\n <...>\n pps pps1: removed\n pps_core: unregistering pps1\n pps_core: deallocating pps1"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/7e5ee3281dc09014367f5112b6d566ba36ea2d49",
diff --git a/CVE-2024/CVE-2024-580xx/CVE-2024-58022.json b/CVE-2024/CVE-2024-580xx/CVE-2024-58022.json
new file mode 100644
index 00000000000..113891a0914
--- /dev/null
+++ b/CVE-2024/CVE-2024-580xx/CVE-2024-58022.json
@@ -0,0 +1,25 @@
+{
+ "id": "CVE-2024-58022",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.073",
+ "lastModified": "2025-02-27T20:16:02.073",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmailbox: th1520: Fix a NULL vs IS_ERR() bug\n\nThe devm_ioremap() function doesn't return error pointers, it returns\nNULL. Update the error checking to match."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/d0f98e14c010bcf27898b635a54c1994ac4110a8",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/ecbde88e544ff016fa08bbf2156dc431bb123e9b",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-580xx/CVE-2024-58034.json b/CVE-2024/CVE-2024-580xx/CVE-2024-58034.json
new file mode 100644
index 00000000000..1dd17e3e219
--- /dev/null
+++ b/CVE-2024/CVE-2024-580xx/CVE-2024-58034.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2024-58034",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.160",
+ "lastModified": "2025-02-27T20:16:02.160",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmemory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code()\n\nAs of_find_node_by_name() release the reference of the argument device\nnode, tegra_emc_find_node_by_ram_code() releases some device nodes while\nstill in use, resulting in possible UAFs. According to the bindings and\nthe in-tree DTS files, the \"emc-tables\" node is always device's child\nnode with the property \"nvidia,use-ram-code\", and the \"lpddr2\" node is a\nchild of the \"emc-tables\" node. Thus utilize the\nfor_each_child_of_node() macro and of_get_child_by_name() instead of\nof_find_node_by_name() to simplify the code.\n\nThis bug was found by an experimental verification tool that I am\ndeveloping.\n\n[krzysztof: applied v1, adjust the commit msg to incorporate v2 parts]"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/3b02273446e23961d910b50cc12528faec649fb2",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/755e44538c190c31de9090d8e8821d228fcfd416",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/b9784e5cde1f9fb83661a70e580e381ae1264d12",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/c144423cb07e4e227a8572d5742ca2b36ada770d",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/e9d07e91de140679eeaf275f47ad154467cb9e05",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-580xx/CVE-2024-58042.json b/CVE-2024/CVE-2024-580xx/CVE-2024-58042.json
new file mode 100644
index 00000000000..44af2678c74
--- /dev/null
+++ b/CVE-2024/CVE-2024-580xx/CVE-2024-58042.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2024-58042",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.257",
+ "lastModified": "2025-02-27T20:16:02.257",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrhashtable: Fix potential deadlock by moving schedule_work outside lock\n\nMove the hash table growth check and work scheduling outside the\nrht lock to prevent a possible circular locking dependency.\n\nThe original implementation could trigger a lockdep warning due to\na potential deadlock scenario involving nested locks between\nrhashtable bucket, rq lock, and dsq lock. By relocating the\ngrowth check and work scheduling after releasing the rth lock, we break\nthis potential deadlock chain.\n\nThis change expands the flexibility of rhashtable by removing\nrestrictive locking that previously limited its use in scheduler\nand workqueue contexts.\n\nImport to say that this calls rht_grow_above_75(), which reads from\nstruct rhashtable without holding the lock, if this is a problem, we can\nmove the check to the lock, and schedule the workqueue after the lock.\n\n\nModified so that atomic_inc is also moved outside of the bucket\nlock along with the growth above 75% check."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/ced8ce3c83a7150c5f5d371a8c332d7bc7f9b66d",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/e1d3422c95f003eba241c176adfe593c33e8a8f6",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/eb2e58484b838fb4e777ee9721bb9e20e6ca971d",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-86xx/CVE-2024-8626.json b/CVE-2024/CVE-2024-86xx/CVE-2024-8626.json
index 2cc4dd73f87..f4c985d8364 100644
--- a/CVE-2024/CVE-2024-86xx/CVE-2024-8626.json
+++ b/CVE-2024/CVE-2024-86xx/CVE-2024-8626.json
@@ -2,8 +2,8 @@
"id": "CVE-2024-8626",
"sourceIdentifier": "PSIRT@rockwellautomation.com",
"published": "2024-10-08T17:15:56.240",
- "lastModified": "2024-10-10T12:56:30.817",
- "vulnStatus": "Undergoing Analysis",
+ "lastModified": "2025-02-27T18:47:11.020",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -30,35 +30,57 @@
"attackRequirements": "NONE",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
- "vulnerableSystemConfidentiality": "HIGH",
- "vulnerableSystemIntegrity": "NONE",
- "vulnerableSystemAvailability": "NONE",
- "subsequentSystemConfidentiality": "NONE",
- "subsequentSystemIntegrity": "NONE",
- "subsequentSystemAvailability": "NONE",
+ "vulnConfidentialityImpact": "HIGH",
+ "vulnIntegrityImpact": "NONE",
+ "vulnAvailabilityImpact": "NONE",
+ "subConfidentialityImpact": "NONE",
+ "subIntegrityImpact": "NONE",
+ "subAvailabilityImpact": "NONE",
"exploitMaturity": "NOT_DEFINED",
- "confidentialityRequirements": "NOT_DEFINED",
- "integrityRequirements": "NOT_DEFINED",
- "availabilityRequirements": "NOT_DEFINED",
+ "confidentialityRequirement": "NOT_DEFINED",
+ "integrityRequirement": "NOT_DEFINED",
+ "availabilityRequirement": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
- "modifiedVulnerableSystemConfidentiality": "NOT_DEFINED",
- "modifiedVulnerableSystemIntegrity": "NOT_DEFINED",
- "modifiedVulnerableSystemAvailability": "NOT_DEFINED",
- "modifiedSubsequentSystemConfidentiality": "NOT_DEFINED",
- "modifiedSubsequentSystemIntegrity": "NOT_DEFINED",
- "modifiedSubsequentSystemAvailability": "NOT_DEFINED",
- "safety": "NOT_DEFINED",
- "automatable": "NOT_DEFINED",
- "recovery": "NOT_DEFINED",
+ "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
+ "modifiedVulnIntegrityImpact": "NOT_DEFINED",
+ "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
+ "modifiedSubConfidentialityImpact": "NOT_DEFINED",
+ "modifiedSubIntegrityImpact": "NOT_DEFINED",
+ "modifiedSubAvailabilityImpact": "NOT_DEFINED",
+ "Safety": "NOT_DEFINED",
+ "Automatable": "NOT_DEFINED",
+ "Recovery": "NOT_DEFINED",
"valueDensity": "NOT_DEFINED",
"vulnerabilityResponseEffort": "NOT_DEFINED",
"providerUrgency": "NOT_DEFINED"
}
}
+ ],
+ "cvssMetricV31": [
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
+ }
]
},
"weaknesses": [
@@ -71,12 +93,199 @@
"value": "CWE-400"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-401"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "operator": "AND",
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:o:rockwellautomation:compactlogix_5380_firmware:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "33.011",
+ "versionEndExcluding": "33.015",
+ "matchCriteriaId": "ADC47AB0-6712-473D-976D-4FE7CCFC2532"
+ }
+ ]
+ },
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": false,
+ "criteria": "cpe:2.3:h:rockwellautomation:compactlogix_5380:-:*:*:*:*:*:*:*",
+ "matchCriteriaId": "EDD040ED-B44C-47D0-B4D4-729C378C4F68"
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "operator": "AND",
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:o:rockwellautomation:compact_guardlogix_5380_firmware:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "33.011",
+ "versionEndExcluding": "33.015",
+ "matchCriteriaId": "9C7450A3-7B44-4CDE-B71A-91F4A695B922"
+ }
+ ]
+ },
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": false,
+ "criteria": "cpe:2.3:h:rockwellautomation:compact_guardlogix_5380:-:*:*:*:*:*:*:*",
+ "matchCriteriaId": "62414E65-73C7-4172-B7BF-F40A66AFBB90"
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "operator": "AND",
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:o:rockwellautomation:compactlogix_5480_firmware:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "33.011",
+ "versionEndExcluding": "33.015",
+ "matchCriteriaId": "209FB84C-5C5D-49D4-B7EF-24BCF8448CDD"
+ }
+ ]
+ },
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": false,
+ "criteria": "cpe:2.3:h:rockwellautomation:compactlogix_5480:-:*:*:*:*:*:*:*",
+ "matchCriteriaId": "80F4F5BE-07DF-402A-BF98-34FBA6A11968"
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "operator": "AND",
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:o:rockwellautomation:controllogix_5580_firmware:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "33.011",
+ "versionEndExcluding": "33.015",
+ "matchCriteriaId": "9C2411ED-FD7A-4A60-87EE-9B530050CCF1"
+ }
+ ]
+ },
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": false,
+ "criteria": "cpe:2.3:h:rockwellautomation:controllogix_5580:-:*:*:*:*:*:*:*",
+ "matchCriteriaId": "51BB883B-B863-4D57-B1C0-FC7B3EBD1EA0"
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "operator": "AND",
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:o:rockwellautomation:guardlogix_5580_firmware:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "33.011",
+ "versionEndExcluding": "33.015",
+ "matchCriteriaId": "D37F9CEA-510D-41EE-B999-F86AF481ACEC"
+ }
+ ]
+ },
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": false,
+ "criteria": "cpe:2.3:h:rockwellautomation:guardlogix_5580:-:*:*:*:*:*:*:*",
+ "matchCriteriaId": "006B7683-9FDF-4748-BA28-2EA22613E092"
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "operator": "AND",
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:o:rockwellautomation:1756-en4tr_firmware:3.002:*:*:*:*:*:*:*",
+ "matchCriteriaId": "6CF51B29-F0CF-44DC-819E-4DC700D82BA7"
+ }
+ ]
+ },
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": false,
+ "criteria": "cpe:2.3:h:rockwellautomation:1756-en4tr:-:*:*:*:*:*:*:*",
+ "matchCriteriaId": "898EE953-E0EF-4B52-8EA0-41AAD8B5CCF3"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://www.rockwellautomation.com/en-us/trust-center/security-advisories/advisory.SD1706.html",
- "source": "PSIRT@rockwellautomation.com"
+ "source": "PSIRT@rockwellautomation.com",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2024/CVE-2024-94xx/CVE-2024-9417.json b/CVE-2024/CVE-2024-94xx/CVE-2024-9417.json
index c1c08488ca0..fc1c8e30cd4 100644
--- a/CVE-2024/CVE-2024-94xx/CVE-2024-9417.json
+++ b/CVE-2024/CVE-2024-94xx/CVE-2024-9417.json
@@ -2,8 +2,8 @@
"id": "CVE-2024-9417",
"sourceIdentifier": "security@wordfence.com",
"published": "2024-10-05T10:15:02.957",
- "lastModified": "2024-10-07T17:48:28.117",
- "vulnStatus": "Awaiting Analysis",
+ "lastModified": "2025-02-27T19:30:33.180",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -51,22 +51,52 @@
]
}
],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:hashthemes:hash_form:*:*:*:*:*:wordpress:*:*",
+ "versionEndExcluding": "1.2.0",
+ "matchCriteriaId": "5279A5E2-D8E3-434E-831F-995426909E9C"
+ }
+ ]
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://plugins.trac.wordpress.org/browser/hash-form/trunk/admin/classes/HashFormUploader.php#L107",
- "source": "security@wordfence.com"
+ "source": "security@wordfence.com",
+ "tags": [
+ "Product"
+ ]
},
{
"url": "https://plugins.trac.wordpress.org/browser/hash-form/trunk/admin/classes/HashFormUploader.php#L135",
- "source": "security@wordfence.com"
+ "source": "security@wordfence.com",
+ "tags": [
+ "Product"
+ ]
},
{
"url": "https://plugins.trac.wordpress.org/changeset/3161828/",
- "source": "security@wordfence.com"
+ "source": "security@wordfence.com",
+ "tags": [
+ "Patch"
+ ]
},
{
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/cad7731a-1f81-4055-9b49-15b35edd3fcf?source=cve",
- "source": "security@wordfence.com"
+ "source": "security@wordfence.com",
+ "tags": [
+ "Third Party Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-07xx/CVE-2025-0767.json b/CVE-2025/CVE-2025-07xx/CVE-2025-0767.json
new file mode 100644
index 00000000000..97a7f6f4409
--- /dev/null
+++ b/CVE-2025/CVE-2025-07xx/CVE-2025-0767.json
@@ -0,0 +1,82 @@
+{
+ "id": "CVE-2025-0767",
+ "sourceIdentifier": "help@fluidattacks.com",
+ "published": "2025-02-27T19:15:49.350",
+ "lastModified": "2025-02-27T19:15:49.350",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "WP Activity Log 5.3.2 was found to be vulnerable. Unvalidated user input is used directly in an unserialize function in myapp/classes/Writers/class-csv-writer.php."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV40": [
+ {
+ "source": "help@fluidattacks.com",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "4.0",
+ "vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
+ "baseScore": 6.3,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "HIGH",
+ "attackRequirements": "NONE",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "vulnConfidentialityImpact": "NONE",
+ "vulnIntegrityImpact": "LOW",
+ "vulnAvailabilityImpact": "LOW",
+ "subConfidentialityImpact": "NONE",
+ "subIntegrityImpact": "NONE",
+ "subAvailabilityImpact": "NONE",
+ "exploitMaturity": "NOT_DEFINED",
+ "confidentialityRequirement": "NOT_DEFINED",
+ "integrityRequirement": "NOT_DEFINED",
+ "availabilityRequirement": "NOT_DEFINED",
+ "modifiedAttackVector": "NOT_DEFINED",
+ "modifiedAttackComplexity": "NOT_DEFINED",
+ "modifiedAttackRequirements": "NOT_DEFINED",
+ "modifiedPrivilegesRequired": "NOT_DEFINED",
+ "modifiedUserInteraction": "NOT_DEFINED",
+ "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
+ "modifiedVulnIntegrityImpact": "NOT_DEFINED",
+ "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
+ "modifiedSubConfidentialityImpact": "NOT_DEFINED",
+ "modifiedSubIntegrityImpact": "NOT_DEFINED",
+ "modifiedSubAvailabilityImpact": "NOT_DEFINED",
+ "Safety": "NOT_DEFINED",
+ "Automatable": "NOT_DEFINED",
+ "Recovery": "NOT_DEFINED",
+ "valueDensity": "NOT_DEFINED",
+ "vulnerabilityResponseEffort": "NOT_DEFINED",
+ "providerUrgency": "NOT_DEFINED"
+ }
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "help@fluidattacks.com",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-502"
+ }
+ ]
+ }
+ ],
+ "references": [
+ {
+ "url": "https://co.wordpress.org/plugins/wp-security-audit-log/",
+ "source": "help@fluidattacks.com"
+ },
+ {
+ "url": "https://fluidattacks.com/advisories/skims-9/",
+ "source": "help@fluidattacks.com"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21714.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21714.json
index 2bf296405c3..71ff9ea37d0 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21714.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21714.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21714",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T02:15:15.050",
- "lastModified": "2025-02-27T02:15:15.050",
+ "lastModified": "2025-02-27T19:15:49.637",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix implicit ODP use after free\n\nPrevent double queueing of implicit ODP mr destroy work by using\n__xa_cmpxchg() to make sure this is the only time we are destroying this\nspecific mr.\n\nWithout this change, we could try to invalidate this mr twice, which in\nturn could result in queuing a MR work destroy twice, and eventually the\nsecond work could execute after the MR was freed due to the first work,\ncausing a user after free and trace below.\n\n refcount_t: underflow; use-after-free.\n WARNING: CPU: 2 PID: 12178 at lib/refcount.c:28 refcount_warn_saturate+0x12b/0x130\n Modules linked in: bonding ib_ipoib vfio_pci ip_gre geneve nf_tables ip6_gre gre ip6_tunnel tunnel6 ipip tunnel4 ib_umad rdma_ucm mlx5_vfio_pci vfio_pci_core vfio_iommu_type1 mlx5_ib vfio ib_uverbs mlx5_core iptable_raw openvswitch nsh rpcrdma ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_cm ib_core xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay zram zsmalloc fuse [last unloaded: ib_uverbs]\n CPU: 2 PID: 12178 Comm: kworker/u20:5 Not tainted 6.5.0-rc1_net_next_mlx5_58c644e #1\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n Workqueue: events_unbound free_implicit_child_mr_work [mlx5_ib]\n RIP: 0010:refcount_warn_saturate+0x12b/0x130\n Code: 48 c7 c7 38 95 2a 82 c6 05 bc c6 fe 00 01 e8 0c 66 aa ff 0f 0b 5b c3 48 c7 c7 e0 94 2a 82 c6 05 a7 c6 fe 00 01 e8 f5 65 aa ff <0f> 0b 5b c3 90 8b 07 3d 00 00 00 c0 74 12 83 f8 01 74 13 8d 50 ff\n RSP: 0018:ffff8881008e3e40 EFLAGS: 00010286\n RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027\n RDX: ffff88852c91b5c8 RSI: 0000000000000001 RDI: ffff88852c91b5c0\n RBP: ffff8881dacd4e00 R08: 00000000ffffffff R09: 0000000000000019\n R10: 000000000000072e R11: 0000000063666572 R12: ffff88812bfd9e00\n R13: ffff8881c792d200 R14: ffff88810011c005 R15: ffff8881002099c0\n FS: 0000000000000000(0000) GS:ffff88852c900000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f5694b5e000 CR3: 00000001153f6003 CR4: 0000000000370ea0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n Call Trace:\n \n ? refcount_warn_saturate+0x12b/0x130\n free_implicit_child_mr_work+0x180/0x1b0 [mlx5_ib]\n process_one_work+0x1cc/0x3c0\n worker_thread+0x218/0x3c0\n kthread+0xc6/0xf0\n ret_from_fork+0x1f/0x30\n "
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/7cc8f681f6d4ae4478ae0f60485fc768f2b450da",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21722.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21722.json
index 18c1ea36394..2d4b2779301 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21722.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21722.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21722",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T02:15:15.883",
- "lastModified": "2025-02-27T02:15:15.883",
+ "lastModified": "2025-02-27T19:15:49.780",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: do not force clear folio if buffer is referenced\n\nPatch series \"nilfs2: protect busy buffer heads from being force-cleared\".\n\nThis series fixes the buffer head state inconsistency issues reported by\nsyzbot that occurs when the filesystem is corrupted and falls back to\nread-only, and the associated buffer head use-after-free issue.\n\n\nThis patch (of 2):\n\nSyzbot has reported that after nilfs2 detects filesystem corruption and\nfalls back to read-only, inconsistencies in the buffer state may occur.\n\nOne of the inconsistencies is that when nilfs2 calls mark_buffer_dirty()\nto set a data or metadata buffer as dirty, but it detects that the buffer\nis not in the uptodate state:\n\n WARNING: CPU: 0 PID: 6049 at fs/buffer.c:1177 mark_buffer_dirty+0x2e5/0x520\n fs/buffer.c:1177\n ...\n Call Trace:\n \n nilfs_palloc_commit_alloc_entry+0x4b/0x160 fs/nilfs2/alloc.c:598\n nilfs_ifile_create_inode+0x1dd/0x3a0 fs/nilfs2/ifile.c:73\n nilfs_new_inode+0x254/0x830 fs/nilfs2/inode.c:344\n nilfs_mkdir+0x10d/0x340 fs/nilfs2/namei.c:218\n vfs_mkdir+0x2f9/0x4f0 fs/namei.c:4257\n do_mkdirat+0x264/0x3a0 fs/namei.c:4280\n __do_sys_mkdirat fs/namei.c:4295 [inline]\n __se_sys_mkdirat fs/namei.c:4293 [inline]\n __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4293\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe other is when nilfs_btree_propagate(), which propagates the dirty\nstate to the ancestor nodes of a b-tree that point to a dirty buffer,\ndetects that the origin buffer is not dirty, even though it should be:\n\n WARNING: CPU: 0 PID: 5245 at fs/nilfs2/btree.c:2089\n nilfs_btree_propagate+0xc79/0xdf0 fs/nilfs2/btree.c:2089\n ...\n Call Trace:\n \n nilfs_bmap_propagate+0x75/0x120 fs/nilfs2/bmap.c:345\n nilfs_collect_file_data+0x4d/0xd0 fs/nilfs2/segment.c:587\n nilfs_segctor_apply_buffers+0x184/0x340 fs/nilfs2/segment.c:1006\n nilfs_segctor_scan_file+0x28c/0xa50 fs/nilfs2/segment.c:1045\n nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1216 [inline]\n nilfs_segctor_collect fs/nilfs2/segment.c:1540 [inline]\n nilfs_segctor_do_construct+0x1c28/0x6b90 fs/nilfs2/segment.c:2115\n nilfs_segctor_construct+0x181/0x6b0 fs/nilfs2/segment.c:2479\n nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline]\n nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701\n kthread+0x2f0/0x390 kernel/kthread.c:389\n ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n \n\nBoth of these issues are caused by the callbacks that handle the\npage/folio write requests, forcibly clear various states, including the\nworking state of the buffers they hold, at unexpected times when they\ndetect read-only fallback.\n\nFix these issues by checking if the buffer is referenced before clearing\nthe page/folio state, and skipping the clear if it is."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/1098bb8d52419d262a3358d099a1598a920b730f",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21729.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21729.json
index 4726936626e..42b0595fc06 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21729.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21729.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21729",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T02:15:16.637",
- "lastModified": "2025-02-27T02:15:16.637",
+ "lastModified": "2025-02-27T19:15:49.920",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw89: fix race between cancel_hw_scan and hw_scan completion\n\nThe rtwdev->scanning flag isn't protected by mutex originally, so\ncancel_hw_scan can pass the condition, but suddenly hw_scan completion\nunset the flag and calls ieee80211_scan_completed() that will free\nlocal->hw_scan_req. Then, cancel_hw_scan raises null-ptr-deref and\nuse-after-free. Fix it by moving the check condition to where\nprotected by mutex.\n\n KASAN: null-ptr-deref in range [0x0000000000000088-0x000000000000008f]\n CPU: 2 PID: 6922 Comm: kworker/2:2 Tainted: G OE\n Hardware name: LENOVO 2356AD1/2356AD1, BIOS G7ETB6WW (2.76 ) 09/10/2019\n Workqueue: events cfg80211_conn_work [cfg80211]\n RIP: 0010:rtw89_fw_h2c_scan_offload_be+0xc33/0x13c3 [rtw89_core]\n Code: 00 45 89 6c 24 1c 0f 85 23 01 00 00 48 8b 85 20 ff ff ff 48 8d\n RSP: 0018:ffff88811fd9f068 EFLAGS: 00010206\n RAX: dffffc0000000000 RBX: ffff88811fd9f258 RCX: 0000000000000001\n RDX: 0000000000000011 RSI: 0000000000000001 RDI: 0000000000000089\n RBP: ffff88811fd9f170 R08: 0000000000000000 R09: 0000000000000000\n R10: ffff88811fd9f108 R11: 0000000000000000 R12: ffff88810e47f960\n R13: 0000000000000000 R14: 000000000000ffff R15: 0000000000000000\n FS: 0000000000000000(0000) GS:ffff8881d6f00000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007531dfca55b0 CR3: 00000001be296004 CR4: 00000000001706e0\n Call Trace:\n \n ? show_regs+0x61/0x73\n ? __die_body+0x20/0x73\n ? die_addr+0x4f/0x7b\n ? exc_general_protection+0x191/0x1db\n ? asm_exc_general_protection+0x27/0x30\n ? rtw89_fw_h2c_scan_offload_be+0xc33/0x13c3 [rtw89_core]\n ? rtw89_fw_h2c_scan_offload_be+0x458/0x13c3 [rtw89_core]\n ? __pfx_rtw89_fw_h2c_scan_offload_be+0x10/0x10 [rtw89_core]\n ? do_raw_spin_lock+0x75/0xdb\n ? __pfx_do_raw_spin_lock+0x10/0x10\n rtw89_hw_scan_offload+0xb5e/0xbf7 [rtw89_core]\n ? _raw_spin_unlock+0xe/0x24\n ? __mutex_lock.constprop.0+0x40c/0x471\n ? __pfx_rtw89_hw_scan_offload+0x10/0x10 [rtw89_core]\n ? __mutex_lock_slowpath+0x13/0x1f\n ? mutex_lock+0xa2/0xdc\n ? __pfx_mutex_lock+0x10/0x10\n rtw89_hw_scan_abort+0x58/0xb7 [rtw89_core]\n rtw89_ops_cancel_hw_scan+0x120/0x13b [rtw89_core]\n ieee80211_scan_cancel+0x468/0x4d0 [mac80211]\n ieee80211_prep_connection+0x858/0x899 [mac80211]\n ieee80211_mgd_auth+0xbea/0xdde [mac80211]\n ? __pfx_ieee80211_mgd_auth+0x10/0x10 [mac80211]\n ? cfg80211_find_elem+0x15/0x29 [cfg80211]\n ? is_bss+0x1b7/0x1d7 [cfg80211]\n ieee80211_auth+0x18/0x27 [mac80211]\n cfg80211_mlme_auth+0x3bb/0x3e7 [cfg80211]\n cfg80211_conn_do_work+0x410/0xb81 [cfg80211]\n ? __pfx_cfg80211_conn_do_work+0x10/0x10 [cfg80211]\n ? __kasan_check_read+0x11/0x1f\n ? psi_group_change+0x8bc/0x944\n ? __kasan_check_write+0x14/0x22\n ? mutex_lock+0x8e/0xdc\n ? __pfx_mutex_lock+0x10/0x10\n ? __pfx___radix_tree_lookup+0x10/0x10\n cfg80211_conn_work+0x245/0x34d [cfg80211]\n ? __pfx_cfg80211_conn_work+0x10/0x10 [cfg80211]\n ? update_cfs_rq_load_avg+0x3bc/0x3d7\n ? sched_clock_noinstr+0x9/0x1a\n ? sched_clock+0x10/0x24\n ? sched_clock_cpu+0x7e/0x42e\n ? newidle_balance+0x796/0x937\n ? __pfx_sched_clock_cpu+0x10/0x10\n ? __pfx_newidle_balance+0x10/0x10\n ? __kasan_check_read+0x11/0x1f\n ? psi_group_change+0x8bc/0x944\n ? _raw_spin_unlock+0xe/0x24\n ? raw_spin_rq_unlock+0x47/0x54\n ? raw_spin_rq_unlock_irq+0x9/0x1f\n ? finish_task_switch.isra.0+0x347/0x586\n ? __schedule+0x27bf/0x2892\n ? mutex_unlock+0x80/0xd0\n ? do_raw_spin_lock+0x75/0xdb\n ? __pfx___schedule+0x10/0x10\n process_scheduled_works+0x58c/0x821\n worker_thread+0x4c7/0x586\n ? __kasan_check_read+0x11/0x1f\n kthread+0x285/0x294\n ? __pfx_worker_thread+0x10/0x10\n ? __pfx_kthread+0x10/0x10\n ret_from_fork+0x29/0x6f\n ? __pfx_kthread+0x10/0x10\n ret_from_fork_asm+0x1b/0x30\n "
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/2403cb3c235d5e339b580cc3a825493769fadca8",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21739.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21739.json
index 134beaa2c52..2541280a47a 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21739.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21739.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21739",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T03:15:14.530",
- "lastModified": "2025-02-27T03:15:14.530",
+ "lastModified": "2025-02-27T19:15:50.067",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: core: Fix use-after free in init error and remove paths\n\ndevm_blk_crypto_profile_init() registers a cleanup handler to run when\nthe associated (platform-) device is being released. For UFS, the\ncrypto private data and pointers are stored as part of the ufs_hba's\ndata structure 'struct ufs_hba::crypto_profile'. This structure is\nallocated as part of the underlying ufshcd and therefore Scsi_host\nallocation.\n\nDuring driver release or during error handling in ufshcd_pltfrm_init(),\nthis structure is released as part of ufshcd_dealloc_host() before the\n(platform-) device associated with the crypto call above is released.\nOnce this device is released, the crypto cleanup code will run, using\nthe just-released 'struct ufs_hba::crypto_profile'. This causes a\nuse-after-free situation:\n\n Call trace:\n kfree+0x60/0x2d8 (P)\n kvfree+0x44/0x60\n blk_crypto_profile_destroy_callback+0x28/0x70\n devm_action_release+0x1c/0x30\n release_nodes+0x6c/0x108\n devres_release_all+0x98/0x100\n device_unbind_cleanup+0x20/0x70\n really_probe+0x218/0x2d0\n\nIn other words, the initialisation code flow is:\n\n platform-device probe\n ufshcd_pltfrm_init()\n ufshcd_alloc_host()\n scsi_host_alloc()\n allocation of struct ufs_hba\n creation of scsi-host devices\n devm_blk_crypto_profile_init()\n devm registration of cleanup handler using platform-device\n\nand during error handling of ufshcd_pltfrm_init() or during driver\nremoval:\n\n ufshcd_dealloc_host()\n scsi_host_put()\n put_device(scsi-host)\n release of struct ufs_hba\n put_device(platform-device)\n crypto cleanup handler\n\nTo fix this use-after free, change ufshcd_alloc_host() to register a\ndevres action to automatically cleanup the underlying SCSI device on\nufshcd destruction, without requiring explicit calls to\nufshcd_dealloc_host(). This way:\n\n * the crypto profile and all other ufs_hba-owned resources are\n destroyed before SCSI (as they've been registered after)\n * a memleak is plugged in tc-dwc-g210-pci.c remove() as a\n side-effect\n * EXPORT_SYMBOL_GPL(ufshcd_dealloc_host) can be removed fully as\n it's not needed anymore\n * no future drivers using ufshcd_alloc_host() could ever forget\n adding the cleanup"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/0c77c0d754fe83cb154715fcfec6c3faef94f207",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21751.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21751.json
index e7b8deef366..7808a976466 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21751.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21751.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21751",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T03:15:15.760",
- "lastModified": "2025-02-27T03:15:15.760",
+ "lastModified": "2025-02-27T19:15:50.220",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: HWS, change error flow on matcher disconnect\n\nCurrently, when firmware failure occurs during matcher disconnect flow,\nthe error flow of the function reconnects the matcher back and returns\nan error, which continues running the calling function and eventually\nfrees the matcher that is being disconnected.\nThis leads to a case where we have a freed matcher on the matchers list,\nwhich in turn leads to use-after-free and eventual crash.\n\nThis patch fixes that by not trying to reconnect the matcher back when\nsome FW command fails during disconnect.\n\nNote that we're dealing here with FW error. We can't overcome this\nproblem. This might lead to bad steering state (e.g. wrong connection\nbetween matchers), and will also lead to resource leakage, as it is\nthe case with any other error handling during resource destruction.\n\nHowever, the goal here is to allow the driver to continue and not crash\nthe machine with use-after-free error."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/1ce840c7a659aa53a31ef49f0271b4fd0dc10296",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21753.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21753.json
index ae0c1d3452b..3c1a684048d 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21753.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21753.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21753",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T03:15:15.950",
- "lastModified": "2025-02-27T03:15:15.950",
+ "lastModified": "2025-02-27T19:15:50.360",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix use-after-free when attempting to join an aborted transaction\n\nWhen we are trying to join the current transaction and if it's aborted,\nwe read its 'aborted' field after unlocking fs_info->trans_lock and\nwithout holding any extra reference count on it. This means that a\nconcurrent task that is aborting the transaction may free the transaction\nbefore we read its 'aborted' field, leading to a use-after-free.\n\nFix this by reading the 'aborted' field while holding fs_info->trans_lock\nsince any freeing task must first acquire that lock and set\nfs_info->running_transaction to NULL before freeing the transaction.\n\nThis was reported by syzbot and Dmitry with the following stack traces\nfrom KASAN:\n\n ==================================================================\n BUG: KASAN: slab-use-after-free in join_transaction+0xd9b/0xda0 fs/btrfs/transaction.c:278\n Read of size 4 at addr ffff888011839024 by task kworker/u4:9/1128\n\n CPU: 0 UID: 0 PID: 1128 Comm: kworker/u4:9 Not tainted 6.13.0-rc7-syzkaller-00019-gc45323b7560e #0\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\n Workqueue: events_unbound btrfs_async_reclaim_data_space\n Call Trace:\n \n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0x169/0x550 mm/kasan/report.c:489\n kasan_report+0x143/0x180 mm/kasan/report.c:602\n join_transaction+0xd9b/0xda0 fs/btrfs/transaction.c:278\n start_transaction+0xaf8/0x1670 fs/btrfs/transaction.c:697\n flush_space+0x448/0xcf0 fs/btrfs/space-info.c:803\n btrfs_async_reclaim_data_space+0x159/0x510 fs/btrfs/space-info.c:1321\n process_one_work kernel/workqueue.c:3236 [inline]\n process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3317\n worker_thread+0x870/0xd30 kernel/workqueue.c:3398\n kthread+0x2f0/0x390 kernel/kthread.c:389\n ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n \n\n Allocated by task 5315:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3f/0x80 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:377 [inline]\n __kasan_kmalloc+0x98/0xb0 mm/kasan/common.c:394\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __kmalloc_cache_noprof+0x243/0x390 mm/slub.c:4329\n kmalloc_noprof include/linux/slab.h:901 [inline]\n join_transaction+0x144/0xda0 fs/btrfs/transaction.c:308\n start_transaction+0xaf8/0x1670 fs/btrfs/transaction.c:697\n btrfs_create_common+0x1b2/0x2e0 fs/btrfs/inode.c:6572\n lookup_open fs/namei.c:3649 [inline]\n open_last_lookups fs/namei.c:3748 [inline]\n path_openat+0x1c03/0x3590 fs/namei.c:3984\n do_filp_open+0x27f/0x4e0 fs/namei.c:4014\n do_sys_openat2+0x13e/0x1d0 fs/open.c:1402\n do_sys_open fs/open.c:1417 [inline]\n __do_sys_creat fs/open.c:1495 [inline]\n __se_sys_creat fs/open.c:1489 [inline]\n __x64_sys_creat+0x123/0x170 fs/open.c:1489\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n Freed by task 5336:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3f/0x80 mm/kasan/common.c:68\n kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:582\n poison_slab_object mm/kasan/common.c:247 [inline]\n __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264\n kasan_slab_free include/linux/kasan.h:233 [inline]\n slab_free_hook mm/slub.c:2353 [inline]\n slab_free mm/slub.c:4613 [inline]\n kfree+0x196/0x430 mm/slub.c:4761\n cleanup_transaction fs/btrfs/transaction.c:2063 [inline]\n btrfs_commit_transaction+0x2c97/0x3720 fs/btrfs/transaction.c:2598\n insert_balance_item+0x1284/0x20b0 fs/btrfs/volumes.c:3757\n btrfs_balance+0x992/\n---truncated---"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/6ba4663ada6c6315af23a6669d386146634808ec",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21756.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21756.json
index 17ab1550018..a100b56fda6 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21756.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21756.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21756",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T03:15:16.250",
- "lastModified": "2025-02-27T03:15:16.250",
+ "lastModified": "2025-02-27T19:15:50.513",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Keep the binding until socket destruction\n\nPreserve sockets bindings; this includes both resulting from an explicit\nbind() and those implicitly bound through autobind during connect().\n\nPrevents socket unbinding during a transport reassignment, which fixes a\nuse-after-free:\n\n 1. vsock_create() (refcnt=1) calls vsock_insert_unbound() (refcnt=2)\n 2. transport->release() calls vsock_remove_bound() without checking if\n sk was bound and moved to bound list (refcnt=1)\n 3. vsock_bind() assumes sk is in unbound list and before\n __vsock_insert_bound(vsock_bound_sockets()) calls\n __vsock_remove_bound() which does:\n list_del_init(&vsk->bound_table); // nop\n sock_put(&vsk->sk); // refcnt=0\n\nBUG: KASAN: slab-use-after-free in __vsock_bind+0x62e/0x730\nRead of size 4 at addr ffff88816b46a74c by task a.out/2057\n dump_stack_lvl+0x68/0x90\n print_report+0x174/0x4f6\n kasan_report+0xb9/0x190\n __vsock_bind+0x62e/0x730\n vsock_bind+0x97/0xe0\n __sys_bind+0x154/0x1f0\n __x64_sys_bind+0x6e/0xb0\n do_syscall_64+0x93/0x1b0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nAllocated by task 2057:\n kasan_save_stack+0x1e/0x40\n kasan_save_track+0x10/0x30\n __kasan_slab_alloc+0x85/0x90\n kmem_cache_alloc_noprof+0x131/0x450\n sk_prot_alloc+0x5b/0x220\n sk_alloc+0x2c/0x870\n __vsock_create.constprop.0+0x2e/0xb60\n vsock_create+0xe4/0x420\n __sock_create+0x241/0x650\n __sys_socket+0xf2/0x1a0\n __x64_sys_socket+0x6e/0xb0\n do_syscall_64+0x93/0x1b0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nFreed by task 2057:\n kasan_save_stack+0x1e/0x40\n kasan_save_track+0x10/0x30\n kasan_save_free_info+0x37/0x60\n __kasan_slab_free+0x4b/0x70\n kmem_cache_free+0x1a1/0x590\n __sk_destruct+0x388/0x5a0\n __vsock_bind+0x5e1/0x730\n vsock_bind+0x97/0xe0\n __sys_bind+0x154/0x1f0\n __x64_sys_bind+0x6e/0xb0\n do_syscall_64+0x93/0x1b0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nrefcount_t: addition on 0; use-after-free.\nWARNING: CPU: 7 PID: 2057 at lib/refcount.c:25 refcount_warn_saturate+0xce/0x150\nRIP: 0010:refcount_warn_saturate+0xce/0x150\n __vsock_bind+0x66d/0x730\n vsock_bind+0x97/0xe0\n __sys_bind+0x154/0x1f0\n __x64_sys_bind+0x6e/0xb0\n do_syscall_64+0x93/0x1b0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 7 PID: 2057 at lib/refcount.c:28 refcount_warn_saturate+0xee/0x150\nRIP: 0010:refcount_warn_saturate+0xee/0x150\n vsock_remove_bound+0x187/0x1e0\n __vsock_release+0x383/0x4a0\n vsock_release+0x90/0x120\n __sock_release+0xa3/0x250\n sock_close+0x14/0x20\n __fput+0x359/0xa80\n task_work_run+0x107/0x1d0\n do_exit+0x847/0x2560\n do_group_exit+0xb8/0x250\n __x64_sys_exit_group+0x3a/0x50\n x64_sys_call+0xfec/0x14f0\n do_syscall_64+0x93/0x1b0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e"
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/3f43540166128951cc1be7ab1ce6b7f05c670d8b",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21786.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21786.json
index 020e5631da0..d160a4250d2 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21786.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21786.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21786",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T03:15:19.450",
- "lastModified": "2025-02-27T03:15:19.450",
+ "lastModified": "2025-02-27T19:15:50.660",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nworkqueue: Put the pwq after detaching the rescuer from the pool\n\nThe commit 68f83057b913(\"workqueue: Reap workers via kthread_stop() and\nremove detach_completion\") adds code to reap the normal workers but\nmistakenly does not handle the rescuer and also removes the code waiting\nfor the rescuer in put_unbound_pool(), which caused a use-after-free bug\nreported by Cheung Wall.\n\nTo avoid the use-after-free bug, the pool\u2019s reference must be held until\nthe detachment is complete. Therefore, move the code that puts the pwq\nafter detaching the rescuer from the pool."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/835b69c868f53f959d4986bbecd561ba6f38e492",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21797.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21797.json
index 3e46d256865..dcf3ede49bf 100644
--- a/CVE-2025/CVE-2025-217xx/CVE-2025-21797.json
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21797.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-21797",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-02-27T03:15:20.607",
- "lastModified": "2025-02-27T03:15:20.607",
+ "lastModified": "2025-02-27T19:15:50.807",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: corsair-void: Add missing delayed work cancel for headset status\n\nThe cancel_delayed_work_sync() call was missed, causing a use-after-free\nin corsair_void_remove()."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
+ "baseScore": 7.8,
+ "baseSeverity": "HIGH",
+ "attackVector": "LOCAL",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.8,
+ "impactScore": 5.9
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-416"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://git.kernel.org/stable/c/2dcb56a0a4da6946f6c18288da595c13e0d2af86",
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21798.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21798.json
new file mode 100644
index 00000000000..3306bdf9793
--- /dev/null
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21798.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21798",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.477",
+ "lastModified": "2025-02-27T20:16:02.477",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfirewire: test: Fix potential null dereference in firewire kunit test\n\nkunit_kzalloc() may return a NULL pointer, dereferencing it without\nNULL check may lead to NULL dereference.\nAdd a NULL check for test_state."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/352fafe97784e81a10a7c74bd508f71a19b53c2a",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/70fcb25472d90dd3b87cbee74b9eb68670b0c7b8",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/c6896bf4c611c3dd126f3e03685f2360a18b3d6f",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-217xx/CVE-2025-21799.json b/CVE-2025/CVE-2025-217xx/CVE-2025-21799.json
new file mode 100644
index 00000000000..e26545c6674
--- /dev/null
+++ b/CVE-2025/CVE-2025-217xx/CVE-2025-21799.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21799",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.563",
+ "lastModified": "2025-02-27T20:16:02.563",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethernet: ti: am65-cpsw: fix freeing IRQ in am65_cpsw_nuss_remove_tx_chns()\n\nWhen getting the IRQ we use k3_udma_glue_tx_get_irq() which returns\nnegative error value on error. So not NULL check is not sufficient\nto deteremine if IRQ is valid. Check that IRQ is greater then zero\nto ensure it is valid.\n\nThere is no issue at probe time but at runtime user can invoke\n.set_channels which results in the following call chain.\nam65_cpsw_set_channels()\n am65_cpsw_nuss_update_tx_rx_chns()\n am65_cpsw_nuss_remove_tx_chns()\n am65_cpsw_nuss_init_tx_chns()\n\nAt this point if am65_cpsw_nuss_init_tx_chns() fails due to\nk3_udma_glue_tx_get_irq() then tx_chn->irq will be set to a\nnegative value.\n\nThen, at subsequent .set_channels with higher channel count we\nwill attempt to free an invalid IRQ in am65_cpsw_nuss_remove_tx_chns()\nleading to a kernel warning.\n\nThe issue is present in the original commit that introduced this driver,\nalthough there, am65_cpsw_nuss_update_tx_rx_chns() existed as\nam65_cpsw_nuss_update_tx_chns()."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/4395a44acb15850e492dd1de9ec4b6479d96bc80",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8448c87b3af68bebca21e3136913f7f77e363515",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/88fd5db8c0073bd91d18391feb5741aeb0a2b475",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8aae91ae1c65782a169ec070e023d4d269e5d6e6",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/aea5cca681d268f794fa2385f9ec26a5cce025cd",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21800.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21800.json
new file mode 100644
index 00000000000..ef6b0505ec7
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21800.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21800",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.660",
+ "lastModified": "2025-02-27T20:16:02.660",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: HWS, fix definer's HWS_SET32 macro for negative offset\n\nWhen bit offset for HWS_SET32 macro is negative,\nUBSAN complains about the shift-out-of-bounds:\n\n UBSAN: shift-out-of-bounds in\n drivers/net/ethernet/mellanox/mlx5/core/steering/hws/definer.c:177:2\n shift exponent -8 is negative"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/69c676c0ded472713e6d1b3a456b3c4f52f66f0e",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/92cff996624c4757d5bbace3dfa3f1567ba94143",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/be482f1d10da781db9445d2753c1e3f1fd82babf",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21801.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21801.json
new file mode 100644
index 00000000000..fcb17b41679
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21801.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21801",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.753",
+ "lastModified": "2025-02-27T20:16:02.753",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ravb: Fix missing rtnl lock in suspend/resume path\n\nFix the suspend/resume path by ensuring the rtnl lock is held where\nrequired. Calls to ravb_open, ravb_close and wol operations must be\nperformed under the rtnl lock to prevent conflicts with ongoing ndo\noperations.\n\nWithout this fix, the following warning is triggered:\n[ 39.032969] =============================\n[ 39.032983] WARNING: suspicious RCU usage\n[ 39.033019] -----------------------------\n[ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious\nrcu_dereference_protected() usage!\n...\n[ 39.033597] stack backtrace:\n[ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted\n6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7\n[ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on\nr9a08g045s33 (DT)\n[ 39.033628] Call trace:\n[ 39.033633] show_stack+0x14/0x1c (C)\n[ 39.033652] dump_stack_lvl+0xb4/0xc4\n[ 39.033664] dump_stack+0x14/0x1c\n[ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c\n[ 39.033682] phy_detach+0x160/0x190\n[ 39.033694] phy_disconnect+0x40/0x54\n[ 39.033703] ravb_close+0x6c/0x1cc\n[ 39.033714] ravb_suspend+0x48/0x120\n[ 39.033721] dpm_run_callback+0x4c/0x14c\n[ 39.033731] device_suspend+0x11c/0x4dc\n[ 39.033740] dpm_suspend+0xdc/0x214\n[ 39.033748] dpm_suspend_start+0x48/0x60\n[ 39.033758] suspend_devices_and_enter+0x124/0x574\n[ 39.033769] pm_suspend+0x1ac/0x274\n[ 39.033778] state_store+0x88/0x124\n[ 39.033788] kobj_attr_store+0x14/0x24\n[ 39.033798] sysfs_kf_write+0x48/0x6c\n[ 39.033808] kernfs_fop_write_iter+0x118/0x1a8\n[ 39.033817] vfs_write+0x27c/0x378\n[ 39.033825] ksys_write+0x64/0xf4\n[ 39.033833] __arm64_sys_write+0x18/0x20\n[ 39.033841] invoke_syscall+0x44/0x104\n[ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4\n[ 39.033862] do_el0_svc+0x18/0x20\n[ 39.033870] el0_svc+0x3c/0xf0\n[ 39.033880] el0t_64_sync_handler+0xc0/0xc4\n[ 39.033888] el0t_64_sync+0x154/0x158\n[ 39.041274] ravb 11c30000.ethernet eth0: Link is Down"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/0296981941cf291edfbc318d3255a93439f368e4",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/2c2ebb2b49573e5f8726112ad06b1dffc3c9ea03",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/ad19522c007bb24ed874468f8baa1503c4662cf4",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21802.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21802.json
new file mode 100644
index 00000000000..b0a3f653422
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21802.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21802",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.847",
+ "lastModified": "2025-02-27T20:16:02.847",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: fix oops when unload drivers paralleling\n\nWhen unload hclge driver, it tries to disable sriov first for each\nae_dev node from hnae3_ae_dev_list. If user unloads hns3 driver at\nthe time, because it removes all the ae_dev nodes, and it may cause\noops.\n\nBut we can't simply use hnae3_common_lock for this. Because in the\nprocess flow of pci_disable_sriov(), it will trigger the remove flow\nof VF, which will also take hnae3_common_lock.\n\nTo fixes it, introduce a new mutex to protect the unload process."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/82736bb83fb0221319c85c2e9917d0189cd84e1e",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/92e5995773774a3e70257e9c95ea03518268bea5",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/b5a8bc47aa0a4aa8bca5466dfa2d12dbb5b3cd0c",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/cafe9a27e22736d4a01b3933e36225f9857c7988",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/e876522659012ef2e73834a0b9f1cbe3f74d5fad",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21803.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21803.json
new file mode 100644
index 00000000000..dd4342ffee9
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21803.json
@@ -0,0 +1,33 @@
+{
+ "id": "CVE-2025-21803",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:02.937",
+ "lastModified": "2025-02-27T20:16:02.937",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Fix warnings during S3 suspend\n\nThe enable_gpe_wakeup() function calls acpi_enable_all_wakeup_gpes(),\nand the later one may call the preempt_schedule_common() function,\nresulting in a thread switch and causing the CPU to be in an interrupt\nenabled state after the enable_gpe_wakeup() function returns, leading\nto the warnings as follow.\n\n[ C0] WARNING: ... at kernel/time/timekeeping.c:845 ktime_get+0xbc/0xc8\n[ C0] ...\n[ C0] Call Trace:\n[ C0] [<90000000002243b4>] show_stack+0x64/0x188\n[ C0] [<900000000164673c>] dump_stack_lvl+0x60/0x88\n[ C0] [<90000000002687e4>] __warn+0x8c/0x148\n[ C0] [<90000000015e9978>] report_bug+0x1c0/0x2b0\n[ C0] [<90000000016478e4>] do_bp+0x204/0x3b8\n[ C0] [<90000000025b1924>] exception_handlers+0x1924/0x10000\n[ C0] [<9000000000343bbc>] ktime_get+0xbc/0xc8\n[ C0] [<9000000000354c08>] tick_sched_timer+0x30/0xb0\n[ C0] [<90000000003408e0>] __hrtimer_run_queues+0x160/0x378\n[ C0] [<9000000000341f14>] hrtimer_interrupt+0x144/0x388\n[ C0] [<9000000000228348>] constant_timer_interrupt+0x38/0x48\n[ C0] [<90000000002feba4>] __handle_irq_event_percpu+0x64/0x1e8\n[ C0] [<90000000002fed48>] handle_irq_event_percpu+0x20/0x80\n[ C0] [<9000000000306b9c>] handle_percpu_irq+0x5c/0x98\n[ C0] [<90000000002fd4a0>] generic_handle_domain_irq+0x30/0x48\n[ C0] [<9000000000d0c7b0>] handle_cpu_irq+0x70/0xa8\n[ C0] [<9000000001646b30>] handle_loongarch_irq+0x30/0x48\n[ C0] [<9000000001646bc8>] do_vint+0x80/0xe0\n[ C0] [<90000000002aea1c>] finish_task_switch.isra.0+0x8c/0x2a8\n[ C0] [<900000000164e34c>] __schedule+0x314/0xa48\n[ C0] [<900000000164ead8>] schedule+0x58/0xf0\n[ C0] [<9000000000294a2c>] worker_thread+0x224/0x498\n[ C0] [<900000000029d2f0>] kthread+0xf8/0x108\n[ C0] [<9000000000221f28>] ret_from_kernel_thread+0xc/0xa4\n[ C0]\n[ C0] ---[ end trace 0000000000000000 ]---\n\nThe root cause is acpi_enable_all_wakeup_gpes() uses a mutex to protect\nacpi_hw_enable_all_wakeup_gpes(), and acpi_ut_acquire_mutex() may cause\na thread switch. Since there is no longer concurrent execution during\nloongarch_acpi_suspend(), we can call acpi_hw_enable_all_wakeup_gpes()\ndirectly in enable_gpe_wakeup().\n\nThe solution is similar to commit 22db06337f590d01 (\"ACPI: sleep: Avoid\nbreaking S3 wakeup due to might_sleep()\")."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/194d26a5a43c26dc98a9b4e2c1d521dcb84dd1bf",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/26c0a2d93af55d30a46d5f45d3e9c42cde730168",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8682a71a7f6de7c683f31b4334b04e19685a05f9",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/d49ab6857d98266010f3446c9c2063014db5b654",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21804.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21804.json
new file mode 100644
index 00000000000..8e1b028aaf8
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21804.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21804",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.030",
+ "lastModified": "2025-02-27T20:16:03.030",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region()\n\nThe rcar_pcie_parse_outbound_ranges() uses the devm_request_mem_region()\nmacro to request a needed resource. A string variable that lives on the\nstack is then used to store a dynamically computed resource name, which\nis then passed on as one of the macro arguments. This can lead to\nundefined behavior.\n\nDepending on the current contents of the memory, the manifestations of\nerrors may vary. One possible output may be as follows:\n\n $ cat /proc/iomem\n 30000000-37ffffff :\n 38000000-3fffffff :\n\nSometimes, garbage may appear after the colon.\n\nIn very rare cases, if no NULL-terminator is found in memory, the system\nmight crash because the string iterator will overrun which can lead to\naccess of unmapped memory above the stack.\n\nThus, fix this by replacing outbound_name with the name of the previously\nrequested resource. With the changes applied, the output will be as\nfollows:\n\n $ cat /proc/iomem\n 30000000-37ffffff : memory2\n 38000000-3fffffff : memory3\n\n[kwilczynski: commit log]"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/24576899c49509c0d533bcf569139f691d8f7af7",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/2c54b9fca1755e80a343ccfde0652dc5ea4744b2",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/2d2da5a4c1b4509f6f7e5a8db015cd420144beb4",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/44708208c2a4b828a57a2abe7799c9d3962e7eaa",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/9ff46b0bfeb6e0724a4ace015aa7a0b887cdb7c1",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21805.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21805.json
new file mode 100644
index 00000000000..9118af5f4f4
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21805.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21805",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.127",
+ "lastModified": "2025-02-27T20:16:03.127",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rtrs: Add missing deinit() call\n\nA warning is triggered when repeatedly connecting and disconnecting the\nrnbd:\n list_add corruption. prev->next should be next (ffff88800b13e480), but was ffff88801ecd1338. (prev=ffff88801ecd1340).\n WARNING: CPU: 1 PID: 36562 at lib/list_debug.c:32 __list_add_valid_or_report+0x7f/0xa0\n Workqueue: ib_cm cm_work_handler [ib_cm]\n RIP: 0010:__list_add_valid_or_report+0x7f/0xa0\n ? __list_add_valid_or_report+0x7f/0xa0\n ib_register_event_handler+0x65/0x93 [ib_core]\n rtrs_srv_ib_dev_init+0x29/0x30 [rtrs_server]\n rtrs_ib_dev_find_or_add+0x124/0x1d0 [rtrs_core]\n __alloc_path+0x46c/0x680 [rtrs_server]\n ? rtrs_rdma_connect+0xa6/0x2d0 [rtrs_server]\n ? rcu_is_watching+0xd/0x40\n ? __mutex_lock+0x312/0xcf0\n ? get_or_create_srv+0xad/0x310 [rtrs_server]\n ? rtrs_rdma_connect+0xa6/0x2d0 [rtrs_server]\n rtrs_rdma_connect+0x23c/0x2d0 [rtrs_server]\n ? __lock_release+0x1b1/0x2d0\n cma_cm_event_handler+0x4a/0x1a0 [rdma_cm]\n cma_ib_req_handler+0x3a0/0x7e0 [rdma_cm]\n cm_process_work+0x28/0x1a0 [ib_cm]\n ? _raw_spin_unlock_irq+0x2f/0x50\n cm_req_handler+0x618/0xa60 [ib_cm]\n cm_work_handler+0x71/0x520 [ib_cm]\n\nCommit 667db86bcbe8 (\"RDMA/rtrs: Register ib event handler\") introduced a\nnew element .deinit but never used it at all. Fix it by invoking the\n`deinit()` to appropriately unregister the IB event handler."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/1af2c769032b6b334cd2a867d7d8c7cbbc527b2d",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/5a79cc9bc961fafe90787f86e8f53ba6fad8d63b",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/81468c4058a62e84e475433b83b3edc613294f5e",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21806.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21806.json
new file mode 100644
index 00000000000..fee1dd5a0c5
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21806.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21806",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.220",
+ "lastModified": "2025-02-27T20:16:03.220",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: let net.core.dev_weight always be non-zero\n\nThe following problem was encountered during stability test:\n\n(NULL net_device): NAPI poll function process_backlog+0x0/0x530 \\\n\treturned 1, exceeding its budget of 0.\n------------[ cut here ]------------\nlist_add double add: new=ffff88905f746f48, prev=ffff88905f746f48, \\\n\tnext=ffff88905f746e40.\nWARNING: CPU: 18 PID: 5462 at lib/list_debug.c:35 \\\n\t__list_add_valid_or_report+0xf3/0x130\nCPU: 18 UID: 0 PID: 5462 Comm: ping Kdump: loaded Not tainted 6.13.0-rc7+\nRIP: 0010:__list_add_valid_or_report+0xf3/0x130\nCall Trace:\n? __warn+0xcd/0x250\n? __list_add_valid_or_report+0xf3/0x130\nenqueue_to_backlog+0x923/0x1070\nnetif_rx_internal+0x92/0x2b0\n__netif_rx+0x15/0x170\nloopback_xmit+0x2ef/0x450\ndev_hard_start_xmit+0x103/0x490\n__dev_queue_xmit+0xeac/0x1950\nip_finish_output2+0x6cc/0x1620\nip_output+0x161/0x270\nip_push_pending_frames+0x155/0x1a0\nraw_sendmsg+0xe13/0x1550\n__sys_sendto+0x3bf/0x4e0\n__x64_sys_sendto+0xdc/0x1b0\ndo_syscall_64+0x5b/0x170\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe reproduction command is as follows:\n sysctl -w net.core.dev_weight=0\n ping 127.0.0.1\n\nThis is because when the napi's weight is set to 0, process_backlog() may\nreturn 0 and clear the NAPI_STATE_SCHED bit of napi->state, causing this\nnapi to be re-polled in net_rx_action() until __do_softirq() times out.\nSince the NAPI_STATE_SCHED bit has been cleared, napi_schedule_rps() can\nbe retriggered in enqueue_to_backlog(), causing this issue.\n\nMaking the napi's weight always non-zero solves this problem.\n\nTriggering this issue requires system-wide admin (setting is\nnot namespaced)."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/1489824e5226a26841c70639ebd2d1aed390764b",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/33e2168788f8fb5cb8bd4f36cb1ef37d1d34dada",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/5860abbf15eeb61838b5e32e721ba67b0aa84450",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/6ce38b5a6a49e65bad163162a54cb3f104c40b48",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/d1f9f79fa2af8e3b45cffdeef66e05833480148a",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21807.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21807.json
new file mode 100644
index 00000000000..78ae1001209
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21807.json
@@ -0,0 +1,25 @@
+{
+ "id": "CVE-2025-21807",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.317",
+ "lastModified": "2025-02-27T20:16:03.317",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: fix queue freeze vs limits lock order in sysfs store methods\n\nqueue_attr_store() always freezes a device queue before calling the\nattribute store operation. For attributes that control queue limits, the\nstore operation will also lock the queue limits with a call to\nqueue_limits_start_update(). However, some drivers (e.g. SCSI sd) may\nneed to issue commands to a device to obtain limit values from the\nhardware with the queue limits locked. This creates a potential ABBA\ndeadlock situation if a user attempts to modify a limit (thus freezing\nthe device queue) while the device driver starts a revalidation of the\ndevice queue limits.\n\nAvoid such deadlock by not freezing the queue before calling the\n->store_limit() method in struct queue_sysfs_entry and instead use the\nqueue_limits_commit_update_frozen helper to freeze the queue after taking\nthe limits lock.\n\nThis also removes taking the sysfs lock for the store_limit method as\nit doesn't protect anything here, but creates even more nesting.\nHopefully it will go away from the actual sysfs methods entirely soon.\n\n(commit log adapted from a similar patch from Damien Le Moal)"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/8985da5481562e96b95e94ed8e5cc9b6565eb82b",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/c99f66e4084a62a2cc401c4704a84328aeddc9ec",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21808.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21808.json
new file mode 100644
index 00000000000..17420288e0a
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21808.json
@@ -0,0 +1,33 @@
+{
+ "id": "CVE-2025-21808",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.410",
+ "lastModified": "2025-02-27T20:16:03.410",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: xdp: Disallow attaching device-bound programs in generic mode\n\nDevice-bound programs are used to support RX metadata kfuncs. These\nkfuncs are driver-specific and rely on the driver context to read the\nmetadata. This means they can't work in generic XDP mode. However, there\nis no check to disallow such programs from being attached in generic\nmode, in which case the metadata kfuncs will be called in an invalid\ncontext, leading to crashes.\n\nFix this by adding a check to disallow attaching device-bound programs\nin generic mode."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/3595599fa8360bb3c7afa7ee50c810b4a64106ea",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/557707906dd3e34b8a8c265f664d19f95799937e",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/5a9eae683d6c36e8a7aa31e5eb8b369e41aa66e1",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/b1bc4a35a04cbeb85b6ef5911ec015baa424989f",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21809.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21809.json
new file mode 100644
index 00000000000..e16aae1d32b
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21809.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21809",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.497",
+ "lastModified": "2025-02-27T20:16:03.497",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc, afs: Fix peer hash locking vs RCU callback\n\nIn its address list, afs now retains pointers to and refs on one or more\nrxrpc_peer objects. The address list is freed under RCU and at this time,\nit puts the refs on those peers.\n\nNow, when an rxrpc_peer object runs out of refs, it gets removed from the\npeer hash table and, for that, rxrpc has to take a spinlock. However, it\nis now being called from afs's RCU cleanup, which takes place in BH\ncontext - but it is just taking an ordinary spinlock.\n\nThe put may also be called from non-BH context, and so there exists the\npossibility of deadlock if the BH-based RCU cleanup happens whilst the hash\nspinlock is held. This led to the attached lockdep complaint.\n\nFix this by changing spinlocks of rxnet->peer_hash_lock back to\nBH-disabling locks.\n\n ================================\n WARNING: inconsistent lock state\n 6.13.0-rc5-build2+ #1223 Tainted: G E\n --------------------------------\n inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.\n swapper/1/0 [HC0[0]:SC1[1]:HE1:SE0] takes:\n ffff88810babe228 (&rxnet->peer_hash_lock){+.?.}-{3:3}, at: rxrpc_put_peer+0xcb/0x180\n {SOFTIRQ-ON-W} state was registered at:\n mark_usage+0x164/0x180\n __lock_acquire+0x544/0x990\n lock_acquire.part.0+0x103/0x280\n _raw_spin_lock+0x2f/0x40\n rxrpc_peer_keepalive_worker+0x144/0x440\n process_one_work+0x486/0x7c0\n process_scheduled_works+0x73/0x90\n worker_thread+0x1c8/0x2a0\n kthread+0x19b/0x1b0\n ret_from_fork+0x24/0x40\n ret_from_fork_asm+0x1a/0x30\n irq event stamp: 972402\n hardirqs last enabled at (972402): [] _raw_spin_unlock_irqrestore+0x2e/0x50\n hardirqs last disabled at (972401): [] _raw_spin_lock_irqsave+0x18/0x60\n softirqs last enabled at (972300): [] handle_softirqs+0x3ee/0x430\n softirqs last disabled at (972313): [] __irq_exit_rcu+0x44/0x110\n\n other info that might help us debug this:\n Possible unsafe locking scenario:\n CPU0\n ----\n lock(&rxnet->peer_hash_lock);\n \n lock(&rxnet->peer_hash_lock);\n\n *** DEADLOCK ***\n 1 lock held by swapper/1/0:\n #0: ffffffff83576be0 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire+0x7/0x30\n\n stack backtrace:\n CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Tainted: G E 6.13.0-rc5-build2+ #1223\n Tainted: [E]=UNSIGNED_MODULE\n Hardware name: ASUS All Series/H97-PLUS, BIOS 2306 10/09/2014\n Call Trace:\n \n dump_stack_lvl+0x57/0x80\n print_usage_bug.part.0+0x227/0x240\n valid_state+0x53/0x70\n mark_lock_irq+0xa5/0x2f0\n mark_lock+0xf7/0x170\n mark_usage+0xe1/0x180\n __lock_acquire+0x544/0x990\n lock_acquire.part.0+0x103/0x280\n _raw_spin_lock+0x2f/0x40\n rxrpc_put_peer+0xcb/0x180\n afs_free_addrlist+0x46/0x90 [kafs]\n rcu_do_batch+0x2d2/0x640\n rcu_core+0x2f7/0x350\n handle_softirqs+0x1ee/0x430\n __irq_exit_rcu+0x44/0x110\n irq_exit_rcu+0xa/0x30\n sysvec_apic_timer_interrupt+0x7f/0xa0\n "
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/0e77dd41689637ac4e1b8fe0f27541f373640855",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/10ba5a3d57af20e494e0d979d1894260989235dd",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/79d458c13056559d49b5e41fbc4b6890e68cf65b",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21810.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21810.json
new file mode 100644
index 00000000000..08c2f36850d
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21810.json
@@ -0,0 +1,33 @@
+{
+ "id": "CVE-2025-21810",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.587",
+ "lastModified": "2025-02-27T20:16:03.587",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: class: Fix wild pointer dereferences in API class_dev_iter_next()\n\nThere are a potential wild pointer dereferences issue regarding APIs\nclass_dev_iter_(init|next|exit)(), as explained by below typical usage:\n\n// All members of @iter are wild pointers.\nstruct class_dev_iter iter;\n\n// class_dev_iter_init(@iter, @class, ...) checks parameter @class for\n// potential class_to_subsys() error, and it returns void type and does\n// not initialize its output parameter @iter, so caller can not detect\n// the error and continues to invoke class_dev_iter_next(@iter) even if\n// @iter still contains wild pointers.\nclass_dev_iter_init(&iter, ...);\n\n// Dereference these wild pointers in @iter here once suffer the error.\nwhile (dev = class_dev_iter_next(&iter)) { ... };\n\n// Also dereference these wild pointers here.\nclass_dev_iter_exit(&iter);\n\nActually, all callers of these APIs have such usage pattern in kernel tree.\nFix by:\n- Initialize output parameter @iter by memset() in class_dev_iter_init()\n and give callers prompt by pr_crit() for the error.\n- Check if @iter is valid in class_dev_iter_next()."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/1614e75d1a1b63db6421c7a4bf37004720c7376c",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/5c504e9767b947cf7d4e29b811c0c8b3c53242b7",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/e128f82f7006991c99a58114f70ef61e937b1ac1",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/f4b9bc823b0cfdebfed479c0e87d6939c7562e87",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21811.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21811.json
new file mode 100644
index 00000000000..f28f673ea2f
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21811.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21811",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.680",
+ "lastModified": "2025-02-27T20:16:03.680",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: protect access to buffers with no active references\n\nnilfs_lookup_dirty_data_buffers(), which iterates through the buffers\nattached to dirty data folios/pages, accesses the attached buffers without\nlocking the folios/pages.\n\nFor data cache, nilfs_clear_folio_dirty() may be called asynchronously\nwhen the file system degenerates to read only, so\nnilfs_lookup_dirty_data_buffers() still has the potential to cause use\nafter free issues when buffers lose the protection of their dirty state\nmidway due to this asynchronous clearing and are unintentionally freed by\ntry_to_free_buffers().\n\nEliminate this race issue by adjusting the lock section in this function."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/367a9bffabe08c04f6d725032cce3d891b2b9e1a",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/4b08d23d7d1917bef4fbee8ad81372f49b006656",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/58c27fa7a610b6e8d44e6220e7dbddfbaccaf439",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8e1b9201c9a24638cf09c6e1c9f224157328010b",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/c437dfac9f7a5a46ac2a5e6d6acd3059e9f68188",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21812.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21812.json
new file mode 100644
index 00000000000..7e35c4c2af5
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21812.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21812",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.783",
+ "lastModified": "2025-02-27T20:16:03.783",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nax25: rcu protect dev->ax25_ptr\n\nsyzbot found a lockdep issue [1].\n\nWe should remove ax25 RTNL dependency in ax25_setsockopt()\n\nThis should also fix a variety of possible UAF in ax25.\n\n[1]\n\nWARNING: possible circular locking dependency detected\n6.13.0-rc3-syzkaller-00762-g9268abe611b0 #0 Not tainted\n------------------------------------------------------\nsyz.5.1818/12806 is trying to acquire lock:\n ffffffff8fcb3988 (rtnl_mutex){+.+.}-{4:4}, at: ax25_setsockopt+0xa55/0xe90 net/ax25/af_ax25.c:680\n\nbut task is already holding lock:\n ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1618 [inline]\n ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_setsockopt+0x209/0xe90 net/ax25/af_ax25.c:574\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-> #1 (sk_lock-AF_AX25){+.+.}-{0:0}:\n lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849\n lock_sock_nested+0x48/0x100 net/core/sock.c:3642\n lock_sock include/net/sock.h:1618 [inline]\n ax25_kill_by_device net/ax25/af_ax25.c:101 [inline]\n ax25_device_event+0x24d/0x580 net/ax25/af_ax25.c:146\n notifier_call_chain+0x1a5/0x3f0 kernel/notifier.c:85\n __dev_notify_flags+0x207/0x400\n dev_change_flags+0xf0/0x1a0 net/core/dev.c:9026\n dev_ifsioc+0x7c8/0xe70 net/core/dev_ioctl.c:563\n dev_ioctl+0x719/0x1340 net/core/dev_ioctl.c:820\n sock_do_ioctl+0x240/0x460 net/socket.c:1234\n sock_ioctl+0x626/0x8e0 net/socket.c:1339\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:906 [inline]\n __se_sys_ioctl+0xf5/0x170 fs/ioctl.c:892\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n-> #0 (rtnl_mutex){+.+.}-{4:4}:\n check_prev_add kernel/locking/lockdep.c:3161 [inline]\n check_prevs_add kernel/locking/lockdep.c:3280 [inline]\n validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904\n __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5226\n lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849\n __mutex_lock_common kernel/locking/mutex.c:585 [inline]\n __mutex_lock+0x1ac/0xee0 kernel/locking/mutex.c:735\n ax25_setsockopt+0xa55/0xe90 net/ax25/af_ax25.c:680\n do_sock_setsockopt+0x3af/0x720 net/socket.c:2324\n __sys_setsockopt net/socket.c:2349 [inline]\n __do_sys_setsockopt net/socket.c:2355 [inline]\n __se_sys_setsockopt net/socket.c:2352 [inline]\n __x64_sys_setsockopt+0x1ee/0x280 net/socket.c:2352\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nother info that might help us debug this:\n\n Possible unsafe locking scenario:\n\n CPU0 CPU1\n ---- ----\n lock(sk_lock-AF_AX25);\n lock(rtnl_mutex);\n lock(sk_lock-AF_AX25);\n lock(rtnl_mutex);\n\n *** DEADLOCK ***\n\n1 lock held by syz.5.1818/12806:\n #0: ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1618 [inline]\n #0: ffff8880617ac258 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_setsockopt+0x209/0xe90 net/ax25/af_ax25.c:574\n\nstack backtrace:\nCPU: 1 UID: 0 PID: 12806 Comm: syz.5.1818 Not tainted 6.13.0-rc3-syzkaller-00762-g9268abe611b0 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024\nCall Trace:\n \n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120\n print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074\n check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206\n check_prev_add kernel/locking/lockdep.c:3161 [inline]\n check_prevs_add kernel/lockin\n---truncated---"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/2802ed4ced27ebd474828fc67ffd7d66f11e3605",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/7705d8a7f2c26c80973c81093db07c6022b2b30e",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8937f5e38a218531dce2a89fae60e3adcc2311e1",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/95fc45d1dea8e1253f8ec58abc5befb71553d666",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/c2531db6de3c95551be58878f859c6a053b7eb2e",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21813.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21813.json
new file mode 100644
index 00000000000..5a1106921f6
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21813.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21813",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.883",
+ "lastModified": "2025-02-27T20:16:03.883",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntimers/migration: Fix off-by-one root mis-connection\n\nBefore attaching a new root to the old root, the children counter of the\nnew root is checked to verify that only the upcoming CPU's top group have\nbeen connected to it. However since the recently added commit b729cc1ec21a\n(\"timers/migration: Fix another race between hotplug and idle entry/exit\")\nthis check is not valid anymore because the old root is pre-accounted\nas a child to the new root. Therefore after connecting the upcoming\nCPU's top group to the new root, the children count to be expected must\nbe 2 and not 1 anymore.\n\nThis omission results in the old root to not be connected to the new\nroot. Then eventually the system may run with more than one top level,\nwhich defeats the purpose of a single idle migrator.\n\nAlso the old root is pre-accounted but not connected upon the new root\ncreation. But it can be connected to the new root later on. Therefore\nthe old root may be accounted twice to the new root. The propagation of\nsuch overcommit can end up creating a double final top-level root with a\ngroupmask incorrectly initialized. Although harmless given that the final\ntop level roots will never have a parent to walk up to, this oddity\nopportunistically reported the core issue:\n\n WARNING: CPU: 8 PID: 0 at kernel/time/timer_migration.c:543 tmigr_requires_handle_remote\n CPU: 8 UID: 0 PID: 0 Comm: swapper/8\n RIP: 0010:tmigr_requires_handle_remote\n Call Trace:\n \n ? tmigr_requires_handle_remote\n ? hrtimer_run_queues\n update_process_times\n tick_periodic\n tick_handle_periodic\n __sysvec_apic_timer_interrupt\n sysvec_apic_timer_interrupt\n \n\nFix the problem by taking the old root into account in the children count\nof the new root so the connection is not omitted.\n\nAlso warn when more than one top level group exists to better detect\nsimilar issues in the future."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/6f449d8fa1808a7f9ee644866bbc079285dbefdd",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/868c9037df626b3c245ee26a290a03ae1f9f58d3",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/c6dd70e5b465a2b77c7a7c3d868736d302e29aec",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21814.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21814.json
new file mode 100644
index 00000000000..7fd6109322d
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21814.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21814",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:03.973",
+ "lastModified": "2025-02-27T20:16:03.973",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nptp: Ensure info->enable callback is always set\n\nThe ioctl and sysfs handlers unconditionally call the ->enable callback.\nNot all drivers implement that callback, leading to NULL dereferences.\nExample of affected drivers: ptp_s390.c, ptp_vclock.c and ptp_mock.c.\n\nInstead use a dummy callback if no better was specified by the driver."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/5d1041c76de656f9f8d5a192218039a9acf9bd00",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/755caf4ee1c615ee5717862e427124370f46b1f3",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/81846070cba17125a866e8023c01d3465b153339",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8441aea46445252df5d2eed6deb6d5246fc24002",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/fd53aa40e65f518453115b6f56183b0c201db26b",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21815.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21815.json
new file mode 100644
index 00000000000..23738b75c28
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21815.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21815",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.063",
+ "lastModified": "2025-02-27T20:16:04.063",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/compaction: fix UBSAN shift-out-of-bounds warning\n\nsyzkaller reported a UBSAN shift-out-of-bounds warning of (1UL << order)\nin isolate_freepages_block(). The bogus compound_order can be any value\nbecause it is union with flags. Add back the MAX_PAGE_ORDER check to fix\nthe warning."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/10b7d3eb535098ccd4c82a182a33655d8a0e5c88",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/4491159774d973a9e2e998d25d8fbb20fada6dfa",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/d1366e74342e75555af2648a2964deb2d5c92200",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21816.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21816.json
new file mode 100644
index 00000000000..237afdd13b1
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21816.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21816",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.150",
+ "lastModified": "2025-02-27T20:16:04.150",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nhrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING\n\nhrtimers are migrated away from the dying CPU to any online target at\nthe CPUHP_AP_HRTIMERS_DYING stage in order not to delay bandwidth timers\nhandling tasks involved in the CPU hotplug forward progress.\n\nHowever wakeups can still be performed by the outgoing CPU after\nCPUHP_AP_HRTIMERS_DYING. Those can result again in bandwidth timers being\narmed. Depending on several considerations (crystal ball power management\nbased election, earliest timer already enqueued, timer migration enabled or\nnot), the target may eventually be the current CPU even if offline. If that\nhappens, the timer is eventually ignored.\n\nThe most notable example is RCU which had to deal with each and every of\nthose wake-ups by deferring them to an online CPU, along with related\nworkarounds:\n\n_ e787644caf76 (rcu: Defer RCU kthreads wakeup when CPU is dying)\n_ 9139f93209d1 (rcu/nocb: Fix RT throttling hrtimer armed from offline CPU)\n_ f7345ccc62a4 (rcu/nocb: Fix rcuog wake-up from offline softirq)\n\nThe problem isn't confined to RCU though as the stop machine kthread\n(which runs CPUHP_AP_HRTIMERS_DYING) reports its completion at the end\nof its work through cpu_stop_signal_done() and performs a wake up that\neventually arms the deadline server timer:\n\n WARNING: CPU: 94 PID: 588 at kernel/time/hrtimer.c:1086 hrtimer_start_range_ns+0x289/0x2d0\n CPU: 94 UID: 0 PID: 588 Comm: migration/94 Not tainted\n Stopper: multi_cpu_stop+0x0/0x120 <- stop_machine_cpuslocked+0x66/0xc0\n RIP: 0010:hrtimer_start_range_ns+0x289/0x2d0\n Call Trace:\n \n start_dl_timer\n enqueue_dl_entity\n dl_server_start\n enqueue_task_fair\n enqueue_task\n ttwu_do_activate\n try_to_wake_up\n complete\n cpu_stopper_thread\n\nInstead of providing yet another bandaid to work around the situation, fix\nit in the hrtimers infrastructure instead: always migrate away a timer to\nan online target whenever it is enqueued from an offline CPU.\n\nThis will also allow to revert all the above RCU disgraceful hacks."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/2aecec58e9040ce3d2694707889f9914a2374955",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/53dac345395c0d2493cbc2f4c85fe38aef5b63f5",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/e456a88bddae4030ba962447bb84be6669f2a0c1",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21817.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21817.json
new file mode 100644
index 00000000000..86c1648d551
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21817.json
@@ -0,0 +1,25 @@
+{
+ "id": "CVE-2025-21817",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.243",
+ "lastModified": "2025-02-27T20:16:04.243",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: mark GFP_NOIO around sysfs ->store()\n\nsysfs ->store is called with queue freezed, meantime we have several\n->store() callbacks(update_nr_requests, wbt, scheduler) to allocate\nmemory with GFP_KERNEL which may run into direct reclaim code path,\nthen potential deadlock can be caused.\n\nFix the issue by marking NOIO around sysfs ->store()"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/2566ce907e5d5db8a039647208e029ce559baa31",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/7c0be4ead1f8f5f8be0803f347de0de81e3b8e1c",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21818.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21818.json
new file mode 100644
index 00000000000..b0e4038249d
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21818.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21818",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.330",
+ "lastModified": "2025-02-27T20:16:04.330",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/xen: fix xen_hypercall_hvm() to not clobber %rbx\n\nxen_hypercall_hvm(), which is used when running as a Xen PVH guest at\nmost only once during early boot, is clobbering %rbx. Depending on\nwhether the caller relies on %rbx to be preserved across the call or\nnot, this clobbering might result in an early crash of the system.\n\nThis can be avoided by using an already saved register instead of %rbx."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/23f6f420cd727d641f95478fcf3bbbee41e4e5d6",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/242f7584da3ad041a9db809d33d27a8be8eccc29",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/4890a0858c09d96f3234a8f94663de80a7201bc4",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/522d726824cc570e0b6bf0b3af4d5a826f1b17c5",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/98a5cfd2320966f40fe049a9855f8787f0126825",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21819.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21819.json
new file mode 100644
index 00000000000..e0ac5e46fcf
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21819.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21819",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.430",
+ "lastModified": "2025-02-27T20:16:04.430",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"drm/amd/display: Use HW lock mgr for PSR1\"\n\nThis reverts commit\na2b5a9956269 (\"drm/amd/display: Use HW lock mgr for PSR1\")\n\nBecause it may cause system hang while connect with two edp panel."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/915697c2e69ac8d14dad498e6d6f43dbb7de3787",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/95c75578c420110c43791295985abb961d6dc033",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/a978864653e45d2671f99b09afcc1110e45d3dd9",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/dcc3f2c06d80da39eee742b51ddf0781affb260c",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/f245b400a223a71d6d5f4c72a2cb9b573a7fc2b6",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21820.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21820.json
new file mode 100644
index 00000000000..2155dd567d4
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21820.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21820",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.520",
+ "lastModified": "2025-02-27T20:16:04.520",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntty: xilinx_uartps: split sysrq handling\n\nlockdep detects the following circular locking dependency:\n\nCPU 0 CPU 1\n========================== ============================\ncdns_uart_isr() printk()\n uart_port_lock(port) console_lock()\n\t\t\t cdns_uart_console_write()\n if (!port->sysrq)\n uart_port_lock(port)\n uart_handle_break()\n port->sysrq = ...\n uart_handle_sysrq_char()\n printk()\n console_lock()\n\nThe fixed commit attempts to avoid this situation by only taking the\nport lock in cdns_uart_console_write if port->sysrq unset. However, if\n(as shown above) cdns_uart_console_write runs before port->sysrq is set,\nthen it will try to take the port lock anyway. This may result in a\ndeadlock.\n\nFix this by splitting sysrq handling into two parts. We use the prepare\nhelper under the port lock and defer handling until we release the lock."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/4410dba9807a17a93f649a9f5870ceaf30a675a3",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8ea0e7b3d7b8f2f0fc9db491ff22a0abe120801c",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/9b88a7c4584ba67267a051069b8abe44fc9595b2",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/b06f388994500297bb91be60ffaf6825ecfd2afe",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/de5bd24197bd9ee37ec1e379a3d882bbd15c5065",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21821.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21821.json
new file mode 100644
index 00000000000..214656e0fad
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21821.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21821",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.613",
+ "lastModified": "2025-02-27T20:16:04.613",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: omap: use threaded IRQ for LCD DMA\n\nWhen using touchscreen and framebuffer, Nokia 770 crashes easily with:\n\n BUG: scheduling while atomic: irq/144-ads7846/82/0x00010000\n Modules linked in: usb_f_ecm g_ether usb_f_rndis u_ether libcomposite configfs omap_udc ohci_omap ohci_hcd\n CPU: 0 UID: 0 PID: 82 Comm: irq/144-ads7846 Not tainted 6.12.7-770 #2\n Hardware name: Nokia 770\n Call trace:\n unwind_backtrace from show_stack+0x10/0x14\n show_stack from dump_stack_lvl+0x54/0x5c\n dump_stack_lvl from __schedule_bug+0x50/0x70\n __schedule_bug from __schedule+0x4d4/0x5bc\n __schedule from schedule+0x34/0xa0\n schedule from schedule_preempt_disabled+0xc/0x10\n schedule_preempt_disabled from __mutex_lock.constprop.0+0x218/0x3b4\n __mutex_lock.constprop.0 from clk_prepare_lock+0x38/0xe4\n clk_prepare_lock from clk_set_rate+0x18/0x154\n clk_set_rate from sossi_read_data+0x4c/0x168\n sossi_read_data from hwa742_read_reg+0x5c/0x8c\n hwa742_read_reg from send_frame_handler+0xfc/0x300\n send_frame_handler from process_pending_requests+0x74/0xd0\n process_pending_requests from lcd_dma_irq_handler+0x50/0x74\n lcd_dma_irq_handler from __handle_irq_event_percpu+0x44/0x130\n __handle_irq_event_percpu from handle_irq_event+0x28/0x68\n handle_irq_event from handle_level_irq+0x9c/0x170\n handle_level_irq from generic_handle_domain_irq+0x2c/0x3c\n generic_handle_domain_irq from omap1_handle_irq+0x40/0x8c\n omap1_handle_irq from generic_handle_arch_irq+0x28/0x3c\n generic_handle_arch_irq from call_with_stack+0x1c/0x24\n call_with_stack from __irq_svc+0x94/0xa8\n Exception stack(0xc5255da0 to 0xc5255de8)\n 5da0: 00000001 c22fc620 00000000 00000000 c08384a8 c106fc00 00000000 c240c248\n 5dc0: c113a600 c3f6ec30 00000001 00000000 c22fc620 c5255df0 c22fc620 c0279a94\n 5de0: 60000013 ffffffff\n __irq_svc from clk_prepare_lock+0x4c/0xe4\n clk_prepare_lock from clk_get_rate+0x10/0x74\n clk_get_rate from uwire_setup_transfer+0x40/0x180\n uwire_setup_transfer from spi_bitbang_transfer_one+0x2c/0x9c\n spi_bitbang_transfer_one from spi_transfer_one_message+0x2d0/0x664\n spi_transfer_one_message from __spi_pump_transfer_message+0x29c/0x498\n __spi_pump_transfer_message from __spi_sync+0x1f8/0x2e8\n __spi_sync from spi_sync+0x24/0x40\n spi_sync from ads7846_halfd_read_state+0x5c/0x1c0\n ads7846_halfd_read_state from ads7846_irq+0x58/0x348\n ads7846_irq from irq_thread_fn+0x1c/0x78\n irq_thread_fn from irq_thread+0x120/0x228\n irq_thread from kthread+0xc8/0xe8\n kthread from ret_from_fork+0x14/0x28\n\nAs a quick fix, switch to a threaded IRQ which provides a stable system."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/7bbbd311dd503653a2cc86d9226740883051dc92",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8392ea100f0b86c234c739c6662f39f0ccc0cefd",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/aa8e22cbedeb626f2a6bda0aea362353d627cd0a",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/e4b6b665df815b4841e71b72f06446884e8aad40",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/fb6a5edb60921887d7d10619fcdcbee9759552cb",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21822.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21822.json
new file mode 100644
index 00000000000..e85a61c475a
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21822.json
@@ -0,0 +1,25 @@
+{
+ "id": "CVE-2025-21822",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.707",
+ "lastModified": "2025-02-27T20:16:04.707",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nptp: vmclock: Set driver data before its usage\n\nIf vmclock_ptp_register() fails during probing, vmclock_remove() is\ncalled to clean up the ptp clock and misc device.\nIt uses dev_get_drvdata() to access the vmclock state.\nHowever the driver data is not yet set at this point.\n\nAssign the driver data earlier."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/6dbd8b91a065d1d8001446a28e72cd140f9acef0",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/f7d07cd4f77d77f366c8ffbb8ba8b61f614e5fce",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21823.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21823.json
new file mode 100644
index 00000000000..854f03fe637
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21823.json
@@ -0,0 +1,37 @@
+{
+ "id": "CVE-2025-21823",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.793",
+ "lastModified": "2025-02-27T20:16:04.793",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: Drop unmanaged ELP metric worker\n\nThe ELP worker needs to calculate new metric values for all neighbors\n\"reachable\" over an interface. Some of the used metric sources require\nlocks which might need to sleep. This sleep is incompatible with the RCU\nlist iterator used for the recorded neighbors. The initial approach to work\naround of this problem was to queue another work item per neighbor and then\nrun this in a new context.\n\nEven when this solved the RCU vs might_sleep() conflict, it has a major\nproblems: Nothing was stopping the work item in case it is not needed\nanymore - for example because one of the related interfaces was removed or\nthe batman-adv module was unloaded - resulting in potential invalid memory\naccesses.\n\nDirectly canceling the metric worker also has various problems:\n\n* cancel_work_sync for a to-be-deactivated interface is called with\n rtnl_lock held. But the code in the ELP metric worker also tries to use\n rtnl_lock() - which will never return in this case. This also means that\n cancel_work_sync would never return because it is waiting for the worker\n to finish.\n* iterating over the neighbor list for the to-be-deactivated interface is\n currently done using the RCU specific methods. Which means that it is\n possible to miss items when iterating over it without the associated\n spinlock - a behaviour which is acceptable for a periodic metric check\n but not for a cleanup routine (which must \"stop\" all still running\n workers)\n\nThe better approch is to get rid of the per interface neighbor metric\nworker and handle everything in the interface worker. The original problems\nare solved by:\n\n* creating a list of neighbors which require new metric information inside\n the RCU protected context, gathering the metric according to the new list\n outside the RCU protected context\n* only use rcu_trylock inside metric gathering code to avoid a deadlock\n when the cancel_delayed_work_sync is called in the interface removal code\n (which is called with the rtnl_lock held)"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/0fdc3c166ac17b26014313fa2b93696354511b24",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/781a06fd265a8151f7601122d9c2e985663828ff",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/8c8ecc98f5c65947b0070a24bac11e12e47cc65d",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/a7aa2317285806640c844acd4cd2cd768e395264",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/af264c2a9adc37f4bdf88ca7f3affa15d8c7de9e",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-218xx/CVE-2025-21824.json b/CVE-2025/CVE-2025-218xx/CVE-2025-21824.json
new file mode 100644
index 00000000000..d00c8bb06fe
--- /dev/null
+++ b/CVE-2025/CVE-2025-218xx/CVE-2025-21824.json
@@ -0,0 +1,29 @@
+{
+ "id": "CVE-2025-21824",
+ "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
+ "published": "2025-02-27T20:16:04.890",
+ "lastModified": "2025-02-27T20:16:04.890",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ngpu: host1x: Fix a use of uninitialized mutex\n\ncommit c8347f915e67 (\"gpu: host1x: Fix boot regression for Tegra\")\ncaused a use of uninitialized mutex leading to below warning when\nCONFIG_DEBUG_MUTEXES and CONFIG_DEBUG_LOCK_ALLOC are enabled.\n\n[ 41.662843] ------------[ cut here ]------------\n[ 41.663012] DEBUG_LOCKS_WARN_ON(lock->magic != lock)\n[ 41.663035] WARNING: CPU: 4 PID: 794 at kernel/locking/mutex.c:587 __mutex_lock+0x670/0x878\n[ 41.663458] Modules linked in: rtw88_8822c(+) bluetooth(+) rtw88_pci rtw88_core mac80211 aquantia libarc4 crc_itu_t cfg80211 tegra194_cpufreq dwmac_tegra(+) arm_dsu_pmu stmmac_platform stmmac pcs_xpcs rfkill at24 host1x(+) tegra_bpmp_thermal ramoops reed_solomon fuse loop nfnetlink xfs mmc_block rpmb_core ucsi_ccg ina3221 crct10dif_ce xhci_tegra ghash_ce lm90 sha2_ce sha256_arm64 sha1_ce sdhci_tegra pwm_fan sdhci_pltfm sdhci gpio_keys rtc_tegra cqhci mmc_core phy_tegra_xusb i2c_tegra tegra186_gpc_dma i2c_tegra_bpmp spi_tegra114 dm_mirror dm_region_hash dm_log dm_mod\n[ 41.665078] CPU: 4 UID: 0 PID: 794 Comm: (udev-worker) Not tainted 6.11.0-29.31_1538613708.el10.aarch64+debug #1\n[ 41.665838] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 36.3.0-gcid-35594366 02/26/2024\n[ 41.672555] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 41.679636] pc : __mutex_lock+0x670/0x878\n[ 41.683834] lr : __mutex_lock+0x670/0x878\n[ 41.688035] sp : ffff800084b77090\n[ 41.691446] x29: ffff800084b77160 x28: ffffdd4bebf7b000 x27: ffffdd4be96b1000\n[ 41.698799] x26: 1fffe0002308361c x25: 1ffff0001096ee18 x24: 0000000000000000\n[ 41.706149] x23: 0000000000000000 x22: 0000000000000002 x21: ffffdd4be6e3c7a0\n[ 41.713500] x20: ffff800084b770f0 x19: ffff00011841b1e8 x18: 0000000000000000\n[ 41.720675] x17: 0000000000000000 x16: 0000000000000000 x15: 0720072007200720\n[ 41.728023] x14: 0000000000000000 x13: 0000000000000001 x12: ffff6001a96eaab3\n[ 41.735375] x11: 1fffe001a96eaab2 x10: ffff6001a96eaab2 x9 : ffffdd4be4838bbc\n[ 41.742723] x8 : 00009ffe5691554e x7 : ffff000d4b755593 x6 : 0000000000000001\n[ 41.749985] x5 : ffff000d4b755590 x4 : 1fffe0001d88f001 x3 : dfff800000000000\n[ 41.756988] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000ec478000\n[ 41.764251] Call trace:\n[ 41.766695] __mutex_lock+0x670/0x878\n[ 41.770373] mutex_lock_nested+0x2c/0x40\n[ 41.774134] host1x_intr_start+0x54/0xf8 [host1x]\n[ 41.778863] host1x_runtime_resume+0x150/0x228 [host1x]\n[ 41.783935] pm_generic_runtime_resume+0x84/0xc8\n[ 41.788485] __rpm_callback+0xa0/0x478\n[ 41.792422] rpm_callback+0x15c/0x1a8\n[ 41.795922] rpm_resume+0x698/0xc08\n[ 41.799597] __pm_runtime_resume+0xa8/0x140\n[ 41.803621] host1x_probe+0x810/0xbc0 [host1x]\n[ 41.807909] platform_probe+0xcc/0x1a8\n[ 41.811845] really_probe+0x188/0x800\n[ 41.815347] __driver_probe_device+0x164/0x360\n[ 41.819810] driver_probe_device+0x64/0x1a8\n[ 41.823834] __driver_attach+0x180/0x490\n[ 41.827773] bus_for_each_dev+0x104/0x1a0\n[ 41.831797] driver_attach+0x44/0x68\n[ 41.835296] bus_add_driver+0x23c/0x4e8\n[ 41.839235] driver_register+0x15c/0x3a8\n[ 41.843170] __platform_register_drivers+0xa4/0x208\n[ 41.848159] tegra_host1x_init+0x4c/0xff8 [host1x]\n[ 41.853147] do_one_initcall+0xd4/0x380\n[ 41.856997] do_init_module+0x1dc/0x698\n[ 41.860758] load_module+0xc70/0x1300\n[ 41.864435] __do_sys_init_module+0x1a8/0x1d0\n[ 41.868721] __arm64_sys_init_module+0x74/0xb0\n[ 41.873183] invoke_syscall.constprop.0+0xdc/0x1e8\n[ 41.877997] do_el0_svc+0x154/0x1d0\n[ 41.881671] el0_svc+0x54/0x140\n[ 41.884820] el0t_64_sync_handler+0x120/0x130\n[ 41.889285] el0t_64_sync+0x1a4/0x1a8\n[ 41.892960] irq event stamp: 69737\n[ 41.896370] hardirqs last enabled at (69737): [] _raw_spin_unlock_irqrestore+0x44/0xe8\n[ 41.905739] hardirqs last disabled at (69736):\n---truncated---"
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://git.kernel.org/stable/c/02458fbfaa0170aabf8506f7d4ed054f02414251",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/127e91638ddcd02b80de92fec2240609a9f90426",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ },
+ {
+ "url": "https://git.kernel.org/stable/c/396d8e5136b4476672bc15b83ba312486bb4bf76",
+ "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-226xx/CVE-2025-22624.json b/CVE-2025/CVE-2025-226xx/CVE-2025-22624.json
new file mode 100644
index 00000000000..0d86e05da72
--- /dev/null
+++ b/CVE-2025/CVE-2025-226xx/CVE-2025-22624.json
@@ -0,0 +1,82 @@
+{
+ "id": "CVE-2025-22624",
+ "sourceIdentifier": "help@fluidattacks.com",
+ "published": "2025-02-27T19:15:50.940",
+ "lastModified": "2025-02-27T19:15:50.940",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "FooGallery \u2013 Responsive Photo Gallery, Image Viewer, Justified, Masonry and Carousel 2.4.29 was found to be vulnerable. The web application dynamically generates web content without validating the source of the potentially untrusted data in myapp/extensions/albums/admin/class-meta boxes.php."
+ }
+ ],
+ "metrics": {
+ "cvssMetricV40": [
+ {
+ "source": "help@fluidattacks.com",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "4.0",
+ "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
+ "baseScore": 6.4,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "attackRequirements": "NONE",
+ "privilegesRequired": "NONE",
+ "userInteraction": "ACTIVE",
+ "vulnConfidentialityImpact": "NONE",
+ "vulnIntegrityImpact": "LOW",
+ "vulnAvailabilityImpact": "NONE",
+ "subConfidentialityImpact": "HIGH",
+ "subIntegrityImpact": "HIGH",
+ "subAvailabilityImpact": "HIGH",
+ "exploitMaturity": "NOT_DEFINED",
+ "confidentialityRequirement": "NOT_DEFINED",
+ "integrityRequirement": "NOT_DEFINED",
+ "availabilityRequirement": "NOT_DEFINED",
+ "modifiedAttackVector": "NOT_DEFINED",
+ "modifiedAttackComplexity": "NOT_DEFINED",
+ "modifiedAttackRequirements": "NOT_DEFINED",
+ "modifiedPrivilegesRequired": "NOT_DEFINED",
+ "modifiedUserInteraction": "NOT_DEFINED",
+ "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
+ "modifiedVulnIntegrityImpact": "NOT_DEFINED",
+ "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
+ "modifiedSubConfidentialityImpact": "NOT_DEFINED",
+ "modifiedSubIntegrityImpact": "NOT_DEFINED",
+ "modifiedSubAvailabilityImpact": "NOT_DEFINED",
+ "Safety": "NOT_DEFINED",
+ "Automatable": "NOT_DEFINED",
+ "Recovery": "NOT_DEFINED",
+ "valueDensity": "NOT_DEFINED",
+ "vulnerabilityResponseEffort": "NOT_DEFINED",
+ "providerUrgency": "NOT_DEFINED"
+ }
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "help@fluidattacks.com",
+ "type": "Primary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-79"
+ }
+ ]
+ }
+ ],
+ "references": [
+ {
+ "url": "https://fluidattacks.com/advisories/skims-10/",
+ "source": "help@fluidattacks.com"
+ },
+ {
+ "url": "https://wordpress.org/plugins/foogallery/",
+ "source": "help@fluidattacks.com"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-229xx/CVE-2025-22952.json b/CVE-2025/CVE-2025-229xx/CVE-2025-22952.json
new file mode 100644
index 00000000000..4424847d315
--- /dev/null
+++ b/CVE-2025/CVE-2025-229xx/CVE-2025-22952.json
@@ -0,0 +1,33 @@
+{
+ "id": "CVE-2025-22952",
+ "sourceIdentifier": "cve@mitre.org",
+ "published": "2025-02-27T20:16:04.983",
+ "lastModified": "2025-02-27T20:16:04.983",
+ "vulnStatus": "Received",
+ "cveTags": [],
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplied URLs, which can be exploited to perform SSRF attacks."
+ }
+ ],
+ "metrics": {},
+ "references": [
+ {
+ "url": "https://elest.io/open-source/memos",
+ "source": "cve@mitre.org"
+ },
+ {
+ "url": "https://github.com/usememos/memos",
+ "source": "cve@mitre.org"
+ },
+ {
+ "url": "https://github.com/usememos/memos/issues/4413",
+ "source": "cve@mitre.org"
+ },
+ {
+ "url": "https://github.com/usememos/memos/pull/4428",
+ "source": "cve@mitre.org"
+ }
+ ]
+}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-253xx/CVE-2025-25333.json b/CVE-2025/CVE-2025-253xx/CVE-2025-25333.json
index 94c52d1395e..4cba045f81b 100644
--- a/CVE-2025/CVE-2025-253xx/CVE-2025-25333.json
+++ b/CVE-2025/CVE-2025-253xx/CVE-2025-25333.json
@@ -2,7 +2,7 @@
"id": "CVE-2025-25333",
"sourceIdentifier": "cve@mitre.org",
"published": "2025-02-27T16:15:40.350",
- "lastModified": "2025-02-27T16:15:40.350",
+ "lastModified": "2025-02-27T20:16:05.073",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
@@ -11,7 +11,42 @@
"value": "An issue in IKEA CN iOS 4.13.0 allows attackers to access sensitive user information via supplying a crafted link."
}
],
- "metrics": {},
+ "metrics": {
+ "cvssMetricV31": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
+ }
+ ]
+ },
+ "weaknesses": [
+ {
+ "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-200"
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://github.com/ZhouZiyi1/Vuls/blob/main/250116-IKEACN/250116-IKEACN.pdf",
diff --git a/CVE-2025/CVE-2025-270xx/CVE-2025-27089.json b/CVE-2025/CVE-2025-270xx/CVE-2025-27089.json
index a7abf40e281..ff07f83b558 100644
--- a/CVE-2025/CVE-2025-270xx/CVE-2025-27089.json
+++ b/CVE-2025/CVE-2025-270xx/CVE-2025-27089.json
@@ -2,8 +2,8 @@
"id": "CVE-2025-27089",
"sourceIdentifier": "security-advisories@github.com",
"published": "2025-02-19T17:15:15.800",
- "lastModified": "2025-02-19T17:15:15.800",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 2.8,
"impactScore": 2.5
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
+ "baseScore": 4.3,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "LOW",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 1.4
}
]
},
@@ -51,14 +71,39 @@
]
}
],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:monospace:directus:*:*:*:*:*:node.js:*:*",
+ "versionStartIncluding": "11.0.0",
+ "versionEndExcluding": "11.1.2",
+ "matchCriteriaId": "E4EEE6EE-0124-48C2-BD2E-A17C8D8F70A7"
+ }
+ ]
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://github.com/directus/directus/releases/tag/v11.1.2",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Release Notes"
+ ]
},
{
"url": "https://github.com/directus/directus/security/advisories/GHSA-99vm-5v2h-h6r6",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-270xx/CVE-2025-27090.json b/CVE-2025/CVE-2025-270xx/CVE-2025-27090.json
index 37ea173c288..ed827ed3799 100644
--- a/CVE-2025/CVE-2025-270xx/CVE-2025-27090.json
+++ b/CVE-2025/CVE-2025-270xx/CVE-2025-27090.json
@@ -2,8 +2,8 @@
"id": "CVE-2025-27090",
"sourceIdentifier": "security-advisories@github.com",
"published": "2025-02-19T22:15:24.247",
- "lastModified": "2025-02-19T22:15:24.247",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -30,35 +30,57 @@
"attackRequirements": "NONE",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
- "vulnerableSystemConfidentiality": "LOW",
- "vulnerableSystemIntegrity": "NONE",
- "vulnerableSystemAvailability": "NONE",
- "subsequentSystemConfidentiality": "NONE",
- "subsequentSystemIntegrity": "NONE",
- "subsequentSystemAvailability": "NONE",
+ "vulnConfidentialityImpact": "LOW",
+ "vulnIntegrityImpact": "NONE",
+ "vulnAvailabilityImpact": "NONE",
+ "subConfidentialityImpact": "NONE",
+ "subIntegrityImpact": "NONE",
+ "subAvailabilityImpact": "NONE",
"exploitMaturity": "NOT_DEFINED",
- "confidentialityRequirements": "NOT_DEFINED",
- "integrityRequirements": "NOT_DEFINED",
- "availabilityRequirements": "NOT_DEFINED",
+ "confidentialityRequirement": "NOT_DEFINED",
+ "integrityRequirement": "NOT_DEFINED",
+ "availabilityRequirement": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
- "modifiedVulnerableSystemConfidentiality": "NOT_DEFINED",
- "modifiedVulnerableSystemIntegrity": "NOT_DEFINED",
- "modifiedVulnerableSystemAvailability": "NOT_DEFINED",
- "modifiedSubsequentSystemConfidentiality": "NOT_DEFINED",
- "modifiedSubsequentSystemIntegrity": "NOT_DEFINED",
- "modifiedSubsequentSystemAvailability": "NOT_DEFINED",
- "safety": "NOT_DEFINED",
- "automatable": "NOT_DEFINED",
- "recovery": "NOT_DEFINED",
+ "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
+ "modifiedVulnIntegrityImpact": "NOT_DEFINED",
+ "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
+ "modifiedSubConfidentialityImpact": "NOT_DEFINED",
+ "modifiedSubIntegrityImpact": "NOT_DEFINED",
+ "modifiedSubAvailabilityImpact": "NOT_DEFINED",
+ "Safety": "NOT_DEFINED",
+ "Automatable": "NOT_DEFINED",
+ "Recovery": "NOT_DEFINED",
"valueDensity": "NOT_DEFINED",
"vulnerabilityResponseEffort": "NOT_DEFINED",
"providerUrgency": "NOT_DEFINED"
}
}
+ ],
+ "cvssMetricV31": [
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
+ "baseScore": 5.3,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 1.4
+ }
]
},
"weaknesses": [
@@ -73,18 +95,47 @@
]
}
],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:bishopfox:sliver:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "1.5.26",
+ "versionEndExcluding": "1.5.43",
+ "matchCriteriaId": "6109E798-21E6-4BD3-A1FE-103E1F5E90AF"
+ }
+ ]
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://github.com/BishopFox/sliver/commit/0f340a25cf3d496ed870dae7da39eab4427bc16f",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Patch"
+ ]
},
{
"url": "https://github.com/BishopFox/sliver/commit/10e245326070c6a5884a02e0790bb7e2baefb3a1",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Patch"
+ ]
},
{
"url": "https://github.com/BishopFox/sliver/security/advisories/GHSA-fh4v-v779-4g2w",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Exploit",
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-270xx/CVE-2025-27091.json b/CVE-2025/CVE-2025-270xx/CVE-2025-27091.json
index 7e98b123d43..8889b3445c2 100644
--- a/CVE-2025/CVE-2025-270xx/CVE-2025-27091.json
+++ b/CVE-2025/CVE-2025-270xx/CVE-2025-27091.json
@@ -2,8 +2,8 @@
"id": "CVE-2025-27091",
"sourceIdentifier": "security-advisories@github.com",
"published": "2025-02-20T18:15:26.850",
- "lastModified": "2025-02-20T18:15:26.850",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -30,35 +30,57 @@
"attackRequirements": "NONE",
"privilegesRequired": "NONE",
"userInteraction": "ACTIVE",
- "vulnerableSystemConfidentiality": "HIGH",
- "vulnerableSystemIntegrity": "HIGH",
- "vulnerableSystemAvailability": "HIGH",
- "subsequentSystemConfidentiality": "NONE",
- "subsequentSystemIntegrity": "NONE",
- "subsequentSystemAvailability": "NONE",
+ "vulnConfidentialityImpact": "HIGH",
+ "vulnIntegrityImpact": "HIGH",
+ "vulnAvailabilityImpact": "HIGH",
+ "subConfidentialityImpact": "NONE",
+ "subIntegrityImpact": "NONE",
+ "subAvailabilityImpact": "NONE",
"exploitMaturity": "NOT_DEFINED",
- "confidentialityRequirements": "NOT_DEFINED",
- "integrityRequirements": "NOT_DEFINED",
- "availabilityRequirements": "NOT_DEFINED",
+ "confidentialityRequirement": "NOT_DEFINED",
+ "integrityRequirement": "NOT_DEFINED",
+ "availabilityRequirement": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
- "modifiedVulnerableSystemConfidentiality": "NOT_DEFINED",
- "modifiedVulnerableSystemIntegrity": "NOT_DEFINED",
- "modifiedVulnerableSystemAvailability": "NOT_DEFINED",
- "modifiedSubsequentSystemConfidentiality": "NOT_DEFINED",
- "modifiedSubsequentSystemIntegrity": "NOT_DEFINED",
- "modifiedSubsequentSystemAvailability": "NOT_DEFINED",
- "safety": "NOT_DEFINED",
- "automatable": "NOT_DEFINED",
- "recovery": "NOT_DEFINED",
+ "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
+ "modifiedVulnIntegrityImpact": "NOT_DEFINED",
+ "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
+ "modifiedSubConfidentialityImpact": "NOT_DEFINED",
+ "modifiedSubIntegrityImpact": "NOT_DEFINED",
+ "modifiedSubAvailabilityImpact": "NOT_DEFINED",
+ "Safety": "NOT_DEFINED",
+ "Automatable": "NOT_DEFINED",
+ "Recovery": "NOT_DEFINED",
"valueDensity": "NOT_DEFINED",
"vulnerabilityResponseEffort": "NOT_DEFINED",
"providerUrgency": "NOT_DEFINED"
}
}
+ ],
+ "cvssMetricV31": [
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "HIGH",
+ "privilegesRequired": "NONE",
+ "userInteraction": "REQUIRED",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "HIGH",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 1.6,
+ "impactScore": 5.9
+ }
]
},
"weaknesses": [
@@ -71,16 +93,50 @@
"value": "CWE-122"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-787"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:cisco:openh264:*:*:*:*:*:*:*:*",
+ "versionEndExcluding": "2.6.0",
+ "matchCriteriaId": "3B92072F-61A5-41D9-8120-955F2AAADD5E"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://github.com/cisco/openh264/releases/tag/v2.6.0",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Release Notes"
+ ]
},
{
"url": "https://github.com/cisco/openh264/security/advisories/GHSA-m99q-5j7x-7m9x",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-270xx/CVE-2025-27092.json b/CVE-2025/CVE-2025-270xx/CVE-2025-27092.json
index 5b06de488b2..90cf1ad392b 100644
--- a/CVE-2025/CVE-2025-270xx/CVE-2025-27092.json
+++ b/CVE-2025/CVE-2025-270xx/CVE-2025-27092.json
@@ -2,8 +2,8 @@
"id": "CVE-2025-27092",
"sourceIdentifier": "security-advisories@github.com",
"published": "2025-02-19T23:15:15.957",
- "lastModified": "2025-02-19T23:15:15.957",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -30,35 +30,57 @@
"attackRequirements": "NONE",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
- "vulnerableSystemConfidentiality": "HIGH",
- "vulnerableSystemIntegrity": "NONE",
- "vulnerableSystemAvailability": "NONE",
- "subsequentSystemConfidentiality": "NONE",
- "subsequentSystemIntegrity": "NONE",
- "subsequentSystemAvailability": "NONE",
+ "vulnConfidentialityImpact": "HIGH",
+ "vulnIntegrityImpact": "NONE",
+ "vulnAvailabilityImpact": "NONE",
+ "subConfidentialityImpact": "NONE",
+ "subIntegrityImpact": "NONE",
+ "subAvailabilityImpact": "NONE",
"exploitMaturity": "NOT_DEFINED",
- "confidentialityRequirements": "NOT_DEFINED",
- "integrityRequirements": "NOT_DEFINED",
- "availabilityRequirements": "NOT_DEFINED",
+ "confidentialityRequirement": "NOT_DEFINED",
+ "integrityRequirement": "NOT_DEFINED",
+ "availabilityRequirement": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
- "modifiedVulnerableSystemConfidentiality": "NOT_DEFINED",
- "modifiedVulnerableSystemIntegrity": "NOT_DEFINED",
- "modifiedVulnerableSystemAvailability": "NOT_DEFINED",
- "modifiedSubsequentSystemConfidentiality": "NOT_DEFINED",
- "modifiedSubsequentSystemIntegrity": "NOT_DEFINED",
- "modifiedSubsequentSystemAvailability": "NOT_DEFINED",
- "safety": "NOT_DEFINED",
- "automatable": "NOT_DEFINED",
- "recovery": "NOT_DEFINED",
+ "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
+ "modifiedVulnIntegrityImpact": "NOT_DEFINED",
+ "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
+ "modifiedSubConfidentialityImpact": "NOT_DEFINED",
+ "modifiedSubIntegrityImpact": "NOT_DEFINED",
+ "modifiedSubAvailabilityImpact": "NOT_DEFINED",
+ "Safety": "NOT_DEFINED",
+ "Automatable": "NOT_DEFINED",
+ "Recovery": "NOT_DEFINED",
"valueDensity": "NOT_DEFINED",
"vulnerabilityResponseEffort": "NOT_DEFINED",
"providerUrgency": "NOT_DEFINED"
}
}
+ ],
+ "cvssMetricV31": [
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
+ }
]
},
"weaknesses": [
@@ -73,14 +95,40 @@
]
}
],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:cmu:ghosts:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "8.0.0",
+ "versionEndExcluding": "8.2.7.90",
+ "matchCriteriaId": "0B3C22C0-6B43-4101-A7B3-55C82E811D0D"
+ }
+ ]
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://github.com/cmu-sei/GHOSTS/commit/e69827556a52ff813de00e1017c4b62598d2c887",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Patch"
+ ]
},
{
"url": "https://github.com/cmu-sei/GHOSTS/security/advisories/GHSA-qr67-m6w9-wj3j",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Vendor Advisory",
+ "Exploit"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-270xx/CVE-2025-27097.json b/CVE-2025/CVE-2025-270xx/CVE-2025-27097.json
index f0ccfe65e5a..8ef91393967 100644
--- a/CVE-2025/CVE-2025-270xx/CVE-2025-27097.json
+++ b/CVE-2025/CVE-2025-270xx/CVE-2025-27097.json
@@ -2,8 +2,8 @@
"id": "CVE-2025-27097",
"sourceIdentifier": "security-advisories@github.com",
"published": "2025-02-20T21:15:26.227",
- "lastModified": "2025-02-20T21:15:26.227",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -30,35 +30,57 @@
"attackRequirements": "NONE",
"privilegesRequired": "LOW",
"userInteraction": "PASSIVE",
- "vulnerableSystemConfidentiality": "NONE",
- "vulnerableSystemIntegrity": "LOW",
- "vulnerableSystemAvailability": "LOW",
- "subsequentSystemConfidentiality": "NONE",
- "subsequentSystemIntegrity": "NONE",
- "subsequentSystemAvailability": "NONE",
+ "vulnConfidentialityImpact": "NONE",
+ "vulnIntegrityImpact": "LOW",
+ "vulnAvailabilityImpact": "LOW",
+ "subConfidentialityImpact": "NONE",
+ "subIntegrityImpact": "NONE",
+ "subAvailabilityImpact": "NONE",
"exploitMaturity": "NOT_DEFINED",
- "confidentialityRequirements": "NOT_DEFINED",
- "integrityRequirements": "NOT_DEFINED",
- "availabilityRequirements": "NOT_DEFINED",
+ "confidentialityRequirement": "NOT_DEFINED",
+ "integrityRequirement": "NOT_DEFINED",
+ "availabilityRequirement": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
- "modifiedVulnerableSystemConfidentiality": "NOT_DEFINED",
- "modifiedVulnerableSystemIntegrity": "NOT_DEFINED",
- "modifiedVulnerableSystemAvailability": "NOT_DEFINED",
- "modifiedSubsequentSystemConfidentiality": "NOT_DEFINED",
- "modifiedSubsequentSystemIntegrity": "NOT_DEFINED",
- "modifiedSubsequentSystemAvailability": "NOT_DEFINED",
- "safety": "NOT_DEFINED",
- "automatable": "NOT_DEFINED",
- "recovery": "NOT_DEFINED",
+ "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
+ "modifiedVulnIntegrityImpact": "NOT_DEFINED",
+ "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
+ "modifiedSubConfidentialityImpact": "NOT_DEFINED",
+ "modifiedSubIntegrityImpact": "NOT_DEFINED",
+ "modifiedSubAvailabilityImpact": "NOT_DEFINED",
+ "Safety": "NOT_DEFINED",
+ "Automatable": "NOT_DEFINED",
+ "Recovery": "NOT_DEFINED",
"valueDensity": "NOT_DEFINED",
"vulnerabilityResponseEffort": "NOT_DEFINED",
"providerUrgency": "NOT_DEFINED"
}
}
+ ],
+ "cvssMetricV31": [
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
+ }
]
},
"weaknesses": [
@@ -71,12 +93,57 @@
"value": "CWE-400"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-401"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:the-guild:graphql_mesh:0.96.5:*:*:*:*:node.js:*:*",
+ "matchCriteriaId": "BE510785-F022-4152-8536-1322352F0698"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:the-guild:graphql_mesh:0.96.6:*:*:*:*:node.js:*:*",
+ "matchCriteriaId": "2D484264-71CC-4CFC-8959-FC43C8E44D5D"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:the-guild:graphql_mesh:0.96.7:*:*:*:*:node.js:*:*",
+ "matchCriteriaId": "42D32CD2-98C5-49CB-A66E-F9F72F560073"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:the-guild:graphql_mesh:0.96.8:*:*:*:*:node.js:*:*",
+ "matchCriteriaId": "B077BCC7-800F-43F3-AB05-6F7B3C05F0AA"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://github.com/ardatan/graphql-mesh/security/advisories/GHSA-rr4x-crhf-8886",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-270xx/CVE-2025-27098.json b/CVE-2025/CVE-2025-270xx/CVE-2025-27098.json
index 7ab6852eda6..2ccfef0d5ea 100644
--- a/CVE-2025/CVE-2025-270xx/CVE-2025-27098.json
+++ b/CVE-2025/CVE-2025-270xx/CVE-2025-27098.json
@@ -2,8 +2,8 @@
"id": "CVE-2025-27098",
"sourceIdentifier": "security-advisories@github.com",
"published": "2025-02-20T21:15:26.370",
- "lastModified": "2025-02-20T21:15:26.370",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 1.6,
"impactScore": 3.7
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "HIGH",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
}
]
},
@@ -49,12 +69,51 @@
"value": "CWE-22"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "NVD-CWE-noinfo"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:the-guild:graphql_mesh_cli:*:*:*:*:*:node.js:*:*",
+ "versionStartIncluding": "0.78.0",
+ "versionEndExcluding": "0.82.22",
+ "matchCriteriaId": "17A62D98-E1B7-47BE-8164-FEFB982D6FCD"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:the-guild:graphql_mesh_http:*:*:*:*:*:node.js:*:*",
+ "versionEndExcluding": "0.3.19",
+ "matchCriteriaId": "96E4C839-3476-4DEC-84A9-8D58BDC2A0A7"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://github.com/ardatan/graphql-mesh/security/advisories/GHSA-j2wh-wrv3-4x4g",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Exploit",
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-271xx/CVE-2025-27108.json b/CVE-2025/CVE-2025-271xx/CVE-2025-27108.json
index d4cda3c03bd..707c44dc30e 100644
--- a/CVE-2025/CVE-2025-271xx/CVE-2025-27108.json
+++ b/CVE-2025/CVE-2025-271xx/CVE-2025-27108.json
@@ -2,13 +2,17 @@
"id": "CVE-2025-27108",
"sourceIdentifier": "security-advisories@github.com",
"published": "2025-02-21T22:15:14.170",
- "lastModified": "2025-02-21T22:15:14.170",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "dom-expressions is a Fine-Grained Runtime for Performant DOM Rendering. In affected versions the use of javascript's `.replace()` opens up to potential Cross-site Scripting (XSS) vulnerabilities with the special replacement patterns beginning with `$`. Particularly, when the attributes of `Meta` tag from solid-meta are user-defined, attackers can utilise the special replacement patterns, either `$'` or `$\\`` to achieve XSS. The solid-meta package has this issue since it uses `useAffect` and context providers, which injects the used assets in the html header. \"dom-expressions\" uses `.replace()` to insert the assets, which is vulnerable to the special replacement patterns listed above. This effectively means that if the attributes of an asset tag contained user-controlled data, it would be vulnerable to XSS. For instance, there might be meta tags for the open graph protocol in a user profile page, but if attackers set the user query to some payload abusing `.replace()`, then they could execute arbitrary javascript in the victim's web browser. Moreover, it could be stored and cause more problems. This issue has been addressed in version 0.39.5 and all users are advised to upgrade. There are no known workarounds for this vulnerability."
+ },
+ {
+ "lang": "es",
+ "value": "dom-expressions es un entorno de ejecuci\u00f3n de grano fino para la representaci\u00f3n de DOM de alto rendimiento. En las versiones afectadas, el uso de `.replace()` de javascript abre la puerta a posibles vulnerabilidades de Cross-site Scripting (XSS) con los patrones de reemplazo especiales que comienzan con `$`. En particular, cuando los atributos de la etiqueta `Meta` de solid-meta est\u00e1n definidos por el usuario, los atacantes pueden utilizar los patrones de reemplazo especiales, ya sea `$'` o `$\\`` para lograr XSS. El paquete solid-meta tiene este problema, ya que utiliza `useAffect` y proveedores de contexto, que inyectan los activos utilizados en el encabezado html. \"dom-expressions\" utiliza `.replace()` para insertar los activos, lo que es vulnerable a los patrones de reemplazo especiales enumerados anteriormente. Esto significa efectivamente que si los atributos de una etiqueta de activo contuvieran datos controlados por el usuario, ser\u00eda vulnerable a XSS. Por ejemplo, puede haber metaetiquetas para el protocolo Open Graph en una p\u00e1gina de perfil de usuario, pero si los atacantes configuran la consulta del usuario con alg\u00fan payload que abuse de `.replace()`, entonces podr\u00edan ejecutar c\u00f3digo JavaScript arbitrario en el navegador web de la v\u00edctima. Adem\u00e1s, podr\u00eda almacenarse y causar m\u00e1s problemas. Este problema se ha solucionado en la versi\u00f3n 0.39.5 y se recomienda a todos los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad."
}
],
"metrics": {
@@ -32,6 +36,26 @@
},
"exploitabilityScore": 3.9,
"impactScore": 3.4
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
+ "baseScore": 6.1,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "REQUIRED",
+ "scope": "CHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 2.8,
+ "impactScore": 2.7
}
]
},
@@ -49,16 +73,50 @@
"value": "CWE-116"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-79"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:ryansolid:dom_expressions:*:*:*:*:*:*:*:*",
+ "versionEndExcluding": "0.39.5",
+ "matchCriteriaId": "62555A6D-E93A-4D12-82B3-2F9E7C812F6F"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://github.com/ryansolid/dom-expressions/commit/521f75dfa89ed24161646e7007d9d7d21da07767",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Patch"
+ ]
},
{
"url": "https://github.com/ryansolid/dom-expressions/security/advisories/GHSA-hw62-58pr-7wc5",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-271xx/CVE-2025-27112.json b/CVE-2025/CVE-2025-271xx/CVE-2025-27112.json
index 464e0c785ce..b8bd1491b29 100644
--- a/CVE-2025/CVE-2025-271xx/CVE-2025-27112.json
+++ b/CVE-2025/CVE-2025-271xx/CVE-2025-27112.json
@@ -2,13 +2,17 @@
"id": "CVE-2025-27112",
"sourceIdentifier": "security-advisories@github.com",
"published": "2025-02-24T19:15:14.597",
- "lastModified": "2025-02-24T19:15:14.597",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Navidrome is an open source web-based music collection server and streamer. Starting in version 0.52.0 and prior to version 0.54.5, in certain Subsonic API endpoints, a flaw in the authentication check process allows an attacker to specify any arbitrary username that does not exist on the system, along with a salted hash of an empty password. Under these conditions, Navidrome treats the request as authenticated, granting access to various Subsonic endpoints without requiring valid credentials. An attacker can use any non-existent username to bypass the authentication system and gain access to various read-only data in Navidrome, such as user playlists. However, any attempt to modify data fails with a \"permission denied\" error due to insufficient permissions, limiting the impact to unauthorized viewing of information. Version 0.54.5 contains a patch for this issue."
+ },
+ {
+ "lang": "es",
+ "value": "Navidrome es un servidor y transmisor de m\u00fasica de c\u00f3digo abierto basado en la web. A partir de la versi\u00f3n 0.52.0 y antes de la versi\u00f3n 0.54.5, en ciertos endpoints de la API de Subsonic, un fallo en el proceso de verificaci\u00f3n de autenticaci\u00f3n permite a un atacante especificar cualquier nombre de usuario arbitrario que no exista en el sistema, junto con un hash con sal de una contrase\u00f1a vac\u00eda. En estas condiciones, Navidrome trata la solicitud como autenticada, otorgando acceso a varios endpoints de Subsonic sin requerir credenciales v\u00e1lidas. Un atacante puede usar cualquier nombre de usuario inexistente para eludir el sistema de autenticaci\u00f3n y obtener acceso a varios datos de solo lectura en Navidrome, como listas de reproducci\u00f3n de usuarios. Sin embargo, cualquier intento de modificar los datos falla con un error de \"permiso denegado\" debido a permisos insuficientes, lo que limita el impacto a la visualizaci\u00f3n no autorizada de la informaci\u00f3n. La versi\u00f3n 0.54.5 contiene un parche para este problema."
}
],
"metrics": {
@@ -26,35 +30,57 @@
"attackRequirements": "NONE",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
- "vulnerableSystemConfidentiality": "LOW",
- "vulnerableSystemIntegrity": "LOW",
- "vulnerableSystemAvailability": "NONE",
- "subsequentSystemConfidentiality": "NONE",
- "subsequentSystemIntegrity": "NONE",
- "subsequentSystemAvailability": "NONE",
+ "vulnConfidentialityImpact": "LOW",
+ "vulnIntegrityImpact": "LOW",
+ "vulnAvailabilityImpact": "NONE",
+ "subConfidentialityImpact": "NONE",
+ "subIntegrityImpact": "NONE",
+ "subAvailabilityImpact": "NONE",
"exploitMaturity": "NOT_DEFINED",
- "confidentialityRequirements": "NOT_DEFINED",
- "integrityRequirements": "NOT_DEFINED",
- "availabilityRequirements": "NOT_DEFINED",
+ "confidentialityRequirement": "NOT_DEFINED",
+ "integrityRequirement": "NOT_DEFINED",
+ "availabilityRequirement": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
- "modifiedVulnerableSystemConfidentiality": "NOT_DEFINED",
- "modifiedVulnerableSystemIntegrity": "NOT_DEFINED",
- "modifiedVulnerableSystemAvailability": "NOT_DEFINED",
- "modifiedSubsequentSystemConfidentiality": "NOT_DEFINED",
- "modifiedSubsequentSystemIntegrity": "NOT_DEFINED",
- "modifiedSubsequentSystemAvailability": "NOT_DEFINED",
- "safety": "NOT_DEFINED",
- "automatable": "NOT_DEFINED",
- "recovery": "NOT_DEFINED",
+ "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
+ "modifiedVulnIntegrityImpact": "NOT_DEFINED",
+ "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
+ "modifiedSubConfidentialityImpact": "NOT_DEFINED",
+ "modifiedSubIntegrityImpact": "NOT_DEFINED",
+ "modifiedSubAvailabilityImpact": "NOT_DEFINED",
+ "Safety": "NOT_DEFINED",
+ "Automatable": "NOT_DEFINED",
+ "Recovery": "NOT_DEFINED",
"valueDensity": "NOT_DEFINED",
"vulnerabilityResponseEffort": "NOT_DEFINED",
"providerUrgency": "NOT_DEFINED"
}
}
+ ],
+ "cvssMetricV31": [
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
+ "baseScore": 6.5,
+ "baseSeverity": "MEDIUM",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "LOW",
+ "integrityImpact": "LOW",
+ "availabilityImpact": "NONE"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 2.5
+ }
]
},
"weaknesses": [
@@ -69,14 +95,40 @@
]
}
],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:navidrome:navidrome:*:*:*:*:*:go:*:*",
+ "versionStartIncluding": "0.52.0",
+ "versionEndExcluding": "0.54.5",
+ "matchCriteriaId": "539CEE37-8539-4175-BAFB-B4B65358B672"
+ }
+ ]
+ }
+ ]
+ }
+ ],
"references": [
{
"url": "https://github.com/navidrome/navidrome/commit/287079a9e409fb6b9708ca384d7daa7b5185c1a0",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Patch"
+ ]
},
{
"url": "https://github.com/navidrome/navidrome/security/advisories/GHSA-c3p4-vm8f-386p",
- "source": "security-advisories@github.com"
+ "source": "security-advisories@github.com",
+ "tags": [
+ "Exploit",
+ "Vendor Advisory"
+ ]
}
]
}
\ No newline at end of file
diff --git a/CVE-2025/CVE-2025-271xx/CVE-2025-27113.json b/CVE-2025/CVE-2025-271xx/CVE-2025-27113.json
index fceb35629ee..e1bebbb9eed 100644
--- a/CVE-2025/CVE-2025-271xx/CVE-2025-27113.json
+++ b/CVE-2025/CVE-2025-271xx/CVE-2025-27113.json
@@ -2,8 +2,8 @@
"id": "CVE-2025-27113",
"sourceIdentifier": "cve@mitre.org",
"published": "2025-02-18T23:15:10.960",
- "lastModified": "2025-02-18T23:15:10.960",
- "vulnStatus": "Received",
+ "lastModified": "2025-02-27T20:18:12.583",
+ "vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
@@ -36,6 +36,26 @@
},
"exploitabilityScore": 1.4,
"impactScore": 1.4
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Primary",
+ "cvssData": {
+ "version": "3.1",
+ "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
+ "baseScore": 7.5,
+ "baseSeverity": "HIGH",
+ "attackVector": "NETWORK",
+ "attackComplexity": "LOW",
+ "privilegesRequired": "NONE",
+ "userInteraction": "NONE",
+ "scope": "UNCHANGED",
+ "confidentialityImpact": "NONE",
+ "integrityImpact": "NONE",
+ "availabilityImpact": "HIGH"
+ },
+ "exploitabilityScore": 3.9,
+ "impactScore": 3.6
}
]
},
@@ -49,12 +69,51 @@
"value": "CWE-476"
}
]
+ },
+ {
+ "source": "nvd@nist.gov",
+ "type": "Secondary",
+ "description": [
+ {
+ "lang": "en",
+ "value": "CWE-476"
+ }
+ ]
+ }
+ ],
+ "configurations": [
+ {
+ "nodes": [
+ {
+ "operator": "OR",
+ "negate": false,
+ "cpeMatch": [
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:xmlsoft:libxml2:*:*:*:*:*:*:*:*",
+ "versionEndExcluding": "2.12.10",
+ "matchCriteriaId": "9EB46E7E-7E29-4F40-A890-EEC2C36FB50E"
+ },
+ {
+ "vulnerable": true,
+ "criteria": "cpe:2.3:a:xmlsoft:libxml2:*:*:*:*:*:*:*:*",
+ "versionStartIncluding": "2.13.0",
+ "versionEndExcluding": "2.13.6",
+ "matchCriteriaId": "AA27632E-368D-4792-B20A-49B3B168F3CE"
+ }
+ ]
+ }
+ ]
}
],
"references": [
{
"url": "https://gitlab.gnome.org/GNOME/libxml2/-/issues/861",
- "source": "cve@mitre.org"
+ "source": "cve@mitre.org",
+ "tags": [
+ "Exploit",
+ "Issue Tracking"
+ ]
}
]
}
\ No newline at end of file
diff --git a/README.md b/README.md
index 7380637dcb6..0e7e5ef94b5 100644
--- a/README.md
+++ b/README.md
@@ -13,13 +13,13 @@ Repository synchronizes with the NVD every 2 hours.
### Last Repository Update
```plain
-2025-02-27T19:00:20.796545+00:00
+2025-02-27T21:00:20.599309+00:00
```
### Most recent CVE Modification Timestamp synchronized with NVD
```plain
-2025-02-27T18:47:11.020000+00:00
+2025-02-27T20:54:25.290000+00:00
```
### Last Data Feed Release
@@ -33,52 +33,69 @@ Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/
### Total Number of included CVEs
```plain
-283401
+283437
```
### CVEs added in the last Commit
-Recently added CVEs: `8`
+Recently added CVEs: `36`
-- [CVE-2024-9285](CVE-2024/CVE-2024-92xx/CVE-2024-9285.json) (`2025-02-27T17:15:15.953`)
-- [CVE-2025-1742](CVE-2025/CVE-2025-17xx/CVE-2025-1742.json) (`2025-02-27T17:15:16.460`)
-- [CVE-2025-1743](CVE-2025/CVE-2025-17xx/CVE-2025-1743.json) (`2025-02-27T18:15:27.650`)
-- [CVE-2025-1745](CVE-2025/CVE-2025-17xx/CVE-2025-1745.json) (`2025-02-27T18:15:27.923`)
-- [CVE-2025-23687](CVE-2025/CVE-2025-236xx/CVE-2025-23687.json) (`2025-02-27T17:15:16.623`)
-- [CVE-2025-25329](CVE-2025/CVE-2025-253xx/CVE-2025-25329.json) (`2025-02-27T17:15:16.773`)
-- [CVE-2025-27157](CVE-2025/CVE-2025-271xx/CVE-2025-27157.json) (`2025-02-27T17:15:16.867`)
-- [CVE-2025-27399](CVE-2025/CVE-2025-273xx/CVE-2025-27399.json) (`2025-02-27T18:15:30.380`)
+- [CVE-2025-21802](CVE-2025/CVE-2025-218xx/CVE-2025-21802.json) (`2025-02-27T20:16:02.847`)
+- [CVE-2025-21803](CVE-2025/CVE-2025-218xx/CVE-2025-21803.json) (`2025-02-27T20:16:02.937`)
+- [CVE-2025-21804](CVE-2025/CVE-2025-218xx/CVE-2025-21804.json) (`2025-02-27T20:16:03.030`)
+- [CVE-2025-21805](CVE-2025/CVE-2025-218xx/CVE-2025-21805.json) (`2025-02-27T20:16:03.127`)
+- [CVE-2025-21806](CVE-2025/CVE-2025-218xx/CVE-2025-21806.json) (`2025-02-27T20:16:03.220`)
+- [CVE-2025-21807](CVE-2025/CVE-2025-218xx/CVE-2025-21807.json) (`2025-02-27T20:16:03.317`)
+- [CVE-2025-21808](CVE-2025/CVE-2025-218xx/CVE-2025-21808.json) (`2025-02-27T20:16:03.410`)
+- [CVE-2025-21809](CVE-2025/CVE-2025-218xx/CVE-2025-21809.json) (`2025-02-27T20:16:03.497`)
+- [CVE-2025-21810](CVE-2025/CVE-2025-218xx/CVE-2025-21810.json) (`2025-02-27T20:16:03.587`)
+- [CVE-2025-21811](CVE-2025/CVE-2025-218xx/CVE-2025-21811.json) (`2025-02-27T20:16:03.680`)
+- [CVE-2025-21812](CVE-2025/CVE-2025-218xx/CVE-2025-21812.json) (`2025-02-27T20:16:03.783`)
+- [CVE-2025-21813](CVE-2025/CVE-2025-218xx/CVE-2025-21813.json) (`2025-02-27T20:16:03.883`)
+- [CVE-2025-21814](CVE-2025/CVE-2025-218xx/CVE-2025-21814.json) (`2025-02-27T20:16:03.973`)
+- [CVE-2025-21815](CVE-2025/CVE-2025-218xx/CVE-2025-21815.json) (`2025-02-27T20:16:04.063`)
+- [CVE-2025-21816](CVE-2025/CVE-2025-218xx/CVE-2025-21816.json) (`2025-02-27T20:16:04.150`)
+- [CVE-2025-21817](CVE-2025/CVE-2025-218xx/CVE-2025-21817.json) (`2025-02-27T20:16:04.243`)
+- [CVE-2025-21818](CVE-2025/CVE-2025-218xx/CVE-2025-21818.json) (`2025-02-27T20:16:04.330`)
+- [CVE-2025-21819](CVE-2025/CVE-2025-218xx/CVE-2025-21819.json) (`2025-02-27T20:16:04.430`)
+- [CVE-2025-21820](CVE-2025/CVE-2025-218xx/CVE-2025-21820.json) (`2025-02-27T20:16:04.520`)
+- [CVE-2025-21821](CVE-2025/CVE-2025-218xx/CVE-2025-21821.json) (`2025-02-27T20:16:04.613`)
+- [CVE-2025-21822](CVE-2025/CVE-2025-218xx/CVE-2025-21822.json) (`2025-02-27T20:16:04.707`)
+- [CVE-2025-21823](CVE-2025/CVE-2025-218xx/CVE-2025-21823.json) (`2025-02-27T20:16:04.793`)
+- [CVE-2025-21824](CVE-2025/CVE-2025-218xx/CVE-2025-21824.json) (`2025-02-27T20:16:04.890`)
+- [CVE-2025-22624](CVE-2025/CVE-2025-226xx/CVE-2025-22624.json) (`2025-02-27T19:15:50.940`)
+- [CVE-2025-22952](CVE-2025/CVE-2025-229xx/CVE-2025-22952.json) (`2025-02-27T20:16:04.983`)
### CVEs modified in the last Commit
-Recently modified CVEs: `48`
+Recently modified CVEs: `102`
-- [CVE-2023-26905](CVE-2023/CVE-2023-269xx/CVE-2023-26905.json) (`2025-02-27T17:15:15.523`)
-- [CVE-2024-23610](CVE-2024/CVE-2024-236xx/CVE-2024-23610.json) (`2025-02-27T17:48:34.007`)
-- [CVE-2024-23611](CVE-2024/CVE-2024-236xx/CVE-2024-23611.json) (`2025-02-27T17:48:34.007`)
-- [CVE-2024-27268](CVE-2024/CVE-2024-272xx/CVE-2024-27268.json) (`2025-02-27T17:58:20.883`)
-- [CVE-2024-27604](CVE-2024/CVE-2024-276xx/CVE-2024-27604.json) (`2025-02-27T17:58:20.883`)
-- [CVE-2024-27605](CVE-2024/CVE-2024-276xx/CVE-2024-27605.json) (`2025-02-27T17:58:20.883`)
-- [CVE-2024-2791](CVE-2024/CVE-2024-27xx/CVE-2024-2791.json) (`2025-02-27T17:58:20.883`)
-- [CVE-2024-31004](CVE-2024/CVE-2024-310xx/CVE-2024-31004.json) (`2025-02-27T17:58:20.883`)
-- [CVE-2024-3226](CVE-2024/CVE-2024-32xx/CVE-2024-3226.json) (`2025-02-27T17:58:20.883`)
-- [CVE-2024-49570](CVE-2024/CVE-2024-495xx/CVE-2024-49570.json) (`2025-02-27T18:15:27.083`)
-- [CVE-2024-54458](CVE-2024/CVE-2024-544xx/CVE-2024-54458.json) (`2025-02-27T18:15:27.273`)
-- [CVE-2024-57984](CVE-2024/CVE-2024-579xx/CVE-2024-57984.json) (`2025-02-27T18:15:27.460`)
-- [CVE-2024-9634](CVE-2024/CVE-2024-96xx/CVE-2024-9634.json) (`2025-02-27T18:47:11.020`)
-- [CVE-2025-21715](CVE-2025/CVE-2025-217xx/CVE-2025-21715.json) (`2025-02-27T18:15:28.153`)
-- [CVE-2025-21726](CVE-2025/CVE-2025-217xx/CVE-2025-21726.json) (`2025-02-27T18:15:28.350`)
-- [CVE-2025-21727](CVE-2025/CVE-2025-217xx/CVE-2025-21727.json) (`2025-02-27T18:15:28.547`)
-- [CVE-2025-21731](CVE-2025/CVE-2025-217xx/CVE-2025-21731.json) (`2025-02-27T18:15:28.727`)
-- [CVE-2025-21759](CVE-2025/CVE-2025-217xx/CVE-2025-21759.json) (`2025-02-27T18:15:28.927`)
-- [CVE-2025-21760](CVE-2025/CVE-2025-217xx/CVE-2025-21760.json) (`2025-02-27T18:15:29.127`)
-- [CVE-2025-21761](CVE-2025/CVE-2025-217xx/CVE-2025-21761.json) (`2025-02-27T18:15:29.327`)
-- [CVE-2025-21762](CVE-2025/CVE-2025-217xx/CVE-2025-21762.json) (`2025-02-27T18:15:29.503`)
-- [CVE-2025-21763](CVE-2025/CVE-2025-217xx/CVE-2025-21763.json) (`2025-02-27T18:15:29.673`)
-- [CVE-2025-21764](CVE-2025/CVE-2025-217xx/CVE-2025-21764.json) (`2025-02-27T18:15:29.903`)
-- [CVE-2025-21791](CVE-2025/CVE-2025-217xx/CVE-2025-21791.json) (`2025-02-27T18:15:30.053`)
-- [CVE-2025-21796](CVE-2025/CVE-2025-217xx/CVE-2025-21796.json) (`2025-02-27T18:15:30.210`)
+- [CVE-2024-44045](CVE-2024/CVE-2024-440xx/CVE-2024-44045.json) (`2025-02-27T19:30:33.180`)
+- [CVE-2024-47059](CVE-2024/CVE-2024-470xx/CVE-2024-47059.json) (`2025-02-27T19:30:33.180`)
+- [CVE-2024-53379](CVE-2024/CVE-2024-533xx/CVE-2024-53379.json) (`2025-02-27T19:15:48.927`)
+- [CVE-2024-57979](CVE-2024/CVE-2024-579xx/CVE-2024-57979.json) (`2025-02-27T19:15:49.077`)
+- [CVE-2024-8626](CVE-2024/CVE-2024-86xx/CVE-2024-8626.json) (`2025-02-27T18:47:11.020`)
+- [CVE-2024-9417](CVE-2024/CVE-2024-94xx/CVE-2024-9417.json) (`2025-02-27T19:30:33.180`)
+- [CVE-2025-21714](CVE-2025/CVE-2025-217xx/CVE-2025-21714.json) (`2025-02-27T19:15:49.637`)
+- [CVE-2025-21722](CVE-2025/CVE-2025-217xx/CVE-2025-21722.json) (`2025-02-27T19:15:49.780`)
+- [CVE-2025-21729](CVE-2025/CVE-2025-217xx/CVE-2025-21729.json) (`2025-02-27T19:15:49.920`)
+- [CVE-2025-21739](CVE-2025/CVE-2025-217xx/CVE-2025-21739.json) (`2025-02-27T19:15:50.067`)
+- [CVE-2025-21751](CVE-2025/CVE-2025-217xx/CVE-2025-21751.json) (`2025-02-27T19:15:50.220`)
+- [CVE-2025-21753](CVE-2025/CVE-2025-217xx/CVE-2025-21753.json) (`2025-02-27T19:15:50.360`)
+- [CVE-2025-21756](CVE-2025/CVE-2025-217xx/CVE-2025-21756.json) (`2025-02-27T19:15:50.513`)
+- [CVE-2025-21786](CVE-2025/CVE-2025-217xx/CVE-2025-21786.json) (`2025-02-27T19:15:50.660`)
+- [CVE-2025-21797](CVE-2025/CVE-2025-217xx/CVE-2025-21797.json) (`2025-02-27T19:15:50.807`)
+- [CVE-2025-25333](CVE-2025/CVE-2025-253xx/CVE-2025-25333.json) (`2025-02-27T20:16:05.073`)
+- [CVE-2025-27089](CVE-2025/CVE-2025-270xx/CVE-2025-27089.json) (`2025-02-27T20:18:12.583`)
+- [CVE-2025-27090](CVE-2025/CVE-2025-270xx/CVE-2025-27090.json) (`2025-02-27T20:18:12.583`)
+- [CVE-2025-27091](CVE-2025/CVE-2025-270xx/CVE-2025-27091.json) (`2025-02-27T20:18:12.583`)
+- [CVE-2025-27092](CVE-2025/CVE-2025-270xx/CVE-2025-27092.json) (`2025-02-27T20:18:12.583`)
+- [CVE-2025-27097](CVE-2025/CVE-2025-270xx/CVE-2025-27097.json) (`2025-02-27T20:18:12.583`)
+- [CVE-2025-27098](CVE-2025/CVE-2025-270xx/CVE-2025-27098.json) (`2025-02-27T20:18:12.583`)
+- [CVE-2025-27108](CVE-2025/CVE-2025-271xx/CVE-2025-27108.json) (`2025-02-27T20:18:12.583`)
+- [CVE-2025-27112](CVE-2025/CVE-2025-271xx/CVE-2025-27112.json) (`2025-02-27T20:18:12.583`)
+- [CVE-2025-27113](CVE-2025/CVE-2025-271xx/CVE-2025-27113.json) (`2025-02-27T20:18:12.583`)
## Download and Usage
diff --git a/_state.csv b/_state.csv
index 127d1e80f17..be74513cec6 100644
--- a/_state.csv
+++ b/_state.csv
@@ -156384,7 +156384,7 @@ CVE-2020-27486,0,0,6a48a3bc3b8904a914f358b9f36b04704611d104df6ebe0afc06d81cb4273
CVE-2020-27488,0,0,a789da6985c32fe71303a3c8648d395a4340eb30b4a324aeac3cbed17fc13067,2024-11-21T05:21:16.397000
CVE-2020-2749,0,0,204c08e538c0612df03860071036c687fae64a9a89dd6be206453188351aa733,2024-11-21T05:26:09.540000
CVE-2020-2750,0,0,54d22360dc78afd050cd1f0f3ad8d1977764665a9c177e0c888d5e49c833e96d,2024-11-21T05:26:09.710000
-CVE-2020-27507,0,0,f1d8da2b2aca1eb75c9414e4671c82c46b206bccb31ae689dca1b0bc575133ff,2024-11-21T05:21:16.647000
+CVE-2020-27507,0,1,3fd76f5785cda1e5bc5d07868f480e9680f4ec5490400bf93445d72e3d5ff296,2025-02-27T19:15:39.567000
CVE-2020-27508,0,0,a2d3b3d363fd951e6661976059a41596631cfecb60d3fff0ee3933fd08544326,2024-11-21T05:21:17.230000
CVE-2020-27509,0,0,c99f3812dd85a0af6b4fddd3cb7d7e79f326732927bd3a18258277c76782ce0c,2024-11-21T05:21:17.577000
CVE-2020-2751,0,0,54fd8c002888b1da0a5777901eeade24ce51d88724baa073a2471d08a8c658d0,2024-11-21T05:26:09.873000
@@ -159569,7 +159569,7 @@ CVE-2020-36831,0,0,ae8f26ef9609750991f1e998286064c227579b1afdf9132784b30dc7eddd2
CVE-2020-36832,0,0,5186f076be3cb1f90a1e086b9b9af14eeb2c9ef96086a0bd4bba43e7a2b8b7c5,2024-10-16T16:38:14.557000
CVE-2020-36833,0,0,b4e9334556d4d7ccf0d0299d6037ac055cf7e627215b6ec1ca8dd6066175544c,2024-10-16T16:38:14.557000
CVE-2020-36834,0,0,8767e0d8dd17f8fa39f1d41fd6c1b637f55d0fc0a5e3d958d439384a995574d5,2024-10-16T16:38:14.557000
-CVE-2020-36835,0,0,f11735848f539c48f9476c3d015a0757979dc3ad646f6bd58912f56d40260e95,2024-10-16T16:38:14.557000
+CVE-2020-36835,0,1,150e278c87f85c8e5180aa2c31bdaf5e2d9f25ffe9052b226ccfac83af870955,2025-02-27T18:47:11.020000
CVE-2020-36836,0,0,e0cacb5074a50a62341f8a30589563d3d3d98e6ebca57a6c11530fc11a8770a0,2024-10-16T16:38:14.557000
CVE-2020-36837,0,0,deb6727e5de21e3bafe32d4ef2eb7d4bc36e0621c64d353387fb4c4ca12e4d46,2024-10-16T16:38:14.557000
CVE-2020-36838,0,0,7037aa5c68e4ceaafa6ff6293973d22668209601d8f504e1fe7445e52cbfbd4b,2024-10-16T16:38:14.557000
@@ -187872,29 +187872,29 @@ CVE-2021-47624,0,0,592282086cd10fb104528f56f6839241d592ee1a02779ba76fa63df422729
CVE-2021-47631,0,0,99f982b2c7cf6d73a7115bc8bd2e1408634d1487c521542057d6f1bd3ab491d6,2025-02-26T06:37:04.400000
CVE-2021-47632,0,0,5e895e1b270063ce04332b3dcf6ad666f2de7aa1c8c979ab1b94d6c1119912b8,2025-02-26T06:37:04.943000
CVE-2021-47633,0,0,e8ede94dddd4afa481fae6a72ea901714b309ea0e517f71d7221a8ecfc8a8823,2025-02-26T06:37:05.060000
-CVE-2021-47634,0,0,997137038efe3ce8b46ab4f9d69543414d2a8ca03cd9a9fa4033f57403fefde7,2025-02-26T06:37:05.173000
+CVE-2021-47634,0,1,ab5528e0eb2af02ab96c66020cd494f91dad5818054db8322dad466bebb37b8b,2025-02-27T19:15:40.623000
CVE-2021-47635,0,0,903dcd5e119b780dd4b83cda32cfa2b7d12f11b33b8fbbde549d23e00230dc63,2025-02-26T06:37:05.280000
CVE-2021-47636,0,0,308e01075387dd21a1f0032e958fd4256d4515b97a1961071b6df02570cd6827,2025-02-26T06:37:05.377000
CVE-2021-47637,0,0,accbd28e4dd4cd7159adb0282ff618fc657acdd73a9f341f088325a31921ffa6,2025-02-26T06:37:05.477000
CVE-2021-47638,0,0,5e7abb40cfe2c98c4ad50fd0a40d1db4654cb01c7d3cfc07e22d8ddedce0cade,2025-02-26T06:37:05.580000
-CVE-2021-47639,0,0,7b8bf6d8de79b9ec3308660e6af583193d3b8426d1a982c24efb4b4726ff450e,2025-02-26T06:37:05.677000
+CVE-2021-47639,0,1,17b8fca6bf4b52114dbce5b1cb2899855c7b3b6e0c480e14fb1d194743173a7f,2025-02-27T19:15:40.773000
CVE-2021-47640,0,0,0398e595f0c4b65f1c48280cc62b93455da59c7e5711d281b52d0710648d26ce,2025-02-26T06:37:05.780000
CVE-2021-47641,0,0,9b6de44cce4467ff48e787d4d4224ac8afad2d242d24bcb035d5b985701cb352,2025-02-26T06:37:05.883000
CVE-2021-47642,0,0,d898c87cba3d04ef4614fdad90cbf21b9d829eeb76bccfcd178acfdae0950ed3,2025-02-26T06:37:05.993000
CVE-2021-47643,0,0,49993d0803a6553b25e355eeeda63314d4c0473475ffc2512d5f99ae93055d64,2025-02-26T06:37:06.097000
CVE-2021-47644,0,0,66153fbd04bc9da11c470999aec6056e193f18ad53b81b98da1f3c51df8957a2,2025-02-26T06:37:06.197000
CVE-2021-47645,0,0,702cecc66a772df959b018b65065c8d95527be4b0a17766b0b3641b5871b6329,2025-02-26T06:37:06.293000
-CVE-2021-47646,0,1,81333abc3b2a80d12c4d7ff59b9a11e55ba8d13768cb502e645619f02f9125c7,2025-02-27T18:15:22.093000
+CVE-2021-47646,0,0,81333abc3b2a80d12c4d7ff59b9a11e55ba8d13768cb502e645619f02f9125c7,2025-02-27T18:15:22.093000
CVE-2021-47647,0,0,4a6fb1577af80a36eaee67445132d90ad22f4abdaf4d4a0ef53bea402a07201f,2025-02-26T06:37:06.490000
CVE-2021-47648,0,0,8aee38a226cc739f36deb3d3942f718605290d671b5efbdfb2822bc34a6474cf,2025-02-26T06:37:06.597000
CVE-2021-47649,0,0,b92abd3e016e981c7b4a21493012d09b454ec48ee442a9a06f04ee8d1e46da3e,2025-02-26T06:37:06.687000
CVE-2021-47650,0,0,c1ee21a8927c50452789b434f4c6a27549f5b0e6efcc84424b87b988ac45220c,2025-02-26T06:37:06.780000
CVE-2021-47651,0,0,38352f07671e2fb89dff6662b2a7803610a4f0830322bddb244e534cdee3f770,2025-02-26T06:37:06.880000
CVE-2021-47652,0,0,5dac3245c4082a8ac667646f369373df0679d08aaa4be0a5117b4ffb032ce1ff,2025-02-26T06:37:06.973000
-CVE-2021-47653,0,0,8bb339fc3c0fd581e138c4f6cebfab0c737e874ad8386f9204dacb0908a9611e,2025-02-26T06:37:07.080000
+CVE-2021-47653,0,1,04eaa3d5f4fd396b8e04c0075027018d64abbfa209a016b6c86bfefccecb9148,2025-02-27T19:15:40.917000
CVE-2021-47654,0,0,6bf7742a801883c2038de658f203dbb939a9a5692a812481f2e91ec4eab50db2,2025-02-26T06:37:07.170000
CVE-2021-47655,0,0,07a286b5437b0ab0bbadc4d0248c6f10174a5456a017ed0c718b269cf986c1b4,2025-02-26T06:37:07.267000
-CVE-2021-47656,0,1,e2177c77ee4fe6ea315be5da13c2e4035835d0163562b408590e31a286ffa4f7,2025-02-27T18:15:23.133000
+CVE-2021-47656,0,0,e2177c77ee4fe6ea315be5da13c2e4035835d0163562b408590e31a286ffa4f7,2025-02-27T18:15:23.133000
CVE-2021-47657,0,0,846313dc19371aad222a353ce5fa52dbc80099cc31d4f0feb9906fdd00c2987f,2025-02-26T06:37:07.467000
CVE-2021-47658,0,0,026227a429c1675cb95b08438f19b7f7b602999a92b3b51e891ff1a0b2001be2,2025-02-26T06:37:07.557000
CVE-2021-47659,0,0,f9dc004467c8894a72bb5439b7f910f7feda091452d5992ee661458d581914df,2025-02-26T06:37:07.640000
@@ -195109,16 +195109,16 @@ CVE-2022-25763,0,0,cb391d4c483d6954bc71de45db0826e9934c6a6e5dcf2bead8ddc729ed578
CVE-2022-25765,0,0,6a5cb0b2bc9975cd474e10128782a150c0921aac2d2713e32ddd08483ff8435d,2024-11-21T06:52:57.720000
CVE-2022-25766,0,0,7650bcdb856cf60ed50e3b2d316e5b1587fb3571a3403ac15b613de5951e2fa3,2024-11-21T06:52:57.857000
CVE-2022-25767,0,0,dce784a783999f17de4573c017bb2bbeb586039a466cddde0cb825c310fefcc3,2024-11-21T06:52:57.967000
-CVE-2022-25768,0,0,65798d677913ee02cc1bd77465d3831de65725b0f33346038e9521443ce9a629,2024-09-20T12:30:17.483000
+CVE-2022-25768,0,1,6aab1a95e1c69778ecbb26fc229c01ef423f5e4e35ba7c6193d932a305454338,2025-02-27T19:30:33.180000
CVE-2022-25769,0,0,0998a8c2839e5b963472953b8a6e7b675aeed2823f1e1b450c7dcfa1d35a8ad4,2024-09-20T12:30:17.483000
CVE-2022-2577,0,0,7dfb4d9179f1eefcc863c8a3e76107909150e1945e894d94650c4a3f70597e2c,2024-11-21T07:01:16.753000
-CVE-2022-25770,0,0,510fc679d9e702469c74e16d4311f3e48d75da55ed647a36d826a76f23b3ba6e,2024-09-20T12:30:17.483000
+CVE-2022-25770,0,1,c192cbfb1384ff5dd4b005d6d88808cffaeeaa59c4244fc9977b6db65b29c98f,2025-02-27T19:30:33.180000
CVE-2022-25772,0,0,ff796297ad7865332e00bb2b318127a389900f15aa53f8502eeaf569afa498b5,2024-11-21T06:52:58.343000
CVE-2022-25773,0,0,00d32a7f292ee7b146bf4498aafb7466139f5e577695a6511ef83b462882762a,2025-02-26T13:15:32.550000
CVE-2022-25774,0,0,bd380684d32ffa9cd4640164928b773a3662f874edc7e0d020930c6456c349a1,2024-09-23T23:21:35.443000
CVE-2022-25775,0,0,86cd764b6a567381983af3ef2ac724e63b9fbc2964b23fee64b226f75093e044,2024-09-23T23:22:15.763000
CVE-2022-25776,0,0,b92a32835cc3936cfcece435820b9a30ee61228c21cc5409787525b6dbc22604,2024-09-24T15:19:46.117000
-CVE-2022-25777,0,0,cebd6e7ee2a9bb3a49e96f8784fc2c69052d22274655c1dd696f05f7a4b5c045,2024-09-20T12:30:17.483000
+CVE-2022-25777,0,1,7a5f526d1033d6ec2e4c59a8c46f997320be9835df73e3c9270077c7ff67cc0e,2025-02-27T19:30:33.180000
CVE-2022-25778,0,0,29dba0e52f5c0ac7c80ebc5cb40e92cfcef54ecfb94f30e4c7a652e8c3bd3c69,2024-11-21T06:52:58.800000
CVE-2022-25779,0,0,6c0d96ba8407178a51fcefcaf2b0012a724e485cce8626ebeb568fd03432c05e,2024-11-21T06:52:58.933000
CVE-2022-2578,0,0,4b44e477ec40385f61f718f3e29e0b3ec4afbb832d6a60436222681a370e7a8f,2024-11-21T07:01:16.887000
@@ -208910,7 +208910,7 @@ CVE-2022-43125,0,0,52955030ba9f39507a30dc5358732311dc919157a079e9c12e2f9c1425bfd
CVE-2022-43126,0,0,32318097da34f209f165497e141dbafa8ba796e007893cd3dca77840fb1731c1,2024-11-21T07:25:58.040000
CVE-2022-43127,0,0,92fe347fff41b643a94872eab09e93681058f003e07c2555a4983f742d9d485c,2024-11-21T07:25:58.200000
CVE-2022-43128,0,0,f007c9f0be159632f9e69ff9af025b1f1f904f8a4fea112fe37a153e0ec1a85e,2023-11-07T03:53:43.393000
-CVE-2022-4313,0,0,283c04b430cc0af18442ad31ef3a5f65594be830dbc0436d6217a46b9f303877,2024-11-21T07:35:00.820000
+CVE-2022-4313,0,1,086460c5bd76f1575461d5a5457e280fc6c4e01652ae257ce74e884478d4e479,2025-02-27T19:15:47.290000
CVE-2022-43135,0,0,5f52f089226dd60a83b3618a46f3f76a0f0a1b462fd33efd8408bc88757a6756,2024-11-21T07:25:58.380000
CVE-2022-43138,0,0,76d290a775639434284c4f96d9c851e3f696d343fa7835c0756314b22ca4d30a,2024-11-21T07:25:58.543000
CVE-2022-4314,0,0,b2d7e2c2d34983b5612bbe613ee90b322bcf58c270b648e62d25d8832fa87daf,2024-11-21T07:35:00.987000
@@ -212305,7 +212305,7 @@ CVE-2022-48107,0,0,ea86b4df2888c77620f092846cd1660fa21ca354f29faf5cf44596d14ec92
CVE-2022-48108,0,0,8d4f3b9b9efdf48cd29c33c16382d7f14321ac3ec536a714fd38fcbac269811b,2024-11-21T07:32:50.467000
CVE-2022-4811,0,0,c9ad55ad708c43d2e552a2a5cff5f2a41a15cb1ba0ee8006d753aaa8ca172523,2024-11-21T07:35:59.310000
CVE-2022-48110,0,0,763d20be13ef5dbfe0eb13693f978f5479f04cde867846fcaa47508cb6f269a5,2024-11-21T07:32:50.707000
-CVE-2022-48111,0,0,a1cb1fc81e08fa0c1f2dfe6507c12d7b4c9489484fa441f778432c8787d2ed65,2024-11-21T07:32:50.970000
+CVE-2022-48111,0,1,6d90f28a337f6a00ea5e92197007edfb483aacede200ab8d61a3d9120f75dc78,2025-02-27T20:15:34.833000
CVE-2022-48113,0,0,b0d683d068557c5969d1f62219ce4bf5e3277c4d0cb6043a6977a60f5c15c44d,2024-11-21T07:32:51.957000
CVE-2022-48114,0,0,efe3af806680c265fe7c78edb3e8c4369f4d49d721d84f4e91d3192d71856932,2024-11-21T07:32:52.123000
CVE-2022-48115,0,0,15206669169e7037b99d6362d516c2e392b240a83497224679be0ab05586b8a0,2024-11-21T07:32:52.267000
@@ -212537,9 +212537,9 @@ CVE-2022-48392,0,0,b9fe3ba20fbbdfc5d1b9633d462e670d9b83c0269326581c320b3af6ba985
CVE-2022-4840,0,0,8593d435f1bfe4de06d5751803d143b53df092b88164a311eec3d96d433c7a2a,2024-11-21T07:36:03.047000
CVE-2022-4841,0,0,aa0be02bc0f514a14ceab97461cd0599b9d6992ea08fddafb73f57498c188781,2024-11-21T07:36:03.167000
CVE-2022-4842,0,0,5f968fb2edae3fdba3ae88b74baa37078b628e670ae5d2f7c0c597f4c2874591,2024-11-21T07:36:03.287000
-CVE-2022-48422,0,1,21280efffd732310e96aab7ce559416bfc11e676f2fac7503fda3c38abd1c1c0,2025-02-27T17:15:13.490000
-CVE-2022-48423,0,1,9a382a8f9283e9cc20387d0ba6add00de2aff03f57ee8431397c94b87413c240,2025-02-27T17:15:14.530000
-CVE-2022-48424,0,1,9da47869864ec90be63e396d6253bb25acaf19379b79f5fbbeffac650f050c1b,2025-02-27T17:15:14.697000
+CVE-2022-48422,0,0,21280efffd732310e96aab7ce559416bfc11e676f2fac7503fda3c38abd1c1c0,2025-02-27T17:15:13.490000
+CVE-2022-48423,0,0,9a382a8f9283e9cc20387d0ba6add00de2aff03f57ee8431397c94b87413c240,2025-02-27T17:15:14.530000
+CVE-2022-48424,0,0,9da47869864ec90be63e396d6253bb25acaf19379b79f5fbbeffac650f050c1b,2025-02-27T17:15:14.697000
CVE-2022-48425,0,0,93864fe860b2f013079492f9e8dfb06bf67caceb010ee43ab9ab04d733583ed7,2025-02-26T20:15:10.493000
CVE-2022-48426,0,0,e18aebb1b534c2a05d63e4f30be752d5746fff5a412fd6531155a734c44d5f7f,2024-11-21T07:33:19.603000
CVE-2022-48427,0,0,0326e52456f97bd2c754bc3da2f531e8b133551d82bbfc3aa6700b24a0427d58,2024-11-21T07:33:19.720000
@@ -213161,25 +213161,25 @@ CVE-2022-49043,0,0,7174066d58537267d7d2a315cb17b3519790e5764e973f2a3d77df9ee2584
CVE-2022-49044,0,0,2203b8b9482d29edc4f6aff384e0ad33203f328bb0b95fe82526cee32393bf09,2025-02-26T07:00:41.680000
CVE-2022-49045,0,0,8a6705459c2b19facd1e9be555aebc389ab445796af96eac29f4caf2d176e70e,2025-02-26T07:00:41.790000
CVE-2022-49046,0,0,df92e917df618b803c8732672c9d86db95e812afeb62618fc8a41440304058dc,2025-02-26T07:00:41.890000
-CVE-2022-49047,0,1,7d1778a660a2d6b6fcbd30662171589ccad6a73fa527f91b3cd6e7bfeeca8f42,2025-02-27T18:15:23.557000
+CVE-2022-49047,0,0,7d1778a660a2d6b6fcbd30662171589ccad6a73fa527f91b3cd6e7bfeeca8f42,2025-02-27T18:15:23.557000
CVE-2022-49048,0,0,dce93d94c79111e32ab37587412c6a76dfde7a46784a34639bf07f311cb6de42,2025-02-26T07:00:42.073000
CVE-2022-49049,0,0,cc4fd9097291bcd9e1239a38d0b84ca4e92d4c321be4d68025addd2f2376adb7,2025-02-26T07:00:42.170000
CVE-2022-4905,0,0,71313ae270fb5be33f7aff9db48d95ece499a953689009ab679dec981b993cf5,2024-11-21T07:36:13.077000
CVE-2022-49050,0,0,58e12274d428d15945ce3440723dee7420e41a58d259189cdab143af8b2a9975,2025-02-26T07:00:42.270000
CVE-2022-49051,0,0,441124ae74f7ae0301f5df6bee558e7250d29cba35895caa2a37efbda1850889,2025-02-26T07:00:42.363000
CVE-2022-49052,0,0,f357a243ec74b7d536892c720bcfc02f1e5b0bf9f945464055ee585c784b09ba,2025-02-26T07:00:42.463000
-CVE-2022-49053,0,1,31f7eedcf568c51249c2c854957cbfca5a677f41384e21ad06fb4587fca7c79c,2025-02-27T18:15:23.733000
+CVE-2022-49053,0,0,31f7eedcf568c51249c2c854957cbfca5a677f41384e21ad06fb4587fca7c79c,2025-02-27T18:15:23.733000
CVE-2022-49054,0,0,a90a230a571286a4dd850a83d1d43fdbdb6ebc0c58e98aade1b252a8e6ae3ec0,2025-02-26T07:00:42.667000
CVE-2022-49055,0,0,711b79189c05d6b8a94fbeaa76941666c2138d3bd9e8e25675e11215e155439a,2025-02-26T07:00:42.760000
CVE-2022-49056,0,0,65735eec858202f4a4989efbef9b24a9987242e501c83850a0b5e13c469a13ee,2025-02-26T07:00:42.863000
CVE-2022-49057,0,0,6407e6574c3a7cbcba9791dbcd18089af1ea2efe0d26a43ae7a6480f3fb5b09e,2025-02-26T07:00:42.957000
CVE-2022-49058,0,0,c495e58cd47ec4ba2f99ad0440daae9be893f6c40c7a7903a23399265fcd0906,2025-02-26T07:00:43.047000
-CVE-2022-49059,0,1,149e7a7b8cef0a8c5f3ed0f1703d5bd32ccaf156f0526bd1e4a3bea5b7fdb3d1,2025-02-27T18:15:23.913000
+CVE-2022-49059,0,0,149e7a7b8cef0a8c5f3ed0f1703d5bd32ccaf156f0526bd1e4a3bea5b7fdb3d1,2025-02-27T18:15:23.913000
CVE-2022-4906,0,0,a823b4bbfbbc923f2df028a42581e18917821bc8c8d60008f8440a61828e4ecc,2024-11-21T07:36:13.207000
CVE-2022-49060,0,0,4bb12bea527861d358c3fecc8e34f58edf94fd37a9267a859bc512d78e3881d9,2025-02-26T07:00:43.257000
CVE-2022-49061,0,0,467c122603b899cd6bdc9ce5b74a1cd7e2c8c3cebba5c726ba766201c25bd453,2025-02-26T07:00:43.353000
CVE-2022-49062,0,0,caf319ab53e98905987a4958e4977fce76daf8c905439205294f21028e096c05,2025-02-26T07:00:43.450000
-CVE-2022-49063,0,0,5df9bdaebdd4ccf05e8aa6544f3e0758688c7c0b3ee2ff8afcdd3c67e017189e,2025-02-26T07:00:43.547000
+CVE-2022-49063,0,1,2f12e34370bf7c85c19bcaab2ed2b991f00af7b953da0ddd12a84c17daa8f6b9,2025-02-27T19:15:41.070000
CVE-2022-49064,0,0,b8d94ded4a909cd311e8fe26e7c2d92130c47dab0113897b222428477202f93d,2025-02-26T07:00:43.637000
CVE-2022-49065,0,0,15a8d0bcb27aa029d913581b6edaf6ff6fd6d0358ed10d1475820c871885ea5f,2025-02-26T07:00:43.723000
CVE-2022-49066,0,0,1b8bf54835c7216314b35e861b33ded5f585b9f6a5a98c16eeb435a92278ef00,2025-02-26T07:00:43.820000
@@ -213193,26 +213193,26 @@ CVE-2022-49072,0,0,a7f651188791101ed667f6a27ca5df2887b2a9a1714747976c03449f11e95
CVE-2022-49073,0,0,fc90533268682274c099c54ecb52b40d1e1e09d91562032c561caaea2b065161,2025-02-26T07:00:44.647000
CVE-2022-49074,0,0,8dbcde2964413863936318f4d761bfded88505acf89e2590978c7021d405e14b,2025-02-26T07:00:44.750000
CVE-2022-49075,0,0,e401caab4e2cd50dd873316e76ce4663c9dd4d2d8b9eb8c7f55dfc2e75eceeab,2025-02-26T07:00:44.847000
-CVE-2022-49076,0,0,89cfa60bd1a594f17795b2fa89ee616d19983b4b8ee7c68806fc76f90dab4bc4,2025-02-26T07:00:44.943000
+CVE-2022-49076,0,1,f99f45adbf51e6e5f03b26f3f09534e5233c1511be722a10480f66c61a4ff671,2025-02-27T19:15:41.213000
CVE-2022-49077,0,0,d5181cd5d0207ec53060d8b12233fdcc4d4124acd7e3b5f2090725e903fea526,2025-02-26T07:00:45.043000
-CVE-2022-49078,0,1,59c353940c9ac703c38116322d815635185f119ae62f9a1e1f5b3d647bfef23b,2025-02-27T18:15:24.090000
+CVE-2022-49078,0,0,59c353940c9ac703c38116322d815635185f119ae62f9a1e1f5b3d647bfef23b,2025-02-27T18:15:24.090000
CVE-2022-49079,0,0,7d6502bafddbbe656bf2b3504d76ba9a41447c925885bd993317c0a042aa4d1e,2025-02-26T07:00:45.250000
CVE-2022-4908,0,0,383323d7ed3fc2aa1cb27670a39714ac299a31d311bbc6cad999a9d72854959d,2024-11-21T07:36:13.443000
CVE-2022-49080,0,0,46daf799a71f3d91f9d3c5a7bd3b03a530669dfb3fb9f38744947062c6ea9df1,2025-02-26T07:00:45.347000
CVE-2022-49081,0,0,ad31b68330d4f1ab28c316884755bef117d87cc1a44e7ad06c2907b8043601a3,2025-02-26T07:00:45.450000
-CVE-2022-49082,0,0,68f5ac358c482a28bcd5462e81311715d7a463ba5421913784e5509d42dcf3e5,2025-02-26T07:00:45.540000
+CVE-2022-49082,0,1,13c05f545b73ccc4dc2e9ef5b0df626c4be1cb4a6a99de51ff0312e6e9d7356f,2025-02-27T19:15:41.353000
CVE-2022-49083,0,0,b535d105f748518c61bd17f72aa6984343610371329e9f2e70886c302c14d784,2025-02-26T07:00:45.643000
CVE-2022-49084,0,0,14f466a56984c6ca4bf531f864ff28aeba45d097692d3c51bbd13e3ecad54f75,2025-02-26T07:00:45.737000
-CVE-2022-49085,0,1,53522bf6db469dbf0c1beee8c1f5710d93802f712a48a599c1cb79dfaad38e86,2025-02-27T18:15:24.270000
+CVE-2022-49085,0,0,53522bf6db469dbf0c1beee8c1f5710d93802f712a48a599c1cb79dfaad38e86,2025-02-27T18:15:24.270000
CVE-2022-49086,0,0,4a98f5f6d7ddb7bd7c15ae6ecf682771da4fdfa80758e54b5fc2b9027660505c,2025-02-26T07:00:45.940000
-CVE-2022-49087,0,0,25a7304c42dfb7da9a337944f1bdde2b59fa7a2cd8c7f7952073163a16a8f61c,2025-02-26T07:00:46.043000
+CVE-2022-49087,0,1,0f0474969e0f9cf7ff3a4493d2c67524869b1e48b29f3fffe71d40895dbec01d,2025-02-27T19:15:41.493000
CVE-2022-49088,0,0,3c74fad7622594426e2a6f2c92cc3996d50a4b1ec096da3568e9817122efa5ff,2025-02-26T07:00:46.143000
CVE-2022-49089,0,0,ad0db0ee42e5d6f1b9d7f541e2a7400e81cba717ab56d786c63f5bd86e56c706,2025-02-26T07:00:46.240000
CVE-2022-4909,0,0,28e150195670658dbb597d2ae16b58acadec9146b9a0e6f41e387727d58a210b,2024-11-21T07:36:13.560000
CVE-2022-49090,0,0,0d8160f98a6b6b1ea1af6921f1498cb9a49f6a768b2c5479a63ab89260b4e208,2025-02-26T07:00:46.337000
CVE-2022-49091,0,0,e348d433bc22cfcac4cb8378cb8a6e0e4673196c953cc3c3311682e67536a792,2025-02-26T07:00:46.430000
CVE-2022-49092,0,0,ca6b3b2829ffc3816a81b270c4631325ea0ab0edf905af210e97dbd63ae59d47,2025-02-26T07:00:46.530000
-CVE-2022-49093,0,0,3254a3cec8018dfef23d047f3bbbadcbcd3ddcb4a878faf4eff6533ffadd2793,2025-02-26T07:00:46.633000
+CVE-2022-49093,0,1,e2ebba6c8d7652acd4ced5cc3169efe99c09593cdb4a270bd01955e1a6a77f78,2025-02-27T19:15:41.640000
CVE-2022-49094,0,0,569eb8d167cebb85be582cb3ea644ceb7ba83cd357ab869b4db3f97faa20d392,2025-02-26T07:00:46.747000
CVE-2022-49095,0,0,8052384cff0087ba80330438f6adf142a2d616e312868814bbf1d228f4e703ec,2025-02-26T07:00:46.887000
CVE-2022-49096,0,0,9e70a354621e717fb799b5e2efcb9cfa1dceeabfbfa379817b72bba3a6950e57,2025-02-26T07:00:47.010000
@@ -213232,7 +213232,7 @@ CVE-2022-49108,0,0,a0a957c05c41d83b387a7118ea9c4365ec02159e32b283814a87c36c6361e
CVE-2022-49109,0,0,e6d0b9bd915508b28af80a4c7d6ccc3b8b397bbd7940345a4920d25f83abea9d,2025-02-26T07:00:48.273000
CVE-2022-4911,0,0,584ace30c9064e713cd09c96d4db8b9174c37337aaf32c92be96843fae8619c7,2024-11-21T07:36:13.780000
CVE-2022-49110,0,0,79c260571f84dbaaba1acd67d8b4c69ef5c796cbdaef6f29e26bd60985fe050a,2025-02-26T07:00:48.363000
-CVE-2022-49111,0,0,e385206268b80477262478d1a05be332efe1d55dd82d973c1d8f594b03c39120,2025-02-26T07:00:48.470000
+CVE-2022-49111,0,1,0f73ff8884819a3d31422b81d543b4b48c8e71296c668745b64672b525f0720c,2025-02-27T19:15:41.783000
CVE-2022-49112,0,0,88d9fda802e3d333c77034ca297f0f2e603b1f6963b81a274a63fd1e572aa4f1,2025-02-26T07:00:48.577000
CVE-2022-49113,0,0,2be1e4b644c51d9a697b6902d895476a4a9aa2c37dd3c2166099056b889228fc,2025-02-26T07:00:48.677000
CVE-2022-49114,0,0,e2d1a5ae7225acfae6868fb2a87d99ce964c5ae85a84ec15313490959eb1513f,2025-02-26T07:00:48.773000
@@ -213249,9 +213249,9 @@ CVE-2022-49123,0,0,0f6205efd2625366cf7436d756f0bce5575dcf365f7b802178450f46c6d04
CVE-2022-49124,0,0,ddb7323e81cfead4ec852710ca5e799576d579b7ce58494bbd001811570b7f2c,2025-02-26T07:00:49.740000
CVE-2022-49125,0,0,a982edad32d5eafe0ca6d4f94e135990db26132a1278a77fa1ffaf00a4798ec9,2025-02-26T07:00:49.837000
CVE-2022-49126,0,0,2a9cb2772331805a762b82db8a43bc63317eb5f0e87b6d4185ead63793578fec,2025-02-26T07:00:49.927000
-CVE-2022-49127,0,0,335a2536334a98c2a26ab04e6c68f4a7397483e654da5199afc0918995c7907d,2025-02-26T07:00:50.023000
+CVE-2022-49127,0,1,f7a75f7608c19258496d1280b50887682decc91ae508aa0b9c144671f52b5f6c,2025-02-27T19:15:41.930000
CVE-2022-49128,0,0,f6d7d91badfbf690a36067f746ef767b9fc3d17309065fd17e24dcd87e93d48d,2025-02-26T07:00:50.113000
-CVE-2022-49129,0,0,635187c24833be1421fd147a77f0a2f9a5dd731a5b7ccd4819fcdebd73d3f567,2025-02-26T07:00:50.203000
+CVE-2022-49129,0,1,8d4ffb98bdfd20948b0b488967a29ada4979fe1906add69d16b32b588153d466,2025-02-27T19:15:42.063000
CVE-2022-4913,0,0,e8dbca49e3518f819fca949d98a7bb3175c26403fd3fd8fca017d6ea88f023bf,2024-11-21T07:36:14
CVE-2022-49130,0,0,855be5ee8cfafb1f6e1d2efc1041ebb62cf40c9b592639b6d4e053b9a594738f,2025-02-26T07:00:50.300000
CVE-2022-49131,0,0,88bf638620237e97a70660d8266662d3955359e4bdcfc54ad9f97aeb6cf8f949,2025-02-26T07:00:50.393000
@@ -213259,7 +213259,7 @@ CVE-2022-49132,0,0,dbc2403edcf0fe8a94fd025236efc808af0828e502ae9ccba3138d68e3caa
CVE-2022-49133,0,0,9dfbea63135d73ab468dcdf665efdbe36b2f7e6b59dc0a92194b0e05ab85369a,2025-02-26T07:00:50.590000
CVE-2022-49134,0,0,81b15360b4c0149d855216e894c9ac4ea22db71898a0c845e6b00506f605b434,2025-02-26T07:00:50.680000
CVE-2022-49135,0,0,30e5827757074130e4c037044d6b4c5ed4efa2bc2acf898d046f684b3bda629e,2025-02-26T07:00:50.770000
-CVE-2022-49136,0,1,3a6e196be9a979eb3f13fbe98b61a934baccb1a49c982c9d13381462b0514b2a,2025-02-27T18:15:24.457000
+CVE-2022-49136,0,0,3a6e196be9a979eb3f13fbe98b61a934baccb1a49c982c9d13381462b0514b2a,2025-02-27T18:15:24.457000
CVE-2022-49137,0,0,5b1746b2ec50f0dc2ec6bf0272d0a3183c707ace26571c91a8fa2971e0704a0a,2025-02-26T07:00:50.953000
CVE-2022-49138,0,0,8437106ee0a6fabf2a2246cb985b009354cf0467f29aadb6b0d556c8df8dbb11,2025-02-26T07:00:51.047000
CVE-2022-49139,0,0,67a318aa5642355e534ed7df583fdf13225b0e9fcaad79c9392e0a29c74de0b2,2025-02-26T07:00:51.133000
@@ -213294,7 +213294,7 @@ CVE-2022-49164,0,0,4c018abbd4f1d7b4615bb0a8d9f779494949e7d5d29037218fcc59fcf71a8
CVE-2022-49165,0,0,5b5aded0c2c4b6917f2f05ca4bd91e354456b639308e0403336f36321763f8c2,2025-02-26T07:00:53.653000
CVE-2022-49166,0,0,f716bd9e2ef4079667efc9f9b5602d4c08fd289203ba1e49ad0071f40d12fb4e,2025-02-26T07:00:53.743000
CVE-2022-49167,0,0,04d7f51f90134d787c73cd94a8d77fff68eb60624dfb8a4c40a84d343ddd3b15,2025-02-26T07:00:53.837000
-CVE-2022-49168,0,0,a5873977864e9d2755cccbcc804c0a1d186c272eff4b632468d6ee2a6be08977,2025-02-26T07:00:53.927000
+CVE-2022-49168,0,1,cbf6789740344e6a1d75a16a1916eac6b32a7b822d902968ee2f27f14034e9bd,2025-02-27T19:15:42.200000
CVE-2022-49169,0,0,993d6d150f2c70adbc43b8ad1b935b02a15f3e62cfaaaff28da594efd829502d,2025-02-26T07:00:54.017000
CVE-2022-4917,0,0,632226f8b02c5f8d00ce4b404529b7905bf41638914202b70d798cef2843a50d,2024-11-21T07:36:14.493000
CVE-2022-49170,0,0,7c87709422d3736ed7539b49fe445e546ec9a8855c9bcd6cee5b8b0955a77a06,2025-02-26T07:00:54.110000
@@ -213303,10 +213303,10 @@ CVE-2022-49172,0,0,b5423a2e59351877d885903dca16c080a58678a47ed9e789946258ece2737
CVE-2022-49173,0,0,2509ad7a7410304e8dee4a2119e65dbcef56f8c7a515bcaaefbcdcd41bc84cbb,2025-02-26T07:00:54.407000
CVE-2022-49174,0,0,c5143b5d6a5ad95c0897b099c6ad5b5c75776be77e7f8750fdca7fbc8f85fcc5,2025-02-26T07:00:54.503000
CVE-2022-49175,0,0,228d68467849fba76d75f7e13b031d387e5652a3ca9fcfa660013ed7e9ea9433,2025-02-26T07:00:54.600000
-CVE-2022-49176,0,0,287ccead8e8bfa076a8ace1a10c2d3ec78fcd16359af3d3f6cc2d1b4f138b771,2025-02-26T07:00:54.717000
+CVE-2022-49176,0,1,b109142f08ed4c01b229bd63542241e4bed36c7aed4710a65ec10475963ff792,2025-02-27T19:15:42.333000
CVE-2022-49177,0,0,6b65621d4d4e4b3576467907edbb3e69f1f42092ce46e543648e695ebb25bb49,2025-02-26T07:00:54.850000
CVE-2022-49178,0,0,540ea6935b001f7814b720e898282c2b2351a93778993fb999959fd695d03799,2025-02-26T07:00:54.947000
-CVE-2022-49179,0,1,a8b68954ee186c443b509036cfabe6155a1873e7f4b5451009933f662f631349,2025-02-27T18:15:24.623000
+CVE-2022-49179,0,0,a8b68954ee186c443b509036cfabe6155a1873e7f4b5451009933f662f631349,2025-02-27T18:15:24.623000
CVE-2022-4918,0,0,c4f03a0a064390463bddfe1751a6538e5a2ff20b187ebaa73606b1a29097d2ab,2024-11-21T07:36:14.707000
CVE-2022-49180,0,0,c4f7dcfa900ffd3b7fc79efef06511387ee33662a968f19a1872650754b01ea0,2025-02-26T07:00:55.137000
CVE-2022-49181,0,0,8a4c3e6b9ca8dc4d9b8f15b356b1ef8d9d688badb48456bd7a0c47c0d7df2b88,2025-02-26T13:15:34.087000
@@ -213355,7 +213355,7 @@ CVE-2022-4922,0,0,845ac042dcd4b5ec74159a973e2efc3ff642abc4a48ec290dcd8ade6154e85
CVE-2022-49220,0,0,1bf5f8f544935453bef31a4ecd67bc2f5fc84f04f266b3fb29793456794b39a6,2025-02-26T07:00:59.070000
CVE-2022-49221,0,0,352783bcb84076ace1f7ef63620bfe9e1964c9ca9b7dd8be35eaa8fad9d738cf,2025-02-26T07:00:59.167000
CVE-2022-49222,0,0,ed5a14b3e6a68cafe149e4495bde341503683b79a937e4a5ee07623212814cff,2025-02-26T07:00:59.260000
-CVE-2022-49223,0,0,cc6832b4d98049880aa8227bcfe078e9047c373148b88dd30abbb6cc14ac0d67,2025-02-26T07:00:59.363000
+CVE-2022-49223,0,1,cc7c44e646ae0d91256fac5d3dc5e1e562bde1153c9f71dffad2ff7fdcd4fe5b,2025-02-27T19:15:42.473000
CVE-2022-49224,0,0,0dfc7b315cc0a9196858b5d3f6926d708463358bbaa76ec923c9b3dd108f2809,2025-02-26T07:00:59.457000
CVE-2022-49225,0,0,b5ecf7157dc9210f63c6a5dee34c00119ffca9cebc209406194aaf48bd53963a,2025-02-26T07:00:59.563000
CVE-2022-49226,0,0,bd6335a0bc58740c540347599a6264847ee35bc10cfabffa0304b21e310a4321,2025-02-26T07:00:59.650000
@@ -213369,9 +213369,9 @@ CVE-2022-49232,0,0,a849a5af0f2665becdc85b37dff49905779a3369327d646829812367ee2d9
CVE-2022-49233,0,0,989473ff019b48f7fedcb6ca5234b9d536fe697b8f704b4dc8ba114fac2b3542,2025-02-26T07:01:00.317000
CVE-2022-49234,0,0,f62cc34ce31e4e24952f3777b23cd8a302adea934499ccb930053f4ce557e087,2025-02-26T07:01:00.407000
CVE-2022-49235,0,0,a8562abcc73c5755f99522d5e5a2926b0f28fa8852556afc18375ece1f0e830e,2025-02-26T07:01:00.500000
-CVE-2022-49236,0,1,32bf91ac4bb1f729eb140d1e40b8418ff861d90b05941f96def5a2c1105fb0d0,2025-02-27T18:15:24.803000
+CVE-2022-49236,0,0,32bf91ac4bb1f729eb140d1e40b8418ff861d90b05941f96def5a2c1105fb0d0,2025-02-27T18:15:24.803000
CVE-2022-49237,0,0,4a10d2383537f0fd099deaa353fac85143df257802f812afe3fea7b11ae63d36,2025-02-26T07:01:00.700000
-CVE-2022-49238,0,0,f8f096e40637e62b88561ae60005748422c0d5fa9fa70846a1d61ad2f02f9b9c,2025-02-26T07:01:00.790000
+CVE-2022-49238,0,1,3eee62dfdb8408bb1db281710d153d7d7efec2ed2dc81082c88a342a4155f76a,2025-02-27T19:15:42.610000
CVE-2022-49239,0,0,4bf4920068aecd0cedc8315cc12e0e84e08834779ac85c08ccaf45f8bf7d5a96,2025-02-26T07:01:00.887000
CVE-2022-4924,0,0,478cd65cc39d1a4a12365dd984816c2000e169260e72489e81fdf56aab2bfb16,2024-11-21T07:36:15.747000
CVE-2022-49240,0,0,584a9751d2751ebfe606ed3b65f602333ef1499b0061b067a87e94d7f3e3b907,2025-02-26T07:01:00.977000
@@ -213393,7 +213393,7 @@ CVE-2022-49254,0,0,de82d9872498309fba0961065d7c690e1307c96fbde02d13b1eb6ebc2cc90
CVE-2022-49255,0,0,1584f53b5b4d9ef816abcf04b2bb6d64dffff362d61885f8d6da57dc7a626afb,2025-02-26T07:01:02.397000
CVE-2022-49256,0,0,0983d9535fb4bc87454ae32f72810fa5245847a82dce93daf9a7ea5f7d270e4e,2025-02-26T07:01:02.497000
CVE-2022-49257,0,0,aef59c8f6c4daf98c543c8a8c965310d4923bf88140e870fe577c6f82fb653ad,2025-02-26T07:01:02.597000
-CVE-2022-49258,0,1,8a58ed784b2f48408c2977a6e1bb161c45d66f3dda49690122c0d878b60d5794,2025-02-27T18:15:24.983000
+CVE-2022-49258,0,0,8a58ed784b2f48408c2977a6e1bb161c45d66f3dda49690122c0d878b60d5794,2025-02-27T18:15:24.983000
CVE-2022-49259,0,0,629cfec34602a0e6688d6ecee568bc7c5e4cea8d0bbb2257e31c91e935220a58,2025-02-26T07:01:02.850000
CVE-2022-4926,0,0,97f811d640cb5b71af561412ae9269e091dd51730c3d06da7203d649f9e5797b,2024-11-21T07:36:15.960000
CVE-2022-49260,0,0,8edc4010767ab82723cf428968a7316b2e8fcbcce09865b615cbfd9317759088,2025-02-26T07:01:02.967000
@@ -213407,7 +213407,7 @@ CVE-2022-49267,0,0,14cf6e86dbee6bfef01eee0d707840d55565948313f6244cb0e36e0f83a35
CVE-2022-49268,0,0,68861c5d695cd4f3f0ecba55b9802f4d295901a17c22f5986c2744aa5d0ee6ab,2025-02-26T07:01:03.710000
CVE-2022-49269,0,0,cfbf2dbdb41932c60c00b5942c6b07ef6d2b39663f15351967811b6961ae13c8,2025-02-26T07:01:03.813000
CVE-2022-4927,0,0,38cabefc86faa21ef7a71fd3b17ce17fef5bf62f0a9bf16de2aec372df1e9418,2024-11-21T07:36:16.143000
-CVE-2022-49270,0,0,c1088f16de28bc387f404fc17624a8e944704f53c0db360d39fcc96b8de8b94d,2025-02-26T07:01:03.907000
+CVE-2022-49270,0,1,6d26bffe36f534dd79e3ce25b25e180dc7f32cd1f9cf72e49142ea53a539d500,2025-02-27T19:15:42.757000
CVE-2022-49271,0,0,81ec18b86300beda71f17ee2dec64ee7abcf84cbdaf8fcd3970c998b9d63d764,2025-02-26T07:01:04
CVE-2022-49272,0,0,2398c975f2a4a553e310ca8af213f15464295377e7f82eb2bd1ef0da7f541839,2025-02-26T07:01:04.097000
CVE-2022-49273,0,0,e75c5ce021d2555c06178559590a309db5c066ce3f7c0db6a274b2043a067ae0,2025-02-26T07:01:04.190000
@@ -213425,12 +213425,12 @@ CVE-2022-49283,0,0,e3d3b0c2407a88f1bb5cc771a887e4b05010b3502dd9e2bb8ec57036f2d16
CVE-2022-49284,0,0,73a0665886f75aa71a2125be1544eddaa1b4d1472b654f06124ccc5139ee34d9,2025-02-26T07:01:05.260000
CVE-2022-49285,0,0,f2c3f399d311b9fa1d07cd4a8ee3a4f3db99b0659d482a36f7571886574891ae,2025-02-26T07:01:05.360000
CVE-2022-49286,0,0,eab7d78b82b8aa770864f42db2ac36370285950df2ac91af16e595291f816695,2025-02-26T07:01:05.453000
-CVE-2022-49287,0,0,3ed873470a132025a98f5b3d3c803f9641fe503f321d8c71ff4747267ea1bc02,2025-02-26T07:01:05.557000
-CVE-2022-49288,0,1,6bdc961d504f97e5df27bc613a19336810919ef7a7a83ac5d27d8ada91031917,2025-02-27T18:15:25.140000
+CVE-2022-49287,0,1,808965b0729186c961e4031a3f524042d4b8e7af928866e44f047b97631598a2,2025-02-27T19:15:42.893000
+CVE-2022-49288,0,0,6bdc961d504f97e5df27bc613a19336810919ef7a7a83ac5d27d8ada91031917,2025-02-27T18:15:25.140000
CVE-2022-49289,0,0,e6fc5461994572a8febc714b17e9a3856912a029b40f3d639447394b03df0fff,2025-02-26T07:01:05.757000
CVE-2022-4929,0,0,44429f972431c9add0abbd71f7b863649b7649f353d704d77271ec361956d7aa,2024-11-21T07:36:16.417000
CVE-2022-49290,0,0,91682a598633e97d4336d00df3891391521f1b7822f1a292237ae649015c2e83,2025-02-26T07:01:05.853000
-CVE-2022-49291,0,1,e9775167ef126df5312083e16a5ee34e408bf4c7664babaa358175d6f2241a6f,2025-02-27T18:15:25.323000
+CVE-2022-49291,0,0,e9775167ef126df5312083e16a5ee34e408bf4c7664babaa358175d6f2241a6f,2025-02-27T18:15:25.323000
CVE-2022-49292,0,0,329d2fe9869cf6ba474956f36ad05755efafcce0bb151e3593029bccd90353c1,2025-02-26T07:01:06.047000
CVE-2022-49293,0,0,a6704f5cc77827a5e3266b83bb663d880e1b44aa6adba028a05e9e7b495af563,2025-02-26T07:01:06.140000
CVE-2022-49294,0,0,0995ee45a86d384bb37a401c653d869b0e95b381ac00621970623ce85bb4fa76,2025-02-26T07:01:06.237000
@@ -213470,7 +213470,7 @@ CVE-2022-49324,0,0,49d0b0c6af4b2cf6aaffda99afb91f52d0f4266510a4d64b9292da85bae66
CVE-2022-49325,0,0,482d9e246153edb772deda69245c75f9f70b88358385c35a0abe49193f929c9c,2025-02-26T07:01:09.323000
CVE-2022-49326,0,0,1868af15a0fe34ac347f83cb11c79f8e079dbc4f3d5db56ff5af3e15515fa129,2025-02-26T07:01:09.417000
CVE-2022-49327,0,0,a528e04f58e5820d5e72d1fb59c2c6e26f71e442866fb3496ad53515181be68d,2025-02-26T07:01:09.510000
-CVE-2022-49328,0,0,3652c56781fd29eb10ce70175a66be5b778e554991237aeab1efbcad0b8dcdbf,2025-02-26T07:01:09.610000
+CVE-2022-49328,0,1,3b0f6a820994c4fcc3cadba16beec1976d8a63a2329755cfe8772f11deefee15,2025-02-27T19:15:43.047000
CVE-2022-49329,0,0,2a93d66a643a197e3f00403749b6af5bf31821c687ab3b9e22744dbbe2cc6a31,2025-02-26T07:01:09.703000
CVE-2022-4933,0,0,d122e5bd0202c57480b45e5b80ba8ba9aee30fe0686b6e4b51d4527b501848e9,2024-11-21T07:36:16.890000
CVE-2022-49330,0,0,a10491dca1a972463b132de636ff60efbeb0972e54557618f2cdc09a6a2cebab,2025-02-26T07:01:09.797000
@@ -213493,7 +213493,7 @@ CVE-2022-49345,0,0,9ef1ee3283cde9374aea6212586339465771a6592b499d9da1291bef262d2
CVE-2022-49346,0,0,3b76f7f7a8a134d64ab19a5786c0d3c9361fcbf66a96ac2845c772a4ff71efa0,2025-02-26T07:01:11.340000
CVE-2022-49347,0,0,762d19c4605e161b5f6840cf63857d82f1015ca95b57b3143a36eecea78e75bb,2025-02-26T07:01:11.433000
CVE-2022-49348,0,0,4194c1bb0bd768fc1bffc1fd63427356d8362131793889924f10118306f4cf5b,2025-02-26T07:01:11.533000
-CVE-2022-49349,0,0,473b18de232a351e7b4816c4b15f8fcf02ac8585f0fcdf62cd5606563592648c,2025-02-26T07:01:11.623000
+CVE-2022-49349,0,1,40cd137b939e23bfee3355a65504a65e611cc4e5e12f1802b255d60058b50a26,2025-02-27T19:15:43.190000
CVE-2022-4935,0,0,c31e88e6073fd3a29bae4107f25ae33694ff5130dac188737279f3976c97e421,2024-11-21T07:36:17.127000
CVE-2022-49350,0,0,515ab58c753f7109f85b7a0304704bc20450dd93f94de4cfaf4317e4a0a054e0,2025-02-26T07:01:11.723000
CVE-2022-49351,0,0,fe208c614edc6928347e2e67d4eb5b3391aac70627cd806f6aa1833ce4354011,2025-02-26T07:01:11.823000
@@ -213504,11 +213504,11 @@ CVE-2022-49355,0,0,80fa4fd5e635de4f91692140e2c86158eee6f65edf7fc01373d8d1f58728f
CVE-2022-49356,0,0,3735a9e7ee38abf62bce69f73999c17e02f700241d5befba3d70faf4b7f21f1a,2025-02-26T07:01:12.300000
CVE-2022-49357,0,0,637dda3e5c27c01e3898a9841a927d5ea912509c344c9f3240b4e0c164d23650,2025-02-26T07:01:12.390000
CVE-2022-49358,0,0,bbe466343a4faeb3203ec7aea9e5679f8d8e076b88172dcfc1582c9214c0a461,2025-02-26T07:01:12.487000
-CVE-2022-49359,0,0,9454c72c679e7259728c797a8a57d63311e6bcd80c07aa5a95bbc1f7b16b2742,2025-02-26T07:01:12.583000
+CVE-2022-49359,0,1,1cdc7d8b0b27a7fd02b8b2d7c003dac984ab3b2ecefc728ed6da1d9577bf95ef,2025-02-27T19:15:43.347000
CVE-2022-4936,0,0,65f80b05cad36259fef0938d250fce71f92bdab50ccfcffc0c93e77961d09f04,2024-11-21T07:36:17.243000
CVE-2022-49360,0,0,2a973a46c18e26c3c82bb1121d82cd674a8f87c32459564bc057342ed04cf78a,2025-02-26T07:01:12.677000
CVE-2022-49361,0,0,4d61c877100016dbe8da0355c8968e7a04c0efb2b2c491eecd65e4aa22640bbe,2025-02-26T07:01:12.770000
-CVE-2022-49362,0,0,9eef5986719bccea7b7484c064d71452a592ce4ef3bd2ca8b012ea81a1f6a019,2025-02-26T07:01:12.860000
+CVE-2022-49362,0,1,dbca1975d3e59cc27bd7294a46fec9cf44b6af6396ae70ed12adaa86bd4bf51a,2025-02-27T19:15:43.487000
CVE-2022-49363,0,0,28743cbb0a82eff7e564a9127bfbca36ea84098cc27f985dbb41642451cf550e,2025-02-26T07:01:12.953000
CVE-2022-49364,0,0,ab0f3010e78c034a68e03706c0f4c28e07880c52d510955d0b1b71690983039c,2025-02-26T07:01:13.043000
CVE-2022-49365,0,0,d90241121918b1a759748a4f5200df56945cc7ee49fe82a3aeab496bba2394f3,2025-02-26T07:01:13.140000
@@ -213524,7 +213524,7 @@ CVE-2022-49373,0,0,4e2854aabfc7d3f78f97c75867345efee30cd9fbf7e6a392327f98f86d4a4
CVE-2022-49374,0,0,d048a10ed657eda737a2f59705a48fd64aa71f142e05010aed4fa38a1507c4e5,2025-02-26T07:01:14.060000
CVE-2022-49375,0,0,a576be0092cf671c7c727c1dcebe8934c0488b41f29e7c11f3fcb22bcb1f0bac,2025-02-26T07:01:14.160000
CVE-2022-49376,0,0,b4ab3efe14c6d810fff7730f6f75421e4d965a7d01df308bba3be417ba3622f4,2025-02-26T07:01:14.260000
-CVE-2022-49377,0,0,c89c5760f1b3bb7aefcfc30e99aa32c0dbcd149cef961318460676cf78777928,2025-02-26T07:01:14.357000
+CVE-2022-49377,0,1,b5b243233019b2644526abf3965cb5bafc8b5e4774851f315291fc746d5f71dc,2025-02-27T19:15:43.623000
CVE-2022-49378,0,0,940e4ed796d272d233f40d57c6bc4a0d7aa0d7d507fb6ed7c2eb6e3f1d9c36b2,2025-02-26T07:01:14.450000
CVE-2022-49379,0,0,7b3af74344a00565a96196b22b16bb3261e4f80c0c366a77e886aed9d9c078f0,2025-02-26T07:01:14.543000
CVE-2022-4938,0,0,2332c28f2266da2838561d3fa8517b8e02799844e68fbf6d1d4046cef0e62add,2024-11-21T07:36:17.473000
@@ -213533,13 +213533,13 @@ CVE-2022-49381,0,0,e91d2cc0817b8375c305f0aab5e8561f39579701be54b8f4a9b2fdb3ad2f9
CVE-2022-49382,0,0,fe6cbc42da6688a0d8c05f6a2537f015e4024e22099a62f240ca8df5e8082501,2025-02-26T07:01:14.823000
CVE-2022-49383,0,0,bb2d55531cd8e60f8bb57bb6e5beed5f00ebb3d054cd1e57068320b7cab7138c,2025-02-26T07:01:14.917000
CVE-2022-49384,0,0,ac26e9b927f63306f5cce0a03da4df2a1fc5a98ae549c36a1e5ab9cd24073ab6,2025-02-26T07:01:15.007000
-CVE-2022-49385,0,1,125f5f1e0383da09a9f63122da718abb9730155ff3fdba4f8e0a94c397c12bb1,2025-02-27T18:15:25.503000
+CVE-2022-49385,0,0,125f5f1e0383da09a9f63122da718abb9730155ff3fdba4f8e0a94c397c12bb1,2025-02-27T18:15:25.503000
CVE-2022-49386,0,0,3b4018aba82375c7c9aeb01d1732096bbdb9b0087f4dadea9720fe106e7748fc,2025-02-26T07:01:15.233000
CVE-2022-49387,0,0,b44c23fdc209060b85c8598dad2f09008a2ea1502e159da0f1048a070c6b2435,2025-02-26T07:01:15.343000
-CVE-2022-49388,0,1,0c241119e12af128dd86d69cecdeb428daad96afc558b5343b1a38c28a97a164,2025-02-27T18:15:25.670000
+CVE-2022-49388,0,0,0c241119e12af128dd86d69cecdeb428daad96afc558b5343b1a38c28a97a164,2025-02-27T18:15:25.670000
CVE-2022-49389,0,0,3f24f12dc127ea1f4bce5dd1bb65d9093dce4bcb6a37a84d6e2e26364da9433b,2025-02-26T07:01:15.527000
CVE-2022-4939,0,0,0cba4e037d925063e40978b79f96a48c7a5c9c275420fe2dbac9dff13a084ba3,2024-11-21T07:36:17.580000
-CVE-2022-49390,0,1,905b2dcefe516a118d4e9e5c3d4abcf04b45fe25407514dd64266c35fa83089a,2025-02-27T18:15:25.843000
+CVE-2022-49390,0,0,905b2dcefe516a118d4e9e5c3d4abcf04b45fe25407514dd64266c35fa83089a,2025-02-27T18:15:25.843000
CVE-2022-49391,0,0,39398bdd44eaac475267d78714be54b1471a0748f3d6a6a0d3aa3d69cbeff27f,2025-02-26T07:01:15.713000
CVE-2022-49392,0,0,62b851b7c7f771f18936846152654a9aa7388d00aa2251dd5ed365f50fbdeb4f,2025-02-26T07:01:15.803000
CVE-2022-49393,0,0,ee7434d2286c74d58de0c7debc30ba2ba07cbe61d4d1287c118741afd27faa9a,2025-02-26T07:01:15.890000
@@ -213563,14 +213563,14 @@ CVE-2022-49409,0,0,e516cb00ab70cb46b87d554f2c3fb499b7308e6f1067057120a28bbf46a19
CVE-2022-4941,0,0,c9bd40e150e10c29b1c1e079ad1ffb2aea9c86536c13026eb988f154ee982f63,2024-11-21T07:36:17.807000
CVE-2022-49410,0,0,a58f7d186ac6bf4a196ad85066e2e191e64e394ad7579864dad99ced160c92cf,2025-02-26T07:01:17.517000
CVE-2022-49411,0,0,f38a47f2adf60e7197a091bc94eb5ef219c27eb48923634d7366ec372ad314d4,2025-02-26T07:01:17.613000
-CVE-2022-49412,0,0,c70220407d15016491df62ff89c9744874a1c68ccc7e0fad1fa109629744f792,2025-02-26T07:01:17.703000
-CVE-2022-49413,0,0,8c4a79d0b330edea3e57664a74d0ed13097fb186c3e483710d0850b97af3cb9a,2025-02-26T07:01:17.800000
+CVE-2022-49412,0,1,e257661e1093127e1e3b1d10efaa44254e095b4a7e9db6cc433c2a0dbb16784f,2025-02-27T19:15:43.770000
+CVE-2022-49413,0,1,a5f886134429476bcc89ea47b1e794868edd648a5bc043f4487b77072e973bfa,2025-02-27T19:15:43.910000
CVE-2022-49414,0,0,1d1ee0437589b3b75a09ef91a95c7e2857b15b8f3d7fd36cebc880e11b2b09da,2025-02-26T07:01:17.890000
CVE-2022-49415,0,0,13f85599b3182f1e5ba4b8ead7cfca08220157b2909d9146d31ce848d56cabe0,2025-02-26T07:01:17.987000
-CVE-2022-49416,0,0,84cf0753041ae8d8c0638126822c51f99ab2ffc3fa6317d5c007bb31e505f14d,2025-02-26T07:01:18.073000
+CVE-2022-49416,0,1,f4a8356dafde63b4ca00c71f55656520b41644114a7e96b02acc883d2fa3fb5a,2025-02-27T19:15:44.047000
CVE-2022-49417,0,0,17b5d635049cb077b4e971cfada27c1fd195d3a22179b278a32746afd9da6996,2025-02-26T07:01:18.170000
CVE-2022-49418,0,0,4ecde112bc03373c3bb2b00eda77333665676c29956a7fd7a5b1808d3f514b84,2025-02-26T07:01:18.260000
-CVE-2022-49419,0,0,ba7653983be0a8c9bd4eb96de99fab076cbebda31e3b4d45e9885f43cf08606e,2025-02-26T07:01:18.350000
+CVE-2022-49419,0,1,3e283e06c3307e14452901e1512179220474812b85d73ef592886fc90fe7bcf9,2025-02-27T19:15:44.190000
CVE-2022-4942,0,0,4bfd31c9d3683237fc0f66ee6838a8e9abe03973c1dc054d19973ecd2181f17a,2024-11-21T07:36:17.917000
CVE-2022-49420,0,0,637257ef12b3fe0a02d337bf7406f3b9affcdb52667be5a01eb55aaee3f0b9df,2025-02-26T07:01:18.440000
CVE-2022-49421,0,0,bd3860ee271687b34b3ca2edd46397f934622cd7791a6621cb526fa3721c1a4d,2025-02-26T07:01:18.533000
@@ -213578,7 +213578,7 @@ CVE-2022-49422,0,0,0589c756644a96b284e09a5275cd61d4f24560ea238981472956da44a5159
CVE-2022-49423,0,0,cafe7c05b5763baf796da66aaf17ee96037e3691f18e935fdf9d669f9b8322be,2025-02-26T07:01:18.783000
CVE-2022-49424,0,0,1b384bfb2d8a28b0b04e2bf71671083b0671cb7d7d784468f77e27e21c1f2a86,2025-02-26T07:01:18.880000
CVE-2022-49425,0,0,eec1086f28fd35e7d3a109335ba6388d180b8145b3460d16175433801c034f81,2025-02-26T07:01:18.977000
-CVE-2022-49426,0,0,583fc7581e26f15e541755d06a17f56758c53aa8d2ce2ce1826d09f0022e92f2,2025-02-26T07:01:19.073000
+CVE-2022-49426,0,1,43b4c8039b747f3a0d03898afe0d08765e8d40e2ba8250758d15bd081bfb87bf,2025-02-27T19:15:44.333000
CVE-2022-49427,0,0,1dab1702689120e7de199d15eabbf38cccaa6d2467792d5bc8f93aa4d14f153f,2025-02-26T07:01:19.187000
CVE-2022-49428,0,0,67421d5b657164565775e5ad04ac62168ecc788a951dc55b796ad2980620e8de,2025-02-26T07:01:19.290000
CVE-2022-49429,0,0,a77c90ea5e9e167ace6e4eaf1be518bf43aa3d4ea438a4a04fa89515a87408ed,2025-02-26T07:01:19.383000
@@ -213620,22 +213620,22 @@ CVE-2022-49460,0,0,fe0b0923c9513a92097a7c1f8d1da32ca58d7dace863b60d9126734022b61
CVE-2022-49461,0,0,74faf687caef89e36114d7956a7a18db362b51069fc3e321422389e97363a002,2025-02-26T07:01:22.423000
CVE-2022-49462,0,0,c8ca2d00e7b9be87321b54aa6affa272b57fb1ded438fac4e56d85f513a12179,2025-02-26T07:01:22.517000
CVE-2022-49463,0,0,bd05c300217e6d154e5bb8b22a7ac4cd153fe3dec27a9b3df908af179995fc46,2025-02-26T07:01:22.603000
-CVE-2022-49464,0,0,2e7f3026c0466cef8ae39110da534b3aecf6c2b2be1a1d05207ee201f3c851dd,2025-02-26T07:01:22.697000
-CVE-2022-49465,0,0,c6be0a56052621c6ad58ded3e81399291100ca5576c7bddc492402712b875986,2025-02-26T07:01:22.787000
+CVE-2022-49464,0,1,15e4ce29e44e4d295f2a493bf93e3fa25f440efd55cac6aa6ff4f02dbddb6a79,2025-02-27T19:15:44.470000
+CVE-2022-49465,0,1,184f64c17a1734c11a8b703f935dcb5db93b7370021895023f853772dbd54145,2025-02-27T19:15:44.603000
CVE-2022-49466,0,0,77b4eb41313aef8460db4397e5a1809bba361069263eba76d0a2032724c90bc1,2025-02-26T07:01:22.880000
CVE-2022-49467,0,0,f771bcac55daa7619c79a1062188ab4bd4efdc14a06e0839c8c60dace866e3c6,2025-02-26T07:01:22.967000
CVE-2022-49468,0,0,2e4259e03719527dcd960576bc49e5288c537a27115ac18fa1bcf31303c52282,2025-02-26T07:01:23.063000
CVE-2022-49469,0,0,822ba518e11cfe2bd7e3a9f448c70fea01a9999dbdb88bfcfe27cc29d83c31fe,2025-02-26T07:01:23.157000
-CVE-2022-49470,0,0,46a87092f6a251b99366f05a652a1316e12d0211b058f9d066e06bc80227200f,2025-02-26T07:01:23.240000
+CVE-2022-49470,0,1,539d4fda4cd4a1d501ba0fe0b1bb70fb9eccdb8235d92b748da146d95261c2d2,2025-02-27T19:15:44.743000
CVE-2022-49471,0,0,66e9e08f5b7b0b79bfaed71bf4a0b2f5b1f9b16204ffa206a0ef0b7b88878831,2025-02-26T07:01:23.333000
CVE-2022-49472,0,0,956c50c3f37512517f2f6940d030066c70ece3dd153e4dbeaa1024cfe4a4eb26,2025-02-26T07:01:23.423000
CVE-2022-49473,0,0,ca4719509337104ef61da10abe55cb95b4661826ce42be25632d7fa25f439023,2025-02-26T07:01:23.517000
-CVE-2022-49474,0,0,b140b5f3ffeea60c0918be17ce1f8fe31c3ff178fe13c150dbc87d752d8ac70e,2025-02-26T07:01:23.613000
+CVE-2022-49474,0,1,30373623081629a291948c921fc51726b8ff472da5efbb1f7e992d56ef372831,2025-02-27T19:15:44.880000
CVE-2022-49475,0,0,6adc491b005ef36749f3be0afebe4409ff418ad62f62a9c6038729d9241f684b,2025-02-26T07:01:23.713000
CVE-2022-49476,0,0,640fbc92ec372b9fc733538d5d06673770f3ebb7fd5fd2d15cbf4426f35f2339,2025-02-26T07:01:23.800000
CVE-2022-49477,0,0,b5d7f2a452fa030f680bb20216240f1b6e2ad8cd555ac11aaa42cce16eb360af,2025-02-26T07:01:23.920000
CVE-2022-49478,0,0,f25e1762442177f803844f822c9ee530fc5c0c034b646b5eeab5c71e4eb36c4d,2025-02-26T07:01:24.050000
-CVE-2022-49479,0,0,f02b3786eef963adc054c322867822a8dff8a8c913703994a560736a6527f761,2025-02-26T07:01:24.153000
+CVE-2022-49479,0,1,5fc59459bea464d240faebd88583c73a807300d867c15059b55809508ceb4e9d,2025-02-27T19:15:45.023000
CVE-2022-4948,0,0,3f06e3662375e23afad4aa4576d0c4fd807f6f0a60e20fd1d377539f48f1a48c,2024-11-21T07:36:18.570000
CVE-2022-49480,0,0,d0179cdcbb9d92338cb7030ebf43a57582627bfd199f799b87711395649e7e93,2025-02-26T07:01:24.243000
CVE-2022-49481,0,0,148b2f51b41ea5cce2a925c20e6698590e9de23705599b2dfddfbef3ee0f72d6,2025-02-26T07:01:24.340000
@@ -213651,7 +213651,7 @@ CVE-2022-4949,0,0,20ecd66c665d4a7df211e25b3128a2f7367a36b316ae054ac00474cadd4e50
CVE-2022-49490,0,0,be1548e2f91eb4b94e259aa0caa5f9af30684172e2d59364aad173af2618ddb8,2025-02-26T07:01:25.183000
CVE-2022-49491,0,0,cd60ea56501cd25d2157510145510046a2b5471362a94666134e36f523b5d661,2025-02-26T07:01:25.280000
CVE-2022-49492,0,0,d82fdea0c2e6fc26fa79cd871499418a6aaeacfed0f6add7e8e3bf3dc8f534c7,2025-02-26T07:01:25.410000
-CVE-2022-49493,0,0,b9a2797661ec6819531c73a15c6acfe126a5aa2407adbc3b6ffc9a6fee120d3f,2025-02-26T07:01:25.520000
+CVE-2022-49493,0,1,ab6a2249755ec3e766545c29de4a1236edc2c8f464e009c6b7ab68abdd01e89b,2025-02-27T19:15:45.153000
CVE-2022-49494,0,0,a7eea3b4ef11a97dd755aab6093e43d3f8252333cba49c9e73f1fc803d726d71,2025-02-26T07:01:25.613000
CVE-2022-49495,0,0,b6dc2e6a9d20b820423bb5c29aea93b630e7075a91738842865e068c3d5efdb8,2025-02-26T07:01:25.707000
CVE-2022-49496,0,0,fd8e4a2e58bc96835ad145f1b2768a27158a33a0a10b3bab015711b7fee9cece,2025-02-26T07:01:25.800000
@@ -213660,11 +213660,11 @@ CVE-2022-49498,0,0,f9600e4a2cac3c4965c2ad0b66be39b675aae56651f80c6115554f7f74f8f
CVE-2022-49499,0,0,2c127c9fd7c88b3d4d5430f28fde103481887c43621d1aa792247a91578222a9,2025-02-26T07:01:26.077000
CVE-2022-4950,0,0,553f8616c590a48d9a934a6dc8477b16541d05a5e26a41275fd32eff9d48e9d2,2024-11-21T07:36:18.810000
CVE-2022-49500,0,0,991df30b70f007d3061c7dd64fe713760c29f3a80be81e2008d1877e0cf5c9c1,2025-02-26T07:01:26.163000
-CVE-2022-49501,0,0,9a159dec21f03e68eb0839300135c49554a6f3bec26f47088d215af5ec3fa783,2025-02-26T07:01:26.257000
+CVE-2022-49501,0,1,9986cfa57df63028a8c54c598d4a278112ec49328247b3a67cd7d40b390b7072,2025-02-27T19:15:45.300000
CVE-2022-49502,0,0,89672d9193ab66e6e4295d3d3a0b950e2c9a8da794cf16b607aebeccadd84a0d,2025-02-26T07:01:26.353000
CVE-2022-49503,0,0,1cd521e3160c7683bcaf6f2f831c7e3f283f7edef8a6db3deaca7c4c165edd9c,2025-02-26T07:01:26.447000
CVE-2022-49504,0,0,fd785117748f74d2fdb63d7fd088e13e19e9bc95c772729b83225421460c1e97,2025-02-26T07:01:26.543000
-CVE-2022-49505,0,1,172102e0c682010efb767ce626dd9ad05425b74ef25a9e8c09eb2304425f00b0,2025-02-27T18:15:26.007000
+CVE-2022-49505,0,0,172102e0c682010efb767ce626dd9ad05425b74ef25a9e8c09eb2304425f00b0,2025-02-27T18:15:26.007000
CVE-2022-49506,0,0,208be324946220bb4165e799d227ea784a01c73a67b01907965e03d8aff97547,2025-02-26T07:01:26.737000
CVE-2022-49507,0,0,ed9ce57a32d7d0954afed61f11275aa9a97676fd2730a4012781fe267a810e3f,2025-02-26T07:01:26.830000
CVE-2022-49508,0,0,229d6f3f4ed32bf1c9d326d60531522b12c2150a7b9d25e73fd1b4ed64bfb544,2025-02-26T07:01:26.923000
@@ -213684,7 +213684,7 @@ CVE-2022-49520,0,0,f2e8bdc19c3d71b9c3d1afad1006c3d2c3f3f4e35db501b1b4fc1d01acdc4
CVE-2022-49521,0,0,0c02454b8e2dc250f97a0a04be93dda8e4f0f9058d8e7871fb4a867673cd9326,2025-02-26T07:01:28.113000
CVE-2022-49522,0,0,a4407bf677fbac155505b03f694d8ed0a9522e5d27fb847bc2ae17efc1f86bff,2025-02-26T07:01:28.210000
CVE-2022-49523,0,0,654be4632aacf3c1117446390883f3f78787ac4ab6caa6c14751f1f6662dc310,2025-02-26T07:01:28.310000
-CVE-2022-49524,0,0,f996416aa5fb20a468be0132cfcc257ecc6410b201c2a94361b9000cdbdd5101,2025-02-26T07:01:28.407000
+CVE-2022-49524,0,1,cd0e0686033af5195a65e5037650da6c341978ebca3c028dba60d3180135791f,2025-02-27T19:15:45.433000
CVE-2022-49525,0,0,1e4561bcb3d9662172ba88a6aba9cb6f4a1f9c3efc84f266ea00867a0f92769d,2025-02-26T07:01:28.500000
CVE-2022-49526,0,0,c417a58a9a8837e9d4203b697af2382f63270ccb642dc99133f70a78c9350c54,2025-02-26T07:01:28.593000
CVE-2022-49527,0,0,1b2cca0b8ce3894f6ffe144f413ee21484316d7f83cf571a96259357dc63307a,2025-02-26T07:01:28.690000
@@ -213696,7 +213696,7 @@ CVE-2022-49531,0,0,bcc8e99c2179eeb842bb7605f5bbf6a3443fd2fe7e0413fd44583d9a16663
CVE-2022-49532,0,0,a5ffd6ff781077501c7b2ebdbffffe12e9981584442a539952766e8cf16f39aa,2025-02-26T07:01:29.170000
CVE-2022-49533,0,0,afcec182555ff5ca487aac89ad597d97856fbecf2c361276f209f8493c77810d,2025-02-26T07:01:29.293000
CVE-2022-49534,0,0,c4461f5c4ba46e3eb7f3de0e571457425a17021a6602c94336443eeada686aa1,2025-02-26T07:01:29.400000
-CVE-2022-49535,0,0,3ca28ee30bf6231e2e29e44c147ae696ce1d6e3e335466b803051bc8e9717a0b,2025-02-26T07:01:29.490000
+CVE-2022-49535,0,1,ed4dd1804801b5f13ba678d3f79622b94f77bcaf710214ac838ca84c8badd4de,2025-02-27T19:15:45.573000
CVE-2022-49536,0,0,5879171cb53c59e2b6b018dffcbafd62095bdcf62e7be357477df9279cd7baa9,2025-02-26T07:01:29.580000
CVE-2022-49537,0,0,f2669b5a1b78518748fb173efd6ad42004496fcfb0f87e4e4b741a2ab901eedd,2025-02-26T07:01:29.667000
CVE-2022-49538,0,0,a21e6f08f092ba11614b7f88efbe3e83bb79952c8014988e30906b73552edd06,2025-02-26T07:01:29.760000
@@ -213792,11 +213792,11 @@ CVE-2022-49619,0,0,f493024bb63d384b281e595de3e97660710297667764b8c83a58e4dbfd03e
CVE-2022-4962,0,0,386805a0e4416acdab18cedde9e47f610c5ba3ec156161822cfc562e819f4b4c,2024-11-21T07:36:20.270000
CVE-2022-49620,0,0,9de1fe816fd2157d488af355312fbf831884f48be8bc3f19a68a5d16ac657df7,2025-02-26T07:01:37.387000
CVE-2022-49621,0,0,66afccc87170c831ba7b5a6b1b241641df0bd8f00641b2ffc442d4cddae80b61,2025-02-26T07:01:37.487000
-CVE-2022-49622,0,0,cd487d27b7076b870f273338e8d5028c632cfd061b18c3accb4aa24a6fcc3918,2025-02-26T07:01:37.580000
+CVE-2022-49622,0,1,d45d50f649ad5d33fed9f6a576ce0e78c881d06600fe3c035d97bf70df076b5d,2025-02-27T19:15:45.707000
CVE-2022-49623,0,0,a28b2a60e9874d468fdd816c216370805099d448f10a012c7797e37935e347f5,2025-02-26T07:01:37.663000
CVE-2022-49624,0,0,dd2bfa5ee832de795cfa794508626771ecb56d853847dc36a5e70a123d501e89,2025-02-26T07:01:37.753000
CVE-2022-49625,0,0,9f58fe38a969e38714d16c17f2a99815539a04b1a6e03ea784518f5bfdf34769,2025-02-26T07:01:37.847000
-CVE-2022-49626,0,0,99525c788693c33cb8c4ecf5d45f8ab842f555b22927bff657c726dd04860471,2025-02-26T07:01:37.937000
+CVE-2022-49626,0,1,4353a65f1a99788c052b1c8611786763f949c78a1b7cbd81e4eab207e4b78fb0,2025-02-27T19:15:45.850000
CVE-2022-49627,0,0,7d61a807fe20d3c1c87260c94102067f804cc7813fdf5ddedcba2d7c9c482b4d,2025-02-26T07:01:38.030000
CVE-2022-49628,0,0,7116a363ad204d4293929b543886ef7c8aecb8eace1240643b1d511c163013bf,2025-02-26T07:01:38.117000
CVE-2022-49629,0,0,50d0a03953fe76b07677b1a8964f4bc78f06fc887a6cef14354f301f52ab6479,2025-02-26T07:01:38.200000
@@ -213819,12 +213819,12 @@ CVE-2022-49643,0,0,f8e50f8802b93ee97fbb1c604f4189150b2065e3aea996b81f906278e8a04
CVE-2022-49644,0,0,ed718a3f6baf2e113a75133f2ff881eb06bf9e4e251d0cffa529309e3edb964c,2025-02-26T07:01:39.567000
CVE-2022-49645,0,0,81be08e506e6945be5038ef5795fd6199a9f4fb2a22e998e4fa378c99a4428a8,2025-02-26T07:01:39.677000
CVE-2022-49646,0,0,2e9a876e5f95933f4c73be0514431615ea6d7849c3b4180954e06f6a67f51aac,2025-02-26T07:01:39.777000
-CVE-2022-49647,0,0,707399151729375fda861f2ef90d81131bcd8bd5be62975941da489c4055417e,2025-02-26T07:01:39.863000
+CVE-2022-49647,0,1,1743dacfcbd6af91395a0d474f140b8e2672835b767270eb0b91f2659f0427aa,2025-02-27T19:15:45.990000
CVE-2022-49648,0,0,294289f4fe7d5537f06f3e820f72235b5e223eeccaafb86e3510285b7cb93c66,2025-02-26T07:01:39.957000
CVE-2022-49649,0,0,7829643169bede34b683f89d95ec494a695a7c973cd6b4c486a5037284e80043,2025-02-26T07:01:40.050000
CVE-2022-4965,0,0,60520f7fe367ad75afc49cb5a38d09f60dd060ea4cbc4cab5dd51ee8b1f8d468,2024-11-21T07:36:20.697000
CVE-2022-49650,0,0,f5d32cf60278699fd6a650d2a09904f9cd969913b2008b33fef0454729763660,2025-02-26T07:01:40.150000
-CVE-2022-49651,0,0,609fa08ffcd235312b13503d78fe717bd334fb10ce4b5d1608779cf0d1cd0146,2025-02-26T07:01:40.237000
+CVE-2022-49651,0,1,a9564f6c7723a9a248c934b09abd391469f95c9714bc0453a6e859f67821b4ff,2025-02-27T19:15:46.143000
CVE-2022-49652,0,0,98bbdf4bf70c62a2c11bab9ce07781b360cae34ec4a8a0a6445cdf7311e2c1fa,2025-02-26T07:01:40.323000
CVE-2022-49653,0,0,f66746824c55a89451f07b881ff883adedb47481deb93dd0d91f20154cf880f1,2025-02-26T07:01:40.420000
CVE-2022-49654,0,0,c7c747dac98ead6ae5a77a62ece5a5789eba4f994fe34059d6b593ad68ffac5d,2025-02-26T07:01:40.510000
@@ -213841,9 +213841,9 @@ CVE-2022-49663,0,0,d65c6449531a59de0c58ad5d7fb8396dab5adf12da29eb4ae84a6bd5a2716
CVE-2022-49664,0,0,acc87b12ff893a72d1e4d50d3289708524a19935aed875fa20333c8c9aba2e92,2025-02-26T07:01:41.420000
CVE-2022-49665,0,0,38402ea9b3a124d6a1df1983495417acc0978c17c7d4aaee08c0f3df7450fc30,2025-02-26T07:01:41.513000
CVE-2022-49666,0,0,e36b7409adf910f421e9cea513f4391491a8502e218ad78820afdc7f7044d80d,2025-02-26T07:01:41.600000
-CVE-2022-49667,0,0,1e099cb23e79847e583751cb9cb100e0907d441455187f259f9ed1a74fc9637f,2025-02-26T07:01:41.687000
+CVE-2022-49667,0,1,01fef2f932e4714973776d6886d79be9e598ee0aebee64d3ee4124d7db7dcf0b,2025-02-27T19:15:46.277000
CVE-2022-49668,0,0,bafeb229616c3db7083f8dbff72ceac6aab45287b893b5d718b6393f0b0c1cc1,2025-02-26T07:01:41.780000
-CVE-2022-49669,0,1,b9944783314d10a3469764465f6aa500318e395c0c7ac42d23ad8fb39773108b,2025-02-27T18:15:26.203000
+CVE-2022-49669,0,0,b9944783314d10a3469764465f6aa500318e395c0c7ac42d23ad8fb39773108b,2025-02-27T18:15:26.203000
CVE-2022-4967,0,0,7bad2c988cb94d61125773a7a88a30404d5f4c0bbce5e0a1937e4f25b7e6b432,2024-11-21T07:36:20.957000
CVE-2022-49670,0,0,c54d3317486660bbd6cde1b7aa381fe4a30b02b38d6df6482f115483995fde19,2025-02-26T07:01:41.953000
CVE-2022-49671,0,0,a93e99b064e6eeafde5c1c56176193a8f2547c81387b08116f956edebdd40ad6,2025-02-26T07:01:42.043000
@@ -213861,7 +213861,7 @@ CVE-2022-49681,0,0,2e367068ac72d3f8cc8654b3b5bce57aaf6953b5402214850999d23be4337
CVE-2022-49682,0,0,37814c4f01d3a0829fad9e4fa7ea16be382963b240c7d1f8ec196665600c81fd,2025-02-26T07:01:43.063000
CVE-2022-49683,0,0,f89cd84deb79228832db270f65a7e8d775337fb7e5339d043a0f0d126b173d03,2025-02-26T07:01:43.153000
CVE-2022-49684,0,0,9694d7a567f090adadd86d68d9e7b55859a96199ac66a1ea7a4566199eb4aa28,2025-02-26T07:01:43.247000
-CVE-2022-49685,0,0,683966b6ae6a2cf5bd2f61e118e2e0b5821796d6914a63895c55cae7dac12bff,2025-02-26T07:01:43.340000
+CVE-2022-49685,0,1,8aca726b91629d955ce8ee2ab8e35ff78ec847c4a7d005c76a864ef63ffa1800,2025-02-27T19:15:46.427000
CVE-2022-49686,0,0,7239daec22d53e71c4f7af2f98e827b6a53d319aec1c6c26df3c1286e411653f,2025-02-26T07:01:43.437000
CVE-2022-49687,0,0,4137488d76e3d12d0579db9f9d9981a8b7c0f1ce2766e8c902ace78539ff2c13,2025-02-26T07:01:43.527000
CVE-2022-49688,0,0,3d3663e9d294c2e59e2a48c65024468f6105404766c6dacdd88939c071db54ef,2025-02-26T07:01:43.617000
@@ -213872,12 +213872,12 @@ CVE-2022-49691,0,0,325d51214696b88d36748aa2db137aaa419b2046bbc8f76fce04401077791
CVE-2022-49692,0,0,9e48fabfd49b351faef80b96b392670b998a599bbdd04b7a7743edc165606e62,2025-02-26T07:01:43.990000
CVE-2022-49693,0,0,31d65d2f199ec52e265937acc096fd57e14bca5c77865f2c0ad34fddebcea4e1,2025-02-26T07:01:44.080000
CVE-2022-49694,0,0,a32977593f82381c19ce979c7ffa18c044daf0fcb9128b2dd7cf474cecf1ada5,2025-02-26T07:01:44.170000
-CVE-2022-49695,0,0,5d98abb865e09b62718e7959c28e23565e9962c963ba67197ad29eb259460d69,2025-02-26T07:01:44.260000
-CVE-2022-49696,0,0,dc5c43dd02e6b41f48ae49a21142d22d95be08e8a3afa1c1e8222ee5b8c16381,2025-02-26T07:01:44.357000
+CVE-2022-49695,0,1,6c59848c28b791220cd5f00f895a2651f6a09013e783dc4fb29f1844d6e6d99d,2025-02-27T19:15:46.573000
+CVE-2022-49696,0,1,b9644e5562f79cc2fc332aad6b0e6a056e9eef7fe74f2200c6847ba48e046c19,2025-02-27T19:15:46.720000
CVE-2022-49697,0,0,37f111100890cc8a6c4b57f219ed290637e7ffd09bf2ee8aa7fbd97234b28102,2025-02-26T07:01:44.450000
CVE-2022-49698,0,0,fba7b0d95440675c9697f9f8e91bea4daa74a5f528c74ed01b53c2bf59757c3c,2025-02-26T07:01:44.547000
CVE-2022-49699,0,0,5533ed2ba7ccd3ba1f9cebc8dbb8c1bfe21a97d92d0c02d9244f66885a67873a,2025-02-26T07:01:44.640000
-CVE-2022-49700,0,0,78d750225653a616b885035698d3dac15a97785171065fa32f7014d7d9064334,2025-02-26T07:01:44.740000
+CVE-2022-49700,0,1,bcb5bc5a5a9c92c2fcbf5f25c3c801ccd1887a607c2e4a334f1d47d78b522c69,2025-02-27T19:15:46.863000
CVE-2022-49701,0,0,62aaacfd738b64040f01c3737dbb2861a3f8ca018a5bdc10ec9b72eafaaac2b7,2025-02-26T07:01:44.930000
CVE-2022-49702,0,0,2f4cf6c65f94da646144a2a1f2ca00e40c2bcfe05a985ee462e1e10492edaaab,2025-02-26T07:01:45.827000
CVE-2022-49703,0,0,2106d8835fb296a6e80ae1004028b21c13a37e45bf665be0c4fb766796980951,2025-02-26T07:01:45.947000
@@ -213889,7 +213889,7 @@ CVE-2022-49708,0,0,8e5427a95a7a8ae48ba2005d5e7b81e5d1b63e8415240ab48ed3d8a1fc31e
CVE-2022-49709,0,0,98473eea65ada0d06fb88733cf1c4e3e4a5573b33e161a3350e00c132677e4cf,2025-02-26T07:01:46.710000
CVE-2022-4971,0,0,8284339847d56a982dc79d79b0900fdcef988337c6504d3d0fb43eff5f9bcb0a,2024-10-30T16:37:33.237000
CVE-2022-49710,0,0,592536be5e15dae2963c97160e23b05940c3349928e5284d53386b96a89b74ad,2025-02-26T07:01:46.800000
-CVE-2022-49711,0,0,5e3d9648df664b4632c9d332ff1c5c700d69eb46b910d181f94eea0ffadcbbea,2025-02-26T07:01:46.893000
+CVE-2022-49711,0,1,355f1e29575ca9651a852eb406c992a0416e94c3441698bb8d722241ce3db9fa,2025-02-27T19:15:47.010000
CVE-2022-49712,0,0,3ee9b40ef91e04be44077581722686fbcacedd0401937b766e99d40f64d75938,2025-02-26T07:01:46.987000
CVE-2022-49713,0,0,c427b68c2cf55fb03ab35896d5ce5c90add114036430b8a5bfe36f5da4ead55c,2025-02-26T07:01:47.083000
CVE-2022-49714,0,0,0e59cd9560bea73e18001122356eeb5c7511354b09b3d34caf687afcfa073fed,2025-02-26T07:01:47.170000
@@ -213910,7 +213910,7 @@ CVE-2022-49727,0,0,ac6a51f7d9b208ce4fad40013a4b9693227dff65516f8a58384c0782ada1e
CVE-2022-49728,0,0,221085aae52fa8aedd1439e92f6f732ee88405dc351e60ea4ea82576c7d83d7f,2025-02-26T07:01:48.433000
CVE-2022-49729,0,0,9dcd52103d8ff8d3cee28bf857d4b545299bf73125d081c11fcdcaf92a2cae34,2025-02-26T07:01:48.523000
CVE-2022-4973,0,0,3f7bb8af7d8ad41d4b8c2b6df6303f0dad9415526c1ebfae5140748d302176bc,2024-10-30T15:58:30.907000
-CVE-2022-49730,0,0,64eb3d78ac04b8105d9b8a2318c8ed002f1f70a14f90c0bd037bbd57747fe8d7,2025-02-26T07:01:48.620000
+CVE-2022-49730,0,1,2bfdce97189f4294a4f5bd9bb6fb8ea7daf4ec20279fe3e8023054ddc72e2701,2025-02-27T19:15:47.153000
CVE-2022-49731,0,0,3087aebf92cbb510ce471fc8272df920f283560767e2c40c990611543a35c126,2025-02-26T07:01:48.710000
CVE-2022-49732,0,0,357e26d46f1a26687bbcdbaccaf2828e1a219bc057c20eaf6d9b9cc65a408ec2,2025-02-26T15:15:17.843000
CVE-2022-4974,0,0,b3c59950ee3eade0f74a15ade2edad03cf700537d377a12415779325d85e4da4,2024-10-16T16:38:14.557000
@@ -218611,7 +218611,7 @@ CVE-2023-23315,0,0,7f211b20f8879185076392acff7b806e30e631935376086702fbcab39b12a
CVE-2023-2332,0,0,da44be4c9a914607350af7cdf1b1da16efda7b342df7dcfe63c493c785f8f06b,2024-11-19T15:55:24.137000
CVE-2023-23324,0,0,5d48828077c8be90528b04711cd87bf712a72c1a2913ba049bb8d673723ba347,2024-11-21T07:45:59.480000
CVE-2023-23325,0,0,518dcf9a2af100841b84c73e77aead56932b04d21c668e4e673d1b9b408ecbdb,2024-11-21T07:45:59.640000
-CVE-2023-23326,0,0,671a267bc297a794c821a6b7b2ac359a9ef7356dbdb7d39183bee70fd49c12c8,2024-11-21T07:45:59.787000
+CVE-2023-23326,0,1,1a4e39362f1c8791076d367fc23df696eb59e6884fa5b2335a9fcfd232e3f37d,2025-02-27T19:15:47.783000
CVE-2023-23327,0,0,6da2ce2cc26156b13a1b95f743a9753609f58547ad519cbf4c93b3a27b663a72,2024-11-21T07:45:59.933000
CVE-2023-23328,0,0,8b7f9244b0915a9b56758c5e614f7cb7fe95d9dce3a04a7593556df54a35d4ba,2024-11-21T07:46:00.090000
CVE-2023-2333,0,0,49815d35ba5652045e1256f3d4e37c7e202552cb53ecfa1b0d6fb27fcb89f551,2024-11-21T07:58:24.400000
@@ -220304,7 +220304,7 @@ CVE-2023-2528,0,0,7354ad96239bf796c6cbd6ba58728972cb6fb7255bae028f505e752f2e6ec6
CVE-2023-25280,0,0,a79c3cb01158c75cebb6ca46dbda57415199643ec1f65d6581773efff9df270f,2024-11-21T07:49:22.837000
CVE-2023-25281,0,0,08a99eed9edd45cf107fcd3f103157d21f276d9348825d0b3afd565c9dcd6a89,2024-11-21T07:49:23.057000
CVE-2023-25282,0,0,f816cb37e750e78c1fe070772f27931ee830b2aa8129db9fffc29b2562f70ec6,2024-11-21T07:49:23.203000
-CVE-2023-25283,0,0,4b599f9b7c79a455a2deecd0341e3515e8ef97b614cf073193430733a2cf44fa,2024-11-21T07:49:23.347000
+CVE-2023-25283,0,1,5f356e0d9f59faa52b6e5bf0560e1bd2b7ce0198ae0f76caceeb35ca6da8acf0,2025-02-27T20:15:36.397000
CVE-2023-25289,0,0,329ff7443b569815cbc864f61fb485ad78c0c94d2eb5ca2650f4ea870fb1efd4,2025-01-29T21:15:14.523000
CVE-2023-2529,0,0,e0c597e5f44df4f0fa35a31922c8c63e9eda9621312de091657b5b531d976868,2024-11-21T07:58:47.050000
CVE-2023-25292,0,0,3f06b791e0f858743cc9523b1e9506d3377c6b13955495c0f2e922089d530295,2025-01-31T19:15:11.643000
@@ -220324,7 +220324,7 @@ CVE-2023-25330,0,0,08f3ee33c083dc703c8c8ce32873b303743eeee4c637ccb5438853532d2b5
CVE-2023-2534,0,0,2765d8e31a6947ae0d35fb13d15df7a661ee4119acfec516d581783fb3089e47,2024-11-21T07:58:47.543000
CVE-2023-25341,0,0,a6c0ae09f38d0a080f9399b91e16f70d20e262ee8151f1a5c7bc5a49f687504a,2024-11-21T15:15:09.430000
CVE-2023-25344,0,0,146165727e4f96e86ffd30149c000b525f7a1da629b64e33c9ea664dc8c6e5d1,2025-02-27T15:15:36.880000
-CVE-2023-25345,0,0,3047d7e94bcb27ce1963bc1007e57600c1401bd6a1e52384238fe1fc44a5b2f8,2024-11-21T07:49:25.413000
+CVE-2023-25345,0,1,ba9755738845722150d5665c294ac2196196f903988e6e0701bffbf5b8b52bdd,2025-02-27T19:15:48.070000
CVE-2023-25346,0,0,1545a193327540134d9d675ee16977b31fe2260b58497e6c55a05aab12a877a0,2025-02-03T19:15:10.233000
CVE-2023-25347,0,0,7dd18f4e49becbf7027509d47983052d9cc5e16b21885845ebdbbaf2c5086acf,2025-02-04T17:15:11.847000
CVE-2023-25348,0,0,7b24e64ac0df04bfc1b24e00ef9e1851d7c486926aa7bdf9d8bc8b9ef222eb15,2025-02-04T16:15:34.780000
@@ -220530,7 +220530,7 @@ CVE-2023-25591,0,0,fc4f6fb3fc9918c1817ba808559e7c27b005f9a0ba1c5880d822b534ea41f
CVE-2023-25592,0,0,b81ed0ff74c765ecc9aba16f9320ec1800540a681e798d80755d140bab2fe509,2025-02-27T15:15:37.023000
CVE-2023-25593,0,0,4693ee6cde961d3b3ba80524ee4ae2a0f29de2b7c3858fb913ceb41b4ebd6820,2025-02-27T15:15:37.180000
CVE-2023-25594,0,0,68933931bd5eb08871ff88f8f6718fc206241addb8bf9e6f06f49b865f4e1fff,2025-02-27T15:15:37.313000
-CVE-2023-25595,0,0,726a4d03782813d387168e4496552502f96f8a0a02861e47f01e358207039d15,2024-11-21T07:49:47.773000
+CVE-2023-25595,0,1,954f8ff1cecfe7c9d7eecc2d7fc1d28df87816b2c244b672d1e460fe97b92eca,2025-02-27T19:15:48.220000
CVE-2023-25596,0,0,22fd223f38dadc90cb60a3e027b685e25cdb48761e367c792452f52201dcb81d,2025-02-27T15:15:37.443000
CVE-2023-25597,0,0,3cc8467908e0af0563c0dcccea858dd0d6f7cdf781593c0d30cc7f58d8e064ed,2025-02-07T22:15:11.907000
CVE-2023-25598,0,0,feb063d3ad1fdbfaa91ec631b072563c17f1eadc253a15c5a5729735749cd8bd,2025-01-17T16:15:29.543000
@@ -221524,8 +221524,8 @@ CVE-2023-2680,0,0,cf811b98841f1513c2c9cc882125b088124ad707dcf6c3cabcc0da07e5dc52
CVE-2023-26800,0,0,32c4ecda2304fc0385dd7ccf4b9de7b489e2cebbf0350eefb1a795c962981f66,2024-11-21T07:51:57.460000
CVE-2023-26801,0,0,44388b9c6e89b71c24dd01a160c99493b222b6c039203123d6783342247000f6,2025-01-09T21:15:22.297000
CVE-2023-26802,0,0,1a739e1530094a4ab46a1861f858a10caae4fd9cb2756f2b601d8b6650469fe5,2024-11-21T07:51:57.747000
-CVE-2023-26805,0,1,b5d78d7ddf04a489ac3bdd0e4351233f6ab2c77781d3a28f13efe92343de35e3,2025-02-27T17:15:15.200000
-CVE-2023-26806,0,1,f2479838fdbf1ee6bf1d4d8151002c6c1143cef7b91f704ea77128a9c133317a,2025-02-27T17:15:15.370000
+CVE-2023-26805,0,0,b5d78d7ddf04a489ac3bdd0e4351233f6ab2c77781d3a28f13efe92343de35e3,2025-02-27T17:15:15.200000
+CVE-2023-26806,0,0,f2479838fdbf1ee6bf1d4d8151002c6c1143cef7b91f704ea77128a9c133317a,2025-02-27T17:15:15.370000
CVE-2023-2681,0,0,41cbb61ca9a35485083109dc074905f734b530fc114e7942a6caf79bd39c2500,2024-11-21T07:59:04.433000
CVE-2023-26812,0,0,405afcd0d18a0ea560dd97c3f75aa90f8bace35b4b99f4dead56b89234a96ab1,2023-11-07T04:09:42.520000
CVE-2023-26813,0,0,11a48edd361ce82d55979cd322e105c7033d8d2b582c11ad569e0eed6257a0e0,2025-01-31T17:15:10.587000
@@ -221569,10 +221569,10 @@ CVE-2023-26877,0,0,819fec43b298c379330673814a83ac2f67016786a169e0e2c35e2972ce86d
CVE-2023-2688,0,0,cedec86db964478a0639bd24931697a753774c108b42310b901f6ac178a61fda,2024-11-21T07:59:05.267000
CVE-2023-2689,0,0,cd3664900b9908c1b5999d712f88124d2222149bbec583c14312e015f11a9c36,2024-11-21T07:59:05.380000
CVE-2023-2690,0,0,d5757ba6cd65b23e63085965cac54915f7979de8accfd333695aecedd9f0eb87,2024-11-21T07:59:05.513000
-CVE-2023-26905,0,1,f47e4f9d80878893ff2d354cb59182f41dcacce5fbfb079d96458b5c64df3de4,2025-02-27T17:15:15.523000
+CVE-2023-26905,0,0,f47e4f9d80878893ff2d354cb59182f41dcacce5fbfb079d96458b5c64df3de4,2025-02-27T17:15:15.523000
CVE-2023-2691,0,0,cdad972a5b1dab057475eceea91b8b4e4026bc1b9e8ac8399b2c1d0f44fa14f4,2024-11-21T07:59:05.650000
CVE-2023-26911,0,0,3c699ec1125fd44557b4cc318bbc724cc49305c037cd57a71dc1c77604421632,2024-11-21T07:52:02.973000
-CVE-2023-26912,0,0,cc82d907f2264644f2eb78c39d7d27bf176738b96b7b283566a267dc32dd9582,2024-11-21T07:52:03.133000
+CVE-2023-26912,0,1,d6cddf8b60e79a6c6b54d6bf89b60b0af9af7cf273188b00bf4c4de512bb89c5,2025-02-27T20:15:36.577000
CVE-2023-26913,0,0,daf6e3585a7ed0249ea37f260c167a69001cd51ef355afc64cddc00b14b53f37,2024-11-21T07:52:03.300000
CVE-2023-26916,0,0,497f635c8dba305fbce8fab06f9d3581177331fb53214aef703a9fe9f75e5b3a,2025-02-18T17:15:16.370000
CVE-2023-26917,0,0,194a99a53507a39df42526194e8d2506a79a7f17d25af812d6883f6f110580ce,2025-02-11T16:15:36.753000
@@ -221678,8 +221678,8 @@ CVE-2023-27067,0,0,f36270d0e6b8a42da033e1bd3bba8a027c28883ffb03b777722d4120ea30a
CVE-2023-27068,0,0,e431ed6fb399fc4497dda9a53200e774963211d0ed3f66b4fe98479433e88230,2025-01-28T21:15:13.647000
CVE-2023-27069,0,0,49ac387c47e6c2c01b238e1e71d94da751da2a76c545730445adad06ce8d8dc0,2024-11-21T07:52:15.947000
CVE-2023-2707,0,0,962e941311c97157758bc3df446195a5bfb2263a2f9839390441282872836d76,2024-11-21T07:59:07.690000
-CVE-2023-27070,0,0,f5c115ac6729f39a464f4207bc6e21a6f6ad3ed79d5368304a99edf499a31e8b,2024-11-21T07:52:16.097000
-CVE-2023-27073,0,0,5180eabfb6c2f9fb0cf327e08648a6cb810bf0ef5c6fecf67aaf9410b195aa41,2024-11-21T07:52:16.240000
+CVE-2023-27070,0,1,fe0200dfd226360ca8307efe7eec64f43dd15f6a114ae016e6b27c6a1176b088,2025-02-27T20:15:36.750000
+CVE-2023-27073,0,1,0c742be2452ab64f46716a20bbecaac07125b48afa997a93f10f5a8b7f29422e,2025-02-27T20:15:36.933000
CVE-2023-27074,0,0,5080e554afe56803022441296bc3b4afc8d4f8252838f35a6b53ef2afbd6c033,2024-11-21T07:52:16.400000
CVE-2023-27075,0,0,05401ef8dad2a53585eeb54c832eb5c4fccc837d5d2374406a156351e1941c17,2025-01-29T21:15:14.853000
CVE-2023-27076,0,0,f921e69d91d66430166831ec089477ac491137f2974df9d34ffac5349d7ff6e2,2024-11-21T07:52:16.703000
@@ -221782,7 +221782,7 @@ CVE-2023-2723,0,0,ab4dd6713a3655efcde860e3e36522d2a86a43809f95e26614f147dbc2b11b
CVE-2023-27231,0,0,757a4dada5a53e2af84d7043b4cff180f4f47d85f0b702e47b1f10302e8926e7,2025-02-18T21:15:15.820000
CVE-2023-27232,0,0,a26890078e5f81e90b1536c128f8ece0c54ccd9d13ce734b3c13316764dc2f9f,2025-02-18T21:15:16.040000
CVE-2023-27233,0,0,994f850112ed4f229ea119f753b0d0f877886e6fcdd0f4225e5f9ce183fae55e,2025-01-22T20:15:29.997000
-CVE-2023-27234,0,0,8a7752bb1b30f5109f35237cc28f0ace1198d6b8423fb706790cd6275247ea06,2024-11-21T07:52:29.960000
+CVE-2023-27234,0,1,75d9b71ade4df35dbec5c9a84bc8f2bb1e016b76068164c49727900e1613ff63,2025-02-27T20:15:37.103000
CVE-2023-27235,0,0,c60453614f616d535021868dd641756962f30770bab77e2c62e439343b77ec43,2024-11-21T07:52:30.097000
CVE-2023-27237,0,0,e09f60848d34f83c21a67da1938fe74ef21b790eaeaa3d9fbd20f0f0b76350dd,2025-01-24T20:15:29.370000
CVE-2023-27238,0,0,d98fc7eb90e07475353f284ec45b33ba5354b97f9b17f461e52280af1f4ddb4c,2025-01-27T17:15:10.970000
@@ -222596,7 +222596,7 @@ CVE-2023-28140,0,0,705b54b75e60ef3773b64c123f4286273ae70f9b6215f3301c95257fe9f25
CVE-2023-28141,0,0,51091879e23c79cbc236a16b2984e2dd44af6d972b83cbe9cb3d897ad4c9b78d,2024-11-21T07:54:28.663000
CVE-2023-28142,0,0,bd9825929300d00d5460431b11a1d8581d243cf18cf72f977e5bffa48978cccd,2024-11-21T07:54:28.780000
CVE-2023-28143,0,0,f4bc53a7895bc10a274f857dc90ffe925bdc4ed21c97eed7b01b695eb8524c4f,2024-11-21T07:54:28.893000
-CVE-2023-28144,0,0,7b641e2a61d30ee74a394a747cfa58dc7b196df561608c2416ce095c8b0edd10,2024-11-21T07:54:29.017000
+CVE-2023-28144,0,1,5437b148a8672ebd217253cc9d82a0cbf8bd2eb1202e722c2e44ddf21dab7b96,2025-02-27T20:15:37.270000
CVE-2023-28147,0,0,f30f408b0910c6b0d7ba587f5aad0dba11a6e0e727d207232a331f413e692c42,2025-01-09T20:15:32.090000
CVE-2023-28149,0,0,08c217aea9c71601c56c1c111b48b7078ef7d7590f65ac919a87a2b9b826f62b,2024-11-07T17:35:03.810000
CVE-2023-2815,0,0,3ea6ea96842ec8c8be5ef2cbe7a9dac57e5243b16578e30f83427e5557cedb1d,2024-11-21T07:59:20.597000
@@ -222604,7 +222604,7 @@ CVE-2023-28150,0,0,7e233abf787b6be455448286692cf055225d89667dc1f8b5a70d223aface2
CVE-2023-28151,0,0,a21bd82f7fe4dbd197fa6218c144a0e9061484d9125546943589c671c5aa358c,2025-02-19T22:15:15.893000
CVE-2023-28152,0,0,fe585acc1eddd1859486c73e3b1acdec109dba4b88f73a29c3af4d631b017828,2025-02-19T22:15:16.077000
CVE-2023-28153,0,0,1086938624151d40d3f408cb17fc2205d9f7b96da58014fdffcb9fba3e1b73cd,2025-01-14T18:15:24.700000
-CVE-2023-28154,0,0,1789c944dd2f50f8e2f8697e5dad5368024e3d322efada71217c4cf620c70f0c,2024-11-21T07:54:30.030000
+CVE-2023-28154,0,1,23e26bbef546a3a12f8f321acf5c24e732251f9183c7931d982fb4523cb0488c,2025-02-27T20:15:37.440000
CVE-2023-28155,0,0,5f10453fafa7e761d33f7605b8a870efa0c943633ed9cc3fbe760cae904558de,2024-11-21T07:54:30.183000
CVE-2023-28158,0,0,b22194a2295a562d894ae8aaf523c794c2432dec80b24116f99f9595acd5aeaa,2025-02-13T17:16:14.527000
CVE-2023-28159,0,0,3a449c52c7ba4013bcdbfcd1295eb1a399ed8fac434b5151137137ea4a69c7ae,2025-01-09T17:15:09.523000
@@ -222782,7 +222782,7 @@ CVE-2023-28335,0,0,0db396a467aafa77c41bfe6421c217d0b35f2a7bf265a8db14b97b4d3af48
CVE-2023-28336,0,0,977e30edea99b3e9a8387702efc2b99158e285246b50cbecab8eeac049761e4f,2024-11-21T07:54:52.450000
CVE-2023-28337,0,0,13848ff2a6c1eae9ad862b68cd48b78bbfd135364ce54e198fd30f6baa7ad7cc,2024-11-21T07:54:52.573000
CVE-2023-28338,0,0,d5ede69190089381c814b0406dd2a4497792ebb5ec2d48dc8d45223832afc3ec,2024-11-21T07:54:52.673000
-CVE-2023-28339,0,0,28c8c80e2f8ce8af2465c32d4337cdf8a86c18afe3b61985d49f8355cb8b98a4,2024-11-21T07:54:52.773000
+CVE-2023-28339,0,1,3a4b878377a97639e9b08f5d0ae41d9bc8e9b3ad6a4d445080104d1802d46424,2025-02-27T20:15:37.613000
CVE-2023-2834,0,0,e63c9dac15f30931d83cefbc2177860a1a94d254b76bc44ed8548a0364c3b9f7,2024-11-21T07:59:22.907000
CVE-2023-28340,0,0,52b134d20e2ac02ceb625f802afb06138d905f98220d628ba7678e3eddc44842,2025-02-10T21:15:15.530000
CVE-2023-28341,0,0,b3028edc6ce55e79e394da39438042c3ca983d0fa87c613f9d7d58e1e326bf35,2025-02-10T21:15:15.707000
@@ -224784,7 +224784,7 @@ CVE-2023-3087,0,0,26b7cfb975445200143a9d9a01ddc2b1346846cdb6963af33839f4e5ae7398
CVE-2023-30870,0,0,9ca9bf8c4508007a0d146a2061ea43e28c5f89d64096d883498a9e5c27cb1a57,2024-12-09T13:15:28.283000
CVE-2023-30871,0,0,c7872b1619856c6bcc56883c585cee901c2a20f5ea0251d3991cf7e237cee272,2024-11-21T08:01:00.683000
CVE-2023-30872,0,0,33cdbcb60ea7a092a02f45b3dad93b21cdf3d81676d4b7902f086c7764b18fef,2024-11-21T08:01:00.817000
-CVE-2023-30873,0,0,c910bc8f31e44604e94ef0a68f1f9934757a885665b15ce13c7b197c5d79f22e,2024-12-09T13:15:28.413000
+CVE-2023-30873,0,1,9c82e0bd8ca1c132f975ed9c12b80369b0fca21b81e1359eff9b330b86f10da9,2025-02-27T20:54:25.290000
CVE-2023-30874,0,0,492ad1d5a025de1cbf1e8cda85dbb296790bd9c6972d7d63b32d0b2af406e60e,2024-11-21T08:01:00.940000
CVE-2023-30875,0,0,7746891135aa95b101c333d7f919bde62ad026de0f55f12be4e8ac10e98e7b91,2024-11-21T08:01:01.067000
CVE-2023-30876,0,0,ff4c8817ea640a8bb8466c3c54938ea962dc0e08f97b8de22424bf7818d8b5ad,2024-11-21T08:01:01.210000
@@ -240807,7 +240807,7 @@ CVE-2023-52231,0,0,5e4a367c83f1d32f7b9bb506fbc9b06f33d3a94154bf0a91100b28707f69d
CVE-2023-52232,0,0,25816897725e03b2601314f3c9389a2be7d7e262fad693583de240b223ce3938,2024-11-21T08:39:27.053000
CVE-2023-52233,0,0,2423e3afa7be038ccf2190464fe2d4c37e2d909a99b6b2c713bd1ae6e307c147,2024-11-21T08:39:27.173000
CVE-2023-52234,0,0,c9a6ddf29001d4456c812ec430c4f36fbd95f7613bd149eda7844272c0c580b7,2024-11-21T08:39:27.303000
-CVE-2023-52235,0,0,8d5e3157d335646999bc111d8ded8a13358c93e41595e9af6c66e81174d62067,2024-11-21T08:39:27.413000
+CVE-2023-52235,0,1,38fc0b124e8fbe66aaf7d1f1df9b950ee33f38eef712db18d6428c2cb89643d8,2025-02-27T20:15:37.787000
CVE-2023-52237,0,0,35b360d50e9b760121f1889838e48d89835ed64825be99fdf2607288a371a69c,2024-11-21T08:39:27.630000
CVE-2023-52238,0,0,ddeb2d67268fd9503273f3eee20bbffb01b1f003b7c33b1b140bc6ad77862bc7,2024-11-21T08:39:27.907000
CVE-2023-52239,0,0,975843b60a991a7ca32ada6646038a0e79b2695391b0152241641e0cb4ea009d,2024-11-21T08:39:28.023000
@@ -251244,8 +251244,8 @@ CVE-2024-23607,0,0,3fec5058d10d6cf455674d1c6284bb37392a28907ec5aace1fd1b3a1426cb
CVE-2024-23608,0,0,f4f0d3dc90613d42fc8485a3197c71394b07fbc0df27981f4d6ad3675d04a364,2024-11-21T08:57:59.797000
CVE-2024-23609,0,0,b90f833366370fe43c05814eb1526887e7cb7b82ee5ea7a039ba9de77d7a868d,2024-11-21T08:57:59.930000
CVE-2024-2361,0,0,cdeca1550c32896fb6fcfb15aca13512200106e857f7cb5e97a4410236124f83,2024-11-21T09:09:35.667000
-CVE-2024-23610,0,1,b0b31c31b2c149c5d0eb2577a4b64475d3597634dc8d673c5f8620673e4b367b,2025-02-27T17:48:34.007000
-CVE-2024-23611,0,1,4df2763245b0194ba29f095413d2e3a6fdd428a0ed977ea6e2a15e1eee3f3d59,2025-02-27T17:48:34.007000
+CVE-2024-23610,0,0,b0b31c31b2c149c5d0eb2577a4b64475d3597634dc8d673c5f8620673e4b367b,2025-02-27T17:48:34.007000
+CVE-2024-23611,0,0,4df2763245b0194ba29f095413d2e3a6fdd428a0ed977ea6e2a15e1eee3f3d59,2025-02-27T17:48:34.007000
CVE-2024-23612,0,0,551735fff18ffc2995a076082860564c5e565633c0eafd5540439eb1e549a92d,2024-11-21T08:58:00.307000
CVE-2024-23613,0,0,ea291e9fd6b4d44fcb5d97e10e844e3125f572d53da45562752a87eb16c83c0d,2024-11-21T08:58:00.433000
CVE-2024-23614,0,0,e9787ac51b1997f2606c262d5dd2661cc5dbff1459a490eee975cea38268443a,2024-11-21T08:58:00.580000
@@ -253512,7 +253512,7 @@ CVE-2024-26731,0,0,93df8098dbc8b35339297c34d2cc186ab96abe59edc56773a7bed56c8ef33
CVE-2024-26732,0,0,93d68c2245823b23f9cd1f7e63a32b54ddda53966feab1e3f497dd7c79e0833d,2025-02-03T16:17:25.537000
CVE-2024-26733,0,0,da33e07722e15d2f0a18149ad788ee6ccfc0a2e4bd4d72b5d551c09bc1b88e06,2024-11-21T09:02:56.620000
CVE-2024-26734,0,0,03f25116197f27b888005564a660d6eab1968d4dee38a6141c97d50d1126d43c,2025-01-14T17:26:43.583000
-CVE-2024-26735,0,0,23416017cb42c35b17ab61282110d884834e0c54e876d15ce4bdaf6d667bf541,2024-11-21T09:02:56.883000
+CVE-2024-26735,0,1,30e8628d9f42aab284fe6448f31e57be199d83e5b82fc9070fc6b1a0ed99caec,2025-02-27T20:15:38
CVE-2024-26736,0,0,b29129ddb5d3afb3852cff1b0fe131c66351f86286513d203d1c2dae3f9ca5da,2024-11-21T09:02:57.090000
CVE-2024-26737,0,0,03a6f3a24bd6f11bc15a839c4e708d9160bb2b3e53fb885adad418a2aca958d6,2024-11-21T09:02:57.210000
CVE-2024-26738,0,0,7401dc8ccba47014fc09b50b349b2fbe5d1a660cb458a9c717c4b0bf3e62c9a2,2025-01-07T21:13:43.273000
@@ -253682,7 +253682,7 @@ CVE-2024-26886,0,0,dd647380a56ebf8acf36498a32884a21c01f77b53c500fad9b448c6df387a
CVE-2024-26887,0,0,3251ccc7a70790e196686afa8951af70ae741b2291763bea2e84a28b5f78b248,2025-01-07T17:14:41.810000
CVE-2024-26888,0,0,74846900da7a6f8b09026caa9be4b4eccab844d24d851aaa854a0bea0b7158e6,2025-01-07T16:43:58.107000
CVE-2024-26889,0,0,a7b27130d8d4ed99b70cd338114a084bdd22e0e2f2a4841c89823888e896a69a,2025-01-24T16:15:35.380000
-CVE-2024-2689,0,0,efd9c698169d4dc6b507d633d5c5bca5635fd88f4fbab04c5f54592266ffc962,2024-11-21T09:10:17.947000
+CVE-2024-2689,0,1,6d24802a118571bb28d9feedd06f3dfb287633f44ac16b8686b487208e72f45d,2025-02-27T20:15:38.563000
CVE-2024-26890,0,0,d28148780134fe9d4fd26b89472d475a8cd9fd94507e1d0beb5192c2d01a8c30,2024-11-21T09:03:18.677000
CVE-2024-26891,0,0,18ef1231e3dab94fd46bd51769a57b4742af39b60702f0ac393cf1e3791be7b3,2024-11-21T09:03:18.877000
CVE-2024-26892,0,0,dff3724f39f4f7d27824ec776eef6bd6154cf578f200db90d4aaf7ae8dcb96a7,2025-01-14T14:34:50.407000
@@ -254077,7 +254077,7 @@ CVE-2024-27264,0,0,f19cd12d9cfd08306f329c4a07156366819b05a23c905069a90f1109f1306
CVE-2024-27265,0,0,503786b57301ba8f6178e18f9e45624064bd29cf748a0b95c345d7c29dce0e4f,2024-11-21T09:04:12.433000
CVE-2024-27266,0,0,8354de79cabd73f9a0b21f06f2a9cfd665437e90c03c063357f6339e60cc24a3,2024-11-21T09:04:12.583000
CVE-2024-27267,0,0,a5d8693bf68d611ea6b320a17ddd770102a308dc1e0715bd0f998cd807a76f32,2024-09-11T13:48:12.250000
-CVE-2024-27268,0,1,2dcbf6964ce8e8841ebc29f79e8d8a5330f19a8a65f2e49de73dbb87cd15e97e,2025-02-27T17:58:20.883000
+CVE-2024-27268,0,0,2dcbf6964ce8e8841ebc29f79e8d8a5330f19a8a65f2e49de73dbb87cd15e97e,2025-02-27T17:58:20.883000
CVE-2024-27269,0,0,52ebdbf805213627c28de793c9dc09dbda04abee28bda6abc5aa430114512ce8,2024-11-21T09:04:12.937000
CVE-2024-2727,0,0,2dee61faac028e2733757e135f6a6c2d9e9cd5dd69c05078e33394419bac0651,2024-11-21T09:10:23.127000
CVE-2024-27270,0,0,54ba2c12ac2b208b283b3485434ba442565d1321f86146b753258ad980afdf25,2024-11-21T09:04:13.080000
@@ -254157,7 +254157,7 @@ CVE-2024-27341,0,0,13da6c7d33e066a09b0d4d4dca1b40112998d6acdc4daf4324465ecb51c87
CVE-2024-27342,0,0,44118e0720a961c463831ac7c838f43df76ddfcaa3e2aa548a24a4369e3158e9,2024-11-21T09:04:22.547000
CVE-2024-27343,0,0,bfb103bab70a9b7272b453e97e45c2d5c6419041ca4715804f06f39cb507a575,2024-11-21T09:04:22.677000
CVE-2024-27344,0,0,2b2469f12515824f584f118a281d1a413dd821722b40f8da0255a4bbb6dfe54f,2024-11-21T09:04:22.803000
-CVE-2024-27345,0,0,a23b69ba340cfa7022c84427fc318cd5e45df434c20ceeaee926a2f95da2a56b,2024-11-21T09:04:22.933000
+CVE-2024-27345,0,1,5302856250baab7bca128752a37153ad7a81fb0b5758186316dafc67abd8d57e,2025-02-27T20:15:38.220000
CVE-2024-27346,0,0,4ef1236f8b7db87812c0165f7f7fb6230e69020f019ead98bf2a8322c5b12458,2024-11-21T09:04:23.063000
CVE-2024-27347,0,0,dbda497b12017e7409f9dc9e20d1261b56f61b10be208d0427d8ee6a8ba51174,2025-02-13T18:17:30.360000
CVE-2024-27348,0,0,cd3e6bcc5d604a91770782a700f1b85a4be37029b865210a45885b66999bf8d0,2025-02-13T18:17:30.597000
@@ -254330,8 +254330,8 @@ CVE-2024-27592,0,0,4856715747f7e20c2fb321622fc57fd9edfc011ed7744e2a258f43e955c82
CVE-2024-27593,0,0,92ecd1489d3acc10d1eb18f4eca08862b4e86cc263358f230cf130b24876abbe,2024-11-21T09:04:47.107000
CVE-2024-2760,0,0,f247d3efc0421c7eb31f935977b8c3c26cfc0a17d562839ee78e4c92b4a167a4,2024-11-21T09:10:27.283000
CVE-2024-27602,0,0,635f2ca656f5be7a2a2ef94a7eed70091f4dbaa306ab7a8309551d68cb2118a4,2024-11-21T09:04:47.327000
-CVE-2024-27604,0,1,ace66ba317050889a478a530e8f48bbda50b0527c00fde281c7915e4f74f2d4f,2025-02-27T17:58:20.883000
-CVE-2024-27605,0,1,f9175c9a8fb8e4af06535126ab724729e1bac0d1009e4f0c2b4c015f03ea199d,2025-02-27T17:58:20.883000
+CVE-2024-27604,0,0,ace66ba317050889a478a530e8f48bbda50b0527c00fde281c7915e4f74f2d4f,2025-02-27T17:58:20.883000
+CVE-2024-27605,0,0,f9175c9a8fb8e4af06535126ab724729e1bac0d1009e4f0c2b4c015f03ea199d,2025-02-27T17:58:20.883000
CVE-2024-27609,0,0,e0d5cf97c16d28e3d1b2a8de7800020400e5be5d064b79a2c8845cd4b08e76bc,2024-11-21T09:04:47.803000
CVE-2024-2761,0,0,adee496e3513e93132287faaff0ce6be7096cf9f85fafedfc4238afd9176f9eb,2024-11-21T09:10:27.420000
CVE-2024-27612,0,0,b540c5f25f4fe6992ab18fbdee8303ebec0a2ad3e75d915f7f3e317a8af58a04,2024-11-21T09:04:48.010000
@@ -254552,7 +254552,7 @@ CVE-2024-27906,0,0,4aabf7efe7321163c3a006a7612eec109447384a538844fd5acf0a9ee7d33
CVE-2024-27907,0,0,93a68ff71d3aeb34f42e681e9dbe8b630d16db6c3637b4d175bc07a7bf1a29ca,2024-11-21T09:05:23.727000
CVE-2024-27908,0,0,840cdafd91ba5316553d234a9ffe03fc9fc46a31b723f45c70182dcee40a4254,2024-11-21T09:05:23.857000
CVE-2024-27909,0,0,f7fa7e105accb9eb0c4b6b109fe14e65b7b64d13c1aec10d06a022e4e69f8cd6,2024-11-21T09:05:24.003000
-CVE-2024-2791,0,1,d092c3ff292deeadd4d5d080f8d684841852cbc4c2e7500f82bebd8411ca427d,2025-02-27T17:58:20.883000
+CVE-2024-2791,0,0,d092c3ff292deeadd4d5d080f8d684841852cbc4c2e7500f82bebd8411ca427d,2025-02-27T17:58:20.883000
CVE-2024-27910,0,0,52110fcf713ce50faa77f0c1619a760331146fd3de5cf9c77fdbc6eecf746dc5,2024-11-21T09:05:24.133000
CVE-2024-27911,0,0,163d4032cccefd06169212e4b4f3531d5c43c99d1d0f8350d0f1bdd5571d171c,2024-11-21T09:05:24.283000
CVE-2024-27912,0,0,17a916159656f5b71e76460ab9dd8159bb40a0e837babb274b88d74bea610fa1,2024-11-21T09:05:24.420000
@@ -255060,7 +255060,7 @@ CVE-2024-28676,0,0,f0e87c474f5cd94c9c0a360ae3e4b29f0c55c5b9cf00b4c9204038ea97ae4
CVE-2024-28677,0,0,8135ecd2860e9918720503a973e6b70ae86292a85588521142ee4270ffbdc123,2024-11-21T09:06:45.597000
CVE-2024-28678,0,0,b297beb058ef2954362c94584a9c654b760016ed6fb653bfe093f1f20dd79e10,2024-11-21T09:06:45.817000
CVE-2024-28679,0,0,6f8b96e72bc5d8aed16297df3fc8d835288ed1497cc3fbe7b3bf726aa4d75453,2024-11-21T09:06:46.053000
-CVE-2024-2868,0,0,8c9a9ecbc1344c52ccfcc28a4e126a4f8658f677aa0141de36cdd758a9619c61,2024-11-21T09:10:43.007000
+CVE-2024-2868,0,1,c87003e05e723d134eed34e8ff1c5739901e2e3d0152e206b8f11aacf27c2a2f,2025-02-27T20:15:38.733000
CVE-2024-28680,0,0,bb616bee4faaaca8abafc5c68ee983a737f77186f2373e9fa937b02412501f37,2024-11-21T09:06:46.260000
CVE-2024-28681,0,0,d052c8b2f46496beb9ba179784cc8722289cb35e4cd4f371958f4d19cfd3d908,2024-11-21T09:06:46.473000
CVE-2024-28682,0,0,eba1627157a7a3a72608d0b3ee7a5e137d680076206e467179ea2ca655b76ff0,2024-11-21T09:06:46.683000
@@ -255736,7 +255736,7 @@ CVE-2024-29738,0,0,8c7de6e64ca0b6d6c89dca0223ef5aad2d4ced944458e86ab12ff44f8d6da
CVE-2024-29739,0,0,df0346e10103b861fc131db19f20059c902c4eff1f464dc3f0be8070a3263292,2024-11-21T09:08:12.613000
CVE-2024-2974,0,0,dc530d1fe178ba3d0196a9b2c5f8fc5fea5ae66b08077bec1e54fb46703c9dc7,2025-01-08T20:06:14.587000
CVE-2024-29740,0,0,b4700812d574daa120bc21f820d9a1090255a14abc9e9b57649051371f118f81,2024-11-21T09:08:12.813000
-CVE-2024-29741,0,0,ad0166c0b9bdadba5399ed38f67d68bf92a9cd9d4585450d760bc972f88174e7,2024-11-21T09:08:13
+CVE-2024-29741,0,1,a3bedfea49f8f9aaaa2d8fcf233f28860393014231743222c09019ed9fbba17b,2025-02-27T20:15:38.403000
CVE-2024-29742,0,0,b9df7a6c13e81176309d5385a85ce7e04b5046d77b80b3b29ab68f5cb7b31339,2024-11-21T09:08:13.120000
CVE-2024-29743,0,0,6a9afac44f6143f44fda726588926ce6f7ad266693c45d776850709161052046,2024-11-21T09:08:13.297000
CVE-2024-29744,0,0,3f075efc1c2de478a44bcccd00b11149529974e1b5df3b6c2dad457a1f95f334,2024-11-21T09:08:13.410000
@@ -256254,7 +256254,7 @@ CVE-2024-30249,0,0,7739ba324f3e92dc8e2e674e85d8b0970fbdaf41806a12e4ef1b61cf68e3a
CVE-2024-3025,0,0,8d1dc1ed59f1e745375f932a0b2d66a442d2ccae1be7b19c301a65e74dcf5427,2024-11-21T09:28:42.597000
CVE-2024-30250,0,0,03328bd203376a10b81c8e55d95e3744134974aa4f39bd72aa00a6edbbd3da53,2024-11-21T09:11:32.493000
CVE-2024-30251,0,0,702ca4ceff36fdb718f97ee0639182b92e79836eb4a997b9d7bb5ace30ee4dd4,2024-11-21T09:11:32.630000
-CVE-2024-30252,0,0,43d60f0a6829a0671658f3438dba5878dce68df025a0ce50c0f00ba9c6df3d84,2024-11-21T09:11:32.780000
+CVE-2024-30252,0,1,1b2b6968ac264910e6ed1bf98690d75d62de04cc9c01e84a5284aca02880e51c,2025-02-27T20:15:38.923000
CVE-2024-30253,0,0,bc4506e5c3b7edd4c1da781f36ecd0afb5af25de6210cbbced76946549d2f93c,2024-11-21T09:11:32.927000
CVE-2024-30254,0,0,35546b7409e4119ccffeb76af2517fdc522bbad8073913d5b4579ec29c98ca9e,2024-11-21T09:11:33.107000
CVE-2024-30255,0,0,78b182f0b7f2b08d83e6ce349e002956760de0eeeb0dd012f4a2379fb98daaa1,2024-11-21T09:11:33.297000
@@ -256331,7 +256331,7 @@ CVE-2024-30327,0,0,e099b89dbd941f4949bca567b08d1e55e8e7cc20427c420e761d233d3cfc6
CVE-2024-30328,0,0,1c9395384a0940ed3b008df49a3508fc363f283e1bfc226c8776d37480edf7e2,2024-11-21T09:11:42.020000
CVE-2024-30329,0,0,8ee57fbab41f4293a3e12513ed81a887139621991de495198e165fec456838ed,2024-11-21T09:11:42.160000
CVE-2024-3033,0,0,1b8e02d84b89b7b89f55321d13194b84a08cf86778da3551a42de9338c38c8e7,2024-11-21T09:28:43.710000
-CVE-2024-30330,0,0,8eb8f7cafd63ccb5d72fd6c1dab1aee417c7669e0166ef2bc1f00015fcc0b1c2,2024-11-21T09:11:42.297000
+CVE-2024-30330,0,1,d80405a45e07f26f4597489f49a13d3f1835c29db0c5d4434c707c7ffa14da4c,2025-02-27T20:15:39.110000
CVE-2024-30331,0,0,c46a3954fa2db7fa82bb01909829239694ec25824569125cd1bdd6ea1cb40806,2024-11-21T09:11:42.450000
CVE-2024-30332,0,0,86e9c4b1f7305283e6be51bc00614ae7d892767a558e3d3e2101ccc40ca04b14,2024-11-21T09:11:42.597000
CVE-2024-30333,0,0,c97c8db7506ef18e690f6b188ca70b4242bc0cf3b5ab465c09f0416ba8016068,2024-11-21T09:11:42.743000
@@ -256797,7 +256797,7 @@ CVE-2024-30965,0,0,d35880fd6e81f76629097cb2da19773a7bb8ced66853b42b46c70ca93712c
CVE-2024-3097,0,0,1c9fe1e37b22abdae4b603dc655a85d3356b60b9c016ebac6292daf17d820cef,2024-11-21T09:28:53.670000
CVE-2024-30973,0,0,4b9b358e50352d05822b089be18105fa82470525594b4a6f4359fb3ba65b0c36,2024-11-21T09:12:38.687000
CVE-2024-30974,0,0,c7311ab8b2f055a083bd3d72d9e86423f8c619657bf03d7df281caed25c5d93f,2024-11-21T09:12:38.900000
-CVE-2024-30977,0,0,8c96e3b1800d6bc6411294e24b286c28689761737d24a559c1b0690caf005532,2024-11-21T09:12:39.107000
+CVE-2024-30977,0,1,3b931d04a5b50cadcfbd0ef03e3999e5924cfa2c8174abf36da981da2e160399,2025-02-27T20:15:39.290000
CVE-2024-30979,0,0,74ca725e154458cb21d21e58aabd33013f7c9f77805d015c87f8fc0dfe3c9bdf,2024-11-21T09:12:39.327000
CVE-2024-3098,0,0,c8c580a846a2eba3442658ac151da746cab0c185ce9595e048de2102b0afecfc,2024-11-21T09:28:53.823000
CVE-2024-30980,0,0,6df176c81fe6661c70a1e4300fc50989b0d95be8ee2ec06d8fc040751c3772cf,2024-11-21T09:12:39.540000
@@ -256815,7 +256815,7 @@ CVE-2024-30998,0,0,25ec2ab4267f10115aa3cc771729cffab1d8cff01e51fde8dd957ba54cada
CVE-2024-3100,0,0,cdfcae3d66ab799d842695f2227f5d408503e80fef0c63776bbe5bbd6058f69a,2024-09-14T11:47:14.677000
CVE-2024-31002,0,0,0b751597f2635484358fb7771a6c157a811fbace97b874ec2f8f9f5018e0c2c4,2024-11-21T09:12:41.733000
CVE-2024-31003,0,0,4a86ccb5a0fcbea3cbde566f13c34d8666fae6648b43209f1961510ead12e846,2024-11-21T09:12:41.960000
-CVE-2024-31004,0,1,d98306a9407b30d2520609036d0550f9cfe09e6bcc2cecb03b65b912241541ee,2025-02-27T17:58:20.883000
+CVE-2024-31004,0,0,d98306a9407b30d2520609036d0550f9cfe09e6bcc2cecb03b65b912241541ee,2025-02-27T17:58:20.883000
CVE-2024-31005,0,0,b2c0584cd82d16d3e12e020edb73f11d01c5ec2399112f7279b9cae23da3a38c,2024-11-21T09:12:42.247000
CVE-2024-31007,0,0,4c0a859b37e4845601b0d3eab4478f21b4a146a0f1413632b63310d7a22ba059,2024-10-23T15:12:34.673000
CVE-2024-31008,0,0,e7e94289c0d70f11986b60bcd28cf23cfc8f6abcbb4fc90eab7137198514a6d7,2024-11-21T09:12:42.713000
@@ -257741,7 +257741,7 @@ CVE-2024-3225,0,0,1702654e86d9615f0cb87e717b5ca06a0ba87dddbca38a637d31aa56e7bfc5
CVE-2024-32254,0,0,27db2cf4047461feeb9a479dba4cf663e9a27869b2fe97e4d3048977601a013e,2024-11-21T09:14:37.663000
CVE-2024-32256,0,0,e878fe31c26ddc2ef1ba0d5960e20d26b67e4ede83d59e4dfc5d31992bbd2f30,2024-12-03T16:15:21.697000
CVE-2024-32258,0,0,6307eaacd8410373f8e4971a56af08ef21a11ce548d7dc244e05c1cbd8242344,2024-11-21T09:14:38.023000
-CVE-2024-3226,0,1,706d35104c0eeb34a9e76514695701d248ce5dd5086c0f49e253b9d243c0e7c4,2025-02-27T17:58:20.883000
+CVE-2024-3226,0,0,706d35104c0eeb34a9e76514695701d248ce5dd5086c0f49e253b9d243c0e7c4,2025-02-27T17:58:20.883000
CVE-2024-32268,0,0,4220b068189651923e7c03eaebbdaa1016b5566433d5df81372417a7a35be918,2025-02-10T23:15:13.667000
CVE-2024-32269,0,0,946bbdfbb629e9015a5d3fff72eb7016b39f3bb020c4b6fcea1e2b24974b3684,2024-11-21T09:14:38.380000
CVE-2024-3227,0,0,28a05cffb436fab86b4dee105af0c7bd6e6a85e8028ebc28c7f55daea5c039c9,2024-11-21T09:29:11.463000
@@ -261357,7 +261357,7 @@ CVE-2024-36938,0,0,4d9924cd7bfb84b3633fe799c0b7fc82709fb3f85bd659837aa01f8cc505c
CVE-2024-36939,0,0,1252d2378806f57c941ac01ee8775cd36c8f32e92eb3d48d9f321c7e990e3e6d,2024-11-21T09:22:51.870000
CVE-2024-36940,0,0,0f74cfba8a07d69670dccad5b3f3987f380658e0c688c06f9d124cfda16efee9,2025-01-10T18:29:29.727000
CVE-2024-36941,0,0,0222ea69f43ad46c3fce7bf3cc89a74c5d85c25a7339eb5a186c15794aa9eae0,2025-01-15T18:37:15.553000
-CVE-2024-36942,0,0,d97ccc71569d5f8b7b55927033df54c99c1926745c1fdf04759b47e6b64b9a09,2025-02-03T15:51:09.253000
+CVE-2024-36942,0,1,6990c41ddeed02c5583595840ca0180a77872ea659da5f8a0bb089b504569ae8,2025-02-27T20:15:39.403000
CVE-2024-36943,0,0,9e8bdb62eb129ccfd7f8944661396439f413c214652e234e842dfcaa990b1f85,2024-11-21T09:22:52.417000
CVE-2024-36944,0,0,672beef3f323dca7c36ab54cbe0681caf41ff668ef1133f7e954b055ae0b9b52,2024-11-21T09:22:52.540000
CVE-2024-36945,0,0,c1a082377dd02154ad85f3fae5c585a902648a9979b6d5d6b224ea3663bc2d6a,2024-11-21T09:22:52.733000
@@ -266982,10 +266982,10 @@ CVE-2024-44039,0,0,b7d8a14283c7069f663e48b18eca1d5d9ac219742ba66b0179a0ba1a8985e
CVE-2024-4404,0,0,9b5efeaa7a431a271ce98955a661c1133eae643e8f59e37243cf043edf2fab54,2025-01-10T16:48:29.307000
CVE-2024-44040,0,0,74b42965e6e3986525fc77deeb0ef094e32ece4aff2cecb84f707822891abd80,2024-10-07T17:47:48.410000
CVE-2024-44041,0,0,40e1db2f65bd9a020f30713b0d9178a6e32ba90a0e086503a110d2a28adbf345,2024-10-07T17:47:48.410000
-CVE-2024-44042,0,0,1d7bbe5f51b27e09708cc24f3986a913e72fd98931fb78d44a1cf4aa3f2fbbd6,2024-10-07T17:47:48.410000
+CVE-2024-44042,0,1,bb3534ce2711063106982e1dce9a420a854d7d7eb6757eb988534ebba6ada5fe,2025-02-27T19:30:33.180000
CVE-2024-44043,0,0,5a54ccce540366e3100b03336264da52bbe72223a1a384e61c57b8debae86b18,2024-10-07T17:47:48.410000
CVE-2024-44044,0,0,e8bcae9c0a925c367758f0b128864c987427cff558dfaebdf800f9a18148883b,2025-02-16T23:15:08.907000
-CVE-2024-44045,0,0,e30add326efb0689032d9e1291ab1ceb0e7cee7d7cad42f2447eb76eafa4c869,2024-10-07T17:47:48.410000
+CVE-2024-44045,0,1,8fadb3a84c1b408a489bbff2c8016efebace55fa9f3ca1ebb63ae422ceeb7b67,2025-02-27T19:30:33.180000
CVE-2024-44046,0,0,8cb28132dcb52c0f855cf896fc0277479d6e2fdc4d9679affa04a96ae7375ecf,2024-10-07T17:47:48.410000
CVE-2024-44047,0,0,55ccceb367f56cca0478fcf20023ed31752b3102ce8e00f651967b31bd809ce5,2024-09-24T22:05:25.723000
CVE-2024-44048,0,0,6b8014dd8975064c6dd10c9a42f93677b98f1ce3ef8f4c594f133e75d244ccf6,2024-09-26T13:32:55.343000
@@ -268926,7 +268926,7 @@ CVE-2024-47050,0,0,0ecdbbebc96569da8fe90045f207bda8eb6f3c0a2e057e37f2da498fe1d2b
CVE-2024-47051,0,0,6504fffb1b1ff2a526046da4d8cf59bb7c31b7b525e3c742538cdccdd586caa9,2025-02-26T13:15:39.957000
CVE-2024-47053,0,0,0cab2623d4d90c181bc28f928f6ec891244940bdaaa59801bf653a0eaa0807ac,2025-02-26T13:15:40.090000
CVE-2024-47058,0,0,edde224a6d4e66b56d994d6f32d48711ac34b74b7c4338e5ce4a876e2e9cffc1,2024-09-27T15:31:30.917000
-CVE-2024-47059,0,0,a179fbcadeac2ac36464946db2605fea6e8bce1b21e66df8aaaa15d1eef57d90,2024-09-20T12:30:17.483000
+CVE-2024-47059,0,1,cce8af7becadd047e01302f00356768b3ff9b2376c0abd09c500bcb1a617ca38,2025-02-27T19:30:33.180000
CVE-2024-4706,0,0,3149e088dc20e2874012557f7a93cad12bf94c4bd0ac600fc84f4786a2c39491,2024-11-21T09:43:25.110000
CVE-2024-47060,0,0,494f551f24292d732b229fd2807625ebf7e1ba719a57e100d6197f38db195de8,2024-09-25T16:43:47.267000
CVE-2024-47061,0,0,f64d0349b66721eed4f56e73b4a8f0b9e381fe2723201d46573bd287af5cf69c,2024-09-26T13:32:55.343000
@@ -270690,7 +270690,7 @@ CVE-2024-49560,0,0,3f26500c4dded44eae4dc46589e64362e416f55913f19fef12f4ea5a50ab2
CVE-2024-49568,0,0,2424937b6c632a3bb8bbe23f1d59070173b0b27451c699774823ff5adcd561d7,2025-01-11T13:15:23.637000
CVE-2024-49569,0,0,b1379fd025e32fab88c21975ab9b6f766098726076e1ee1ddc484d172b3d093a,2025-01-11T13:15:23.840000
CVE-2024-4957,0,0,faf1bb90e1dc631958a9f6c5494539e38e22b9c3203a1f9393f289eefc9d7e39,2024-11-21T09:43:56.650000
-CVE-2024-49570,0,1,96aabf41b2e0e8c3aedb8a1b9852af2b449a88e13b6e1636bbb3438806723533,2025-02-27T18:15:27.083000
+CVE-2024-49570,0,0,96aabf41b2e0e8c3aedb8a1b9852af2b449a88e13b6e1636bbb3438806723533,2025-02-27T18:15:27.083000
CVE-2024-49571,0,0,48d41a1ed34da6a8d207508416dbadcc69c521f2274992ee3d4ce336a0c1087e,2025-01-11T13:15:24.027000
CVE-2024-49573,0,0,bd822bfcb04a1a23a0356060b4b02e8952dd69548a8ed6c8619ad13c8392c259,2025-01-11T13:15:24.223000
CVE-2024-49574,0,0,285edf65c7736387bb1f5e69a3d9da68a65cb104e57ac1234838e33c6baad7dd,2024-11-20T16:32:37.770000
@@ -273532,11 +273532,12 @@ CVE-2024-53365,0,0,a93e9b8a9b0b556658347d02609f6ad1ef6238df632d2e5010e1700b801de
CVE-2024-5337,0,0,833c775533ef7ae5a7edcd24b7882543f8822839060a2f050988cae0593a7c5b,2024-11-21T09:47:26.857000
CVE-2024-53375,0,0,03acfc3ce1465046824ce662fbf44dee8291f967ecd696fbbf82e7a2b14619b6,2024-12-17T21:15:08.073000
CVE-2024-53376,0,0,8911dbfc8997baa2a57cf32f34b4dcc9a56903a67bd0c4ffc9a41950a9065ad0,2024-12-17T20:15:22.380000
-CVE-2024-53379,0,0,a8fbe197952f6a68093de9265430eb32359fe1201562896010368e976d222777,2025-01-23T23:15:07.993000
+CVE-2024-53379,0,1,2b6df428322956cd20e5c553031d5487355c33ab4cabbe810e5c3a60725bbc7b,2025-02-27T19:15:48.927000
CVE-2024-5338,0,0,abd3cd0960193de57487be3582f664d37ab06a1518c59aace36e92f8c263b67a,2024-11-21T09:47:26.997000
CVE-2024-5339,0,0,710abf6b65aa86d6904f8abe1101ad889bace87733c06f79ec2fe20822e1db4d,2024-11-21T09:47:27.133000
CVE-2024-5340,0,0,2c2fba286498156a3309f1d9db161c67194b50596b7c53b6a9c7d8df9b89917d,2024-11-21T09:47:27.263000
CVE-2024-53407,0,0,028a3e4d14bfc90eea9cc0c6159117f08c823fe19cf4dd25d6c1d6ae5f9691c6,2025-01-31T21:15:10.213000
+CVE-2024-53408,1,1,fad2504477aa5345271d8863f19e55b9d1c9b4f8952b0c3b4bfd093802e01e07,2025-02-27T20:16:01.790000
CVE-2024-5341,0,0,65ff8689965c5e29ef124f69d82afd0c059edc6db5694aac65d8224f8b995833,2025-01-29T18:09:48.960000
CVE-2024-5342,0,0,c19ccffd3ff364daed28ff3ce4f3e63c62c97b909f79a312d9891c60f97a9cce,2024-11-21T09:47:27.517000
CVE-2024-53425,0,0,dba41ac0d03c322e076798942c48ad94ab227d8220eb1e3a3534e4bdae7c6815,2024-11-26T18:15:20.090000
@@ -273874,6 +273875,7 @@ CVE-2024-53940,0,0,04215bb77d44b273e9849b212da1715e4a88663d0a04d658e8b426292d6b2
CVE-2024-53941,0,0,958fbab1dcd158d91125ecb71056e34e403404760a1ce78a6e1b2e3ede2a0630,2024-12-03T19:15:13.113000
CVE-2024-53942,0,0,a82102ce95ecba9d91a325449993277e8666efd3fba33597504408ca5c2b2e17,2025-02-03T18:15:36.633000
CVE-2024-53943,0,0,437d28c72b812c4593516003fc2aba4b613f671a694938fbad086ef025289004,2025-02-05T19:15:44.257000
+CVE-2024-53944,1,1,654de1ab7038b0be68acea0a61a6baf4e50998aff9395f8ec3956737ef669cf2,2025-02-27T20:16:01.887000
CVE-2024-53947,0,0,b42db7838a4330c67a4fe62e48645e7bfb198c9a3c642c30c8c0bf4ba786d6fa,2024-12-09T14:15:12.267000
CVE-2024-53948,0,0,b3d726d03ac5bb44151016e2190cf661b3901a0bee5c01681d65f576dc3ec03d,2025-02-11T16:27:31.023000
CVE-2024-53949,0,0,e6b9e69d49b032ccd0101f81928ad74ff4792c6996f261665810f89cba506d0e,2025-02-12T10:15:13.790000
@@ -274320,7 +274322,7 @@ CVE-2024-54454,0,0,d67e1bf29a3aaa483b825ac163d62022e2785b5de9b64863f3bc27235cd67
CVE-2024-54455,0,0,20565313a23365c4c17140fe19943535439cfbd982b6e19cd3463b943b5d9db9,2025-01-11T13:15:26.970000
CVE-2024-54456,0,0,28dd9591dea6ab614e4970f03407badae263baf62853d971ba3cb4d7ede26fae,2025-02-27T03:15:10.667000
CVE-2024-54457,0,0,da0353a7ec7d859fd477580e7c54e31a24aeea86ab2c2ac2e00b7a1eda59c2cf,2024-12-18T07:15:08.377000
-CVE-2024-54458,0,1,b8c27b547df4bbc9396a40929c4786c7ab5c0cbf310c6333fed6727ada313852,2025-02-27T18:15:27.273000
+CVE-2024-54458,0,0,b8c27b547df4bbc9396a40929c4786c7ab5c0cbf310c6333fed6727ada313852,2025-02-27T18:15:27.273000
CVE-2024-54460,0,0,46a2824e2a284b445162d596321895979fee49d319c455c9a3391c11ac25744d,2025-01-16T15:15:42.083000
CVE-2024-54461,0,0,a18c4495fe08936148cc1903452fcd50e5f604d768b2f0428be9a05087d45a0b,2025-01-29T12:15:28.437000
CVE-2024-54462,0,0,2f90ca1ad44c149203a354a165acc297b755622fe323a9b60f945492974c33e2,2025-01-29T12:15:28.627000
@@ -274520,6 +274522,7 @@ CVE-2024-5494,0,0,01220fe18988d81f50a7497aa6ab19647b6ffe5fd178defdb09fee026bb9cf
CVE-2024-5495,0,0,5042268a950e30bd3019e8943c12e21fd198069753506c20c0160553a125c76e,2024-12-26T16:42:57.383000
CVE-2024-54951,0,0,8b2bcbe23ae754cb335a19524b9fb140fa909ba5063a6b13cf36fb5639e89ebb,2025-02-14T16:15:34.060000
CVE-2024-54954,0,0,c5f7bba0f482724c8baeb34ff731ef8127c621f5f601d09231830cf72a39e47f,2025-02-26T19:15:22.440000
+CVE-2024-54957,1,1,aad85f2b85bf507c08451cc1991a7a3bb3b1909ba8b78b5df92f773ef0a1525a,2025-02-27T20:16:01.980000
CVE-2024-54958,0,0,69980aeea30a2a881a4d3d60af27dc56a66e90cd80d98f68c95b14c20a9676de,2025-02-21T22:15:12.440000
CVE-2024-54959,0,0,9f0a686e6ecddb708d340473cce33ce83c57a259a6f56d0e5117df6a2fd44baa,2025-02-21T22:15:12.593000
CVE-2024-5496,0,0,9136fd74dd5c910c46896c769e58528b87587fcd9bbfc0ee678598fdc16fe0a5,2024-12-26T16:43:17.607000
@@ -276113,13 +276116,13 @@ CVE-2024-57975,0,0,cb69d9a311887f4b534587384c990ff308b1380cbfc2d7252bdcecd7dbc0f
CVE-2024-57976,0,0,7f09566c0feeca43e88331a7b08960623ddee4f005b52f57b309033e09c409f6,2025-02-27T02:15:10.790000
CVE-2024-57977,0,0,95d6e3cfdf7d059ffc8f36aea59ffac8f831718016b7d9622c1ff999e22b555d,2025-02-27T13:15:11.053000
CVE-2024-57978,0,0,e8ec9a121960a685f9c435a7ce1a5bc00fc9f8a0953711b3760133a98ea218ac,2025-02-27T02:15:10.990000
-CVE-2024-57979,0,0,022cf17af330e8a9f7ce941e4c03648881e6a5a964e2654b247615aeae7964b8,2025-02-27T02:15:11.087000
+CVE-2024-57979,0,1,ec364853eeaf88bcd505e49b02bbac5b08950e2f002b1ede31d3d12837f3b28a,2025-02-27T19:15:49.077000
CVE-2024-5798,0,0,1cf6b5fddcb53bc6e432a6a3428f56651407d96c3d029c184944ae69fb8dd23b,2024-11-21T09:48:21.013000
CVE-2024-57980,0,0,89bfd9a25c4e9369350a4449c15f56c4d731c340746fe511daefbde4562cc736,2025-02-27T02:15:11.190000
CVE-2024-57981,0,0,c7b9798745dab28cf705a3d517fab8fa7ef55021d1e9921a8c24bc879e7d3409,2025-02-27T02:15:11.293000
CVE-2024-57982,0,0,2e14c424f43f3ef2e56bbd7c634847aebbc48a76817fb36f29f428a529741e04,2025-02-27T02:15:11.397000
CVE-2024-57983,0,0,10bc3b141784d98884249c034f6788adfb8039accce5c7b05571610ccaa93db2,2025-02-27T02:15:11.503000
-CVE-2024-57984,0,1,b51843389055f5f899ce07379732c5bea8ebe0a7137d6cfbc4c9dfedf3599ec8,2025-02-27T18:15:27.460000
+CVE-2024-57984,0,0,b51843389055f5f899ce07379732c5bea8ebe0a7137d6cfbc4c9dfedf3599ec8,2025-02-27T18:15:27.460000
CVE-2024-57985,0,0,4aec490eb67ded35d6be2f91681087c27ad005d40c184e16475fdf18b5f3187e,2025-02-27T02:15:11.703000
CVE-2024-57986,0,0,3a9db4363951f761b5787db5bb2ba75d22743103ba97176a9748f6a0ec3c52f3,2025-02-27T02:15:12.597000
CVE-2024-57987,0,0,7e3a43f71100acdb8df43f94b6ed6efa305c6d10cee9361a42e6abdb9ad4d818,2025-02-27T02:15:12.700000
@@ -276161,8 +276164,11 @@ CVE-2024-58019,0,0,904f7e6de053926a7a7857ae1d944b0d99c93c5b21a2e4b8c6e5f5c7d2783
CVE-2024-5802,0,0,19fff604014c9cef9e0f8bc6a62b84f7523f1797653eafe6700c36b3d03bd7a8,2024-11-21T09:48:21.447000
CVE-2024-58020,0,0,4a110a80daea948a17db5525c61cf06f99a7fb31b4bb1b32bbb55e99b10c4eff,2025-02-27T03:15:12.997000
CVE-2024-58021,0,0,db91dc296face0f431063f73829fc75c2d514198b5509c869ecf3fd68c1b0266,2025-02-27T03:15:13.110000
+CVE-2024-58022,1,1,c59187fdd2099f2dec586001ea4c6972a210587752ee11248ba233a172fffa01,2025-02-27T20:16:02.073000
CVE-2024-5803,0,0,9f82593b4c57457c96daef99978d68eaca19c8db6ce80dfb437501b3b95974d3,2024-10-04T13:50:43.727000
+CVE-2024-58034,1,1,cc4586e256ea3a904aa545c9e73a00467700457983ff55b15386cc6fc02e817f,2025-02-27T20:16:02.160000
CVE-2024-5804,0,0,2f00fd3e9947e9e26596c3d44370745abf63c8732a08c44c5ab0acfd9a8ea957,2024-11-21T09:48:21.677000
+CVE-2024-58042,1,1,e35446aa13eaa7d3266b93c7dc119c4bb6b62f917daca1dc874bd9a8c676557a,2025-02-27T20:16:02.257000
CVE-2024-5805,0,0,fce2cd9169116102e5375089f5975fe2795253d6c4b763ab35cc7d32ac26b7a6,2024-11-21T09:48:21.803000
CVE-2024-5806,0,0,5ac9637d8c764ba881b38672e3b3265f75ae0c44c191480b6554928fc9eb1283,2025-01-16T16:57:19.660000
CVE-2024-5807,0,0,bcd7f1773756c308216942ed74fe8b63dad936ebebf2c4e22c08a44714f2e7fd,2024-11-21T09:48:22.057000
@@ -278661,7 +278667,7 @@ CVE-2024-8622,0,0,c0236be19c6f76388397240005bc8328efcd3afeb9b22de958aad09c2038c5
CVE-2024-8623,0,0,56ef81b3b9760b3060b925939b7f80127617fa135795d5260a98ea0e77ac317d,2024-09-26T16:46:28.590000
CVE-2024-8624,0,0,522cf4c9e0d095c65b39c7d99282ef53065d33993728082b5639660998b19008,2024-09-26T16:45:40.470000
CVE-2024-8625,0,0,1f961d9f44de1933e5f0790b78bd4aa6a0ce41f79feaab7dc1128a72edd8300e,2024-10-24T13:56:29.230000
-CVE-2024-8626,0,0,2c8a2d5aee3f01f0fef0e5eaadb2e85a1d283c16076dc94c8cf894e4343029ae,2024-10-10T12:56:30.817000
+CVE-2024-8626,0,1,d981285e91d113542d9d061a8ad73a2bdd93c62905e9807281385513c6c176fd,2025-02-27T18:47:11.020000
CVE-2024-8627,0,0,27266881d63aaccae1399dc0ad1d0628066993bee61c3c604c55c6aa4f5b389f,2024-11-06T23:06:39.400000
CVE-2024-8628,0,0,b68a3e50b7aa7f345a4a8d9267235e89f90c245dc8aedbab47c4bc06341f36d2,2024-09-26T16:42:16.700000
CVE-2024-8629,0,0,e2a922a358bf246c8de0dd6bfffe026aac95a455217a4a0cb80f1b479dc48aaa,2024-10-10T12:56:30.817000
@@ -279220,7 +279226,7 @@ CVE-2024-9281,0,0,da8a0ab96f117a518a860154a2b10e51a3bf826eb3beadfd472bea78c9193a
CVE-2024-9282,0,0,0f6658865bdfecb9534db957c91de6eea6f34868f85b33242348a99ddfb3e538,2024-10-04T18:33:38.293000
CVE-2024-9283,0,0,e3a6ced02e3e6102d5895c64217f05f9dcefd62a5e0c1b52a27a37d3b3deca81,2024-09-30T12:45:57.823000
CVE-2024-9284,0,0,e747cbb82ef430c65e12719c88c63c2fbce54e52eb20c21371241717d7cc4e0f,2024-09-30T12:45:57.823000
-CVE-2024-9285,1,1,62f9f055980a2e6dc9b70ac782069b62d0d65b4ecc79cdd438ce768b905bf8e1,2025-02-27T17:15:15.953000
+CVE-2024-9285,0,0,62f9f055980a2e6dc9b70ac782069b62d0d65b4ecc79cdd438ce768b905bf8e1,2025-02-27T17:15:15.953000
CVE-2024-9286,0,0,5c87b07f904b24f28322b109601842556e84152397134ac82da299aaabaf274a,2024-11-21T17:15:27.713000
CVE-2024-9287,0,0,790dfd8bbd7430a054c58d9335ddc630ff6c3f8f84cf731bdb62503212dbb72e,2025-02-10T18:47:16.547000
CVE-2024-9289,0,0,82efcd622bd05af8234fb7f9750f1266ba9c6595f5976c11981038e615a0ed09,2024-10-07T18:25:21.380000
@@ -279326,7 +279332,7 @@ CVE-2024-9411,0,0,e50aa5df9882c6abf161705df00e21c86ccc46f5aab40d94fb697ab05189f8
CVE-2024-9412,0,0,9526c334819a7b75c7714247446625cfcb488e4872ebe39a906d083584d99dc8,2024-10-10T12:51:56.987000
CVE-2024-9413,0,0,a06de6835130fe994a1b9f10a16e4d390bb61a1bb02ceb9b43d0f4e1eeae3597,2024-11-27T16:15:15.180000
CVE-2024-9414,0,0,daa11a618576f3dd1bc2a87a2671aa82c6ce206bc2d923313e6d592311bc638a,2024-10-18T12:52:33.507000
-CVE-2024-9417,0,0,216f9ce7a9e770763e40db955a327ba67f06d2e630f73f66eb3add63da2d3dc5,2024-10-07T17:48:28.117000
+CVE-2024-9417,0,1,f1ad593c893f867a6d176bb6430fe849da268206280e48ce85bc230b1eac2b90,2025-02-27T19:30:33.180000
CVE-2024-9419,0,0,75c2ffcece6c8d9641e61b7d83db859a8f0c6a3be035496f4eedc8e263459f13,2024-11-01T12:57:03.417000
CVE-2024-9420,0,0,0e84e878b3a1f98289c88b1fb777d3526a495ded70c4b0ad1ee8e42f7524d058,2025-01-17T20:29:36.007000
CVE-2024-9421,0,0,037ff18a423af7d430246a25c13267312b520381fc2b22b38075ef45225d8825,2024-10-10T20:59:01.600000
@@ -279509,7 +279515,7 @@ CVE-2024-9630,0,0,c5bfebdfc374c6829acf4f216485f47c7193dffe76ae06b5710261faf3a923
CVE-2024-9631,0,0,8b9648c02ba078f0734a6594b2ae5a0daf10ff539344382557488d0ca821b44f,2025-02-05T20:15:45.210000
CVE-2024-9632,0,0,239a4c189d3eed560921482fe12c18bb19732b61a1100ff2b6e56460beb86ea5,2024-11-21T19:15:14.210000
CVE-2024-9633,0,0,464719aabf82d4c51da737aba0ef58dd3d7e243c61253713abe304606828160b,2024-12-12T21:43:44.480000
-CVE-2024-9634,0,1,5a1303eaa7f93b6eb08e5bf2c5ca20cd76106538f564ad02f1744a438904d495,2025-02-27T18:47:11.020000
+CVE-2024-9634,0,0,5a1303eaa7f93b6eb08e5bf2c5ca20cd76106538f564ad02f1744a438904d495,2025-02-27T18:47:11.020000
CVE-2024-9635,0,0,9f77fd7ccc96fa6d4c00f44465f9f4a309bfc7a2ae1c26c3627ef0449f3c9e02,2024-11-23T07:15:05.027000
CVE-2024-9636,0,0,0b62f247a55adcf843a0ddc11a4709285f570b0022910e18b3e03743a1ef61f4,2025-01-15T10:15:08.607000
CVE-2024-9637,0,0,0f4d16db68000f66da50bae84c41a0f228004e7436fcad95d0969905f72e932a,2024-10-28T13:58:09.230000
@@ -280238,6 +280244,7 @@ CVE-2025-0754,0,0,01e22cbc27c23b2a20fc22b4b38925f42f70aba0e3cf26d239fd3f71faae49
CVE-2025-0759,0,0,f572811706ba51744ee45129f48d6948c8d40f854e28ffb23f9648591608afb2,2025-02-27T15:15:40.603000
CVE-2025-0760,0,0,41c51c3186d7c1d82dcf6c1e725fcfd59fdc585d73de4a715eb553b80d5dac62,2025-02-26T00:15:10.890000
CVE-2025-0762,0,0,e4f54e0a8112ca4bbd93833150136d658b70b741ccb351b92cec93e89ce75210,2025-01-29T15:15:17.687000
+CVE-2025-0767,1,1,18b19f88a460710b0a272571f92b11e64f98033d887b75623068759f9e10d0cf,2025-02-27T19:15:49.350000
CVE-2025-0781,0,0,b187217e5320659130c2f954520571f906b51edbf3680129182cf06170507db1,2025-01-29T22:15:30.187000
CVE-2025-0783,0,0,8924456cd6700604f4e019fec6c3db3aae4fc1d29681bfa897a8d15c04913bcb,2025-01-28T19:15:14.410000
CVE-2025-0784,0,0,7bf35a66d1e5bba1c28f1ce408a8faeeb60c83b8f697f3920a03b5139a10a1a9,2025-01-28T20:15:56.230000
@@ -280688,9 +280695,9 @@ CVE-2025-1728,0,0,126b29abd5a8b7142eab21be075a4425d5b9e0d4bb1eedd2c9477807954e21
CVE-2025-1738,0,0,5e1b2b2b1d4db3558f89d0488b29d771876500128261550d8395e9a1552dcb39,2025-02-27T13:15:11.720000
CVE-2025-1739,0,0,474bd41a40b4d7e6fdfff026df5b08f6be7f300b56e56bcc0fdd145be437283a,2025-02-27T13:15:11.883000
CVE-2025-1741,0,0,344f7bc016a7178d5c4314a2e4d09672c42edf31aa2ee8b574916c55f2eebd7d,2025-02-27T16:15:38.930000
-CVE-2025-1742,1,1,739398478edc9ddece71d3399efb7eaab9bd1f42fe6e327305583b23ec5e53bd,2025-02-27T17:15:16.460000
-CVE-2025-1743,1,1,f420185c057195d1e0f14c6168b6487602fc3aa63e73bf5c979d7d5fa960e55c,2025-02-27T18:15:27.650000
-CVE-2025-1745,1,1,9e47846683e7157da502ac5a77516ebab38eebca4e7114c00a2b8bf268b0ef4b,2025-02-27T18:15:27.923000
+CVE-2025-1742,0,0,739398478edc9ddece71d3399efb7eaab9bd1f42fe6e327305583b23ec5e53bd,2025-02-27T17:15:16.460000
+CVE-2025-1743,0,0,f420185c057195d1e0f14c6168b6487602fc3aa63e73bf5c979d7d5fa960e55c,2025-02-27T18:15:27.650000
+CVE-2025-1745,0,0,9e47846683e7157da502ac5a77516ebab38eebca4e7114c00a2b8bf268b0ef4b,2025-02-27T18:15:27.923000
CVE-2025-1751,0,0,e01d857b710fac9b7b6217b59ced116e365117c6a164f06207b3b6874d6bb32a,2025-02-27T12:15:35.030000
CVE-2025-1755,0,0,022c1cdfb96f9a1d1782ea7a255dc456cf2cd5b57b21fa0b4b69f69925763fae,2025-02-27T16:15:39.137000
CVE-2025-1756,0,0,20464066b464a87a383feb7ebdf7bcca2a5e74a3cb642d459cada04b2b771e8c,2025-02-27T16:15:39.287000
@@ -281253,24 +281260,24 @@ CVE-2025-21710,0,0,caac5a8cd4f59a38798bb65050c056c6ac14dc33ba2554c9f9132c1822475
CVE-2025-21711,0,0,1ad137bce1c83de2777c91aff300be1d715180746549ec95097915a0e6f83f97,2025-02-27T02:15:14.760000
CVE-2025-21712,0,0,0d2ee91f96988cef698a87645cfd8480b918f5263551051bca1f5bac6a7c256e,2025-02-27T13:15:12.043000
CVE-2025-21713,0,0,c0471bfe099bcdf2eb9fbfdd85133612e7add0d99f327db2a3131e92e92f3a86,2025-02-27T02:15:14.960000
-CVE-2025-21714,0,0,0443c9d2a524f4163004ed6af8df0ace54b54c7c2169bb90bedac2c54123834a,2025-02-27T02:15:15.050000
-CVE-2025-21715,0,1,47514ac9f06cb4c40bc5559f845eeddf8c1c89f63d1510e48724de1a12970e5f,2025-02-27T18:15:28.153000
+CVE-2025-21714,0,1,308c5b3c6f4ccd745dd8d04e72d820dab298861b11c84d9724f0167626767f7f,2025-02-27T19:15:49.637000
+CVE-2025-21715,0,0,47514ac9f06cb4c40bc5559f845eeddf8c1c89f63d1510e48724de1a12970e5f,2025-02-27T18:15:28.153000
CVE-2025-21716,0,0,9d695cb97deae26f96dea1b483a17bd9606280eb538b110a06de98a3a595d664,2025-02-27T02:15:15.273000
CVE-2025-21717,0,0,7ca6cd69efbb56fd36ed628b74ce2e13274561c37d021271d3bfd71e8ee64ffb,2025-02-27T02:15:15.373000
CVE-2025-21718,0,0,5fb025932012588e486a67bbb8003b6c391d3e39000a93f80ecbca817adbd3c0,2025-02-27T02:15:15.473000
CVE-2025-21719,0,0,157d53c5a8fa7b32509ec25adac9f4941a4f315dbe964473d128ebd5d2106061,2025-02-27T02:15:15.580000
CVE-2025-21720,0,0,c2a7c6189229fd84b828b80d035a48cf5be9b44c4fdaaa3cb13d86df8037388f,2025-02-27T02:15:15.683000
CVE-2025-21721,0,0,0f9bd98b6879198ba8cb006a744eda8143b70b9014761347ae9f9283e95be19a,2025-02-27T13:15:12.150000
-CVE-2025-21722,0,0,4ff28cbb7db6f566613f999667bae8e043c8ef362dbc89d551947bea584f4f92,2025-02-27T02:15:15.883000
+CVE-2025-21722,0,1,afa91b278ac195f08acdcf5b2fc50040fa471425a6d7ce26835602ea15b3cc30,2025-02-27T19:15:49.780000
CVE-2025-21723,0,0,dae0449f384656e24d333a5692bdb0c67d65760a84aa08200fd65093c57cece1,2025-02-27T02:15:15.993000
CVE-2025-21724,0,0,87af61e9bb904173709cf188d0701c3b5e1fc2fa500e06d42307eb73dd3567c4,2025-02-27T02:15:16.113000
CVE-2025-21725,0,0,aae1864f5be60c901a7f7d2bc22c2f019bb064536a9e56b914fa827f03e149bd,2025-02-27T02:15:16.220000
-CVE-2025-21726,0,1,d225d4d7591b085d0df86c29c463154baabd6cc113af7dc04eba205c3daa83e2,2025-02-27T18:15:28.350000
-CVE-2025-21727,0,1,3c3ac67407988db52d76f6f2cf3942928e954cc389919130c436ba870224d628,2025-02-27T18:15:28.547000
+CVE-2025-21726,0,0,d225d4d7591b085d0df86c29c463154baabd6cc113af7dc04eba205c3daa83e2,2025-02-27T18:15:28.350000
+CVE-2025-21727,0,0,3c3ac67407988db52d76f6f2cf3942928e954cc389919130c436ba870224d628,2025-02-27T18:15:28.547000
CVE-2025-21728,0,0,1da8388633c1d6e4ff31a488f8976f3bd0c289e0e8b6558f7e896f3d2f296913,2025-02-27T02:15:16.530000
-CVE-2025-21729,0,0,15271fcf2780e48fa4335cd669681068060c3cab565250e43e1ec0da75e25990,2025-02-27T02:15:16.637000
+CVE-2025-21729,0,1,a3aa719741ce894d70a89991bef338e5b66177dced362fca55cc6a35ae27f480,2025-02-27T19:15:49.920000
CVE-2025-21730,0,0,5992631d1f378725d3194b05000263ee4d8ee1acbc0c181e9f0cdc98f263b07c,2025-02-27T02:15:16.733000
-CVE-2025-21731,0,1,463010fe1eb003136c17079fe1b9e8d8df5dc900c7e011c74fc639e9d080ea2e,2025-02-27T18:15:28.727000
+CVE-2025-21731,0,0,463010fe1eb003136c17079fe1b9e8d8df5dc900c7e011c74fc639e9d080ea2e,2025-02-27T18:15:28.727000
CVE-2025-21732,0,0,6dcd6bd9bfefa340e9cba5991b851ac5f328d81b5e5d7dbae57af4ec34d1a9a4,2025-02-27T03:15:13.820000
CVE-2025-21733,0,0,8ed0d54b34f8a3602de8d6eb2336e24416c84513634f3455543ee5fbc64f822d,2025-02-27T03:15:13.923000
CVE-2025-21734,0,0,48ee60a79ac18d73e2e9a39f6ecee6b3c36e0f82b224a8177acf8c7eeeb90b78,2025-02-27T03:15:14.030000
@@ -281278,7 +281285,7 @@ CVE-2025-21735,0,0,8992d2ee08af6de91513a5707b684275b3dd935f25284d100c64c9dd89d53
CVE-2025-21736,0,0,93956cc846e95f47c14d6218d4851de997b7b0c8df949cea2cf32d735d479f55,2025-02-27T03:15:14.230000
CVE-2025-21737,0,0,c596c94e0cef54faf6fd7d3ebadf75ef6818d7455874f0c6a5132d57b0f7bd01,2025-02-27T03:15:14.327000
CVE-2025-21738,0,0,9dbfc481ed055656bdca0ab52ba4cae87e8b2c9da89042a2552623f1a61977b4,2025-02-27T03:15:14.427000
-CVE-2025-21739,0,0,ea45bb6167636519ff185da6b8c047f095b4bacbdf87d270e6e1bf485567f231,2025-02-27T03:15:14.530000
+CVE-2025-21739,0,1,fe5868dccad3c28f2517bbac5952a23c663a34b6b5331989b44f7c0c789331ed,2025-02-27T19:15:50.067000
CVE-2025-21740,0,0,bc64fb406f292ac6b189fad1761465403d12972b8ed6fb681b752717e4753813,2025-02-27T03:15:14.630000
CVE-2025-21741,0,0,629c7cbcbd6f85b9ee2a4c7bf55b82d7ea60c63601fc12c63869f1e280a20745,2025-02-27T03:15:14.730000
CVE-2025-21742,0,0,51c376b8442050e3ecce4cd435613cc2fa3091d1d17189e7df759dc221b5a6de,2025-02-27T03:15:14.830000
@@ -281290,20 +281297,20 @@ CVE-2025-21747,0,0,b4c7b8e9bbe08c3621e3d19d7432493cfeaae5b0fc274069a49e2619d118b
CVE-2025-21748,0,0,3c89dfc075db5c3cfdcdd002206c2f3c37c4cb82a3a4b4823a2372ec53398649,2025-02-27T03:15:15.440000
CVE-2025-21749,0,0,a7a8fa1c39a893df0dbcfcec02a053688ff8871d74d4e9c34c4774d7189b8c61,2025-02-27T03:15:15.543000
CVE-2025-21750,0,0,4cf8ca959c174b12cd52a6ff02ecc17bc8dec4e236cf714a8c19d31b325047c1,2025-02-27T03:15:15.647000
-CVE-2025-21751,0,0,5afe9d8caab0abababa4d1c9d5355075fc9d247d0ef686921d41baf954bec76a,2025-02-27T03:15:15.760000
+CVE-2025-21751,0,1,cc6ddd9710306d6e406cc6e623607915bf873d32c96711a24c46a99767c44692,2025-02-27T19:15:50.220000
CVE-2025-21752,0,0,6530d50c3281b73cb46447eb8d41cd293c5d945b6bff17d84d65e6b1472c9793,2025-02-27T03:15:15.853000
-CVE-2025-21753,0,0,29b12a1983ac3745f76a130756507ca8859ab50f2463f5dbf6c088e576ce480e,2025-02-27T03:15:15.950000
+CVE-2025-21753,0,1,79d437a2c189083cc36e7cfa532d5f9f7e37d84f4940760c623e1ec6fd7b4e74,2025-02-27T19:15:50.360000
CVE-2025-21754,0,0,1a8b7112bb5b3b6fd0926576bf3c4ee21bc88ec8d673e4bd95aa7a05addc423e,2025-02-27T03:15:16.050000
CVE-2025-21755,0,0,409a0cbcf238c1c3ea6643dea30d72c2db000f676aee71bfcf910b93a011dfdc,2025-02-27T03:15:16.150000
-CVE-2025-21756,0,0,53b4c7a5eb9f6dd16c6e387d0ceef610bef1a9d91b29e929487dc2a9284c6498,2025-02-27T03:15:16.250000
+CVE-2025-21756,0,1,83bffc3f5036f00d925f4604196fa3d2728cdbb9c8ed2735e14412a7e9bd2e28,2025-02-27T19:15:50.513000
CVE-2025-21757,0,0,38e86c3caa030988c0231a12bf7643d7816857332d199b87d5f593aaf5156bce,2025-02-27T03:15:16.353000
CVE-2025-21758,0,0,7ac672abae0649b7ee445870615f924bfd19c9c113b2d802b6c89e708349141c,2025-02-27T03:15:16.450000
-CVE-2025-21759,0,1,5b2432b41b9bcdf579156c2221c88dc8dcf09e962180de906fc384eb5f933d03,2025-02-27T18:15:28.927000
-CVE-2025-21760,0,1,d4e8082834f3d4a3f48a9d756f23c8650a31e249bf3ba52421331735f80b1974,2025-02-27T18:15:29.127000
-CVE-2025-21761,0,1,14e7d739dd520b3d67fe2d4bca4ad8c48c34315516eff46576fa2f64d01acd60,2025-02-27T18:15:29.327000
-CVE-2025-21762,0,1,ab27c40879c5cad97523af06dd0be19ff4d5f72f1caed772b6215dedc9de17d1,2025-02-27T18:15:29.503000
-CVE-2025-21763,0,1,96ecc0e40662857318a00b3abb0c2c9d4ca642aabdcb3315bb9d291f85aa7ba7,2025-02-27T18:15:29.673000
-CVE-2025-21764,0,1,3bf4a9e3d03706ef5c82105701c01750296fec64a27d5dab244b9d06431b8824,2025-02-27T18:15:29.903000
+CVE-2025-21759,0,0,5b2432b41b9bcdf579156c2221c88dc8dcf09e962180de906fc384eb5f933d03,2025-02-27T18:15:28.927000
+CVE-2025-21760,0,0,d4e8082834f3d4a3f48a9d756f23c8650a31e249bf3ba52421331735f80b1974,2025-02-27T18:15:29.127000
+CVE-2025-21761,0,0,14e7d739dd520b3d67fe2d4bca4ad8c48c34315516eff46576fa2f64d01acd60,2025-02-27T18:15:29.327000
+CVE-2025-21762,0,0,ab27c40879c5cad97523af06dd0be19ff4d5f72f1caed772b6215dedc9de17d1,2025-02-27T18:15:29.503000
+CVE-2025-21763,0,0,96ecc0e40662857318a00b3abb0c2c9d4ca642aabdcb3315bb9d291f85aa7ba7,2025-02-27T18:15:29.673000
+CVE-2025-21764,0,0,3bf4a9e3d03706ef5c82105701c01750296fec64a27d5dab244b9d06431b8824,2025-02-27T18:15:29.903000
CVE-2025-21765,0,0,84b514415b470ade0ac2ac2cf96329afd183e8547ad9084584dcc30336bb1e05,2025-02-27T03:15:17.173000
CVE-2025-21766,0,0,51d0c18c995c25a898c111f5fc9f288f82964675b2a236afa313542efb05e7df,2025-02-27T03:15:17.273000
CVE-2025-21767,0,0,5829e76bd69ea8d88fb4093af1e8a32fe79ae2d05e4dc4f3e61a6718f572504e,2025-02-27T03:15:17.383000
@@ -281325,18 +281332,45 @@ CVE-2025-21782,0,0,afde209e3b6d07b40a6f602e22e0618e943b87c35f7672b8ea9b5e80c13be
CVE-2025-21783,0,0,c2e84128aecc9231e1e01efa3fbb42716de07cc4ba861abcd948cbd45d4ef5d2,2025-02-27T03:15:19.150000
CVE-2025-21784,0,0,ddb3534249589ded30f2d3dd4794cbc7aa7f4571853ac9bec3787267d12dcb91,2025-02-27T03:15:19.247000
CVE-2025-21785,0,0,2ce172bae5986be8c51dcd93d766a0b84101dbea5fb329c6cedc99c9ec0a2793,2025-02-27T03:15:19.350000
-CVE-2025-21786,0,0,17aeb849e3abe3744007b606fe811b05bd5f034c58fe37713a9e1ca3dffabc6f,2025-02-27T03:15:19.450000
+CVE-2025-21786,0,1,573ec32bcf6643cf8ca3133f6a767aa73bb24aecac6cc7a8e873f04763039461,2025-02-27T19:15:50.660000
CVE-2025-21787,0,0,4b0f5665e4061ae1813cc5be8bedea1e929a49ca585be9c89665348d0010f7d8,2025-02-27T03:15:19.553000
CVE-2025-21788,0,0,e83634564fe764318d8301bd02b72bec6115392300efccbc618c7969cf8752b1,2025-02-27T03:15:19.663000
CVE-2025-21789,0,0,8984c1c7e35774969c10262cd58ba7b60b21ea235fc528225fd992da17139f95,2025-02-27T03:15:19.763000
CVE-2025-21790,0,0,510c000393047837010aedd86501648d1ed04a9ff80380f472de2ee8f205d2d3,2025-02-27T03:15:19.870000
-CVE-2025-21791,0,1,ac54441bf5ad86ab764d0277e85632a6d097a78ab733a7eb052e6c2acd173fa6,2025-02-27T18:15:30.053000
+CVE-2025-21791,0,0,ac54441bf5ad86ab764d0277e85632a6d097a78ab733a7eb052e6c2acd173fa6,2025-02-27T18:15:30.053000
CVE-2025-21792,0,0,d7d67d6a4ab826bfac90bf76e6d97dbaccdc4f0d6081f0b21f695f464875df43,2025-02-27T03:15:20.080000
CVE-2025-21793,0,0,453d78f6521e190278dbaba81bbaa8323401129fea331a0de5aaad11ddb4d45f,2025-02-27T03:15:20.190000
CVE-2025-21794,0,0,9832c619a82f18d28f0a7e86bf0adac27a16a7b0cc9157ba0d29a36711cac0c0,2025-02-27T03:15:20.293000
CVE-2025-21795,0,0,39bd1fd575ef715615bcf04cfa21fd5bc633989225e9cc19b52ab20b759ec599,2025-02-27T03:15:20.390000
-CVE-2025-21796,0,1,7f08110ad219adf4b6d38f6c9fa72453b590baa69c82fab3e73fa15c81d29c1f,2025-02-27T18:15:30.210000
-CVE-2025-21797,0,0,4b41e92e5965f1c2445d1b5b13db4387e46c769e89caf1a237e699357d28ecd2,2025-02-27T03:15:20.607000
+CVE-2025-21796,0,0,7f08110ad219adf4b6d38f6c9fa72453b590baa69c82fab3e73fa15c81d29c1f,2025-02-27T18:15:30.210000
+CVE-2025-21797,0,1,17c4b4f1f150490a4e61df3fdcf2249554fab9e1a9e4499a5aa1ecd8adb4263d,2025-02-27T19:15:50.807000
+CVE-2025-21798,1,1,7895780e9e5d8c8a1f4734d73ddab195277e9c9b518131fb97f41abf985f7b37,2025-02-27T20:16:02.477000
+CVE-2025-21799,1,1,d417ae611a8872914eef3fd5c81517c36c7d160708cf1d892d73739fdad68bce,2025-02-27T20:16:02.563000
+CVE-2025-21800,1,1,4950e166c6dbd6b5c5400416c70877abc8a4b8d84197ecc107fde3a656637afa,2025-02-27T20:16:02.660000
+CVE-2025-21801,1,1,f6d76f65068d90516e85c99f71de3cb4d197ef71e579886ea64ced33d1d8f98a,2025-02-27T20:16:02.753000
+CVE-2025-21802,1,1,6042f1468c607ff19953f6a399150f8b6cff2455ca3005e4996ff02aa716df45,2025-02-27T20:16:02.847000
+CVE-2025-21803,1,1,88eb8c31940fd7ed25127bfe3deb69973d8cc8355e05a61901f24085d2f08dcc,2025-02-27T20:16:02.937000
+CVE-2025-21804,1,1,360b6caf9fd682754bd1541835419850592ebaddecb83de31f691886c3798f82,2025-02-27T20:16:03.030000
+CVE-2025-21805,1,1,d66f1238d1de7192f6e5313afab1d209855844ecedaa40db7fda88b9436a79cf,2025-02-27T20:16:03.127000
+CVE-2025-21806,1,1,1b348681ceb341f19a3eb69e3236089ce9f3a3fc70696f534307e786daa1ed64,2025-02-27T20:16:03.220000
+CVE-2025-21807,1,1,67a05dacb52811b9bf569fbd8fcf4a8b83466e02cf646f7af0aef4d628ae5d85,2025-02-27T20:16:03.317000
+CVE-2025-21808,1,1,10ba643382834cd75f5810dabc6d17f09c5762feea4e8aae689210d176851fb8,2025-02-27T20:16:03.410000
+CVE-2025-21809,1,1,774815977ce22b27b9b4271ad5f5e31a8d2ee08f73adf866e97eebb52a2bd8de,2025-02-27T20:16:03.497000
+CVE-2025-21810,1,1,605c985c56f5e0b3355a4692d46dce4cbb887fdc232f368462199a701d27d678,2025-02-27T20:16:03.587000
+CVE-2025-21811,1,1,a79a0d5323633b25308a555c838df1bae950ad25d4649726eb20cd50cb96947d,2025-02-27T20:16:03.680000
+CVE-2025-21812,1,1,e33984ff28968d3b124b0e4b60ba112a5619d0e919c0188ad940a7310ccc0aca,2025-02-27T20:16:03.783000
+CVE-2025-21813,1,1,a2ac3d0a57dd533983cc6a16133862989635ca286010be19e414c33729fd42b5,2025-02-27T20:16:03.883000
+CVE-2025-21814,1,1,1459a52e8fa302fdfc1223d6aefb723bb09b77814f7fd0d7b3d0addfc9c27191,2025-02-27T20:16:03.973000
+CVE-2025-21815,1,1,035642d7e64701dea99eb6f4f97274899266dc3d7b451ef440759bf2aab3fd21,2025-02-27T20:16:04.063000
+CVE-2025-21816,1,1,92560a9b0f42fe30ac5e04038b73717a2a490f560288e3cf776f478da14d0ba5,2025-02-27T20:16:04.150000
+CVE-2025-21817,1,1,cd9e37ca374f905d8a849dc7bf1fbc62e5b8b3233e502d0584e2cf7339d59e83,2025-02-27T20:16:04.243000
+CVE-2025-21818,1,1,f180b726a7eea4496e746be0e21726c1f61c0b2262e2b4d49e3048111ba86598,2025-02-27T20:16:04.330000
+CVE-2025-21819,1,1,04cff062526a3cc4040faa29edd822e220ba17b0ce76f7055e4dafd1cd31b179,2025-02-27T20:16:04.430000
+CVE-2025-21820,1,1,d4d632575af6037c264e028166586d53e781ca18870cfe8a4f2c8f97e7efb1b0,2025-02-27T20:16:04.520000
+CVE-2025-21821,1,1,31a4e0c1a84f57342a2219da96b8c5e7a3f7843b10cea483db6e7d6a22159422,2025-02-27T20:16:04.613000
+CVE-2025-21822,1,1,cebdb89de9c638f1d2d37c7769bec6a0191a179976752b4e7bc8e6498b350547,2025-02-27T20:16:04.707000
+CVE-2025-21823,1,1,a5c2dc20b952d1a6f9b27dc79bb595204b6b0797fc9e06476e3ca3dbbc476375,2025-02-27T20:16:04.793000
+CVE-2025-21824,1,1,865963987d7fb25d458dc021cccba4aba1a6837e918ddf851a001c8c46c5cd8d,2025-02-27T20:16:04.890000
CVE-2025-22129,0,0,d84466451eb5813ecdb45d579943a91ad86a0d891b836c8fd8053b0ece067119,2025-02-04T19:15:33.360000
CVE-2025-22130,0,0,a71c51c8237898c4394724aa5ef423b90094196082b564075e1f1cf6c2992343,2025-01-08T16:15:38.543000
CVE-2025-22131,0,0,69440877e24142b0c883a083dd220512bc0b0c9b1551c23031d4be6598836d66,2025-01-20T16:15:27.880000
@@ -281598,6 +281632,7 @@ CVE-2025-22619,0,0,94078c2e9a44454365aeb387ac2d1c51351bb08f1b9ba4f80444a5076273d
CVE-2025-22620,0,0,428c7806e74732326369c718351571848c196156b9eb9eb7ffe99ba9002a1b52,2025-01-20T16:15:28.017000
CVE-2025-22621,0,0,6ff4aa50f3e07d892cb8ed858e238d42c832836da0723e6a77be4111c28ff27e,2025-01-15T17:15:20.810000
CVE-2025-22622,0,0,a17fde34fef88dfd64eac5d9ad181049ae5c9c1d06109d360781ad8823ac8fab,2025-02-19T04:15:10.550000
+CVE-2025-22624,1,1,b0ed4869a52d535456bfa286c8574270e428bb586fcd6ea2246c6f85c4f4722e,2025-02-27T19:15:50.940000
CVE-2025-22630,0,0,65b344426847ac6a4e95d84540acfcdf1858b38747b882234f69839751f9e2a8,2025-02-14T07:15:32.750000
CVE-2025-22631,0,0,69e436df531baecdd19497293d19b2a0d95d2dffd87c903061a5c63214d7075d,2025-02-23T23:15:10.290000
CVE-2025-22632,0,0,151de0b6b8ae5806217a6edccafcf72033afe36b0e0bb440488dc904e4930918,2025-02-23T23:15:10.440000
@@ -281774,6 +281809,7 @@ CVE-2025-22921,0,0,8e982b362e449850e2ea02538af900c3ab253faa0ab7197d6c0c9fbcb9c93
CVE-2025-22936,0,0,d81f6f27c0c4b19886d50175e4767c83ad84386da04b2ebc81be17b6a19a6c20,2025-02-12T14:15:33.187000
CVE-2025-22946,0,0,7db37666dfbf9142b1788db2e9c9ed7b839c8fa56ddb82a64c0b003e5a2cac22,2025-01-14T15:15:28.480000
CVE-2025-22949,0,0,4497a547d6c85b77c71713f92e0bd769cd0fee1b37f22227e370aa8af86f0dec,2025-01-14T15:15:28.637000
+CVE-2025-22952,1,1,305d96a4fa174b5131d07f54f0d216ab2e9a8de566b980a6bbe4d02adb97cbff,2025-02-27T20:16:04.983000
CVE-2025-22957,0,0,a83a10114b8bffbb61185f4b7e1da98510853b7fa64b4f1d87dfa557428e19b8,2025-02-18T19:15:26.813000
CVE-2025-22960,0,0,744fb252a3ba84e23c5f280db7b14361506334b92f4ff5cce622de97d4dcb10c,2025-02-13T23:15:10.960000
CVE-2025-22961,0,0,606400b37cc64b2ede47464265e2232f7088ed78d881daa978231e97f31679dc,2025-02-13T23:15:11.047000
@@ -282097,7 +282133,7 @@ CVE-2025-23683,0,0,11ab818cdded601704d5457da26238366cc9a2cdec8e1cfa4e95b50fb941a
CVE-2025-23684,0,0,529ecfa4f2d7884c1c74d4451718ec8edc46df51f82091b8eeba652ef379906c,2025-02-18T20:15:27.947000
CVE-2025-23685,0,0,0ae9c880b577c05bd221b5d47c19ae7f8930d7d9f3014e4cbcee69e11cc74cc0,2025-02-03T15:15:22.420000
CVE-2025-23686,0,0,3faeff7525d93cc6d2031f95de86c7e21308c8342ae317b9dc855fcb527afe0f,2025-02-18T20:15:28.090000
-CVE-2025-23687,1,1,9a249ef64a7e48c97c5c32f161bd2ee808a44bd9516e6d868df00cf6d33b3ccc,2025-02-27T17:15:16.623000
+CVE-2025-23687,0,0,9a249ef64a7e48c97c5c32f161bd2ee808a44bd9516e6d868df00cf6d33b3ccc,2025-02-27T17:15:16.623000
CVE-2025-23689,0,0,3a077a022662cdd0d4798ac2d9b9685961bbdf05d3a8d2e748b53124c3ed929b,2025-01-16T20:15:44.040000
CVE-2025-23690,0,0,b9e8b4ce7cf418df7c2c552d6aa61f7715b27609fc2dbb370252e45d7528a647,2025-01-16T20:15:44.197000
CVE-2025-23691,0,0,8bccb2407b1830314e082c5ccc8a74914d5f3fb937895330615769bfb1ba0062,2025-01-16T20:15:44.353000
@@ -282951,10 +282987,10 @@ CVE-2025-25323,0,0,9d54f6ab903f7d667d98dd6d95d826ddc61bd41984daa807a0cea6e5a7b66
CVE-2025-25324,0,0,7416fec2baed5a33bce83e714c820e6bbedabfbd40ca8cfcf862246456e22209,2025-02-27T16:15:39.760000
CVE-2025-25325,0,0,c86828d940531de1f9ba9a0442c7b2c96402c4863bc6449fb0dd3ed1d3adb216,2025-02-27T16:15:39.870000
CVE-2025-25326,0,0,955c851f345060263e9fe55f19172f235fd67cd8788d63ce6cc31b2512aba192,2025-02-27T16:15:39.987000
-CVE-2025-25329,1,1,c3d3063744527b7041f8dc9250e7653ecc91051586557f2eedaceff36c858bc4,2025-02-27T17:15:16.773000
+CVE-2025-25329,0,0,c3d3063744527b7041f8dc9250e7653ecc91051586557f2eedaceff36c858bc4,2025-02-27T17:15:16.773000
CVE-2025-25330,0,0,0a92c33d73444ad205c8dff313935ffbef10654588ff371f4eadabd58b6898b2,2025-02-27T16:15:40.103000
CVE-2025-25331,0,0,a7e1084033f53e04a790d37a366d6556d7807dba3d23cde5c9e0f882a523fe13,2025-02-27T16:15:40.217000
-CVE-2025-25333,0,0,362d6f3754ba1c2d14ca30e072a63aa1a54fd62201532f919863b8050dce3230,2025-02-27T16:15:40.350000
+CVE-2025-25333,0,1,6ec9229dcc048d32377c65843d4940ce53486855d56d23de2a9388232fef0e38,2025-02-27T20:16:05.073000
CVE-2025-25334,0,0,09f902b448e0e9b7a4421fffc73864efaba3e065c215ef17ffb5bb8d88ce2adc,2025-02-27T16:15:40.463000
CVE-2025-25343,0,0,58830c0cbe4e53f265b0e865057002c72f07a9ce6d9abf6a7103aa5f63054e04,2025-02-19T16:41:43.887000
CVE-2025-25349,0,0,7493ec8dd478515c80e3ecdac0113c1e149e92926bb9c4a90d85a8a01928eead,2025-02-14T19:34:31.553000
@@ -283317,22 +283353,22 @@ CVE-2025-27012,0,0,7363d114ae429e53b3d9610c9cb193ed78cd11421be4a33a19fcf6bd0f11d
CVE-2025-27013,0,0,5da49234db7e8d732a635aee7726c50524766c42564dc53ab30d5668c258b6b4,2025-02-18T20:15:33.880000
CVE-2025-27016,0,0,5734e0571ba6c0e2c4f7b9ec5f3fbe3b4fb52f565f2d154b09a195684451638c,2025-02-18T20:15:34.013000
CVE-2025-27088,0,0,09d6e70f976103888a70528f06cfe4d5e2532860157df7adae24247eee34e541,2025-02-21T22:15:13.673000
-CVE-2025-27089,0,0,448a9e8f6db990532f78e895caacd3237576915743771cc603136eefd3cabf5b,2025-02-19T17:15:15.800000
-CVE-2025-27090,0,0,3ec553f17ea0ae116be2cc2bd856275e78c4e0654c83946e3af868683f50a7f5,2025-02-19T22:15:24.247000
-CVE-2025-27091,0,0,721ff5d16671af309c1911f7bc031da413f847f8a17055755107c3ee0e59632c,2025-02-20T18:15:26.850000
-CVE-2025-27092,0,0,5ec2aeafb43c7c2a09d8dd21048778fe0610eeb99d26c3067a1f3c2e3e938a4d,2025-02-19T23:15:15.957000
+CVE-2025-27089,0,1,a454d43bdd21fb972482a0ce87896ca310da5d909b4331caf97bfdced4edbcb7,2025-02-27T20:18:12.583000
+CVE-2025-27090,0,1,0a4ccf92007267c16eee4b4b222c0a1bb704a8cf350c4393244356bc535834a9,2025-02-27T20:18:12.583000
+CVE-2025-27091,0,1,b859d3590fe981ab912d6921b74efbe324bec6c5ee689190e2cf257247d50a52,2025-02-27T20:18:12.583000
+CVE-2025-27092,0,1,7104bc7ae5ee9a84de752291fd5401045f96963015db3ee80e61b32134a06641,2025-02-27T20:18:12.583000
CVE-2025-27096,0,0,8031126df0bc9bd3535aad716c9693bd2a080d56a9e9b993fd3a05d39ceae52c,2025-02-20T19:15:12.157000
-CVE-2025-27097,0,0,fea29f969519154b2a8c182fbb3d1d2e3776d37dcbd6b6494f8af1cbae9e182c,2025-02-20T21:15:26.227000
-CVE-2025-27098,0,0,2237b458f6b45c9faae78425b7ee60243eb05c73776387b094e26cb3990ae307,2025-02-20T21:15:26.370000
+CVE-2025-27097,0,1,2589fa071c1a9a9a5c73ad315b8e6452ddbba374e2341b11c614c9f7d8047e61,2025-02-27T20:18:12.583000
+CVE-2025-27098,0,1,492c80cbc63ad6506b976d2c569a0f82a671edac45cb267f8bf0fb56623897bc,2025-02-27T20:18:12.583000
CVE-2025-27100,0,0,152b527bb539a37ffbb5e9412203b3d57121014fdbae99a77c0074299a956949,2025-02-21T00:15:09.250000
CVE-2025-27104,0,0,15aaaf6917676f5eff2f89fbd0c3a21c0c13a6b224565fcd05537a337b8876ab,2025-02-22T16:15:32.640000
CVE-2025-27105,0,0,2bcb6c340eab97672213237573c8f6ca4eeeb614b47978107b021b4da927b7cb,2025-02-22T16:15:32.827000
CVE-2025-27106,0,0,2aea6dfc75b6de975e9d792b22b24672e89a28876099e5c80ae756f94e64cf9c,2025-02-22T16:15:33.003000
-CVE-2025-27108,0,0,7cd07cb1baebc7581e6189da86b0f89ab8f66cca7350d7768234c5e33b5a7c6f,2025-02-21T22:15:14.170000
+CVE-2025-27108,0,1,34d6d1e5e32f01741f013d8e11085ab9652369eb805ee793ac08ed811303f050,2025-02-27T20:18:12.583000
CVE-2025-27109,0,0,887a9677b59d7647aa063bf92caff49be61f0df690b2560df78fd44f58dfdb6b,2025-02-24T17:15:14.850000
CVE-2025-27110,0,0,7df50a11c50cb45bc21a78ad4204e1dc19268096b7d3b27e0bd7325516e8f0a2,2025-02-25T20:15:37.517000
-CVE-2025-27112,0,0,ee0d927c6fb13b15cf89a5e5e15c73d10b42a1b52bf52c1bf9cbd01c1bbcaebd,2025-02-24T19:15:14.597000
-CVE-2025-27113,0,0,d170fa3c72db3eb74309693f02d592d61ed72cb3e9e67a063d1482cf1b9614a1,2025-02-18T23:15:10.960000
+CVE-2025-27112,0,1,ad3bd22bf68a43e9ef7354153af5bf27543e71ad253b691f1b313d10f702063d,2025-02-27T20:18:12.583000
+CVE-2025-27113,0,1,1163a140c7451a5d3ce8342e9e475fc7cc692a5677dca273619df06c0d4a282d,2025-02-27T20:18:12.583000
CVE-2025-27133,0,0,29844716abafc4dda273789005e3e16abe4d7d6eca7ec6dff9bfc7d4679fc1f2,2025-02-24T19:15:14.763000
CVE-2025-27135,0,0,2b4ca3a6c4bb963ede6b8510aa33d7ae3bb4bf8b75f298a6d5163ae954eac93d,2025-02-25T19:15:15.677000
CVE-2025-27137,0,0,5036444bad86a0c9ebb929b7c838035a7163ade99e11b550d9873b63f4ee5567,2025-02-24T21:15:11.213000
@@ -283346,7 +283382,7 @@ CVE-2025-27145,0,0,38c5004ff48d2670f12fb99a3982f3e02a12208e5ab880775c9f41ae19934
CVE-2025-27146,0,0,1949c93bb4c1257d1700888fb7aa70bba73c2053b702350dbd7e6c46a590f25c,2025-02-25T20:15:38.030000
CVE-2025-27148,0,0,5163b56718d84c64a6427ae7a494a2fc79bb8ffbfb0430ce497f1576aee3262b,2025-02-25T21:15:18.073000
CVE-2025-27154,0,0,53a6480a35165b490ac534e1504555080f684ed1444ce4f625bdb4de17643976,2025-02-27T15:15:41.937000
-CVE-2025-27157,1,1,fe20e9b45276a7828e86cd9ecf48db6cff11dc0f19acc72f560fbce846be5f73,2025-02-27T17:15:16.867000
+CVE-2025-27157,0,0,fe20e9b45276a7828e86cd9ecf48db6cff11dc0f19acc72f560fbce846be5f73,2025-02-27T17:15:16.867000
CVE-2025-27218,0,0,efa55c2dc9300fcbe5554c514f0fd9c100e33cfb72ff20b2eedb0bf35dee5b0b,2025-02-20T21:15:26.510000
CVE-2025-27265,0,0,f92ef224928c265ed828ba40cf1c61290404ad79163953c8c2df56f81d7b8ab6,2025-02-24T15:15:14.310000
CVE-2025-27266,0,0,7b4f333de7657eb474765345c5822ee79cdee853af3b515f2a266de5b5a75147,2025-02-24T15:15:14.443000
@@ -283399,4 +283435,4 @@ CVE-2025-27355,0,0,66e7c6f2a2b25e7dd96aabb373de405f0d7238e697b5f6eca301307be69d4
CVE-2025-27356,0,0,451dc4587cf2e56d947661dd5ce87ee61b0a9c7d0fddf41bb2794ffa4d5028c9,2025-02-24T15:15:21.077000
CVE-2025-27357,0,0,a7a6432997c064e16448c81c4ebf75b9895532aa24152d8d607748003751d3d3,2025-02-24T15:15:21.233000
CVE-2025-27364,0,0,a6f68b00caeb3fd723cefacab1c9d3bfa45e0696d3b00b1760eeb7e038956a23,2025-02-24T20:15:34.180000
-CVE-2025-27399,1,1,047834ae4cb02eb8c620e48e474a23f71c1292e787766a014db687c899a834cc,2025-02-27T18:15:30.380000
+CVE-2025-27399,0,0,047834ae4cb02eb8c620e48e474a23f71c1292e787766a014db687c899a834cc,2025-02-27T18:15:30.380000