diff --git a/advisories/unreviewed/2023/06/GHSA-89fh-5c8q-jj65/GHSA-89fh-5c8q-jj65.json b/advisories/unreviewed/2023/06/GHSA-89fh-5c8q-jj65/GHSA-89fh-5c8q-jj65.json
index 41a0dd99267..d2753fdd628 100644
--- a/advisories/unreviewed/2023/06/GHSA-89fh-5c8q-jj65/GHSA-89fh-5c8q-jj65.json
+++ b/advisories/unreviewed/2023/06/GHSA-89fh-5c8q-jj65/GHSA-89fh-5c8q-jj65.json
@@ -25,7 +25,9 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
+    "cwe_ids": [
+      "CWE-404"
+    ],
     "severity": "HIGH",
     "github_reviewed": false,
     "github_reviewed_at": null,
diff --git a/advisories/unreviewed/2024/05/GHSA-2qgr-37h8-x3w9/GHSA-2qgr-37h8-x3w9.json b/advisories/unreviewed/2024/05/GHSA-2qgr-37h8-x3w9/GHSA-2qgr-37h8-x3w9.json
index 3001b405fd3..c5438bd0a2c 100644
--- a/advisories/unreviewed/2024/05/GHSA-2qgr-37h8-x3w9/GHSA-2qgr-37h8-x3w9.json
+++ b/advisories/unreviewed/2024/05/GHSA-2qgr-37h8-x3w9/GHSA-2qgr-37h8-x3w9.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-2qgr-37h8-x3w9",
-  "modified": "2024-05-21T15:31:41Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:41Z",
   "aliases": [
     "CVE-2021-47260"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix a potential NULL dereference in nfs_get_client()\n\nNone of the callers are expecting NULL returns from nfs_get_client() so\nthis code will lead to an Oops.  It's better to return an error\npointer.  I expect that this is dead code so hopefully no one is\naffected.",
-  "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": [
     {
@@ -48,8 +53,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-21T15:15:14Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-3qvj-8qwq-5jxj/GHSA-3qvj-8qwq-5jxj.json b/advisories/unreviewed/2024/05/GHSA-3qvj-8qwq-5jxj/GHSA-3qvj-8qwq-5jxj.json
index 873d5f3fafc..3c100e517f1 100644
--- a/advisories/unreviewed/2024/05/GHSA-3qvj-8qwq-5jxj/GHSA-3qvj-8qwq-5jxj.json
+++ b/advisories/unreviewed/2024/05/GHSA-3qvj-8qwq-5jxj/GHSA-3qvj-8qwq-5jxj.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-3qvj-8qwq-5jxj",
-  "modified": "2024-05-21T15:31:43Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:43Z",
   "aliases": [
     "CVE-2021-47330"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ntty: serial: 8250: serial_cs: Fix a memory leak in error handling path\n\nIn the probe function, if the final 'serial_config()' fails, 'info' is\nleaking.\n\nAdd a resource handling path to free this memory.",
-  "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-21T15:15:19Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-4xq8-m4f5-h82h/GHSA-4xq8-m4f5-h82h.json b/advisories/unreviewed/2024/05/GHSA-4xq8-m4f5-h82h/GHSA-4xq8-m4f5-h82h.json
index ffe7d7e78d2..70a637ce0ce 100644
--- a/advisories/unreviewed/2024/05/GHSA-4xq8-m4f5-h82h/GHSA-4xq8-m4f5-h82h.json
+++ b/advisories/unreviewed/2024/05/GHSA-4xq8-m4f5-h82h/GHSA-4xq8-m4f5-h82h.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-4xq8-m4f5-h82h",
-  "modified": "2024-05-21T15:31:41Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:41Z",
   "aliases": [
     "CVE-2021-47270"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: fix various gadgets null ptr deref on 10gbps cabling.\n\nThis avoids a null pointer dereference in\nf_{ecm,eem,hid,loopback,printer,rndis,serial,sourcesink,subset,tcm}\nby simply reusing the 5gbps config for 10gbps.",
-  "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": [
     {
@@ -44,8 +49,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-21T15:15:15Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-5vvx-6299-h82w/GHSA-5vvx-6299-h82w.json b/advisories/unreviewed/2024/05/GHSA-5vvx-6299-h82w/GHSA-5vvx-6299-h82w.json
index db98035dcc4..d08ca90a90b 100644
--- a/advisories/unreviewed/2024/05/GHSA-5vvx-6299-h82w/GHSA-5vvx-6299-h82w.json
+++ b/advisories/unreviewed/2024/05/GHSA-5vvx-6299-h82w/GHSA-5vvx-6299-h82w.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-5vvx-6299-h82w",
-  "modified": "2024-05-21T15:31:43Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:43Z",
   "aliases": [
     "CVE-2021-47337"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: Fix bad pointer dereference when ehandler kthread is invalid\n\nCommit 66a834d09293 (\"scsi: core: Fix error handling of scsi_host_alloc()\")\nchanged the allocation logic to call put_device() to perform host cleanup\nwith the assumption that IDA removal and stopping the kthread would\nproperly be performed in scsi_host_dev_release(). However, in the unlikely\ncase that the error handler thread fails to spawn, shost->ehandler is set\nto ERR_PTR(-ENOMEM).\n\nThe error handler cleanup code in scsi_host_dev_release() will call\nkthread_stop() if shost->ehandler != NULL which will always be the case\nwhether the kthread was successfully spawned or not. In the case that it\nfailed to spawn this has the nasty side effect of trying to dereference an\ninvalid pointer when kthread_stop() is called. The following splat provides\nan example of this behavior in the wild:\n\nscsi host11: error handler thread failed to spawn, error = -4\nKernel attempted to read user page (10c) - exploit attempt? (uid: 0)\nBUG: Kernel NULL pointer dereference on read at 0x0000010c\nFaulting instruction address: 0xc00000000818e9a8\nOops: Kernel access of bad area, sig: 11 [#1]\nLE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries\nModules linked in: ibmvscsi(+) scsi_transport_srp dm_multipath dm_mirror dm_region\n hash dm_log dm_mod fuse overlay squashfs loop\nCPU: 12 PID: 274 Comm: systemd-udevd Not tainted 5.13.0-rc7 #1\nNIP:  c00000000818e9a8 LR: c0000000089846e8 CTR: 0000000000007ee8\nREGS: c000000037d12ea0 TRAP: 0300   Not tainted  (5.13.0-rc7)\nMSR:  800000000280b033 <SF,VEC,VSX,EE,FP,ME,IR,DR,RI,LE>  CR: 28228228\nXER: 20040001\nCFAR: c0000000089846e4 DAR: 000000000000010c DSISR: 40000000 IRQMASK: 0\nGPR00: c0000000089846e8 c000000037d13140 c000000009cc1100 fffffffffffffffc\nGPR04: 0000000000000001 0000000000000000 0000000000000000 c000000037dc0000\nGPR08: 0000000000000000 c000000037dc0000 0000000000000001 00000000fffff7ff\nGPR12: 0000000000008000 c00000000a049000 c000000037d13d00 000000011134d5a0\nGPR16: 0000000000001740 c0080000190d0000 c0080000190d1740 c000000009129288\nGPR20: c000000037d13bc0 0000000000000001 c000000037d13bc0 c0080000190b7898\nGPR24: c0080000190b7708 0000000000000000 c000000033bb2c48 0000000000000000\nGPR28: c000000046b28280 0000000000000000 000000000000010c fffffffffffffffc\nNIP [c00000000818e9a8] kthread_stop+0x38/0x230\nLR [c0000000089846e8] scsi_host_dev_release+0x98/0x160\nCall Trace:\n[c000000033bb2c48] 0xc000000033bb2c48 (unreliable)\n[c0000000089846e8] scsi_host_dev_release+0x98/0x160\n[c00000000891e960] device_release+0x60/0x100\n[c0000000087e55c4] kobject_release+0x84/0x210\n[c00000000891ec78] put_device+0x28/0x40\n[c000000008984ea4] scsi_host_alloc+0x314/0x430\n[c0080000190b38bc] ibmvscsi_probe+0x54/0xad0 [ibmvscsi]\n[c000000008110104] vio_bus_probe+0xa4/0x4b0\n[c00000000892a860] really_probe+0x140/0x680\n[c00000000892aefc] driver_probe_device+0x15c/0x200\n[c00000000892b63c] device_driver_attach+0xcc/0xe0\n[c00000000892b740] __driver_attach+0xf0/0x200\n[c000000008926f28] bus_for_each_dev+0xa8/0x130\n[c000000008929ce4] driver_attach+0x34/0x50\n[c000000008928fc0] bus_add_driver+0x1b0/0x300\n[c00000000892c798] driver_register+0x98/0x1a0\n[c00000000810eb60] __vio_register_driver+0x80/0xe0\n[c0080000190b4a30] ibmvscsi_module_init+0x9c/0xdc [ibmvscsi]\n[c0000000080121d0] do_one_initcall+0x60/0x2d0\n[c000000008261abc] do_init_module+0x7c/0x320\n[c000000008265700] load_module+0x2350/0x25b0\n[c000000008265cb4] __do_sys_finit_module+0xd4/0x160\n[c000000008031110] system_call_exception+0x150/0x2d0\n[c00000000800d35c] system_call_common+0xec/0x278\n\nFix this be nulling shost->ehandler when the kthread fails to spawn.",
-  "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": [
     {
@@ -48,8 +53,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-21T15:15:20Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-836m-cmjj-qv5g/GHSA-836m-cmjj-qv5g.json b/advisories/unreviewed/2024/05/GHSA-836m-cmjj-qv5g/GHSA-836m-cmjj-qv5g.json
index 6344fd015fe..2028f926dce 100644
--- a/advisories/unreviewed/2024/05/GHSA-836m-cmjj-qv5g/GHSA-836m-cmjj-qv5g.json
+++ b/advisories/unreviewed/2024/05/GHSA-836m-cmjj-qv5g/GHSA-836m-cmjj-qv5g.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-836m-cmjj-qv5g",
-  "modified": "2024-05-21T15:31:43Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:43Z",
   "aliases": [
     "CVE-2021-47331"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: common: usb-conn-gpio: fix NULL pointer dereference of charger\n\nWhen power on system with OTG cable, IDDIG's interrupt arises before\nthe charger registration, it will cause a NULL pointer dereference,\nfix the issue by registering the power supply before requesting\nIDDIG/VBUS irq.",
-  "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-21T15:15:20Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-9rr2-xw5v-w787/GHSA-9rr2-xw5v-w787.json b/advisories/unreviewed/2024/05/GHSA-9rr2-xw5v-w787/GHSA-9rr2-xw5v-w787.json
index 39153ac4623..fc9009a15d6 100644
--- a/advisories/unreviewed/2024/05/GHSA-9rr2-xw5v-w787/GHSA-9rr2-xw5v-w787.json
+++ b/advisories/unreviewed/2024/05/GHSA-9rr2-xw5v-w787/GHSA-9rr2-xw5v-w787.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-9rr2-xw5v-w787",
-  "modified": "2024-05-21T15:31:44Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:44Z",
   "aliases": [
     "CVE-2021-47359"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncifs: Fix soft lockup during fsstress\n\nBelow traces are observed during fsstress and system got hung.\n[  130.698396] watchdog: BUG: soft lockup - CPU#6 stuck for 26s!",
-  "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-667"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-21T15:15:22Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-fj34-p4r2-ghh5/GHSA-fj34-p4r2-ghh5.json b/advisories/unreviewed/2024/05/GHSA-fj34-p4r2-ghh5/GHSA-fj34-p4r2-ghh5.json
index abacad0e70d..0dfa3d8c887 100644
--- a/advisories/unreviewed/2024/05/GHSA-fj34-p4r2-ghh5/GHSA-fj34-p4r2-ghh5.json
+++ b/advisories/unreviewed/2024/05/GHSA-fj34-p4r2-ghh5/GHSA-fj34-p4r2-ghh5.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-fj34-p4r2-ghh5",
-  "modified": "2024-05-21T15:31:41Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:41Z",
   "aliases": [
     "CVE-2021-47281"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: seq: Fix race of snd_seq_timer_open()\n\nThe timer instance per queue is exclusive, and snd_seq_timer_open()\nshould have managed the concurrent accesses.  It looks as if it's\nchecking the already existing timer instance at the beginning, but\nit's not right, because there is no protection, hence any later\nconcurrent call of snd_seq_timer_open() may override the timer\ninstance easily.  This may result in UAF, as the leftover timer\ninstance can keep running while the queue itself gets closed, as\nspotted by syzkaller recently.\n\nFor avoiding the race, add a proper check at the assignment of\ntmr->timeri again, and return -EBUSY if it's been already registered.",
-  "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": [
     {
@@ -28,8 +33,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-21T15:15:16Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-g2fc-vv42-p4pc/GHSA-g2fc-vv42-p4pc.json b/advisories/unreviewed/2024/05/GHSA-g2fc-vv42-p4pc/GHSA-g2fc-vv42-p4pc.json
index c296977550a..c4b46473a31 100644
--- a/advisories/unreviewed/2024/05/GHSA-g2fc-vv42-p4pc/GHSA-g2fc-vv42-p4pc.json
+++ b/advisories/unreviewed/2024/05/GHSA-g2fc-vv42-p4pc/GHSA-g2fc-vv42-p4pc.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-g2fc-vv42-p4pc",
-  "modified": "2024-05-21T15:31:44Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:44Z",
   "aliases": [
     "CVE-2021-47399"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup\n\nThe ixgbe driver currently generates a NULL pointer dereference with\nsome machine (online cpus < 63). This is due to the fact that the\nmaximum value of num_xdp_queues is nr_cpu_ids. Code is in\n\"ixgbe_set_rss_queues\"\".\n\nHere's how the problem repeats itself:\nSome machine (online cpus < 63), And user set num_queues to 63 through\nethtool. Code is in the \"ixgbe_set_channels\",\n\tadapter->ring_feature[RING_F_FDIR].limit = count;\n\nIt becomes 63.\n\nWhen user use xdp, \"ixgbe_set_rss_queues\" will set queues num.\n\tadapter->num_rx_queues = rss_i;\n\tadapter->num_tx_queues = rss_i;\n\tadapter->num_xdp_queues = ixgbe_xdp_queues(adapter);\n\nAnd rss_i's value is from\n\tf = &adapter->ring_feature[RING_F_FDIR];\n\trss_i = f->indices = f->limit;\n\nSo \"num_rx_queues\" > \"num_xdp_queues\", when run to \"ixgbe_xdp_setup\",\n\tfor (i = 0; i < adapter->num_rx_queues; i++)\n\t\tif (adapter->xdp_ring[i]->xsk_umem)\n\nIt leads to panic.\n\nCall trace:\n[exception RIP: ixgbe_xdp+368]\nRIP: ffffffffc02a76a0  RSP: ffff9fe16202f8d0  RFLAGS: 00010297\nRAX: 0000000000000000  RBX: 0000000000000020  RCX: 0000000000000000\nRDX: 0000000000000000  RSI: 000000000000001c  RDI: ffffffffa94ead90\nRBP: ffff92f8f24c0c18   R8: 0000000000000000   R9: 0000000000000000\nR10: ffff9fe16202f830  R11: 0000000000000000  R12: ffff92f8f24c0000\nR13: ffff9fe16202fc01  R14: 000000000000000a  R15: ffffffffc02a7530\nORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n 7 [ffff9fe16202f8f0] dev_xdp_install at ffffffffa89fbbcc\n 8 [ffff9fe16202f920] dev_change_xdp_fd at ffffffffa8a08808\n 9 [ffff9fe16202f960] do_setlink at ffffffffa8a20235\n10 [ffff9fe16202fa88] rtnl_setlink at ffffffffa8a20384\n11 [ffff9fe16202fc78] rtnetlink_rcv_msg at ffffffffa8a1a8dd\n12 [ffff9fe16202fcf0] netlink_rcv_skb at ffffffffa8a717eb\n13 [ffff9fe16202fd40] netlink_unicast at ffffffffa8a70f88\n14 [ffff9fe16202fd80] netlink_sendmsg at ffffffffa8a71319\n15 [ffff9fe16202fdf0] sock_sendmsg at ffffffffa89df290\n16 [ffff9fe16202fe08] __sys_sendto at ffffffffa89e19c8\n17 [ffff9fe16202ff30] __x64_sys_sendto at ffffffffa89e1a64\n18 [ffff9fe16202ff38] do_syscall_64 at ffffffffa84042b9\n19 [ffff9fe16202ff50] entry_SYSCALL_64_after_hwframe at ffffffffa8c0008c\n\nSo I fix ixgbe_max_channels so that it will not allow a setting of queues\nto be higher than the num_online_cpus(). And when run to ixgbe_xdp_setup,\ntake the smaller value of num_rx_queues and num_xdp_queues.",
-  "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-21T15:15:25Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-hm5p-668j-x4q6/GHSA-hm5p-668j-x4q6.json b/advisories/unreviewed/2024/05/GHSA-hm5p-668j-x4q6/GHSA-hm5p-668j-x4q6.json
index 9a1fa2381be..e56b254d915 100644
--- a/advisories/unreviewed/2024/05/GHSA-hm5p-668j-x4q6/GHSA-hm5p-668j-x4q6.json
+++ b/advisories/unreviewed/2024/05/GHSA-hm5p-668j-x4q6/GHSA-hm5p-668j-x4q6.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-hm5p-668j-x4q6",
-  "modified": "2024-05-21T15:31:43Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:43Z",
   "aliases": [
     "CVE-2021-47344"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: zr364xx: fix memory leak in zr364xx_start_readpipe\n\nsyzbot reported memory leak in zr364xx driver.\nThe problem was in non-freed urb in case of\nusb_submit_urb() fail.\n\nbacktrace:\n  [<ffffffff82baedf6>] kmalloc include/linux/slab.h:561 [inline]\n  [<ffffffff82baedf6>] usb_alloc_urb+0x66/0xe0 drivers/usb/core/urb.c:74\n  [<ffffffff82f7cce8>] zr364xx_start_readpipe+0x78/0x130 drivers/media/usb/zr364xx/zr364xx.c:1022\n  [<ffffffff84251dfc>] zr364xx_board_init drivers/media/usb/zr364xx/zr364xx.c:1383 [inline]\n  [<ffffffff84251dfc>] zr364xx_probe+0x6a3/0x851 drivers/media/usb/zr364xx/zr364xx.c:1516\n  [<ffffffff82bb6507>] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396\n  [<ffffffff826018a9>] really_probe+0x159/0x500 drivers/base/dd.c:576",
-  "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-21T15:15:21Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-m2r9-3c4r-qv68/GHSA-m2r9-3c4r-qv68.json b/advisories/unreviewed/2024/05/GHSA-m2r9-3c4r-qv68/GHSA-m2r9-3c4r-qv68.json
index 37829aa23d0..9715df401b0 100644
--- a/advisories/unreviewed/2024/05/GHSA-m2r9-3c4r-qv68/GHSA-m2r9-3c4r-qv68.json
+++ b/advisories/unreviewed/2024/05/GHSA-m2r9-3c4r-qv68/GHSA-m2r9-3c4r-qv68.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-m2r9-3c4r-qv68",
-  "modified": "2024-05-21T15:31:43Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:43Z",
   "aliases": [
     "CVE-2021-47338"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfbmem: Do not delete the mode that is still in use\n\nThe execution of fb_delete_videomode() is not based on the result of the\nprevious fbcon_mode_deleted(). As a result, the mode is directly deleted,\nregardless of whether it is still in use, which may cause UAF.\n\n==================================================================\nBUG: KASAN: use-after-free in fb_mode_is_equal+0x36e/0x5e0 \\\ndrivers/video/fbdev/core/modedb.c:924\nRead of size 4 at addr ffff88807e0ddb1c by task syz-executor.0/18962\n\nCPU: 2 PID: 18962 Comm: syz-executor.0 Not tainted 5.10.45-rc1+ #3\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ...\nCall Trace:\n __dump_stack lib/dump_stack.c:77 [inline]\n dump_stack+0x137/0x1be lib/dump_stack.c:118\n print_address_description+0x6c/0x640 mm/kasan/report.c:385\n __kasan_report mm/kasan/report.c:545 [inline]\n kasan_report+0x13d/0x1e0 mm/kasan/report.c:562\n fb_mode_is_equal+0x36e/0x5e0 drivers/video/fbdev/core/modedb.c:924\n fbcon_mode_deleted+0x16a/0x220 drivers/video/fbdev/core/fbcon.c:2746\n fb_set_var+0x1e1/0xdb0 drivers/video/fbdev/core/fbmem.c:975\n do_fb_ioctl+0x4d9/0x6e0 drivers/video/fbdev/core/fbmem.c:1108\n vfs_ioctl fs/ioctl.c:48 [inline]\n __do_sys_ioctl fs/ioctl.c:753 [inline]\n __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:739\n do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46\n entry_SYSCALL_64_after_hwframe+0x44/0xa9\n\nFreed by task 18960:\n kasan_save_stack mm/kasan/common.c:48 [inline]\n kasan_set_track+0x3d/0x70 mm/kasan/common.c:56\n kasan_set_free_info+0x17/0x30 mm/kasan/generic.c:355\n __kasan_slab_free+0x108/0x140 mm/kasan/common.c:422\n slab_free_hook mm/slub.c:1541 [inline]\n slab_free_freelist_hook+0xd6/0x1a0 mm/slub.c:1574\n slab_free mm/slub.c:3139 [inline]\n kfree+0xca/0x3d0 mm/slub.c:4121\n fb_delete_videomode+0x56a/0x820 drivers/video/fbdev/core/modedb.c:1104\n fb_set_var+0x1f3/0xdb0 drivers/video/fbdev/core/fbmem.c:978\n do_fb_ioctl+0x4d9/0x6e0 drivers/video/fbdev/core/fbmem.c:1108\n vfs_ioctl fs/ioctl.c:48 [inline]\n __do_sys_ioctl fs/ioctl.c:753 [inline]\n __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:739\n do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46\n entry_SYSCALL_64_after_hwframe+0x44/0xa9",
-  "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": [
     {
@@ -36,8 +41,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-21T15:15:20Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-pmrx-2gv3-hv52/GHSA-pmrx-2gv3-hv52.json b/advisories/unreviewed/2024/05/GHSA-pmrx-2gv3-hv52/GHSA-pmrx-2gv3-hv52.json
index 2b1fe9d9010..932e8b86c1e 100644
--- a/advisories/unreviewed/2024/05/GHSA-pmrx-2gv3-hv52/GHSA-pmrx-2gv3-hv52.json
+++ b/advisories/unreviewed/2024/05/GHSA-pmrx-2gv3-hv52/GHSA-pmrx-2gv3-hv52.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-pmrx-2gv3-hv52",
-  "modified": "2024-05-21T15:31:43Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:43Z",
   "aliases": [
     "CVE-2021-47332"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usx2y: Don't call free_pages_exact() with NULL address\n\nUnlike some other functions, we can't pass NULL pointer to\nfree_pages_exact().  Add a proper NULL check for avoiding possible\nOops.",
-  "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-476"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-21T15:15:20Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-pv65-xqrg-hc85/GHSA-pv65-xqrg-hc85.json b/advisories/unreviewed/2024/05/GHSA-pv65-xqrg-hc85/GHSA-pv65-xqrg-hc85.json
index 94b9b90dc5c..1bd6d53fc16 100644
--- a/advisories/unreviewed/2024/05/GHSA-pv65-xqrg-hc85/GHSA-pv65-xqrg-hc85.json
+++ b/advisories/unreviewed/2024/05/GHSA-pv65-xqrg-hc85/GHSA-pv65-xqrg-hc85.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-pv65-xqrg-hc85",
-  "modified": "2024-05-21T15:31:43Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:43Z",
   "aliases": [
     "CVE-2021-47345"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cma: Fix rdma_resolve_route() memory leak\n\nFix a memory leak when \"mda_resolve_route() is called more than once on\nthe same \"rdma_cm_id\".\n\nThis is possible if cma_query_handler() triggers the\nRDMA_CM_EVENT_ROUTE_ERROR flow which puts the state machine back and\nallows rdma_resolve_route() to be called again.",
-  "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-21T15:15:21Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-pwqm-5jrg-2v3g/GHSA-pwqm-5jrg-2v3g.json b/advisories/unreviewed/2024/05/GHSA-pwqm-5jrg-2v3g/GHSA-pwqm-5jrg-2v3g.json
index c92273b888a..0e54955c4c4 100644
--- a/advisories/unreviewed/2024/05/GHSA-pwqm-5jrg-2v3g/GHSA-pwqm-5jrg-2v3g.json
+++ b/advisories/unreviewed/2024/05/GHSA-pwqm-5jrg-2v3g/GHSA-pwqm-5jrg-2v3g.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-pwqm-5jrg-2v3g",
-  "modified": "2024-05-21T15:31:42Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:42Z",
   "aliases": [
     "CVE-2021-47320"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfs: fix acl memory leak of posix_acl_create()\n\nWhen looking into another nfs xfstests report, I found acl and\ndefault_acl in nfs3_proc_create() and nfs3_proc_mknod() error\npaths are possibly leaked. Fix them in advance.",
-  "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-21T15:15:19Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-qp63-w47q-g9vj/GHSA-qp63-w47q-g9vj.json b/advisories/unreviewed/2024/05/GHSA-qp63-w47q-g9vj/GHSA-qp63-w47q-g9vj.json
index 2e15845f529..3765cfe4f80 100644
--- a/advisories/unreviewed/2024/05/GHSA-qp63-w47q-g9vj/GHSA-qp63-w47q-g9vj.json
+++ b/advisories/unreviewed/2024/05/GHSA-qp63-w47q-g9vj/GHSA-qp63-w47q-g9vj.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-qp63-w47q-g9vj",
-  "modified": "2024-05-21T15:31:41Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:41Z",
   "aliases": [
     "CVE-2021-47269"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: dwc3: ep0: fix NULL pointer exception\n\nThere is no validation of the index from dwc3_wIndex_to_dep() and we might\nbe referring a non-existing ep and trigger a NULL pointer exception. In\ncertain configurations we might use fewer eps and the index might wrongly\nindicate a larger ep index than existing.\n\nBy adding this validation from the patch we can actually report a wrong\nindex back to the caller.\n\nIn our usecase we are using a composite device on an older kernel, but\nupstream might use this fix also. Unfortunately, I cannot describe the\nhardware for others to reproduce the issue as it is a proprietary\nimplementation.\n\n[   82.958261] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a4\n[   82.966891] Mem abort info:\n[   82.969663]   ESR = 0x96000006\n[   82.972703]   Exception class = DABT (current EL), IL = 32 bits\n[   82.978603]   SET = 0, FnV = 0\n[   82.981642]   EA = 0, S1PTW = 0\n[   82.984765] Data abort info:\n[   82.987631]   ISV = 0, ISS = 0x00000006\n[   82.991449]   CM = 0, WnR = 0\n[   82.994409] user pgtable: 4k pages, 39-bit VAs, pgdp = 00000000c6210ccc\n[   83.000999] [00000000000000a4] pgd=0000000053aa5003, pud=0000000053aa5003, pmd=0000000000000000\n[   83.009685] Internal error: Oops: 96000006 [#1] PREEMPT SMP\n[   83.026433] Process irq/62-dwc3 (pid: 303, stack limit = 0x000000003985154c)\n[   83.033470] CPU: 0 PID: 303 Comm: irq/62-dwc3 Not tainted 4.19.124 #1\n[   83.044836] pstate: 60000085 (nZCv daIf -PAN -UAO)\n[   83.049628] pc : dwc3_ep0_handle_feature+0x414/0x43c\n[   83.054558] lr : dwc3_ep0_interrupt+0x3b4/0xc94\n\n...\n\n[   83.141788] Call trace:\n[   83.144227]  dwc3_ep0_handle_feature+0x414/0x43c\n[   83.148823]  dwc3_ep0_interrupt+0x3b4/0xc94\n[   83.181546] ---[ end trace aac6b5267d84c32f ]---",
-  "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": [
     {
@@ -48,8 +53,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-21T15:15:15Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-qxvg-qh99-hg66/GHSA-qxvg-qh99-hg66.json b/advisories/unreviewed/2024/05/GHSA-qxvg-qh99-hg66/GHSA-qxvg-qh99-hg66.json
index 4aa37d3da17..36f1296a5d1 100644
--- a/advisories/unreviewed/2024/05/GHSA-qxvg-qh99-hg66/GHSA-qxvg-qh99-hg66.json
+++ b/advisories/unreviewed/2024/05/GHSA-qxvg-qh99-hg66/GHSA-qxvg-qh99-hg66.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-qxvg-qh99-hg66",
-  "modified": "2024-05-21T15:31:41Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:41Z",
   "aliases": [
     "CVE-2021-47264"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: core: Fix Null-point-dereference in fmt_single_name()\n\nCheck the return value of devm_kstrdup() in case of\nNull-point-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": [
     {
@@ -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-21T15:15:15Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-rcjv-j3v6-r6cv/GHSA-rcjv-j3v6-r6cv.json b/advisories/unreviewed/2024/05/GHSA-rcjv-j3v6-r6cv/GHSA-rcjv-j3v6-r6cv.json
index 0b2217fb423..f0e26d58102 100644
--- a/advisories/unreviewed/2024/05/GHSA-rcjv-j3v6-r6cv/GHSA-rcjv-j3v6-r6cv.json
+++ b/advisories/unreviewed/2024/05/GHSA-rcjv-j3v6-r6cv/GHSA-rcjv-j3v6-r6cv.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-rcjv-j3v6-r6cv",
-  "modified": "2024-05-21T15:31:41Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:41Z",
   "aliases": [
     "CVE-2021-47280"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm: Fix use-after-free read in drm_getunique()\n\nThere is a time-of-check-to-time-of-use error in drm_getunique() due\nto retrieving file_priv->master prior to locking the device's master\nmutex.\n\nAn example can be seen in the crash report of the use-after-free error\nfound by Syzbot:\nhttps://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803\n\nIn the report, the master pointer was used after being freed. This is\nbecause another process had acquired the device's master mutex in\ndrm_setmaster_ioctl(), then overwrote fpriv->master in\ndrm_new_set_master(). The old value of fpriv->master was subsequently\nfreed before the mutex was unlocked.\n\nTo fix this, we lock the device's master mutex before retrieving the\npointer from from fpriv->master. This patch passes the Syzbot\nreproducer test.",
-  "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": [
     {
@@ -40,8 +45,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-21T15:15:16Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-v5r4-g8jp-rvxf/GHSA-v5r4-g8jp-rvxf.json b/advisories/unreviewed/2024/05/GHSA-v5r4-g8jp-rvxf/GHSA-v5r4-g8jp-rvxf.json
index 206972bd8a8..5cf197817dd 100644
--- a/advisories/unreviewed/2024/05/GHSA-v5r4-g8jp-rvxf/GHSA-v5r4-g8jp-rvxf.json
+++ b/advisories/unreviewed/2024/05/GHSA-v5r4-g8jp-rvxf/GHSA-v5r4-g8jp-rvxf.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-v5r4-g8jp-rvxf",
-  "modified": "2024-05-21T15:31:43Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-05-21T15:31:43Z",
   "aliases": [
     "CVE-2021-47353"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nudf: Fix NULL pointer dereference in udf_symlink function\n\nIn function udf_symlink, epos.bh is assigned with the value returned\nby udf_tgetblk. The function udf_tgetblk is defined in udf/misc.c\nand returns the value of sb_getblk function that could be NULL.\nThen, epos.bh is used without any check, causing a possible\nNULL pointer dereference when sb_getblk fails.\n\nThis fix adds a check to validate the value of epos.bh.",
-  "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-21T15:15:21Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-v8p3-mfrc-9v8j/GHSA-v8p3-mfrc-9v8j.json b/advisories/unreviewed/2024/05/GHSA-v8p3-mfrc-9v8j/GHSA-v8p3-mfrc-9v8j.json
index b4006256a97..f27692a41aa 100644
--- a/advisories/unreviewed/2024/05/GHSA-v8p3-mfrc-9v8j/GHSA-v8p3-mfrc-9v8j.json
+++ b/advisories/unreviewed/2024/05/GHSA-v8p3-mfrc-9v8j/GHSA-v8p3-mfrc-9v8j.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-v8p3-mfrc-9v8j",
-  "modified": "2024-05-21T15:31:45Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:44Z",
   "aliases": [
     "CVE-2021-47397"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb\n\nWe should always check if skb_header_pointer's return is NULL before\nusing it, otherwise it may cause null-ptr-deref, as syzbot reported:\n\n  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n  RIP: 0010:sctp_rcv_ootb net/sctp/input.c:705 [inline]\n  RIP: 0010:sctp_rcv+0x1d84/0x3220 net/sctp/input.c:196\n  Call Trace:\n  <IRQ>\n   sctp6_rcv+0x38/0x60 net/sctp/ipv6.c:1109\n   ip6_protocol_deliver_rcu+0x2e9/0x1ca0 net/ipv6/ip6_input.c:422\n   ip6_input_finish+0x62/0x170 net/ipv6/ip6_input.c:463\n   NF_HOOK include/linux/netfilter.h:307 [inline]\n   NF_HOOK include/linux/netfilter.h:301 [inline]\n   ip6_input+0x9c/0xd0 net/ipv6/ip6_input.c:472\n   dst_input include/net/dst.h:460 [inline]\n   ip6_rcv_finish net/ipv6/ip6_input.c:76 [inline]\n   NF_HOOK include/linux/netfilter.h:307 [inline]\n   NF_HOOK include/linux/netfilter.h:301 [inline]\n   ipv6_rcv+0x28c/0x3c0 net/ipv6/ip6_input.c:297",
-  "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-21T15:15:25Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-w883-jj58-rv96/GHSA-w883-jj58-rv96.json b/advisories/unreviewed/2024/05/GHSA-w883-jj58-rv96/GHSA-w883-jj58-rv96.json
index baf3c1c1894..703b3c4efdd 100644
--- a/advisories/unreviewed/2024/05/GHSA-w883-jj58-rv96/GHSA-w883-jj58-rv96.json
+++ b/advisories/unreviewed/2024/05/GHSA-w883-jj58-rv96/GHSA-w883-jj58-rv96.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-w883-jj58-rv96",
-  "modified": "2024-05-21T15:31:45Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:44Z",
   "aliases": [
     "CVE-2021-47404"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: betop: fix slab-out-of-bounds Write in betop_probe\n\nSyzbot reported slab-out-of-bounds Write bug in hid-betopff driver.\nThe problem is the driver assumes the device must have an input report but\nsome malicious devices violate this assumption.\n\nSo this patch checks hid_device's input is non empty before it's been used.",
-  "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-787"
+    ],
+    "severity": "HIGH",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-05-21T15:15:25Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-wvfx-f2w6-5jrg/GHSA-wvfx-f2w6-5jrg.json b/advisories/unreviewed/2024/05/GHSA-wvfx-f2w6-5jrg/GHSA-wvfx-f2w6-5jrg.json
index 9b44a3de295..794aa48b011 100644
--- a/advisories/unreviewed/2024/05/GHSA-wvfx-f2w6-5jrg/GHSA-wvfx-f2w6-5jrg.json
+++ b/advisories/unreviewed/2024/05/GHSA-wvfx-f2w6-5jrg/GHSA-wvfx-f2w6-5jrg.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-wvfx-f2w6-5jrg",
-  "modified": "2024-05-21T15:31:42Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:42Z",
   "aliases": [
     "CVE-2021-47314"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmemory: fsl_ifc: fix leak of private memory on probe failure\n\nOn probe error the driver should free the memory allocated for private\nstructure.  Fix this by using resource-managed allocation.",
-  "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-21T15:15:18Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-x95x-w6hq-mwxc/GHSA-x95x-w6hq-mwxc.json b/advisories/unreviewed/2024/05/GHSA-x95x-w6hq-mwxc/GHSA-x95x-w6hq-mwxc.json
index a41558088c1..4bf3cdad0d8 100644
--- a/advisories/unreviewed/2024/05/GHSA-x95x-w6hq-mwxc/GHSA-x95x-w6hq-mwxc.json
+++ b/advisories/unreviewed/2024/05/GHSA-x95x-w6hq-mwxc/GHSA-x95x-w6hq-mwxc.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-x95x-w6hq-mwxc",
-  "modified": "2024-06-21T15:31:05Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:42Z",
   "aliases": [
     "CVE-2021-47316"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix NULL dereference in nfs3svc_encode_getaclres\n\nIn error cases the dentry may be NULL.\n\nBefore 20798dfe249a, the encoder also checked dentry and\nd_really_is_positive(dentry), but that looks like overkill to me--zero\nstatus should be enough to guarantee a positive dentry.\n\nThis isn't the first time we've seen an error-case NULL dereference\nhidden in the initialization of a local variable in an xdr encoder.  But\nI went back through the other recent rewrites and didn't spot any\nsimilar bugs.",
-  "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-21T15:15:18Z"
diff --git a/advisories/unreviewed/2024/05/GHSA-xmfc-6x2r-fqv5/GHSA-xmfc-6x2r-fqv5.json b/advisories/unreviewed/2024/05/GHSA-xmfc-6x2r-fqv5/GHSA-xmfc-6x2r-fqv5.json
index b3440b5d05b..c9fe325b2cc 100644
--- a/advisories/unreviewed/2024/05/GHSA-xmfc-6x2r-fqv5/GHSA-xmfc-6x2r-fqv5.json
+++ b/advisories/unreviewed/2024/05/GHSA-xmfc-6x2r-fqv5/GHSA-xmfc-6x2r-fqv5.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-xmfc-6x2r-fqv5",
-  "modified": "2024-05-21T15:31:42Z",
+  "modified": "2024-12-24T18:30:48Z",
   "published": "2024-05-21T15:31:42Z",
   "aliases": [
     "CVE-2021-47319"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nvirtio-blk: Fix memory leak among suspend/resume procedure\n\nThe vblk->vqs should be freed before we call init_vqs()\nin virtblk_restore().",
-  "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-21T15:15:19Z"
diff --git a/advisories/unreviewed/2024/11/GHSA-j7rp-c5hp-xpqv/GHSA-j7rp-c5hp-xpqv.json b/advisories/unreviewed/2024/11/GHSA-j7rp-c5hp-xpqv/GHSA-j7rp-c5hp-xpqv.json
index e1993877d07..b2654f0cc1e 100644
--- a/advisories/unreviewed/2024/11/GHSA-j7rp-c5hp-xpqv/GHSA-j7rp-c5hp-xpqv.json
+++ b/advisories/unreviewed/2024/11/GHSA-j7rp-c5hp-xpqv/GHSA-j7rp-c5hp-xpqv.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-j7rp-c5hp-xpqv",
-  "modified": "2024-11-26T00:33:31Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-11-26T00:33:31Z",
   "aliases": [
     "CVE-2024-53098"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe/ufence: Prefetch ufence addr to catch bogus address\n\naccess_ok() only checks for addr overflow so also try to read the addr\nto catch invalid addr sent from userspace.\n\n(cherry picked from commit 9408c4508483ffc60811e910a93d6425b8e63928)",
-  "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": [
     {
@@ -24,8 +29,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-787"
+    ],
+    "severity": "HIGH",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-11-25T22:15:16Z"
diff --git a/advisories/unreviewed/2024/11/GHSA-mh5g-qxxq-3x3p/GHSA-mh5g-qxxq-3x3p.json b/advisories/unreviewed/2024/11/GHSA-mh5g-qxxq-3x3p/GHSA-mh5g-qxxq-3x3p.json
index d3b9f12cee2..b15f8ea015d 100644
--- a/advisories/unreviewed/2024/11/GHSA-mh5g-qxxq-3x3p/GHSA-mh5g-qxxq-3x3p.json
+++ b/advisories/unreviewed/2024/11/GHSA-mh5g-qxxq-3x3p/GHSA-mh5g-qxxq-3x3p.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-mh5g-qxxq-3x3p",
-  "modified": "2024-11-26T00:33:32Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-11-26T00:33:31Z",
   "aliases": [
     "CVE-2024-53100"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme: tcp: avoid race between queue_lock lock and destroy\n\nCommit 76d54bf20cdc (\"nvme-tcp: don't access released socket during\nerror recovery\") added a mutex_lock() call for the queue->queue_lock\nin nvme_tcp_get_address(). However, the mutex_lock() races with\nmutex_destroy() in nvme_tcp_free_queue(), and causes the WARN below.\n\nDEBUG_LOCKS_WARN_ON(lock->magic != lock)\nWARNING: CPU: 3 PID: 34077 at kernel/locking/mutex.c:587 __mutex_lock+0xcf0/0x1220\nModules linked in: nvmet_tcp nvmet nvme_tcp nvme_fabrics iw_cm ib_cm ib_core pktcdvd nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables qrtr sunrpc ppdev 9pnet_virtio 9pnet pcspkr netfs parport_pc parport e1000 i2c_piix4 i2c_smbus loop fuse nfnetlink zram bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper xfs drm sym53c8xx floppy nvme scsi_transport_spi nvme_core nvme_auth serio_raw ata_generic pata_acpi dm_multipath qemu_fw_cfg [last unloaded: ib_uverbs]\nCPU: 3 UID: 0 PID: 34077 Comm: udisksd Not tainted 6.11.0-rc7 #319\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:__mutex_lock+0xcf0/0x1220\nCode: 08 84 d2 0f 85 c8 04 00 00 8b 15 ef b6 c8 01 85 d2 0f 85 78 f4 ff ff 48 c7 c6 20 93 ee af 48 c7 c7 60 91 ee af e8 f0 a7 6d fd <0f> 0b e9 5e f4 ff ff 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1\nRSP: 0018:ffff88811305f760 EFLAGS: 00010286\nRAX: 0000000000000000 RBX: ffff88812c652058 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001\nRBP: ffff88811305f8b0 R08: 0000000000000001 R09: ffffed1075c36341\nR10: ffff8883ae1b1a0b R11: 0000000000010498 R12: 0000000000000000\nR13: 0000000000000000 R14: dffffc0000000000 R15: ffff88812c652058\nFS:  00007f9713ae4980(0000) GS:ffff8883ae180000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fcd78483c7c CR3: 0000000122c38000 CR4: 00000000000006f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n <TASK>\n ? __warn.cold+0x5b/0x1af\n ? __mutex_lock+0xcf0/0x1220\n ? report_bug+0x1ec/0x390\n ? handle_bug+0x3c/0x80\n ? exc_invalid_op+0x13/0x40\n ? asm_exc_invalid_op+0x16/0x20\n ? __mutex_lock+0xcf0/0x1220\n ? nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp]\n ? __pfx___mutex_lock+0x10/0x10\n ? __lock_acquire+0xd6a/0x59e0\n ? nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp]\n nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp]\n ? __pfx_nvme_tcp_get_address+0x10/0x10 [nvme_tcp]\n nvme_sysfs_show_address+0x81/0xc0 [nvme_core]\n dev_attr_show+0x42/0x80\n ? __asan_memset+0x1f/0x40\n sysfs_kf_seq_show+0x1f0/0x370\n seq_read_iter+0x2cb/0x1130\n ? rw_verify_area+0x3b1/0x590\n ? __mutex_lock+0x433/0x1220\n vfs_read+0x6a6/0xa20\n ? lockdep_hardirqs_on+0x78/0x100\n ? __pfx_vfs_read+0x10/0x10\n ksys_read+0xf7/0x1d0\n ? __pfx_ksys_read+0x10/0x10\n ? __x64_sys_openat+0x105/0x1d0\n do_syscall_64+0x93/0x180\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? __pfx_ksys_read+0x10/0x10\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on_prepare+0x16d/0x400\n ? do_syscall_64+0x9f/0x180\n ? lockdep_hardirqs_on+0x78/0x100\n ? do_syscall_64+0x9f/0x180\n ? do_syscall_64+0x9f/0x180\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7f9713f55cfa\nCode: 55 48 89 e5 48 83 ec 20 48 89 55 e8 48 89 75 f0 89 7d f8 e8 e8 74 f8 ff 48 8b 55 e8 48 8b 75 f0 4\n---truncated---",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:H/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-362"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-11-25T22:15:16Z"
diff --git a/advisories/unreviewed/2024/11/GHSA-pg27-6936-jg2x/GHSA-pg27-6936-jg2x.json b/advisories/unreviewed/2024/11/GHSA-pg27-6936-jg2x/GHSA-pg27-6936-jg2x.json
index 62fa5bef764..bd575a460ae 100644
--- a/advisories/unreviewed/2024/11/GHSA-pg27-6936-jg2x/GHSA-pg27-6936-jg2x.json
+++ b/advisories/unreviewed/2024/11/GHSA-pg27-6936-jg2x/GHSA-pg27-6936-jg2x.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-pg27-6936-jg2x",
-  "modified": "2024-11-26T00:33:31Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-11-26T00:33:31Z",
   "aliases": [
     "CVE-2024-53097"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm: krealloc: Fix MTE false alarm in __do_krealloc\n\nThis patch addresses an issue introduced by commit 1a83a716ec233 (\"mm:\nkrealloc: consider spare memory for __GFP_ZERO\") which causes MTE\n(Memory Tagging Extension) to falsely report a slab-out-of-bounds error.\n\nThe problem occurs when zeroing out spare memory in __do_krealloc. The\noriginal code only considered software-based KASAN and did not account\nfor MTE. It does not reset the KASAN tag before calling memset, leading\nto a mismatch between the pointer tag and the memory tag, resulting\nin a false positive.\n\nExample of the error:\n==================================================================\nswapper/0: BUG: KASAN: slab-out-of-bounds in __memset+0x84/0x188\nswapper/0: Write at addr f4ffff8005f0fdf0 by task swapper/0/1\nswapper/0: Pointer tag: [f4], memory tag: [fe]\nswapper/0:\nswapper/0: CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.\nswapper/0: Hardware name: MT6991(ENG) (DT)\nswapper/0: Call trace:\nswapper/0:  dump_backtrace+0xfc/0x17c\nswapper/0:  show_stack+0x18/0x28\nswapper/0:  dump_stack_lvl+0x40/0xa0\nswapper/0:  print_report+0x1b8/0x71c\nswapper/0:  kasan_report+0xec/0x14c\nswapper/0:  __do_kernel_fault+0x60/0x29c\nswapper/0:  do_bad_area+0x30/0xdc\nswapper/0:  do_tag_check_fault+0x20/0x34\nswapper/0:  do_mem_abort+0x58/0x104\nswapper/0:  el1_abort+0x3c/0x5c\nswapper/0:  el1h_64_sync_handler+0x80/0xcc\nswapper/0:  el1h_64_sync+0x68/0x6c\nswapper/0:  __memset+0x84/0x188\nswapper/0:  btf_populate_kfunc_set+0x280/0x3d8\nswapper/0:  __register_btf_kfunc_id_set+0x43c/0x468\nswapper/0:  register_btf_kfunc_id_set+0x48/0x60\nswapper/0:  register_nf_nat_bpf+0x1c/0x40\nswapper/0:  nf_nat_init+0xc0/0x128\nswapper/0:  do_one_initcall+0x184/0x464\nswapper/0:  do_initcall_level+0xdc/0x1b0\nswapper/0:  do_initcalls+0x70/0xc0\nswapper/0:  do_basic_setup+0x1c/0x28\nswapper/0:  kernel_init_freeable+0x144/0x1b8\nswapper/0:  kernel_init+0x20/0x1a8\nswapper/0:  ret_from_fork+0x10/0x20\n==================================================================",
-  "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": [
     {
@@ -45,7 +50,7 @@
   ],
   "database_specific": {
     "cwe_ids": [],
-    "severity": null,
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-11-25T22:15:15Z"
diff --git a/advisories/unreviewed/2024/11/GHSA-xmv6-x39j-72gg/GHSA-xmv6-x39j-72gg.json b/advisories/unreviewed/2024/11/GHSA-xmv6-x39j-72gg/GHSA-xmv6-x39j-72gg.json
index 721b7900d1e..77522a38e99 100644
--- a/advisories/unreviewed/2024/11/GHSA-xmv6-x39j-72gg/GHSA-xmv6-x39j-72gg.json
+++ b/advisories/unreviewed/2024/11/GHSA-xmv6-x39j-72gg/GHSA-xmv6-x39j-72gg.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-xmv6-x39j-72gg",
-  "modified": "2024-11-26T00:33:31Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-11-26T00:33:31Z",
   "aliases": [
     "CVE-2024-53099"
   ],
   "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check validity of link->type in bpf_link_show_fdinfo()\n\nIf a newly-added link type doesn't invoke BPF_LINK_TYPE(), accessing\nbpf_link_type_strs[link->type] may result in an out-of-bounds access.\n\nTo spot such missed invocations early in the future, checking the\nvalidity of link->type in bpf_link_show_fdinfo() and emitting a warning\nwhen such invocations are missed.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -28,8 +33,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": null,
+    "cwe_ids": [
+      "CWE-125"
+    ],
+    "severity": "HIGH",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-11-25T22:15:16Z"
diff --git a/advisories/unreviewed/2024/12/GHSA-325m-pvh6-hvj7/GHSA-325m-pvh6-hvj7.json b/advisories/unreviewed/2024/12/GHSA-325m-pvh6-hvj7/GHSA-325m-pvh6-hvj7.json
index aed5c8088d6..9fe3722656e 100644
--- a/advisories/unreviewed/2024/12/GHSA-325m-pvh6-hvj7/GHSA-325m-pvh6-hvj7.json
+++ b/advisories/unreviewed/2024/12/GHSA-325m-pvh6-hvj7/GHSA-325m-pvh6-hvj7.json
@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-325m-pvh6-hvj7",
-  "modified": "2024-12-23T00:30:54Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-12-23T00:30:54Z",
   "aliases": [
     "CVE-2024-12896"
@@ -23,6 +23,10 @@
       "type": "ADVISORY",
       "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-12896"
     },
+    {
+      "type": "WEB",
+      "url": "https://netsecfish.notion.site/IntelBras-IP-Camera-Information-Disclosure-15e6b683e67c80a89f89daf59daa9ea8"
+    },
     {
       "type": "WEB",
       "url": "https://netsecfish.notion.site/IntelBras-IP-Camera-Information-Disclosure-15e6b683e67c80a89f89daf59daa9ea8?pvs=73"
diff --git a/advisories/unreviewed/2024/12/GHSA-929x-9cm9-h83r/GHSA-929x-9cm9-h83r.json b/advisories/unreviewed/2024/12/GHSA-929x-9cm9-h83r/GHSA-929x-9cm9-h83r.json
index 3672ce7c3c5..84cbf864c06 100644
--- a/advisories/unreviewed/2024/12/GHSA-929x-9cm9-h83r/GHSA-929x-9cm9-h83r.json
+++ b/advisories/unreviewed/2024/12/GHSA-929x-9cm9-h83r/GHSA-929x-9cm9-h83r.json
@@ -1,13 +1,18 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-929x-9cm9-h83r",
-  "modified": "2024-12-24T06:30:42Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-12-24T06:30:42Z",
   "aliases": [
     "CVE-2024-12096"
   ],
   "details": "The Exhibit to WP Gallery WordPress plugin through 0.0.2 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
+    }
+  ],
   "affected": [],
   "references": [
     {
@@ -21,7 +26,7 @@
   ],
   "database_specific": {
     "cwe_ids": [],
-    "severity": null,
+    "severity": "MODERATE",
     "github_reviewed": false,
     "github_reviewed_at": null,
     "nvd_published_at": "2024-12-24T06:15:32Z"
diff --git a/advisories/unreviewed/2024/12/GHSA-cpq8-gjrv-h7mr/GHSA-cpq8-gjrv-h7mr.json b/advisories/unreviewed/2024/12/GHSA-cpq8-gjrv-h7mr/GHSA-cpq8-gjrv-h7mr.json
index 3d2fcba80c2..cafe2b0acf2 100644
--- a/advisories/unreviewed/2024/12/GHSA-cpq8-gjrv-h7mr/GHSA-cpq8-gjrv-h7mr.json
+++ b/advisories/unreviewed/2024/12/GHSA-cpq8-gjrv-h7mr/GHSA-cpq8-gjrv-h7mr.json
@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-cpq8-gjrv-h7mr",
-  "modified": "2024-12-23T00:30:54Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-12-23T00:30:54Z",
   "aliases": [
     "CVE-2024-12897"
@@ -23,6 +23,10 @@
       "type": "ADVISORY",
       "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-12897"
     },
+    {
+      "type": "WEB",
+      "url": "https://netsecfish.notion.site/Path-Traversal-Vulnerability-in-IntelBras-IP-Cameras-mtd-Config-Sha1Account1-and-mtd-Confi-15e6b683e67c80809442ee3425f753b7"
+    },
     {
       "type": "WEB",
       "url": "https://netsecfish.notion.site/Path-Traversal-Vulnerability-in-IntelBras-IP-Cameras-mtd-Config-Sha1Account1-and-mtd-Confi-15e6b683e67c80809442ee3425f753b7?pvs=4"
diff --git a/advisories/unreviewed/2024/12/GHSA-f697-gm3h-xrf9/GHSA-f697-gm3h-xrf9.json b/advisories/unreviewed/2024/12/GHSA-f697-gm3h-xrf9/GHSA-f697-gm3h-xrf9.json
index e914eb062e7..2b0eae20f09 100644
--- a/advisories/unreviewed/2024/12/GHSA-f697-gm3h-xrf9/GHSA-f697-gm3h-xrf9.json
+++ b/advisories/unreviewed/2024/12/GHSA-f697-gm3h-xrf9/GHSA-f697-gm3h-xrf9.json
@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-f697-gm3h-xrf9",
-  "modified": "2024-12-24T12:30:42Z",
+  "modified": "2024-12-24T18:30:49Z",
   "published": "2024-12-24T12:30:42Z",
   "aliases": [
     "CVE-2024-43441"
@@ -17,6 +17,10 @@
     {
       "type": "WEB",
       "url": "https://lists.apache.org/thread/h2607yv32wgcrywov960jpxhvsmmlf12"
+    },
+    {
+      "type": "WEB",
+      "url": "http://www.openwall.com/lists/oss-security/2024/12/24/2"
     }
   ],
   "database_specific": {