diff --git a/advisories/unreviewed/2021/12/GHSA-qc3g-2wrf-8fcw/GHSA-qc3g-2wrf-8fcw.json b/advisories/unreviewed/2021/12/GHSA-qc3g-2wrf-8fcw/GHSA-qc3g-2wrf-8fcw.json
index 15c1e6535b8..30dd7debafb 100644
--- a/advisories/unreviewed/2021/12/GHSA-qc3g-2wrf-8fcw/GHSA-qc3g-2wrf-8fcw.json
+++ b/advisories/unreviewed/2021/12/GHSA-qc3g-2wrf-8fcw/GHSA-qc3g-2wrf-8fcw.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-qc3g-2wrf-8fcw",
-  "modified": "2022-01-05T00:02:02Z",
+  "modified": "2024-12-23T15:30:45Z",
   "published": "2021-12-22T00:00:30Z",
   "aliases": [
     "CVE-2021-44207"
   ],
   "details": "Acclaim USAHERDS through 7.4.0.1 uses hard-coded credentials.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
diff --git a/advisories/unreviewed/2024/05/GHSA-2jv6-v65m-qjx7/GHSA-2jv6-v65m-qjx7.json b/advisories/unreviewed/2024/05/GHSA-2jv6-v65m-qjx7/GHSA-2jv6-v65m-qjx7.json
index 4c718a071ff..ee496ffb973 100644
--- a/advisories/unreviewed/2024/05/GHSA-2jv6-v65m-qjx7/GHSA-2jv6-v65m-qjx7.json
+++ b/advisories/unreviewed/2024/05/GHSA-2jv6-v65m-qjx7/GHSA-2jv6-v65m-qjx7.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-2jv6-v65m-qjx7",
-  "modified": "2024-05-01T06:31:42Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26975"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\npowercap: intel_rapl: Fix a NULL pointer dereference\n\nA NULL pointer dereference is triggered when probing the MMIO RAPL\ndriver on platforms with CPU ID not listed in intel_rapl_common CPU\nmodel list.\n\nThis is because the intel_rapl_common module still probes on such\nplatforms even if 'defaults_msr' is not set after commit 1488ac990ac8\n(\"powercap: intel_rapl: Allow probing without CPUID match\"). Thus the\nMMIO RAPL rp->priv->defaults is NULL when registering to RAPL framework.\n\nFix the problem by adding sanity check to ensure rp->priv->rapl_defaults\nis always valid.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -32,8 +37,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-476"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:14Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-3h33-78cr-x67r/GHSA-3h33-78cr-x67r.json b/advisories/unreviewed/2024/05/GHSA-3h33-78cr-x67r/GHSA-3h33-78cr-x67r.json
index 463b31eb9a8..3a2f223127f 100644
--- a/advisories/unreviewed/2024/05/GHSA-3h33-78cr-x67r/GHSA-3h33-78cr-x67r.json
+++ b/advisories/unreviewed/2024/05/GHSA-3h33-78cr-x67r/GHSA-3h33-78cr-x67r.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-3h33-78cr-x67r",
-  "modified": "2024-05-01T06:31:42Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26964"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci: Add error handling in xhci_map_urb_for_dma\n\nCurrently xhci_map_urb_for_dma() creates a temporary buffer and copies\nthe SG list to the new linear buffer. But if the kzalloc_node() fails,\nthen the following sg_pcopy_to_buffer() can lead to crash since it\ntries to memcpy to NULL pointer.\n\nSo return -ENOMEM if kzalloc returns null pointer.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -40,8 +45,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-476"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:12Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-3m73-m9xc-48pv/GHSA-3m73-m9xc-48pv.json b/advisories/unreviewed/2024/05/GHSA-3m73-m9xc-48pv/GHSA-3m73-m9xc-48pv.json
index e55ba774eec..d1a6bba519a 100644
--- a/advisories/unreviewed/2024/05/GHSA-3m73-m9xc-48pv/GHSA-3m73-m9xc-48pv.json
+++ b/advisories/unreviewed/2024/05/GHSA-3m73-m9xc-48pv/GHSA-3m73-m9xc-48pv.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-3m73-m9xc-48pv",
-  "modified": "2024-05-01T06:31:42Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26962"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm-raid456, md/raid456: fix a deadlock for dm-raid456 while io concurrent with reshape\n\nFor raid456, if reshape is still in progress, then IO across reshape\nposition will wait for reshape to make progress. However, for dm-raid,\nin following cases reshape will never make progress hence IO will hang:\n\n1) the array is read-only;\n2) MD_RECOVERY_WAIT is set;\n3) MD_RECOVERY_FROZEN is set;\n\nAfter commit c467e97f079f (\"md/raid6: use valid sector values to determine\nif an I/O should wait on the reshape\") fix the problem that IO across\nreshape position doesn't wait for reshape, the dm-raid test\nshell/lvconvert-raid-reshape.sh start to hang:\n\n[root@fedora ~]# cat /proc/979/stack\n[<0>] wait_woken+0x7d/0x90\n[<0>] raid5_make_request+0x929/0x1d70 [raid456]\n[<0>] md_handle_request+0xc2/0x3b0 [md_mod]\n[<0>] raid_map+0x2c/0x50 [dm_raid]\n[<0>] __map_bio+0x251/0x380 [dm_mod]\n[<0>] dm_submit_bio+0x1f0/0x760 [dm_mod]\n[<0>] __submit_bio+0xc2/0x1c0\n[<0>] submit_bio_noacct_nocheck+0x17f/0x450\n[<0>] submit_bio_noacct+0x2bc/0x780\n[<0>] submit_bio+0x70/0xc0\n[<0>] mpage_readahead+0x169/0x1f0\n[<0>] blkdev_readahead+0x18/0x30\n[<0>] read_pages+0x7c/0x3b0\n[<0>] page_cache_ra_unbounded+0x1ab/0x280\n[<0>] force_page_cache_ra+0x9e/0x130\n[<0>] page_cache_sync_ra+0x3b/0x110\n[<0>] filemap_get_pages+0x143/0xa30\n[<0>] filemap_read+0xdc/0x4b0\n[<0>] blkdev_read_iter+0x75/0x200\n[<0>] vfs_read+0x272/0x460\n[<0>] ksys_read+0x7a/0x170\n[<0>] __x64_sys_read+0x1c/0x30\n[<0>] do_syscall_64+0xc6/0x230\n[<0>] entry_SYSCALL_64_after_hwframe+0x6c/0x74\n\nThis is because reshape can't make progress.\n\nFor md/raid, the problem doesn't exist because register new sync_thread\ndoesn't rely on the IO to be done any more:\n\n1) If array is read-only, it can switch to read-write by ioctl/sysfs;\n2) md/raid never set MD_RECOVERY_WAIT;\n3) If MD_RECOVERY_FROZEN is set, mddev_suspend() doesn't hold\n   'reconfig_mutex', hence it can be cleared and reshape can continue by\n   sysfs api 'sync_action'.\n\nHowever, I'm not sure yet how to avoid the problem in dm-raid yet. This\npatch on the one hand make sure raid_message() can't change\nsync_thread() through raid_message() after presuspend(), on the other\nhand detect the above 3 cases before wait for IO do be done in\ndm_suspend(), and let dm-raid requeue those IO.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -28,8 +33,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-667"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:12Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-5mg2-xwpp-qvmq/GHSA-5mg2-xwpp-qvmq.json b/advisories/unreviewed/2024/05/GHSA-5mg2-xwpp-qvmq/GHSA-5mg2-xwpp-qvmq.json
index e77f45929eb..e366836bca0 100644
--- a/advisories/unreviewed/2024/05/GHSA-5mg2-xwpp-qvmq/GHSA-5mg2-xwpp-qvmq.json
+++ b/advisories/unreviewed/2024/05/GHSA-5mg2-xwpp-qvmq/GHSA-5mg2-xwpp-qvmq.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-5mg2-xwpp-qvmq",
-  "modified": "2024-05-01T15:30:36Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:36Z",
   "aliases": [
     "CVE-2024-27064"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: Fix a memory leak in nf_tables_updchain\n\nIf nft_netdev_register_hooks() fails, the memory associated with\nnft_stats is not freed, causing a memory leak.\n\nThis patch fixes it by moving nft_stats_alloc() down after\nnft_netdev_register_hooks() succeeds.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -32,8 +37,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-401"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:50Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-5xmm-chg9-ppmr/GHSA-5xmm-chg9-ppmr.json b/advisories/unreviewed/2024/05/GHSA-5xmm-chg9-ppmr/GHSA-5xmm-chg9-ppmr.json
index b5a9a53bfad..8b3035c79ab 100644
--- a/advisories/unreviewed/2024/05/GHSA-5xmm-chg9-ppmr/GHSA-5xmm-chg9-ppmr.json
+++ b/advisories/unreviewed/2024/05/GHSA-5xmm-chg9-ppmr/GHSA-5xmm-chg9-ppmr.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-5xmm-chg9-ppmr",
-  "modified": "2024-06-26T00:31:38Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26958"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfs: fix UAF in direct writes\n\nIn production we have been hitting the following warning consistently\n\n------------[ cut here ]------------\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 17 PID: 1800359 at lib/refcount.c:28 refcount_warn_saturate+0x9c/0xe0\nWorkqueue: nfsiod nfs_direct_write_schedule_work [nfs]\nRIP: 0010:refcount_warn_saturate+0x9c/0xe0\nPKRU: 55555554\nCall Trace:\n <TASK>\n ? __warn+0x9f/0x130\n ? refcount_warn_saturate+0x9c/0xe0\n ? report_bug+0xcc/0x150\n ? handle_bug+0x3d/0x70\n ? exc_invalid_op+0x16/0x40\n ? asm_exc_invalid_op+0x16/0x20\n ? refcount_warn_saturate+0x9c/0xe0\n nfs_direct_write_schedule_work+0x237/0x250 [nfs]\n process_one_work+0x12f/0x4a0\n worker_thread+0x14e/0x3b0\n ? ZSTD_getCParams_internal+0x220/0x220\n kthread+0xdc/0x120\n ? __btf_name_valid+0xa0/0xa0\n ret_from_fork+0x1f/0x30\n\nThis is because we're completing the nfs_direct_request twice in a row.\n\nThe source of this is when we have our commit requests to submit, we\nprocess them and send them off, and then in the completion path for the\ncommit requests we have\n\nif (nfs_commit_end(cinfo.mds))\n\tnfs_direct_write_complete(dreq);\n\nHowever since we're submitting asynchronous requests we sometimes have\none that completes before we submit the next one, so we end up calling\ncomplete on the nfs_direct_request twice.\n\nThe only other place we use nfs_generic_commit_list() is in\n__nfs_commit_inode, which wraps this call in a\n\nnfs_commit_begin();\nnfs_commit_end();\n\nWhich is a common pattern for this style of completion handling, one\nthat is also repeated in the direct code with get_dreq()/put_dreq()\ncalls around where we process events as well as in the completion paths.\n\nFix this by using the same pattern for the commit requests.\n\nBefore with my 200 node rocksdb stress running this warning would pop\nevery 10ish minutes.  With my patch the stress test has been running for\nseveral hours without popping.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -48,8 +53,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-416"
+    ],
+    "severity": "HIGH",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:12Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-6f8x-5hmv-67rj/GHSA-6f8x-5hmv-67rj.json b/advisories/unreviewed/2024/05/GHSA-6f8x-5hmv-67rj/GHSA-6f8x-5hmv-67rj.json
index 2b4ee48541c..5c00bb16457 100644
--- a/advisories/unreviewed/2024/05/GHSA-6f8x-5hmv-67rj/GHSA-6f8x-5hmv-67rj.json
+++ b/advisories/unreviewed/2024/05/GHSA-6f8x-5hmv-67rj/GHSA-6f8x-5hmv-67rj.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-6f8x-5hmv-67rj",
-  "modified": "2024-06-25T21:31:12Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:35Z",
   "aliases": [
     "CVE-2024-27038"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: Fix clk_core_get NULL dereference\n\nIt is possible for clk_core_get to dereference a NULL in the following\nsequence:\n\nclk_core_get()\n    of_clk_get_hw_from_clkspec()\n        __of_clk_get_hw_from_provider()\n            __clk_get_hw()\n\n__clk_get_hw() can return NULL which is dereferenced by clk_core_get() at\nhw->core.\n\nPrior to commit dde4eff47c82 (\"clk: Look for parents with clkdev based\nclk_lookups\") the check IS_ERR_OR_NULL() was performed which would have\ncaught the NULL.\n\nReading the description of this function it talks about returning NULL but\nthat cannot be so at the moment.\n\nUpdate the function to check for hw before dereferencing it and return NULL\nif hw is NULL.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -52,8 +57,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-476"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:49Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-7533-c28p-jp9p/GHSA-7533-c28p-jp9p.json b/advisories/unreviewed/2024/05/GHSA-7533-c28p-jp9p/GHSA-7533-c28p-jp9p.json
index c808439e405..66d12ad1aa9 100644
--- a/advisories/unreviewed/2024/05/GHSA-7533-c28p-jp9p/GHSA-7533-c28p-jp9p.json
+++ b/advisories/unreviewed/2024/05/GHSA-7533-c28p-jp9p/GHSA-7533-c28p-jp9p.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-7533-c28p-jp9p",
-  "modified": "2024-06-26T00:31:39Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26961"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmac802154: fix llsec key resources release in mac802154_llsec_key_del\n\nmac802154_llsec_key_del() can free resources of a key directly without\nfollowing the RCU rules for waiting before the end of a grace period. This\nmay lead to use-after-free in case llsec_lookup_key() is traversing the\nlist of keys in parallel with a key deletion:\n\nrefcount_t: addition on 0; use-after-free.\nWARNING: CPU: 4 PID: 16000 at lib/refcount.c:25 refcount_warn_saturate+0x162/0x2a0\nModules linked in:\nCPU: 4 PID: 16000 Comm: wpan-ping Not tainted 6.7.0 #19\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x162/0x2a0\nCall Trace:\n <TASK>\n llsec_lookup_key.isra.0+0x890/0x9e0\n mac802154_llsec_encrypt+0x30c/0x9c0\n ieee802154_subif_start_xmit+0x24/0x1e0\n dev_hard_start_xmit+0x13e/0x690\n sch_direct_xmit+0x2ae/0xbc0\n __dev_queue_xmit+0x11dd/0x3c20\n dgram_sendmsg+0x90b/0xd60\n __sys_sendto+0x466/0x4c0\n __x64_sys_sendto+0xe0/0x1c0\n do_syscall_64+0x45/0xf0\n entry_SYSCALL_64_after_hwframe+0x6e/0x76\n\nAlso, ieee802154_llsec_key_entry structures are not freed by\nmac802154_llsec_key_del():\n\nunreferenced object 0xffff8880613b6980 (size 64):\n  comm \"iwpan\", pid 2176, jiffies 4294761134 (age 60.475s)\n  hex dump (first 32 bytes):\n    78 0d 8f 18 80 88 ff ff 22 01 00 00 00 00 ad de  x.......\".......\n    00 00 00 00 00 00 00 00 03 00 cd ab 00 00 00 00  ................\n  backtrace:\n    [<ffffffff81dcfa62>] __kmem_cache_alloc_node+0x1e2/0x2d0\n    [<ffffffff81c43865>] kmalloc_trace+0x25/0xc0\n    [<ffffffff88968b09>] mac802154_llsec_key_add+0xac9/0xcf0\n    [<ffffffff8896e41a>] ieee802154_add_llsec_key+0x5a/0x80\n    [<ffffffff8892adc6>] nl802154_add_llsec_key+0x426/0x5b0\n    [<ffffffff86ff293e>] genl_family_rcv_msg_doit+0x1fe/0x2f0\n    [<ffffffff86ff46d1>] genl_rcv_msg+0x531/0x7d0\n    [<ffffffff86fee7a9>] netlink_rcv_skb+0x169/0x440\n    [<ffffffff86ff1d88>] genl_rcv+0x28/0x40\n    [<ffffffff86fec15c>] netlink_unicast+0x53c/0x820\n    [<ffffffff86fecd8b>] netlink_sendmsg+0x93b/0xe60\n    [<ffffffff86b91b35>] ____sys_sendmsg+0xac5/0xca0\n    [<ffffffff86b9c3dd>] ___sys_sendmsg+0x11d/0x1c0\n    [<ffffffff86b9c65a>] __sys_sendmsg+0xfa/0x1d0\n    [<ffffffff88eadbf5>] do_syscall_64+0x45/0xf0\n    [<ffffffff890000ea>] entry_SYSCALL_64_after_hwframe+0x6e/0x76\n\nHandle the proper resource release in the RCU callback function\nmac802154_llsec_key_del_rcu().\n\nNote that if llsec_lookup_key() finds a key, it gets a refcount via\nllsec_key_get() and locally copies key id from key_entry (which is a\nlist element). So it's safe to call llsec_key_put() and free the list\nentry after the RCU grace period elapses.\n\nFound by Linux Verification Center (linuxtesting.org).",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -48,8 +53,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-416"
+    ],
+    "severity": "HIGH",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:12Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-75hm-6r7q-72p3/GHSA-75hm-6r7q-72p3.json b/advisories/unreviewed/2024/05/GHSA-75hm-6r7q-72p3/GHSA-75hm-6r7q-72p3.json
index 09d814bdee2..a2679e9ad1b 100644
--- a/advisories/unreviewed/2024/05/GHSA-75hm-6r7q-72p3/GHSA-75hm-6r7q-72p3.json
+++ b/advisories/unreviewed/2024/05/GHSA-75hm-6r7q-72p3/GHSA-75hm-6r7q-72p3.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-75hm-6r7q-72p3",
-  "modified": "2024-06-27T15:30:38Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:37Z",
   "aliases": [
     "CVE-2024-27078"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: v4l2-tpg: fix some memleaks in tpg_alloc\n\nIn tpg_alloc, resources should be deallocated in each and every\nerror-handling paths, since they are allocated in for statements.\nOtherwise there would be memleaks because tpg_free is called only when\ntpg_alloc return 0.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -60,8 +65,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-401"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:51Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-75m5-rxwg-h223/GHSA-75m5-rxwg-h223.json b/advisories/unreviewed/2024/05/GHSA-75m5-rxwg-h223/GHSA-75m5-rxwg-h223.json
index 6f0ca1bbbd6..825f9035c56 100644
--- a/advisories/unreviewed/2024/05/GHSA-75m5-rxwg-h223/GHSA-75m5-rxwg-h223.json
+++ b/advisories/unreviewed/2024/05/GHSA-75m5-rxwg-h223/GHSA-75m5-rxwg-h223.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-75m5-rxwg-h223",
-  "modified": "2024-06-27T12:30:45Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:37Z",
   "aliases": [
     "CVE-2024-27077"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: v4l2-mem2mem: fix a memleak in v4l2_m2m_register_entity\n\nThe entity->name (i.e. name) is allocated in v4l2_m2m_register_entity\nbut isn't freed in its following error-handling paths. This patch\nadds such deallocation to prevent memleak of entity->name.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -60,8 +65,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-401"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:51Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-767c-45p6-hv5q/GHSA-767c-45p6-hv5q.json b/advisories/unreviewed/2024/05/GHSA-767c-45p6-hv5q/GHSA-767c-45p6-hv5q.json
index 237dd1ef9cc..4786e4af161 100644
--- a/advisories/unreviewed/2024/05/GHSA-767c-45p6-hv5q/GHSA-767c-45p6-hv5q.json
+++ b/advisories/unreviewed/2024/05/GHSA-767c-45p6-hv5q/GHSA-767c-45p6-hv5q.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-767c-45p6-hv5q",
-  "modified": "2024-06-27T12:30:45Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26974"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - resolve race condition during AER recovery\n\nDuring the PCI AER system's error recovery process, the kernel driver\nmay encounter a race condition with freeing the reset_data structure's\nmemory. If the device restart will take more than 10 seconds the function\nscheduling that restart will exit due to a timeout, and the reset_data\nstructure will be freed. However, this data structure is used for\ncompletion notification after the restart is completed, which leads\nto a UAF bug.\n\nThis results in a KFENCE bug notice.\n\n  BUG: KFENCE: use-after-free read in adf_device_reset_worker+0x38/0xa0 [intel_qat]\n  Use-after-free read at 0x00000000bc56fddf (in kfence-#142):\n  adf_device_reset_worker+0x38/0xa0 [intel_qat]\n  process_one_work+0x173/0x340\n\nTo resolve this race condition, the memory associated to the container\nof the work_struct is freed on the worker if the timeout expired,\notherwise on the function that schedules the worker.\nThe timeout detection can be done by checking if the caller is\nstill waiting for completion or not by using completion_done() function.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -60,8 +65,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-367"
+    ],
+    "severity": "HIGH",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:14Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-858x-8r82-7826/GHSA-858x-8r82-7826.json b/advisories/unreviewed/2024/05/GHSA-858x-8r82-7826/GHSA-858x-8r82-7826.json
index c7b457fc4e8..7d4a5547d79 100644
--- a/advisories/unreviewed/2024/05/GHSA-858x-8r82-7826/GHSA-858x-8r82-7826.json
+++ b/advisories/unreviewed/2024/05/GHSA-858x-8r82-7826/GHSA-858x-8r82-7826.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-858x-8r82-7826",
-  "modified": "2024-06-27T15:30:38Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:34Z",
   "aliases": [
     "CVE-2023-52650"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tegra: dsi: Add missing check for of_find_device_by_node\n\nAdd check for the return value of of_find_device_by_node() and return\nthe error if it fails in order to avoid NULL pointer dereference.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -60,8 +65,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-476"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:48Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-8979-xf4w-fmjp/GHSA-8979-xf4w-fmjp.json b/advisories/unreviewed/2024/05/GHSA-8979-xf4w-fmjp/GHSA-8979-xf4w-fmjp.json
index cbadad1741b..620836c8963 100644
--- a/advisories/unreviewed/2024/05/GHSA-8979-xf4w-fmjp/GHSA-8979-xf4w-fmjp.json
+++ b/advisories/unreviewed/2024/05/GHSA-8979-xf4w-fmjp/GHSA-8979-xf4w-fmjp.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-8979-xf4w-fmjp",
-  "modified": "2024-05-01T06:31:42Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26968"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: qcom: gcc-ipq9574: fix terminating of frequency table arrays\n\nThe frequency table arrays are supposed to be terminated with an\nempty element. Add such entry to the end of the arrays where it\nis missing in order to avoid possible out-of-bound access when\nthe table is traversed by functions like qcom_find_freq() or\nqcom_find_freq_floor().\n\nOnly compile tested.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -32,8 +37,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-129"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:13Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-8prj-gx2p-fgx6/GHSA-8prj-gx2p-fgx6.json b/advisories/unreviewed/2024/05/GHSA-8prj-gx2p-fgx6/GHSA-8prj-gx2p-fgx6.json
index c7319652a06..1b6c3bdc8e5 100644
--- a/advisories/unreviewed/2024/05/GHSA-8prj-gx2p-fgx6/GHSA-8prj-gx2p-fgx6.json
+++ b/advisories/unreviewed/2024/05/GHSA-8prj-gx2p-fgx6/GHSA-8prj-gx2p-fgx6.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-8prj-gx2p-fgx6",
-  "modified": "2024-06-26T00:31:41Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:37Z",
   "aliases": [
     "CVE-2024-27076"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imx: csc/scaler: fix v4l2_ctrl_handler memory leak\n\nFree the memory allocated in v4l2_ctrl_handler_init on release.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -52,8 +57,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-401"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:51Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-97jf-xcmh-9j8r/GHSA-97jf-xcmh-9j8r.json b/advisories/unreviewed/2024/05/GHSA-97jf-xcmh-9j8r/GHSA-97jf-xcmh-9j8r.json
index af932c7fd6b..9bcb1687204 100644
--- a/advisories/unreviewed/2024/05/GHSA-97jf-xcmh-9j8r/GHSA-97jf-xcmh-9j8r.json
+++ b/advisories/unreviewed/2024/05/GHSA-97jf-xcmh-9j8r/GHSA-97jf-xcmh-9j8r.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-97jf-xcmh-9j8r",
-  "modified": "2024-05-01T15:30:36Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:36Z",
   "aliases": [
     "CVE-2024-27068"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nthermal/drivers/mediatek/lvts_thermal: Fix a memory leak in an error handling path\n\nIf devm_krealloc() fails, then 'efuse' is leaking.\nSo free it to avoid a leak.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -32,8 +37,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-401"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:50Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-9g4f-34x6-x7jf/GHSA-9g4f-34x6-x7jf.json b/advisories/unreviewed/2024/05/GHSA-9g4f-34x6-x7jf/GHSA-9g4f-34x6-x7jf.json
index bc21401c443..d0f7543cbc2 100644
--- a/advisories/unreviewed/2024/05/GHSA-9g4f-34x6-x7jf/GHSA-9g4f-34x6-x7jf.json
+++ b/advisories/unreviewed/2024/05/GHSA-9g4f-34x6-x7jf/GHSA-9g4f-34x6-x7jf.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-9g4f-34x6-x7jf",
-  "modified": "2024-10-04T18:31:08Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:36Z",
   "aliases": [
     "CVE-2024-27060"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nthunderbolt: Fix NULL pointer dereference in tb_port_update_credits()\n\nOlliver reported that his system crashes when plugging in Thunderbolt 1\ndevice:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000020\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n PGD 0 P4D 0\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n RIP: 0010:tb_port_do_update_credits+0x1b/0x130 [thunderbolt]\n Call Trace:\n  <TASK>\n  ? __die+0x23/0x70\n  ? page_fault_oops+0x171/0x4e0\n  ? exc_page_fault+0x7f/0x180\n  ? asm_exc_page_fault+0x26/0x30\n  ? tb_port_do_update_credits+0x1b/0x130\n  ? tb_switch_update_link_attributes+0x83/0xd0\n  tb_switch_add+0x7a2/0xfe0\n  tb_scan_port+0x236/0x6f0\n  tb_handle_hotplug+0x6db/0x900\n  process_one_work+0x171/0x340\n  worker_thread+0x27b/0x3a0\n  ? __pfx_worker_thread+0x10/0x10\n  kthread+0xe5/0x120\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x31/0x50\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork_asm+0x1b/0x30\n  </TASK>\n\nThis is due the fact that some Thunderbolt 1 devices only have one lane\nadapter. Fix this by checking for the lane 1 before we read its credits.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -28,8 +33,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-476"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:50Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-jmvg-mjm5-3vc4/GHSA-jmvg-mjm5-3vc4.json b/advisories/unreviewed/2024/05/GHSA-jmvg-mjm5-3vc4/GHSA-jmvg-mjm5-3vc4.json
index 1e290cd20bf..40a4490ca0d 100644
--- a/advisories/unreviewed/2024/05/GHSA-jmvg-mjm5-3vc4/GHSA-jmvg-mjm5-3vc4.json
+++ b/advisories/unreviewed/2024/05/GHSA-jmvg-mjm5-3vc4/GHSA-jmvg-mjm5-3vc4.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-jmvg-mjm5-3vc4",
-  "modified": "2024-05-01T06:31:42Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26967"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: qcom: camcc-sc8280xp: fix terminating of frequency table arrays\n\nThe frequency table arrays are supposed to be terminated with an\nempty element. Add such entry to the end of the arrays where it\nis missing in order to avoid possible out-of-bound access when\nthe table is traversed by functions like qcom_find_freq() or\nqcom_find_freq_floor().\n\nOnly compile tested.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -24,8 +29,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-129"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:13Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-m4vr-jmc8-6xrj/GHSA-m4vr-jmc8-6xrj.json b/advisories/unreviewed/2024/05/GHSA-m4vr-jmc8-6xrj/GHSA-m4vr-jmc8-6xrj.json
index c8aaf7a5bbf..dc85143184a 100644
--- a/advisories/unreviewed/2024/05/GHSA-m4vr-jmc8-6xrj/GHSA-m4vr-jmc8-6xrj.json
+++ b/advisories/unreviewed/2024/05/GHSA-m4vr-jmc8-6xrj/GHSA-m4vr-jmc8-6xrj.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-m4vr-jmc8-6xrj",
-  "modified": "2024-06-27T12:30:46Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:36Z",
   "aliases": [
     "CVE-2024-27074"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: go7007: fix a memleak in go7007_load_encoder\n\nIn go7007_load_encoder, bounce(i.e. go->boot_fw), is allocated without\na deallocation thereafter. After the following call chain:\n\nsaa7134_go7007_init\n  |-> go7007_boot_encoder\n        |-> go7007_load_encoder\n  |-> kfree(go)\n\ngo is freed and thus bounce is leaked.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -60,8 +65,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-401"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:51Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-p9xp-vch3-fpjp/GHSA-p9xp-vch3-fpjp.json b/advisories/unreviewed/2024/05/GHSA-p9xp-vch3-fpjp/GHSA-p9xp-vch3-fpjp.json
index ef76b623526..34108e2fc37 100644
--- a/advisories/unreviewed/2024/05/GHSA-p9xp-vch3-fpjp/GHSA-p9xp-vch3-fpjp.json
+++ b/advisories/unreviewed/2024/05/GHSA-p9xp-vch3-fpjp/GHSA-p9xp-vch3-fpjp.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-p9xp-vch3-fpjp",
-  "modified": "2024-06-26T00:31:40Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:35Z",
   "aliases": [
     "CVE-2024-27044"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Fix potential NULL pointer dereferences in 'dcn10_set_output_transfer_func()'\n\nThe 'stream' pointer is used in dcn10_set_output_transfer_func() before\nthe check if 'stream' is NULL.\n\nFixes the below:\ndrivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn10/dcn10_hwseq.c:1892 dcn10_set_output_transfer_func() warn: variable dereferenced before check 'stream' (see line 1875)",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -52,8 +57,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-476"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:49Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-q557-gm3j-fg4w/GHSA-q557-gm3j-fg4w.json b/advisories/unreviewed/2024/05/GHSA-q557-gm3j-fg4w/GHSA-q557-gm3j-fg4w.json
index 632b3f74ddc..672e3c47ed0 100644
--- a/advisories/unreviewed/2024/05/GHSA-q557-gm3j-fg4w/GHSA-q557-gm3j-fg4w.json
+++ b/advisories/unreviewed/2024/05/GHSA-q557-gm3j-fg4w/GHSA-q557-gm3j-fg4w.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-q557-gm3j-fg4w",
-  "modified": "2024-06-27T12:30:45Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26966"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: qcom: mmcc-apq8084: fix terminating of frequency table arrays\n\nThe frequency table arrays are supposed to be terminated with an\nempty element. Add such entry to the end of the arrays where it\nis missing in order to avoid possible out-of-bound access when\nthe table is traversed by functions like qcom_find_freq() or\nqcom_find_freq_floor().\n\nOnly compile tested.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -60,8 +65,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-129"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:12Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-qfxq-cgcj-hcmg/GHSA-qfxq-cgcj-hcmg.json b/advisories/unreviewed/2024/05/GHSA-qfxq-cgcj-hcmg/GHSA-qfxq-cgcj-hcmg.json
index 0cd1e4759ae..152a8afe366 100644
--- a/advisories/unreviewed/2024/05/GHSA-qfxq-cgcj-hcmg/GHSA-qfxq-cgcj-hcmg.json
+++ b/advisories/unreviewed/2024/05/GHSA-qfxq-cgcj-hcmg/GHSA-qfxq-cgcj-hcmg.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-qfxq-cgcj-hcmg",
-  "modified": "2024-10-10T12:31:11Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:43Z",
   "aliases": [
     "CVE-2024-27011"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix memleak in map from abort path\n\nThe delete set command does not rely on the transaction object for\nelement removal, therefore, a combination of delete element + delete set\nfrom the abort path could result in restoring twice the refcount of the\nmapping.\n\nCheck for inactive element in the next generation for the delete element\ncommand in the abort path, skip restoring state if next generation bit\nhas been already cleared. This is similar to the activate logic using\nthe set walk iterator.\n\n[ 6170.286929] ------------[ cut here ]------------\n[ 6170.286939] WARNING: CPU: 6 PID: 790302 at net/netfilter/nf_tables_api.c:2086 nf_tables_chain_destroy+0x1f7/0x220 [nf_tables]\n[ 6170.287071] Modules linked in: [...]\n[ 6170.287633] CPU: 6 PID: 790302 Comm: kworker/6:2 Not tainted 6.9.0-rc3+ #365\n[ 6170.287768] RIP: 0010:nf_tables_chain_destroy+0x1f7/0x220 [nf_tables]\n[ 6170.287886] Code: df 48 8d 7d 58 e8 69 2e 3b df 48 8b 7d 58 e8 80 1b 37 df 48 8d 7d 68 e8 57 2e 3b df 48 8b 7d 68 e8 6e 1b 37 df 48 89 ef eb c4 <0f> 0b 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 0f\n[ 6170.287895] RSP: 0018:ffff888134b8fd08 EFLAGS: 00010202\n[ 6170.287904] RAX: 0000000000000001 RBX: ffff888125bffb28 RCX: dffffc0000000000\n[ 6170.287912] RDX: 0000000000000003 RSI: ffffffffa20298ab RDI: ffff88811ebe4750\n[ 6170.287919] RBP: ffff88811ebe4700 R08: ffff88838e812650 R09: fffffbfff0623a55\n[ 6170.287926] R10: ffffffff8311d2af R11: 0000000000000001 R12: ffff888125bffb10\n[ 6170.287933] R13: ffff888125bffb10 R14: dead000000000122 R15: dead000000000100\n[ 6170.287940] FS:  0000000000000000(0000) GS:ffff888390b00000(0000) knlGS:0000000000000000\n[ 6170.287948] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 6170.287955] CR2: 00007fd31fc00710 CR3: 0000000133f60004 CR4: 00000000001706f0\n[ 6170.287962] Call Trace:\n[ 6170.287967]  <TASK>\n[ 6170.287973]  ? __warn+0x9f/0x1a0\n[ 6170.287986]  ? nf_tables_chain_destroy+0x1f7/0x220 [nf_tables]\n[ 6170.288092]  ? report_bug+0x1b1/0x1e0\n[ 6170.287986]  ? nf_tables_chain_destroy+0x1f7/0x220 [nf_tables]\n[ 6170.288092]  ? report_bug+0x1b1/0x1e0\n[ 6170.288104]  ? handle_bug+0x3c/0x70\n[ 6170.288112]  ? exc_invalid_op+0x17/0x40\n[ 6170.288120]  ? asm_exc_invalid_op+0x1a/0x20\n[ 6170.288132]  ? nf_tables_chain_destroy+0x2b/0x220 [nf_tables]\n[ 6170.288243]  ? nf_tables_chain_destroy+0x1f7/0x220 [nf_tables]\n[ 6170.288366]  ? nf_tables_chain_destroy+0x2b/0x220 [nf_tables]\n[ 6170.288483]  nf_tables_trans_destroy_work+0x588/0x590 [nf_tables]",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -40,8 +45,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-401"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:19Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-rqgx-53jr-xx5j/GHSA-rqgx-53jr-xx5j.json b/advisories/unreviewed/2024/05/GHSA-rqgx-53jr-xx5j/GHSA-rqgx-53jr-xx5j.json
index fd03f783254..627f1100165 100644
--- a/advisories/unreviewed/2024/05/GHSA-rqgx-53jr-xx5j/GHSA-rqgx-53jr-xx5j.json
+++ b/advisories/unreviewed/2024/05/GHSA-rqgx-53jr-xx5j/GHSA-rqgx-53jr-xx5j.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-rqgx-53jr-xx5j",
-  "modified": "2024-06-27T15:30:38Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26969"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: qcom: gcc-ipq8074: fix terminating of frequency table arrays\n\nThe frequency table arrays are supposed to be terminated with an\nempty element. Add such entry to the end of the arrays where it\nis missing in order to avoid possible out-of-bound access when\nthe table is traversed by functions like qcom_find_freq() or\nqcom_find_freq_floor().\n\nOnly compile tested.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -60,8 +65,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-129"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:13Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-vf44-3g39-fv4r/GHSA-vf44-3g39-fv4r.json b/advisories/unreviewed/2024/05/GHSA-vf44-3g39-fv4r/GHSA-vf44-3g39-fv4r.json
index d229c9e519e..fc7d18eb395 100644
--- a/advisories/unreviewed/2024/05/GHSA-vf44-3g39-fv4r/GHSA-vf44-3g39-fv4r.json
+++ b/advisories/unreviewed/2024/05/GHSA-vf44-3g39-fv4r/GHSA-vf44-3g39-fv4r.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-vf44-3g39-fv4r",
-  "modified": "2024-05-03T03:30:47Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:43Z",
   "aliases": [
     "CVE-2024-27010"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Fix mirred deadlock on device recursion\n\nWhen the mirred action is used on a classful egress qdisc and a packet is\nmirrored or redirected to self we hit a qdisc lock deadlock.\nSee trace below.\n\n[..... other info removed for brevity....]\n[   82.890906]\n[   82.890906] ============================================\n[   82.890906] WARNING: possible recursive locking detected\n[   82.890906] 6.8.0-05205-g77fadd89fe2d-dirty #213 Tainted: G        W\n[   82.890906] --------------------------------------------\n[   82.890906] ping/418 is trying to acquire lock:\n[   82.890906] ffff888006994110 (&sch->q.lock){+.-.}-{3:3}, at:\n__dev_queue_xmit+0x1778/0x3550\n[   82.890906]\n[   82.890906] but task is already holding lock:\n[   82.890906] ffff888006994110 (&sch->q.lock){+.-.}-{3:3}, at:\n__dev_queue_xmit+0x1778/0x3550\n[   82.890906]\n[   82.890906] other info that might help us debug this:\n[   82.890906]  Possible unsafe locking scenario:\n[   82.890906]\n[   82.890906]        CPU0\n[   82.890906]        ----\n[   82.890906]   lock(&sch->q.lock);\n[   82.890906]   lock(&sch->q.lock);\n[   82.890906]\n[   82.890906]  *** DEADLOCK ***\n[   82.890906]\n[..... other info removed for brevity....]\n\nExample setup (eth0->eth0) to recreate\ntc qdisc add dev eth0 root handle 1: htb default 30\ntc filter add dev eth0 handle 1: protocol ip prio 2 matchall \\\n     action mirred egress redirect dev eth0\n\nAnother example(eth0->eth1->eth0) to recreate\ntc qdisc add dev eth0 root handle 1: htb default 30\ntc filter add dev eth0 handle 1: protocol ip prio 2 matchall \\\n     action mirred egress redirect dev eth1\n\ntc qdisc add dev eth1 root handle 1: htb default 30\ntc filter add dev eth1 handle 1: protocol ip prio 2 matchall \\\n     action mirred egress redirect dev eth0\n\nWe fix this by adding an owner field (CPU id) to struct Qdisc set after\nroot qdisc is entered. When the softirq enters it a second time, if the\nqdisc owner is the same CPU, the packet is dropped to break the loop.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -36,8 +41,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-667"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:19Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-vxff-46qf-f9jx/GHSA-vxff-46qf-f9jx.json b/advisories/unreviewed/2024/05/GHSA-vxff-46qf-f9jx/GHSA-vxff-46qf-f9jx.json
index 3e27734cbd6..26f3a4e18d3 100644
--- a/advisories/unreviewed/2024/05/GHSA-vxff-46qf-f9jx/GHSA-vxff-46qf-f9jx.json
+++ b/advisories/unreviewed/2024/05/GHSA-vxff-46qf-f9jx/GHSA-vxff-46qf-f9jx.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-vxff-46qf-f9jx",
-  "modified": "2024-05-03T03:30:46Z",
+  "modified": "2024-12-23T15:30:46Z",
   "published": "2024-05-01T06:31:42Z",
   "aliases": [
     "CVE-2024-26983"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbootconfig: use memblock_free_late to free xbc memory to buddy\n\nOn the time to free xbc memory in xbc_exit(), memblock may has handed\nover memory to buddy allocator. So it doesn't make sense to free memory\nback to memblock. memblock_free() called by xbc_exit() even causes UAF bugs\non architectures with CONFIG_ARCH_KEEP_MEMBLOCK disabled like x86.\nFollowing KASAN logs shows this case.\n\nThis patch fixes the xbc memory free problem by calling memblock_free()\nin early xbc init error rewind path and calling memblock_free_late() in\nxbc exit path to free memory to buddy allocator.\n\n[    9.410890] ==================================================================\n[    9.418962] BUG: KASAN: use-after-free in memblock_isolate_range+0x12d/0x260\n[    9.426850] Read of size 8 at addr ffff88845dd30000 by task swapper/0/1\n\n[    9.435901] CPU: 9 PID: 1 Comm: swapper/0 Tainted: G     U             6.9.0-rc3-00208-g586b5dfb51b9 #5\n[    9.446403] Hardware name: Intel Corporation RPLP LP5 (CPU:RaptorLake)/RPLP LP5 (ID:13), BIOS IRPPN02.01.01.00.00.19.015.D-00000000 Dec 28 2023\n[    9.460789] Call Trace:\n[    9.463518]  <TASK>\n[    9.465859]  dump_stack_lvl+0x53/0x70\n[    9.469949]  print_report+0xce/0x610\n[    9.473944]  ? __virt_addr_valid+0xf5/0x1b0\n[    9.478619]  ? memblock_isolate_range+0x12d/0x260\n[    9.483877]  kasan_report+0xc6/0x100\n[    9.487870]  ? memblock_isolate_range+0x12d/0x260\n[    9.493125]  memblock_isolate_range+0x12d/0x260\n[    9.498187]  memblock_phys_free+0xb4/0x160\n[    9.502762]  ? __pfx_memblock_phys_free+0x10/0x10\n[    9.508021]  ? mutex_unlock+0x7e/0xd0\n[    9.512111]  ? __pfx_mutex_unlock+0x10/0x10\n[    9.516786]  ? kernel_init_freeable+0x2d4/0x430\n[    9.521850]  ? __pfx_kernel_init+0x10/0x10\n[    9.526426]  xbc_exit+0x17/0x70\n[    9.529935]  kernel_init+0x38/0x1e0\n[    9.533829]  ? _raw_spin_unlock_irq+0xd/0x30\n[    9.538601]  ret_from_fork+0x2c/0x50\n[    9.542596]  ? __pfx_kernel_init+0x10/0x10\n[    9.547170]  ret_from_fork_asm+0x1a/0x30\n[    9.551552]  </TASK>\n\n[    9.555649] The buggy address belongs to the physical page:\n[    9.561875] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x45dd30\n[    9.570821] flags: 0x200000000000000(node=0|zone=2)\n[    9.576271] page_type: 0xffffffff()\n[    9.580167] raw: 0200000000000000 ffffea0011774c48 ffffea0012ba1848 0000000000000000\n[    9.588823] raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000\n[    9.597476] page dumped because: kasan: bad access detected\n\n[    9.605362] Memory state around the buggy address:\n[    9.610714]  ffff88845dd2ff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n[    9.618786]  ffff88845dd2ff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n[    9.626857] >ffff88845dd30000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[    9.634930]                    ^\n[    9.638534]  ffff88845dd30080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[    9.646605]  ffff88845dd30100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[    9.654675] ==================================================================",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -44,8 +49,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-416"
+    ],
+    "severity": "HIGH",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T06:15:15Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-wr42-h5m2-qmx6/GHSA-wr42-h5m2-qmx6.json b/advisories/unreviewed/2024/05/GHSA-wr42-h5m2-qmx6/GHSA-wr42-h5m2-qmx6.json
index ed32b5fce59..0421732cedd 100644
--- a/advisories/unreviewed/2024/05/GHSA-wr42-h5m2-qmx6/GHSA-wr42-h5m2-qmx6.json
+++ b/advisories/unreviewed/2024/05/GHSA-wr42-h5m2-qmx6/GHSA-wr42-h5m2-qmx6.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-wr42-h5m2-qmx6",
-  "modified": "2024-05-01T15:30:36Z",
+  "modified": "2024-12-23T15:30:47Z",
   "published": "2024-05-01T15:30:36Z",
   "aliases": [
     "CVE-2024-27071"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbacklight: hx8357: Fix potential NULL pointer dereference\n\nThe \"im\" pins are optional. Add missing check in the hx8357_probe().",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -24,8 +29,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-476"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-01T13:15:51Z"
diff --git a/advisories/unreviewed/2024/12/GHSA-f27q-fqv4-577w/GHSA-f27q-fqv4-577w.json b/advisories/unreviewed/2024/12/GHSA-f27q-fqv4-577w/GHSA-f27q-fqv4-577w.json
new file mode 100644
index 00000000000..87d013d794e
--- /dev/null
+++ b/advisories/unreviewed/2024/12/GHSA-f27q-fqv4-577w/GHSA-f27q-fqv4-577w.json
@@ -0,0 +1,36 @@
+{
+  "schema_version": "1.4.0",
+  "id": "GHSA-f27q-fqv4-577w",
+  "modified": "2024-12-23T15:30:47Z",
+  "published": "2024-12-23T15:30:47Z",
+  "aliases": [
+    "CVE-2024-55539"
+  ],
+  "details": "Weak algorithm used to sign RPM package. The following products are affected: Acronis Cyber Protect Cloud Agent (Linux) before build 39185.",
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N"
+    }
+  ],
+  "affected": [],
+  "references": [
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-55539"
+    },
+    {
+      "type": "WEB",
+      "url": "https://security-advisory.acronis.com/advisories/SEC-5825"
+    }
+  ],
+  "database_specific": {
+    "cwe_ids": [
+      "CWE-327"
+    ],
+    "severity": "LOW",
+    "github_reviewed": false,
+    "github_reviewed_at": null,
+    "nvd_published_at": "2024-12-23T14:15:06Z"
+  }
+}
\ No newline at end of file
diff --git a/advisories/unreviewed/2024/12/GHSA-j9gp-2c97-g73x/GHSA-j9gp-2c97-g73x.json b/advisories/unreviewed/2024/12/GHSA-j9gp-2c97-g73x/GHSA-j9gp-2c97-g73x.json
new file mode 100644
index 00000000000..db2d092bf2f
--- /dev/null
+++ b/advisories/unreviewed/2024/12/GHSA-j9gp-2c97-g73x/GHSA-j9gp-2c97-g73x.json
@@ -0,0 +1,36 @@
+{
+  "schema_version": "1.4.0",
+  "id": "GHSA-j9gp-2c97-g73x",
+  "modified": "2024-12-23T15:30:47Z",
+  "published": "2024-12-23T15:30:47Z",
+  "aliases": [
+    "CVE-2024-12903"
+  ],
+  "details": "Incorrect default permissions vulnerability in Evoko Home, affecting version 2.4.2 to 2.7.4. A non-admin user could exploit weak file and folder permissions to escalate privileges, execute arbitrary code and maintain persistence on the compromised machine. It has been identified that full control permissions exist on the ‘Everyone’ group (i.e. any user who has local access to the operating system regardless of their privileges).",
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
+    }
+  ],
+  "affected": [],
+  "references": [
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-12903"
+    },
+    {
+      "type": "WEB",
+      "url": "https://www.incibe.es/en/incibe-cert/notices/aviso/incorrect-default-permissions-biamp-evoko-home"
+    }
+  ],
+  "database_specific": {
+    "cwe_ids": [
+      "CWE-276"
+    ],
+    "severity": "HIGH",
+    "github_reviewed": false,
+    "github_reviewed_at": null,
+    "nvd_published_at": "2024-12-23T13:15:06Z"
+  }
+}
\ No newline at end of file