admin/nvd-json-data-feeds
1
0
Fork 0
mirror of https://github.com/fkie-cad/nvd-json-data-feeds.git synced 2025-06-21 17:41:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Auto-Update: 2024-07-05T08:01:25.528333+00:00

Browse Source
This commit is contained in:
cad-safe-bot 2024-07-05 08:04:20 +00:00
parent f3cb46ad73
commit 153bc9363e
18 changed files with 517 additions and 89 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
CVE-2022/CVE-2022-487xx/CVE-2022-48736.json
View File

@ -2,47 +2,15 @@
"id": "CVE-2022-48736",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-06-20T12:15:11.973",
"lastModified": "2024-06-20T12:43:25.663",
"vulnStatus": "Awaiting Analysis",
"lastModified": "2024-07-05T07:15:09.673",
"vulnStatus": "Rejected",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()\n\nWe don't currently validate that the values being set are within the range\nwe advertised to userspace as being valid, do so and reject any values\nthat are out of range."
"value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/17e16a66b4f9a310713d8599e6e1ca4a0c9fd28c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4cf28e9ae6e2e11a044be1bcbcfa1b0d8675fe4d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/54abca038e287d3746dd40016514670a7f654c5c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6877f87579ed830f9ff6d478539074f035d04bfb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7659f25a80e6affb784b690df8994b79b4212fd4",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b0a7836ecf1345814a7d8ef748fb797c520dad18",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e09cf398e8c6db69c620b6d8073abc4377a07af5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/fd9a23319f16e7031f0d8c98eed6e093c2927229",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
"references": []
}

42
CVE-2022/CVE-2022-487xx/CVE-2022-48737.json
View File

@ -2,47 +2,15 @@
"id": "CVE-2022-48737",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-06-20T12:15:12.060",
"lastModified": "2024-06-20T12:43:25.663",
"vulnStatus": "Awaiting Analysis",
"lastModified": "2024-07-05T07:15:09.927",
"vulnStatus": "Rejected",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()\n\nWe don't currently validate that the values being set are within the range\nwe advertised to userspace as being valid, do so and reject any values\nthat are out of range."
"value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/038f8b7caa74d29e020949a43ca368c93f6b29b9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4977491e4b3aad8567f57e2a9992d251410c1db3",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4f1e50d6a9cf9c1b8c859d449b5031cacfa8404e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9a12fcbf3c622f9bf6b110a873d62b0cba93972e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9e5c40b5706d8aae2cf70bd7e01f0b4575a642d0",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c33402b056de61104b6146dedbe138ca8d7ec62b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e8e07c5e25a29e2a6f119fd947f55d7a55eb8a13",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ef6cd9eeb38062a145802b7b56be7ae1090e165e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
"references": []
}

21
CVE-2024/CVE-2024-394xx/CVE-2024-39472.json Normal file
View File

@ -0,0 +1,21 @@
{
"id": "CVE-2024-39472",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.020",
"lastModified": "2024-07-05T07:15:10.020",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: fix log recovery buffer allocation for the legacy h_size fixup\n\nCommit a70f9fe52daa (\"xfs: detect and handle invalid iclog size set by\nmkfs\") added a fixup for incorrect h_size values used for the initial\numount record in old xfsprogs versions. Later commit 0c771b99d6c9\n(\"xfs: clean up calculation of LR header blocks\") cleaned up the log\nreover buffer calculation, but stoped using the fixed up h_size value\nto size the log recovery buffer, which can lead to an out of bounds\naccess when the incorrect h_size does not come from the old mkfs\ntool, but a fuzzer.\n\nFix this by open coding xlog_logrec_hblks and taking the fixed h_size\ninto account for this calculation."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/45cf976008ddef4a9c9a30310c9b4fb2a9a6602a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

29
CVE-2024/CVE-2024-394xx/CVE-2024-39473.json Normal file
View File

@ -0,0 +1,29 @@
{
"id": "CVE-2024-39473",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.123",
"lastModified": "2024-07-05T07:15:10.123",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: ipc4-topology: Fix input format query of process modules without base extension\n\nIf a process module does not have base config extension then the same\nformat applies to all of it's inputs and the process->base_config_ext is\nNULL, causing NULL dereference when specifically crafted topology and\nsequences used."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/9e16f17a2a0e97b43538b272e7071537a3e03368",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e3ae00ee238bce6cfa5ad935c921181c14d18fd6",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ffa077b2f6ad124ec3d23fbddc5e4b0ff2647af8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

33
CVE-2024/CVE-2024-394xx/CVE-2024-39474.json Normal file
View File

@ -0,0 +1,33 @@
{
"id": "CVE-2024-39474",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.190",
"lastModified": "2024-07-05T07:15:10.190",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmalloc: fix vmalloc which may return null if called with __GFP_NOFAIL\n\ncommit a421ef303008 (\"mm: allow !GFP_KERNEL allocations for kvmalloc\")\nincludes support for __GFP_NOFAIL, but it presents a conflict with commit\ndd544141b9eb (\"vmalloc: back off when the current task is OOM-killed\"). A\npossible scenario is as follows:\n\nprocess-a\n__vmalloc_node_range(GFP_KERNEL | __GFP_NOFAIL)\n __vmalloc_area_node()\n vm_area_alloc_pages()\n\t\t--> oom-killer send SIGKILL to process-a\n if (fatal_signal_pending(current)) break;\n--> return NULL;\n\nTo fix this, do not check fatal_signal_pending() in vm_area_alloc_pages()\nif __GFP_NOFAIL set.\n\nThis issue occurred during OPLUS KASAN TEST. Below is part of the log\n-> oom-killer sends signal to process\n[65731.222840] [ T1308] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/apps/uid_10198,task=gs.intelligence,pid=32454,uid=10198\n\n[65731.259685] [T32454] Call trace:\n[65731.259698] [T32454] dump_backtrace+0xf4/0x118\n[65731.259734] [T32454] show_stack+0x18/0x24\n[65731.259756] [T32454] dump_stack_lvl+0x60/0x7c\n[65731.259781] [T32454] dump_stack+0x18/0x38\n[65731.259800] [T32454] mrdump_common_die+0x250/0x39c [mrdump]\n[65731.259936] [T32454] ipanic_die+0x20/0x34 [mrdump]\n[65731.260019] [T32454] atomic_notifier_call_chain+0xb4/0xfc\n[65731.260047] [T32454] notify_die+0x114/0x198\n[65731.260073] [T32454] die+0xf4/0x5b4\n[65731.260098] [T32454] die_kernel_fault+0x80/0x98\n[65731.260124] [T32454] __do_kernel_fault+0x160/0x2a8\n[65731.260146] [T32454] do_bad_area+0x68/0x148\n[65731.260174] [T32454] do_mem_abort+0x151c/0x1b34\n[65731.260204] [T32454] el1_abort+0x3c/0x5c\n[65731.260227] [T32454] el1h_64_sync_handler+0x54/0x90\n[65731.260248] [T32454] el1h_64_sync+0x68/0x6c\n\n[65731.260269] [T32454] z_erofs_decompress_queue+0x7f0/0x2258\n--> be->decompressed_pages = kvcalloc(be->nr_pages, sizeof(struct page *), GFP_KERNEL | __GFP_NOFAIL);\n\tkernel panic by NULL pointer dereference.\n\terofs assume kvmalloc with __GFP_NOFAIL never return NULL.\n[65731.260293] [T32454] z_erofs_runqueue+0xf30/0x104c\n[65731.260314] [T32454] z_erofs_readahead+0x4f0/0x968\n[65731.260339] [T32454] read_pages+0x170/0xadc\n[65731.260364] [T32454] page_cache_ra_unbounded+0x874/0xf30\n[65731.260388] [T32454] page_cache_ra_order+0x24c/0x714\n[65731.260411] [T32454] filemap_fault+0xbf0/0x1a74\n[65731.260437] [T32454] __do_fault+0xd0/0x33c\n[65731.260462] [T32454] handle_mm_fault+0xf74/0x3fe0\n[65731.260486] [T32454] do_mem_abort+0x54c/0x1b34\n[65731.260509] [T32454] el0_da+0x44/0x94\n[65731.260531] [T32454] el0t_64_sync_handler+0x98/0xb4\n[65731.260553] [T32454] el0t_64_sync+0x198/0x19c"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/198a80833e3421d4c9820a4ae907120adf598c91",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/758678b65164b2158fc1de411092191cb3c394d4",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8e0545c83d672750632f46e3f9ad95c48c91a0fc",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c55d3564ad25ce87ab7cc6af251f9574faebd8da",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

49
CVE-2024/CVE-2024-394xx/CVE-2024-39475.json Normal file
View File

@ -0,0 +1,49 @@
{
"id": "CVE-2024-39475",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.267",
"lastModified": "2024-07-05T07:15:10.267",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: savage: Handle err return when savagefb_check_var failed\n\nThe commit 04e5eac8f3ab(\"fbdev: savage: Error out if pixclock equals zero\")\nchecks the value of pixclock to avoid divide-by-zero error. However\nthe function savagefb_probe doesn't handle the error return of\nsavagefb_check_var. When pixclock is 0, it will cause divide-by-zero error."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/32f92b0078ebf79dbe4827288e0acb50d89d3d5b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4b2c67e30b4e1d2ae19dba8b8e8f3b5fd3cf8089",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/5f446859bfa46df0ffb34149499f48a2c2d8cd95",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6ad959b6703e2c4c5d7af03b4cfd5ff608036339",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/86435f39c18967cdd937d7a49ba539cdea7fb547",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b8385ff814ca4cb7e63789841e6ec2a14c73e1e8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/be754cbd77eaf2932408a4e18532e4945274a5c7",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/edaa57480b876e8203b51df7c3d14a51ea6b09e3",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

49
CVE-2024/CVE-2024-394xx/CVE-2024-39476.json Normal file
View File

@ -0,0 +1,49 @@
{
"id": "CVE-2024-39476",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.340",
"lastModified": "2024-07-05T07:15:10.340",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING\n\nXiao reported that lvm2 test lvconvert-raid-takeover.sh can hang with\nsmall possibility, the root cause is exactly the same as commit\nbed9e27baf52 (\"Revert \"md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d\"\")\n\nHowever, Dan reported another hang after that, and junxiao investigated\nthe problem and found out that this is caused by plugged bio can't issue\nfrom raid5d().\n\nCurrent implementation in raid5d() has a weird dependence:\n\n1) md_check_recovery() from raid5d() must hold 'reconfig_mutex' to clear\n MD_SB_CHANGE_PENDING;\n2) raid5d() handles IO in a deadloop, until all IO are issued;\n3) IO from raid5d() must wait for MD_SB_CHANGE_PENDING to be cleared;\n\nThis behaviour is introduce before v2.6, and for consequence, if other\ncontext hold 'reconfig_mutex', and md_check_recovery() can't update\nsuper_block, then raid5d() will waste one cpu 100% by the deadloop, until\n'reconfig_mutex' is released.\n\nRefer to the implementation from raid1 and raid10, fix this problem by\nskipping issue IO if MD_SB_CHANGE_PENDING is still set after\nmd_check_recovery(), daemon thread will be woken up when 'reconfig_mutex'\nis released. Meanwhile, the hang problem will be fixed as well."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/098d54934814dd876963abfe751c3b1cf7fbe56a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0fa",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3f8d5e802d4cedd445f9a89be8c3fd2d0e99024b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/634ba3c97ec413cb10681c7b196db43ee461ecf4",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/aa64464c8f4d2ab92f6d0b959a1e0767b829d787",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b32aa95843cac6b12c2c014d40fca18aef24a347",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/cd2538e5af495b3c747e503db346470fc1ffc447",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e332a12f65d8fed8cf63bedb4e9317bb872b9ac7",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

25
CVE-2024/CVE-2024-394xx/CVE-2024-39477.json Normal file
View File

@ -0,0 +1,25 @@
{
"id": "CVE-2024-39477",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.413",
"lastModified": "2024-07-05T07:15:10.413",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/hugetlb: do not call vma_add_reservation upon ENOMEM\n\nsysbot reported a splat [1] on __unmap_hugepage_range(). This is because\nvma_needs_reservation() can return -ENOMEM if\nallocate_file_region_entries() fails to allocate the file_region struct\nfor the reservation.\n\nCheck for that and do not call vma_add_reservation() if that is the case,\notherwise region_abort() and region_del() will see that we do not have any\nfile_regions.\n\nIf we detect that vma_needs_reservation() returned -ENOMEM, we clear the\nhugetlb_restore_reserve flag as if this reservation was still consumed, so\nfree_huge_folio() will not increment the resv count.\n\n[1] https://lore.kernel.org/linux-mm/0000000000004096100617c58d54@google.com/T/#ma5983bc1ab18a54910da83416b3f89f3c7ee43aa"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/8daf9c702ee7f825f0de8600abff764acfedea13",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/aa998f9dcb34c28448f86e8f5490f20d5eb0eac7",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

25
CVE-2024/CVE-2024-394xx/CVE-2024-39478.json Normal file
View File

@ -0,0 +1,25 @@
{
"id": "CVE-2024-39478",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.470",
"lastModified": "2024-07-05T07:15:10.470",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: starfive - Do not free stack buffer\n\nRSA text data uses variable length buffer allocated in software stack.\nCalling kfree on it causes undefined behaviour in subsequent operations."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/5944de192663f272033501dcd322b008fca72006",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d7f01649f4eaf1878472d3d3f480ae1e50d98f6c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

29
CVE-2024/CVE-2024-394xx/CVE-2024-39479.json Normal file
View File

@ -0,0 +1,29 @@
{
"id": "CVE-2024-39479",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.530",
"lastModified": "2024-07-05T07:15:10.530",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/hwmon: Get rid of devm\n\nWhen both hwmon and hwmon drvdata (on which hwmon depends) are device\nmanaged resources, the expectation, on device unbind, is that hwmon will be\nreleased before drvdata. However, in i915 there are two separate code\npaths, which both release either drvdata or hwmon and either can be\nreleased before the other. These code paths (for device unbind) are as\nfollows (see also the bug referenced below):\n\nCall Trace:\nrelease_nodes+0x11/0x70\ndevres_release_group+0xb2/0x110\ncomponent_unbind_all+0x8d/0xa0\ncomponent_del+0xa5/0x140\nintel_pxp_tee_component_fini+0x29/0x40 [i915]\nintel_pxp_fini+0x33/0x80 [i915]\ni915_driver_remove+0x4c/0x120 [i915]\ni915_pci_remove+0x19/0x30 [i915]\npci_device_remove+0x32/0xa0\ndevice_release_driver_internal+0x19c/0x200\nunbind_store+0x9c/0xb0\n\nand\n\nCall Trace:\nrelease_nodes+0x11/0x70\ndevres_release_all+0x8a/0xc0\ndevice_unbind_cleanup+0x9/0x70\ndevice_release_driver_internal+0x1c1/0x200\nunbind_store+0x9c/0xb0\n\nThis means that in i915, if use devm, we cannot gurantee that hwmon will\nalways be released before drvdata. Which means that we have a uaf if hwmon\nsysfs is accessed when drvdata has been released but hwmon hasn't.\n\nThe only way out of this seems to be do get rid of devm_ and release/free\neverything explicitly during device unbind.\n\nv2: Change commit message and other minor code changes\nv3: Cleanup from i915_hwmon_register on error (Armin Wolf)\nv4: Eliminate potential static analyzer warning (Rodrigo)\n Eliminate fetch_and_zero (Jani)\nv5: Restore previous logic for ddat_gt->hwmon_dev error return (Andi)"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/5bc9de065b8bb9b8dd8799ecb4592d0403b54281",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ce5a22d22db691d14516c3b8fdbf69139eb2ea8f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/cfa73607eb21a4ce1d6294a2c5733628897b48a2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

49
CVE-2024/CVE-2024-394xx/CVE-2024-39480.json Normal file
View File

@ -0,0 +1,49 @@
{
"id": "CVE-2024-39480",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.590",
"lastModified": "2024-07-05T07:15:10.590",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nkdb: Fix buffer overflow during tab-complete\n\nCurrently, when the user attempts symbol completion with the Tab key, kdb\nwill use strncpy() to insert the completed symbol into the command buffer.\nUnfortunately it passes the size of the source buffer rather than the\ndestination to strncpy() with predictably horrible results. Most obviously\nif the command buffer is already full but cp, the cursor position, is in\nthe middle of the buffer, then we will write past the end of the supplied\nbuffer.\n\nFix this by replacing the dubious strncpy() calls with memmove()/memcpy()\ncalls plus explicit boundary checks to make sure we have enough space\nbefore we start moving characters around."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/107e825cc448b7834b31e8b1b3cf0f57426d46d5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/33d9c814652b971461d1e30bead6792851c209e7",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/cfdc2fa4db57503bc6d3817240547c8ddc55fa96",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ddd2972d8e2dee3b33e8121669d55def59f0be8a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e9730744bf3af04cda23799029342aa3cddbc454",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f636a40834d22e5e3fc748f060211879c056cd33",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f694da720dcf795dc3eb97bf76d220213f76aaa7",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/fb824a99e148ff272a53d71d84122728b5f00992",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

33
CVE-2024/CVE-2024-394xx/CVE-2024-39481.json Normal file
View File

@ -0,0 +1,33 @@
{
"id": "CVE-2024-39481",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.653",
"lastModified": "2024-07-05T07:15:10.653",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: mc: Fix graph walk in media_pipeline_start\n\nThe graph walk tries to follow all links, even if they are not between\npads. This causes a crash with, e.g. a MEDIA_LNK_FL_ANCILLARY_LINK link.\n\nFix this by allowing the walk to proceed only for MEDIA_LNK_FL_DATA_LINK\nlinks."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/788fd0f11e45ae8d3a8ebbd3452a6e83f92db376",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8a9d420149c477e7c97fbd6453704e4612bdd3fa",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bee9440bc0b6b3b7432f7bfde28656262a3484a2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e80d9db99b7b6c697d8d952dfd25c3425cf61499",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

33
CVE-2024/CVE-2024-394xx/CVE-2024-39482.json Normal file
View File

@ -0,0 +1,33 @@
{
"id": "CVE-2024-39482",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.710",
"lastModified": "2024-07-05T07:15:10.710",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbcache: fix variable length array abuse in btree_iter\n\nbtree_iter is used in two ways: either allocated on the stack with a\nfixed size MAX_BSETS, or from a mempool with a dynamic size based on the\nspecific cache set. Previously, the struct had a fixed-length array of\nsize MAX_BSETS which was indexed out-of-bounds for the dynamically-sized\niterators, which causes UBSAN to complain.\n\nThis patch uses the same approach as in bcachefs's sort_iter and splits\nthe iterator into a btree_iter with a flexible array member and a\nbtree_iter_stack which embeds a btree_iter as well as a fixed-length\ndata array."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/0c31344e22dd8d6b1394c6e4c41d639015bdc671",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3a861560ccb35f2a4f0a4b8207fa7c2a35fc7f31",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6479b9f41583b013041943c4602e1ad61cec8148",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/934e1e4331859183a861f396d7dfaf33cb5afb02",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

29
CVE-2024/CVE-2024-394xx/CVE-2024-39483.json Normal file
View File

@ -0,0 +1,29 @@
{
"id": "CVE-2024-39483",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.767",
"lastModified": "2024-07-05T07:15:10.767",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: WARN on vNMI + NMI window iff NMIs are outright masked\n\nWhen requesting an NMI window, WARN on vNMI support being enabled if and\nonly if NMIs are actually masked, i.e. if the vCPU is already handling an\nNMI. KVM's ABI for NMIs that arrive simultanesouly (from KVM's point of\nview) is to inject one NMI and pend the other. When using vNMI, KVM pends\nthe second NMI simply by setting V_NMI_PENDING, and lets the CPU do the\nrest (hardware automatically sets V_NMI_BLOCKING when an NMI is injected).\n\nHowever, if KVM can't immediately inject an NMI, e.g. because the vCPU is\nin an STI shadow or is running with GIF=0, then KVM will request an NMI\nwindow and trigger the WARN (but still function correctly).\n\nWhether or not the GIF=0 case makes sense is debatable, as the intent of\nKVM's behavior is to provide functionality that is as close to real\nhardware as possible. E.g. if two NMIs are sent in quick succession, the\nprobability of both NMIs arriving in an STI shadow is infinitesimally low\non real hardware, but significantly larger in a virtual environment, e.g.\nif the vCPU is preempted in the STI shadow. For GIF=0, the argument isn't\nas clear cut, because the window where two NMIs can collide is much larger\nin bare metal (though still small).\n\nThat said, KVM should not have divergent behavior for the GIF=0 case based\non whether or not vNMI support is enabled. And KVM has allowed\nsimultaneous NMIs with GIF=0 for over a decade, since commit 7460fb4a3400\n(\"KVM: Fix simultaneous NMIs\"). I.e. KVM's GIF=0 handling shouldn't be\nmodified without a *really* good reason to do so, and if KVM's behavior\nwere to be modified, it should be done irrespective of vNMI support."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/1d87cf2eba46deaff6142366127f2323de9f84d1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b4bd556467477420ee3a91fbcba73c579669edc6",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f79edaf7370986d73d204b36c50cc563a4c0f356",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

33
CVE-2024/CVE-2024-394xx/CVE-2024-39484.json Normal file
View File

@ -0,0 +1,33 @@
{
"id": "CVE-2024-39484",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.823",
"lastModified": "2024-07-05T07:15:10.823",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmmc: davinci: Don't strip remove function when driver is builtin\n\nUsing __exit for the remove function results in the remove callback being\ndiscarded with CONFIG_MMC_DAVINCI=y. When such a device gets unbound (e.g.\nusing sysfs or hotplug), the driver is just removed without the cleanup\nbeing performed. This results in resource leaks. Fix it by compiling in the\nremove callback unconditionally.\n\nThis also fixes a W=1 modpost warning:\n\nWARNING: modpost: drivers/mmc/host/davinci_mmc: section mismatch in\nreference: davinci_mmcsd_driver+0x10 (section: .data) ->\ndavinci_mmcsd_remove (section: .exit.text)"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/1d5ed0efe51d36b9ae9b64f133bf41cdbf56f584",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/55c421b364482b61c4c45313a535e61ed5ae4ea3",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/5ee241f72edc6dce5051a5f100eab6cc019d873e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7590da4c04dd4aa9c262da0231e978263861c6eb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

29
CVE-2024/CVE-2024-394xx/CVE-2024-39485.json Normal file
View File

@ -0,0 +1,29 @@
{
"id": "CVE-2024-39485",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-07-05T07:15:10.890",
"lastModified": "2024-07-05T07:15:10.890",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: v4l: async: Properly re-initialise notifier entry in unregister\n\nThe notifier_entry of a notifier is not re-initialised after unregistering\nthe notifier. This leads to dangling pointers being left there so use\nlist_del_init() to return the notifier_entry an empty list."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/1aa6cd4adfc0380fa1ccc2f146848940ff882a66",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/87100b09246202a91fce4a1562955c32229173bb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9537a8425a7a0222999d5839a0b394b1e8834b4a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}

30
README.md
View File

@ -13,13 +13,13 @@ Repository synchronizes with the NVD every 2 hours.
### Last Repository Update
```plain
2024-07-05T04:01:05.264124+00:00
2024-07-05T08:01:25.528333+00:00
```
### Most recent CVE Modification Timestamp synchronized with NVD
```plain
2024-07-05T02:15:10+00:00
2024-07-05T07:15:10.890000+00:00
```
### Last Data Feed Release
@ -33,23 +33,35 @@ Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/
### Total Number of included CVEs
```plain
255892
255906
```
### CVEs added in the last Commit
Recently added CVEs: `4`
Recently added CVEs: `14`
- [CVE-2023-52340](CVE-2023/CVE-2023-523xx/CVE-2023-52340.json) (`2024-07-05T02:15:09.747`)
- [CVE-2024-32498](CVE-2024/CVE-2024-324xx/CVE-2024-32498.json) (`2024-07-05T02:15:09.840`)
- [CVE-2024-34481](CVE-2024/CVE-2024-344xx/CVE-2024-34481.json) (`2024-07-05T02:15:09.920`)
- [CVE-2024-36041](CVE-2024/CVE-2024-360xx/CVE-2024-36041.json) (`2024-07-05T02:15:10.000`)
- [CVE-2024-39472](CVE-2024/CVE-2024-394xx/CVE-2024-39472.json) (`2024-07-05T07:15:10.020`)
- [CVE-2024-39473](CVE-2024/CVE-2024-394xx/CVE-2024-39473.json) (`2024-07-05T07:15:10.123`)
- [CVE-2024-39474](CVE-2024/CVE-2024-394xx/CVE-2024-39474.json) (`2024-07-05T07:15:10.190`)
- [CVE-2024-39475](CVE-2024/CVE-2024-394xx/CVE-2024-39475.json) (`2024-07-05T07:15:10.267`)
- [CVE-2024-39476](CVE-2024/CVE-2024-394xx/CVE-2024-39476.json) (`2024-07-05T07:15:10.340`)
- [CVE-2024-39477](CVE-2024/CVE-2024-394xx/CVE-2024-39477.json) (`2024-07-05T07:15:10.413`)
- [CVE-2024-39478](CVE-2024/CVE-2024-394xx/CVE-2024-39478.json) (`2024-07-05T07:15:10.470`)
- [CVE-2024-39479](CVE-2024/CVE-2024-394xx/CVE-2024-39479.json) (`2024-07-05T07:15:10.530`)
- [CVE-2024-39480](CVE-2024/CVE-2024-394xx/CVE-2024-39480.json) (`2024-07-05T07:15:10.590`)
- [CVE-2024-39481](CVE-2024/CVE-2024-394xx/CVE-2024-39481.json) (`2024-07-05T07:15:10.653`)
- [CVE-2024-39482](CVE-2024/CVE-2024-394xx/CVE-2024-39482.json) (`2024-07-05T07:15:10.710`)
- [CVE-2024-39483](CVE-2024/CVE-2024-394xx/CVE-2024-39483.json) (`2024-07-05T07:15:10.767`)
- [CVE-2024-39484](CVE-2024/CVE-2024-394xx/CVE-2024-39484.json) (`2024-07-05T07:15:10.823`)
- [CVE-2024-39485](CVE-2024/CVE-2024-394xx/CVE-2024-39485.json) (`2024-07-05T07:15:10.890`)
### CVEs modified in the last Commit
Recently modified CVEs: `0`
Recently modified CVEs: `2`
- [CVE-2022-48736](CVE-2022/CVE-2022-487xx/CVE-2022-48736.json) (`2024-07-05T07:15:09.673`)
- [CVE-2022-48737](CVE-2022/CVE-2022-487xx/CVE-2022-48737.json) (`2024-07-05T07:15:09.927`)
## Download and Usage

26
_state.csv
View File

@ -212164,8 +212164,8 @@ CVE-2022-48732,0,0,192ff78d4a4cf41f34317ecdfd997618baf0973772aa995d6f1f0eed9d77f
CVE-2022-48733,0,0,4a91d0d69317ccefdfc251097930a5397746654afd8611241cb6025b76376922,2024-06-20T12:43:25.663000
CVE-2022-48734,0,0,1a0d2941f2fa212dea26e808d10b87095a9dd60a71b597df13fce37156d26d13,2024-06-20T12:43:25.663000
CVE-2022-48735,0,0,a777165f0cecd1755ce7587d54f6f0cea4b57fb7a5bd75b7072a508231a279b4,2024-06-20T12:43:25.663000
CVE-2022-48736,0,0,ee49716c40468d7d5d7138c89f94edeec4ee0849e5b37595e0282a435b91787d,2024-06-20T12:43:25.663000
CVE-2022-48737,0,0,0c92627e1e3d48e57566517ec8438a4e13707a2c370f8a39c709308dec02dca9,2024-06-20T12:43:25.663000
CVE-2022-48736,0,1,81ca9bdcd7e3a82c08985a14ce832c395c4228e286c7331dc57b0f38ea5fffd7,2024-07-05T07:15:09.673000
CVE-2022-48737,0,1,8b9225412227b870ab231e96f2617a46f9a2746c195f03ce0afc138fa1aaec62,2024-07-05T07:15:09.927000
CVE-2022-48738,0,0,b8253a7cf38cc1862912a6bb21627b8f7c0bdc327005a4e407e135cb227b651e,2024-06-20T12:43:25.663000
CVE-2022-48739,0,0,bcdc582d0f8e6bdb336b784c1034abfab8d23293788f50a02490d94b7f49935b,2024-06-20T12:43:25.663000
CVE-2022-4874,0,0,11bc171fda6fc861e0708d150c2ec522d2356e3420b85bbff8eb41cec9dc83eb,2023-11-07T03:59:09.523000
@ -238311,7 +238311,7 @@ CVE-2023-52337,0,0,55fa913fa16a3f0160ce03eb40c23b005cbeaa3ffa6035c50c9b775c51f9b
CVE-2023-52338,0,0,c19a89634d444e8b7418866f672b3a80a92a3dcfedfc6c85a948f1f2cb0e5bd6,2024-07-03T01:43:29.373000
CVE-2023-52339,0,0,4bbe57cf8d5f09dfe60f342a3942dda58e6da98c8314b5c5a36b0823a95b8323,2024-02-05T03:15:07.563000
CVE-2023-5234,0,0,0558a6bed4fe4d192c05a4915c3afbcc280f1387dd5837f40b9ee15558ea5e92,2023-11-29T02:25:14.437000
CVE-2023-52340,1,1,b59add23ec236b25e7f79418d979e4814c989d7d4bd1b14d84ece1a086576496,2024-07-05T02:15:09.747000
CVE-2023-52340,0,0,b59add23ec236b25e7f79418d979e4814c989d7d4bd1b14d84ece1a086576496,2024-07-05T02:15:09.747000
CVE-2023-52341,0,0,e416d66dc300a1fec35b92634bca599425c1eba7c994f713ffc16aead39c631c,2024-04-08T18:48:40.217000
CVE-2023-52342,0,0,3cc4e6ba05ffe1f6726d37db2a1fc94b4779e068fbeefca5708009567484b5be,2024-04-08T18:48:40.217000
CVE-2023-52343,0,0,2299760ff7547b5552eafba56878152128c4cea2a164feb9e7c4648c28b7609e,2024-04-08T18:48:40.217000
@ -250501,7 +250501,7 @@ CVE-2024-3249,0,0,76c646e2435d001bf01037ff3fd93961dd050fc46c496185359532e97ed741
CVE-2024-32491,0,0,d30474497268ba8f1eca4a0213eacdfe653c7390c8a6bb0f205ad6c8bcf6d00f,2024-07-03T01:56:37.743000
CVE-2024-32492,0,0,b8f37fd95afd9f3c0db9b82f19324f4f73a560600fb9ed3392952c1c91bb381c,2024-07-03T01:56:38.510000
CVE-2024-32493,0,0,ffb6c116d41e9a5c89f19db9ee55928315a8849f99630d88960b7d23ca7c5aa5,2024-07-03T01:56:39.257000
CVE-2024-32498,1,1,6ae58d9244f2dc2017702a07fea164c2b2588bb25b5f4905231c608649022465,2024-07-05T02:15:09.840000
CVE-2024-32498,0,0,6ae58d9244f2dc2017702a07fea164c2b2588bb25b5f4905231c608649022465,2024-07-05T02:15:09.840000
CVE-2024-3250,0,0,42d0527e4e3750c8dcbea25ddc3c02af060082636d586aa4581df30dc613d6b8,2024-04-04T22:15:09.350000
CVE-2024-32502,0,0,69fe824b685653a546225dc4ea95ba763f416a7963602dbf9b708132b70355bf,2024-06-07T19:24:09.243000
CVE-2024-32503,0,0,186ab37f647c5868bd0439903b3f859b2664660460df6c82459d804d339c4ae7,2024-06-07T19:24:09.243000
@ -251786,7 +251786,7 @@ CVE-2024-34476,0,0,f460d7b07cd8e1102230047a90895024b7118c0a722ec4264bd02b84a90ba
CVE-2024-34477,0,0,1582bb27a51733ef5d8216b768cf631f7623fa6704a59528ef32a8f5c53cec81,2024-06-07T14:15:10.293000
CVE-2024-34478,0,0,e041b25b36e3062d0ab338fb8a5bf2a23de65e7f383d14a7d54f9bd405368aa0,2024-05-06T12:44:56.377000
CVE-2024-3448,0,0,38511310080ef6cbfb33c1721e41ad41c6df0877e6ffcdbf14f478fa1ea7a673,2024-04-10T19:49:51.183000
CVE-2024-34481,1,1,2a73ad3877257172fa1f55f502cd23990a4cf440b449a6be81b11ec8061b119e,2024-07-05T02:15:09.920000
CVE-2024-34481,0,0,2a73ad3877257172fa1f55f502cd23990a4cf440b449a6be81b11ec8061b119e,2024-07-05T02:15:09.920000
CVE-2024-34483,0,0,6f3bfc57c4ac08b52bc633ea80c521be2c99b03f22d863fb736d441dc611c592,2024-07-03T02:00:16.293000
CVE-2024-34484,0,0,627f49dadca95e26dd01857c2e82a7ff7d913e52fd5d19d3f5a26ae697877b79,2024-05-06T12:44:56.377000
CVE-2024-34486,0,0,26f6d0ef1222cf4bd0474871265bd9abd6351340002c593000a39a9f2c434af7,2024-05-06T12:44:56.377000
@ -252771,7 +252771,7 @@ CVE-2024-36036,0,0,399529c38d111e737eeb859298f0b12af936846a2a63555a4e1fd24103a1a
CVE-2024-36037,0,0,b69974bc3633092c95e0c07f5aa24d13ab328cfb54a9948a0d1d9e8d060f0b0a,2024-07-03T02:02:41.210000
CVE-2024-36038,0,0,c689030949db2782a8d69ade71f9a1affc97ffaf319c773509c47cb5ee7f1cd3,2024-06-24T12:57:36.513000
CVE-2024-36039,0,0,2459d11347af42cb829e5007b01f06e3d0aed0906f508ec72619f858b8aa6d3e,2024-06-24T07:15:15.230000
CVE-2024-36041,1,1,b2c8d3fc339a1a6761eb49802f7b28f8f05360f7f016ced19015d066940057b1,2024-07-05T02:15:10
CVE-2024-36041,0,0,b2c8d3fc339a1a6761eb49802f7b28f8f05360f7f016ced19015d066940057b1,2024-07-05T02:15:10
CVE-2024-36042,0,0,5e54aecb20c44082aa92fd61c0f8a58aa5121675b55d97309cf9a5aaaf11ac5e,2024-07-03T02:02:42.150000
CVE-2024-36043,0,0,a692d077d358c1feb0a509deb9a8e16caf647bf207b7ab7a4cd103038bbab39e,2024-05-20T13:00:04.957000
CVE-2024-36048,0,0,28009f5c9c89d66914a954a3622c5cc8d7b761845f43a58d1b9db13955c9fa8c,2024-06-10T17:16:32.167000
@ -254132,7 +254132,21 @@ CVE-2024-39469,0,0,ecc4b4c7cd43592ae948b90a57c2de7235270598b7f7d8a8dfabf927d5126
CVE-2024-3947,0,0,6b686b580be940e69d22db9dc22782fabd42ffc94dd05568de0bb8f1494d4474,2024-05-30T13:15:41.297000
CVE-2024-39470,0,0,b5fc13f36f82d569439701fae5f56693f98d2351447e7a9e630197f507c5ca47,2024-06-25T18:50:42.040000
CVE-2024-39471,0,0,416dd80dbe9c043e6dbca2fdc8279f4fbac009d216acde71cd007a15b728287a,2024-06-25T18:50:42.040000
CVE-2024-39472,1,1,1edf1073bbaa582cc2a052fc58a57cf2c34719e99d35b369834b85fc084b255c,2024-07-05T07:15:10.020000
CVE-2024-39473,1,1,4dde74fe86d53a03430df35b4971ea6e155dbd6848dd4a2d9f8359fa35d53391,2024-07-05T07:15:10.123000
CVE-2024-39474,1,1,4e66e516a9542ac61620a0cee22164815f1d476c1658ff10a8af2f4672fdb77a,2024-07-05T07:15:10.190000
CVE-2024-39475,1,1,39257dab85e4d5b265a76b49fd9bf617a00bf3cae665ceea57ea34bdfa1e2090,2024-07-05T07:15:10.267000
CVE-2024-39476,1,1,b8876ae57c04f6c7e8d2c9b12325c8c417abb8ca1411646ff6124b383c0a70e5,2024-07-05T07:15:10.340000
CVE-2024-39477,1,1,1728a5fb6e3978250a38fff7f8b1c0f4f961488ea31012b1ce484f355055a976,2024-07-05T07:15:10.413000
CVE-2024-39478,1,1,7a1a95be75cf46187cf117f2046a2af0ebde4891daf292cb3e6d6c780f476402,2024-07-05T07:15:10.470000
CVE-2024-39479,1,1,92c953a4dbf306e8ed837649f4c58b4b64048f8c451e81f891922cb3c1252450,2024-07-05T07:15:10.530000
CVE-2024-3948,0,0,376ea8906f03fda3c144927b149cbacf34b84dec1b654121329bc158cfe1d518,2024-05-17T02:40:12.107000
CVE-2024-39480,1,1,c399e64eb2709fae7e2b3b2570f7a76c80a7dd4c8cc72a1cacadd43bed01a26b,2024-07-05T07:15:10.590000
CVE-2024-39481,1,1,38984bd855a0d520d953480a80ee2f150654a76291542b5c1a1e1fbf5c247522,2024-07-05T07:15:10.653000
CVE-2024-39482,1,1,d13dfbf8d2c61ca7c20b0fdd4fc782136e0b99c158f4f49c5e3588ea53be9c08,2024-07-05T07:15:10.710000
CVE-2024-39483,1,1,aa0762336685a43bc4c42c2d34da10d97c3e41453ed1a75906e6cbe175759038,2024-07-05T07:15:10.767000
CVE-2024-39484,1,1,aa6d45798a337122b172a81f74f3b98cc7156a4537827ac626fdde17c8ad311f,2024-07-05T07:15:10.823000
CVE-2024-39485,1,1,2508c68d4bee663b947179b8877f18e8702b5636ec8ffc65d8713a60d90ce404,2024-07-05T07:15:10.890000
CVE-2024-3951,0,0,d1eb572088193a792816003caae4c8900ea1808fb70b3f34eb162771a0d73b1e,2024-05-08T17:05:24.083000
CVE-2024-3952,0,0,92f1da274771947c3cb4a43546670c1af8a997980dc361a71cd2fb07f162ad15,2024-05-14T16:11:39.510000
CVE-2024-3954,0,0,45f1b348fcace6f84e3157e2d0f8a54fc4228bb396d26e03c9556cd235947f43,2024-05-14T16:11:39.510000

Can't render this file because it is too large.