{"id":"CVE-2025-21977","aliases":["BELL-CVE-2025-21977","DEBIAN-CVE-2025-21977","EUVD-2025-9343","GHSA-fcxj-8496-8247","ROOT-OS-UBUNTU-2404-CVE-2025-21977","UBUNTU-CVE-2025-21977","USN-7605-1","USN-7605-2","USN-7606-1","USN-7628-1","USN-7764-1","USN-7764-2","USN-7765-1","USN-7766-1","USN-7767-1","USN-7767-2","USN-7779-1","USN-7790-1","USN-7800-1","USN-7801-1","USN-7801-2","USN-7801-3","USN-7802-1","USN-7809-1"],"status":"published","title":"fbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs\n\nGen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer\ndevice. When the kdump kernel runs in such a VM, loading the efifb\ndriver may hang because of accessing the framebuffer at the wrong\nmemory address.\n\nThe scenario occurs when the hyperv_fb driver in the original kernel\nmoves the framebuffer to a different MMIO address because of conflicts\nwith an already-running efifb or simplefb driver. The hyperv_fb driver\nthen informs Hyper-V of the change, which is allowed by the Hyper-V FB\nVMBus device protocol. However, when the kexec command loads the kdump\nkernel into crash memory via the kexec_file_load() system call, the\nsystem call doesn't know the framebuffer has moved, and it sets up the\nkdump screen_info using the original framebuffer address. The transition\nto the kdump kernel does not go through the Hyper-V host, so Hyper-V\ndoes not reset the framebuffer address like it would do on a reboot.\nWhen efifb tries to run, it accesses a non-existent framebuffer\naddress, which traps to the Hyper-V host. After many such accesses,\nthe Hyper-V host thinks the guest is being malicious, and throttles\nthe guest to the point that it runs very slowly or appears to have hung.\n\nWhen the kdump kernel is loaded into crash memory via the kexec_load()\nsystem call, the problem does not occur. In this case, the kexec command\nbuilds the screen_info table itself in user space from data returned\nby the FBIOGET_FSCREENINFO ioctl against /dev/fb0, which gives it the\nnew framebuffer location.\n\nThis problem was originally reported in 2020 [1], resulting in commit\n3cb73bc3fa2a (\"hyperv_fb: Update screen_info after removing old\nframebuffer\"). This commit solved the problem by setting orig_video_isVGA\nto 0, so the kdump kernel was unaware of the EFI framebuffer. The efifb\ndriver did not try to load, and no hang occurred. But in 2024, commit\nc25a19afb81c (\"fbdev/hyperv_fb: Do not clear global screen_info\")\neffectively reverted 3cb73bc3fa2a. Commit c25a19afb81c has no reference\nto 3cb73bc3fa2a, so perhaps it was done without knowing the implications\nthat were reported with 3cb73bc3fa2a. In any case, as of commit\nc25a19afb81c, the original problem came back again.\n\nInterestingly, the hyperv_drm driver does not have this problem because\nit never moves the framebuffer. The difference is that the hyperv_drm\ndriver removes any conflicting framebuffers *before* allocating an MMIO\naddress, while the hyperv_fb drivers removes conflicting framebuffers\n*after* allocating an MMIO address. With the \"after\" ordering, hyperv_fb\nmay encounter a conflict and move the framebuffer to a different MMIO\naddress. But the conflict is essentially bogus because it is removed\na few lines of code later.\n\nRather than fix the problem with the approach from 2020 in commit\n3cb73bc3fa2a, instead slightly reorder the steps in hyperv_fb so\nconflicting framebuffers are removed before allocating an MMIO address.\nThen the default framebuffer MMIO address should always be available, and\nthere's never any confusion about which framebuffer address the kdump\nkernel should use -- it's always the original address provided by\nthe Hyper-V host. This approach is already used by the hyperv_drm\ndriver, and is consistent with the usage guidelines at the head of\nthe module with the function aperture_remove_conflicting_devices().\n\nThis approach also solves a related minor problem when kexec_load()\nis used to load the kdump kernel. With current code, unbinding and\nrebinding the hyperv_fb driver could result in the framebuffer moving\nback to the default framebuffer address, because on the rebind there\nare no conflicts. If such a move is done after the kdump kernel is\nloaded with the new framebuffer address, at kdump time it could again\nhave the wrong address.\n\nThis problem and fix are described in terms of the kdump kernel, but\nit can also occur\n---truncated---","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.00191,"percentile":0.08787,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2025-04-01T15:47:07Z","modified":"2026-11-06T16:17:41Z","fixes":[{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.12.20","6.13.8"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.20-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.12.20-1"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1039.41~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1036.42~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1040.42~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-85.85~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1037.37~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-84.84.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1039.42~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1037.38~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-84.84~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1034.35~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-84.84"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1039.41"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1038.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","fixed_in":["6.11.0-1018.18~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","fixed_in":["6.8.0-1025.27"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1040.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","fixed_in":["6.11.0-1016.16~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1036.40"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1023.25"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","fixed_in":["6.11.0-28.28~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1037.37"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-84.84.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","fixed_in":["6.11.0-1015.16~24.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1039.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","fixed_in":["6.11.0-1012.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1039.42.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1010.10"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","fixed_in":["6.11.0-1024.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1037.38"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1039.43"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1018.19"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2030.31"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1034.35"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1039.41+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1040.46+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-84.84+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1040.42+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.8.0"},{"fixed":"6.12.20"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.13.8"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.20-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.20-1"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.41~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1036.42~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1040.42~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-85.85~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.37~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.38~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1034.35~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.41"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1038.44"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1018.18~24.04.1"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1025.27"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1040.42"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1016.16~24.04.1"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1036.40"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.25"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-28.28~24.04.1"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.37"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-intel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1005.12","6.8.0-1006.13","6.8.0-1007.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1015.16~24.04.2"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1012.12"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3","6.11.0-1007.7","6.11.0-1010.10","6.11.0-1011.11"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1010.10"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1024.24"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1031.31","6.8.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.38"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.43"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1018.19"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2030.31"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1034.35"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.41+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1040.46+fips1"}]}],"versions":["6.8.0-1034.39+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1040.42+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1016.16~24.04.1"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1"],"bundled":177},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-28.28~24.04.1"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1"],"bundled":177},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1015.16~24.04.2"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1"],"bundled":177},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1024.24"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23"],"bundled":177},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1018.18~24.04.1"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1"],"bundled":183},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.41"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1040.42"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1036.40"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.25"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-84.84~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1"],"bundled":103},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1"],"bundled":102},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41"],"bundled":102},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1"],"bundled":102},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.41~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1"],"bundled":101},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1040.42~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1"],"bundled":101},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1034.35"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34"],"bundled":101},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1034.35~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1"],"bundled":101},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.37~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1"],"bundled":107},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.37"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36"],"bundled":107},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.43"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42"],"bundled":100},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2031.32"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31"],"bundled":106},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-85.85~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1"],"bundled":107},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.38"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36"],"bundled":107},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.38~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1"],"bundled":107},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1036.42~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1"],"bundled":106},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1038.44"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39"],"bundled":106},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1025.27"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23"],"bundled":113}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/cfffe46a994ac6d5de3b119917680ea1e9a96125","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/2924802d35e00a36b1503a4e786f1926b2fdc1d0","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/304386373007aaca9236a3f36afac0bbedcd2bf0","tags":["Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21977","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-fcxj-8496-8247"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-21977","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21977.json","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-21977","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-21977","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21977","tags":["report"]},{"url":"https://git.kernel.org/linus/304386373007aaca9236a3f36afac0bbedcd2bf0","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7605-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7606-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7605-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7628-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7764-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7765-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7766-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7767-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7779-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7767-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7764-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7790-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7800-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7801-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7802-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7801-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7809-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7801-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2023-53034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-2312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38683","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2025-21977","title":"fbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs\n\nGen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer\ndevice. When the kdump kernel runs in such a VM, loading the efifb\ndriver may hang because of accessing the framebuffer at the wrong\nmemory address.\n\nThe scenario occurs when the hyperv_fb driver in the original kernel\nmoves the framebuffer to a different MMIO address because of conflicts\nwith an already-running efifb or simplefb driver. The hyperv_fb driver\nthen informs Hyper-V of the change, which is allowed by the Hyper-V FB\nVMBus device protocol. However, when the kexec command loads the kdump\nkernel into crash memory via the kexec_file_load() system call, the\nsystem call doesn't know the framebuffer has moved, and it sets up the\nkdump screen_info using the original framebuffer address. The transition\nto the kdump kernel does not go through the Hyper-V host, so Hyper-V\ndoes not reset the framebuffer address like it would do on a reboot.\nWhen efifb tries to run, it accesses a non-existent framebuffer\naddress, which traps to the Hyper-V host. After many such accesses,\nthe Hyper-V host thinks the guest is being malicious, and throttles\nthe guest to the point that it runs very slowly or appears to have hung.\n\nWhen the kdump kernel is loaded into crash memory via the kexec_load()\nsystem call, the problem does not occur. In this case, the kexec command\nbuilds the screen_info table itself in user space from data returned\nby the FBIOGET_FSCREENINFO ioctl against /dev/fb0, which gives it the\nnew framebuffer location.\n\nThis problem was originally reported in 2020 [1], resulting in commit\n3cb73bc3fa2a (\"hyperv_fb: Update screen_info after removing old\nframebuffer\"). This commit solved the problem by setting orig_video_isVGA\nto 0, so the kdump kernel was unaware of the EFI framebuffer. The efifb\ndriver did not try to load, and no hang occurred. But in 2024, commit\nc25a19afb81c (\"fbdev/hyperv_fb: Do not clear global screen_info\")\neffectively reverted 3cb73bc3fa2a. Commit c25a19afb81c has no reference\nto 3cb73bc3fa2a, so perhaps it was done without knowing the implications\nthat were reported with 3cb73bc3fa2a. In any case, as of commit\nc25a19afb81c, the original problem came back again.\n\nInterestingly, the hyperv_drm driver does not have this problem because\nit never moves the framebuffer. The difference is that the hyperv_drm\ndriver removes any conflicting framebuffers *before* allocating an MMIO\naddress, while the hyperv_fb drivers removes conflicting framebuffers\n*after* allocating an MMIO address. With the \"after\" ordering, hyperv_fb\nmay encounter a conflict and move the framebuffer to a different MMIO\naddress. But the conflict is essentially bogus because it is removed\na few lines of code later.\n\nRather than fix the problem with the approach from 2020 in commit\n3cb73bc3fa2a, instead slightly reorder the steps in hyperv_fb so\nconflicting framebuffers are removed before allocating an MMIO address.\nThen the default framebuffer MMIO address should always be available, and\nthere's never any confusion about which framebuffer address the kdump\nkernel should use -- it's always the original address provided by\nthe Hyper-V host. This approach is already used by the hyperv_drm\ndriver, and is consistent with the usage guidelines at the head of\nthe module with the function aperture_remove_conflicting_devices().\n\nThis approach also solves a related minor problem when kexec_load()\nis used to load the kdump kernel. With current code, unbinding and\nrebinding the hyperv_fb driver could result in the framebuffer moving\nback to the default framebuffer address, because on the rebind there\nare no conflicts. If such a move is done after the kdump kernel is\nloaded with the new framebuffer address, at kdump time it could again\nhave the wrong address.\n\nThis problem and fix are described in terms of the kdump kernel, but\nit can also occur\n---truncated---","status":"published","published":"2025-04-01T15:47:07.642Z","modified":"2026-05-11T21:10:15.103Z","updated_at":"2026-11-02T14:32:32.30152Z"}],"euvd":[{"id":"EUVD-2025-9343","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs\n\nGen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer\ndevice. When the kdump kernel runs in such a VM, loading the efifb\ndriver may hang because of accessing the framebuffer at the wrong\nmemory address.\n\nThe scenario occurs when the hyperv_fb driver in the original kernel\nmoves the framebuffer to a different MMIO address because of conflicts\nwith an already-running efifb or simplefb driver. The hyperv_fb driver\nthen informs Hyper-V of the change, which is allowed by the Hyper-V FB\nVMBus device protocol. However, when the kexec command loads the kdump\nkernel into crash memory via the kexec_file_load() system call, the\nsystem call doesn't know the framebuffer has moved, and it sets up the\nkdump screen_info using the original framebuffer address. The transition\nto the kdump kernel does not go through the Hyper-V host, so Hyper-V\ndoes not reset the framebuffer address like it would do on a reboot.\nWhen efifb tries to run, it accesses a non-existent framebuffer\naddress, which traps to the Hyper-V host. After many such accesses,\nthe Hyper-V host thinks the guest is being malicious, and throttles\nthe guest to the point that it runs very slowly or appears to have hung.\n\nWhen the kdump kernel is loaded into crash memory via the kexec_load()\nsystem call, the problem does not occur. In this case, the kexec command\nbuilds the screen_info table itself in user space from data returned\nby the FBIOGET_FSCREENINFO ioctl against /dev/fb0, which gives it the\nnew framebuffer location.\n\nThis problem was originally reported in 2020 [1], resulting in commit\n3cb73bc3fa2a (\"hyperv_fb: Update screen_info after removing old\nframebuffer\"). This commit solved the problem by setting orig_video_isVGA\nto 0, so the kdump kernel was unaware of the EFI framebuffer. The efifb\ndriver did not try to load, and no hang occurred. But in 2024, commit\nc25a19afb81c (\"fbdev/hyperv_fb: Do not clear global screen_info\")\neffectively reverted 3cb73bc3fa2a. Commit c25a19afb81c has no reference\nto 3cb73bc3fa2a, so perhaps it was done without knowing the implications\nthat were reported with 3cb73bc3fa2a. In any case, as of commit\nc25a19afb81c, the original problem came back again.\n\nInterestingly, the hyperv_drm driver does not have this problem because\nit never moves the framebuffer. The difference is that the hyperv_drm\ndriver removes any conflicting framebuffers *before* allocating an MMIO\naddress, while the hyperv_fb drivers removes conflicting framebuffers\n*after* allocating an MMIO address. With the \"after\" ordering, hyperv_fb\nmay encounter a conflict and move the framebuffer to a different MMIO\naddress. But the conflict is essentially bogus because it is removed\na few lines of code later.\n\nRather than fix the problem with the approach from 2020 in commit\n3cb73bc3fa2a, instead slightly reorder the steps in hyperv_fb so\nconflicting framebuffers are removed before allocating an MMIO address.\nThen the default framebuffer MMIO address should always be available, and\nthere's never any confusion about which framebuffer address the kdump\nkernel should use -- it's always the original address provided by\nthe Hyper-V host. This approach is already used by the hyperv_drm\ndriver, and is consistent with the usage guidelines at the head of\nthe module with the function aperture_remove_conflicting_devices().\n\nThis approach also solves a related minor problem when kexec_load()\nis used to load the kdump kernel. With current code, unbinding and\nrebinding the hyperv_fb driver could result in the framebuffer moving\nback to the default framebuffer address, because on the rebind there\nare no conflicts. If such a move is done after the kdump kernel is\nloaded with the new framebuffer address, at kdump time it could again\nhave the wrong address.\n\nThis problem and fix are described in terms of the kdump kernel, but\nit can also occur\n---truncated---","status":"published","published":"2025-04-01T15:47:07Z","modified":"2026-05-11T21:10:15Z","updated_at":"2026-11-02T19:04:50.94993Z"}],"ghsa":[{"id":"GHSA-fcxj-8496-8247","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: hyperv_fb: Fix hang...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs\n\nGen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer\ndevice. When the kdump kernel runs in such a VM, loading the efifb\ndriver may hang because of accessing the framebuffer at the wrong\nmemory address.\n\nThe scenario occurs when the hyperv_fb driver in the original kernel\nmoves the framebuffer to a different MMIO address because of conflicts\nwith an already-running efifb or simplefb driver. The hyperv_fb driver\nthen informs Hyper-V of the change, which is allowed by the Hyper-V FB\nVMBus device protocol. However, when the kexec command loads the kdump\nkernel into crash memory via the kexec_file_load() system call, the\nsystem call doesn't know the framebuffer has moved, and it sets up the\nkdump screen_info using the original framebuffer address. The transition\nto the kdump kernel does not go through the Hyper-V host, so Hyper-V\ndoes not reset the framebuffer address like it would do on a reboot.\nWhen efifb tries to run, it accesses a non-existent framebuffer\naddress, which traps to the Hyper-V host. After many such accesses,\nthe Hyper-V host thinks the guest is being malicious, and throttles\nthe guest to the point that it runs very slowly or appears to have hung.\n\nWhen the kdump kernel is loaded into crash memory via the kexec_load()\nsystem call, the problem does not occur. In this case, the kexec command\nbuilds the screen_info table itself in user space from data returned\nby the FBIOGET_FSCREENINFO ioctl against /dev/fb0, which gives it the\nnew framebuffer location.\n\nThis problem was originally reported in 2020 [1], resulting in commit\n3cb73bc3fa2a (\"hyperv_fb: Update screen_info after removing old\nframebuffer\"). This commit solved the problem by setting orig_video_isVGA\nto 0, so the kdump kernel was unaware of the EFI framebuffer. The efifb\ndriver did not try to load, and no hang occurred. But in 2024, commit\nc25a19afb81c (\"fbdev/hyperv_fb: Do not clear global screen_info\")\neffectively reverted 3cb73bc3fa2a. Commit c25a19afb81c has no reference\nto 3cb73bc3fa2a, so perhaps it was done without knowing the implications\nthat were reported with 3cb73bc3fa2a. In any case, as of commit\nc25a19afb81c, the original problem came back again.\n\nInterestingly, the hyperv_drm driver does not have this problem because\nit never moves the framebuffer. The difference is that the hyperv_drm\ndriver removes any conflicting framebuffers *before* allocating an MMIO\naddress, while the hyperv_fb drivers removes conflicting framebuffers\n*after* allocating an MMIO address. With the \"after\" ordering, hyperv_fb\nmay encounter a conflict and move the framebuffer to a different MMIO\naddress. But the conflict is essentially bogus because it is removed\na few lines of code later.\n\nRather than fix the problem with the approach from 2020 in commit\n3cb73bc3fa2a, instead slightly reorder the steps in hyperv_fb so\nconflicting framebuffers are removed before allocating an MMIO address.\nThen the default framebuffer MMIO address should always be available, and\nthere's never any confusion about which framebuffer address the kdump\nkernel should use -- it's always the original address provided by\nthe Hyper-V host. This approach is already used by the hyperv_drm\ndriver, and is consistent with the usage guidelines at the head of\nthe module with the function aperture_remove_conflicting_devices().\n\nThis approach also solves a related minor problem when kexec_load()\nis used to load the kdump kernel. With current code, unbinding and\nrebinding the hyperv_fb driver could result in the framebuffer moving\nback to the default framebuffer address, because on the rebind there\nare no conflicts. If such a move is done after the kdump kernel is\nloaded with the new framebuffer address, at kdump time it could again\nhave the wrong address.\n\nThis problem and fix are described in terms of the kdump kernel, but\nit can also occur\n---truncated---","status":"published","published":"2025-04-01T18:30:54Z","modified":"2025-10-30T21:30:41Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:04:15.956958Z"}],"nvd":[{"id":"CVE-2025-21977","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs\n\nGen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer\ndevice. When the kdump kernel runs in such a VM, loading the efifb\ndriver may hang because of accessing the framebuffer at the wrong\nmemory address.\n\nThe scenario occurs when the hyperv_fb driver in the original kernel\nmoves the framebuffer to a different MMIO address because of conflicts\nwith an already-running efifb or simplefb driver. The hyperv_fb driver\nthen informs Hyper-V of the change, which is allowed by the Hyper-V FB\nVMBus device protocol. However, when the kexec command loads the kdump\nkernel into crash memory via the kexec_file_load() system call, the\nsystem call doesn't know the framebuffer has moved, and it sets up the\nkdump screen_info using the original framebuffer address. The transition\nto the kdump kernel does not go through the Hyper-V host, so Hyper-V\ndoes not reset the framebuffer address like it would do on a reboot.\nWhen efifb tries to run, it accesses a non-existent framebuffer\naddress, which traps to the Hyper-V host. After many such accesses,\nthe Hyper-V host thinks the guest is being malicious, and throttles\nthe guest to the point that it runs very slowly or appears to have hung.\n\nWhen the kdump kernel is loaded into crash memory via the kexec_load()\nsystem call, the problem does not occur. In this case, the kexec command\nbuilds the screen_info table itself in user space from data returned\nby the FBIOGET_FSCREENINFO ioctl against /dev/fb0, which gives it the\nnew framebuffer location.\n\nThis problem was originally reported in 2020 [1], resulting in commit\n3cb73bc3fa2a (\"hyperv_fb: Update screen_info after removing old\nframebuffer\"). This commit solved the problem by setting orig_video_isVGA\nto 0, so the kdump kernel was unaware of the EFI framebuffer. The efifb\ndriver did not try to load, and no hang occurred. But in 2024, commit\nc25a19afb81c (\"fbdev/hyperv_fb: Do not clear global screen_info\")\neffectively reverted 3cb73bc3fa2a. Commit c25a19afb81c has no reference\nto 3cb73bc3fa2a, so perhaps it was done without knowing the implications\nthat were reported with 3cb73bc3fa2a. In any case, as of commit\nc25a19afb81c, the original problem came back again.\n\nInterestingly, the hyperv_drm driver does not have this problem because\nit never moves the framebuffer. The difference is that the hyperv_drm\ndriver removes any conflicting framebuffers *before* allocating an MMIO\naddress, while the hyperv_fb drivers removes conflicting framebuffers\n*after* allocating an MMIO address. With the \"after\" ordering, hyperv_fb\nmay encounter a conflict and move the framebuffer to a different MMIO\naddress. But the conflict is essentially bogus because it is removed\na few lines of code later.\n\nRather than fix the problem with the approach from 2020 in commit\n3cb73bc3fa2a, instead slightly reorder the steps in hyperv_fb so\nconflicting framebuffers are removed before allocating an MMIO address.\nThen the default framebuffer MMIO address should always be available, and\nthere's never any confusion about which framebuffer address the kdump\nkernel should use -- it's always the original address provided by\nthe Hyper-V host. This approach is already used by the hyperv_drm\ndriver, and is consistent with the usage guidelines at the head of\nthe module with the function aperture_remove_conflicting_devices().\n\nThis approach also solves a related minor problem when kexec_load()\nis used to load the kdump kernel. With current code, unbinding and\nrebinding the hyperv_fb driver could result in the framebuffer moving\nback to the default framebuffer address, because on the rebind there\nare no conflicts. If such a move is done after the kdump kernel is\nloaded with the new framebuffer address, at kdump time it could again\nhave the wrong address.\n\nThis problem and fix are described in terms of the kdump kernel, but\nit can also occur\n---truncated---","status":"published","published":"2025-04-01T16:15:29.077Z","modified":"2026-06-17T08:44:45.317Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"updated_at":"2026-11-02T14:10:58.094557Z"}],"osv":[{"id":"BELL-CVE-2025-21977","status":"published","published":"2025-04-02T05:58:15.217674Z","modified":"2026-06-25T07:18:22.818427943Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:21.491466Z"},{"id":"DEBIAN-CVE-2025-21977","description":"In the Linux kernel, the following vulnerability has been resolved:  fbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs  Gen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer device. When the kdump kernel runs in such a VM, loading the efifb driver may hang because of accessing the framebuffer at the wrong memory address.  The scenario occurs when the hyperv_fb driver in the original kernel moves the framebuffer to a different MMIO address because of conflicts with an already-running efifb or simplefb driver. The hyperv_fb driver then informs Hyper-V of the change, which is allowed by the Hyper-V FB VMBus device protocol. However, when the kexec command loads the kdump kernel into crash memory via the kexec_file_load() system call, the system call doesn't know the framebuffer has moved, and it sets up the kdump screen_info using the original framebuffer address. The transition to the kdump kernel does not go through the Hyper-V host, so Hyper-V does not reset the framebuffer address like it would do on a reboot. When efifb tries to run, it accesses a non-existent framebuffer address, which traps to the Hyper-V host. After many such accesses, the Hyper-V host thinks the guest is being malicious, and throttles the guest to the point that it runs very slowly or appears to have hung.  When the kdump kernel is loaded into crash memory via the kexec_load() system call, the problem does not occur. In this case, the kexec command builds the screen_info table itself in user space from data returned by the FBIOGET_FSCREENINFO ioctl against /dev/fb0, which gives it the new framebuffer location.  This problem was originally reported in 2020 [1], resulting in commit 3cb73bc3fa2a (\"hyperv_fb: Update screen_info after removing old framebuffer\"). This commit solved the problem by setting orig_video_isVGA to 0, so the kdump kernel was unaware of the EFI framebuffer. The efifb driver did not try to load, and no hang occurred. But in 2024, commit c25a19afb81c (\"fbdev/hyperv_fb: Do not clear global screen_info\") effectively reverted 3cb73bc3fa2a. Commit c25a19afb81c has no reference to 3cb73bc3fa2a, so perhaps it was done without knowing the implications that were reported with 3cb73bc3fa2a. In any case, as of commit c25a19afb81c, the original problem came back again.  Interestingly, the hyperv_drm driver does not have this problem because it never moves the framebuffer. The difference is that the hyperv_drm driver removes any conflicting framebuffers *before* allocating an MMIO address, while the hyperv_fb drivers removes conflicting framebuffers *after* allocating an MMIO address. With the \"after\" ordering, hyperv_fb may encounter a conflict and move the framebuffer to a different MMIO address. But the conflict is essentially bogus because it is removed a few lines of code later.  Rather than fix the problem with the approach from 2020 in commit 3cb73bc3fa2a, instead slightly reorder the steps in hyperv_fb so conflicting framebuffers are removed before allocating an MMIO address. Then the default framebuffer MMIO address should always be available, and there's never any confusion about which framebuffer address the kdump kernel should use -- it's always the original address provided by the Hyper-V host. This approach is already used by the hyperv_drm driver, and is consistent with the usage guidelines at the head of the module with the function aperture_remove_conflicting_devices().  This approach also solves a related minor problem when kexec_load() is used to load the kdump kernel. With current code, unbinding and rebinding the hyperv_fb driver could result in the framebuffer moving back to the default framebuffer address, because on the rebind there are no conflicts. If such a move is done after the kdump kernel is loaded with the new framebuffer address, at kdump time it could again have the wrong address.  This problem and fix are described in terms of the kdump kernel, but it can also occur ---truncated---","status":"published","published":"2025-04-01T16:15:29.077Z","modified":"2026-09-01T20:05:43.292288206Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:45.524682Z"},{"id":"UBUNTU-CVE-2025-21977","description":"In the Linux kernel, the following vulnerability has been resolved: fbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs Gen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer device. When the kdump kernel runs in such a VM, loading the efifb driver may hang because of accessing the framebuffer at the wrong memory address. The scenario occurs when the hyperv_fb driver in the original kernel moves the framebuffer to a different MMIO address because of conflicts with an already-running efifb or simplefb driver. The hyperv_fb driver then informs Hyper-V of the change, which is allowed by the Hyper-V FB VMBus device protocol. However, when the kexec command loads the kdump kernel into crash memory via the kexec_file_load() system call, the system call doesn't know the framebuffer has moved, and it sets up the kdump screen_info using the original framebuffer address. The transition to the kdump kernel does not go through the Hyper-V host, so Hyper-V does not reset the framebuffer address like it would do on a reboot. When efifb tries to run, it accesses a non-existent framebuffer address, which traps to the Hyper-V host. After many such accesses, the Hyper-V host thinks the guest is being malicious, and throttles the guest to the point that it runs very slowly or appears to have hung. When the kdump kernel is loaded into crash memory via the kexec_load() system call, the problem does not occur. In this case, the kexec command builds the screen_info table itself in user space from data returned by the FBIOGET_FSCREENINFO ioctl against /dev/fb0, which gives it the new framebuffer location. This problem was originally reported in 2020 [1], resulting in commit 3cb73bc3fa2a (\"hyperv_fb: Update screen_info after removing old framebuffer\"). This commit solved the problem by setting orig_video_isVGA to 0, so the kdump kernel was unaware of the EFI framebuffer. The efifb driver did not try to load, and no hang occurred. But in 2024, commit c25a19afb81c (\"fbdev/hyperv_fb: Do not clear global screen_info\") effectively reverted 3cb73bc3fa2a. Commit c25a19afb81c has no reference to 3cb73bc3fa2a, so perhaps it was done without knowing the implications that were reported with 3cb73bc3fa2a. In any case, as of commit c25a19afb81c, the original problem came back again. Interestingly, the hyperv_drm driver does not have this problem because it never moves the framebuffer. The difference is that the hyperv_drm driver removes any conflicting framebuffers *before* allocating an MMIO address, while the hyperv_fb drivers removes conflicting framebuffers *after* allocating an MMIO address. With the \"after\" ordering, hyperv_fb may encounter a conflict and move the framebuffer to a different MMIO address. But the conflict is essentially bogus because it is removed a few lines of code later. Rather than fix the problem with the approach from 2020 in commit 3cb73bc3fa2a, instead slightly reorder the steps in hyperv_fb so conflicting framebuffers are removed before allocating an MMIO address. Then the default framebuffer MMIO address should always be available, and there's never any confusion about which framebuffer address the kdump kernel should use -- it's always the original address provided by the Hyper-V host. This approach is already used by the hyperv_drm driver, and is consistent with the usage guidelines at the head of the module with the function aperture_remove_conflicting_devices(). This approach also solves a related minor problem when kexec_load() is used to load the kdump kernel. With current code, unbinding and rebinding the hyperv_fb driver could result in the framebuffer moving back to the default framebuffer address, because on the rebind there are no conflicts. If such a move is done after the kdump kernel is loaded with the new framebuffer address, at kdump time it could again have the wrong address. This problem and fix are described in terms of the kdump kernel, but it can also occur ---truncated---","status":"published","published":"2025-04-01T16:15:00Z","modified":"2026-10-08T12:53:11.588730722Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T16:55:22.579335Z"},{"id":"CVE-2025-21977","title":"fbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs\n\nGen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer\ndevice. When the kdump kernel runs in such a VM, loading the efifb\ndriver may hang because of accessing the framebuffer at the wrong\nmemory address.\n\nThe scenario occurs when the hyperv_fb driver in the original kernel\nmoves the framebuffer to a different MMIO address because of conflicts\nwith an already-running efifb or simplefb driver. The hyperv_fb driver\nthen informs Hyper-V of the change, which is allowed by the Hyper-V FB\nVMBus device protocol. However, when the kexec command loads the kdump\nkernel into crash memory via the kexec_file_load() system call, the\nsystem call doesn't know the framebuffer has moved, and it sets up the\nkdump screen_info using the original framebuffer address. The transition\nto the kdump kernel does not go through the Hyper-V host, so Hyper-V\ndoes not reset the framebuffer address like it would do on a reboot.\nWhen efifb tries to run, it accesses a non-existent framebuffer\naddress, which traps to the Hyper-V host. After many such accesses,\nthe Hyper-V host thinks the guest is being malicious, and throttles\nthe guest to the point that it runs very slowly or appears to have hung.\n\nWhen the kdump kernel is loaded into crash memory via the kexec_load()\nsystem call, the problem does not occur. In this case, the kexec command\nbuilds the screen_info table itself in user space from data returned\nby the FBIOGET_FSCREENINFO ioctl against /dev/fb0, which gives it the\nnew framebuffer location.\n\nThis problem was originally reported in 2020 [1], resulting in commit\n3cb73bc3fa2a (\"hyperv_fb: Update screen_info after removing old\nframebuffer\"). This commit solved the problem by setting orig_video_isVGA\nto 0, so the kdump kernel was unaware of the EFI framebuffer. The efifb\ndriver did not try to load, and no hang occurred. But in 2024, commit\nc25a19afb81c (\"fbdev/hyperv_fb: Do not clear global screen_info\")\neffectively reverted 3cb73bc3fa2a. Commit c25a19afb81c has no reference\nto 3cb73bc3fa2a, so perhaps it was done without knowing the implications\nthat were reported with 3cb73bc3fa2a. In any case, as of commit\nc25a19afb81c, the original problem came back again.\n\nInterestingly, the hyperv_drm driver does not have this problem because\nit never moves the framebuffer. The difference is that the hyperv_drm\ndriver removes any conflicting framebuffers *before* allocating an MMIO\naddress, while the hyperv_fb drivers removes conflicting framebuffers\n*after* allocating an MMIO address. With the \"after\" ordering, hyperv_fb\nmay encounter a conflict and move the framebuffer to a different MMIO\naddress. But the conflict is essentially bogus because it is removed\na few lines of code later.\n\nRather than fix the problem with the approach from 2020 in commit\n3cb73bc3fa2a, instead slightly reorder the steps in hyperv_fb so\nconflicting framebuffers are removed before allocating an MMIO address.\nThen the default framebuffer MMIO address should always be available, and\nthere's never any confusion about which framebuffer address the kdump\nkernel should use -- it's always the original address provided by\nthe Hyper-V host. This approach is already used by the hyperv_drm\ndriver, and is consistent with the usage guidelines at the head of\nthe module with the function aperture_remove_conflicting_devices().\n\nThis approach also solves a related minor problem when kexec_load()\nis used to load the kdump kernel. With current code, unbinding and\nrebinding the hyperv_fb driver could result in the framebuffer moving\nback to the default framebuffer address, because on the rebind there\nare no conflicts. If such a move is done after the kdump kernel is\nloaded with the new framebuffer address, at kdump time it could again\nhave the wrong address.\n\nThis problem and fix are described in terms of the kdump kernel, but\nit can also occur\n---truncated---","status":"published","published":"2025-04-01T15:47:07.642Z","modified":"2026-10-28T02:30:59.754276155Z","updated_at":"2026-11-02T15:44:47.009967Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2025-21977","title":"CVE-2025-21977 in linux - Patched by Root","description":"Root has patched CVE-2025-21977 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T15:54:27Z","modified":"2026-11-06T16:17:41.983268978Z","updated_at":"2026-11-06T16:59:12.24096Z"},{"id":"USN-7605-1","title":"linux, linux-aws, linux-gcp, linux-gcp-6.11, linux-hwe-6.11, linux-oracle, linux-raspi, linux-realtime vulnerabilities","description":"It was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly verify the target namespace when handling\nupcalls. An attacker could use this to expose sensitive information.\n(CVE-2025-2312)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - Clock framework and drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MemoryStick subsystem;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - VideoCore services drivers;\n  - Thermal drivers;\n  - USB DSL drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - W1 Dallas's 1-wire bus driver;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Key Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - UProbes tracing;\n  - RDMA verbs API;\n  - SoC audio core drivers;\n  - BPF subsystem;\n  - Perf events;\n  - Kernel fork() syscall;\n  - Tracing infrastructure;\n  - Watch queue notification mechanism;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n  - Key management;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2025-21913, CVE-2025-22070, CVE-2025-21918, CVE-2025-21916,\nCVE-2025-22090, CVE-2025-22040, CVE-2025-21972, CVE-2025-21920,\nCVE-2025-22071, CVE-2025-21989, CVE-2025-22037, CVE-2025-22068,\nCVE-2025-38049, CVE-2025-21980, CVE-2025-21956, CVE-2025-21962,\nCVE-2025-21929, CVE-2025-37785, CVE-2025-37889, CVE-2025-21990,\nCVE-2025-21966, CVE-2025-38240, CVE-2025-22058, CVE-2025-22072,\nCVE-2025-22056, CVE-2025-21963, CVE-2025-23134, CVE-2025-22075,\nCVE-2025-22054, CVE-2025-22064, CVE-2025-22027, CVE-2025-21927,\nCVE-2025-21943, CVE-2025-22081, CVE-2025-21975, CVE-2025-39735,\nCVE-2025-22088, CVE-2025-21996, CVE-2025-22009, CVE-2025-22000,\nCVE-2025-21912, CVE-2025-21967, CVE-2025-21995, CVE-2025-21973,\nCVE-2025-21908, CVE-2025-22047, CVE-2025-21930, CVE-2025-22078,\nCVE-2025-21957, CVE-2025-22021, CVE-2025-22019, CVE-2025-21935,\nCVE-2025-21951, CVE-2025-37937, CVE-2025-22043, CVE-2025-22057,\nCVE-2025-21922, CVE-2025-22003, CVE-2025-21978, CVE-2025-22010,\nCVE-2025-39989, CVE-2025-22034, CVE-2025-21986, CVE-2025-22016,\nCVE-2025-21960, CVE-2025-22038, CVE-2025-21924, CVE-2025-22015,\nCVE-2025-38152, CVE-2025-21939, CVE-2025-21917, CVE-2025-21974,\nCVE-2025-22001, CVE-2025-22025, CVE-2025-22062, CVE-2025-21979,\nCVE-2025-21911, CVE-2025-22045, CVE-2025-21914, CVE-2025-21937,\nCVE-2025-22095, CVE-2025-21981, CVE-2025-22014, CVE-2025-21947,\nCVE-2025-22007, CVE-2025-21925, CVE-2025-22089, CVE-2025-21923,\nCVE-2025-38575, CVE-2025-22018, CVE-2025-22073, CVE-2025-21948,\nCVE-2025-22080, CVE-2025-22053, CVE-2025-21903, CVE-2025-21969,\nCVE-2025-21926, CVE-2025-21941, CVE-2025-40114, CVE-2025-22066,\nCVE-2025-22017, CVE-2025-21945, CVE-2025-22065, CVE-2025-22086,\nCVE-2025-22032, CVE-2025-22097, CVE-2025-22083, CVE-2025-22044,\nCVE-2025-23136, CVE-2025-22046, CVE-2025-22041, CVE-2025-38479,\nCVE-2025-21998, CVE-2025-22002, CVE-2025-39688, CVE-2025-22033,\nCVE-2025-21970, CVE-2025-22022, CVE-2025-21936, CVE-2025-22050,\nCVE-2025-21984, CVE-2025-21928, CVE-2025-38637, CVE-2025-22030,\nCVE-2025-21915, CVE-2025-22013, CVE-2025-21997, CVE-2025-22059,\nCVE-2025-21961, CVE-2025-21909, CVE-2025-21955, CVE-2025-39778,\nCVE-2025-22055, CVE-2023-53034, CVE-2025-39728, CVE-2025-22020,\nCVE-2025-22005, CVE-2025-22060, CVE-2025-21902, CVE-2025-22008,\nCVE-2025-23138, CVE-2025-21991, CVE-2025-21999, CVE-2025-21982,\nCVE-2024-58092, CVE-2025-21992, CVE-2025-22028, CVE-2025-22042,\nCVE-2025-22087, CVE-2025-21894, CVE-2025-21934, CVE-2025-21893,\nCVE-2025-22079, CVE-2025-22023, CVE-2025-21977, CVE-2024-58093,\nCVE-2025-21904, CVE-2025-21910, CVE-2025-22024, CVE-2025-21964,\nCVE-2025-21946, CVE-2025-21905, CVE-2025-22084, CVE-2025-21950,\nCVE-2025-22011, CVE-2025-21968, CVE-2025-22035, CVE-2025-22004,\nCVE-2025-21919, CVE-2025-22039, CVE-2025-22063, CVE-2024-53222,\nCVE-2025-21944, CVE-2025-21959, CVE-2025-21994, CVE-2025-21906)\n","status":"published","published":"2025-06-30T17:22:43Z","modified":"2026-11-03T14:31:50.132719293Z","updated_at":"2026-11-03T14:35:23.570529Z"},{"id":"USN-7605-2","title":"linux-lowlatency, linux-lowlatency-hwe-6.11 vulnerabilities","description":"It was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly verify the target namespace when handling\nupcalls. An attacker could use this to expose sensitive information.\n(CVE-2025-2312)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - Clock framework and drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MemoryStick subsystem;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - VideoCore services drivers;\n  - Thermal drivers;\n  - USB DSL drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - W1 Dallas's 1-wire bus driver;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Key Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - UProbes tracing;\n  - RDMA verbs API;\n  - SoC audio core drivers;\n  - BPF subsystem;\n  - Perf events;\n  - Kernel fork() syscall;\n  - Tracing infrastructure;\n  - Watch queue notification mechanism;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n  - Key management;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2025-21913, CVE-2025-22070, CVE-2025-21918, CVE-2025-21916,\nCVE-2025-22090, CVE-2025-22040, CVE-2025-21972, CVE-2025-21920,\nCVE-2025-22071, CVE-2025-21989, CVE-2025-22037, CVE-2025-22068,\nCVE-2025-38049, CVE-2025-21980, CVE-2025-21956, CVE-2025-21962,\nCVE-2025-21929, CVE-2025-37785, CVE-2025-37889, CVE-2025-21990,\nCVE-2025-21966, CVE-2025-38240, CVE-2025-22058, CVE-2025-22072,\nCVE-2025-22056, CVE-2025-21963, CVE-2025-23134, CVE-2025-22075,\nCVE-2025-22054, CVE-2025-22064, CVE-2025-22027, CVE-2025-21927,\nCVE-2025-21943, CVE-2025-22081, CVE-2025-21975, CVE-2025-39735,\nCVE-2025-22088, CVE-2025-21996, CVE-2025-22009, CVE-2025-22000,\nCVE-2025-21912, CVE-2025-21967, CVE-2025-21995, CVE-2025-21973,\nCVE-2025-21908, CVE-2025-22047, CVE-2025-21930, CVE-2025-22078,\nCVE-2025-21957, CVE-2025-22021, CVE-2025-22019, CVE-2025-21935,\nCVE-2025-21951, CVE-2025-37937, CVE-2025-22043, CVE-2025-22057,\nCVE-2025-21922, CVE-2025-22003, CVE-2025-21978, CVE-2025-22010,\nCVE-2025-39989, CVE-2025-22034, CVE-2025-21986, CVE-2025-22016,\nCVE-2025-21960, CVE-2025-22038, CVE-2025-21924, CVE-2025-22015,\nCVE-2025-38152, CVE-2025-21939, CVE-2025-21917, CVE-2025-21974,\nCVE-2025-22001, CVE-2025-22025, CVE-2025-22062, CVE-2025-21979,\nCVE-2025-21911, CVE-2025-22045, CVE-2025-21914, CVE-2025-21937,\nCVE-2025-22095, CVE-2025-21981, CVE-2025-22014, CVE-2025-21947,\nCVE-2025-22007, CVE-2025-21925, CVE-2025-22089, CVE-2025-21923,\nCVE-2025-38575, CVE-2025-22018, CVE-2025-22073, CVE-2025-21948,\nCVE-2025-22080, CVE-2025-22053, CVE-2025-21903, CVE-2025-21969,\nCVE-2025-21926, CVE-2025-21941, CVE-2025-40114, CVE-2025-22066,\nCVE-2025-22017, CVE-2025-21945, CVE-2025-22065, CVE-2025-22086,\nCVE-2025-22032, CVE-2025-22097, CVE-2025-22083, CVE-2025-22044,\nCVE-2025-23136, CVE-2025-22046, CVE-2025-22041, CVE-2025-38479,\nCVE-2025-21998, CVE-2025-22002, CVE-2025-39688, CVE-2025-22033,\nCVE-2025-21970, CVE-2025-22022, CVE-2025-21936, CVE-2025-22050,\nCVE-2025-21984, CVE-2025-21928, CVE-2025-38637, CVE-2025-22030,\nCVE-2025-21915, CVE-2025-22013, CVE-2025-21997, CVE-2025-22059,\nCVE-2025-21961, CVE-2025-21909, CVE-2025-21955, CVE-2025-39778,\nCVE-2025-22055, CVE-2023-53034, CVE-2025-39728, CVE-2025-22020,\nCVE-2025-22005, CVE-2025-22060, CVE-2025-21902, CVE-2025-22008,\nCVE-2025-23138, CVE-2025-21991, CVE-2025-21999, CVE-2025-21982,\nCVE-2024-58092, CVE-2025-21992, CVE-2025-22028, CVE-2025-22042,\nCVE-2025-22087, CVE-2025-21894, CVE-2025-21934, CVE-2025-21893,\nCVE-2025-22079, CVE-2025-22023, CVE-2025-21977, CVE-2024-58093,\nCVE-2025-21904, CVE-2025-21910, CVE-2025-22024, CVE-2025-21964,\nCVE-2025-21946, CVE-2025-21905, CVE-2025-22084, CVE-2025-21950,\nCVE-2025-22011, CVE-2025-21968, CVE-2025-22035, CVE-2025-22004,\nCVE-2025-21919, CVE-2025-22039, CVE-2025-22063, CVE-2024-53222,\nCVE-2025-21944, CVE-2025-21959, CVE-2025-21994, CVE-2025-21906)\n","status":"published","published":"2025-07-04T14:24:27Z","modified":"2026-11-03T14:31:44.961806591Z","updated_at":"2026-11-03T14:35:23.570529Z"},{"id":"USN-7606-1","title":"linux-oem-6.11 vulnerabilities","description":"It was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly verify the target namespace when handling\nupcalls. An attacker could use this to expose sensitive information.\n(CVE-2025-2312)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - Clock framework and drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MemoryStick subsystem;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - VideoCore services drivers;\n  - Thermal drivers;\n  - USB DSL drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - W1 Dallas's 1-wire bus driver;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Key Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - UProbes tracing;\n  - RDMA verbs API;\n  - SoC audio core drivers;\n  - BPF subsystem;\n  - Perf events;\n  - Kernel fork() syscall;\n  - Tracing infrastructure;\n  - Watch queue notification mechanism;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n  - Key management;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2025-22072, CVE-2025-22039, CVE-2025-22078, CVE-2025-21972,\nCVE-2025-21989, CVE-2025-21919, CVE-2025-22030, CVE-2025-22084,\nCVE-2025-22086, CVE-2025-21956, CVE-2025-21924, CVE-2025-22016,\nCVE-2025-23138, CVE-2025-22059, CVE-2025-21928, CVE-2025-21906,\nCVE-2025-21947, CVE-2025-21936, CVE-2025-21982, CVE-2025-38152,\nCVE-2025-38049, CVE-2025-21974, CVE-2025-21962, CVE-2025-22075,\nCVE-2025-21959, CVE-2025-22002, CVE-2025-22014, CVE-2025-21905,\nCVE-2025-22044, CVE-2025-22000, CVE-2025-21925, CVE-2025-21944,\nCVE-2025-21926, CVE-2025-21904, CVE-2024-58092, CVE-2025-21964,\nCVE-2025-22009, CVE-2025-22083, CVE-2025-21992, CVE-2025-39778,\nCVE-2025-22021, CVE-2025-22090, CVE-2025-21934, CVE-2025-22043,\nCVE-2025-22027, CVE-2025-21951, CVE-2025-22019, CVE-2025-21908,\nCVE-2025-22062, CVE-2025-22071, CVE-2025-21914, CVE-2025-21966,\nCVE-2025-21984, CVE-2025-39735, CVE-2025-21912, CVE-2025-21979,\nCVE-2025-22063, CVE-2025-37785, CVE-2025-22081, CVE-2025-22024,\nCVE-2025-38637, CVE-2025-22070, CVE-2025-21911, CVE-2025-21935,\nCVE-2024-58093, CVE-2025-21960, CVE-2025-21913, CVE-2025-21927,\nCVE-2025-21977, CVE-2025-37843, CVE-2025-22055, CVE-2025-22035,\nCVE-2025-21998, CVE-2025-22041, CVE-2025-21945, CVE-2025-22080,\nCVE-2025-21963, CVE-2025-21994, CVE-2025-21957, CVE-2025-22079,\nCVE-2025-22034, CVE-2025-21946, CVE-2025-22053, CVE-2025-22003,\nCVE-2025-22042, CVE-2025-22023, CVE-2025-22020, CVE-2025-21910,\nCVE-2025-22037, CVE-2025-22095, CVE-2025-22089, CVE-2025-21986,\nCVE-2025-39688, CVE-2025-22040, CVE-2025-39728, CVE-2025-21981,\nCVE-2025-21969, CVE-2025-21922, CVE-2025-22022, CVE-2025-23136,\nCVE-2025-22058, CVE-2025-21970, CVE-2025-22050, CVE-2025-21978,\nCVE-2025-21990, CVE-2025-22046, CVE-2025-21975, CVE-2025-21973,\nCVE-2025-21916, CVE-2025-21991, CVE-2025-22007, CVE-2025-21937,\nCVE-2025-22004, CVE-2025-21948, CVE-2025-22033, CVE-2025-22017,\nCVE-2025-38575, CVE-2025-22097, CVE-2025-22066, CVE-2025-21999,\nCVE-2025-21903, CVE-2025-21915, CVE-2025-21961, CVE-2025-21941,\nCVE-2025-22064, CVE-2025-21968, CVE-2025-21980, CVE-2025-22010,\nCVE-2025-38240, CVE-2025-38479, CVE-2025-22008, CVE-2025-21939,\nCVE-2025-22045, CVE-2025-22068, CVE-2025-21893, CVE-2025-37889,\nCVE-2024-53222, CVE-2025-22047, CVE-2025-22018, CVE-2025-22013,\nCVE-2025-21920, CVE-2025-23134, CVE-2025-22025, CVE-2025-39989,\nCVE-2025-22005, CVE-2025-22054, CVE-2025-22057, CVE-2025-22087,\nCVE-2025-22088, CVE-2025-22056, CVE-2025-22060, CVE-2025-22015,\nCVE-2025-37937, CVE-2025-22001, CVE-2025-21930, CVE-2025-21894,\nCVE-2025-21943, CVE-2025-22028, CVE-2025-22032, CVE-2025-22065,\nCVE-2025-21929, CVE-2025-21996, CVE-2025-22038, CVE-2025-21923,\nCVE-2025-40114, CVE-2025-21967, CVE-2025-21995, CVE-2023-53034,\nCVE-2025-21909, CVE-2025-21997, CVE-2025-21955, CVE-2025-21918,\nCVE-2025-21917, CVE-2025-22073, CVE-2025-22011, CVE-2025-21950)\n","status":"published","published":"2025-06-30T18:29:21Z","modified":"2026-11-03T14:31:31.578654634Z","updated_at":"2026-11-03T14:35:23.570529Z"},{"id":"USN-7628-1","title":"linux-azure, linux-azure-6.11 vulnerabilities","description":"It was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly verify the target namespace when handling\nupcalls. An attacker could use this to expose sensitive information.\n(CVE-2025-2312)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - Clock framework and drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - Qualcomm firmware drivers;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MemoryStick subsystem;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - VideoCore services drivers;\n  - Thermal drivers;\n  - USB DSL drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - W1 Dallas's 1-wire bus driver;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Key Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - UProbes tracing;\n  - RDMA verbs API;\n  - SoC audio core drivers;\n  - BPF subsystem;\n  - Perf events;\n  - Kernel fork() syscall;\n  - Tracing infrastructure;\n  - Watch queue notification mechanism;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n  - Key management;\n  - ALSA framework;\n  - SoC Audio for Freescale CPUs drivers;\n(CVE-2025-39728, CVE-2025-22059, CVE-2025-22008, CVE-2025-37932,\nCVE-2025-22033, CVE-2025-21984, CVE-2025-22063, CVE-2025-22065,\nCVE-2025-21991, CVE-2025-38479, CVE-2025-21948, CVE-2025-21936,\nCVE-2025-22038, CVE-2025-21951, CVE-2025-21906, CVE-2025-21924,\nCVE-2025-21966, CVE-2025-22073, CVE-2025-22020, CVE-2025-21974,\nCVE-2025-22043, CVE-2025-22088, CVE-2025-21959, CVE-2025-38575,\nCVE-2025-22035, CVE-2025-23134, CVE-2025-22009, CVE-2025-22010,\nCVE-2025-21941, CVE-2025-21914, CVE-2025-22066, CVE-2025-22017,\nCVE-2025-21911, CVE-2025-21928, CVE-2025-21998, CVE-2025-21920,\nCVE-2025-21961, CVE-2025-21992, CVE-2025-21995, CVE-2025-21997,\nCVE-2025-22084, CVE-2025-22011, CVE-2025-22039, CVE-2025-21977,\nCVE-2025-21963, CVE-2025-21981, CVE-2024-53222, CVE-2025-22037,\nCVE-2025-22070, CVE-2025-21950, CVE-2025-21980, CVE-2025-22023,\nCVE-2025-38049, CVE-2025-22018, CVE-2025-22072, CVE-2025-22021,\nCVE-2025-21986, CVE-2025-22019, CVE-2025-22045, CVE-2025-21990,\nCVE-2025-21926, CVE-2025-39989, CVE-2025-21902, CVE-2025-21946,\nCVE-2025-21908, CVE-2025-22081, CVE-2025-22042, CVE-2024-58092,\nCVE-2025-21939, CVE-2025-22086, CVE-2025-21996, CVE-2025-21929,\nCVE-2025-21947, CVE-2025-21919, CVE-2025-21922, CVE-2023-53034,\nCVE-2025-22013, CVE-2025-21979, CVE-2025-21968, CVE-2025-22056,\nCVE-2025-37937, CVE-2025-22047, CVE-2025-21956, CVE-2025-22064,\nCVE-2025-21903, CVE-2025-22062, CVE-2025-21934, CVE-2025-22050,\nCVE-2025-21957, CVE-2025-39778, CVE-2025-21970, CVE-2025-21944,\nCVE-2025-37890, CVE-2025-21945, CVE-2025-22046, CVE-2025-38152,\nCVE-2025-23138, CVE-2025-39735, CVE-2025-22041, CVE-2025-22083,\nCVE-2025-21969, CVE-2025-37785, CVE-2025-21967, CVE-2025-21910,\nCVE-2025-22078, CVE-2025-21915, CVE-2025-22089, CVE-2025-39688,\nCVE-2025-21923, CVE-2025-22002, CVE-2025-22014, CVE-2025-38240,\nCVE-2025-21943, CVE-2025-21904, CVE-2025-21893, CVE-2025-21913,\nCVE-2025-22034, CVE-2025-22015, CVE-2025-21925, CVE-2025-22087,\nCVE-2025-40114, CVE-2025-21917, CVE-2025-22040, CVE-2025-21989,\nCVE-2025-21927, CVE-2025-22075, CVE-2025-21912, CVE-2025-38000,\nCVE-2025-22057, CVE-2025-22025, CVE-2025-22058, CVE-2025-22016,\nCVE-2025-22027, CVE-2025-22097, CVE-2025-22095, CVE-2025-22007,\nCVE-2025-22001, CVE-2025-23136, CVE-2025-21982, CVE-2025-21999,\nCVE-2025-22079, CVE-2025-22055, CVE-2025-22000, CVE-2025-22004,\nCVE-2025-21964, CVE-2025-38001, CVE-2025-37889, CVE-2025-21909,\nCVE-2025-38637, CVE-2025-22071, CVE-2025-22044, CVE-2025-22032,\nCVE-2025-21973, CVE-2025-22003, CVE-2025-21894, CVE-2025-21994,\nCVE-2025-22080, CVE-2024-58093, CVE-2025-21975, CVE-2025-22054,\nCVE-2025-37798, CVE-2025-22060, CVE-2025-21955, CVE-2025-22028,\nCVE-2025-21978, CVE-2025-22090, CVE-2025-22053, CVE-2025-21918,\nCVE-2025-21962, CVE-2025-22024, CVE-2025-22005, CVE-2025-21935,\nCVE-2025-21937, CVE-2025-21972, CVE-2025-21916, CVE-2025-37997,\nCVE-2025-22022, CVE-2025-21905, CVE-2025-22068, CVE-2025-22030,\nCVE-2025-21930, CVE-2025-21960)\n","status":"published","published":"2025-07-08T22:30:53Z","modified":"2026-11-03T14:31:54.388520677Z","updated_at":"2026-11-03T14:35:23.570529Z"},{"id":"USN-7764-1","title":"linux, linux-aws, linux-gcp, linux-gke, linux-gkeop, linux-lowlatency, linux-lowlatency-hwe-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-22008, CVE-2025-21872, CVE-2025-21945, CVE-2025-37889,\nCVE-2025-21997, CVE-2025-21935, CVE-2025-21986, CVE-2025-21890,\nCVE-2025-21925, CVE-2024-58090, CVE-2025-38569, CVE-2025-21911,\nCVE-2025-21957, CVE-2025-21891, CVE-2025-21924, CVE-2025-21956,\nCVE-2025-21994, CVE-2025-22013, CVE-2025-21964, CVE-2025-21909,\nCVE-2025-21888, CVE-2025-21918, CVE-2025-21981, CVE-2025-21966,\nCVE-2025-22011, CVE-2025-21877, CVE-2025-21913, CVE-2025-21895,\nCVE-2025-21929, CVE-2025-22010, CVE-2025-21992, CVE-2025-21930,\nCVE-2025-21982, CVE-2025-21894, CVE-2025-21934, CVE-2025-21873,\nCVE-2025-21914, CVE-2025-21941, CVE-2025-21962, CVE-2025-22014,\nCVE-2025-21905, CVE-2025-21908, CVE-2025-21898, CVE-2025-21878,\nCVE-2025-22009, CVE-2025-21961, CVE-2025-22015, CVE-2025-21883,\nCVE-2025-21916, CVE-2025-22016, CVE-2025-21936, CVE-2025-21947,\nCVE-2025-21927, CVE-2025-22004, CVE-2025-21926, CVE-2025-21969,\nCVE-2025-21976, CVE-2025-21912, CVE-2025-21920, CVE-2025-21951,\nCVE-2025-22005, CVE-2025-21978, CVE-2025-21975, CVE-2025-22007,\nCVE-2025-21928, CVE-2025-21968, CVE-2025-21963, CVE-2025-21977,\nCVE-2025-21915, CVE-2025-21980, CVE-2025-22047, CVE-2025-21972,\nCVE-2025-21892, CVE-2025-22003, CVE-2025-21979, CVE-2025-21944,\nCVE-2025-21880, CVE-2025-21899, CVE-2025-21995, CVE-2025-22017,\nCVE-2025-21946, CVE-2025-22001, CVE-2025-21904, CVE-2025-21881,\nCVE-2025-21917, CVE-2025-21970, CVE-2025-21889, CVE-2025-21922,\nCVE-2025-21875, CVE-2025-21919, CVE-2025-21991, CVE-2025-21967,\nCVE-2025-21960, CVE-2025-21959, CVE-2025-21955, CVE-2025-21996,\nCVE-2025-21950, CVE-2025-21937, CVE-2025-21948, CVE-2025-21903,\nCVE-2025-21885, CVE-2025-21999, CVE-2025-21910)\n","status":"published","published":"2025-09-24T10:43:56Z","modified":"2026-10-30T21:56:23.858878537Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7764-2","title":"linux-hwe-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-21945, CVE-2025-21991, CVE-2025-22008, CVE-2025-21996,\nCVE-2025-21924, CVE-2025-21986, CVE-2025-21872, CVE-2025-21962,\nCVE-2025-22007, CVE-2025-37889, CVE-2025-21889, CVE-2025-21968,\nCVE-2025-21903, CVE-2025-21955, CVE-2025-21982, CVE-2025-21929,\nCVE-2025-21944, CVE-2025-22004, CVE-2025-21997, CVE-2025-21941,\nCVE-2025-22047, CVE-2025-21915, CVE-2025-21995, CVE-2025-22011,\nCVE-2025-21891, CVE-2025-22009, CVE-2025-22015, CVE-2024-58090,\nCVE-2025-21947, CVE-2025-21976, CVE-2025-21964, CVE-2025-21904,\nCVE-2025-21880, CVE-2025-21918, CVE-2025-21950, CVE-2025-21948,\nCVE-2025-21888, CVE-2025-22014, CVE-2025-21963, CVE-2025-21875,\nCVE-2025-21967, CVE-2025-21972, CVE-2025-21895, CVE-2025-21961,\nCVE-2025-21926, CVE-2025-21892, CVE-2025-21916, CVE-2025-21894,\nCVE-2025-21930, CVE-2025-21927, CVE-2025-21911, CVE-2025-21936,\nCVE-2025-21881, CVE-2025-38569, CVE-2025-21873, CVE-2025-21951,\nCVE-2025-22003, CVE-2025-21877, CVE-2025-21908, CVE-2025-21956,\nCVE-2025-21977, CVE-2025-21917, CVE-2025-21922, CVE-2025-21959,\nCVE-2025-22005, CVE-2025-22017, CVE-2025-22016, CVE-2025-21878,\nCVE-2025-21970, CVE-2025-21905, CVE-2025-21978, CVE-2025-21981,\nCVE-2025-21980, CVE-2025-21910, CVE-2025-21925, CVE-2025-21885,\nCVE-2025-21946, CVE-2025-21937, CVE-2025-21919, CVE-2025-22013,\nCVE-2025-21883, CVE-2025-21957, CVE-2025-21914, CVE-2025-21909,\nCVE-2025-21934, CVE-2025-21975, CVE-2025-21912, CVE-2025-21969,\nCVE-2025-21898, CVE-2025-21890, CVE-2025-21899, CVE-2025-22001,\nCVE-2025-21979, CVE-2025-21966, CVE-2025-21935, CVE-2025-21920,\nCVE-2025-21913, CVE-2025-22010, CVE-2025-21992, CVE-2025-21960,\nCVE-2025-21994, CVE-2025-21999, CVE-2025-21928)\n","status":"published","published":"2025-09-26T07:36:37Z","modified":"2026-06-03T14:04:15.580266169Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7765-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-21980, CVE-2025-21999, CVE-2025-21991, CVE-2025-21937,\nCVE-2025-22016, CVE-2025-21920, CVE-2025-21979, CVE-2025-21919,\nCVE-2025-21969, CVE-2025-21872, CVE-2025-21996, CVE-2025-21927,\nCVE-2025-21904, CVE-2025-22013, CVE-2025-21928, CVE-2025-21891,\nCVE-2025-21889, CVE-2025-21972, CVE-2025-21981, CVE-2025-38569,\nCVE-2025-21910, CVE-2025-21945, CVE-2025-22011, CVE-2025-21916,\nCVE-2025-21924, CVE-2025-21922, CVE-2025-21975, CVE-2025-21880,\nCVE-2025-21995, CVE-2025-21977, CVE-2025-21947, CVE-2025-21914,\nCVE-2025-21905, CVE-2025-22009, CVE-2025-21892, CVE-2025-22005,\nCVE-2024-58090, CVE-2025-21926, CVE-2025-37889, CVE-2025-21966,\nCVE-2025-21955, CVE-2025-22007, CVE-2025-21894, CVE-2025-21909,\nCVE-2025-21883, CVE-2025-21992, CVE-2025-21976, CVE-2025-21890,\nCVE-2025-21898, CVE-2025-21982, CVE-2025-21877, CVE-2025-21925,\nCVE-2025-21970, CVE-2025-21930, CVE-2025-21946, CVE-2025-22017,\nCVE-2025-21908, CVE-2025-21944, CVE-2025-21885, CVE-2025-22010,\nCVE-2025-21917, CVE-2025-21918, CVE-2025-21934, CVE-2025-21950,\nCVE-2025-21963, CVE-2025-22003, CVE-2025-21961, CVE-2025-21967,\nCVE-2025-21878, CVE-2025-21895, CVE-2025-21913, CVE-2025-21875,\nCVE-2025-21959, CVE-2025-22008, CVE-2025-21968, CVE-2025-21936,\nCVE-2025-21956, CVE-2025-21903, CVE-2025-22004, CVE-2025-21986,\nCVE-2025-21915, CVE-2025-21964, CVE-2025-22014, CVE-2025-21994,\nCVE-2025-21912, CVE-2025-21873, CVE-2025-21957, CVE-2025-22015,\nCVE-2025-21997, CVE-2025-21948, CVE-2025-21951, CVE-2025-21962,\nCVE-2025-22001, CVE-2025-21978, CVE-2025-21960, CVE-2025-22047,\nCVE-2025-21935, CVE-2025-21899, CVE-2025-21911, CVE-2025-21881,\nCVE-2025-21929, CVE-2025-21941)\n","status":"published","published":"2025-09-24T10:58:58Z","modified":"2026-10-30T21:56:10.473433967Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7766-1","title":"linux-aws-6.8, linux-gcp-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-21961, CVE-2025-21895, CVE-2025-21934, CVE-2025-21898,\nCVE-2024-58090, CVE-2025-21999, CVE-2025-22004, CVE-2025-21966,\nCVE-2025-21922, CVE-2025-21920, CVE-2025-21911, CVE-2025-21885,\nCVE-2025-21912, CVE-2025-21996, CVE-2025-21924, CVE-2025-21914,\nCVE-2025-21936, CVE-2025-21944, CVE-2025-21877, CVE-2025-21909,\nCVE-2025-21986, CVE-2025-21890, CVE-2025-22009, CVE-2025-21905,\nCVE-2025-21969, CVE-2025-21935, CVE-2025-21917, CVE-2025-22008,\nCVE-2025-21994, CVE-2025-21980, CVE-2025-22014, CVE-2025-21915,\nCVE-2025-21991, CVE-2025-22015, CVE-2025-21875, CVE-2025-21975,\nCVE-2025-21878, CVE-2025-21930, CVE-2025-21967, CVE-2025-21908,\nCVE-2025-22007, CVE-2025-21899, CVE-2025-21950, CVE-2025-21959,\nCVE-2025-21937, CVE-2025-22010, CVE-2025-21945, CVE-2025-21997,\nCVE-2025-21992, CVE-2025-22003, CVE-2025-22013, CVE-2025-21963,\nCVE-2025-22001, CVE-2025-21927, CVE-2025-21894, CVE-2025-21960,\nCVE-2025-21956, CVE-2025-21948, CVE-2025-21929, CVE-2025-21919,\nCVE-2025-21972, CVE-2025-21883, CVE-2025-21880, CVE-2025-21976,\nCVE-2025-22005, CVE-2025-22016, CVE-2025-21978, CVE-2025-21873,\nCVE-2025-21925, CVE-2025-21904, CVE-2025-21928, CVE-2025-21892,\nCVE-2025-21891, CVE-2025-21995, CVE-2025-21968, CVE-2025-21982,\nCVE-2025-21918, CVE-2025-21889, CVE-2025-21970, CVE-2025-21910,\nCVE-2025-21913, CVE-2025-21926, CVE-2025-21955, CVE-2025-21947,\nCVE-2025-21979, CVE-2025-21981, CVE-2025-22011, CVE-2025-21888,\nCVE-2025-37889, CVE-2025-21957, CVE-2025-21977, CVE-2025-21903,\nCVE-2025-21946, CVE-2025-21941, CVE-2025-21964, CVE-2025-21951,\nCVE-2025-21962, CVE-2025-22017, CVE-2025-21872, CVE-2025-21881,\nCVE-2025-21916)\n","status":"published","published":"2025-09-24T11:08:38Z","modified":"2026-10-30T21:56:07.667368874Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7767-1","title":"linux-realtime vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-21966, CVE-2025-21895, CVE-2025-21944, CVE-2025-21986,\nCVE-2025-21918, CVE-2025-21873, CVE-2025-21963, CVE-2025-21929,\nCVE-2025-21995, CVE-2025-22017, CVE-2025-21991, CVE-2025-21960,\nCVE-2025-21946, CVE-2025-21976, CVE-2025-21922, CVE-2025-21925,\nCVE-2025-21903, CVE-2025-21978, CVE-2025-21979, CVE-2025-22016,\nCVE-2025-21936, CVE-2025-21997, CVE-2025-21992, CVE-2025-21920,\nCVE-2025-21875, CVE-2025-21934, CVE-2025-21919, CVE-2025-21972,\nCVE-2025-22001, CVE-2025-21981, CVE-2025-21910, CVE-2025-21969,\nCVE-2025-22010, CVE-2025-21908, CVE-2025-21957, CVE-2025-22009,\nCVE-2025-21927, CVE-2025-21930, CVE-2025-21994, CVE-2025-21980,\nCVE-2025-21885, CVE-2025-21967, CVE-2025-21899, CVE-2025-21890,\nCVE-2025-21948, CVE-2025-21964, CVE-2025-21911, CVE-2025-21982,\nCVE-2025-21883, CVE-2025-21913, CVE-2025-21917, CVE-2025-21905,\nCVE-2025-21968, CVE-2025-22013, CVE-2025-22005, CVE-2025-21916,\nCVE-2025-21880, CVE-2025-21881, CVE-2025-22003, CVE-2025-21892,\nCVE-2025-21937, CVE-2025-21970, CVE-2025-22004, CVE-2025-21950,\nCVE-2025-21924, CVE-2025-21894, CVE-2025-21904, CVE-2025-21915,\nCVE-2025-21889, CVE-2025-21912, CVE-2025-21909, CVE-2025-21888,\nCVE-2025-21935, CVE-2025-22008, CVE-2025-37889, CVE-2025-21878,\nCVE-2025-21926, CVE-2025-22011, CVE-2025-21962, CVE-2025-22007,\nCVE-2025-21941, CVE-2025-21898, CVE-2025-21956, CVE-2025-22015,\nCVE-2025-21961, CVE-2025-21872, CVE-2025-21891, CVE-2025-21947,\nCVE-2025-21955, CVE-2025-21877, CVE-2025-21996, CVE-2025-21977,\nCVE-2025-21945, CVE-2025-21914, CVE-2025-21975, CVE-2024-58090,\nCVE-2025-21959, CVE-2025-22014, CVE-2025-21951, CVE-2025-21928,\nCVE-2025-21999)\n","status":"published","published":"2025-09-24T11:27:06Z","modified":"2026-10-30T21:56:05.783004554Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7767-2","title":"linux-realtime-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-21964, CVE-2025-21890, CVE-2025-21934, CVE-2025-21929,\nCVE-2025-21922, CVE-2025-21970, CVE-2025-21913, CVE-2025-21937,\nCVE-2025-21872, CVE-2025-21972, CVE-2025-21892, CVE-2025-21991,\nCVE-2025-21967, CVE-2025-21894, CVE-2025-21881, CVE-2025-21885,\nCVE-2025-21999, CVE-2025-21978, CVE-2025-22001, CVE-2025-21979,\nCVE-2025-21951, CVE-2025-22003, CVE-2025-21963, CVE-2025-21936,\nCVE-2025-21891, CVE-2025-21941, CVE-2025-21895, CVE-2025-21982,\nCVE-2025-21919, CVE-2025-21961, CVE-2025-21946, CVE-2025-21889,\nCVE-2025-21899, CVE-2025-21873, CVE-2025-37889, CVE-2025-22008,\nCVE-2025-21969, CVE-2025-21957, CVE-2025-21925, CVE-2025-21945,\nCVE-2025-21927, CVE-2025-21878, CVE-2025-21995, CVE-2025-21981,\nCVE-2025-21956, CVE-2025-21909, CVE-2025-21955, CVE-2025-21918,\nCVE-2025-21960, CVE-2025-21915, CVE-2025-21992, CVE-2025-21914,\nCVE-2025-21877, CVE-2025-21875, CVE-2025-21928, CVE-2025-22013,\nCVE-2025-22014, CVE-2025-21950, CVE-2025-21948, CVE-2025-21912,\nCVE-2025-21944, CVE-2025-22004, CVE-2025-22009, CVE-2025-21968,\nCVE-2025-21888, CVE-2025-21980, CVE-2025-21911, CVE-2025-22017,\nCVE-2025-21975, CVE-2025-21930, CVE-2025-21947, CVE-2025-21908,\nCVE-2025-21994, CVE-2024-58090, CVE-2025-21910, CVE-2025-21959,\nCVE-2025-21977, CVE-2025-21903, CVE-2025-22016, CVE-2025-21976,\nCVE-2025-21898, CVE-2025-21986, CVE-2025-22011, CVE-2025-21905,\nCVE-2025-22015, CVE-2025-21996, CVE-2025-21966, CVE-2025-21883,\nCVE-2025-22010, CVE-2025-21904, CVE-2025-21916, CVE-2025-21935,\nCVE-2025-21924, CVE-2025-22005, CVE-2025-21962, CVE-2025-21917,\nCVE-2025-21920, CVE-2025-21997, CVE-2025-21880, CVE-2025-21926,\nCVE-2025-22007)\n","status":"published","published":"2025-09-25T14:30:46Z","modified":"2026-10-30T21:56:06.173073166Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7779-1","title":"linux-ibm, linux-ibm-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-22017, CVE-2025-22003, CVE-2025-22009, CVE-2025-22015,\nCVE-2025-21934, CVE-2025-21908, CVE-2025-21885, CVE-2025-21979,\nCVE-2025-21887, CVE-2025-21922, CVE-2025-21944, CVE-2025-21905,\nCVE-2025-21969, CVE-2025-21904, CVE-2025-21926, CVE-2025-21951,\nCVE-2025-21997, CVE-2025-21920, CVE-2025-21994, CVE-2025-21977,\nCVE-2025-21976, CVE-2025-21975, CVE-2025-21972, CVE-2025-22013,\nCVE-2025-21894, CVE-2025-21963, CVE-2025-21978, CVE-2025-38569,\nCVE-2025-21936, CVE-2025-21873, CVE-2025-22010, CVE-2025-21981,\nCVE-2025-22005, CVE-2025-21959, CVE-2025-21929, CVE-2025-21927,\nCVE-2025-21966, CVE-2025-22008, CVE-2025-21957, CVE-2025-21970,\nCVE-2025-21968, CVE-2025-21889, CVE-2025-22047, CVE-2025-21881,\nCVE-2025-21956, CVE-2025-22011, CVE-2025-21986, CVE-2025-21892,\nCVE-2025-21964, CVE-2025-21899, CVE-2025-21877, CVE-2025-21875,\nCVE-2025-21912, CVE-2025-22001, CVE-2025-38350, CVE-2025-21991,\nCVE-2025-21930, CVE-2025-21962, CVE-2025-21880, CVE-2024-57996,\nCVE-2025-21914, CVE-2025-22014, CVE-2025-21888, CVE-2025-21955,\nCVE-2025-21937, CVE-2025-21924, CVE-2025-21895, CVE-2025-21947,\nCVE-2025-21946, CVE-2025-21878, CVE-2025-21918, CVE-2025-21913,\nCVE-2025-21945, CVE-2025-37752, CVE-2025-21935, CVE-2025-21950,\nCVE-2025-21960, CVE-2024-58090, CVE-2025-21992, CVE-2025-21961,\nCVE-2025-21948, CVE-2025-21982, CVE-2025-21910, CVE-2025-21909,\nCVE-2025-21925, CVE-2025-37889, CVE-2025-21967, CVE-2025-21898,\nCVE-2025-22007, CVE-2025-21995, CVE-2025-22016, CVE-2025-21891,\nCVE-2025-21911, CVE-2025-21890, CVE-2025-21999, CVE-2025-22004,\nCVE-2025-21915, CVE-2025-21996, CVE-2025-21980, CVE-2025-21903,\nCVE-2025-21916, CVE-2025-21941, CVE-2025-21928, CVE-2025-21919,\nCVE-2025-21883, CVE-2025-21872, CVE-2025-21917)\n","status":"published","published":"2025-09-25T14:19:06Z","modified":"2026-10-30T21:56:05.767705174Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7790-1","title":"linux-raspi vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-21944, CVE-2025-21927, CVE-2025-21996, CVE-2025-21928,\nCVE-2025-21888, CVE-2025-21995, CVE-2025-21929, CVE-2025-21873,\nCVE-2025-21875, CVE-2025-21894, CVE-2025-21878, CVE-2025-21977,\nCVE-2024-58090, CVE-2025-21872, CVE-2025-21905, CVE-2025-21963,\nCVE-2025-21991, CVE-2025-21947, CVE-2025-21924, CVE-2025-21899,\nCVE-2025-21992, CVE-2025-21909, CVE-2025-21920, CVE-2025-21917,\nCVE-2025-21972, CVE-2025-21997, CVE-2025-21999, CVE-2025-21895,\nCVE-2025-22013, CVE-2025-21936, CVE-2025-21881, CVE-2025-21956,\nCVE-2025-22010, CVE-2025-22015, CVE-2025-21959, CVE-2025-21980,\nCVE-2025-22017, CVE-2025-22005, CVE-2025-21935, CVE-2025-21911,\nCVE-2025-21914, CVE-2025-22001, CVE-2025-21913, CVE-2025-22007,\nCVE-2025-21966, CVE-2025-21962, CVE-2025-21908, CVE-2025-21910,\nCVE-2025-22014, CVE-2025-22016, CVE-2025-21957, CVE-2025-21968,\nCVE-2025-21986, CVE-2025-21981, CVE-2025-21880, CVE-2025-21950,\nCVE-2025-21982, CVE-2025-21976, CVE-2025-21979, CVE-2025-21912,\nCVE-2025-21951, CVE-2025-21994, CVE-2025-21946, CVE-2025-21955,\nCVE-2025-21898, CVE-2025-21960, CVE-2025-21883, CVE-2025-21970,\nCVE-2025-21891, CVE-2025-21919, CVE-2025-21964, CVE-2025-21926,\nCVE-2025-21877, CVE-2025-21903, CVE-2025-21978, CVE-2025-21885,\nCVE-2025-21948, CVE-2025-21930, CVE-2025-22009, CVE-2025-21918,\nCVE-2025-21890, CVE-2025-21925, CVE-2025-22003, CVE-2025-22008,\nCVE-2025-21934, CVE-2025-21961, CVE-2025-22004, CVE-2025-21941,\nCVE-2025-21915, CVE-2025-21967, CVE-2025-21904, CVE-2025-21916,\nCVE-2025-37889, CVE-2025-21922, CVE-2025-21892, CVE-2025-21975,\nCVE-2025-21945, CVE-2025-21889, CVE-2025-21937, CVE-2025-21969)\n","status":"published","published":"2025-10-01T14:52:45Z","modified":"2026-10-30T21:56:05.389787523Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7800-1","title":"linux-raspi-realtime vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Ext4 file system;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Packet sockets;\n  - Network traffic control;\n  - Switch device API;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n(CVE-2025-38617, CVE-2025-21898, CVE-2025-21996, CVE-2025-21903,\nCVE-2025-21980, CVE-2025-22007, CVE-2025-22010, CVE-2025-37756,\nCVE-2025-21970, CVE-2025-21930, CVE-2025-37785, CVE-2025-22015,\nCVE-2025-21927, CVE-2025-21914, CVE-2025-21963, CVE-2025-22004,\nCVE-2025-21934, CVE-2025-21986, CVE-2025-22008, CVE-2025-21895,\nCVE-2025-21928, CVE-2025-21899, CVE-2025-21891, CVE-2025-21925,\nCVE-2025-21979, CVE-2025-21945, CVE-2025-22005, CVE-2025-21880,\nCVE-2025-21946, CVE-2025-21957, CVE-2025-21890, CVE-2025-21955,\nCVE-2025-21961, CVE-2025-21935, CVE-2025-21959, CVE-2025-37889,\nCVE-2025-21894, CVE-2024-58090, CVE-2025-22001, CVE-2025-21924,\nCVE-2025-21909, CVE-2025-22009, CVE-2025-21892, CVE-2025-21976,\nCVE-2025-21875, CVE-2025-21915, CVE-2025-21967, CVE-2025-38618,\nCVE-2025-21918, CVE-2025-21881, CVE-2025-21872, CVE-2025-21873,\nCVE-2025-21960, CVE-2025-22014, CVE-2025-21885, CVE-2025-21950,\nCVE-2025-21981, CVE-2025-21917, CVE-2025-21913, CVE-2025-21972,\nCVE-2025-21975, CVE-2025-21977, CVE-2025-21951, CVE-2025-21962,\nCVE-2025-38500, CVE-2025-21916, CVE-2025-21888, CVE-2025-21910,\nCVE-2025-21994, CVE-2025-21904, CVE-2025-21947, CVE-2025-21995,\nCVE-2025-22013, CVE-2025-21920, CVE-2025-21997, CVE-2025-21905,\nCVE-2025-21941, CVE-2025-21877, CVE-2025-21878, CVE-2025-21937,\nCVE-2025-21966, CVE-2025-21919, CVE-2025-21992, CVE-2025-21948,\nCVE-2025-21922, CVE-2025-21911, CVE-2025-21926, CVE-2025-21908,\nCVE-2025-21956, CVE-2025-22003, CVE-2025-21969, CVE-2025-21999,\nCVE-2025-38477, CVE-2025-21944, CVE-2025-21936, CVE-2025-21978,\nCVE-2025-21991, CVE-2025-21912, CVE-2025-21968, CVE-2025-22017,\nCVE-2025-21883, CVE-2025-21964, CVE-2025-21889, CVE-2025-21982,\nCVE-2025-22016, CVE-2025-21929)\n","status":"published","published":"2025-10-02T13:46:50Z","modified":"2026-11-03T14:33:50.836449527Z","updated_at":"2026-11-03T15:17:23.859376Z"},{"id":"USN-7801-1","title":"linux-hwe-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Ext4 file system;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Packet sockets;\n  - Network traffic control;\n  - Switch device API;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n(CVE-2025-21928, CVE-2025-21976, CVE-2025-21890, CVE-2025-21929,\nCVE-2025-21960, CVE-2025-21978, CVE-2025-21937, CVE-2025-21908,\nCVE-2025-21999, CVE-2025-22015, CVE-2025-21967, CVE-2025-21913,\nCVE-2025-21898, CVE-2025-37756, CVE-2025-38617, CVE-2025-21927,\nCVE-2025-21956, CVE-2025-21979, CVE-2025-21955, CVE-2025-21895,\nCVE-2025-21969, CVE-2025-21877, CVE-2025-21936, CVE-2025-22001,\nCVE-2025-37889, CVE-2025-21875, CVE-2025-21888, CVE-2025-21911,\nCVE-2025-21904, CVE-2025-21878, CVE-2025-21961, CVE-2025-22013,\nCVE-2025-21986, CVE-2025-21915, CVE-2025-21889, CVE-2025-21903,\nCVE-2025-21909, CVE-2025-21950, CVE-2025-21885, CVE-2025-21966,\nCVE-2025-21873, CVE-2025-21883, CVE-2025-21946, CVE-2025-22003,\nCVE-2025-22014, CVE-2024-58090, CVE-2025-21891, CVE-2025-21962,\nCVE-2025-21948, CVE-2025-21924, CVE-2025-22017, CVE-2025-21975,\nCVE-2025-21920, CVE-2025-21972, CVE-2025-21964, CVE-2025-21917,\nCVE-2025-21894, CVE-2025-21982, CVE-2025-21945, CVE-2025-21996,\nCVE-2025-21995, CVE-2025-21912, CVE-2025-21910, CVE-2025-21980,\nCVE-2025-21951, CVE-2025-21934, CVE-2025-21994, CVE-2025-37785,\nCVE-2025-22009, CVE-2025-38618, CVE-2025-21992, CVE-2025-21930,\nCVE-2025-21941, CVE-2025-21916, CVE-2025-22004, CVE-2025-21919,\nCVE-2025-21880, CVE-2025-21963, CVE-2025-21914, CVE-2025-21981,\nCVE-2025-38500, CVE-2025-22005, CVE-2025-21959, CVE-2025-21899,\nCVE-2025-21926, CVE-2025-21968, CVE-2025-21944, CVE-2025-22016,\nCVE-2025-38477, CVE-2025-22008, CVE-2025-21925, CVE-2025-21997,\nCVE-2025-21935, CVE-2025-21947, CVE-2025-22010, CVE-2025-21977,\nCVE-2025-21922, CVE-2025-21881, CVE-2025-21970, CVE-2025-22007,\nCVE-2025-21991, CVE-2025-21918, CVE-2025-21905, CVE-2025-22011,\nCVE-2025-21872, CVE-2025-21957, CVE-2025-21892)\n","status":"published","published":"2025-10-02T13:56:04Z","modified":"2026-11-03T14:33:53.834134216Z","updated_at":"2026-11-03T15:17:23.859376Z"},{"id":"USN-7801-2","title":"linux-oracle vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Ext4 file system;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Packet sockets;\n  - Network traffic control;\n  - Switch device API;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n(CVE-2025-21911, CVE-2025-21937, CVE-2025-21951, CVE-2025-21948,\nCVE-2025-22017, CVE-2025-21982, CVE-2025-21927, CVE-2025-21935,\nCVE-2025-21944, CVE-2025-21917, CVE-2025-21895, CVE-2025-21966,\nCVE-2025-21975, CVE-2025-21945, CVE-2025-21964, CVE-2025-22001,\nCVE-2025-21955, CVE-2025-21980, CVE-2025-21925, CVE-2025-21957,\nCVE-2025-22003, CVE-2025-21999, CVE-2025-21969, CVE-2025-21885,\nCVE-2025-21996, CVE-2025-21883, CVE-2025-21908, CVE-2025-21978,\nCVE-2025-21894, CVE-2025-21929, CVE-2025-21910, CVE-2025-21979,\nCVE-2025-21961, CVE-2025-21915, CVE-2025-21916, CVE-2025-22008,\nCVE-2025-37785, CVE-2025-21873, CVE-2025-21922, CVE-2025-21936,\nCVE-2025-22015, CVE-2025-22016, CVE-2025-21913, CVE-2025-22009,\nCVE-2025-21928, CVE-2025-21899, CVE-2025-22007, CVE-2025-21898,\nCVE-2025-21946, CVE-2025-21920, CVE-2025-22005, CVE-2025-21872,\nCVE-2025-21962, CVE-2025-21888, CVE-2025-21934, CVE-2025-38618,\nCVE-2025-22010, CVE-2025-22014, CVE-2024-58090, CVE-2025-21941,\nCVE-2025-21968, CVE-2025-21972, CVE-2025-21977, CVE-2025-22013,\nCVE-2025-21959, CVE-2025-21919, CVE-2025-21950, CVE-2025-21926,\nCVE-2025-21892, CVE-2025-21880, CVE-2025-21994, CVE-2025-21909,\nCVE-2025-21976, CVE-2025-21956, CVE-2025-21947, CVE-2025-21981,\nCVE-2025-21877, CVE-2025-21995, CVE-2025-21918, CVE-2025-38500,\nCVE-2025-22004, CVE-2025-37756, CVE-2025-21970, CVE-2025-21891,\nCVE-2025-21924, CVE-2025-38477, CVE-2025-21878, CVE-2025-21881,\nCVE-2025-21904, CVE-2025-21960, CVE-2025-21992, CVE-2025-37889,\nCVE-2025-21997, CVE-2025-38617, CVE-2025-21963, CVE-2025-21890,\nCVE-2025-21903, CVE-2025-21912, CVE-2025-22011, CVE-2025-21889,\nCVE-2025-21991, CVE-2025-21914, CVE-2025-21905, CVE-2025-21986,\nCVE-2025-21930, CVE-2025-21875, CVE-2025-21967)\n","status":"published","published":"2025-10-06T14:26:41Z","modified":"2026-11-03T14:33:40.423654283Z","updated_at":"2026-11-03T15:17:29.920737Z"},{"id":"USN-7801-3","title":"linux-oracle-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Ext4 file system;\n  - Network file system (NFS) client;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Packet sockets;\n  - Network traffic control;\n  - Switch device API;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n(CVE-2025-21969, CVE-2025-21976, CVE-2025-21898, CVE-2025-21981,\nCVE-2025-21929, CVE-2025-21935, CVE-2025-22009, CVE-2025-21967,\nCVE-2025-21963, CVE-2025-21944, CVE-2025-21970, CVE-2025-21962,\nCVE-2025-21912, CVE-2025-38477, CVE-2025-21977, CVE-2025-21881,\nCVE-2025-21980, CVE-2025-22013, CVE-2025-21946, CVE-2025-22008,\nCVE-2025-21975, CVE-2025-21878, CVE-2025-21891, CVE-2025-22014,\nCVE-2025-21916, CVE-2025-21950, CVE-2024-58090, CVE-2025-21917,\nCVE-2025-21885, CVE-2025-21914, CVE-2025-21873, CVE-2025-21959,\nCVE-2025-21964, CVE-2025-22010, CVE-2025-21928, CVE-2025-21872,\nCVE-2025-21908, CVE-2025-22004, CVE-2025-21895, CVE-2025-21991,\nCVE-2025-21936, CVE-2025-21982, CVE-2025-21996, CVE-2025-21888,\nCVE-2025-21961, CVE-2025-21894, CVE-2025-21966, CVE-2025-21941,\nCVE-2025-21890, CVE-2025-21930, CVE-2025-21883, CVE-2025-21903,\nCVE-2025-21922, CVE-2025-21945, CVE-2025-22005, CVE-2025-22016,\nCVE-2025-21926, CVE-2025-21927, CVE-2025-21924, CVE-2025-21919,\nCVE-2025-21997, CVE-2025-21986, CVE-2025-21905, CVE-2025-21995,\nCVE-2025-38617, CVE-2025-21875, CVE-2025-21910, CVE-2025-21920,\nCVE-2025-21913, CVE-2025-21909, CVE-2025-21911, CVE-2025-22001,\nCVE-2025-21972, CVE-2025-37785, CVE-2025-21889, CVE-2025-21979,\nCVE-2025-21918, CVE-2025-22011, CVE-2025-37756, CVE-2025-21992,\nCVE-2025-38618, CVE-2025-21915, CVE-2025-38500, CVE-2025-21978,\nCVE-2025-21947, CVE-2025-21951, CVE-2025-21994, CVE-2025-21999,\nCVE-2025-21960, CVE-2025-37889, CVE-2025-21892, CVE-2025-21934,\nCVE-2025-21877, CVE-2025-22007, CVE-2025-22003, CVE-2025-22017,\nCVE-2025-21925, CVE-2025-21880, CVE-2025-21957, CVE-2025-21899,\nCVE-2025-21956, CVE-2025-21948, CVE-2025-21955, CVE-2025-21937,\nCVE-2025-21968, CVE-2025-21904, CVE-2025-22015)\n","status":"published","published":"2025-10-15T14:36:18Z","modified":"2026-11-03T14:33:51.423891131Z","updated_at":"2026-11-03T15:17:23.859376Z"},{"id":"USN-7802-1","title":"linux-azure, linux-azure-6.8 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Network file system (NFS) client;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - Switch device API;\n  - Wireless networking;\n  - eXpress Data Path;\n(CVE-2025-21935, CVE-2025-21967, CVE-2025-21908, CVE-2025-22004,\nCVE-2025-21926, CVE-2025-21927, CVE-2025-21995, CVE-2025-21895,\nCVE-2025-21936, CVE-2025-21948, CVE-2025-21969, CVE-2025-21972,\nCVE-2025-21951, CVE-2025-22017, CVE-2025-21962, CVE-2025-21917,\nCVE-2025-22013, CVE-2025-21991, CVE-2025-22009, CVE-2025-22016,\nCVE-2024-57996, CVE-2025-21966, CVE-2025-21947, CVE-2025-21928,\nCVE-2025-21959, CVE-2025-21910, CVE-2025-21957, CVE-2025-21978,\nCVE-2025-21887, CVE-2025-37954, CVE-2025-21996, CVE-2025-21979,\nCVE-2025-37889, CVE-2025-21930, CVE-2025-21980, CVE-2025-21878,\nCVE-2025-21918, CVE-2025-21889, CVE-2024-58090, CVE-2025-22011,\nCVE-2025-21955, CVE-2025-21904, CVE-2025-21894, CVE-2025-21892,\nCVE-2025-21945, CVE-2025-21994, CVE-2025-21986, CVE-2025-21912,\nCVE-2025-21968, CVE-2025-21976, CVE-2025-21898, CVE-2025-21875,\nCVE-2025-21964, CVE-2025-21963, CVE-2025-21960, CVE-2025-21999,\nCVE-2025-21997, CVE-2025-21916, CVE-2025-21891, CVE-2025-21920,\nCVE-2025-21909, CVE-2025-21944, CVE-2025-21883, CVE-2025-22005,\nCVE-2025-22007, CVE-2025-21911, CVE-2025-21992, CVE-2025-21919,\nCVE-2025-22003, CVE-2025-21915, CVE-2025-21970, CVE-2025-21903,\nCVE-2025-21899, CVE-2025-21880, CVE-2025-21956, CVE-2025-21934,\nCVE-2025-21925, CVE-2025-21941, CVE-2025-21977, CVE-2025-21975,\nCVE-2025-21913, CVE-2025-21981, CVE-2025-21872, CVE-2025-37752,\nCVE-2025-22008, CVE-2025-21905, CVE-2025-21888, CVE-2025-38350,\nCVE-2025-21922, CVE-2025-21937, CVE-2025-21950, CVE-2025-21924,\nCVE-2025-22014, CVE-2025-22001, CVE-2025-21885, CVE-2025-21881,\nCVE-2025-21929, CVE-2025-21914, CVE-2025-21877, CVE-2025-22015,\nCVE-2025-21961, CVE-2025-22010, CVE-2025-21982, CVE-2025-21890,\nCVE-2025-21946, CVE-2025-21873)\n","status":"published","published":"2025-10-02T15:30:41Z","modified":"2026-11-03T14:34:01.830263072Z","updated_at":"2026-11-03T15:17:16.577329Z"},{"id":"USN-7809-1","title":"linux-azure-nvidia vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - I2C subsystem;\n  - InfiniBand drivers;\n  - Multiple devices driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Pin controllers subsystem;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - QCOM SoC drivers;\n  - UFS subsystem;\n  - USB DSL drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Framebuffer layer;\n  - ACRN Hypervisor Service Module driver;\n  - Ext4 file system;\n  - Network file system (NFS) client;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - SoC audio core drivers;\n  - Perf events;\n  - Tracing infrastructure;\n  - Memory management;\n  - 802.1Q VLAN protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - Bluetooth subsystem;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - Netfilter;\n  - Packet sockets;\n  - Network traffic control;\n  - Switch device API;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n(CVE-2025-21976, CVE-2025-21890, CVE-2025-38617, CVE-2025-21945,\nCVE-2025-21878, CVE-2025-21925, CVE-2025-21927, CVE-2025-21997,\nCVE-2025-21919, CVE-2025-21979, CVE-2025-21899, CVE-2025-21955,\nCVE-2025-21967, CVE-2024-57996, CVE-2025-22014, CVE-2025-21956,\nCVE-2025-21887, CVE-2025-37785, CVE-2025-21935, CVE-2024-58090,\nCVE-2025-21975, CVE-2025-21969, CVE-2025-21914, CVE-2025-21963,\nCVE-2025-21934, CVE-2025-21872, CVE-2025-21961, CVE-2025-38244,\nCVE-2025-21908, CVE-2025-21920, CVE-2025-21980, CVE-2025-21904,\nCVE-2025-22008, CVE-2025-21911, CVE-2025-21880, CVE-2025-21928,\nCVE-2025-21885, CVE-2025-21913, CVE-2025-37752, CVE-2025-22015,\nCVE-2025-38500, CVE-2025-22013, CVE-2025-21970, CVE-2025-21877,\nCVE-2025-21916, CVE-2025-21889, CVE-2025-21982, CVE-2025-22001,\nCVE-2025-22007, CVE-2025-22016, CVE-2025-21981, CVE-2025-37756,\nCVE-2025-21962, CVE-2025-21891, CVE-2025-21968, CVE-2025-21936,\nCVE-2025-21995, CVE-2025-21922, CVE-2025-21930, CVE-2025-21894,\nCVE-2025-38477, CVE-2025-22011, CVE-2025-21991, CVE-2025-38618,\nCVE-2025-22003, CVE-2025-21903, CVE-2025-21986, CVE-2025-21941,\nCVE-2025-21951, CVE-2025-22004, CVE-2025-21929, CVE-2025-21917,\nCVE-2025-21915, CVE-2025-21977, CVE-2025-21875, CVE-2025-21959,\nCVE-2025-22017, CVE-2025-21881, CVE-2025-21937, CVE-2025-22009,\nCVE-2025-38350, CVE-2025-21944, CVE-2025-21918, CVE-2025-21947,\nCVE-2025-21883, CVE-2025-21892, CVE-2025-21966, CVE-2025-21950,\nCVE-2025-21926, CVE-2025-37954, CVE-2025-21999, CVE-2025-21992,\nCVE-2025-21948, CVE-2025-21960, CVE-2025-21924, CVE-2025-21873,\nCVE-2025-21895, CVE-2025-21946, CVE-2025-37889, CVE-2025-21978,\nCVE-2025-21905, CVE-2025-22010, CVE-2025-38683, CVE-2025-21898,\nCVE-2025-21910, CVE-2025-21994, CVE-2025-21996, CVE-2025-21972,\nCVE-2025-21912, CVE-2025-22005, CVE-2025-21909, CVE-2025-21957,\nCVE-2025-21964)\n","status":"published","published":"2025-10-08T08:52:19Z","modified":"2026-11-03T14:33:55.640013958Z","updated_at":"2026-11-03T15:17:23.859376Z"}]}}