{"id":"CVE-2023-52597","aliases":["ALSA-2024:2394","BELL-CVE-2023-52597","DEBIAN-CVE-2023-52597","DLA-3842-1","DSA-5681-1","EUVD-2023-57221","GHSA-6j3q-64jm-q33g","OESA-2024-1482","OESA-2024-1483","OESA-2024-1484","OESA-2024-1485","OESA-2024-1486","OESA-2024-1487","RHSA-2024:2394","RHSA-2024:2950","RHSA-2024:3138","RXSA-2024:3138","SUSE-SU-2024:0856-1","SUSE-SU-2024:0857-1","SUSE-SU-2024:0925-1","SUSE-SU-2024:0926-1","SUSE-SU-2024:0975-1","SUSE-SU-2024:0976-1","SUSE-SU-2024:1320-1","SUSE-SU-2024:1321-1","SUSE-SU-2024:1466-1","SUSE-SU-2024:1480-1","SUSE-SU-2024:1490-1","UBUNTU-CVE-2023-52597","USN-6688-1","USN-6766-1","USN-6766-2","USN-6766-3","USN-6767-1","USN-6767-2","USN-6795-1","USN-6818-1","USN-6818-3","USN-6818-4","USN-6819-1","USN-6819-3","USN-6819-4","USN-6828-1"],"status":"published","title":"KVM: s390: fix setting of fpc register","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: fix setting of fpc register\n\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\n\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\n\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\n\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\n\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\n\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.","severity":{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-10","score":0.00233,"percentile":0.14244,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2024-03-06T06:45:26Z","modified":"2026-11-10T02:48:58Z","fixes":[{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.81-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.12.41-r0"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["4.19.307","5.4.269","5.10.210","5.15.149","6.1.77","6.6.16","6.7.4"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.82-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.7.7-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.7.7-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","fixed_in":["5.4.0-1124.134~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","fixed_in":["5.4.0-1129.136~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","fixed_in":["5.4.0-1128.137~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","fixed_in":["5.4.0-181.201~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","fixed_in":["5.4.0-1071.76~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","fixed_in":["5.4.0-1123.132~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","fixed_in":["5.4.0-1108.120~18.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux","fixed_in":["5.4.0-181.201"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","fixed_in":["5.4.0-1124.134"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1061.67~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","fixed_in":["5.4.0-1129.136"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1063.72~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","fixed_in":["5.4.0-1084.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","fixed_in":["5.4.0-1128.137"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1059.67~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","fixed_in":["5.4.0-1091.95"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","fixed_in":["5.15.0-1044.51~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-106.116~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","fixed_in":["5.4.0-1071.76"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1054.57~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1058.64~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","fixed_in":["5.4.0-1036.37"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","fixed_in":["5.4.0-1112.119"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-106.116~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1027.27~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","fixed_in":["5.4.0-1123.132"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1059.65~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","fixed_in":["5.4.0-1108.120"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1057.61~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.4.0-1043.47"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","fixed_in":["5.4.0-1124.134+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","fixed_in":["5.4.0-1129.136+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","fixed_in":["5.4.0-1098.108"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","fixed_in":["5.4.0-1128.137+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-106.116"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1061.67"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1063.72"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","fixed_in":["6.5.0-1022.23~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","fixed_in":["5.15.0-1063.72.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1059.67"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","fixed_in":["6.5.0-1022.24~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1058.63"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1044.51"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","fixed_in":["6.5.0-41.41~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1054.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1057.63"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1058.63"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-106.116"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","fixed_in":["6.5.0-41.41.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1054.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","fixed_in":["6.5.0-1021.22"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1026.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1015.15"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","fixed_in":["6.1.0-1035.35"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","fixed_in":["6.5.0-1024.25"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1059.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","fixed_in":["6.5.0-1024.24~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1054.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","fixed_in":["6.5.0-40.40.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","fixed_in":["6.5.0-1015.16~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1030.34"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1043.45"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1054.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1062.70"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1061.67+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1063.72+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-106.116+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1059.67+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2001.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"AlmaLinux:9","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.3.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"AlmaLinux:9","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-427.13.1.el9_4"}]}],"bundled":61},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.74-r0"},{"fixed":"6.1.81-r0"}]}]},{"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.6.100-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.13.0"},{"fixed":"4.19.307"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.20.0"},{"fixed":"5.4.269"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.210"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.149"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.77"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.16"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.7.4"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.82-1"}]}],"versions":["6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.7.7-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.7.7-1"}]}]},{"source":"osv","ecosystem":"Debian:10","package":"linux-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.216-1~deb10u1"}]}],"versions":["5.10.136-1~deb10u1","5.10.136-1~deb10u2","5.10.136-1~deb10u3","5.10.149-2~deb10u1","5.10.158-2~deb10u1","5.10.162-1~deb10u1","5.10.178-3~deb10u1","5.10.179-1~deb10u1","5.10.179-3~deb10u1","5.10.179-5~deb10u1","5.10.197-1~deb10u1","5.10.205-2~deb10u1","5.10.209-2~deb10u1"],"bundled":344},{"source":"osv","ecosystem":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.216-1"}]}],"versions":["5.10.103-1","5.10.103-1~bpo10+1","5.10.106-1","5.10.113-1","5.10.120-1","5.10.120-1~bpo10+1","5.10.127-1","5.10.127-2","5.10.127-2~bpo10+1","5.10.136-1","5.10.140-1","5.10.148-1","5.10.149-1","5.10.149-2","5.10.158-1","5.10.158-2","5.10.162-1","5.10.178-1","5.10.178-2","5.10.178-3","5.10.179-1","5.10.179-2","5.10.179-3","5.10.179-4","5.10.179-5","5.10.191-1","5.10.197-1","5.10.205-1","5.10.205-2","5.10.209-1","5.10.209-2","5.10.46-4","5.10.46-5","5.10.70-1","5.10.70-1~bpo10+1","5.10.84-1","5.10.92-1","5.10.92-1~bpo10+1","5.10.92-2"],"bundled":246},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-196.0.0.109.oe2203sp3"}]}],"bundled":27},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.90-2404.2.0.0246.oe1"}]}],"bundled":46},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.90-2404.2.0.0273.oe2003sp4"}]}],"bundled":46},{"source":"osv","ecosystem":"openEuler:22.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-60.134.0.161.oe2203"}]}],"bundled":23},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-136.72.0.152.oe2203sp1"}]}],"bundled":24},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-153.51.0.129.oe2203sp2"}]}],"bundled":25},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"kernel-zfcpdump-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-64k-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::nfv","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.3.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"libperf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::realtime","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.14.0-427.13.1.el9_4"}]}],"bundled":341},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::nfv","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::realtime","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.rt7.342.el8_10"}]}],"bundled":49},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"kernel-zfcpdump-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"bpftool-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-debuginfo-common-x86_64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::crb","package":"python3-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.el8_10"}]}],"bundled":163},{"source":"osv","ecosystem":"Rocky Linux:8","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.18.0-553.123.1.el8_10.cloud.0.1"}]}],"bundled":160},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.161.1"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.161.1"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.161.1"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.161.1"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-livepatch-SLE15-SP3_Update_42","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150300.7.3.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2.150300.18.90.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.1"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2.150300.18.90.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.1"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2.150300.18.90.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.1"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2.150300.18.90.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2.150300.18.90.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2.150300.18.90.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.2"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.153.1"}]}],"bundled":67},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_54","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.7.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.2"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.201.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP2","package":"kernel-livepatch-SLE15-SP2_Update_46","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150200.5.3.2"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1.150200.9.93.2"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1.150200.9.93.2"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1.150200.9.93.2"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150200.24.183.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.173.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.173.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.173.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.173.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.173.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-16.173.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 12 SP5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-10.171.1"}]}],"bundled":47},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 12 SP5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-10.171.1"}]}],"bundled":47},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 12 SP5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-10.171.1"}]}],"bundled":47},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 12 SP5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-10.171.1"}]}],"bundled":47},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.76.1"}]}],"bundled":70},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.76.1"}]}],"bundled":70},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.76.1"}]}],"bundled":70},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.76.1"}]}],"bundled":70},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.3","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.76.1"}]}],"bundled":70},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.4","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.76.1"}]}],"bundled":70},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-livepatch-SLE15-SP4_Update_25","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150400.9.5.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1"}]}],"bundled":77},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.116.1.150400.24.54.5"}]}],"bundled":77},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5-RT_Update_13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":149},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.47.1"}]}],"bundled":149},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1.150500.6.25.7"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1.150500.6.25.7"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.7.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1.150500.6.25.7"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.59.1"}]}],"bundled":150},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.48.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.48.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.48.1"}]}],"bundled":183},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.48.1"}]}],"bundled":183},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.48.1"}]}],"bundled":183},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.33.48.1"}]}],"bundled":183},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.11.0-12.19","3.12.0-1.3","3.12.0-2.5","3.12.0-2.7","3.12.0-3.8","3.12.0-3.9","3.12.0-4.10","3.12.0-4.12","3.12.0-5.13","3.12.0-7.15","3.13.0-1.16","3.13.0-2.17","3.13.0-3.18","3.13.0-4.19","3.13.0-5.20","3.13.0-6.23","3.13.0-7.25","3.13.0-7.26","3.13.0-8.27","3.13.0-8.28","3.13.0-10.30","3.13.0-11.31","3.13.0-12.32","3.13.0-13.33","3.13.0-14.34","3.13.0-15.35","3.13.0-16.36","3.13.0-17.37","3.13.0-18.38","3.13.0-19.39","3.13.0-19.40","3.13.0-20.42","3.13.0-21.43","3.13.0-22.44","3.13.0-23.45","3.13.0-24.46","3.13.0-24.47","3.13.0-27.50","3.13.0-29.53","3.13.0-30.54","3.13.0-30.55","3.13.0-32.57","3.13.0-33.58","3.13.0-34.60","3.13.0-35.62","3.13.0-36.63","3.13.0-37.64","3.13.0-39.66","3.13.0-40.69","3.13.0-41.70","3.13.0-43.72","3.13.0-44.73","3.13.0-45.74","3.13.0-46.75","3.13.0-46.76","3.13.0-46.77","3.13.0-46.79","3.13.0-48.80","3.13.0-49.81","3.13.0-49.83","3.13.0-51.84","3.13.0-52.85","3.13.0-52.86","3.13.0-53.88","3.13.0-53.89","3.13.0-54.91","3.13.0-55.92","3.13.0-55.94","3.13.0-57.95","3.13.0-58.97","3.13.0-59.98","3.13.0-61.100","3.13.0-62.102","3.13.0-63.103","3.13.0-65.105","3.13.0-65.106","3.13.0-66.108","3.13.0-67.110","3.13.0-68.111","3.13.0-70.113","3.13.0-71.114","3.13.0-73.116","3.13.0-74.118","3.13.0-76.120","3.13.0-77.121","3.13.0-79.123","3.13.0-83.127","3.13.0-85.129","3.13.0-86.130","3.13.0-86.131","3.13.0-87.133","3.13.0-88.135","3.13.0-91.138","3.13.0-92.139","3.13.0-93.140","3.13.0-95.142","3.13.0-96.143","3.13.0-98.145","3.13.0-100.147","3.13.0-101.148","3.13.0-103.150","3.13.0-105.152","3.13.0-106.153","3.13.0-107.154","3.13.0-108.155","3.13.0-109.156","3.13.0-110.157","3.13.0-111.158","3.13.0-112.159","3.13.0-113.160","3.13.0-115.162","3.13.0-116.163","3.13.0-117.164","3.13.0-119.166","3.13.0-121.170","3.13.0-123.172","3.13.0-125.174","3.13.0-126.175","3.13.0-128.177","3.13.0-129.178","3.13.0-132.181","3.13.0-133.182","3.13.0-135.184","3.13.0-137.186","3.13.0-139.188","3.13.0-141.190","3.13.0-142.191","3.13.0-143.192","3.13.0-144.193","3.13.0-145.194","3.13.0-147.196","3.13.0-149.199","3.13.0-151.201","3.13.0-153.203","3.13.0-155.205","3.13.0-156.206","3.13.0-157.207","3.13.0-158.208","3.13.0-160.210","3.13.0-161.211","3.13.0-162.212","3.13.0-163.213","3.13.0-164.214","3.13.0-165.215","3.13.0-166.216","3.13.0-167.217","3.13.0-168.218","3.13.0-169.219","3.13.0-170.220","3.13.0-171.222","3.13.0-172.223","3.13.0-173.224","3.13.0-174.225","3.13.0-175.226","3.13.0-176.227","3.13.0-180.231","3.13.0-181.232","3.13.0-182.233","3.13.0-183.234","3.13.0-184.235","3.13.0-185.236","3.13.0-186.237","3.13.0-187.238","3.13.0-188.239","3.13.0-189.240","3.13.0-190.241","3.13.0-191.242","3.13.0-192.243","3.13.0-193.244","3.13.0-194.245","3.13.0-195.246","3.13.0-196.247","3.13.0-197.248","3.13.0-198.249","3.13.0-199.250","3.13.0-200.251","3.13.0-201.252","3.13.0-202.253","3.13.0-203.254","3.13.0-204.255","3.13.0-205.256","3.13.0-206.257","3.13.0-207.258","3.13.0-208.259","3.13.0-209.260","3.13.0-210.261","3.13.0-211.262","3.13.0-212.263","3.13.0-214.265","3.13.0-215.266","3.13.0-217.268","3.13.0-218.269","3.13.0-219.270","3.13.0-220.271"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1002.2","4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1011.11","4.4.0-1012.12","4.4.0-1014.14","4.4.0-1016.16","4.4.0-1017.17","4.4.0-1019.19","4.4.0-1022.22","4.4.0-1023.23","4.4.0-1024.25","4.4.0-1025.26","4.4.0-1027.30","4.4.0-1028.31","4.4.0-1029.32","4.4.0-1031.34","4.4.0-1032.35","4.4.0-1034.37","4.4.0-1036.39","4.4.0-1037.40","4.4.0-1038.41","4.4.0-1039.42","4.4.0-1040.43","4.4.0-1042.45","4.4.0-1044.47","4.4.0-1045.48","4.4.0-1046.50","4.4.0-1048.52","4.4.0-1050.54","4.4.0-1052.56","4.4.0-1054.58","4.4.0-1055.59","4.4.0-1056.60","4.4.0-1058.62","4.4.0-1059.63","4.4.0-1060.64","4.4.0-1061.65","4.4.0-1062.66","4.4.0-1064.68","4.4.0-1065.69","4.4.0-1066.70","4.4.0-1067.71","4.4.0-1073.77","4.4.0-1074.78","4.4.0-1075.79","4.4.0-1076.80","4.4.0-1077.81","4.4.0-1078.82","4.4.0-1081.85","4.4.0-1082.86","4.4.0-1083.87","4.4.0-1085.89","4.4.0-1086.90","4.4.0-1087.91","4.4.0-1088.92","4.4.0-1090.94","4.4.0-1091.95","4.4.0-1092.96","4.4.0-1093.97","4.4.0-1094.99","4.4.0-1095.100","4.4.0-1096.101","4.4.0-1097.102","4.4.0-1098.103","4.4.0-1099.104","4.4.0-1101.106","4.4.0-1102.107","4.4.0-1103.108","4.4.0-1104.109","4.4.0-1107.113","4.4.0-1109.115","4.4.0-1110.116","4.4.0-1111.117","4.4.0-1112.118","4.4.0-1113.119","4.4.0-1114.120","4.4.0-1115.121","4.4.0-1116.122","4.4.0-1117.123","4.4.0-1118.124","4.4.0-1119.125","4.4.0-1120.126","4.4.0-1121.127","4.4.0-1122.128","4.4.0-1123.129","4.4.0-1124.130","4.4.0-1125.131","4.4.0-1127.133","4.4.0-1128.134","4.4.0-1129.135","4.4.0-1130.136","4.4.0-1131.137","4.4.0-1133.139","4.4.0-1134.140","4.4.0-1135.141","4.4.0-1136.142","4.4.0-1137.143","4.4.0-1138.144","4.4.0-1139.145","4.4.0-1140.146","4.4.0-1141.147","4.4.0-1142.148","4.4.0-1143.149","4.4.0-1144.150","4.4.0-1145.151","4.4.0-1146.152","4.4.0-1147.153","4.4.0-1148.154","4.4.0-1149.155","4.4.0-1150.156","4.4.0-1151.157","4.4.0-1152.158","4.4.0-1153.159","4.4.0-1154.160","4.4.0-1155.161","4.4.0-1156.162","4.4.0-1157.163","4.4.0-1158.164","4.4.0-1159.165","4.4.0-1160.166","4.4.0-1161.167","4.4.0-1162.168"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1023.24~14.04.1","4.15.0-1030.31~14.04.1","4.15.0-1031.32~14.04.1","4.15.0-1032.33~14.04.2","4.15.0-1035.36~14.04.2","4.15.0-1036.38~14.04.2","4.15.0-1037.39~14.04.2","4.15.0-1039.41~14.04.2","4.15.0-1040.44~14.04.1","4.15.0-1041.45~14.04.1","4.15.0-1042.46~14.04.1","4.15.0-1045.49~14.04.1","4.15.0-1046.50~14.04.1","4.15.0-1047.51~14.04.1","4.15.0-1049.54~14.04.1","4.15.0-1050.55~14.04.1","4.15.0-1051.56~14.04.1","4.15.0-1052.57~14.04.1","4.15.0-1055.60~14.04.1","4.15.0-1056.61~14.04.1","4.15.0-1057.62~14.04.1","4.15.0-1059.64~14.04.1","4.15.0-1060.65~14.04.1","4.15.0-1061.66~14.04.1","4.15.0-1063.68~14.04.1","4.15.0-1064.69~14.04.1","4.15.0-1066.71~14.04.1","4.15.0-1067.72~14.04.1","4.15.0-1069.74~14.04.1","4.15.0-1071.76~14.04.1","4.15.0-1074.79~14.04.1","4.15.0-1077.82~14.04.1","4.15.0-1082.92~14.04.1","4.15.0-1083.93~14.04.1","4.15.0-1089.99~14.04.1","4.15.0-1091.101~14.04.1","4.15.0-1092.102~14.04.1","4.15.0-1093.103~14.04.1","4.15.0-1095.105~14.04.1","4.15.0-1096.106~14.04.1","4.15.0-1098.109~14.04.1","4.15.0-1100.111~14.04.1","4.15.0-1102.113~14.04.1","4.15.0-1103.114~14.04.1","4.15.0-1106.118~14.04.1","4.15.0-1108.120~14.04.1","4.15.0-1109.121~14.04.1","4.15.0-1110.122~14.04.1","4.15.0-1111.123~14.04.1","4.15.0-1112.124~14.04.1","4.15.0-1113.126~14.04.1","4.15.0-1114.127~14.04.1","4.15.0-1115.128~14.04.1","4.15.0-1118.131~14.04.1","4.15.0-1121.134~14.04.1","4.15.0-1122.135~14.04.1","4.15.0-1123.136~14.04.1","4.15.0-1124.137~14.04.1","4.15.0-1125.138~14.04.1","4.15.0-1126.139~14.04.1","4.15.0-1127.140~14.04.1","4.15.0-1129.142~14.04.1","4.15.0-1130.143~14.04.1","4.15.0-1131.144~14.04.1","4.15.0-1133.146~14.04.1","4.15.0-1134.147~14.04.1","4.15.0-1136.149~14.04.1","4.15.0-1137.150~14.04.1","4.15.0-1138.151~14.04.1","4.15.0-1139.152~14.04.1","4.15.0-1142.156~14.04.1","4.15.0-1145.160~14.04.1","4.15.0-1146.161~14.04.1","4.15.0-1149.164~14.04.1","4.15.0-1150.165~14.04.1","4.15.0-1151.166~14.04.1","4.15.0-1153.168~14.04.1","4.15.0-1157.172~14.04.2","4.15.0-1158.173~14.04.1","4.15.0-1159.174~14.04.1","4.15.0-1162.177~14.04.1","4.15.0-1163.178~14.04.1","4.15.0-1164.179~14.04.1","4.15.0-1165.180~14.04.1","4.15.0-1166.181~14.04.1","4.15.0-1167.182~14.04.1","4.15.0-1168.183~14.04.1","4.15.0-1169.184~14.04.1","4.15.0-1170.185~14.04.1","4.15.0-1171.186~14.04.1","4.15.0-1172.187~14.04.1","4.15.0-1173.188~14.04.1","4.15.0-1174.189~14.04.1","4.15.0-1175.190~14.04.1","4.15.0-1176.191~14.04.1","4.15.0-1177.192~14.04.1","4.15.0-1178.193~14.04.1","4.15.0-1179.194~14.04.1","4.15.0-1180.195~14.04.1","4.15.0-1181.196~14.04.1","4.15.0-1182.197~14.04.1","4.15.0-1183.198~14.04.1","4.15.0-1184.199~14.04.1","4.15.0-1185.200~14.04.1","4.15.0-1186.201~14.04.1","4.15.0-1187.202~14.04.1","4.15.0-1188.203~14.04.1","4.15.0-1189.204~14.04.1","4.15.0-1190.205~14.04.1","4.15.0-1191.206~14.04.1","4.15.0-1192.207~14.04.1","4.15.0-1193.208~14.04.1","4.15.0-1194.209~14.04.1","4.15.0-1195.210~14.04.1","4.15.0-1196.211~14.04.1","4.15.0-1197.212~14.04.1","4.15.0-1199.214~14.04.1","4.15.0-1200.215~14.04.1","4.15.0-1201.216~14.04.1","4.15.0-1202.217~14.04.1","4.15.0-1205.220~14.04.1","4.15.0-1206.221~14.04.1","4.15.0-1207.222~14.04.1","4.15.0-1208.223~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-13.29~14.04.1","4.4.0-14.30~14.04.2","4.4.0-15.31~14.04.1","4.4.0-18.34~14.04.1","4.4.0-21.37~14.04.1","4.4.0-22.39~14.04.1","4.4.0-22.40~14.04.1","4.4.0-24.43~14.04.1","4.4.0-28.47~14.04.1","4.4.0-31.50~14.04.1","4.4.0-34.53~14.04.1","4.4.0-36.55~14.04.1","4.4.0-38.57~14.04.1","4.4.0-42.62~14.04.1","4.4.0-45.66~14.04.1","4.4.0-47.68~14.04.1","4.4.0-51.72~14.04.1","4.4.0-53.74~14.04.1","4.4.0-57.78~14.04.1","4.4.0-59.80~14.04.1","4.4.0-62.83~14.04.1","4.4.0-63.84~14.04.2","4.4.0-64.85~14.04.1","4.4.0-66.87~14.04.1","4.4.0-67.88~14.04.1","4.4.0-70.91~14.04.1","4.4.0-71.92~14.04.1","4.4.0-72.93~14.04.1","4.4.0-75.96~14.04.1","4.4.0-78.99~14.04.2","4.4.0-79.100~14.04.1","4.4.0-81.104~14.04.1","4.4.0-83.106~14.04.1","4.4.0-87.110~14.04.1","4.4.0-89.112~14.04.1","4.4.0-91.114~14.04.1","4.4.0-92.115~14.04.1","4.4.0-93.116~14.04.1","4.4.0-96.119~14.04.1","4.4.0-97.120~14.04.1","4.4.0-98.121~14.04.1","4.4.0-101.124~14.04.1","4.4.0-103.126~14.04.1","4.4.0-104.127~14.04.1","4.4.0-108.131~14.04.1","4.4.0-109.132~14.04.1","4.4.0-111.134~14.04.1","4.4.0-112.135~14.04.1","4.4.0-116.140~14.04.1","4.4.0-119.143~14.04.1","4.4.0-121.145~14.04.1","4.4.0-124.148~14.04.1","4.4.0-127.153~14.04.1","4.4.0-128.154~14.04.1","4.4.0-130.156~14.04.1","4.4.0-131.157~14.04.1","4.4.0-133.159~14.04.1","4.4.0-134.160~14.04.1","4.4.0-135.161~14.04.1","4.4.0-137.163~14.04.1","4.4.0-138.164~14.04.1","4.4.0-139.165~14.04.1","4.4.0-140.166~14.04.1","4.4.0-141.167~14.04.1","4.4.0-142.168~14.04.1","4.4.0-143.169~14.04.2","4.4.0-144.170~14.04.1","4.4.0-146.172~14.04.1","4.4.0-148.174~14.04.1","4.4.0-150.176~14.04.1","4.4.0-151.178~14.04.1","4.4.0-154.181~14.04.1","4.4.0-157.185~14.04.1","4.4.0-159.187~14.04.1","4.4.0-161.189~14.04.1","4.4.0-164.192~14.04.1","4.4.0-165.193~14.04.1","4.4.0-166.195~14.04.1","4.4.0-168.197~14.04.1","4.4.0-169.198~14.04.1","4.4.0-170.199~14.04.1","4.4.0-171.200~14.04.1","4.4.0-173.203~14.04.1","4.4.0-174.204~14.04.1","4.4.0-176.206~14.04.1","4.4.0-177.207~14.04.1","4.4.0-178.208~14.04.1","4.4.0-179.209~14.04.1","4.4.0-184.214~14.04.1","4.4.0-185.215~14.04.1","4.4.0-186.216~14.04.1","4.4.0-187.217~14.04.1","4.4.0-189.219~14.04.1","4.4.0-190.220~14.04.1","4.4.0-193.224~14.04.1","4.4.0-194.226~14.04.1","4.4.0-197.229~14.04.1","4.4.0-198.230~14.04.1","4.4.0-200.232~14.04.1","4.4.0-201.233~14.04.1","4.4.0-203.235~14.04.1","4.4.0-204.236~14.04.1","4.4.0-206.238~14.04.1","4.4.0-208.240~14.04.1","4.4.0-209.241~14.04.1","4.4.0-210.242~14.04.1","4.4.0-211.243~14.04.1","4.4.0-212.244~14.04.1","4.4.0-213.245~14.04.1","4.4.0-214.246~14.04.1","4.4.0-215.247~14.04.1","4.4.0-218.251~14.04.1","4.4.0-219.252~14.04.1","4.4.0-221.254~14.04.1","4.4.0-222.255~14.04.1","4.4.0-223.256~14.04.1","4.4.0-224.257~14.04.1","4.4.0-227.261~14.04.1","4.4.0-229.263~14.04.1","4.4.0-230.264~14.04.1","4.4.0-231.265~14.04.1","4.4.0-233.267~14.04.1","4.4.0-234.268~14.04.1","4.4.0-235.269~14.04.1","4.4.0-236.270~14.04.1","4.4.0-237.271~14.04.1","4.4.0-239.273~14.04.1","4.4.0-240.274~14.04.1","4.4.0-241.275~14.04.1","4.4.0-242.276~14.04.1","4.4.0-243.277~14.04.1","4.4.0-244.278~14.04.1","4.4.0-245.279~14.04.1","4.4.0-246.280~14.04.1","4.4.0-248.282~14.04.1","4.4.0-250.284~14.04.1","4.4.0-251.285~14.04.1","4.4.0-252.286~14.04.1","4.4.0-253.287~14.04.1","4.4.0-254.288~14.04.1","4.4.0-256.290~14.04.1","4.4.0-257.291~14.04.1","4.4.0-258.292~14.04.2","4.4.0-259.293~14.04.1","4.4.0-260.294~14.04.1","4.4.0-261.295~14.04.1","4.4.0-262.296~14.04.1","4.4.0-263.297~14.04.1","4.4.0-264.298~14.04.1","4.4.0-266.300~14.04.1","4.4.0-267.301~14.04.1","4.4.0-268.302~14.04.1","4.4.0-269.303~14.04.1","4.4.0-270.304~14.04.1","4.4.0-271.305~14.04.1","4.4.0-272.306~14.04.1","4.4.0-273.307~14.04.1","4.4.0-274.308~14.04.1","4.4.0-276.310~14.04.1","4.4.0-277.311~14.04.1","4.4.0-278.312~14.04.1","4.4.0-279.313~14.04.1","4.4.0-280.314~14.04.1","4.4.0-281.315~14.04.1","4.4.0-283.317~14.04.1","4.4.0-284.318~14.04.1","4.4.0-287.321~14.04.1","4.4.0-288.322~14.04.1","4.4.0-289.323~14.04.1","4.4.0-290.324~14.04.1","4.4.0-291.325~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.2.0-16.19","4.2.0-17.21","4.2.0-19.23","4.3.0-1.10","4.3.0-2.11","4.3.0-5.16","4.3.0-6.17","4.3.0-7.18","4.4.0-2.16","4.4.0-4.19","4.4.0-6.21","4.4.0-7.22","4.4.0-8.23","4.4.0-9.24","4.4.0-10.25","4.4.0-11.26","4.4.0-12.28","4.4.0-13.29","4.4.0-14.30","4.4.0-15.31","4.4.0-16.32","4.4.0-17.33","4.4.0-18.34","4.4.0-21.37","4.4.0-22.39","4.4.0-22.40","4.4.0-24.43","4.4.0-28.47","4.4.0-31.50","4.4.0-34.53","4.4.0-36.55","4.4.0-38.57","4.4.0-42.62","4.4.0-43.63","4.4.0-45.66","4.4.0-47.68","4.4.0-51.72","4.4.0-53.74","4.4.0-57.78","4.4.0-59.80","4.4.0-62.83","4.4.0-63.84","4.4.0-64.85","4.4.0-65.86","4.4.0-66.87","4.4.0-67.88","4.4.0-70.91","4.4.0-71.92","4.4.0-72.93","4.4.0-75.96","4.4.0-77.98","4.4.0-78.99","4.4.0-79.100","4.4.0-81.104","4.4.0-83.106","4.4.0-87.110","4.4.0-89.112","4.4.0-91.114","4.4.0-92.115","4.4.0-93.116","4.4.0-96.119","4.4.0-97.120","4.4.0-98.121","4.4.0-101.124","4.4.0-103.126","4.4.0-104.127","4.4.0-108.131","4.4.0-109.132","4.4.0-112.135","4.4.0-116.140","4.4.0-119.143","4.4.0-121.145","4.4.0-122.146","4.4.0-124.148","4.4.0-127.153","4.4.0-128.154","4.4.0-130.156","4.4.0-131.157","4.4.0-133.159","4.4.0-134.160","4.4.0-135.161","4.4.0-137.163","4.4.0-138.164","4.4.0-139.165","4.4.0-140.166","4.4.0-141.167","4.4.0-142.168","4.4.0-143.169","4.4.0-145.171","4.4.0-146.172","4.4.0-148.174","4.4.0-150.176","4.4.0-151.178","4.4.0-154.181","4.4.0-157.185","4.4.0-159.187","4.4.0-161.189","4.4.0-164.192","4.4.0-165.193","4.4.0-166.195","4.4.0-168.197","4.4.0-169.198","4.4.0-170.199","4.4.0-171.200","4.4.0-173.203","4.4.0-174.204","4.4.0-176.206","4.4.0-177.207","4.4.0-178.208","4.4.0-179.209","4.4.0-184.214","4.4.0-185.215","4.4.0-186.216","4.4.0-187.217","4.4.0-189.219","4.4.0-190.220","4.4.0-193.224","4.4.0-194.226","4.4.0-197.229","4.4.0-198.230","4.4.0-200.232","4.4.0-201.233","4.4.0-203.235","4.4.0-204.236","4.4.0-206.238","4.4.0-208.240","4.4.0-209.241","4.4.0-210.242","4.4.0-211.243","4.4.0-212.244","4.4.0-213.245","4.4.0-214.246","4.4.0-216.249","4.4.0-217.250","4.4.0-218.251","4.4.0-219.252","4.4.0-221.254","4.4.0-222.255","4.4.0-223.256","4.4.0-224.257","4.4.0-227.261","4.4.0-229.263","4.4.0-230.264","4.4.0-231.265","4.4.0-233.267","4.4.0-234.268","4.4.0-235.269","4.4.0-236.270","4.4.0-237.271","4.4.0-239.273","4.4.0-240.274","4.4.0-241.275","4.4.0-242.276","4.4.0-243.277","4.4.0-244.278","4.4.0-245.279","4.4.0-246.280","4.4.0-248.282","4.4.0-250.284","4.4.0-251.285","4.4.0-252.286","4.4.0-253.287","4.4.0-254.288","4.4.0-256.290","4.4.0-257.291","4.4.0-258.292","4.4.0-259.293","4.4.0-260.294","4.4.0-261.295","4.4.0-262.296","4.4.0-263.297","4.4.0-264.298","4.4.0-266.300","4.4.0-267.301","4.4.0-268.302","4.4.0-269.303","4.4.0-270.304","4.4.0-271.305","4.4.0-272.306","4.4.0-273.307","4.4.0-274.308","4.4.0-276.310","4.4.0-277.311","4.4.0-278.312","4.4.0-279.313","4.4.0-280.314","4.4.0-281.315","4.4.0-283.317","4.4.0-284.318","4.4.0-287.321","4.4.0-288.322","4.4.0-289.323","4.4.0-290.324","4.4.0-291.325"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1001.10","4.4.0-1003.12","4.4.0-1004.13","4.4.0-1007.16","4.4.0-1009.18","4.4.0-1011.20","4.4.0-1012.21","4.4.0-1013.22","4.4.0-1016.25","4.4.0-1017.26","4.4.0-1018.27","4.4.0-1020.29","4.4.0-1022.31","4.4.0-1026.35","4.4.0-1028.37","4.4.0-1030.39","4.4.0-1031.40","4.4.0-1032.41","4.4.0-1035.44","4.4.0-1037.46","4.4.0-1038.47","4.4.0-1039.48","4.4.0-1041.50","4.4.0-1043.52","4.4.0-1044.53","4.4.0-1047.56","4.4.0-1048.57","4.4.0-1049.58","4.4.0-1050.59","4.4.0-1052.61","4.4.0-1054.63","4.4.0-1055.64","4.4.0-1057.66","4.4.0-1060.69","4.4.0-1061.70","4.4.0-1062.71","4.4.0-1063.72","4.4.0-1065.75","4.4.0-1066.76","4.4.0-1067.77","4.4.0-1069.79","4.4.0-1070.80","4.4.0-1072.82","4.4.0-1073.83","4.4.0-1074.84","4.4.0-1075.85","4.4.0-1077.87","4.4.0-1079.89","4.4.0-1081.91","4.4.0-1083.93","4.4.0-1084.94","4.4.0-1085.96","4.4.0-1087.98","4.4.0-1088.99","4.4.0-1090.101","4.4.0-1092.103","4.4.0-1094.105","4.4.0-1095.106","4.4.0-1096.107","4.4.0-1098.109","4.4.0-1099.110","4.4.0-1100.111","4.4.0-1101.112","4.4.0-1102.113","4.4.0-1104.115","4.4.0-1105.116","4.4.0-1106.117","4.4.0-1107.118","4.4.0-1109.120","4.4.0-1110.121","4.4.0-1111.123","4.4.0-1112.124","4.4.0-1113.126","4.4.0-1114.127","4.4.0-1117.131","4.4.0-1118.132","4.4.0-1119.133","4.4.0-1121.135","4.4.0-1122.136","4.4.0-1123.137","4.4.0-1124.138","4.4.0-1126.140","4.4.0-1127.141","4.4.0-1128.142","4.4.0-1129.143","4.4.0-1130.144","4.4.0-1131.145","4.4.0-1132.146","4.4.0-1133.147","4.4.0-1134.148","4.4.0-1135.149","4.4.0-1137.151","4.4.0-1138.152","4.4.0-1139.153","4.4.0-1140.154","4.4.0-1143.158","4.4.0-1145.160","4.4.0-1146.161","4.4.0-1147.162","4.4.0-1148.163","4.4.0-1150.165","4.4.0-1151.166","4.4.0-1152.167","4.4.0-1153.168","4.4.0-1154.169","4.4.0-1155.170","4.4.0-1156.171","4.4.0-1157.172","4.4.0-1158.173","4.4.0-1159.174","4.4.0-1160.175","4.4.0-1161.176","4.4.0-1162.177","4.4.0-1163.178","4.4.0-1164.179","4.4.0-1165.180","4.4.0-1166.181","4.4.0-1167.182","4.4.0-1168.183","4.4.0-1169.184","4.4.0-1171.186","4.4.0-1172.187","4.4.0-1173.188","4.4.0-1174.189","4.4.0-1175.190","4.4.0-1176.191","4.4.0-1177.192","4.4.0-1178.193","4.4.0-1179.194","4.4.0-1180.195","4.4.0-1181.196","4.4.0-1182.197","4.4.0-1183.198","4.4.0-1184.199","4.4.0-1185.200","4.4.0-1186.201","4.4.0-1187.202","4.4.0-1188.203","4.4.0-1189.204","4.4.0-1190.205","4.4.0-1191.206","4.4.0-1192.207","4.4.0-1193.208","4.4.0-1194.209","4.4.0-1195.210","4.4.0-1196.211","4.4.0-1197.212","4.4.0-1198.213","4.4.0-1199.214","4.4.0-1200.215"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.31~16.04.1","4.15.0-1031.33~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1035.37~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1039.41~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43~16.04.1","4.15.0-1043.45~16.04.1","4.15.0-1044.46~16.04.1","4.15.0-1045.47~16.04.1","4.15.0-1047.49~16.04.1","4.15.0-1048.50~16.04.1","4.15.0-1050.52~16.04.1","4.15.0-1051.53~16.04.1","4.15.0-1052.54~16.04.1","4.15.0-1054.56~16.04.1","4.15.0-1056.58~16.04.1","4.15.0-1057.59~16.04.1","4.15.0-1058.60~16.04.1","4.15.0-1060.62~16.04.1","4.15.0-1063.67~16.04.1","4.15.0-1065.69~16.04.1","4.15.0-1066.70~16.04.1","4.15.0-1067.71~16.04.1","4.15.0-1073.77~16.04.1","4.15.0-1074.78~16.04.1","4.15.0-1079.83~16.04.1","4.15.0-1080.84~16.04.1","4.15.0-1082.86~16.04.1","4.15.0-1083.87~16.04.1","4.15.0-1085.90~16.04.1","4.15.0-1088.93~16.04.1","4.15.0-1090.95~16.04.1","4.15.0-1091.96~16.04.1","4.15.0-1093.99~16.04.1","4.15.0-1094.101~16.04.1","4.15.0-1095.102~16.04.1","4.15.0-1096.103~16.04.1","4.15.0-1097.104~16.04.1","4.15.0-1098.105~16.04.1","4.15.0-1099.106~16.04.1","4.15.0-1102.109~16.04.1","4.15.0-1103.110~16.04.1","4.15.0-1106.113~16.04.1","4.15.0-1109.116~16.04.1","4.15.0-1110.117~16.04.1","4.15.0-1111.118~16.04.1","4.15.0-1112.119~16.04.1","4.15.0-1113.120~16.04.1","4.15.0-1115.122~16.04.1","4.15.0-1116.123~16.04.1","4.15.0-1118.125~16.04.1","4.15.0-1119.126~16.04.2","4.15.0-1120.128~16.04.1","4.15.0-1123.132~16.04.1","4.15.0-1124.133~16.04.1","4.15.0-1126.135~16.04.2","4.15.0-1127.136~16.04.1","4.15.0-1128.137~16.04.1","4.15.0-1130.139~16.04.1","4.15.0-1133.143~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.154~16.04.1","4.15.0-1143.155~16.04.1","4.15.0-1146.158~16.04.2","4.15.0-1147.159~16.04.1","4.15.0-1148.160~16.04.1","4.15.0-1151.164~16.04.1","4.15.0-1153.166~16.04.1","4.15.0-1154.167~16.04.1","4.15.0-1155.168~16.04.1","4.15.0-1156.169~16.04.1","4.15.0-1157.170~16.04.1","4.15.0-1158.171~16.04.1","4.15.0-1159.172~16.04.1","4.15.0-1160.173~16.04.1","4.15.0-1161.174~16.04.1","4.15.0-1162.175~16.04.1","4.15.0-1163.176~16.04.1","4.15.0-1164.177~16.04.1","4.15.0-1165.178~16.04.1","4.15.0-1166.179~16.04.1","4.15.0-1167.180~16.04.1","4.15.0-1168.181~16.04.1","4.15.0-1169.182~16.04.1","4.15.0-1170.183~16.04.1","4.15.0-1172.185~16.04.1","4.15.0-1173.186~16.04.1","4.15.0-1174.187~16.04.1","4.15.0-1175.188~16.04.1","4.15.0-1176.189~16.04.1","4.15.0-1177.190~16.04.1","4.15.0-1178.191~16.04.1","4.15.0-1179.192~16.04.1","4.15.0-1180.193~16.04.1","4.15.0-1181.194~16.04.1","4.15.0-1182.195~16.04.1","4.15.0-1183.196~16.04.1","4.15.0-1184.197~16.04.1","4.15.0-1185.198~16.04.1","4.15.0-1186.199~16.04.1","4.15.0-1187.200~16.04.1","4.15.0-1188.201~16.04.1","4.15.0-1189.202~16.04.1","4.15.0-1190.203~16.04.1","4.15.0-1191.204~16.04.1","4.15.0-1192.205~16.04.1","4.15.0-1194.207~16.04.1","4.15.0-1195.208~16.04.1","4.15.0-1196.209~16.04.1","4.15.0-1197.210~16.04.1","4.15.0-1198.211~16.04.1","4.15.0-1199.212~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.11.0-1009.9","4.11.0-1011.11","4.11.0-1013.13","4.11.0-1014.14","4.11.0-1015.15","4.11.0-1016.16","4.13.0-1005.7","4.13.0-1006.8","4.13.0-1007.9","4.13.0-1009.12","4.13.0-1011.14","4.13.0-1012.15","4.13.0-1014.17","4.13.0-1016.19","4.13.0-1018.21","4.15.0-1013.13~16.04.2","4.15.0-1014.14~16.04.1","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1","4.15.0-1022.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1025.26~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1030.31~16.04.1","4.15.0-1031.32~16.04.1","4.15.0-1032.33~16.04.1","4.15.0-1035.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1039.43","4.15.0-1040.44","4.15.0-1041.45","4.15.0-1042.46","4.15.0-1045.49","4.15.0-1046.50","4.15.0-1047.51","4.15.0-1049.54","4.15.0-1050.55","4.15.0-1051.56","4.15.0-1052.57","4.15.0-1055.60","4.15.0-1056.61","4.15.0-1057.62","4.15.0-1059.64","4.15.0-1060.65","4.15.0-1061.66","4.15.0-1063.68","4.15.0-1064.69","4.15.0-1066.71","4.15.0-1067.72","4.15.0-1069.74","4.15.0-1071.76","4.15.0-1075.80","4.15.0-1077.82","4.15.0-1082.92~16.04.1","4.15.0-1083.93~16.04.1","4.15.0-1089.99~16.04.1","4.15.0-1091.101~16.04.1","4.15.0-1092.102~16.04.1","4.15.0-1093.103~16.04.1","4.15.0-1095.105~16.04.1","4.15.0-1096.106~16.04.1","4.15.0-1098.109~16.04.1","4.15.0-1100.111~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1103.114~16.04.1","4.15.0-1106.118~16.04.1","4.15.0-1108.120~16.04.1","4.15.0-1109.121~16.04.1","4.15.0-1110.122~16.04.1","4.15.0-1111.123~16.04.1","4.15.0-1112.124~16.04.1","4.15.0-1113.126~16.04.1","4.15.0-1114.127~16.04.1","4.15.0-1115.128~16.04.1","4.15.0-1118.131~16.04.1","4.15.0-1121.134~16.04.1","4.15.0-1122.135~16.04.1","4.15.0-1123.136~16.04.1","4.15.0-1124.137~16.04.1","4.15.0-1125.138~16.04.1","4.15.0-1126.139~16.04.1","4.15.0-1127.140~16.04.1","4.15.0-1129.142~16.04.1","4.15.0-1130.143~16.04.1","4.15.0-1131.144~16.04.1","4.15.0-1133.146~16.04.1","4.15.0-1134.147~16.04.1","4.15.0-1136.149~16.04.1","4.15.0-1137.150~16.04.1","4.15.0-1138.151~16.04.1","4.15.0-1139.152~16.04.1","4.15.0-1142.156~16.04.1","4.15.0-1145.160~16.04.1","4.15.0-1146.161~16.04.1","4.15.0-1149.164~16.04.1","4.15.0-1150.165~16.04.1","4.15.0-1151.166~16.04.1","4.15.0-1153.168~16.04.1","4.15.0-1159.174~16.04.1","4.15.0-1162.177~16.04.1","4.15.0-1163.178~16.04.1","4.15.0-1164.179~16.04.1","4.15.0-1165.180~16.04.1","4.15.0-1166.181~16.04.1","4.15.0-1167.182~16.04.1","4.15.0-1168.183~16.04.1","4.15.0-1169.184~16.04.1","4.15.0-1170.185~16.04.1","4.15.0-1171.186~16.04.1","4.15.0-1172.187~16.04.1","4.15.0-1173.188~16.04.1","4.15.0-1174.189~16.04.1","4.15.0-1175.190~16.04.1","4.15.0-1176.191~16.04.1","4.15.0-1177.192~16.04.1","4.15.0-1178.193~16.04.1","4.15.0-1179.194~16.04.1","4.15.0-1180.195~16.04.1","4.15.0-1181.196~16.04.1","4.15.0-1182.197~16.04.1","4.15.0-1183.198~16.04.1","4.15.0-1184.199~16.04.1","4.15.0-1185.200~16.04.1","4.15.0-1186.201~16.04.1","4.15.0-1187.202~16.04.1","4.15.0-1188.203~16.04.1","4.15.0-1189.204~16.04.1","4.15.0-1190.205~16.04.1","4.15.0-1191.206~16.04.1","4.15.0-1192.207~16.04.1","4.15.0-1193.208~16.04.1","4.15.0-1194.209~16.04.1","4.15.0-1195.210~16.04.1","4.15.0-1196.211~16.04.1","4.15.0-1197.212~16.04.1","4.15.0-1200.215~16.04.1","4.15.0-1204.219~16.04.1","4.15.0-1205.220~16.04.1","4.15.0-1206.221~16.04.1","4.15.0-1208.223~16.04.1","4.15.0-1209.224~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.10.0-1004.4","4.10.0-1006.6","4.10.0-1007.7","4.10.0-1008.8","4.10.0-1009.9","4.13.0-1002.5","4.13.0-1006.9","4.13.0-1007.10","4.13.0-1008.11","4.13.0-1011.15","4.13.0-1012.16","4.13.0-1013.17","4.13.0-1015.19","4.13.0-1017.21","4.13.0-1019.23","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1","4.15.0-1018.19~16.04.2","4.15.0-1019.20~16.04.1","4.15.0-1021.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1024.25~16.04.2","4.15.0-1025.26~16.04.1","4.15.0-1026.27~16.04.1","4.15.0-1027.28~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1029.31~16.04.1","4.15.0-1030.32~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1034.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1046.49","4.15.0-1047.50","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.56","4.15.0-1055.59","4.15.0-1058.62","4.15.0-1060.64","4.15.0-1061.65","4.15.0-1071.81~16.04.1","4.15.0-1077.87~16.04.1","4.15.0-1078.88~16.04.1","4.15.0-1080.90~16.04.1","4.15.0-1081.92~16.04.1","4.15.0-1083.94~16.04.1","4.15.0-1084.95~16.04.1","4.15.0-1086.98~16.04.1","4.15.0-1087.100~16.04.1","4.15.0-1088.101~16.04.1","4.15.0-1090.103~16.04.1","4.15.0-1091.104~16.04.1","4.15.0-1092.105~16.04.1","4.15.0-1093.106~16.04.1","4.15.0-1094.107~16.04.1","4.15.0-1095.108~16.04.1","4.15.0-1096.109~16.04.1","4.15.0-1097.110~16.04.1","4.15.0-1098.111~16.04.1","4.15.0-1099.112~16.04.1","4.15.0-1100.113~16.04.1","4.15.0-1103.116~16.04.1","4.15.0-1106.120~16.04.1","4.15.0-1107.121~16.04.1","4.15.0-1108.122~16.04.1","4.15.0-1109.123~16.04.1","4.15.0-1110.124~16.04.1","4.15.0-1111.125~16.04.1","4.15.0-1112.126~16.04.1","4.15.0-1114.128~16.04.1","4.15.0-1115.129~16.04.1","4.15.0-1116.130~16.04.1","4.15.0-1118.132~16.04.1","4.15.0-1119.133~16.04.1","4.15.0-1120.134~16.04.1","4.15.0-1121.135~16.04.1","4.15.0-1122.136~16.04.1","4.15.0-1124.138~16.04.1","4.15.0-1127.142~16.04.1","4.15.0-1130.146~16.04.1","4.15.0-1131.147~16.04.1","4.15.0-1134.150~16.04.2","4.15.0-1135.151~16.04.2","4.15.0-1136.152~16.04.1","4.15.0-1137.153~16.04.1","4.15.0-1138.154~16.04.1","4.15.0-1141.157~16.04.2","4.15.0-1142.158~16.04.1","4.15.0-1143.159~16.04.1","4.15.0-1146.162~16.04.1","4.15.0-1147.163~16.04.1","4.15.0-1148.164~16.04.1","4.15.0-1149.165~16.04.1","4.15.0-1150.166~16.04.1","4.15.0-1151.167~16.04.1","4.15.0-1152.168~16.04.1","4.15.0-1153.170~16.04.1","4.15.0-1154.171~16.04.1","4.15.0-1155.172~16.04.1","4.15.0-1156.173~16.04.1","4.15.0-1157.174~16.04.1","4.15.0-1158.175~16.04.1","4.15.0-1159.176~16.04.1","4.15.0-1160.177~16.04.1","4.15.0-1161.178~16.04.1","4.15.0-1162.179~16.04.1","4.15.0-1163.180~16.04.1","4.15.0-1164.181~16.04.1","4.15.0-1165.182~16.04.1","4.15.0-1166.183~16.04.1","4.15.0-1167.184~16.04.2","4.15.0-1168.185~16.04.1","4.15.0-1169.186~16.04.1","4.15.0-1170.187~16.04.1","4.15.0-1171.188~16.04.1","4.15.0-1172.189~16.04.1","4.15.0-1173.190~16.04.1","4.15.0-1174.191~16.04.1","4.15.0-1175.192~16.04.1","4.15.0-1176.193~16.04.1","4.15.0-1177.194~16.04.1","4.15.0-1178.195~16.04.1","4.15.0-1179.196~16.04.1","4.15.0-1180.197~16.04.1","4.15.0-1181.198~16.04.1","4.15.0-1182.199~16.04.1","4.15.0-1183.200~16.04.2","4.15.0-1184.201~16.04.1","4.15.0-1185.202~16.04.1","4.15.0-1187.204~16.04.1","4.15.0-1188.205~16.04.1","4.15.0-1189.206~16.04.1","4.15.0-1190.207~16.04.1","4.15.0-1191.208~16.04.1","4.15.0-1192.209~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1","4.10.0-37.41~16.04.1","4.10.0-38.42~16.04.1","4.10.0-40.44~16.04.1","4.10.0-42.46~16.04.1","4.13.0-26.29~16.04.2","4.13.0-31.34~16.04.1","4.13.0-32.35~16.04.1","4.13.0-36.40~16.04.1","4.13.0-37.42~16.04.1","4.13.0-38.43~16.04.1","4.13.0-39.44~16.04.1","4.13.0-41.46~16.04.1","4.13.0-43.48~16.04.1","4.13.0-45.50~16.04.1","4.15.0-24.26~16.04.1","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1","4.15.0-33.36~16.04.1","4.15.0-34.37~16.04.1","4.15.0-36.39~16.04.1","4.15.0-38.41~16.04.1","4.15.0-39.42~16.04.1","4.15.0-42.45~16.04.1","4.15.0-43.46~16.04.1","4.15.0-45.48~16.04.1","4.15.0-46.49~16.04.1","4.15.0-47.50~16.04.1","4.15.0-48.51~16.04.1","4.15.0-50.54~16.04.1","4.15.0-51.55~16.04.1","4.15.0-52.56~16.04.1","4.15.0-54.58~16.04.1","4.15.0-55.60~16.04.2","4.15.0-58.64~16.04.1","4.15.0-60.67~16.04.1","4.15.0-62.69~16.04.1","4.15.0-64.73~16.04.1","4.15.0-65.74~16.04.1","4.15.0-66.75~16.04.1","4.15.0-69.78~16.04.1","4.15.0-70.79~16.04.1","4.15.0-72.81~16.04.1","4.15.0-74.83~16.04.1","4.15.0-76.86~16.04.1","4.15.0-88.88~16.04.1","4.15.0-91.92~16.04.1","4.15.0-96.97~16.04.1","4.15.0-99.100~16.04.1","4.15.0-101.102~16.04.1","4.15.0-106.107~16.04.1","4.15.0-107.108~16.04.1","4.15.0-112.113~16.04.1","4.15.0-115.116~16.04.1","4.15.0-117.118~16.04.1","4.15.0-118.119~16.04.1","4.15.0-120.122~16.04.1","4.15.0-122.124~16.04.1","4.15.0-123.126~16.04.1","4.15.0-126.129~16.04.1","4.15.0-128.131~16.04.1","4.15.0-129.132~16.04.1","4.15.0-132.136~16.04.1","4.15.0-133.137~16.04.1","4.15.0-136.140~16.04.1","4.15.0-137.141~16.04.1","4.15.0-139.143~16.04.1","4.15.0-140.144~16.04.1","4.15.0-142.146~16.04.1","4.15.0-143.147~16.04.3","4.15.0-144.148~16.04.1","4.15.0-147.151~16.04.1","4.15.0-151.157~16.04.1","4.15.0-153.160~16.04.1","4.15.0-154.161~16.04.1","4.15.0-156.163~16.04.1","4.15.0-158.166~16.04.1","4.15.0-159.167~16.04.1","4.15.0-161.169~16.04.1","4.15.0-162.170~16.04.1","4.15.0-163.171~16.04.1","4.15.0-166.174~16.04.1","4.15.0-167.175~16.04.1","4.15.0-169.177~16.04.1","4.15.0-171.180~16.04.1","4.15.0-173.182~16.04.1","4.15.0-175.184~16.04.1","4.15.0-176.185~16.04.1","4.15.0-177.186~16.04.1","4.15.0-180.189~16.04.1","4.15.0-184.194~16.04.1","4.15.0-187.198~16.04.1","4.15.0-188.199~16.04.1","4.15.0-189.200~16.04.1","4.15.0-191.202~16.04.1","4.15.0-192.203~16.04.1","4.15.0-193.204~16.04.1","4.15.0-194.205~16.04.1","4.15.0-196.207~16.04.1","4.15.0-197.208~16.04.1","4.15.0-200.211~16.04.2","4.15.0-201.212~16.04.1","4.15.0-202.213~16.04.1","4.15.0-206.217~16.04.1","4.15.0-208.219~16.04.1","4.15.0-209.220~16.04.1","4.15.0-210.221~16.04.1","4.15.0-211.222~16.04.1","4.15.0-212.223~16.04.1","4.15.0-213.224~16.04.1","4.15.0-214.225~16.04.1","4.15.0-216.227~16.04.1","4.15.0-218.229~16.04.1","4.15.0-219.230~16.04.1","4.15.0-220.231~16.04.1","4.15.0-221.232~16.04.1","4.15.0-222.233~16.04.1","4.15.0-223.235~16.04.1","4.15.0-224.236~16.04.1","4.15.0-225.237~16.04.1","4.15.0-226.238~16.04.1","4.15.0-227.239~16.04.1","4.15.0-228.240~16.04.1","4.15.0-229.241~16.04.1","4.15.0-230.242~16.04.1","4.15.0-231.243~16.04.1","4.15.0-232.244~16.04.1","4.15.0-233.245~16.04.1","4.15.0-234.246~16.04.1","4.15.0-235.247~16.04.1","4.15.0-236.248~16.04.1","4.15.0-237.249~16.04.1","4.15.0-238.250~16.04.1","4.15.0-239.251~16.04.1","4.15.0-240.252~16.04.1","4.15.0-241.253~16.04.1","4.15.0-242.254~16.04.1","4.15.0-243.255~16.04.1","4.15.0-245.257~16.04.1","4.15.0-246.258~16.04.1","4.15.0-247.259~16.04.1","4.15.0-248.260~16.04.1","4.15.0-249.261~16.04.1","4.15.0-250.262~16.04.1","4.15.0-253.265~16.04.1","4.15.0-254.266~16.04.1","4.15.0-257.269~16.04.1","4.15.0-260.272~16.04.2","4.15.0-261.273~16.04.1","4.15.0-262.274~16.04.1"]},{"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:Pro:16.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13","4.4.0-1009.14","4.4.0-1010.15","4.4.0-1012.17","4.4.0-1013.18","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1020.25","4.4.0-1021.26","4.4.0-1023.28","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1029.34","4.4.0-1031.37","4.4.0-1032.38","4.4.0-1033.39","4.4.0-1035.41","4.4.0-1036.42","4.4.0-1037.43","4.4.0-1038.44","4.4.0-1039.45","4.4.0-1040.46","4.4.0-1041.47","4.4.0-1043.49","4.4.0-1044.50","4.4.0-1046.52","4.4.0-1047.53","4.4.0-1048.55","4.4.0-1051.58","4.4.0-1052.59","4.4.0-1054.61","4.4.0-1056.63","4.4.0-1058.65","4.4.0-1059.66","4.4.0-1060.67","4.4.0-1062.69","4.4.0-1063.70","4.4.0-1064.71","4.4.0-1065.72","4.4.0-1066.73","4.4.0-1068.75","4.4.0-1069.76","4.4.0-1070.77","4.4.0-1071.78","4.4.0-1075.82","4.4.0-1076.83","4.4.0-1077.84","4.4.0-1078.85","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1082.91","4.4.0-1084.93","4.4.0-1085.94","4.4.0-1087.96","4.4.0-1088.97","4.4.0-1089.98","4.4.0-1090.99","4.4.0-1091.100","4.4.0-1092.101","4.4.0-1093.102","4.4.0-1094.103","4.4.0-1095.104","4.4.0-1096.105","4.4.0-1097.106","4.4.0-1098.107","4.4.0-1099.108","4.4.0-1100.109","4.4.0-1102.111","4.4.0-1103.112","4.4.0-1104.113","4.4.0-1105.114","4.4.0-1108.118","4.4.0-1110.120","4.4.0-1111.121","4.4.0-1112.122","4.4.0-1113.123","4.4.0-1114.124","4.4.0-1115.125","4.4.0-1116.126","4.4.0-1117.127","4.4.0-1118.128","4.4.0-1119.129","4.4.0-1120.130","4.4.0-1121.131","4.4.0-1122.132","4.4.0-1123.133","4.4.0-1124.134","4.4.0-1125.135","4.4.0-1126.136","4.4.0-1128.138","4.4.0-1129.139","4.4.0-1130.140","4.4.0-1131.141","4.4.0-1132.142","4.4.0-1134.144","4.4.0-1135.145","4.4.0-1136.146","4.4.0-1137.147","4.4.0-1138.148","4.4.0-1139.149","4.4.0-1140.151","4.4.0-1141.152","4.4.0-1142.153","4.4.0-1143.154","4.4.0-1144.155","4.4.0-1145.156","4.4.0-1146.157","4.4.0-1147.158","4.4.0-1148.159","4.4.0-1149.160","4.4.0-1150.161","4.4.0-1151.162","4.4.0-1152.163","4.4.0-1153.164","4.4.0-1154.165","4.4.0-1155.166","4.4.0-1156.167","4.4.0-1157.168","4.4.0-1158.169","4.4.0-1159.170","4.4.0-1160.171","4.4.0-1161.172","4.4.0-1162.173","4.4.0-1163.174"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9~16.04.1","4.15.0-1008.10~16.04.1","4.15.0-1009.11~16.04.1","4.15.0-1010.12~16.04.1","4.15.0-1011.13~16.04.1","4.15.0-1013.15~16.04.1","4.15.0-1014.16~16.04.1","4.15.0-1015.17~16.04.1","4.15.0-1017.19~16.04.2","4.15.0-1018.20~16.04.1","4.15.0-1021.23~16.04.1","4.15.0-1022.25~16.04.1","4.15.0-1023.26~16.04.1","4.15.0-1025.28~16.04.1","4.15.0-1026.29~16.04.1","4.15.0-1027.30~16.04.1","4.15.0-1029.32~16.04.1","4.15.0-1030.33~16.04.1","4.15.0-1031.34~16.04.1","4.15.0-1033.36~16.04.1","4.15.0-1035.38~16.04.1","4.15.0-1037.41~16.04.1","4.15.0-1038.42~16.04.1","4.15.0-1039.43~16.04.1","4.15.0-1045.49~16.04.1","4.15.0-1046.50~16.04.1","4.15.0-1050.54~16.04.1","4.15.0-1051.55~16.04.1","4.15.0-1053.57~16.04.1","4.15.0-1054.58~16.04.1","4.15.0-1056.61~16.04.1","4.15.0-1058.64~16.04.1","4.15.0-1059.65~16.04.1","4.15.0-1061.67~16.04.1","4.15.0-1062.68~16.04.1","4.15.0-1064.71~16.04.1","4.15.0-1065.73~16.04.1","4.15.0-1066.74~16.04.1","4.15.0-1067.75~16.04.1","4.15.0-1068.76~16.04.1","4.15.0-1069.77~16.04.1","4.15.0-1070.78~16.04.1","4.15.0-1071.79~16.04.1","4.15.0-1072.80~16.04.1","4.15.0-1075.83~16.04.1","4.15.0-1078.86~16.04.1","4.15.0-1079.87~16.04.1","4.15.0-1080.88~16.04.1","4.15.0-1081.89~16.04.1","4.15.0-1082.90~16.04.1","4.15.0-1083.91~16.04.1","4.15.0-1084.92~16.04.1","4.15.0-1085.93~16.04.1","4.15.0-1086.94~16.04.1","4.15.0-1087.95~16.04.1","4.15.0-1089.98~16.04.1","4.15.0-1090.99~16.04.1","4.15.0-1091.100~16.04.1","4.15.0-1092.101~16.04.1","4.15.0-1093.102~16.04.1","4.15.0-1095.104~16.04.1","4.15.0-1098.108~16.04.1","4.15.0-1101.112~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1104.115~16.04.1","4.15.0-1105.116~16.04.1","4.15.0-1106.117~16.04.1","4.15.0-1107.118~16.04.1","4.15.0-1108.119~16.04.1","4.15.0-1111.122~16.04.2","4.15.0-1112.123~16.04.1","4.15.0-1113.124~16.04.1","4.15.0-1115.126~16.04.1","4.15.0-1116.127~16.04.1","4.15.0-1117.128~16.04.1","4.15.0-1118.129~16.04.1","4.15.0-1119.130~16.04.1","4.15.0-1120.131~16.04.1","4.15.0-1121.132~16.04.1","4.15.0-1122.133~16.04.1","4.15.0-1123.134~16.04.1","4.15.0-1124.135~16.04.1","4.15.0-1125.136~16.04.1","4.15.0-1126.137~16.04.1","4.15.0-1127.138~16.04.1","4.15.0-1128.139~16.04.1","4.15.0-1129.140~16.04.1","4.15.0-1130.141~16.04.1","4.15.0-1131.142~16.04.1","4.15.0-1132.143~16.04.1","4.15.0-1133.144~16.04.1","4.15.0-1134.145~16.04.1","4.15.0-1135.146~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1138.149~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.153~16.04.1","4.15.0-1143.154~16.04.1","4.15.0-1144.155~16.04.1","4.15.0-1145.156~16.04.1","4.15.0-1148.159~16.04.1","4.15.0-1149.160~16.04.1","4.15.0-1150.161~16.04.1","4.15.0-1151.162~16.04.1","4.15.0-1153.164~16.04.1","4.15.0-1154.165~16.04.1","4.15.0-1156.167~16.04.1","4.15.0-1158.169~16.04.1","4.15.0-1160.171~16.04.1","4.15.0-1161.172~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1008.10","4.4.0-1010.13","4.4.0-1011.14","4.4.0-1012.16","4.4.0-1013.17","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1021.26","4.4.0-1022.27","4.4.0-1023.28","4.4.0-1025.30","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1028.33","4.4.0-1029.34","4.4.0-1031.36","4.4.0-1032.37","4.4.0-1033.38","4.4.0-1034.39","4.4.0-1041.46","4.4.0-1042.47","4.4.0-1043.48","4.4.0-1044.49","4.4.0-1045.50","4.4.0-1046.51","4.4.0-1048.53","4.4.0-1049.55","4.4.0-1051.57","4.4.0-1052.58","4.4.0-1054.60","4.4.0-1055.61","4.4.0-1056.62","4.4.0-1057.63","4.4.0-1058.64","4.4.0-1060.66","4.4.0-1061.67","4.4.0-1062.68","4.4.0-1063.69","4.4.0-1064.70","4.4.0-1065.71","4.4.0-1066.72","4.4.0-1067.73","4.4.0-1068.74","4.4.0-1069.75","4.4.0-1071.77","4.4.0-1072.78","4.4.0-1073.79","4.4.0-1074.80","4.4.0-1077.84","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1081.88","4.4.0-1082.89","4.4.0-1083.90","4.4.0-1084.91","4.4.0-1085.92","4.4.0-1086.93","4.4.0-1088.95","4.4.0-1089.96","4.4.0-1090.97","4.4.0-1091.98","4.4.0-1092.99","4.4.0-1093.100","4.4.0-1094.101","4.4.0-1095.102","4.4.0-1097.104","4.4.0-1099.106","4.4.0-1100.107","4.4.0-1101.108","4.4.0-1102.109","4.4.0-1103.110","4.4.0-1104.111","4.4.0-1105.112","4.4.0-1106.113","4.4.0-1107.114","4.4.0-1108.115","4.4.0-1109.116","4.4.0-1110.117","4.4.0-1111.118","4.4.0-1112.119","4.4.0-1113.120","4.4.0-1114.121","4.4.0-1115.122","4.4.0-1116.123","4.4.0-1117.124","4.4.0-1119.126","4.4.0-1120.127","4.4.0-1121.128","4.4.0-1122.129","4.4.0-1123.130","4.4.0-1124.131","4.4.0-1125.132","4.4.0-1126.133","4.4.0-1127.134","4.4.0-1128.135","4.4.0-1129.136","4.4.0-1130.137","4.4.0-1131.138"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1001.1","4.4.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35","4.15.0-33.36","4.15.0-34.37","4.15.0-36.39","4.15.0-38.41","4.15.0-39.42","4.15.0-42.45","4.15.0-43.46","4.15.0-44.47","4.15.0-45.48","4.15.0-46.49","4.15.0-47.50","4.15.0-48.51","4.15.0-50.54","4.15.0-51.55","4.15.0-52.56","4.15.0-54.58","4.15.0-55.60","4.15.0-58.64","4.15.0-60.67","4.15.0-62.69","4.15.0-64.73","4.15.0-65.74","4.15.0-66.75","4.15.0-69.78","4.15.0-70.79","4.15.0-72.81","4.15.0-74.84","4.15.0-76.86","4.15.0-88.88","4.15.0-91.92","4.15.0-96.97","4.15.0-99.100","4.15.0-101.102","4.15.0-106.107","4.15.0-108.109","4.15.0-109.110","4.15.0-111.112","4.15.0-112.113","4.15.0-115.116","4.15.0-117.118","4.15.0-118.119","4.15.0-121.123","4.15.0-122.124","4.15.0-123.126","4.15.0-124.127","4.15.0-126.129","4.15.0-128.131","4.15.0-129.132","4.15.0-130.134","4.15.0-132.136","4.15.0-134.138","4.15.0-135.139","4.15.0-136.140","4.15.0-137.141","4.15.0-139.143","4.15.0-140.144","4.15.0-141.145","4.15.0-142.146","4.15.0-143.147","4.15.0-144.148","4.15.0-147.151","4.15.0-151.157","4.15.0-153.160","4.15.0-154.161","4.15.0-156.163","4.15.0-158.166","4.15.0-159.167","4.15.0-161.169","4.15.0-162.170","4.15.0-163.171","4.15.0-166.174","4.15.0-167.175","4.15.0-169.177","4.15.0-171.180","4.15.0-173.182","4.15.0-175.184","4.15.0-176.185","4.15.0-177.186","4.15.0-180.189","4.15.0-184.194","4.15.0-187.198","4.15.0-188.199","4.15.0-189.200","4.15.0-191.202","4.15.0-192.203","4.15.0-193.204","4.15.0-194.205","4.15.0-196.207","4.15.0-197.208","4.15.0-200.211","4.15.0-201.212","4.15.0-202.213","4.15.0-204.215","4.15.0-206.217","4.15.0-208.220","4.15.0-209.220","4.15.0-210.221","4.15.0-211.222","4.15.0-212.223","4.15.0-213.224","4.15.0-214.225","4.15.0-216.227","4.15.0-218.229","4.15.0-219.230","4.15.0-220.231","4.15.0-221.232","4.15.0-222.233","4.15.0-223.235","4.15.0-224.236","4.15.0-225.237","4.15.0-226.238","4.15.0-227.239","4.15.0-228.240","4.15.0-229.241","4.15.0-230.242","4.15.0-231.243","4.15.0-232.244","4.15.0-233.245","4.15.0-234.246","4.15.0-235.247","4.15.0-236.248","4.15.0-237.249","4.15.0-238.250","4.15.0-239.251","4.15.0-240.252","4.15.0-241.253","4.15.0-242.254","4.15.0-243.255","4.15.0-245.257","4.15.0-246.258","4.15.0-247.259","4.15.0-248.260","4.15.0-249.261","4.15.0-250.262","4.15.0-251.263","4.15.0-253.265","4.15.0-254.266","4.15.0-257.269","4.15.0-260.272","4.15.0-261.273","4.15.0-262.274"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws","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-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1027.27","4.15.0-1029.30","4.15.0-1031.33","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1035.37","4.15.0-1037.39","4.15.0-1039.41","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1043.45","4.15.0-1044.46","4.15.0-1045.47","4.15.0-1047.49","4.15.0-1048.50","4.15.0-1050.52","4.15.0-1051.53","4.15.0-1052.54","4.15.0-1054.56","4.15.0-1056.58","4.15.0-1057.59","4.15.0-1058.60","4.15.0-1060.62","4.15.0-1063.67","4.15.0-1065.69","4.15.0-1066.70","4.15.0-1067.71","4.15.0-1073.77","4.15.0-1076.80","4.15.0-1077.81","4.15.0-1079.83","4.15.0-1080.84","4.15.0-1082.86","4.15.0-1083.87","4.15.0-1086.91","4.15.0-1087.92","4.15.0-1088.93","4.15.0-1090.95","4.15.0-1091.96","4.15.0-1092.98","4.15.0-1093.99","4.15.0-1094.101","4.15.0-1095.102","4.15.0-1096.103","4.15.0-1097.104","4.15.0-1098.105","4.15.0-1099.106","4.15.0-1101.108","4.15.0-1102.109","4.15.0-1103.110","4.15.0-1106.113","4.15.0-1109.116","4.15.0-1110.117","4.15.0-1111.118","4.15.0-1112.119","4.15.0-1114.121","4.15.0-1115.122","4.15.0-1116.123","4.15.0-1118.125","4.15.0-1119.127","4.15.0-1121.129","4.15.0-1123.132","4.15.0-1124.133","4.15.0-1126.135","4.15.0-1127.136","4.15.0-1128.137","4.15.0-1130.139","4.15.0-1133.143","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1150.163","4.15.0-1151.164","4.15.0-1153.166","4.15.0-1154.167","4.15.0-1155.168","4.15.0-1156.169","4.15.0-1157.170","4.15.0-1158.171","4.15.0-1159.172","4.15.0-1160.173","4.15.0-1161.174","4.15.0-1162.175","4.15.0-1163.176","4.15.0-1164.177","4.15.0-1165.178","4.15.0-1166.179","4.15.0-1167.180","4.15.0-1168.181","4.15.0-1169.182","4.15.0-1170.183","4.15.0-1172.185","4.15.0-1173.186","4.15.0-1174.187","4.15.0-1175.188","4.15.0-1176.189","4.15.0-1177.190","4.15.0-1178.191","4.15.0-1179.192","4.15.0-1180.193","4.15.0-1181.194","4.15.0-1182.195","4.15.0-1183.196","4.15.0-1184.197","4.15.0-1185.198","4.15.0-1186.199","4.15.0-1187.200","4.15.0-1188.201","4.15.0-1189.202","4.15.0-1190.203","4.15.0-1191.204","4.15.0-1192.205","4.15.0-1194.207","4.15.0-1195.208","4.15.0-1196.209","4.15.0-1197.210","4.15.0-1198.211","4.15.0-1199.212"]},{"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:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1124.134~18.04.1"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~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-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1"]},{"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:Pro:18.04:LTS","package":"linux-azure-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1082.92","4.15.0-1083.93","4.15.0-1089.99","4.15.0-1091.101","4.15.0-1092.102","4.15.0-1093.103","4.15.0-1095.105","4.15.0-1096.106","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1102.113","4.15.0-1103.114","4.15.0-1104.116","4.15.0-1106.118","4.15.0-1108.120","4.15.0-1109.121","4.15.0-1110.122","4.15.0-1111.123","4.15.0-1112.125","4.15.0-1113.126","4.15.0-1114.127","4.15.0-1115.128","4.15.0-1118.131","4.15.0-1121.134","4.15.0-1122.135","4.15.0-1123.136","4.15.0-1124.137","4.15.0-1125.138","4.15.0-1126.139","4.15.0-1127.140","4.15.0-1129.142","4.15.0-1130.143","4.15.0-1131.144","4.15.0-1133.146","4.15.0-1134.147","4.15.0-1136.149","4.15.0-1137.150","4.15.0-1138.151","4.15.0-1139.152","4.15.0-1142.156","4.15.0-1145.160","4.15.0-1146.161","4.15.0-1149.164","4.15.0-1150.165","4.15.0-1151.166","4.15.0-1153.168","4.15.0-1157.172","4.15.0-1158.173","4.15.0-1159.174","4.15.0-1161.176","4.15.0-1162.177","4.15.0-1163.178","4.15.0-1164.179","4.15.0-1165.180","4.15.0-1166.181","4.15.0-1167.182","4.15.0-1168.183","4.15.0-1169.184","4.15.0-1170.185","4.15.0-1171.186","4.15.0-1172.187","4.15.0-1173.188","4.15.0-1174.189","4.15.0-1175.190","4.15.0-1176.191","4.15.0-1177.192","4.15.0-1178.193","4.15.0-1179.194","4.15.0-1180.195","4.15.0-1181.196","4.15.0-1182.197","4.15.0-1183.198","4.15.0-1184.199","4.15.0-1185.200","4.15.0-1186.201","4.15.0-1187.202","4.15.0-1188.203","4.15.0-1189.204","4.15.0-1190.205","4.15.0-1191.206","4.15.0-1192.207","4.15.0-1193.208","4.15.0-1194.209","4.15.0-1195.210","4.15.0-1196.211","4.15.0-1197.212","4.15.0-1199.214","4.15.0-1200.215","4.15.0-1201.216","4.15.0-1202.217","4.15.0-1204.219","4.15.0-1205.220","4.15.0-1206.221","4.15.0-1207.222","4.15.0-1208.223","4.15.0-1209.224"]},{"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:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1129.136~18.04.1"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~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-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.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-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1"]},{"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:Pro:18.04:LTS","package":"linux-gcp-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1071.81","4.15.0-1077.87","4.15.0-1078.88","4.15.0-1080.90","4.15.0-1081.92","4.15.0-1083.94","4.15.0-1084.95","4.15.0-1086.98","4.15.0-1087.100","4.15.0-1088.101","4.15.0-1090.103","4.15.0-1091.104","4.15.0-1092.105","4.15.0-1093.106","4.15.0-1094.107","4.15.0-1095.108","4.15.0-1096.109","4.15.0-1097.110","4.15.0-1098.111","4.15.0-1099.112","4.15.0-1100.113","4.15.0-1103.116","4.15.0-1106.120","4.15.0-1107.121","4.15.0-1108.122","4.15.0-1109.123","4.15.0-1110.124","4.15.0-1111.125","4.15.0-1112.126","4.15.0-1114.128","4.15.0-1115.129","4.15.0-1116.130","4.15.0-1118.132","4.15.0-1119.133","4.15.0-1120.134","4.15.0-1121.135","4.15.0-1122.136","4.15.0-1124.138","4.15.0-1127.142","4.15.0-1130.146","4.15.0-1131.147","4.15.0-1134.150","4.15.0-1135.151","4.15.0-1136.152","4.15.0-1137.153","4.15.0-1138.154","4.15.0-1141.157","4.15.0-1142.158","4.15.0-1143.159","4.15.0-1145.161","4.15.0-1146.162","4.15.0-1147.163","4.15.0-1148.164","4.15.0-1149.165","4.15.0-1150.166","4.15.0-1151.167","4.15.0-1152.168","4.15.0-1153.170","4.15.0-1154.171","4.15.0-1155.172","4.15.0-1156.173","4.15.0-1157.174","4.15.0-1158.175","4.15.0-1159.176","4.15.0-1160.177","4.15.0-1161.178","4.15.0-1162.179","4.15.0-1163.180","4.15.0-1164.181","4.15.0-1165.182","4.15.0-1166.183","4.15.0-1167.184","4.15.0-1168.185","4.15.0-1169.186","4.15.0-1170.187","4.15.0-1171.188","4.15.0-1172.189","4.15.0-1173.190","4.15.0-1174.191","4.15.0-1175.192","4.15.0-1176.193","4.15.0-1177.194","4.15.0-1178.195","4.15.0-1179.196","4.15.0-1180.197","4.15.0-1181.198","4.15.0-1182.199","4.15.0-1183.200","4.15.0-1184.201","4.15.0-1185.202","4.15.0-1186.203","4.15.0-1187.204","4.15.0-1188.205","4.15.0-1189.206","4.15.0-1190.207","4.15.0-1191.208","4.15.0-1192.209"]},{"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:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1128.137~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~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-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~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:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-181.201~18.04.1"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1"]},{"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:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1071.76~18.04.1"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-kvm","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-1006.6","4.15.0-1008.8","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1012.12","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1026.26","4.15.0-1027.27","4.15.0-1028.28","4.15.0-1029.29","4.15.0-1030.30","4.15.0-1031.31","4.15.0-1032.32","4.15.0-1034.34","4.15.0-1035.35","4.15.0-1036.36","4.15.0-1038.38","4.15.0-1039.39","4.15.0-1042.42","4.15.0-1043.43","4.15.0-1044.44","4.15.0-1046.46","4.15.0-1047.47","4.15.0-1048.48","4.15.0-1050.50","4.15.0-1051.51","4.15.0-1052.52","4.15.0-1053.53","4.15.0-1056.57","4.15.0-1058.59","4.15.0-1059.60","4.15.0-1060.61","4.15.0-1067.68","4.15.0-1069.70","4.15.0-1071.72","4.15.0-1072.73","4.15.0-1074.75","4.15.0-1075.76","4.15.0-1077.79","4.15.0-1079.81","4.15.0-1081.83","4.15.0-1082.84","4.15.0-1084.86","4.15.0-1085.87","4.15.0-1086.88","4.15.0-1087.89","4.15.0-1088.90","4.15.0-1089.91","4.15.0-1090.92","4.15.0-1091.93","4.15.0-1092.94","4.15.0-1094.96","4.15.0-1097.99","4.15.0-1098.100","4.15.0-1099.101","4.15.0-1100.102","4.15.0-1101.103","4.15.0-1102.104","4.15.0-1103.105","4.15.0-1105.107","4.15.0-1106.108","4.15.0-1107.109","4.15.0-1109.112","4.15.0-1110.113","4.15.0-1112.115","4.15.0-1113.116","4.15.0-1114.117","4.15.0-1116.119","4.15.0-1119.123","4.15.0-1122.127","4.15.0-1123.128","4.15.0-1125.130","4.15.0-1126.131","4.15.0-1127.132","4.15.0-1128.133","4.15.0-1129.134","4.15.0-1132.137","4.15.0-1133.138","4.15.0-1134.139","4.15.0-1135.140","4.15.0-1136.141","4.15.0-1137.142","4.15.0-1138.143","4.15.0-1139.144","4.15.0-1140.145","4.15.0-1141.146","4.15.0-1142.147","4.15.0-1143.148","4.15.0-1144.149","4.15.0-1145.150","4.15.0-1146.151","4.15.0-1147.152","4.15.0-1148.153","4.15.0-1149.154","4.15.0-1150.155","4.15.0-1151.156","4.15.0-1152.157","4.15.0-1153.158","4.15.0-1154.159","4.15.0-1155.160","4.15.0-1156.161","4.15.0-1157.162","4.15.0-1158.163","4.15.0-1159.164","4.15.0-1160.165","4.15.0-1161.166","4.15.0-1162.167","4.15.0-1163.168","4.15.0-1164.169","4.15.0-1165.170","4.15.0-1166.171","4.15.0-1167.172","4.15.0-1168.173","4.15.0-1169.174","4.15.0-1170.175","4.15.0-1171.176","4.15.0-1172.177","4.15.0-1173.178","4.15.0-1174.179","4.15.0-1175.180","4.15.0-1176.181","4.15.0-1177.182","4.15.0-1178.183","4.15.0-1179.184","4.15.0-1180.185","4.15.0-1181.186"]},{"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:Pro:18.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9","4.15.0-1008.10","4.15.0-1009.11","4.15.0-1010.12","4.15.0-1011.13","4.15.0-1013.15","4.15.0-1014.16","4.15.0-1015.17","4.15.0-1017.19","4.15.0-1018.20","4.15.0-1021.23","4.15.0-1022.25","4.15.0-1023.26","4.15.0-1025.28","4.15.0-1026.29","4.15.0-1027.30","4.15.0-1029.32","4.15.0-1030.33","4.15.0-1031.34","4.15.0-1033.36","4.15.0-1035.39","4.15.0-1037.41","4.15.0-1038.42","4.15.0-1039.43","4.15.0-1045.49","4.15.0-1047.51","4.15.0-1048.52","4.15.0-1050.54","4.15.0-1051.55","4.15.0-1053.57","4.15.0-1054.58","4.15.0-1057.62","4.15.0-1058.64","4.15.0-1059.65","4.15.0-1061.67","4.15.0-1062.68","4.15.0-1063.70","4.15.0-1064.71","4.15.0-1065.73","4.15.0-1066.74","4.15.0-1067.75","4.15.0-1068.76","4.15.0-1069.77","4.15.0-1070.78","4.15.0-1071.79","4.15.0-1072.80","4.15.0-1075.83","4.15.0-1078.86","4.15.0-1079.87","4.15.0-1080.88","4.15.0-1081.89","4.15.0-1082.90","4.15.0-1083.91","4.15.0-1084.92","4.15.0-1085.93","4.15.0-1086.94","4.15.0-1087.95","4.15.0-1089.98","4.15.0-1090.99","4.15.0-1091.100","4.15.0-1092.101","4.15.0-1093.102","4.15.0-1095.104","4.15.0-1098.108","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1106.117","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1120.131","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1138.149","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.153","4.15.0-1143.154","4.15.0-1144.155","4.15.0-1145.156","4.15.0-1146.157","4.15.0-1147.158","4.15.0-1148.159","4.15.0-1149.160","4.15.0-1150.161","4.15.0-1151.162","4.15.0-1152.163","4.15.0-1153.164","4.15.0-1154.165","4.15.0-1155.166","4.15.0-1156.167","4.15.0-1158.169","4.15.0-1160.171","4.15.0-1161.172"]},{"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:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1123.132~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1108.120~18.04.1"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4","4.15.0-2018.18","4.15.0-2021.21","4.15.0-2022.22","4.15.0-2024.24","4.15.0-2025.25","4.15.0-2026.26","4.15.0-2027.27","4.15.0-2030.31","4.15.0-2031.32","4.15.0-2033.34","4.15.0-2034.35","4.15.0-2035.37","4.15.0-2036.38","4.15.0-2037.39","4.15.0-2038.40","4.15.0-2039.41","4.15.0-2040.42","4.15.0-2041.43","4.15.0-2042.44","4.15.0-2044.46","4.15.0-2045.47","4.15.0-2048.50","4.15.0-2051.53","4.15.0-2052.54","4.15.0-2053.55","4.15.0-2054.56","4.15.0-2055.57","4.15.0-2056.58","4.15.0-2057.59","4.15.0-2059.61","4.15.0-2060.62","4.15.0-2061.63","4.15.0-2063.66","4.15.0-2064.67","4.15.0-2065.68","4.15.0-2066.69","4.15.0-2067.70","4.15.0-2069.72","4.15.0-2072.76","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2078.83","4.15.0-2079.84","4.15.0-2080.85","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2085.91","4.15.0-2087.93","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2103.109","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2107.113","4.15.0-2108.114","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119","4.15.0-2114.120","4.15.0-2115.121","4.15.0-2116.122","4.15.0-2117.123","4.15.0-2118.124","4.15.0-2119.125","4.15.0-2120.126","4.15.0-2121.127","4.15.0-2122.128","4.15.0-2123.129","4.15.0-2124.130","4.15.0-2125.131","4.15.0-2126.132","4.15.0-2127.133","4.15.0-2128.134","4.15.0-2129.135","4.15.0-2130.136","4.15.0-2132.138","4.15.0-2133.139","4.15.0-2134.140","4.15.0-2135.141","4.15.0-2136.142","4.15.0-2137.143"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-2006.7","4.15.0-2007.8","4.15.0-2008.9","4.15.0-2009.10","4.15.0-2012.14","4.15.0-2013.15","4.15.0-2015.17","4.15.0-2016.18","4.15.0-2017.20","4.15.0-2018.21","4.15.0-2020.23","4.15.0-2021.24","4.15.0-2022.25","4.15.0-2023.26","4.15.0-2024.27","4.15.0-2025.28","4.15.0-2026.29","4.15.0-2027.30","4.15.0-2030.33","4.15.0-2033.37","4.15.0-2034.38","4.15.0-2035.39","4.15.0-2036.40","4.15.0-2037.41","4.15.0-2038.42","4.15.0-2039.43","4.15.0-2041.45","4.15.0-2042.46","4.15.0-2043.47","4.15.0-2045.49","4.15.0-2046.50","4.15.0-2047.51","4.15.0-2048.52","4.15.0-2049.53","4.15.0-2050.54","4.15.0-2053.58","4.15.0-2056.62","4.15.0-2057.63","4.15.0-2059.65","4.15.0-2060.66","4.15.0-2062.68","4.15.0-2066.72","4.15.0-2067.73","4.15.0-2068.74","4.15.0-2070.76","4.15.0-2071.77","4.15.0-2072.78","4.15.0-2073.79","4.15.0-2074.80","4.15.0-2075.81","4.15.0-2076.82","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119","4.15.0-2114.120","4.15.0-2115.121","4.15.0-2116.122","4.15.0-2117.123"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1027.32","4.15.0-1029.34","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1037.42","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1040.45","4.15.0-1041.46","4.15.0-1044.50","4.15.0-1045.52","4.15.0-1046.53","4.15.0-1048.55","4.15.0-1049.56","4.15.0-1050.58","4.15.0-1051.59","4.15.0-1052.60","4.15.0-1053.61","4.15.0-1054.62","4.15.0-1055.63","4.15.0-1056.64","4.15.0-1057.65","4.15.0-1058.66","4.15.0-1059.67","4.15.0-1060.68","4.15.0-1063.71","4.15.0-1066.75","4.15.0-1067.76","4.15.0-1068.77","4.15.0-1069.78","4.15.0-1070.79","4.15.0-1071.80","4.15.0-1072.81","4.15.0-1073.82","4.15.0-1075.84","4.15.0-1076.85","4.15.0-1078.87","4.15.0-1080.89","4.15.0-1081.90","4.15.0-1083.92","4.15.0-1084.93","4.15.0-1085.94","4.15.0-1087.96","4.15.0-1090.100","4.15.0-1093.104","4.15.0-1094.105","4.15.0-1096.107","4.15.0-1097.108","4.15.0-1098.109","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1103.114","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1109.120","4.15.0-1110.121","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1138.149","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.153","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1145.157","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1149.161","4.15.0-1150.162","4.15.0-1151.163","4.15.0-1152.164","4.15.0-1153.165","4.15.0-1154.166"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2013.14","4.15.0-2016.18","4.15.0-2017.19","4.15.0-2018.20","4.15.0-2019.21","4.15.0-2020.22","4.15.0-2021.23","4.15.0-2022.24","4.15.0-2024.26","4.15.0-2025.27","4.15.0-2026.28","4.15.0-2028.31","4.15.0-2029.32","4.15.0-2030.33","4.15.0-2031.34","4.15.0-2032.35","4.15.0-2034.37","4.15.0-2037.41","4.15.0-2040.45","4.15.0-2041.46","4.15.0-2043.48","4.15.0-2044.49","4.15.0-2045.50","4.15.0-2047.52","4.15.0-2050.55","4.15.0-2052.57","4.15.0-2054.59","4.15.0-2055.60","4.15.0-2056.61","4.15.0-2057.62","4.15.0-2058.63","4.15.0-2059.64","4.15.0-2060.65","4.15.0-2061.66","4.15.0-2062.67","4.15.0-2063.68","4.15.0-2064.69","4.15.0-2065.70","4.15.0-2066.71","4.15.0-2067.72","4.15.0-2068.73","4.15.0-2069.74","4.15.0-2070.75","4.15.0-2071.76","4.15.0-2072.77","4.15.0-2073.78","4.15.0-2074.79","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1011.12"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-181.201"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1124.134"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1061.67~20.04.1"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1129.136"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.72~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~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.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~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-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1084.91"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1128.137"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.67~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1091.95"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.51~20.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1071.76"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.57~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.64~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","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-1021.26~20.04.1","5.15.0-1023.28~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-1030.35~20.04.1","5.15.0-1031.36~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-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1036.37"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","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-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1112.119"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","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-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","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-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1027.27~20.04.1"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1123.132"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.65~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~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-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~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-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1108.120"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1057.61~20.04.1"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1043.47"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46"]},{"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-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:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1124.134+fips1"}]}],"versions":["5.4.0-1021.21+fips2","5.4.0-1069.73+fips2","5.4.0-1071.76+fips1","5.4.0-1072.77+fips1","5.4.0-1073.78+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1083.90+fips1","5.4.0-1085.92+fips1","5.4.0-1086.93+fips1","5.4.0-1088.96+fips1","5.4.0-1089.97+fips1","5.4.0-1092.100+fips1","5.4.0-1093.101+fips1","5.4.0-1094.102+fips1","5.4.0-1096.104+fips1","5.4.0-1099.107+fips1","5.4.0-1100.108+fips1","5.4.0-1101.109+fips1","5.4.0-1102.110+fips1","5.4.0-1103.111+fips1","5.4.0-1104.112+fips1","5.4.0-1105.113+fips1","5.4.0-1106.114+fips1","5.4.0-1107.115+fips1","5.4.0-1108.116+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.123+fips1","5.4.0-1114.124+fips1","5.4.0-1116.126+fips1","5.4.0-1117.127+fips1","5.4.0-1118.128+fips1","5.4.0-1119.129+fips1","5.4.0-1120.130+fips1","5.4.0-1121.131+fips1","5.4.0-1122.132+fips1","5.4.0-1123.133+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1129.136+fips1"}]}],"versions":["5.4.0-1022.22+fips1","5.4.0-1073.76+fips1","5.4.0-1074.77+fips1","5.4.0-1076.79+fips1","5.4.0-1078.81+fips1","5.4.0-1080.83+fips1","5.4.0-1083.87+fips1","5.4.0-1085.90+fips1","5.4.0-1086.91+fips1","5.4.0-1089.94+fips1","5.4.0-1090.95+fips1","5.4.0-1091.96+fips1","5.4.0-1094.100+fips1","5.4.0-1095.101+fips1","5.4.0-1098.104+fips1","5.4.0-1100.106+fips1","5.4.0-1101.107+fips1","5.4.0-1103.109+fips1","5.4.0-1104.110+fips1","5.4.0-1105.111+fips1","5.4.0-1106.112+fips1","5.4.0-1107.113+fips1","5.4.0-1108.114+fips1","5.4.0-1109.115+fips1","5.4.0-1110.116+fips1","5.4.0-1111.117+fips1","5.4.0-1112.118+fips1","5.4.0-1113.119+fips1","5.4.0-1114.120+fips1","5.4.0-1115.122+fips1","5.4.0-1116.123+fips1","5.4.0-1117.124+fips1","5.4.0-1118.125+fips1","5.4.0-1119.126+fips1","5.4.0-1121.128+fips1","5.4.0-1122.129+fips1","5.4.0-1123.130+fips1","5.4.0-1124.131+fips1","5.4.0-1126.133+fips1","5.4.0-1127.134+fips1","5.4.0-1128.135+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1098.108"}]}],"versions":["5.4.0-1026.30","5.4.0-1028.32","5.4.0-1031.36","5.4.0-1032.37","5.4.0-1033.38","5.4.0-1034.40","5.4.0-1035.41","5.4.0-1036.42","5.4.0-1037.43","5.4.0-1038.44","5.4.0-1040.46","5.4.0-1041.47","5.4.0-1042.48","5.4.0-1043.49","5.4.0-1045.51","5.4.0-1046.52","5.4.0-1047.53","5.4.0-1048.54","5.4.0-1049.55","5.4.0-1051.57","5.4.0-1054.61","5.4.0-1056.64","5.4.0-1057.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1061.69","5.4.0-1062.70","5.4.0-1064.73","5.4.0-1065.74","5.4.0-1068.77","5.4.0-1069.78","5.4.0-1070.79","5.4.0-1072.81","5.4.0-1073.82","5.4.0-1074.83","5.4.0-1075.84","5.4.0-1076.85","5.4.0-1077.86","5.4.0-1078.87","5.4.0-1079.88","5.4.0-1080.89","5.4.0-1081.90","5.4.0-1082.91","5.4.0-1083.92","5.4.0-1084.93","5.4.0-1085.94","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1088.97","5.4.0-1089.98","5.4.0-1090.100","5.4.0-1091.101","5.4.0-1092.102","5.4.0-1094.104","5.4.0-1095.105","5.4.0-1096.106","5.4.0-1097.107"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1128.137+fips1"}]}],"versions":["5.4.0-1021.21+fips1","5.4.0-1067.71~20.04.1","5.4.0-1069.73+fips2","5.4.0-1071.75+fips1","5.4.0-1073.78+fips1","5.4.0-1075.80+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1086.94+fips1","5.4.0-1087.95+fips1","5.4.0-1089.97+fips1","5.4.0-1092.101+fips1","5.4.0-1093.102+fips1","5.4.0-1096.105+fips1","5.4.0-1097.106+fips1","5.4.0-1098.107+fips1","5.4.0-1100.109+fips1","5.4.0-1101.110+fips1","5.4.0-1102.111+fips1","5.4.0-1103.112+fips1","5.4.0-1104.113+fips1","5.4.0-1105.114+fips1","5.4.0-1106.115+fips1","5.4.0-1107.116+fips1","5.4.0-1108.117+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.122+fips1","5.4.0-1115.124+fips1","5.4.0-1116.125+fips1","5.4.0-1117.126+fips1","5.4.0-1118.127+fips1","5.4.0-1120.129+fips1","5.4.0-1121.130+fips1","5.4.0-1122.131+fips1","5.4.0-1124.133+fips1","5.4.0-1125.134+fips1","5.4.0-1126.135+fips1","5.4.0-1127.136+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.8"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1061.67"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","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","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66"]},{"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-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.72"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70"]},{"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"},{"fixed":"6.5.0-1022.23~22.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.72.1"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.67"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66"]},{"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"},{"fixed":"6.5.0-1022.24~22.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.63"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.51"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50"]},{"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"},{"fixed":"6.5.0-41.41~22.04.2"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.57"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1057.63"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.63"}]}],"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-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115"]},{"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"},{"fixed":"6.5.0-41.41.1~22.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.55"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54"]},{"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"},{"fixed":"6.5.0-1021.22"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1026.26"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1015.15"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","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-1009.9","5.15.0-1012.12","5.15.0-1013.13"]},{"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"},{"fixed":"6.1.0-1035.35"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-1024.25"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.65"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-1024.24~22.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.57"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56"]},{"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"},{"fixed":"6.5.0-40.40.1~22.04.1"}]}],"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"]},{"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"},{"fixed":"6.5.0-1015.16~22.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1030.34"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1043.45"}]}],"versions":["5.15.0-1011.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1017.19","5.15.0-1019.21","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1031.33","5.15.0-1032.34","5.15.0-1033.35","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1040.42","5.15.0-1042.44"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.56"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1062.70"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1061.67+fips1"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.72+fips1"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116+fips1"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.67+fips1"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2001.1"}]}],"versions":["6.7.0-2001.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.0-1035.35"}]}],"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"],"bundled":63},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.72~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~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.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~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-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.72~20.04.1.1"}]}],"versions":["5.15.0-1019.24~20.04.1.1","5.15.0-1020.25~20.04.1.1","5.15.0-1021.26~20.04.1.1","5.15.0-1029.36~20.04.1.1","5.15.0-1030.37~20.04.1.1","5.15.0-1031.38~20.04.1.1","5.15.0-1033.40~20.04.1.1","5.15.0-1034.41~20.04.1.2","5.15.0-1035.42~20.04.1.1","5.15.0-1036.43~20.04.1.1","5.15.0-1037.44~20.04.1.1","5.15.0-1038.45~20.04.1.1","5.15.0-1039.46~20.04.1.1","5.15.0-1040.47~20.04.1.1","5.15.0-1041.48~20.04.1.1","5.15.0-1042.49~20.04.1.1","5.15.0-1043.50~20.04.1.1","5.15.0-1046.53~20.04.1.1","5.15.0-1047.54~20.04.1.1","5.15.0-1049.56~20.04.1.1","5.15.0-1050.57~20.04.1.1","5.15.0-1051.59~20.04.1.1","5.15.0-1052.60~20.04.1.1","5.15.0-1053.61~20.04.1.1","5.15.0-1054.62~20.04.1.1","5.15.0-1056.64~20.04.1.1","5.15.0-1057.65~20.04.1.1","5.15.0-1058.66~20.04.2.1","5.15.0-1059.67~20.04.1.1","5.15.0-1060.69~20.04.1.1","5.15.0-1061.70~20.04.1.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.67~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.51~20.04.1"}]}],"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"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.57~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.65~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~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-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~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-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.72"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1063.72.1"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.67"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.63"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.51"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.57"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.63"}]}],"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-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.55"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1059.65"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-106.116~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1054.57"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1061.67~20.04.1"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1061.67"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","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","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66"],"bundled":91},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1124.134~18.04.1"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~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-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1129.136~18.04.1"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~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-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.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-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1128.137~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~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-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-181.201~18.04.1"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1071.76~18.04.1"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1123.132~18.04.1"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1108.120~18.04.1"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-181.201"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1124.134"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1129.136"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1128.137"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1091.95"}]}],"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"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1071.76"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1036.37"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","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-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1112.119"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","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-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","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-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1123.132"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1108.120"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1043.47"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1084.91"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90"],"bundled":48},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1057.63"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61"],"bundled":94},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-1022.24~22.04.1"}]}],"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"],"bundled":150},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-41.41.1~22.04.1"}]}],"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"],"bundled":150},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-1021.22"}]}],"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"],"bundled":150},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-41.41~22.04.2"}]}],"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"],"bundled":150},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-1022.23~22.04.1"}]}],"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"],"bundled":149},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-1015.16~22.04.1"}]}],"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"],"bundled":149},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-1024.25"}]}],"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"],"bundled":149},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.5.0-1024.24~22.04.1"}]}],"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"],"bundled":149},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1058.64~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","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-1021.26~20.04.1","5.15.0-1023.28~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-1030.35~20.04.1","5.15.0-1031.36~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-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1"],"bundled":245}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/3a04410b0bc7e056e0843ac598825dd359246d18","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/150a3a3871490e8c454ffbac2e60abeafcecff99","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/732a3bea7aba5b15026ea42d14953c3425cc7dc2","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/0671f42a9c1084db10d68ac347d08dbf6689ecb3","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/c87d7d910775a025e230fd6359b60627e392460f","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7","tags":["x_transferred","Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/b988b1bb0053c0dcd26187d29ef07566a565cf55","tags":["x_transferred","Patch","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html","tags":["x_transferred","Mailing List","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52597","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-6j3q-64jm-q33g"},{"url":"https://access.redhat.com/errata/RHSA-2024:2394","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/1918601","tags":["report"]},{"url":"https://bugzilla.redhat.com/2049700","tags":["report"]},{"url":"https://bugzilla.redhat.com/2133452","tags":["report"]},{"url":"https://bugzilla.redhat.com/2151959","tags":["report"]},{"url":"https://bugzilla.redhat.com/2177759","tags":["report"]},{"url":"https://bugzilla.redhat.com/2185519","tags":["report"]},{"url":"https://bugzilla.redhat.com/2188102","tags":["report"]},{"url":"https://bugzilla.redhat.com/2210024","tags":["report"]},{"url":"https://bugzilla.redhat.com/2213132","tags":["report"]},{"url":"https://bugzilla.redhat.com/2218332","tags":["report"]},{"url":"https://bugzilla.redhat.com/2219359","tags":["report"]},{"url":"https://bugzilla.redhat.com/2221039","tags":["report"]},{"url":"https://bugzilla.redhat.com/2221463","tags":["report"]},{"url":"https://bugzilla.redhat.com/2221702","tags":["report"]},{"url":"https://bugzilla.redhat.com/2226777","tags":["report"]},{"url":"https://bugzilla.redhat.com/2226787","tags":["report"]},{"url":"https://bugzilla.redhat.com/2226788","tags":["report"]},{"url":"https://bugzilla.redhat.com/2231410","tags":["report"]},{"url":"https://bugzilla.redhat.com/2239845","tags":["report"]},{"url":"https://bugzilla.redhat.com/2239848","tags":["report"]},{"url":"https://bugzilla.redhat.com/2244720","tags":["report"]},{"url":"https://bugzilla.redhat.com/2246980","tags":["report"]},{"url":"https://bugzilla.redhat.com/2250043","tags":["report"]},{"url":"https://bugzilla.redhat.com/2252731","tags":["report"]},{"url":"https://bugzilla.redhat.com/2253034","tags":["report"]},{"url":"https://bugzilla.redhat.com/2253632","tags":["report"]},{"url":"https://bugzilla.redhat.com/2254961","tags":["report"]},{"url":"https://bugzilla.redhat.com/2254982","tags":["report"]},{"url":"https://bugzilla.redhat.com/2255283","tags":["report"]},{"url":"https://bugzilla.redhat.com/2255498","tags":["report"]},{"url":"https://bugzilla.redhat.com/2256490","tags":["report"]},{"url":"https://bugzilla.redhat.com/2256822","tags":["report"]},{"url":"https://bugzilla.redhat.com/2257682","tags":["report"]},{"url":"https://bugzilla.redhat.com/2258013","tags":["report"]},{"url":"https://bugzilla.redhat.com/2258518","tags":["report"]},{"url":"https://bugzilla.redhat.com/2260005","tags":["report"]},{"url":"https://bugzilla.redhat.com/2262126","tags":["report"]},{"url":"https://bugzilla.redhat.com/2262127","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265285","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265517","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265518","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265519","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265520","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265645","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265646","tags":["report"]},{"url":"https://bugzilla.redhat.com/2265653","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267041","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267695","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267750","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267758","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267760","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267761","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267788","tags":["report"]},{"url":"https://bugzilla.redhat.com/2267795","tags":["report"]},{"url":"https://bugzilla.redhat.com/2269189","tags":["report"]},{"url":"https://bugzilla.redhat.com/2269217","tags":["report"]},{"url":"https://bugzilla.redhat.com/2270080","tags":["report"]},{"url":"https://bugzilla.redhat.com/2270118","tags":["report"]},{"url":"https://bugzilla.redhat.com/2270883","tags":["report"]},{"url":"https://errata.almalinux.org/9/ALSA-2024-2394.html","tags":["advisory"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2020-26555.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2022-0480.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2022-38096.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2022-45934.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-24023.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-25775.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-28464.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-28866.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-31083.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-3567.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-37453.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-39189.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-39193.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-39194.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-39198.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-4133.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-42754.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-42756.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-45863.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-46862.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-51043.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-51779.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-51780.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52434.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52448.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52450.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52476.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52489.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52522.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52529.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52574.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52578.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52580.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52581.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52597.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52610.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-52620.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6040.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6121.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6176.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6531.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6546.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6622.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6915.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6931.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2023-6932.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-0565.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-0841.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-1085.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-1086.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-25744.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26582.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26583.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26584.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26585.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26586.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26593.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26602.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26609.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26633.html","tags":["report"]},{"url":"https://www.redhat.com/security/data/cve/CVE-2024-26671.html","tags":["report"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2023-52597","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/52xxx/CVE-2023-52597.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-2023-52597","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1482","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-46926","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52464","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52500","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52507","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52515","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52525","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52530","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52561","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52568","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52573","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52577","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52578","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26601","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-36783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-46984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47143","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47144","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47170","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47180","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1484","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1485","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52516","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1486","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1487","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.4_release_notes/index","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1918601","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2049700","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2133452","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2151959","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2177759","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2185519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2188102","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2210024","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2213132","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2218332","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2219359","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2221039","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2221463","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2221702","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2226777","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2226787","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2226788","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2231410","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2239845","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2239848","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2244720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2246980","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2250043","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2252731","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2253034","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2253632","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2254961","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2254982","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2255283","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2255498","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2256490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2256822","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2257682","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258013","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258518","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2260005","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2262126","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2262127","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265285","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265517","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265518","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265520","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265645","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265646","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265653","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267041","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267695","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267750","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267758","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267760","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267761","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267788","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269189","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269217","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270080","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270118","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270883","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-15897","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-15937","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-16024","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-17986","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-19081","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-2376","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-2421","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-2907","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-3923","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-6012","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-7936","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9127","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_2394.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2020-26555","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-26555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26555","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-47579","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2293250","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-47579","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47579","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024061915-CVE-2021-47579-4f78@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-0480","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-0480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-0480","tags":["advisory"]},{"url":"https://github.com/kata-containers/kata-containers/issues/3373","tags":["article"]},{"url":"https://lore.kernel.org/linux-mm/20210902215519.AWcuVc3li%25akpm@linux-foundation.org/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-38096","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-38096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-38096","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-45934","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-45934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-45934","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=ae4569813a6e931258db627cdfe50dfb4f917d5d","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48632","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2277840","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48632","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024042854-CVE-2022-48632-465f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-48947","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320770","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-48947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48947","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102140-CVE-2022-48947-0ab5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49011","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2320778","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49011","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024102152-CVE-2022-49011-069a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49322","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347717","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49322","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022637-CVE-2022-49322-b0f0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49350","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348007","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49350","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022642-CVE-2022-49350-c5d2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49721","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348109","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49721","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022632-CVE-2022-49721-b74f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49744","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355495","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49744","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032758-CVE-2022-49744-8c5a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49754","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355528","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49754","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032701-CVE-2022-49754-cc36@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49940","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373397","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061848-CVE-2022-49940-181b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49977","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373574","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49977","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061819-CVE-2022-49977-3826@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50080","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373446","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50080","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061856-CVE-2022-50080-a32c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50116","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373692","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50116","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061809-CVE-2022-50116-bf10@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50202","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373411","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50202","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50202","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061840-CVE-2022-50202-48e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50277","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395401","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50277","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091506-CVE-2022-50277-085f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50286","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395325","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50286","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091508-CVE-2022-50286-b313@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50313","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395304","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50313","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091500-CVE-2022-50313-2fa9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50318","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395235","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50318","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091552-CVE-2022-50318-6f5e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50346","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395861","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50346","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091639-CVE-2022-50346-49b1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50374","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396106","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50374","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091717-CVE-2022-50374-6da4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50377","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50377","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50377","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091851-CVE-2022-50377-f43b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50447","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400804","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50447","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50447","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100115-CVE-2022-50447-4de6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50453","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400743","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50453","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50453","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100117-CVE-2022-50453-204a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50485","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401531","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50485","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50485","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100441-CVE-2022-50485-9d4c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50637","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420275","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50637","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120935-CVE-2022-50637-f1b4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50638","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420266","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50638","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120935-CVE-2022-50638-fb89@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50642","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420291","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50642","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50642","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120936-CVE-2022-50642-6975@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50673","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420347","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50673","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120947-CVE-2022-50673-f920@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50736","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425020","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50736","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50736","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122422-CVE-2022-50736-1cb3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50777","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425168","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50777","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50777","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122400-CVE-2022-50777-d1e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50780","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425204","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50780","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122401-CVE-2022-50780-bc90@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50782","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50782","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122402-CVE-2022-50782-d849@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50845","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426024","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50845","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50845","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2022-50845-367a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426076","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50879","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123024-CVE-2022-50879-47a7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-3567","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-3567","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-3567","tags":["advisory"]},{"url":"https://www.spinics.net/lists/stable-commits/msg285184.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-4133","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-4133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-4133","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6040","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6040","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2024/01/12/1","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6121","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6176","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6176","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cfaa80c91f6f99b9342b6557f0f0e1143e434066","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6531","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6531","tags":["advisory"]},{"url":"https://lore.kernel.org/all/c716c88321939156909cfa1bd8b0faaf1c804103.1701868795.git.asml.silence@gmail.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6546","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6546","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/3c4f8333b582487a2d1e02171f1465531cde53e3","tags":["article"]},{"url":"https://www.zerodayinitiative.com/advisories/ZDI-CAN-20527","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6622","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6622","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/3701cd390fd731ee7ae8b8006246c8db82c72bea","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6915","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6915","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/af73483f4e8b6f5c68c9aa63257bdd929a9c194a","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6931","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=382c27f4ed28f803b1f1473ac2d8db0afc795a1b","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-6932","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-6932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6932","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-24023","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-24023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-24023","tags":["advisory"]},{"url":"https://www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/bluffs-vulnerability/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-25775","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-25775","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-25775","tags":["advisory"]},{"url":"https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00794.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-28464","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-28464","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-28464","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2023/03/28/2","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-28866","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-28866","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-28866","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=95084403f8c070ccf5d7cbe72352519c1798a40a","tags":["article"]},{"url":"https://lore.kernel.org/lkml/20230321015018.1759683-1-iam@sung-woo.kim/","tags":["article"]},{"url":"https://patchwork.kernel.org/project/bluetooth/patch/20230322232543.3079578-1-luiz.dentz@gmail.com","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-31083","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-31083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-31083","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/bluetooth/hci_ldisc.c?h=v6.6-rc7\u0026id=9c33663af9ad115f90c076a1828129a3fbadea98","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-37453","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-37453","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-37453","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-39189","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-39189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-39189","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-39193","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-39193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-39193","tags":["advisory"]},{"url":"https://www.zerodayinitiative.com/advisories/ZDI-CAN-18866/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-39194","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-39194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-39194","tags":["advisory"]},{"url":"https://www.zerodayinitiative.com/advisories/ZDI-CAN-18111/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-39198","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-39198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-39198","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-42754","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-42754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-42754","tags":["advisory"]},{"url":"https://seclists.org/oss-sec/2023/q4/14","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-42756","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-42756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-42756","tags":["advisory"]},{"url":"https://seclists.org/oss-sec/2023/q3/242","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-45863","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-45863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-45863","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-46862","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-46862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-46862","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-51043","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-51043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-51043","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/4e076c73e4f6e90816b30fcd4a0d7ab365087255","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-51779","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-51779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-51779","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/2e07e8348ea454615e268222ae3fc240421be768","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-51780","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-51780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-51780","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/24e90b9e34f9e039f56b5f25f6e6eb92cdd8f4b3","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52434","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52434","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52434","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=17a0f64cc02d4972e21c733d9f21d1c512963afa","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=af1689a9b7701d9907dfc84d2a4b57c4bc907144","tags":["article"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022033-makeshift-flammable-cb72@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52448","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52448","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022255-CVE-2023-52448-7bf2@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52450","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2265649","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52450","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022256-CVE-2023-52450-48ba@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52469","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266341","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52469","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/28dd788382c43b330480f57cd34cde0840896743","tags":["article"]},{"url":"https://git.kernel.org/stable/c/3426f059eacc33ecc676b0d66539297e1cfafd02","tags":["article"]},{"url":"https://git.kernel.org/stable/c/35fa2394d26e919f63600ce631e6aefc95ec2706","tags":["article"]},{"url":"https://git.kernel.org/stable/c/520e213a0b97b64735a13950e9371e0a5d7a5dc3","tags":["article"]},{"url":"https://git.kernel.org/stable/c/8a27d9d9fc9b5564b8904c3a77a7dea482bfa34e","tags":["article"]},{"url":"https://git.kernel.org/stable/c/8b55b06e737feb2a645b0293ea27e38418876d63","tags":["article"]},{"url":"https://git.kernel.org/stable/c/95084632a65d5c0d682a83b55935560bdcd2a1e3","tags":["article"]},{"url":"https://git.kernel.org/stable/c/b6dcba02ee178282e0d28684d241e0b8462dea6a","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52470","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2266358","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52470","tags":["advisory"]},{"url":"https://git.kernel.org/stable/c/0b813a6a0087451cb702b6eb841f10856f49d088","tags":["article"]},{"url":"https://git.kernel.org/stable/c/14bbfaa5df273b26cde6707f6e655585700e6fe1","tags":["article"]},{"url":"https://git.kernel.org/stable/c/21b1645660717d6126dd4866c850fcc5c4703a41","tags":["article"]},{"url":"https://git.kernel.org/stable/c/57ca7984806d79b38af528de88fd803babf27feb","tags":["article"]},{"url":"https://git.kernel.org/stable/c/5d12c5d75f7c78b83a738025947651ec5c95b4d4","tags":["article"]},{"url":"https://git.kernel.org/stable/c/7a2464fac80d42f6f8819fed97a553e9c2f43310","tags":["article"]},{"url":"https://git.kernel.org/stable/c/c4ff55408187f2595066967047363ca84e76db85","tags":["article"]},{"url":"https://git.kernel.org/stable/c/fb2d8bc9b5e55848b8a7c3c028e2ee8d49f28f97","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52476","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52476","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52476-e307@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52478","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267036","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52478","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52478-c0a1@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52486","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2269070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52486","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52486","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-27-lee@kernel.org/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52489","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52489","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52489","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-30-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52519","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2267798","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52519","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52519","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52519-d53f@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52522","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52522","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52522-6abd@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52529","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52529","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52529","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52529-56ff@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52574","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52574","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52574","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52574-a423@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52578","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52578","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52578-50cb@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52580","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52580","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030258-CVE-2023-52580-c37e@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52581","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52581","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030258-CVE-2023-52581-2165@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52597","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268311","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52597","tags":["advisory","report"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024030646-CVE-2023-52597-2ed6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52610","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52610","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52610","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-10-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52620","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52620","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52620","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024032147-CVE-2023-52620-11a9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272041","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52628","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024032850-CVE-2023-52628-14fb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52817","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282676","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52817","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052104-CVE-2023-52817-ba29@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52832","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2282645","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52832","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52832","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052108-CVE-2023-52832-b9d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52881","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2258875","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52881","tags":["advisory"]},{"url":"https://lore.kernel.org/all/20231205161841.2702925-1-edumazet@google.com/","tags":["article"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024052941-CVE-2023-52881-4283@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52924","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2343897","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52924","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025020500-CVE-2023-52924-03d7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52934","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355463","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52934","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032720-CVE-2023-52934-bd3c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52939","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355456","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52939","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032722-CVE-2023-52939-8bb1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52940","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355488","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52940","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032722-CVE-2023-52940-2e53@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52973","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355433","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52973","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032703-CVE-2023-52973-a993@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52976","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52976","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032704-CVE-2023-52976-eda3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52984","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355472","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52984","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032707-CVE-2023-52984-19ad@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52985","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355496","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52985","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52985","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032707-CVE-2023-52985-3f52@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52999","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355485","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52999","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032711-CVE-2023-52999-e28e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53004","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355465","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53004","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032713-CVE-2023-53004-e58b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53016","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355451","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53016","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032716-CVE-2023-53016-f30c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53017","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355494","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53017","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032716-CVE-2023-53017-8dd9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53018","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355511","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53018","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032717-CVE-2023-53018-c89c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53019","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355493","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53019","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032717-CVE-2023-53019-441a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53046","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363700","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53046","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050204-CVE-2023-53046-f1fc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53047","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363689","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53047","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050204-CVE-2023-53047-7e31@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53052","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363695","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53052","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050206-CVE-2023-53052-41f8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53057","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363734","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050208-CVE-2023-53057-71cc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53094","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363768","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53094","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050221-CVE-2023-53094-a015@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53097","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363721","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53097","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050222-CVE-2023-53097-fd46@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53134","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363705","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53134","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050235-CVE-2023-53134-68c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53140","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363767","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53140","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53140","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050238-CVE-2023-53140-a5f2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395231","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53148","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091552-CVE-2023-53148-e1b8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53149","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395246","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53149","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091552-CVE-2023-53149-2f0a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53150","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395327","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53150","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091552-CVE-2023-53150-29b0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53151","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53151","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091552-CVE-2023-53151-263e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53152","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395307","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53152","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091552-CVE-2023-53152-130d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53164","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395350","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53164","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53164","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091553-CVE-2023-53164-3a5d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53180","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395333","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53180","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091556-CVE-2023-53180-5e16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53181","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395369","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53181","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53181","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091556-CVE-2023-53181-608c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53184","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395376","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53184","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53184","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091557-CVE-2023-53184-3b7a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53192","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395232","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53192","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091558-CVE-2023-53192-5ca6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53193","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395409","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53193","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091558-CVE-2023-53193-74f6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53202","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395326","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53202","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53202","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091509-CVE-2023-53202-5e01@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53204","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395332","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53204","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091509-CVE-2023-53204-3e15@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53208","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395440","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53208","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091510-CVE-2023-53208-b31d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53209","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395321","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53209","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091510-CVE-2023-53209-ed9e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53210","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395424","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53210","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53210","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091511-CVE-2023-53210-0e06@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53221","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395223","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53221","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091513-CVE-2023-53221-c23e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53228","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395430","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53228","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091514-CVE-2023-53228-441c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53235","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395384","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53235","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091515-CVE-2023-53235-1104@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53237","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395288","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53237","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091516-CVE-2023-53237-7d1b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53246","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395404","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53246","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091501-CVE-2023-53246-a539@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53248","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395250","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53248","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53248","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091501-CVE-2023-53248-aa39@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53252","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395337","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53252","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091502-CVE-2023-53252-3a4f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53256","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395313","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53256","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53256","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091503-CVE-2023-53256-d5af@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53258","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395426","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53258","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091503-CVE-2023-53258-35f0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53263","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395660","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53263","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53263","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091600-CVE-2023-53263-9abe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53270","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395662","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53270","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091603-CVE-2023-53270-4af2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53275","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395693","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53275","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53275","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091623-CVE-2023-53275-3ac4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53280","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395680","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53280","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091624-CVE-2023-53280-30a2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53285","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395666","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53285","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091625-CVE-2023-53285-7cb1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53288","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395665","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53288","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091625-CVE-2023-53288-b799@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53290","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395694","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53290","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53290","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091626-CVE-2023-53290-34e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53293","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395674","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53293","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091626-CVE-2023-53293-73cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53297","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395681","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53297","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53297","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091627-CVE-2023-53297-8746@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53304","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395846","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53304","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091641-CVE-2023-53304-9a57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53309","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395882","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53309","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091642-CVE-2023-53309-005a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53317","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395887","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53317","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53317","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091643-CVE-2023-53317-c945@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53321","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395890","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53321","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091644-CVE-2023-53321-0003@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53322","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395891","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53322","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091644-CVE-2023-53322-45ba@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53335","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396111","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53335","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53335","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091717-CVE-2023-53335-1e5d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53338","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53338","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53338","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091718-CVE-2023-53338-8224@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53343","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396136","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53343","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091719-CVE-2023-53343-880b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53351","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396115","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53351","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091720-CVE-2023-53351-7b67@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53352","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396113","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53352","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091720-CVE-2023-53352-9be5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53354","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396158","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53354","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53354","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091721-CVE-2023-53354-771f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53365","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396130","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53365","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53365","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091723-CVE-2023-53365-acb1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53370","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396394","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53370","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53370","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091855-CVE-2023-53370-1085@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53371","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396397","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53371","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091855-CVE-2023-53371-e5f9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53380","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396425","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53380","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53380","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091856-CVE-2023-53380-b2e0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53384","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396428","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53384","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091857-CVE-2023-53384-042e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53394","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396380","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53394","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53394","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091859-CVE-2023-53394-dd17@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53415","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53415","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53415","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091802-CVE-2023-53415-ea27@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53421","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396500","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53421","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091855-CVE-2023-53421-0dd9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53441","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53441","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091859-CVE-2023-53441-0641@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53442","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53442","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53442","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091859-CVE-2023-53442-8a1f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53444","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396489","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53444","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53444","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091859-CVE-2023-53444-41d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53451","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400701","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53451","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53451","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100103-CVE-2023-53451-bb02@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53462","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400742","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53462","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100107-CVE-2023-53462-7a33@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53465","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400759","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53465","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53465","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100108-CVE-2023-53465-eb0b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53471","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400800","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53471","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100110-CVE-2023-53471-09f6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53473","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400719","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53473","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100110-CVE-2023-53473-bf5d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53476","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400821","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53476","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100111-CVE-2023-53476-d6d3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53479","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400749","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53479","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53479","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100112-CVE-2023-53479-5c70@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53487","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400784","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53487","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100115-CVE-2023-53487-c3f7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53490","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400760","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53490","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53490","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100123-CVE-2023-53490-c90f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53496","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400813","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53496","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100125-CVE-2023-53496-b145@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53501","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400711","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53501","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100127-CVE-2023-53501-5859@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53513","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400795","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53513","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53513","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100130-CVE-2023-53513-4667@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53525","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400694","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53525","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53525","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100134-CVE-2023-53525-ee57@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53527","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400787","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53527","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100135-CVE-2023-53527-3ce7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53530","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400733","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53530","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53530","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100136-CVE-2023-53530-853b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53536","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401532","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53536","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53536","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100442-CVE-2023-53536-0e4f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53539","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401510","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53539","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53539","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100443-CVE-2023-53539-4411@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53544","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401474","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53544","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100445-CVE-2023-53544-f48f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53545","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401539","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53545","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53545","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100445-CVE-2023-53545-8d50@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53546","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401561","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53546","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100445-CVE-2023-53546-a432@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53547","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401511","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53547","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53547","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100446-CVE-2023-53547-38ce@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53550","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401463","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53550","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53550","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100447-CVE-2023-53550-bbac@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53552","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401514","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53552","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100447-CVE-2023-53552-5ba9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53553","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401552","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53553","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53553","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100448-CVE-2023-53553-f661@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53559","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401489","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53559","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53559","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100449-CVE-2023-53559-c2f0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53563","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401571","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53563","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53563","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100451-CVE-2023-53563-5cbe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53570","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401560","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53570","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100453-CVE-2023-53570-3733@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53577","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401573","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53577","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53577","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100455-CVE-2023-53577-96e9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53580","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401476","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53580","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100423-CVE-2023-53580-7d16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53581","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401545","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53581","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100424-CVE-2023-53581-80fa@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53585","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401495","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53585","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53585","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100425-CVE-2023-53585-b855@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53586","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401541","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53586","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53586","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100425-CVE-2023-53586-67e1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53611","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401557","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53611","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100433-CVE-2023-53611-a508@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53612","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401502","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53612","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100434-CVE-2023-53612-b146@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53615","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401469","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53615","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100435-CVE-2023-53615-843c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53621","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402239","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53621","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100710-CVE-2023-53621-b6f9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402243","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53628","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100712-CVE-2023-53628-a5b2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53632","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402254","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53632","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100713-CVE-2023-53632-d2de@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53645","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402284","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53645","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100717-CVE-2023-53645-6c08@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53646","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402234","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53646","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53646","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100717-CVE-2023-53646-c40e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53647","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402235","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53647","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53647","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100718-CVE-2023-53647-c01f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53649","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402214","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53649","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100718-CVE-2023-53649-0a4a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53652","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402279","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53652","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53652","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100719-CVE-2023-53652-d67a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53655","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402218","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53655","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53655","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100701-CVE-2023-53655-d389@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53657","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402281","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53657","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53657","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100701-CVE-2023-53657-d0c7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53660","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402238","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53660","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100702-CVE-2023-53660-92d3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53661","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402245","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53661","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53661","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100702-CVE-2023-53661-6142@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53663","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402209","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53663","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100703-CVE-2023-53663-0a4e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53664","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402206","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53664","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100703-CVE-2023-53664-a38d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53665","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402216","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53665","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100704-CVE-2023-53665-3411@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53666","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402299","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53666","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53666","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100704-CVE-2023-53666-62bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53673","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402193","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53673","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100706-CVE-2023-53673-36b9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53677","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402203","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53677","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100707-CVE-2023-53677-1cc8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53696","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405745","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53696","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102210-CVE-2023-53696-dadf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53709","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405758","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53709","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102212-CVE-2023-53709-553a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53711","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405779","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53711","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53711","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102213-CVE-2023-53711-24c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53713","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405753","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53713","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102213-CVE-2023-53713-550a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53722","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405756","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53722","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53722","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102215-CVE-2023-53722-f3ab@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53726","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405768","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53726","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102215-CVE-2023-53726-29cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53730","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405738","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53730","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102216-CVE-2023-53730-d257@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53743","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419914","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53743","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120840-CVE-2023-53743-5da6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53751","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419858","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53751","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53751","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120842-CVE-2023-53751-2ff2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53761","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419892","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53761","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120844-CVE-2023-53761-ea1d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53762","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419838","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53762","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53762","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120845-CVE-2023-53762-01bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53784","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420246","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53784","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53784","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120939-CVE-2023-53784-a381@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53791","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420251","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53791","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120941-CVE-2023-53791-a2ea@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53795","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420238","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53795","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120941-CVE-2023-53795-f912@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53806","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420232","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53806","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53806","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120943-CVE-2023-53806-03cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53810","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420280","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53810","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53810","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120944-CVE-2023-53810-e48e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53813","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420286","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53813","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120944-CVE-2023-53813-cd16@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53819","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420264","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53819","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120945-CVE-2023-53819-15be@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53821","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420329","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53821","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120950-CVE-2023-53821-9542@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53823","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420361","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53823","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120950-CVE-2023-53823-c6fe@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53833","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420366","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53833","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120954-CVE-2023-53833-09d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53842","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420310","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53842","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53842","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120957-CVE-2023-53842-d1e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53843","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420327","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53843","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120958-CVE-2023-53843-195d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53844","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420316","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53844","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53844","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120958-CVE-2023-53844-92b4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420349","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53847","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120959-CVE-2023-53847-1f94@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53848","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420331","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53848","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120900-CVE-2023-53848-8cd8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53857","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420362","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53857","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120903-CVE-2023-53857-5513@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53860","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420339","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53860","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120904-CVE-2023-53860-3722@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53863","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420333","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53863","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120905-CVE-2023-53863-8742@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53990","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424954","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53990","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122423-CVE-2023-53990-b239@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53992","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424955","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53992","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122424-CVE-2023-53992-d45e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53993","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424965","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53993","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53993","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122424-CVE-2023-53993-7ec2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53995","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424967","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53995","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122425-CVE-2023-53995-1860@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53999","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424951","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53999","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122426-CVE-2023-53999-57a4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54003","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424996","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54003","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122427-CVE-2023-54003-01b7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54006","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425000","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54006","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122428-CVE-2023-54006-d646@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54008","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424928","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54008","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122429-CVE-2023-54008-cfde@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54014","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424950","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54014","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122431-CVE-2023-54014-9b8c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54016","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424971","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54016","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122432-CVE-2023-54016-522e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54021","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424989","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54021","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122433-CVE-2023-54021-15bf@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54022","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424937","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54022","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122434-CVE-2023-54022-ae26@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54026","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424932","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54026","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122435-CVE-2023-54026-123c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54028","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424983","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54028","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122436-CVE-2023-54028-2399@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54030","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424968","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54030","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122436-CVE-2023-54030-e7f3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54031","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424991","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54031","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122437-CVE-2023-54031-90af@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54033","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424986","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54033","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122437-CVE-2023-54033-ad11@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54035","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424970","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54035","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122438-CVE-2023-54035-76a5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54038","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424931","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54038","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122439-CVE-2023-54038-41bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54048","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425013","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54048","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122424-CVE-2023-54048-ea7d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54052","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425052","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54052","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122425-CVE-2023-54052-302d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54060","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425045","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54060","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122428-CVE-2023-54060-2029@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54062","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425016","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54062","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122428-CVE-2023-54062-d861@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54064","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425018","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54064","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122429-CVE-2023-54064-7509@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54069","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425063","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54069","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122431-CVE-2023-54069-1a17@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54070","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425050","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54070","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122431-CVE-2023-54070-6104@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54072","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425014","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54072","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122432-CVE-2023-54072-4a34@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54076","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425075","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54076","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122433-CVE-2023-54076-e317@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54090","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425098","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54090","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122406-CVE-2023-54090-2944@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54091","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425176","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54091","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122407-CVE-2023-54091-577a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54096","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425131","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54096","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122408-CVE-2023-54096-efde@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54100","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425099","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54100","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122410-CVE-2023-54100-91a9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54106","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425199","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54106","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54106","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122412-CVE-2023-54106-b8da@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54120","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425183","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54120","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122416-CVE-2023-54120-d966@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54135","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425167","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54135","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122421-CVE-2023-54135-ffa3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54137","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425187","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54137","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122422-CVE-2023-54137-1873@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54141","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425142","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54141","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122423-CVE-2023-54141-86e5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54145","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54145","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122424-CVE-2023-54145-421d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54148","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425103","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54148","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122425-CVE-2023-54148-569b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54154","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425166","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54154","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122427-CVE-2023-54154-bc1e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54155","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425206","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54155","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122427-CVE-2023-54155-e238@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54156","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425100","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54156","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122428-CVE-2023-54156-832a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54160","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425143","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54160","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122429-CVE-2023-54160-ed90@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54166","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426051","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54166","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54166","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123019-CVE-2023-54166-baff@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54169","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426227","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54169","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123020-CVE-2023-54169-21bb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54170","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426038","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54170","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54170","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123020-CVE-2023-54170-f1c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54173","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426128","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54173","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2023-54173-2f44@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54179","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426244","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54179","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54179","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123023-CVE-2023-54179-e6e3@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54184","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426090","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54184","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54184","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123025-CVE-2023-54184-e958@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54186","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426180","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54186","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123026-CVE-2023-54186-a9c9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54197","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426140","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54197","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123029-CVE-2023-54197-aeec@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54201","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426049","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54201","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54201","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123030-CVE-2023-54201-3f26@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54214","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426069","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54214","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123025-CVE-2023-54214-c4a6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54215","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426168","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54215","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123025-CVE-2023-54215-d1c0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54221","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426031","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54221","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123027-CVE-2023-54221-567b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54229","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426256","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54229","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123030-CVE-2023-54229-80e7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54235","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426233","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54235","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123032-CVE-2023-54235-51bc@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54242","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426210","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54242","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54242","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123034-CVE-2023-54242-9771@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54251","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426020","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54251","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123054-CVE-2023-54251-2a3b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54254","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426011","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54254","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123055-CVE-2023-54254-8a3e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54260","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426234","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54260","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54260","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123057-CVE-2023-54260-cc1d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54261","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426154","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54261","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123057-CVE-2023-54261-0331@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54263","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426033","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54263","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54263","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123058-CVE-2023-54263-0976@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54274","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426026","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54274","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54274","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123002-CVE-2023-54274-79a7@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54283","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54283","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123026-CVE-2023-54283-b319@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54289","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426167","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54289","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123028-CVE-2023-54289-5309@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54292","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426208","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54292","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123029-CVE-2023-54292-26cb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54296","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426083","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54296","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123031-CVE-2023-54296-e667@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54302","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426187","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54302","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123033-CVE-2023-54302-a9e9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54303","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426113","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54303","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123033-CVE-2023-54303-0e92@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54312","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54312","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123036-CVE-2023-54312-8b23@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54316","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426135","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54316","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123037-CVE-2023-54316-f3c8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54324","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426236","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54324","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123015-CVE-2023-54324-7149@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54326","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426228","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54326","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54326","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123016-CVE-2023-54326-43b2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-0565","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-0565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-0565","tags":["advisory"]},{"url":"https://www.spinics.net/lists/stable-commits/msg328851.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-0841","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-0841","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-0841","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-1085","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-1085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-1085","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b1db244ffd041a49ecc9618e8feb6b5c1afcdaa7","tags":["article"]},{"url":"https://kernel.dance/b1db244ffd041a49ecc9618e8feb6b5c1afcdaa7","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-1086","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-1086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-1086","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f342de4e2f33e0e39165d8639387aa6c19dff660","tags":["article"]},{"url":"https://kernel.dance/f342de4e2f33e0e39165d8639387aa6c19dff660","tags":["article"]},{"url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-25744","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2263875","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-25744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-25744","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b82a8dbd3d2f4563156f7150c6f2ecab6e960b30","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26582","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26582","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022139-spruce-prelude-c358@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26583","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26583","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022146-traction-unjustly-f451@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26584","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26584","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26584","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022148-showpiece-yanking-107c@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26585","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26585","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26585","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022150-fancy-numerate-94ab@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26586","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26586","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26586","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022253-CVE-2024-26586-6632@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26593","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26593","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26593","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022315-CVE-2024-26593-9d89@gregkh/T/#u","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26602","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26602","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/944d5fe50f3f03daacfea16300e656a1691c4a23","tags":["article"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024022414-CVE-2024-26602-5e76@gregkh/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26609","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26609","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-41-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26633","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26633","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26633","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-16-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26649","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271796","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26649","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-17-lee@kernel.org/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26671","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2272811","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26671","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26671-2543@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-26830","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2275596","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-26830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26830","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2024041703-CVE-2024-26830-5bc0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-38053","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373362","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-38053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38053","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061832-CVE-2025-38053-e145@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/errata/RHSA-2024:2950","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.10_release_notes/index","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1731000","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1746732","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1888726","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1999589","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2039178","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2043520","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2044578","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2150953","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2179892","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2226784","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2230042","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2235306","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2239847","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2257979","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2270836","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_2950.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-13631","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-13631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-13631","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-15505","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-15505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-15505","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2020-25656","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-25656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-25656","tags":["advisory"]},{"url":"https://lkml.org/lkml/2020/10/16/84","tags":["article"]},{"url":"https://lkml.org/lkml/2020/10/29/528","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-3753","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-3753","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-3753","tags":["advisory"]},{"url":"https://github.com/torvalds/linux/commit/2287a51ba822384834dafc1c798453375d1107c7","tags":["article"]},{"url":"https://www.openwall.com/lists/oss-security/2021/09/01/4","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-4204","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-4204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-4204","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2022/01/11/4","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-0500","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-0500","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-0500","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=20b2aff4bc15bda809f994761d5719827d66c0b4","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=216e3cd2f28dbbf1fe86848e0e29e6693b9f0a20","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34d3a78c681e8e7844b43d1a2f4671a04249c821","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c4807322660d4290ac9062c034aed6b87243861","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=48946bd6a5d695c50b34546864b79c1f910a33c1","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c25b2ae136039ffa820c26138ed4a5e5f3ab3841","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cf9f2f8d62eca810afbd1ee6cc0800202b000e57","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3565","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3565","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-23222","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-23222","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-23222","tags":["advisory"]},{"url":"https://www.openwall.com/lists/oss-security/2022/01/13/1","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-1513","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-1513","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-1513","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-4244","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-4244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-4244","tags":["advisory"]},{"url":"https://lore.kernel.org/netdev/20230810070830.24064-1-pablo@netfilter.org/","tags":["article"]},{"url":"https://lore.kernel.org/netdev/20230815223011.7019-1-fw@strlen.de/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-38409","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-38409","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-38409","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=fffb0b52d5258554c645c966c6cbef7de50b851d","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-39192","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-39192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-39192","tags":["advisory"]},{"url":"https://www.zerodayinitiative.com/advisories/ZDI-CAN-18408/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-42755","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-42755","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-42755","tags":["advisory"]},{"url":"https://seclists.org/oss-sec/2023/q3/229","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-52340","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-52340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52340","tags":["advisory"]},{"url":"https://alas.aws.amazon.com/cve/html/CVE-2023-52340.html","tags":["article"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=af6d10345ca76670c1b7c37799f0d5576ccef277","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-25742","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-25742","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-25743","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-25743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-25743","tags":["advisory"]},{"url":"https://arxiv.org/html/2404.03526v1","tags":["article"]},{"url":"https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3008.html","tags":["article"]},{"url":"https://access.redhat.com/errata/RHSA-2024:3138","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1930388","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2231130","tags":["report"]},{"url":"https://issues.redhat.com/browse/RHEL-15148","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-15311","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-6030","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-7994","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-9128","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_3138.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49081","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2347739","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49081","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49081","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022657-CVE-2022-49081-7a0f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49700","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2348237","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49700","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025022629-CVE-2022-49700-2b3e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49759","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2355497","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49759","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025032702-CVE-2022-49759-5392@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-49885","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363361","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-49885","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49885","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050156-CVE-2022-49885-efae@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50126","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373442","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50126","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061813-CVE-2022-50126-5c77@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50153","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2373447","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50153","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025061822-CVE-2022-50153-d408@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50274","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395314","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50274","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50274","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091505-CVE-2022-50274-ad8d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50327","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395438","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50327","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50327","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091554-CVE-2022-50327-5d27@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50344","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395860","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50344","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091639-CVE-2022-50344-8893@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50403","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396494","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50403","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091852-CVE-2022-50403-0471@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50423","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400780","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50423","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50423","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100155-CVE-2022-50423-5a66@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50546","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402240","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50546","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100757-CVE-2022-50546-ef71@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50635","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420274","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50635","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120935-CVE-2022-50635-b2b8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50668","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420350","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50668","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120945-CVE-2022-50668-153a@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50717","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425070","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50717","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50717","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122416-CVE-2022-50717-dc68@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-50730","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425043","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-50730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50730","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122420-CVE-2022-50730-a4ca@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53070","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363685","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53070","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050213-CVE-2023-53070-d7b8@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53072","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363749","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53072","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050213-CVE-2023-53072-4ab2@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53088","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363766","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53088","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050219-CVE-2023-53088-501c@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53089","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363736","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53089","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050219-CVE-2023-53089-b8c6@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53103","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2363728","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53103","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025050224-CVE-2023-53103-9c37@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53182","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395248","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53182","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091556-CVE-2023-53182-dcdb@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53205","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395415","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53205","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53205","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091510-CVE-2023-53205-9a2b@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53224","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395241","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53224","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091513-CVE-2023-53224-190d@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53266","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2395670","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53266","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53266","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091602-CVE-2023-53266-f945@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53392","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2396427","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53392","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025091858-CVE-2023-53392-9703@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53483","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2400788","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53483","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100113-CVE-2023-53483-cf50@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53576","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2401524","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53576","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53576","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100454-CVE-2023-53576-c5dd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53623","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402289","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53623","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53623","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100710-CVE-2023-53623-2687@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53648","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2402287","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53648","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53648","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025100718-CVE-2023-53648-3c04@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53698","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405730","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53698","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102211-CVE-2023-53698-c1f4@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53705","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2405713","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53705","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025102212-CVE-2023-53705-38d9@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53746","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2419839","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53746","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120841-CVE-2023-53746-cbfd@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53798","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2420252","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53798","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025120942-CVE-2023-53798-7845@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53867","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424984","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53867","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122422-CVE-2023-53867-cb3e@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-53996","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424944","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-53996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53996","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122425-CVE-2023-53996-2c23@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54004","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424964","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54004","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122428-CVE-2023-54004-34a0@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54010","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424948","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54010","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122430-CVE-2023-54010-9ff1@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54057","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2425015","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54057","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025122427-CVE-2023-54057-f0c5@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54244","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426096","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54244","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123052-CVE-2023-54244-9a1f@gregkh/T","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-54320","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2426195","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-54320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54320","tags":["advisory"]},{"url":"https://lore.kernel.org/linux-cve-announce/2025123021-CVE-2023-54320-465d@gregkh/T","tags":["article"]},{"url":"https://errata.rockylinux.org/RXSA-2024:3138","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240856-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1155518","tags":["report"]},{"url":"https://bugzilla.suse.com/1184436","tags":["report"]},{"url":"https://bugzilla.suse.com/1185988","tags":["report"]},{"url":"https://bugzilla.suse.com/1186286","tags":["report"]},{"url":"https://bugzilla.suse.com/1200599","tags":["report"]},{"url":"https://bugzilla.suse.com/1207653","tags":["report"]},{"url":"https://bugzilla.suse.com/1212514","tags":["report"]},{"url":"https://bugzilla.suse.com/1213456","tags":["report"]},{"url":"https://bugzilla.suse.com/1216223","tags":["report"]},{"url":"https://bugzilla.suse.com/1218195","tags":["report"]},{"url":"https://bugzilla.suse.com/1218689","tags":["report"]},{"url":"https://bugzilla.suse.com/1218915","tags":["report"]},{"url":"https://bugzilla.suse.com/1219127","tags":["report"]},{"url":"https://bugzilla.suse.com/1219128","tags":["report"]},{"url":"https://bugzilla.suse.com/1219146","tags":["report"]},{"url":"https://bugzilla.suse.com/1219295","tags":["report"]},{"url":"https://bugzilla.suse.com/1219653","tags":["report"]},{"url":"https://bugzilla.suse.com/1219827","tags":["report"]},{"url":"https://bugzilla.suse.com/1219835","tags":["report"]},{"url":"https://bugzilla.suse.com/1219915","tags":["report"]},{"url":"https://bugzilla.suse.com/1220009","tags":["report"]},{"url":"https://bugzilla.suse.com/1220140","tags":["report"]},{"url":"https://bugzilla.suse.com/1220187","tags":["report"]},{"url":"https://bugzilla.suse.com/1220238","tags":["report"]},{"url":"https://bugzilla.suse.com/1220240","tags":["report"]},{"url":"https://bugzilla.suse.com/1220241","tags":["report"]},{"url":"https://bugzilla.suse.com/1220243","tags":["report"]},{"url":"https://bugzilla.suse.com/1220250","tags":["report"]},{"url":"https://bugzilla.suse.com/1220253","tags":["report"]},{"url":"https://bugzilla.suse.com/1220255","tags":["report"]},{"url":"https://bugzilla.suse.com/1220328","tags":["report"]},{"url":"https://bugzilla.suse.com/1220330","tags":["report"]},{"url":"https://bugzilla.suse.com/1220344","tags":["report"]},{"url":"https://bugzilla.suse.com/1220398","tags":["report"]},{"url":"https://bugzilla.suse.com/1220409","tags":["report"]},{"url":"https://bugzilla.suse.com/1220416","tags":["report"]},{"url":"https://bugzilla.suse.com/1220418","tags":["report"]},{"url":"https://bugzilla.suse.com/1220421","tags":["report"]},{"url":"https://bugzilla.suse.com/1220436","tags":["report"]},{"url":"https://bugzilla.suse.com/1220444","tags":["report"]},{"url":"https://bugzilla.suse.com/1220459","tags":["report"]},{"url":"https://bugzilla.suse.com/1220469","tags":["report"]},{"url":"https://bugzilla.suse.com/1220482","tags":["report"]},{"url":"https://bugzilla.suse.com/1220526","tags":["report"]},{"url":"https://bugzilla.suse.com/1220538","tags":["report"]},{"url":"https://bugzilla.suse.com/1220570","tags":["report"]},{"url":"https://bugzilla.suse.com/1220572","tags":["report"]},{"url":"https://bugzilla.suse.com/1220599","tags":["report"]},{"url":"https://bugzilla.suse.com/1220627","tags":["report"]},{"url":"https://bugzilla.suse.com/1220641","tags":["report"]},{"url":"https://bugzilla.suse.com/1220649","tags":["report"]},{"url":"https://bugzilla.suse.com/1220660","tags":["report"]},{"url":"https://bugzilla.suse.com/1220700","tags":["report"]},{"url":"https://bugzilla.suse.com/1220735","tags":["report"]},{"url":"https://bugzilla.suse.com/1220736","tags":["report"]},{"url":"https://bugzilla.suse.com/1220737","tags":["report"]},{"url":"https://bugzilla.suse.com/1220742","tags":["report"]},{"url":"https://bugzilla.suse.com/1220745","tags":["report"]},{"url":"https://bugzilla.suse.com/1220767","tags":["report"]},{"url":"https://bugzilla.suse.com/1220796","tags":["report"]},{"url":"https://bugzilla.suse.com/1220825","tags":["report"]},{"url":"https://bugzilla.suse.com/1220826","tags":["report"]},{"url":"https://bugzilla.suse.com/1220831","tags":["report"]},{"url":"https://bugzilla.suse.com/1220845","tags":["report"]},{"url":"https://bugzilla.suse.com/1220860","tags":["report"]},{"url":"https://bugzilla.suse.com/1220863","tags":["report"]},{"url":"https://bugzilla.suse.com/1220870","tags":["report"]},{"url":"https://bugzilla.suse.com/1220917","tags":["report"]},{"url":"https://bugzilla.suse.com/1220918","tags":["report"]},{"url":"https://bugzilla.suse.com/1220930","tags":["report"]},{"url":"https://bugzilla.suse.com/1220931","tags":["report"]},{"url":"https://bugzilla.suse.com/1220932","tags":["report"]},{"url":"https://bugzilla.suse.com/1221039","tags":["report"]},{"url":"https://bugzilla.suse.com/1221040","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2019-25162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-36777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-36784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-20154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48627","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-35827","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-46343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-51042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-0340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-0607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-1151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26622","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240857-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1220689","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240925-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1050549","tags":["report"]},{"url":"https://bugzilla.suse.com/1186484","tags":["report"]},{"url":"https://bugzilla.suse.com/1218450","tags":["report"]},{"url":"https://bugzilla.suse.com/1218527","tags":["report"]},{"url":"https://bugzilla.suse.com/1220340","tags":["report"]},{"url":"https://bugzilla.suse.com/1220468","tags":["report"]},{"url":"https://bugzilla.suse.com/1220575","tags":["report"]},{"url":"https://bugzilla.suse.com/1220607","tags":["report"]},{"url":"https://bugzilla.suse.com/1220613","tags":["report"]},{"url":"https://bugzilla.suse.com/1220638","tags":["report"]},{"url":"https://bugzilla.suse.com/1220861","tags":["report"]},{"url":"https://bugzilla.suse.com/1220957","tags":["report"]},{"url":"https://bugzilla.suse.com/1221287","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-33200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26600","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240926-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240975-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1217987","tags":["report"]},{"url":"https://bugzilla.suse.com/1217988","tags":["report"]},{"url":"https://bugzilla.suse.com/1217989","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6536","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240976-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241320-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1220237","tags":["report"]},{"url":"https://bugzilla.suse.com/1220320","tags":["report"]},{"url":"https://bugzilla.suse.com/1220366","tags":["report"]},{"url":"https://bugzilla.suse.com/1220411","tags":["report"]},{"url":"https://bugzilla.suse.com/1220413","tags":["report"]},{"url":"https://bugzilla.suse.com/1220439","tags":["report"]},{"url":"https://bugzilla.suse.com/1220443","tags":["report"]},{"url":"https://bugzilla.suse.com/1220445","tags":["report"]},{"url":"https://bugzilla.suse.com/1220466","tags":["report"]},{"url":"https://bugzilla.suse.com/1220478","tags":["report"]},{"url":"https://bugzilla.suse.com/1220484","tags":["report"]},{"url":"https://bugzilla.suse.com/1220486","tags":["report"]},{"url":"https://bugzilla.suse.com/1220487","tags":["report"]},{"url":"https://bugzilla.suse.com/1220790","tags":["report"]},{"url":"https://bugzilla.suse.com/1220833","tags":["report"]},{"url":"https://bugzilla.suse.com/1220836","tags":["report"]},{"url":"https://bugzilla.suse.com/1220839","tags":["report"]},{"url":"https://bugzilla.suse.com/1220840","tags":["report"]},{"url":"https://bugzilla.suse.com/1220843","tags":["report"]},{"url":"https://bugzilla.suse.com/1220871","tags":["report"]},{"url":"https://bugzilla.suse.com/1220872","tags":["report"]},{"url":"https://bugzilla.suse.com/1220878","tags":["report"]},{"url":"https://bugzilla.suse.com/1220879","tags":["report"]},{"url":"https://bugzilla.suse.com/1220885","tags":["report"]},{"url":"https://bugzilla.suse.com/1220898","tags":["report"]},{"url":"https://bugzilla.suse.com/1220920","tags":["report"]},{"url":"https://bugzilla.suse.com/1220921","tags":["report"]},{"url":"https://bugzilla.suse.com/1220926","tags":["report"]},{"url":"https://bugzilla.suse.com/1220927","tags":["report"]},{"url":"https://bugzilla.suse.com/1220929","tags":["report"]},{"url":"https://bugzilla.suse.com/1220938","tags":["report"]},{"url":"https://bugzilla.suse.com/1220940","tags":["report"]},{"url":"https://bugzilla.suse.com/1220954","tags":["report"]},{"url":"https://bugzilla.suse.com/1220955","tags":["report"]},{"url":"https://bugzilla.suse.com/1220959","tags":["report"]},{"url":"https://bugzilla.suse.com/1220960","tags":["report"]},{"url":"https://bugzilla.suse.com/1220961","tags":["report"]},{"url":"https://bugzilla.suse.com/1220965","tags":["report"]},{"url":"https://bugzilla.suse.com/1220969","tags":["report"]},{"url":"https://bugzilla.suse.com/1220978","tags":["report"]},{"url":"https://bugzilla.suse.com/1220979","tags":["report"]},{"url":"https://bugzilla.suse.com/1220981","tags":["report"]},{"url":"https://bugzilla.suse.com/1220982","tags":["report"]},{"url":"https://bugzilla.suse.com/1220983","tags":["report"]},{"url":"https://bugzilla.suse.com/1220985","tags":["report"]},{"url":"https://bugzilla.suse.com/1220986","tags":["report"]},{"url":"https://bugzilla.suse.com/1220987","tags":["report"]},{"url":"https://bugzilla.suse.com/1220989","tags":["report"]},{"url":"https://bugzilla.suse.com/1220990","tags":["report"]},{"url":"https://bugzilla.suse.com/1221009","tags":["report"]},{"url":"https://bugzilla.suse.com/1221012","tags":["report"]},{"url":"https://bugzilla.suse.com/1221015","tags":["report"]},{"url":"https://bugzilla.suse.com/1221022","tags":["report"]},{"url":"https://bugzilla.suse.com/1221048","tags":["report"]},{"url":"https://bugzilla.suse.com/1221055","tags":["report"]},{"url":"https://bugzilla.suse.com/1221058","tags":["report"]},{"url":"https://bugzilla.suse.com/1221077","tags":["report"]},{"url":"https://bugzilla.suse.com/1221276","tags":["report"]},{"url":"https://bugzilla.suse.com/1221551","tags":["report"]},{"url":"https://bugzilla.suse.com/1221553","tags":["report"]},{"url":"https://bugzilla.suse.com/1221725","tags":["report"]},{"url":"https://bugzilla.suse.com/1222073","tags":["report"]},{"url":"https://bugzilla.suse.com/1222619","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-46936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48626","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52517","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52520","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52523","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52524","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52621","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-25742","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241321-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1209635","tags":["report"]},{"url":"https://bugzilla.suse.com/1220251","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52447","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241466-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1200465","tags":["report"]},{"url":"https://bugzilla.suse.com/1205316","tags":["report"]},{"url":"https://bugzilla.suse.com/1207948","tags":["report"]},{"url":"https://bugzilla.suse.com/1209657","tags":["report"]},{"url":"https://bugzilla.suse.com/1214852","tags":["report"]},{"url":"https://bugzilla.suse.com/1215221","tags":["report"]},{"url":"https://bugzilla.suse.com/1215322","tags":["report"]},{"url":"https://bugzilla.suse.com/1217339","tags":["report"]},{"url":"https://bugzilla.suse.com/1217829","tags":["report"]},{"url":"https://bugzilla.suse.com/1217959","tags":["report"]},{"url":"https://bugzilla.suse.com/1218321","tags":["report"]},{"url":"https://bugzilla.suse.com/1218336","tags":["report"]},{"url":"https://bugzilla.suse.com/1218479","tags":["report"]},{"url":"https://bugzilla.suse.com/1218562","tags":["report"]},{"url":"https://bugzilla.suse.com/1218643","tags":["report"]},{"url":"https://bugzilla.suse.com/1218777","tags":["report"]},{"url":"https://bugzilla.suse.com/1219169","tags":["report"]},{"url":"https://bugzilla.suse.com/1219170","tags":["report"]},{"url":"https://bugzilla.suse.com/1219264","tags":["report"]},{"url":"https://bugzilla.suse.com/1219834","tags":["report"]},{"url":"https://bugzilla.suse.com/1220114","tags":["report"]},{"url":"https://bugzilla.suse.com/1220176","tags":["report"]},{"url":"https://bugzilla.suse.com/1220325","tags":["report"]},{"url":"https://bugzilla.suse.com/1220337","tags":["report"]},{"url":"https://bugzilla.suse.com/1220365","tags":["report"]},{"url":"https://bugzilla.suse.com/1220433","tags":["report"]},{"url":"https://bugzilla.suse.com/1220492","tags":["report"]},{"url":"https://bugzilla.suse.com/1220703","tags":["report"]},{"url":"https://bugzilla.suse.com/1220775","tags":["report"]},{"url":"https://bugzilla.suse.com/1220797","tags":["report"]},{"url":"https://bugzilla.suse.com/1220848","tags":["report"]},{"url":"https://bugzilla.suse.com/1220883","tags":["report"]},{"url":"https://bugzilla.suse.com/1220887","tags":["report"]},{"url":"https://bugzilla.suse.com/1220933","tags":["report"]},{"url":"https://bugzilla.suse.com/1220937","tags":["report"]},{"url":"https://bugzilla.suse.com/1221044","tags":["report"]},{"url":"https://bugzilla.suse.com/1221045","tags":["report"]},{"url":"https://bugzilla.suse.com/1221046","tags":["report"]},{"url":"https://bugzilla.suse.com/1221056","tags":["report"]},{"url":"https://bugzilla.suse.com/1221060","tags":["report"]},{"url":"https://bugzilla.suse.com/1221061","tags":["report"]},{"url":"https://bugzilla.suse.com/1221062","tags":["report"]},{"url":"https://bugzilla.suse.com/1221066","tags":["report"]},{"url":"https://bugzilla.suse.com/1221067","tags":["report"]},{"url":"https://bugzilla.suse.com/1221068","tags":["report"]},{"url":"https://bugzilla.suse.com/1221069","tags":["report"]},{"url":"https://bugzilla.suse.com/1221070","tags":["report"]},{"url":"https://bugzilla.suse.com/1221071","tags":["report"]},{"url":"https://bugzilla.suse.com/1221082","tags":["report"]},{"url":"https://bugzilla.suse.com/1221090","tags":["report"]},{"url":"https://bugzilla.suse.com/1221097","tags":["report"]},{"url":"https://bugzilla.suse.com/1221156","tags":["report"]},{"url":"https://bugzilla.suse.com/1221252","tags":["report"]},{"url":"https://bugzilla.suse.com/1221273","tags":["report"]},{"url":"https://bugzilla.suse.com/1221274","tags":["report"]},{"url":"https://bugzilla.suse.com/1221277","tags":["report"]},{"url":"https://bugzilla.suse.com/1221291","tags":["report"]},{"url":"https://bugzilla.suse.com/1221293","tags":["report"]},{"url":"https://bugzilla.suse.com/1221298","tags":["report"]},{"url":"https://bugzilla.suse.com/1221337","tags":["report"]},{"url":"https://bugzilla.suse.com/1221338","tags":["report"]},{"url":"https://bugzilla.suse.com/1221375","tags":["report"]},{"url":"https://bugzilla.suse.com/1221379","tags":["report"]},{"url":"https://bugzilla.suse.com/1221613","tags":["report"]},{"url":"https://bugzilla.suse.com/1221614","tags":["report"]},{"url":"https://bugzilla.suse.com/1221616","tags":["report"]},{"url":"https://bugzilla.suse.com/1221618","tags":["report"]},{"url":"https://bugzilla.suse.com/1221631","tags":["report"]},{"url":"https://bugzilla.suse.com/1221633","tags":["report"]},{"url":"https://bugzilla.suse.com/1221713","tags":["report"]},{"url":"https://bugzilla.suse.com/1221777","tags":["report"]},{"url":"https://bugzilla.suse.com/1221814","tags":["report"]},{"url":"https://bugzilla.suse.com/1221816","tags":["report"]},{"url":"https://bugzilla.suse.com/1221830","tags":["report"]},{"url":"https://bugzilla.suse.com/1221951","tags":["report"]},{"url":"https://bugzilla.suse.com/1222033","tags":["report"]},{"url":"https://bugzilla.suse.com/1222056","tags":["report"]},{"url":"https://bugzilla.suse.com/1222060","tags":["report"]},{"url":"https://bugzilla.suse.com/1222070","tags":["report"]},{"url":"https://bugzilla.suse.com/1222117","tags":["report"]},{"url":"https://bugzilla.suse.com/1222274","tags":["report"]},{"url":"https://bugzilla.suse.com/1222291","tags":["report"]},{"url":"https://bugzilla.suse.com/1222300","tags":["report"]},{"url":"https://bugzilla.suse.com/1222304","tags":["report"]},{"url":"https://bugzilla.suse.com/1222317","tags":["report"]},{"url":"https://bugzilla.suse.com/1222331","tags":["report"]},{"url":"https://bugzilla.suse.com/1222355","tags":["report"]},{"url":"https://bugzilla.suse.com/1222356","tags":["report"]},{"url":"https://bugzilla.suse.com/1222360","tags":["report"]},{"url":"https://bugzilla.suse.com/1222366","tags":["report"]},{"url":"https://bugzilla.suse.com/1222373","tags":["report"]},{"url":"https://bugzilla.suse.com/1222952","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52486","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52617","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-7042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-7192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-0841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-2201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-22099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-25739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26614","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26627","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26717","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241480-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1219443","tags":["report"]},{"url":"https://bugzilla.suse.com/1220393","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-25743","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241490-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1177529","tags":["report"]},{"url":"https://bugzilla.suse.com/1192145","tags":["report"]},{"url":"https://bugzilla.suse.com/1219126","tags":["report"]},{"url":"https://bugzilla.suse.com/1220901","tags":["report"]},{"url":"https://bugzilla.suse.com/1220915","tags":["report"]},{"url":"https://bugzilla.suse.com/1220935","tags":["report"]},{"url":"https://bugzilla.suse.com/1221162","tags":["report"]},{"url":"https://bugzilla.suse.com/1221791","tags":["report"]},{"url":"https://bugzilla.suse.com/1222011","tags":["report"]},{"url":"https://bugzilla.suse.com/1222051","tags":["report"]},{"url":"https://bugzilla.suse.com/1222247","tags":["report"]},{"url":"https://bugzilla.suse.com/1222266","tags":["report"]},{"url":"https://bugzilla.suse.com/1222416","tags":["report"]},{"url":"https://bugzilla.suse.com/1222422","tags":["report"]},{"url":"https://bugzilla.suse.com/1222427","tags":["report"]},{"url":"https://bugzilla.suse.com/1222428","tags":["report"]},{"url":"https://bugzilla.suse.com/1222431","tags":["report"]},{"url":"https://bugzilla.suse.com/1222437","tags":["report"]},{"url":"https://bugzilla.suse.com/1222445","tags":["report"]},{"url":"https://bugzilla.suse.com/1222449","tags":["report"]},{"url":"https://bugzilla.suse.com/1222503","tags":["report"]},{"url":"https://bugzilla.suse.com/1222520","tags":["report"]},{"url":"https://bugzilla.suse.com/1222536","tags":["report"]},{"url":"https://bugzilla.suse.com/1222549","tags":["report"]},{"url":"https://bugzilla.suse.com/1222550","tags":["report"]},{"url":"https://bugzilla.suse.com/1222557","tags":["report"]},{"url":"https://bugzilla.suse.com/1222585","tags":["report"]},{"url":"https://bugzilla.suse.com/1222586","tags":["report"]},{"url":"https://bugzilla.suse.com/1222596","tags":["report"]},{"url":"https://bugzilla.suse.com/1222609","tags":["report"]},{"url":"https://bugzilla.suse.com/1222610","tags":["report"]},{"url":"https://bugzilla.suse.com/1222630","tags":["report"]},{"url":"https://bugzilla.suse.com/1222632","tags":["report"]},{"url":"https://bugzilla.suse.com/1222660","tags":["report"]},{"url":"https://bugzilla.suse.com/1222662","tags":["report"]},{"url":"https://bugzilla.suse.com/1222664","tags":["report"]},{"url":"https://bugzilla.suse.com/1222669","tags":["report"]},{"url":"https://bugzilla.suse.com/1222677","tags":["report"]},{"url":"https://bugzilla.suse.com/1222678","tags":["report"]},{"url":"https://bugzilla.suse.com/1222680","tags":["report"]},{"url":"https://bugzilla.suse.com/1222706","tags":["report"]},{"url":"https://bugzilla.suse.com/1222720","tags":["report"]},{"url":"https://bugzilla.suse.com/1222724","tags":["report"]},{"url":"https://bugzilla.suse.com/1222726","tags":["report"]},{"url":"https://bugzilla.suse.com/1222727","tags":["report"]},{"url":"https://bugzilla.suse.com/1222764","tags":["report"]},{"url":"https://bugzilla.suse.com/1222772","tags":["report"]},{"url":"https://bugzilla.suse.com/1222781","tags":["report"]},{"url":"https://bugzilla.suse.com/1222784","tags":["report"]},{"url":"https://bugzilla.suse.com/1222798","tags":["report"]},{"url":"https://bugzilla.suse.com/1222801","tags":["report"]},{"url":"https://bugzilla.suse.com/1223030","tags":["report"]},{"url":"https://bugzilla.suse.com/1223067","tags":["report"]},{"url":"https://bugzilla.suse.com/1223068","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-47189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52561","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52627","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-23850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26776","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26779","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26848","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2023-52597","tags":["report"]},{"url":"https://git.kernel.org/linus/b988b1bb0053c0dcd26187d29ef07566a565cf55","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-6688-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6766-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6767-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6767-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6766-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6766-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6795-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6818-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6819-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6818-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6828-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6819-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6819-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6818-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6818-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-6819-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2023-5633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-6610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-46838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-50431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-0340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-1085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-1086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-24860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26628","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52435","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-1151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-2201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-47233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-6356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-6535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-6536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-21823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35837","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-6270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-7042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-0841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-22099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-27436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-35845","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2023-52597","title":"KVM: s390: fix setting of fpc register","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: fix setting of fpc register\n\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\n\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\n\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\n\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\n\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\n\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.","status":"published","published":"2024-03-06T06:45:26.608Z","modified":"2026-05-11T19:30:04.359Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium","assessor":"adp"}],"updated_at":"2026-11-02T14:35:18.508816Z"}],"euvd":[{"id":"EUVD-2023-57221","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: fix setting of fpc register\n\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\n\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\n\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\n\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\n\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\n\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.","status":"published","published":"2024-03-06T06:45:26Z","modified":"2026-05-11T19:30:04Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T19:05:02.705427Z"}],"ghsa":[{"id":"GHSA-6j3q-64jm-q33g","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: fix setting of...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: fix setting of fpc register\n\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\n\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\n\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\n\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\n\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\n\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.","status":"published","published":"2024-03-06T09:30:28Z","modified":"2024-11-07T21:32:40Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T14:58:45.881488Z"}],"nvd":[{"id":"CVE-2023-52597","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: fix setting of fpc register\n\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\n\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\n\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\n\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\n\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\n\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.","status":"published","published":"2024-03-06T07:15:09.827Z","modified":"2026-06-17T06:43:06.93Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium","assessor":"secondary"}],"updated_at":"2026-11-02T14:09:10.192572Z"}],"osv":[{"id":"BELL-CVE-2023-52597","status":"published","published":"2024-03-07T05:56:42.188294Z","modified":"2026-01-26T09:40:32.786338Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:28:18.192656Z"},{"id":"CVE-2023-52597","title":"KVM: s390: fix setting of fpc register","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: fix setting of fpc register\n\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\n\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\n\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\n\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\n\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\n\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.","status":"published","published":"2024-03-06T06:45:26.608Z","modified":"2026-10-29T11:42:20.64851479Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:44:35.245372Z"},{"id":"DEBIAN-CVE-2023-52597","description":"In the Linux kernel, the following vulnerability has been resolved:  KVM: s390: fix setting of fpc register  kvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control (fpc) register of a guest cpu. The new value is tested for validity by temporarily loading it into the fpc register.  This may lead to corruption of the fpc register of the host process: if an interrupt happens while the value is temporarily loaded into the fpc register, and within interrupt context floating point or vector registers are used, the current fp/vx registers are saved with save_fpu_regs() assuming they belong to user space and will be loaded into fp/vx registers when returning to user space.  test_fp_ctl() restores the original user space / host process fpc register value, however it will be discarded, when returning to user space.  In result the host process will incorrectly continue to run with the value that was supposed to be used for a guest cpu.  Fix this by simply removing the test. There is another test right before the SIE context is entered which will handles invalid values.  This results in a change of behaviour: invalid values will now be accepted instead of that the ioctl fails with -EINVAL. This seems to be acceptable, given that this interface is most likely not used anymore, and this is in addition the same behaviour implemented with the memory mapped interface (replace invalid values with zero) - see sync_regs() in kvm-s390.c.","status":"published","published":"2024-03-06T07:15:09.827Z","modified":"2026-10-26T18:02:43.177630643Z","cvss":[{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:45:40.586408Z"},{"id":"OESA-2024-1482","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: hda: intel-sdw-acpi: harden detection of controller\r\n\r\nThe existing code currently sets a pointer to an ACPI handle before\nchecking that it\u0026apos;s actually a SoundWire controller. This can lead to\nissues where the graph walk continues and eventually fails, but the\npointer was set already.\r\n\r\nThis patch changes the logic so that the information provided to\nthe caller is set when a controller is found.(CVE-2021-46926)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix another memory leak in error handling paths\r\n\r\nMemory allocated by \u0026apos;vmbus_alloc_ring()\u0026apos; at the beginning of the probe\nfunction is never freed in the error handling path.\r\n\r\nAdd the missing \u0026apos;vmbus_free_ring()\u0026apos; call.\r\n\r\nNote that it is already freed in the .remove function.(CVE-2021-47070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nasix: fix uninit-value in asix_mdio_read()\r\n\r\nasix_read_cmd() may read less than sizeof(smsr) bytes and in this case\nsmsr will be uninitialized.\r\n\r\nFail log:\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\nBUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\n asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nEDAC/thunderx: Fix possible out-of-bounds string access\r\n\r\nEnabling -Wstringop-overflow globally exposes a warning for a common bug\nin the usage of strncat():\r\n\r\n  drivers/edac/thunderx_edac.c: In function \u0026apos;thunderx_ocx_com_threaded_isr\u0026apos;:\n  drivers/edac/thunderx_edac.c:1136:17: error: \u0026apos;strncat\u0026apos; specified bound 1024 equals destination size [-Werror=stringop-overflow=]\n   1136 |                 strncat(msg, other, OCX_MESSAGE_SIZE);\n        |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n   ...\n   1145 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\n   ...\n   1150 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\r\n\r\n   ...\r\n\r\nApparently the author of this driver expected strncat() to behave the\nway that strlcat() does, which uses the size of the destination buffer\nas its third argument rather than the length of the source buffer. The\nresult is that there is no check on the size of the allocated buffer.\r\n\r\nChange it to strlcat().\r\n\r\n  [ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nInput: powermate - fix use-after-free in powermate_config_complete\r\n\r\nsyzbot has found a use-after-free bug [1] in the powermate driver. This\nhappens when the device is disconnected, which leads to a memory free from\nthe powermate_device struct.  When an asynchronous control message\ncompletes after the kfree and its callback is invoked, the lock does not\nexist anymore and hence the bug.\r\n\r\nUse usb_kill_urb() on pm-\u0026gt;config to cancel any in-progress requests upon\ndevice disconnection.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command\r\n\r\nTags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed\nwhen we receive the response.(CVE-2023-52500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: assert requested protocol is valid\r\n\r\nThe protocol is used in a bit mask to determine if the protocol is\nsupported. Assert the provided protocol is less than the maximum\ndefined so it doesn\u0026apos;t potentially perform a shift-out-of-bounds and\nprovide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nieee802154: ca8210: Fix a potential UAF in ca8210_probe\r\n\r\nIf of_clk_add_provider() fails in ca8210_register_ext_clock(),\nit calls clk_unregister() to release priv-\u0026gt;clk and returns an\nerror. However, the caller ca8210_probe() then calls ca8210_remove(),\nwhere priv-\u0026gt;clk is freed again in ca8210_unregister_ext_clock(). In\nthis case, a use-after-free may happen in the second time we call\nclk_unregister().\r\n\r\nFix this by removing the first clk_unregister(). Also, priv-\u0026gt;clk could\nbe an error code on failure of clk_register_fixed_rate(). Use\nIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/srp: Do not call scsi_done() from srp_abort()\r\n\r\nAfter scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler\ncallback, it performs one of the following actions:\n* Call scsi_queue_insert().\n* Call scsi_finish_command().\n* Call scsi_eh_scmd_add().\nHence, SCSI abort handlers must not call scsi_done(). Otherwise all\nthe above actions would trigger a use-after-free. Hence remove the\nscsi_done() call from srp_abort(). Keep the srp_free_req() call\nbefore returning SUCCESS because we may not see the command again if\nSUCCESS is returned.(CVE-2023-52515)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix possible store tearing in neigh_periodic_work()\r\n\r\nWhile looking at a related syzbot report involving neigh_periodic_work(),\nI found that I forgot to add an annotation when deleting an\nRCU protected item from a list.\r\n\r\nReaders use rcu_deference(*np), we need to use either\nrcu_assign_pointer() or WRITE_ONCE() on writer side\nto prevent store tearing.\r\n\r\nI use rcu_assign_pointer() to have lockdep support,\nthis was the choice made in neigh_flush_dev().(CVE-2023-52522)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet\r\n\r\nOnly skip the code path trying to access the rfc1042 headers when the\nbuffer is too small, so the driver can still process packets without\nrfc1042 headers.(CVE-2023-52525)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: fix potential key use-after-free\r\n\r\nWhen ieee80211_key_link() is called by ieee80211_gtk_rekey_add()\nbut returns 0 due to KRACK protection (identical key reinstall),\nieee80211_gtk_rekey_add() will still return a pointer into the\nkey, in a potential use-after-free. This normally doesn\u0026apos;t happen\nsince it\u0026apos;s only called by iwlwifi in case of WoWLAN rekey offload\nwhich has its own KRACK protection, but still better to fix, do\nthat by returning an error code and converting that to success on\nthe cfg80211 boundary only, leaving the error for bad callers of\nieee80211_gtk_rekey_add().(CVE-2023-52530)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions()\r\n\r\nWhen CONFIG_DAMON_VADDR_KUNIT_TEST=y and making CONFIG_DEBUG_KMEMLEAK=y\nand CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN=y, the below memory leak is detected.\r\n\r\nSince commit 9f86d624292c (\u0026quot;mm/damon/vaddr-test: remove unnecessary\nvariables\u0026quot;), the damon_destroy_ctx() is removed, but still call\ndamon_new_target() and damon_new_region(), the damon_region which is\nallocated by kmem_cache_alloc() in damon_new_region() and the damon_target\nwhich is allocated by kmalloc in damon_new_target() are not freed.  And\nthe damon_region which is allocated in damon_new_region() in\ndamon_set_regions() is also not freed.\r\n\r\nSo use damon_destroy_target to free all the damon_regions and damon_target.\r\n\r\n    unreferenced object 0xffff888107c9a940 (size 64):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1069, jiffies 4294670592 (age 732.761s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 06 00 00 00 6b 6b 6b 6b  ............kkkk\n        60 c7 9c 07 81 88 ff ff f8 cb 9c 07 81 88 ff ff  `...............\n      backtrace:\n        [\u0026lt;ffffffff817e0167\u0026gt;] kmalloc_trace+0x27/0xa0\n        [\u0026lt;ffffffff819c11cf\u0026gt;] damon_new_target+0x3f/0x1b0\n        [\u0026lt;ffffffff819c7d55\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0x95/0x3e0\n        [\u0026lt;ffffffff819c82be\u0026gt;] damon_test_apply_three_regions1+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff8881079cc740 (size 56):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1069, jiffies 4294670592 (age 732.761s)\n      hex dump (first 32 bytes):\n        05 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00  ................\n        6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 6b 6b 6b 6b  kkkkkkkk....kkkk\n      backtrace:\n        [\u0026lt;ffffffff819bc492\u0026gt;] damon_new_region+0x22/0x1c0\n        [\u0026lt;ffffffff819c7d91\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0xd1/0x3e0\n        [\u0026lt;ffffffff819c82be\u0026gt;] damon_test_apply_three_regions1+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff888107c9ac40 (size 64):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1071, jiffies 4294670595 (age 732.843s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 06 00 00 00 6b 6b 6b 6b  ............kkkk\n        a0 cc 9c 07 81 88 ff ff 78 a1 76 07 81 88 ff ff  ........x.v.....\n      backtrace:\n        [\u0026lt;ffffffff817e0167\u0026gt;] kmalloc_trace+0x27/0xa0\n        [\u0026lt;ffffffff819c11cf\u0026gt;] damon_new_target+0x3f/0x1b0\n        [\u0026lt;ffffffff819c7d55\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0x95/0x3e0\n        [\u0026lt;ffffffff819c851e\u0026gt;] damon_test_apply_three_regions2+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff8881079ccc80 (size 56):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1071, jiffies 4294670595 (age 732.843s)\n      hex dump (first 32 bytes):\n        05 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00  ................\n        6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 6b 6b 6b 6b  kkkkkkkk....kkkk\n      backtrace:\n        [\u0026lt;ffffffff819bc492\u0026gt;] damon_new_region+0x22/0x1c0\n        [\u0026lt;ffffffff819c7d91\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0xd1/0x3e0\n        [\u0026lt;ffffffff819c851e\u0026gt;] damon_test_apply_three_regions2+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffff\n---truncated---(CVE-2023-52560)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\narm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved\r\n\r\nAdding a reserved memory region for the framebuffer memory\n(the splash memory region set up by the bootloader).\r\n\r\nIt fixes a kernel panic (arm-smmu: Unhandled context fault\nat this particular memory region) reported on DB845c running\nv5.10.y.(CVE-2023-52561)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential use after free in nilfs_gccache_submit_read_data()\r\n\r\nIn nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the\nreference count of bh when the call to nilfs_dat_translate() fails.  If\nthe reference count hits 0 and its owner page gets unlocked, bh may be\nfreed.  However, bh-\u0026gt;b_page is dereferenced to put the page after that,\nwhich may result in a use-after-free bug.  This patch moves the release\noperation after unlocking and putting the page.\r\n\r\nNOTE: The function in question is only called in GC, and in combination\nwith current userland tools, address translation using DAT does not occur\nin that function, so the code path that causes this issue will not be\nexecuted.  However, it is possible to run that code path by intentionally\nmodifying the userland GC library or by calling the GC ioctl directly.\r\n\r\n[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nx86/sgx: Resolves SECS reclaim vs. page fault for EAUG race\r\n\r\nThe SGX EPC reclaimer (ksgxd) may reclaim the SECS EPC page for an\nenclave and set secs.epc_page to NULL. The SECS page is used for EAUG\nand ELDU in the SGX page fault handler. However, the NULL check for\nsecs.epc_page is only done for ELDU, not EAUG before being used.\r\n\r\nFix this by doing the same NULL check and reloading of the SECS page as\nneeded for both EAUG and ELDU.\r\n\r\nThe SECS page holds global enclave metadata. It can only be reclaimed\nwhen there are no other enclave pages remaining. At that point,\nvirtually nothing can be done with the enclave until the SECS page is\npaged back in.\r\n\r\nAn enclave can not run nor generate page faults without a resident SECS\npage. But it is still possible for a #PF for a non-SECS page to race\nwith paging out the SECS page: when the last resident non-SECS page A\ntriggers a #PF in a non-resident page B, and then page A and the SECS\nboth are paged out before the #PF on B is handled.\r\n\r\nHitting this bug requires that race triggered with a #PF for EAUG.\nFollowing is a trace when it happens.\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nRIP: 0010:sgx_encl_eaug_page+0xc7/0x210\nCall Trace:\n ? __kmem_cache_alloc_node+0x16a/0x440\n ? xa_load+0x6e/0xa0\n sgx_vma_fault+0x119/0x230\n __do_fault+0x36/0x140\n do_fault+0x12f/0x400\n __handle_mm_fault+0x728/0x1110\n handle_mm_fault+0x105/0x310\n do_user_addr_fault+0x1ee/0x750\n ? __this_cpu_preempt_check+0x13/0x20\n exc_page_fault+0x76/0x180\n asm_exc_page_fault+0x27/0x30(CVE-2023-52568)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: rds: Fix possible NULL-pointer dereference\r\n\r\nIn rds_rdma_cm_event_handler_cmn() check, if conn pointer exists\nbefore dereferencing it as rdma_set_service_type() argument\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2023-52573)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndccp: fix dccp_v4_err()/dccp_v6_err() again\r\n\r\ndh-\u0026gt;dccph_x is the 9th byte (offset 8) in \u0026quot;struct dccp_hdr\u0026quot;,\nnot in the \u0026quot;byte 7\u0026quot; as Jann claimed.\r\n\r\nWe need to make sure the ICMP messages are big enough,\nusing more standard ways (no more assumptions).\r\n\r\nsyzbot reported:\nBUG: KMSAN: uninit-value in pskb_may_pull_reason include/linux/skbuff.h:2667 [inline]\nBUG: KMSAN: uninit-value in pskb_may_pull include/linux/skbuff.h:2681 [inline]\nBUG: KMSAN: uninit-value in dccp_v6_err+0x426/0x1aa0 net/dccp/ipv6.c:94\npskb_may_pull_reason include/linux/skbuff.h:2667 [inline]\npskb_may_pull include/linux/skbuff.h:2681 [inline]\ndccp_v6_err+0x426/0x1aa0 net/dccp/ipv6.c:94\nicmpv6_notify+0x4c7/0x880 net/ipv6/icmp.c:867\nicmpv6_rcv+0x19d5/0x30d0\nip6_protocol_deliver_rcu+0xda6/0x2a60 net/ipv6/ip6_input.c:438\nip6_input_finish net/ipv6/ip6_input.c:483 [inline]\nNF_HOOK include/linux/netfilter.h:304 [inline]\nip6_input+0x15d/0x430 net/ipv6/ip6_input.c:492\nip6_mc_input+0xa7e/0xc80 net/ipv6/ip6_input.c:586\ndst_input include/net/dst.h:468 [inline]\nip6_rcv_finish+0x5db/0x870 net/ipv6/ip6_input.c:79\nNF_HOOK include/linux/netfilter.h:304 [inline]\nipv6_rcv+0xda/0x390 net/ipv6/ip6_input.c:310\n__netif_receive_skb_one_core net/core/dev.c:5523 [inline]\n__netif_receive_skb+0x1a6/0x5a0 net/core/dev.c:5637\nnetif_receive_skb_internal net/core/dev.c:5723 [inline]\nnetif_receive_skb+0x58/0x660 net/core/dev.c:5782\ntun_rx_batched+0x83b/0x920\ntun_get_user+0x564c/0x6940 drivers/net/tun.c:2002\ntun_chr_write_iter+0x3af/0x5d0 drivers/net/tun.c:2048\ncall_write_iter include/linux/fs.h:1985 [inline]\nnew_sync_write fs/read_write.c:491 [inline]\nvfs_write+0x8ef/0x15c0 fs/read_write.c:584\nksys_write+0x20f/0x4c0 fs/read_write.c:637\n__do_sys_write fs/read_write.c:649 [inline]\n__se_sys_write fs/read_write.c:646 [inline]\n__x64_sys_write+0x93/0xd0 fs/read_write.c:646\ndo_syscall_x64 arch/x86/entry/common.c:50 [inline]\ndo_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80\nentry_SYSCALL_64_after_hwframe+0x63/0xcd\r\n\r\nUninit was created at:\nslab_post_alloc_hook+0x12f/0xb70 mm/slab.h:767\nslab_alloc_node mm/slub.c:3478 [inline]\nkmem_cache_alloc_node+0x577/0xa80 mm/slub.c:3523\nkmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:559\n__alloc_skb+0x318/0x740 net/core/skbuff.c:650\nalloc_skb include/linux/skbuff.h:1286 [inline]\nalloc_skb_with_frags+0xc8/0xbd0 net/core/skbuff.c:6313\nsock_alloc_send_pskb+0xa80/0xbf0 net/core/sock.c:2795\ntun_alloc_skb drivers/net/tun.c:1531 [inline]\ntun_get_user+0x23cf/0x6940 drivers/net/tun.c:1846\ntun_chr_write_iter+0x3af/0x5d0 drivers/net/tun.c:2048\ncall_write_iter include/linux/fs.h:1985 [inline]\nnew_sync_write fs/read_write.c:491 [inline]\nvfs_write+0x8ef/0x15c0 fs/read_write.c:584\nksys_write+0x20f/0x4c0 fs/read_write.c:637\n__do_sys_write fs/read_write.c:649 [inline]\n__se_sys_write fs/read_write.c:646 [inline]\n__x64_sys_write+0x93/0xd0 fs/read_write.c:646\ndo_syscall_x64 arch/x86/entry/common.c:50 [inline]\ndo_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80\nentry_SYSCALL_64_after_hwframe+0x63/0xcd\r\n\r\nCPU: 0 PID: 4995 Comm: syz-executor153 Not tainted 6.6.0-rc1-syzkaller-00014-ga747acc0b752 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023(CVE-2023-52577)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: use DEV_STATS_INC()\r\n\r\nsyzbot/KCSAN reported data-races in br_handle_frame_finish() [1]\nThis function can run from multiple cpus without mutual exclusion.\r\n\r\nAdopt SMP safe DEV_STATS_INC() to update dev-\u0026gt;stats fields.\r\n\r\nHandles updates to dev-\u0026gt;stats.tx_dropped while we are at it.\r\n\r\n[1]\nBUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\nrun_ksoftirqd+0x17/0x20 kernel/softirq.c:921\nsmpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\ndo_softirq+0x5e/0x90 kernel/softirq.c:454\n__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381\n__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210\nspin_unlock_bh include/linux/spinlock.h:396 [inline]\nbatadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356\nbatadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560\nprocess_one_work kernel/workqueue.c:2630 [inline]\nprocess_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703\nworker_thread+0x525/0x730 kernel/workqueue.c:2784\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nvalue changed: 0x00000000000d7190 -\u0026gt; 0x00000000000d7191\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nceph: fix deadlock or deadcode of misusing dget()\r\n\r\nThe lock order is incorrect between denty and its parent, we should\nalways make sure that the parent get the lock first.\r\n\r\nBut since this deadcode is never used and the parent dir will always\nbe set from the callers, let\u0026apos;s just remove it.(CVE-2023-52583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/ipoib: Fix mcast list locking\r\n\r\nReleasing the `priv-\u0026gt;lock` while iterating the `priv-\u0026gt;multicast_list` in\n`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to\nremove the items while in the middle of iteration. If the mcast is removed\nwhile the lock was dropped, the for loop spins forever resulting in a hard\nlockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):\r\n\r\n    Task A (kworker/u72:2 below)       | Task B (kworker/u72:0 below)\n    -----------------------------------+-----------------------------------\n    ipoib_mcast_join_task(work)        | ipoib_ib_dev_flush_light(work)\n      spin_lock_irq(\u0026amp;priv-\u0026gt;lock)       | __ipoib_ib_dev_flush(priv, ...)\n      list_for_each_entry(mcast,       | ipoib_mcast_dev_flush(dev = priv-\u0026gt;dev)\n          \u0026amp;priv-\u0026gt;multicast_list, list) |\n        ipoib_mcast_join(dev, mcast)   |\n          spin_unlock_irq(\u0026amp;priv-\u0026gt;lock) |\n                                       |   spin_lock_irqsave(\u0026amp;priv-\u0026gt;lock, flags)\n                                       |   list_for_each_entry_safe(mcast, tmcast,\n                                       |                  \u0026amp;priv-\u0026gt;multicast_list, list)\n                                       |     list_del(\u0026amp;mcast-\u0026gt;list);\n                                       |     list_add_tail(\u0026amp;mcast-\u0026gt;list, \u0026amp;remove_list)\n                                       |   spin_unlock_irqrestore(\u0026amp;priv-\u0026gt;lock, flags)\n          spin_lock_irq(\u0026amp;priv-\u0026gt;lock)   |\n                                       |   ipoib_mcast_remove_list(\u0026amp;remove_list)\n   (Here, `mcast` is no longer on the  |     list_for_each_entry_safe(mcast, tmcast,\n    `priv-\u0026gt;multicast_list` and we keep |                            remove_list, list)\n    spinning on the `remove_list` of   |  \u0026gt;\u0026gt;\u0026gt;  wait_for_completion(\u0026amp;mcast-\u0026gt;done)\n    the other thread which is blocked  |\n    and the list is still valid on     |\n    it\u0026apos;s stack.)\r\n\r\nFix this by keeping the lock held and changing to GFP_ATOMIC to prevent\neventual sleeps.\nUnfortunately we could not reproduce the lockup and confirm this fix but\nbased on the code review I think this fix should address such lockups.\r\n\r\ncrash\u0026gt; bc 31\nPID: 747      TASK: ff1c6a1a007e8000  CPU: 31   COMMAND: \u0026quot;kworker/u72:2\u0026quot;\n--\n    [exception RIP: ipoib_mcast_join_task+0x1b1]\n    RIP: ffffffffc0944ac1  RSP: ff646f199a8c7e00  RFLAGS: 00000002\n    RAX: 0000000000000000  RBX: ff1c6a1a04dc82f8  RCX: 0000000000000000\n                                  work (\u0026amp;priv-\u0026gt;mcast_task{,.work})\n    RDX: ff1c6a192d60ac68  RSI: 0000000000000286  RDI: ff1c6a1a04dc8000\n           \u0026amp;mcast-\u0026gt;list\n    RBP: ff646f199a8c7e90   R8: ff1c699980019420   R9: ff1c6a1920c9a000\n    R10: ff646f199a8c7e00  R11: ff1c6a191a7d9800  R12: ff1c6a192d60ac00\n                                                         mcast\n    R13: ff1c6a1d82200000  R14: ff1c6a1a04dc8000  R15: ff1c6a1a04dc82d8\n           dev                    priv (\u0026amp;priv-\u0026gt;lock)     \u0026amp;priv-\u0026gt;multicast_list (aka head)\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n--- \u0026lt;NMI exception stack\u0026gt; ---\n #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]\n #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967\r\n\r\ncrash\u0026gt; rx ff646f199a8c7e68\nff646f199a8c7e68:  ff1c6a1a04dc82f8 \u0026lt;\u0026lt;\u0026lt; work = \u0026amp;priv-\u0026gt;mcast_task.work\r\n\r\ncrash\u0026gt; list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000\n(empty)\r\n\r\ncrash\u0026gt; ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000\n  mcast_task.work.func = 0xffffffffc0944910 \u0026lt;ipoib_mcast_join_task\u0026gt;,\n  mcast_mutex.owner.counter = 0xff1c69998efec000\r\n\r\ncrash\u0026gt; b 8\nPID: 8        TASK: ff1c69998efec000  CPU: 33   COMMAND: \u0026quot;kworker/u72:0\u0026quot;\n--\n #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646\n #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]\n #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]\n #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]\n #7 [ff\n---truncated---(CVE-2023-52587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()\r\n\r\nFix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug\noccurs when txs-\u0026gt;cnt, data from a URB provided by a USB device, is\nbigger than the size of the array txs-\u0026gt;txstatus, which is\nHTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug\nhandling code after the check. Make the function return if that is the\ncase.\r\n\r\nFound by a modified version of syzkaller.\r\n\r\nUBSAN: array-index-out-of-bounds in htc_drv_txrx.c\nindex 13 is out of range for type \u0026apos;__wmi_event_txstatus [12]\u0026apos;\nCall Trace:\n ath9k_htc_txstatus\n ath9k_wmi_event_tasklet\n tasklet_action_common\n __do_softirq\n irq_exit_rxu\n sysvec_apic_timer_interrupt(CVE-2023-52594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rt2x00: restart beacon queue when hardware reset\r\n\r\nWhen a hardware reset is triggered, all registers are reset, so all\nqueues are forced to stop in hardware interface. However, mac80211\nwill not automatically stop the queue. If we don\u0026apos;t manually stop the\nbeacon queue, the queue will be deadlocked and unable to start again.\nThis patch fixes the issue where Apple devices cannot connect to the\nAP after calling ieee80211_restart_hw().(CVE-2023-52595)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: s390: fix setting of fpc register\r\n\r\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\r\n\r\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\r\n\r\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\r\n\r\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/ptrace: handle setting of fpc register correctly\r\n\r\nIf the content of the floating point control (fpc) register of a traced\nprocess is modified with the ptrace interface the new value is tested for\nvalidity by temporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the tracing process:\nif an interrupt happens while the value is temporarily loaded into the\nfpc register, and within interrupt context floating point or vector\nregisters are used, the current fp/vx registers are saved with\nsave_fpu_regs() assuming they belong to user space and will be loaded into\nfp/vx registers when returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space fpc register value, however\nit will be discarded, when returning to user space.\r\n\r\nIn result the tracer will incorrectly continue to run with the value that\nwas supposed to be used for the traced process.\r\n\r\nFix this by saving fpu register contents with save_fpu_regs() before using\ntest_fp_ctl().(CVE-2023-52598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: avoid online resizing failures due to oversized flex bg\r\n\r\nWhen we online resize an ext4 filesystem with a oversized flexbg_size,\r\n\r\n     mkfs.ext4 -F -G 67108864 $dev -b 4096 100M\n     mount $dev $dir\n     resize2fs $dev 16G\r\n\r\nthe following WARN_ON is triggered:\n==================================================================\nWARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550\nModules linked in: sg(E)\nCPU: 0 PID: 427 Comm: resize2fs Tainted: G  E  6.6.0-rc5+ #314\nRIP: 0010:__alloc_pages+0x411/0x550\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __kmalloc_large_node+0xa2/0x200\n __kmalloc+0x16e/0x290\n ext4_resize_fs+0x481/0xd80\n __ext4_ioctl+0x1616/0x1d90\n ext4_ioctl+0x12/0x20\n __x64_sys_ioctl+0xf0/0x150\n do_syscall_64+0x3b/0x90\n==================================================================\r\n\r\nThis is because flexbg_size is too large and the size of the new_group_data\narray to be allocated exceeds MAX_ORDER. Currently, the minimum value of\nMAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding\nmaximum number of groups that can be allocated is:\r\n\r\n (PAGE_SIZE \u0026lt;\u0026lt; MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845\r\n\r\nAnd the value that is down-aligned to the power of 2 is 16384. Therefore,\nthis value is defined as MAX_RESIZE_BG, and the number of groups added\neach time does not exceed this value during resizing, and is added multiple\ntimes to complete the online resizing. The difference is that the metadata\nin a flex_bg may be more dispersed.(CVE-2023-52622)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: regenerate buddy after block freeing failed if under fc replay\r\n\r\nThis mostly reverts commit 6bd97bf273bd (\u0026quot;ext4: remove redundant\nmb_regenerate_buddy()\u0026quot;) and reintroduces mb_regenerate_buddy(). Based on\ncode in mb_free_blocks(), fast commit replay can end up marking as free\nblocks that are already marked as such. This causes corruption of the\nbuddy bitmap so we need to regenerate it in that case.(CVE-2024-26601)","status":"published","published":"2024-04-19T11:06:55Z","modified":"2026-08-18T01:17:17.133820371Z","cvss":[{"version":"3.1","score":6.7,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","level":"medium"}],"updated_at":"2026-11-02T15:52:41.095407Z"},{"id":"OESA-2024-1483","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: img-scb: fix reference leak when pm_runtime_get_sync fails\r\n\r\nThe PM reference count is not expected to be incremented on\nreturn in functions img_i2c_xfer and img_i2c_init.\r\n\r\nHowever, pm_runtime_get_sync will increment the PM reference\ncount even failed. Forgetting to putting operation will result\nin a reference leak here.\r\n\r\nReplace it with pm_runtime_resume_and_get to keep usage\ncounter balanced.(CVE-2020-36783)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkyber: fix out of bounds access when preempted\r\n\r\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u0026gt;bio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \u0026quot;works\u0026quot; accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx\u0026apos;s than the first one (i.e., if\nctx-\u0026gt;index_hw[hctx-\u0026gt;type] \u0026gt; hctx-\u0026gt;nr_ctx).\r\n\r\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\r\n\r\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type \u0026apos;long unsigned int [128]\u0026apos;\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\r\n\r\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u0026gt;bio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.(CVE-2021-46984)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbus: qcom: Put child node before return\r\n\r\nPut child node before return to fix potential reference count leak.\nGenerally, the reference count of child is incremented and decremented\nautomatically in the macro for_each_available_child_of_node() and should\nbe decremented manually if the loop is broken in loop body.(CVE-2021-47054)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init\r\n\r\nADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()\nbefore calling adf_iov_putmsg()-\u0026gt;mutex_lock(vf2pf_lock), however the\nvf2pf_lock is initialized in adf_dev_init(), which can fail and when it\nfail, the vf2pf_lock is either not initialized or destroyed, a subsequent\nuse of vf2pf_lock will cause issue.\nTo fix this issue, only set this flag if adf_dev_init() returns 0.\r\n\r\n[    7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0\n[    7.180345] Call Trace:\n[    7.182576]  mutex_lock+0xc9/0xd0\n[    7.183257]  adf_iov_putmsg+0x118/0x1a0 [intel_qat]\n[    7.183541]  adf_vf2pf_shutdown+0x4d/0x7b [intel_qat]\n[    7.183834]  adf_dev_shutdown+0x172/0x2b0 [intel_qat]\n[    7.184127]  adf_probe+0x5e9/0x600 [qat_dh895xccvf](CVE-2021-47056)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Stop looking for coalesced MMIO zones if the bus is destroyed\r\n\r\nAbort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()\nfails to allocate memory for the new instance of the bus.  If it can\u0026apos;t\ninstantiate a new bus, unregister_dev() destroys all devices _except_ the\ntarget device.   But, it doesn\u0026apos;t tell the caller that it obliterated the\nbus and invoked the destructor for all devices that were on the bus.  In\nthe coalesced MMIO case, this can result in a deleted list entry\ndereference due to attempting to continue iterating on coalesced_zones\nafter future entries (in the walk) have been deleted.\r\n\r\nOpportunistically add curly braces to the for-loop, which encompasses\nmany lines but sneaks by without braces due to the guts being a single\nif statement.(CVE-2021-47060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Destroy I/O bus devices on unregister failure _after_ sync\u0026apos;ing SRCU\r\n\r\nIf allocating a new instance of an I/O bus fails when unregistering a\ndevice, wait to destroy the device until after all readers are guaranteed\nto see the new null bus.  Destroying devices before the bus is nullified\ncould lead to use-after-free since readers expect the devices on their\nreference of the bus to remain valid.(CVE-2021-47061)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: bridge/panel: Cleanup connector on bridge detach\r\n\r\nIf we don\u0026apos;t call drm_connector_cleanup() manually in\npanel_bridge_detach(), the connector will be cleaned up with the other\nDRM objects in the call to drm_mode_config_cleanup(). However, since our\ndrm_connector is devm-allocated, by the time drm_mode_config_cleanup()\nwill be called, our connector will be long gone. Therefore, the\nconnector must be cleaned up when the bridge is detached to avoid\nuse-after-free conditions.\r\n\r\nv2: Cleanup connector only if it was created\r\n\r\nv3: Add FIXME\r\n\r\nv4: (Use connector-\u0026gt;dev) directly in if() block(CVE-2021-47063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix a memory leak in error handling paths\r\n\r\nIf \u0026apos;vmbus_establish_gpadl()\u0026apos; fails, the (recv|send)_gpadl will not be\nupdated and \u0026apos;hv_uio_cleanup()\u0026apos; in the error handling path will not be\nable to free the corresponding buffer.\r\n\r\nIn such a case, we need to free the buffer explicitly.(CVE-2021-47071)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme-loop: fix memory leak in nvme_loop_create_ctrl()\r\n\r\nWhen creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()\nfails, the loop ctrl should be freed before jumping to the \u0026quot;out\u0026quot; label.(CVE-2021-47074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qedf: Add pointer checks in qedf_update_link_speed()\r\n\r\nThe following trace was observed:\r\n\r\n [   14.042059] Call Trace:\n [   14.042061]  \u0026lt;IRQ\u0026gt;\n [   14.042068]  qedf_link_update+0x144/0x1f0 [qedf]\n [   14.042117]  qed_link_update+0x5c/0x80 [qed]\n [   14.042135]  qed_mcp_handle_link_change+0x2d2/0x410 [qed]\n [   14.042155]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042170]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042186]  ? qed_rd+0x13/0x40 [qed]\n [   14.042205]  qed_mcp_handle_events+0x437/0x690 [qed]\n [   14.042221]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042239]  qed_int_sp_dpc+0x3a6/0x3e0 [qed]\n [   14.042245]  tasklet_action_common.isra.14+0x5a/0x100\n [   14.042250]  __do_softirq+0xe4/0x2f8\n [   14.042253]  irq_exit+0xf7/0x100\n [   14.042255]  do_IRQ+0x7f/0xd0\n [   14.042257]  common_interrupt+0xf/0xf\n [   14.042259]  \u0026lt;/IRQ\u0026gt;\r\n\r\nAPI qedf_link_update() is getting called from QED but by that time\nshost_data is not initialised. This results in a NULL pointer dereference\nwhen we try to dereference shost_data while updating supported_speeds.\r\n\r\nAdd a NULL pointer check before dereferencing shost_data.(CVE-2021-47077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/rxe: Clear all QP fields if creation failed\r\n\r\nrxe_qp_do_cleanup() relies on valid pointer values in QP for the properly\ncreated ones, but in case rxe_qp_from_init() failed it was filled with\ngarbage and caused tot the following error.\r\n\r\n  refcount_t: underflow; use-after-free.\n  WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28\n  Modules linked in:\n  CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0\n  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\n  RIP: 0010:refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28\n  Code: e9 db fe ff ff 48 89 df e8 2c c2 ea fd e9 8a fe ff ff e8 72 6a a7 fd 48 c7 c7 e0 b2 c1 89 c6 05 dc 3a e6 09 01 e8 ee 74 fb 04 \u0026lt;0f\u0026gt; 0b e9 af fe ff ff 0f 1f 84 00 00 00 00 00 41 56 41 55 41 54 55\n  RSP: 0018:ffffc900097ceba8 EFLAGS: 00010286\n  RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000\n  RDX: 0000000000040000 RSI: ffffffff815bb075 RDI: fffff520012f9d67\n  RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000\n  R10: ffffffff815b4eae R11: 0000000000000000 R12: ffff8880322a4800\n  R13: ffff8880322a4940 R14: ffff888033044e00 R15: 0000000000000000\n  FS:  00007f6eb2be3700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fdbe5d41000 CR3: 000000001d181000 CR4: 00000000001506e0\n  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n  Call Trace:\n   __refcount_sub_and_test include/linux/refcount.h:283 [inline]\n   __refcount_dec_and_test include/linux/refcount.h:315 [inline]\n   refcount_dec_and_test include/linux/refcount.h:333 [inline]\n   kref_put include/linux/kref.h:64 [inline]\n   rxe_qp_do_cleanup+0x96f/0xaf0 drivers/infiniband/sw/rxe/rxe_qp.c:805\n   execute_in_process_context+0x37/0x150 kernel/workqueue.c:3327\n   rxe_elem_release+0x9f/0x180 drivers/infiniband/sw/rxe/rxe_pool.c:391\n   kref_put include/linux/kref.h:65 [inline]\n   rxe_create_qp+0x2cd/0x310 drivers/infiniband/sw/rxe/rxe_verbs.c:425\n   _ib_create_qp drivers/infiniband/core/core_priv.h:331 [inline]\n   ib_create_named_qp+0x2ad/0x1370 drivers/infiniband/core/verbs.c:1231\n   ib_create_qp include/rdma/ib_verbs.h:3644 [inline]\n   create_mad_qp+0x177/0x2d0 drivers/infiniband/core/mad.c:2920\n   ib_mad_port_open drivers/infiniband/core/mad.c:3001 [inline]\n   ib_mad_init_device+0xd6f/0x1400 drivers/infiniband/core/mad.c:3092\n   add_client_context+0x405/0x5e0 drivers/infiniband/core/device.c:717\n   enable_device_and_get+0x1cd/0x3b0 drivers/infiniband/core/device.c:1331\n   ib_register_device drivers/infiniband/core/device.c:1413 [inline]\n   ib_register_device+0x7c7/0xa50 drivers/infiniband/core/device.c:1365\n   rxe_register_device+0x3d5/0x4a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1147\n   rxe_add+0x12fe/0x16d0 drivers/infiniband/sw/rxe/rxe.c:247\n   rxe_net_add+0x8c/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:503\n   rxe_newlink drivers/infiniband/sw/rxe/rxe.c:269 [inline]\n   rxe_newlink+0xb7/0xe0 drivers/infiniband/sw/rxe/rxe.c:250\n   nldev_newlink+0x30e/0x550 drivers/infiniband/core/nldev.c:1555\n   rdma_nl_rcv_msg+0x36d/0x690 drivers/infiniband/core/netlink.c:195\n   rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n   rdma_nl_rcv+0x2ee/0x430 drivers/infiniband/core/netlink.c:259\n   netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]\n   netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338\n   netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927\n   sock_sendmsg_nosec net/socket.c:654 [inline]\n   sock_sendmsg+0xcf/0x120 net/socket.c:674\n   ____sys_sendmsg+0x6e8/0x810 net/socket.c:2350\n   ___sys_sendmsg+0xf3/0x170 net/socket.c:2404\n   __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433\n   do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47\n   entry_SYSCALL_64_after_hwframe+0\n---truncated---(CVE-2021-47078)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nasix: fix uninit-value in asix_mdio_read()\r\n\r\nasix_read_cmd() may read less than sizeof(smsr) bytes and in this case\nsmsr will be uninitialized.\r\n\r\nFail log:\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\nBUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\n asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/tls: Fix use-after-free after the TLS device goes down and up\r\n\r\nWhen a netdev with active TLS offload goes down, tls_device_down is\ncalled to stop the offload and tear down the TLS context. However, the\nsocket stays alive, and it still points to the TLS context, which is now\ndeallocated. If a netdev goes up, while the connection is still active,\nand the data flow resumes after a number of TCP retransmissions, it will\nlead to a use-after-free of the TLS context.\r\n\r\nThis commit addresses this bug by keeping the context alive until its\nnormal destruction, and implements the necessary fallbacks, so that the\nconnection can resume in software (non-offloaded) kTLS mode.\r\n\r\nOn the TX side tls_sw_fallback is used to encrypt all packets. The RX\nside already has all the necessary fallbacks, because receiving\nnon-decrypted packets is supported. The thing needed on the RX side is\nto block resync requests, which are normally produced after receiving\nnon-decrypted packets.\r\n\r\nThe necessary synchronization is implemented for a graceful teardown:\nfirst the fallbacks are deployed, then the driver resources are released\n(it used to be possible to have a tls_dev_resync after tls_dev_del).\r\n\r\nA new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback\nmode. It\u0026apos;s used to skip the RX resync logic completely, as it becomes\nuseless, and some objects may be released (for example, resync_async,\nwhich is allocated and freed by the driver).(CVE-2021-47131)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix a use-after-free\r\n\r\nlooks like we forget to set ttm-\u0026gt;sg to NULL.\nHit panic below\r\n\r\n[ 1235.844104] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7b4b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI\n[ 1235.989074] Call Trace:\n[ 1235.991751]  sg_free_table+0x17/0x20\n[ 1235.995667]  amdgpu_ttm_backend_unbind.cold+0x4d/0xf7 [amdgpu]\n[ 1236.002288]  amdgpu_ttm_backend_destroy+0x29/0x130 [amdgpu]\n[ 1236.008464]  ttm_tt_destroy+0x1e/0x30 [ttm]\n[ 1236.013066]  ttm_bo_cleanup_memtype_use+0x51/0xa0 [ttm]\n[ 1236.018783]  ttm_bo_release+0x262/0xa50 [ttm]\n[ 1236.023547]  ttm_bo_put+0x82/0xd0 [ttm]\n[ 1236.027766]  amdgpu_bo_unref+0x26/0x50 [amdgpu]\n[ 1236.032809]  amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0x7aa/0xd90 [amdgpu]\n[ 1236.040400]  kfd_ioctl_alloc_memory_of_gpu+0xe2/0x330 [amdgpu]\n[ 1236.046912]  kfd_ioctl+0x463/0x690 [amdgpu](CVE-2021-47142)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/smc: remove device from smcd_dev_list after failed device_add()\r\n\r\nIf the device_add() for a smcd_dev fails, there\u0026apos;s no cleanup step that\nrolls back the earlier list_add(). The device subsequently gets freed,\nand we end up with a corrupted list.\r\n\r\nAdd some error handling that removes the device from the list.(CVE-2021-47143)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/amdgpu: fix refcount leak\r\n\r\n[Why]\nthe gem object rfb-\u0026gt;base.obj[0] is get according to num_planes\nin amdgpufb_create, but is not put according to num_planes\r\n\r\n[How]\nput rfb-\u0026gt;base.obj[0] in amdgpu_fbdev_destroy according to num_planes(CVE-2021-47144)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: do not BUG_ON in link_to_fixup_dir\r\n\r\nWhile doing error injection testing I got the following panic\r\n\r\n  kernel BUG at fs/btrfs/tree-log.c:1862!\n  invalid opcode: 0000 [#1] SMP NOPTI\n  CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014\n  RIP: 0010:link_to_fixup_dir+0xd5/0xe0\n  RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216\n  RAX: fffffffffffffffb RBX: 00000000fffffffb RCX: ffff8f595287faf0\n  RDX: ffffb5800180fa37 RSI: ffff8f5954978800 RDI: 0000000000000000\n  RBP: ffff8f5953af9450 R08: 0000000000000019 R09: 0000000000000001\n  R10: 000151f408682970 R11: 0000000120021001 R12: ffff8f5954978800\n  R13: ffff8f595287faf0 R14: ffff8f5953c77dd0 R15: 0000000000000065\n  FS:  00007fc5284c8c40(0000) GS:ffff8f59bbd00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fc5287f47c0 CR3: 000000011275e002 CR4: 0000000000370ee0\n  Call Trace:\n   replay_one_buffer+0x409/0x470\n   ? btree_read_extent_buffer_pages+0xd0/0x110\n   walk_up_log_tree+0x157/0x1e0\n   walk_log_tree+0xa6/0x1d0\n   btrfs_recover_log_trees+0x1da/0x360\n   ? replay_one_extent+0x7b0/0x7b0\n   open_ctree+0x1486/0x1720\n   btrfs_mount_root.cold+0x12/0xea\n   ? __kmalloc_track_caller+0x12f/0x240\n   legacy_get_tree+0x24/0x40\n   vfs_get_tree+0x22/0xb0\n   vfs_kern_mount.part.0+0x71/0xb0\n   btrfs_mount+0x10d/0x380\n   ? vfs_parse_fs_string+0x4d/0x90\n   legacy_get_tree+0x24/0x40\n   vfs_get_tree+0x22/0xb0\n   path_mount+0x433/0xa10\n   __x64_sys_mount+0xe3/0x120\n   do_syscall_64+0x3d/0x80\n   entry_SYSCALL_64_after_hwframe+0x44/0xae\r\n\r\nWe can get -EIO or any number of legitimate errors from\nbtrfs_search_slot(), panicing here is not the appropriate response.  The\nerror path for this code handles errors properly, simply return the\nerror.(CVE-2021-47145)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmld: fix panic in mld_newpack()\r\n\r\nmld_newpack() doesn\u0026apos;t allow to allocate high order page,\nonly order-0 allocation is allowed.\nIf headroom size is too large, a kernel panic could occur in skb_put().\r\n\r\nTest commands:\n    ip netns del A\n    ip netns del B\n    ip netns add A\n    ip netns add B\n    ip link add veth0 type veth peer name veth1\n    ip link set veth0 netns A\n    ip link set veth1 netns B\r\n\r\n    ip netns exec A ip link set lo up\n    ip netns exec A ip link set veth0 up\n    ip netns exec A ip -6 a a 2001:db8:0::1/64 dev veth0\n    ip netns exec B ip link set lo up\n    ip netns exec B ip link set veth1 up\n    ip netns exec B ip -6 a a 2001:db8:0::2/64 dev veth1\n    for i in {1..99}\n    do\n        let A=$i-1\n        ip netns exec A ip link add ip6gre$i type ip6gre \\\n\tlocal 2001:db8:$A::1 remote 2001:db8:$A::2 encaplimit 100\n        ip netns exec A ip -6 a a 2001:db8:$i::1/64 dev ip6gre$i\n        ip netns exec A ip link set ip6gre$i up\r\n\r\n        ip netns exec B ip link add ip6gre$i type ip6gre \\\n\tlocal 2001:db8:$A::2 remote 2001:db8:$A::1 encaplimit 100\n        ip netns exec B ip -6 a a 2001:db8:$i::2/64 dev ip6gre$i\n        ip netns exec B ip link set ip6gre$i up\n    done\r\n\r\nSplat looks like:\nkernel BUG at net/core/skbuff.c:110!\ninvalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.12.0+ #891\nWorkqueue: ipv6_addrconf addrconf_dad_work\nRIP: 0010:skb_panic+0x15d/0x15f\nCode: 92 fe 4c 8b 4c 24 10 53 8b 4d 70 45 89 e0 48 c7 c7 00 ae 79 83\n41 57 41 56 41 55 48 8b 54 24 a6 26 f9 ff \u0026lt;0f\u0026gt; 0b 48 8b 6c 24 20 89\n34 24 e8 4a 4e 92 fe 8b 34 24 48 c7 c1 20\nRSP: 0018:ffff88810091f820 EFLAGS: 00010282\nRAX: 0000000000000089 RBX: ffff8881086e9000 RCX: 0000000000000000\nRDX: 0000000000000089 RSI: 0000000000000008 RDI: ffffed1020123efb\nRBP: ffff888005f6eac0 R08: ffffed1022fc0031 R09: ffffed1022fc0031\nR10: ffff888117e00187 R11: ffffed1022fc0030 R12: 0000000000000028\nR13: ffff888008284eb0 R14: 0000000000000ed8 R15: 0000000000000ec0\nFS:  0000000000000000(0000) GS:ffff888117c00000(0000)\nknlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8b801c5640 CR3: 0000000033c2c006 CR4: 00000000003706f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n ? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n ? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n skb_put.cold.104+0x22/0x22\n ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n ? rcu_read_lock_sched_held+0x91/0xc0\n mld_newpack+0x398/0x8f0\n ? ip6_mc_hdr.isra.26.constprop.46+0x600/0x600\n ? lock_contended+0xc40/0xc40\n add_grhead.isra.33+0x280/0x380\n add_grec+0x5ca/0xff0\n ? mld_sendpack+0xf40/0xf40\n ? lock_downgrade+0x690/0x690\n mld_send_initial_cr.part.34+0xb9/0x180\n ipv6_mc_dad_complete+0x15d/0x1b0\n addrconf_dad_completed+0x8d2/0xbb0\n ? lock_downgrade+0x690/0x690\n ? addrconf_rs_timer+0x660/0x660\n ? addrconf_dad_work+0x73c/0x10e0\n addrconf_dad_work+0x73c/0x10e0\r\n\r\nAllowing high order page allocation could fix this problem.(CVE-2021-47146)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: i801: Don\u0026apos;t generate an interrupt on bus reset\r\n\r\nNow that the i2c-i801 driver supports interrupts, setting the KILL bit\nin a attempt to recover from a timed out transaction triggers an\ninterrupt. Unfortunately, the interrupt handler (i801_isr) is not\nprepared for this situation and will try to process the interrupt as\nif it was signaling the end of a successful transaction. In the case\nof a block transaction, this can result in an out-of-range memory\naccess.\r\n\r\nThis condition was reproduced several times by syzbot:\nhttps://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e\nhttps://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e\nhttps://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e\nhttps://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb\nhttps://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a\nhttps://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79\r\n\r\nSo disable interrupts while trying to reset the bus. Interrupts will\nbe enabled again for the following transaction.(CVE-2021-47153)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: fix a crash if -\u0026gt;get_sset_count() fails\r\n\r\nIf ds-\u0026gt;ops-\u0026gt;get_sset_count() fails then it \u0026quot;count\u0026quot; is a negative error\ncode such as -EOPNOTSUPP.  Because \u0026quot;i\u0026quot; is an unsigned int, the negative\nerror code is type promoted to a very high value and the loop will\ncorrupt memory until the system crashes.\r\n\r\nFix this by checking for error codes and changing the type of \u0026quot;i\u0026quot; to\njust int.(CVE-2021-47159)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: mt7530: fix VLAN traffic leaks\r\n\r\nPCR_MATRIX field was set to all 1\u0026apos;s when VLAN filtering is enabled, but\nwas not reset when it is disabled, which may cause traffic leaks:\r\n\r\n\tip link add br0 type bridge vlan_filtering 1\n\tip link add br1 type bridge vlan_filtering 1\n\tip link set swp0 master br0\n\tip link set swp1 master br1\n\tip link set br0 type bridge vlan_filtering 0\n\tip link set br1 type bridge vlan_filtering 0\n\t# traffic in br0 and br1 will start leaking to each other\r\n\r\nAs port_bridge_{add,del} have set up PCR_MATRIX properly, remove the\nPCR_MATRIX write from mt7530_port_set_vlan_aware.(CVE-2021-47160)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: spi-fsl-dspi: Fix a resource leak in an error handling path\r\n\r\n\u0026apos;dspi_request_dma()\u0026apos; should be undone by a \u0026apos;dspi_release_dma()\u0026apos; call in the\nerror handling path of the probe function, as already done in the remove\nfunction(CVE-2021-47161)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: skb_linearize the head skb when reassembling msgs\r\n\r\nIt\u0026apos;s not a good idea to append the frag skb to a skb\u0026apos;s frag_list if\nthe frag_list already has skbs from elsewhere, such as this skb was\ncreated by pskb_copy() where the frag_list was cloned (all the skbs\nin it were skb_get\u0026apos;ed) and shared by multiple skbs.\r\n\r\nHowever, the new appended frag skb should have been only seen by the\ncurrent skb. Otherwise, it will cause use after free crashes as this\nappended frag skb are seen by multiple skbs but it only got skb_get\ncalled once.\r\n\r\nThe same thing happens with a skb updated by pskb_may_pull() with a\nskb_cloned skb. Li Shuang has reported quite a few crashes caused\nby this when doing testing over macvlan devices:\r\n\r\n  [] kernel BUG at net/core/skbuff.c:1970!\n  [] Call Trace:\n  []  skb_clone+0x4d/0xb0\n  []  macvlan_broadcast+0xd8/0x160 [macvlan]\n  []  macvlan_process_broadcast+0x148/0x150 [macvlan]\n  []  process_one_work+0x1a7/0x360\n  []  worker_thread+0x30/0x390\r\n\r\n  [] kernel BUG at mm/usercopy.c:102!\n  [] Call Trace:\n  []  __check_heap_object+0xd3/0x100\n  []  __check_object_size+0xff/0x16b\n  []  simple_copy_to_iter+0x1c/0x30\n  []  __skb_datagram_iter+0x7d/0x310\n  []  __skb_datagram_iter+0x2a5/0x310\n  []  skb_copy_datagram_iter+0x3b/0x90\n  []  tipc_recvmsg+0x14a/0x3a0 [tipc]\n  []  ____sys_recvmsg+0x91/0x150\n  []  ___sys_recvmsg+0x7b/0xc0\r\n\r\n  [] kernel BUG at mm/slub.c:305!\n  [] Call Trace:\n  []  \u0026lt;IRQ\u0026gt;\n  []  kmem_cache_free+0x3ff/0x400\n  []  __netif_receive_skb_core+0x12c/0xc40\n  []  ? kmem_cache_alloc+0x12e/0x270\n  []  netif_receive_skb_internal+0x3d/0xb0\n  []  ? get_rx_page_info+0x8e/0xa0 [be2net]\n  []  be_poll+0x6ef/0xd00 [be2net]\n  []  ? irq_exit+0x4f/0x100\n  []  net_rx_action+0x149/0x3b0\r\n\r\n  ...\r\n\r\nThis patch is to fix it by linearizing the head skb if it has frag_list\nset in tipc_buf_append(). Note that we choose to do this before calling\nskb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can\nnot just drop the frag_list either as the early time.(CVE-2021-47162)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: wait and exit until all work queues are done\r\n\r\nOn some host, a crash could be triggered simply by repeating these\ncommands several times:\r\n\r\n  # modprobe tipc\n  # tipc bearer enable media udp name UDP1 localip 127.0.0.1\n  # rmmod tipc\r\n\r\n  [] BUG: unable to handle kernel paging request at ffffffffc096bb00\n  [] Workqueue: events 0xffffffffc096bb00\n  [] Call Trace:\n  []  ? process_one_work+0x1a7/0x360\n  []  ? worker_thread+0x30/0x390\n  []  ? create_worker+0x1a0/0x1a0\n  []  ? kthread+0x116/0x130\n  []  ? kthread_flush_work_fn+0x10/0x10\n  []  ? ret_from_fork+0x35/0x40\r\n\r\nWhen removing the TIPC module, the UDP tunnel sock will be delayed to\nrelease in a work queue as sock_release() can\u0026apos;t be done in rtnl_lock().\nIf the work queue is schedule to run after the TIPC module is removed,\nkernel will crash as the work queue function cleanup_beareri() code no\nlonger exists when trying to invoke it.\r\n\r\nTo fix it, this patch introduce a member wq_count in tipc_net to track\nthe numbers of work queues in schedule, and  wait and exit until all\nwork queues are done in tipc_exit_net().(CVE-2021-47163)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFS: Fix an Oopsable condition in __nfs_pageio_add_request()\r\n\r\nEnsure that nfs_pageio_error_cleanup() resets the mirror array contents,\nso that the structure reflects the fact that it is now empty.\nAlso change the test in nfs_pageio_do_add_request() to be more robust by\nchecking whether or not the list is empty rather than relying on the\nvalue of pg_count.(CVE-2021-47167)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: usbfs: Don\u0026apos;t WARN about excessively large memory allocations\r\n\r\nSyzbot found that the kernel generates a WARNing if the user tries to\nsubmit a bulk transfer through usbfs with a buffer that is way too\nlarge.  This isn\u0026apos;t a bug in the kernel; it\u0026apos;s merely an invalid request\nfrom the user and the usbfs code does handle it correctly.\r\n\r\nIn theory the same thing can happen with async transfers, or with the\npacket descriptor table for isochronous transfers.\r\n\r\nTo prevent the MM subsystem from complaining about these bad\nallocation requests, add the __GFP_NOWARN flag to the kmalloc calls\nfor these buffers.(CVE-2021-47170)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: usb: fix memory leak in smsc75xx_bind\r\n\r\nSyzbot reported memory leak in smsc75xx_bind().\nThe problem was is non-freed memory in case of\nerrors after memory allocation.\r\n\r\nbacktrace:\n  [\u0026lt;ffffffff84245b62\u0026gt;] kmalloc include/linux/slab.h:556 [inline]\n  [\u0026lt;ffffffff84245b62\u0026gt;] kzalloc include/linux/slab.h:686 [inline]\n  [\u0026lt;ffffffff84245b62\u0026gt;] smsc75xx_bind+0x7a/0x334 drivers/net/usb/smsc75xx.c:1460\n  [\u0026lt;ffffffff82b5b2e6\u0026gt;] usbnet_probe+0x3b6/0xc30 drivers/net/usb/usbnet.c:1728(CVE-2021-47171)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmisc/uss720: fix memory leak in uss720_probe\r\n\r\nuss720_probe forgets to decrease the refcount of usbdev in uss720_probe.\nFix this by decreasing the refcount of usbdev by usb_put_dev.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888101113800 (size 2048):\n  comm \u0026quot;kworker/0:1\u0026quot;, pid 7, jiffies 4294956777 (age 28.870s)\n  hex dump (first 32 bytes):\n    ff ff ff ff 31 00 00 00 00 00 00 00 00 00 00 00  ....1...........\n    00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00  ................\n  backtrace:\n    [\u0026lt;ffffffff82b8e822\u0026gt;] kmalloc include/linux/slab.h:554 [inline]\n    [\u0026lt;ffffffff82b8e822\u0026gt;] kzalloc include/linux/slab.h:684 [inline]\n    [\u0026lt;ffffffff82b8e822\u0026gt;] usb_alloc_dev+0x32/0x450 drivers/usb/core/usb.c:582\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_port_connect drivers/usb/core/hub.c:5129 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_port_connect_change drivers/usb/core/hub.c:5363 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] port_event drivers/usb/core/hub.c:5509 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_event+0x1171/0x20c0 drivers/usb/core/hub.c:5591\n    [\u0026lt;ffffffff81259229\u0026gt;] process_one_work+0x2c9/0x600 kernel/workqueue.c:2275\n    [\u0026lt;ffffffff81259b19\u0026gt;] worker_thread+0x59/0x5d0 kernel/workqueue.c:2421\n    [\u0026lt;ffffffff81261228\u0026gt;] kthread+0x178/0x1b0 kernel/kthread.c:292\n    [\u0026lt;ffffffff8100227f\u0026gt;] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294(CVE-2021-47173)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFC: nci: fix memory leak in nci_allocate_device\r\n\r\nnfcmrvl_disconnect fails to free the hci_dev field in struct nci_dev.\nFix this by freeing hci_dev in nci_free_device.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888111ea6800 (size 1024):\n  comm \u0026quot;kworker/1:0\u0026quot;, pid 19, jiffies 4294942308 (age 13.580s)\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 60 fd 0c 81 88 ff ff  .........`......\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [\u0026lt;000000004bc25d43\u0026gt;] kmalloc include/linux/slab.h:552 [inline]\n    [\u0026lt;000000004bc25d43\u0026gt;] kzalloc include/linux/slab.h:682 [inline]\n    [\u0026lt;000000004bc25d43\u0026gt;] nci_hci_allocate+0x21/0xd0 net/nfc/nci/hci.c:784\n    [\u0026lt;00000000c59cff92\u0026gt;] nci_allocate_device net/nfc/nci/core.c:1170 [inline]\n    [\u0026lt;00000000c59cff92\u0026gt;] nci_allocate_device+0x10b/0x160 net/nfc/nci/core.c:1132\n    [\u0026lt;00000000006e0a8e\u0026gt;] nfcmrvl_nci_register_dev+0x10a/0x1c0 drivers/nfc/nfcmrvl/main.c:153\n    [\u0026lt;000000004da1b57e\u0026gt;] nfcmrvl_probe+0x223/0x290 drivers/nfc/nfcmrvl/usb.c:345\n    [\u0026lt;00000000d506aed9\u0026gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396\n    [\u0026lt;00000000bc632c92\u0026gt;] really_probe+0x159/0x4a0 drivers/base/dd.c:554\n    [\u0026lt;00000000f5009125\u0026gt;] driver_probe_device+0x84/0x100 drivers/base/dd.c:740\n    [\u0026lt;000000000ce658ca\u0026gt;] __device_attach_driver+0xee/0x110 drivers/base/dd.c:846\n    [\u0026lt;000000007067d05f\u0026gt;] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431\n    [\u0026lt;00000000f8e13372\u0026gt;] __device_attach+0x122/0x250 drivers/base/dd.c:914\n    [\u0026lt;000000009cf68860\u0026gt;] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491\n    [\u0026lt;00000000359c965a\u0026gt;] device_add+0x5be/0xc30 drivers/base/core.c:3109\n    [\u0026lt;00000000086e4bd3\u0026gt;] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164\n    [\u0026lt;00000000ca036872\u0026gt;] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238\n    [\u0026lt;00000000d40d36f6\u0026gt;] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293\n    [\u0026lt;00000000bc632c92\u0026gt;] really_probe+0x159/0x4a0 drivers/base/dd.c:554(CVE-2021-47180)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nEDAC/thunderx: Fix possible out-of-bounds string access\r\n\r\nEnabling -Wstringop-overflow globally exposes a warning for a common bug\nin the usage of strncat():\r\n\r\n  drivers/edac/thunderx_edac.c: In function \u0026apos;thunderx_ocx_com_threaded_isr\u0026apos;:\n  drivers/edac/thunderx_edac.c:1136:17: error: \u0026apos;strncat\u0026apos; specified bound 1024 equals destination size [-Werror=stringop-overflow=]\n   1136 |                 strncat(msg, other, OCX_MESSAGE_SIZE);\n        |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n   ...\n   1145 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\n   ...\n   1150 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\r\n\r\n   ...\r\n\r\nApparently the author of this driver expected strncat() to behave the\nway that strlcat() does, which uses the size of the destination buffer\nas its third argument rather than the length of the source buffer. The\nresult is that there is no check on the size of the allocated buffer.\r\n\r\nChange it to strlcat().\r\n\r\n  [ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nInput: powermate - fix use-after-free in powermate_config_complete\r\n\r\nsyzbot has found a use-after-free bug [1] in the powermate driver. This\nhappens when the device is disconnected, which leads to a memory free from\nthe powermate_device struct.  When an asynchronous control message\ncompletes after the kfree and its callback is invoked, the lock does not\nexist anymore and hence the bug.\r\n\r\nUse usb_kill_urb() on pm-\u0026gt;config to cancel any in-progress requests upon\ndevice disconnection.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command\r\n\r\nTags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed\nwhen we receive the response.(CVE-2023-52500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: assert requested protocol is valid\r\n\r\nThe protocol is used in a bit mask to determine if the protocol is\nsupported. Assert the provided protocol is less than the maximum\ndefined so it doesn\u0026apos;t potentially perform a shift-out-of-bounds and\nprovide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nieee802154: ca8210: Fix a potential UAF in ca8210_probe\r\n\r\nIf of_clk_add_provider() fails in ca8210_register_ext_clock(),\nit calls clk_unregister() to release priv-\u0026gt;clk and returns an\nerror. However, the caller ca8210_probe() then calls ca8210_remove(),\nwhere priv-\u0026gt;clk is freed again in ca8210_unregister_ext_clock(). In\nthis case, a use-after-free may happen in the second time we call\nclk_unregister().\r\n\r\nFix this by removing the first clk_unregister(). Also, priv-\u0026gt;clk could\nbe an error code on failure of clk_register_fixed_rate(). Use\nIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/srp: Do not call scsi_done() from srp_abort()\r\n\r\nAfter scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler\ncallback, it performs one of the following actions:\n* Call scsi_queue_insert().\n* Call scsi_finish_command().\n* Call scsi_eh_scmd_add().\nHence, SCSI abort handlers must not call scsi_done(). Otherwise all\nthe above actions would trigger a use-after-free. Hence remove the\nscsi_done() call from srp_abort(). Keep the srp_free_req() call\nbefore returning SUCCESS because we may not see the command again if\nSUCCESS is returned.(CVE-2023-52515)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix possible store tearing in neigh_periodic_work()\r\n\r\nWhile looking at a related syzbot report involving neigh_periodic_work(),\nI found that I forgot to add an annotation when deleting an\nRCU protected item from a list.\r\n\r\nReaders use rcu_deference(*np), we need to use either\nrcu_assign_pointer() or WRITE_ONCE() on writer side\nto prevent store tearing.\r\n\r\nI use rcu_assign_pointer() to have lockdep support,\nthis was the choice made in neigh_flush_dev().(CVE-2023-52522)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: fix potential key use-after-free\r\n\r\nWhen ieee80211_key_link() is called by ieee80211_gtk_rekey_add()\nbut returns 0 due to KRACK protection (identical key reinstall),\nieee80211_gtk_rekey_add() will still return a pointer into the\nkey, in a potential use-after-free. This normally doesn\u0026apos;t happen\nsince it\u0026apos;s only called by iwlwifi in case of WoWLAN rekey offload\nwhich has its own KRACK protection, but still better to fix, do\nthat by returning an error code and converting that to success on\nthe cfg80211 boundary only, leaving the error for bad callers of\nieee80211_gtk_rekey_add().(CVE-2023-52530)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential use after free in nilfs_gccache_submit_read_data()\r\n\r\nIn nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the\nreference count of bh when the call to nilfs_dat_translate() fails.  If\nthe reference count hits 0 and its owner page gets unlocked, bh may be\nfreed.  However, bh-\u0026gt;b_page is dereferenced to put the page after that,\nwhich may result in a use-after-free bug.  This patch moves the release\noperation after unlocking and putting the page.\r\n\r\nNOTE: The function in question is only called in GC, and in combination\nwith current userland tools, address translation using DAT does not occur\nin that function, so the code path that causes this issue will not be\nexecuted.  However, it is possible to run that code path by intentionally\nmodifying the userland GC library or by calling the GC ioctl directly.\r\n\r\n[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: use DEV_STATS_INC()\r\n\r\nsyzbot/KCSAN reported data-races in br_handle_frame_finish() [1]\nThis function can run from multiple cpus without mutual exclusion.\r\n\r\nAdopt SMP safe DEV_STATS_INC() to update dev-\u0026gt;stats fields.\r\n\r\nHandles updates to dev-\u0026gt;stats.tx_dropped while we are at it.\r\n\r\n[1]\nBUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\nrun_ksoftirqd+0x17/0x20 kernel/softirq.c:921\nsmpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\ndo_softirq+0x5e/0x90 kernel/softirq.c:454\n__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381\n__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210\nspin_unlock_bh include/linux/spinlock.h:396 [inline]\nbatadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356\nbatadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560\nprocess_one_work kernel/workqueue.c:2630 [inline]\nprocess_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703\nworker_thread+0x525/0x730 kernel/workqueue.c:2784\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nvalue changed: 0x00000000000d7190 -\u0026gt; 0x00000000000d7191\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nceph: fix deadlock or deadcode of misusing dget()\r\n\r\nThe lock order is incorrect between denty and its parent, we should\nalways make sure that the parent get the lock first.\r\n\r\nBut since this deadcode is never used and the parent dir will always\nbe set from the callers, let\u0026apos;s just remove it.(CVE-2023-52583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/ipoib: Fix mcast list locking\r\n\r\nReleasing the `priv-\u0026gt;lock` while iterating the `priv-\u0026gt;multicast_list` in\n`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to\nremove the items while in the middle of iteration. If the mcast is removed\nwhile the lock was dropped, the for loop spins forever resulting in a hard\nlockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):\r\n\r\n    Task A (kworker/u72:2 below)       | Task B (kworker/u72:0 below)\n    -----------------------------------+-----------------------------------\n    ipoib_mcast_join_task(work)        | ipoib_ib_dev_flush_light(work)\n      spin_lock_irq(\u0026amp;priv-\u0026gt;lock)       | __ipoib_ib_dev_flush(priv, ...)\n      list_for_each_entry(mcast,       | ipoib_mcast_dev_flush(dev = priv-\u0026gt;dev)\n          \u0026amp;priv-\u0026gt;multicast_list, list) |\n        ipoib_mcast_join(dev, mcast)   |\n          spin_unlock_irq(\u0026amp;priv-\u0026gt;lock) |\n                                       |   spin_lock_irqsave(\u0026amp;priv-\u0026gt;lock, flags)\n                                       |   list_for_each_entry_safe(mcast, tmcast,\n                                       |                  \u0026amp;priv-\u0026gt;multicast_list, list)\n                                       |     list_del(\u0026amp;mcast-\u0026gt;list);\n                                       |     list_add_tail(\u0026amp;mcast-\u0026gt;list, \u0026amp;remove_list)\n                                       |   spin_unlock_irqrestore(\u0026amp;priv-\u0026gt;lock, flags)\n          spin_lock_irq(\u0026amp;priv-\u0026gt;lock)   |\n                                       |   ipoib_mcast_remove_list(\u0026amp;remove_list)\n   (Here, `mcast` is no longer on the  |     list_for_each_entry_safe(mcast, tmcast,\n    `priv-\u0026gt;multicast_list` and we keep |                            remove_list, list)\n    spinning on the `remove_list` of   |  \u0026gt;\u0026gt;\u0026gt;  wait_for_completion(\u0026amp;mcast-\u0026gt;done)\n    the other thread which is blocked  |\n    and the list is still valid on     |\n    it\u0026apos;s stack.)\r\n\r\nFix this by keeping the lock held and changing to GFP_ATOMIC to prevent\neventual sleeps.\nUnfortunately we could not reproduce the lockup and confirm this fix but\nbased on the code review I think this fix should address such lockups.\r\n\r\ncrash\u0026gt; bc 31\nPID: 747      TASK: ff1c6a1a007e8000  CPU: 31   COMMAND: \u0026quot;kworker/u72:2\u0026quot;\n--\n    [exception RIP: ipoib_mcast_join_task+0x1b1]\n    RIP: ffffffffc0944ac1  RSP: ff646f199a8c7e00  RFLAGS: 00000002\n    RAX: 0000000000000000  RBX: ff1c6a1a04dc82f8  RCX: 0000000000000000\n                                  work (\u0026amp;priv-\u0026gt;mcast_task{,.work})\n    RDX: ff1c6a192d60ac68  RSI: 0000000000000286  RDI: ff1c6a1a04dc8000\n           \u0026amp;mcast-\u0026gt;list\n    RBP: ff646f199a8c7e90   R8: ff1c699980019420   R9: ff1c6a1920c9a000\n    R10: ff646f199a8c7e00  R11: ff1c6a191a7d9800  R12: ff1c6a192d60ac00\n                                                         mcast\n    R13: ff1c6a1d82200000  R14: ff1c6a1a04dc8000  R15: ff1c6a1a04dc82d8\n           dev                    priv (\u0026amp;priv-\u0026gt;lock)     \u0026amp;priv-\u0026gt;multicast_list (aka head)\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n--- \u0026lt;NMI exception stack\u0026gt; ---\n #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]\n #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967\r\n\r\ncrash\u0026gt; rx ff646f199a8c7e68\nff646f199a8c7e68:  ff1c6a1a04dc82f8 \u0026lt;\u0026lt;\u0026lt; work = \u0026amp;priv-\u0026gt;mcast_task.work\r\n\r\ncrash\u0026gt; list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000\n(empty)\r\n\r\ncrash\u0026gt; ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000\n  mcast_task.work.func = 0xffffffffc0944910 \u0026lt;ipoib_mcast_join_task\u0026gt;,\n  mcast_mutex.owner.counter = 0xff1c69998efec000\r\n\r\ncrash\u0026gt; b 8\nPID: 8        TASK: ff1c69998efec000  CPU: 33   COMMAND: \u0026quot;kworker/u72:0\u0026quot;\n--\n #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646\n #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]\n #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]\n #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]\n #7 [ff\n---truncated---(CVE-2023-52587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()\r\n\r\nFix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug\noccurs when txs-\u0026gt;cnt, data from a URB provided by a USB device, is\nbigger than the size of the array txs-\u0026gt;txstatus, which is\nHTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug\nhandling code after the check. Make the function return if that is the\ncase.\r\n\r\nFound by a modified version of syzkaller.\r\n\r\nUBSAN: array-index-out-of-bounds in htc_drv_txrx.c\nindex 13 is out of range for type \u0026apos;__wmi_event_txstatus [12]\u0026apos;\nCall Trace:\n ath9k_htc_txstatus\n ath9k_wmi_event_tasklet\n tasklet_action_common\n __do_softirq\n irq_exit_rxu\n sysvec_apic_timer_interrupt(CVE-2023-52594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rt2x00: restart beacon queue when hardware reset\r\n\r\nWhen a hardware reset is triggered, all registers are reset, so all\nqueues are forced to stop in hardware interface. However, mac80211\nwill not automatically stop the queue. If we don\u0026apos;t manually stop the\nbeacon queue, the queue will be deadlocked and unable to start again.\nThis patch fixes the issue where Apple devices cannot connect to the\nAP after calling ieee80211_restart_hw().(CVE-2023-52595)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: s390: fix setting of fpc register\r\n\r\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\r\n\r\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\r\n\r\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\r\n\r\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/ptrace: handle setting of fpc register correctly\r\n\r\nIf the content of the floating point control (fpc) register of a traced\nprocess is modified with the ptrace interface the new value is tested for\nvalidity by temporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the tracing process:\nif an interrupt happens while the value is temporarily loaded into the\nfpc register, and within interrupt context floating point or vector\nregisters are used, the current fp/vx registers are saved with\nsave_fpu_regs() assuming they belong to user space and will be loaded into\nfp/vx registers when returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space fpc register value, however\nit will be discarded, when returning to user space.\r\n\r\nIn result the tracer will incorrectly continue to run with the value that\nwas supposed to be used for the traced process.\r\n\r\nFix this by saving fpu register contents with save_fpu_regs() before using\ntest_fp_ctl().(CVE-2023-52598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: avoid online resizing failures due to oversized flex bg\r\n\r\nWhen we online resize an ext4 filesystem with a oversized flexbg_size,\r\n\r\n     mkfs.ext4 -F -G 67108864 $dev -b 4096 100M\n     mount $dev $dir\n     resize2fs $dev 16G\r\n\r\nthe following WARN_ON is triggered:\n==================================================================\nWARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550\nModules linked in: sg(E)\nCPU: 0 PID: 427 Comm: resize2fs Tainted: G  E  6.6.0-rc5+ #314\nRIP: 0010:__alloc_pages+0x411/0x550\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __kmalloc_large_node+0xa2/0x200\n __kmalloc+0x16e/0x290\n ext4_resize_fs+0x481/0xd80\n __ext4_ioctl+0x1616/0x1d90\n ext4_ioctl+0x12/0x20\n __x64_sys_ioctl+0xf0/0x150\n do_syscall_64+0x3b/0x90\n==================================================================\r\n\r\nThis is because flexbg_size is too large and the size of the new_group_data\narray to be allocated exceeds MAX_ORDER. Currently, the minimum value of\nMAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding\nmaximum number of groups that can be allocated is:\r\n\r\n (PAGE_SIZE \u0026lt;\u0026lt; MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845\r\n\r\nAnd the value that is down-aligned to the power of 2 is 16384. Therefore,\nthis value is defined as MAX_RESIZE_BG, and the number of groups added\neach time does not exceed this value during resizing, and is added multiple\ntimes to complete the online resizing. The difference is that the metadata\nin a flex_bg may be more dispersed.(CVE-2023-52622)","status":"published","published":"2024-04-19T11:06:55Z","modified":"2026-08-18T01:17:17.136339012Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.095407Z"},{"id":"OESA-2024-1484","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: img-scb: fix reference leak when pm_runtime_get_sync fails\r\n\r\nThe PM reference count is not expected to be incremented on\nreturn in functions img_i2c_xfer and img_i2c_init.\r\n\r\nHowever, pm_runtime_get_sync will increment the PM reference\ncount even failed. Forgetting to putting operation will result\nin a reference leak here.\r\n\r\nReplace it with pm_runtime_resume_and_get to keep usage\ncounter balanced.(CVE-2020-36783)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkyber: fix out of bounds access when preempted\r\n\r\n__blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and\npasses the hctx to -\u0026gt;bio_merge(). kyber_bio_merge() then gets the ctx\nfor the current CPU again and uses that to get the corresponding Kyber\ncontext in the passed hctx. However, the thread may be preempted between\nthe two calls to blk_mq_get_ctx(), and the ctx returned the second time\nmay no longer correspond to the passed hctx. This \u0026quot;works\u0026quot; accidentally\nmost of the time, but it can cause us to read garbage if the second ctx\ncame from an hctx with more ctx\u0026apos;s than the first one (i.e., if\nctx-\u0026gt;index_hw[hctx-\u0026gt;type] \u0026gt; hctx-\u0026gt;nr_ctx).\r\n\r\nThis manifested as this UBSAN array index out of bounds error reported\nby Jakub:\r\n\r\nUBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9\nindex 13106 is out of range for type \u0026apos;long unsigned int [128]\u0026apos;\nCall Trace:\n dump_stack+0xa4/0xe5\n ubsan_epilogue+0x5/0x40\n __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34\n queued_spin_lock_slowpath+0x476/0x480\n do_raw_spin_lock+0x1c2/0x1d0\n kyber_bio_merge+0x112/0x180\n blk_mq_submit_bio+0x1f5/0x1100\n submit_bio_noacct+0x7b0/0x870\n submit_bio+0xc2/0x3a0\n btrfs_map_bio+0x4f0/0x9d0\n btrfs_submit_data_bio+0x24e/0x310\n submit_one_bio+0x7f/0xb0\n submit_extent_page+0xc4/0x440\n __extent_writepage_io+0x2b8/0x5e0\n __extent_writepage+0x28d/0x6e0\n extent_write_cache_pages+0x4d7/0x7a0\n extent_writepages+0xa2/0x110\n do_writepages+0x8f/0x180\n __writeback_single_inode+0x99/0x7f0\n writeback_sb_inodes+0x34e/0x790\n __writeback_inodes_wb+0x9e/0x120\n wb_writeback+0x4d2/0x660\n wb_workfn+0x64d/0xa10\n process_one_work+0x53a/0xa80\n worker_thread+0x69/0x5b0\n kthread+0x20b/0x240\n ret_from_fork+0x1f/0x30\r\n\r\nOnly Kyber uses the hctx, so fix it by passing the request_queue to\n-\u0026gt;bio_merge() instead. BFQ and mq-deadline just use that, and Kyber can\nmap the queues itself to avoid the mismatch.(CVE-2021-46984)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbus: qcom: Put child node before return\r\n\r\nPut child node before return to fix potential reference count leak.\nGenerally, the reference count of child is incremented and decremented\nautomatically in the macro for_each_available_child_of_node() and should\nbe decremented manually if the loop is broken in loop body.(CVE-2021-47054)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init\r\n\r\nADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()\nbefore calling adf_iov_putmsg()-\u0026gt;mutex_lock(vf2pf_lock), however the\nvf2pf_lock is initialized in adf_dev_init(), which can fail and when it\nfail, the vf2pf_lock is either not initialized or destroyed, a subsequent\nuse of vf2pf_lock will cause issue.\nTo fix this issue, only set this flag if adf_dev_init() returns 0.\r\n\r\n[    7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0\n[    7.180345] Call Trace:\n[    7.182576]  mutex_lock+0xc9/0xd0\n[    7.183257]  adf_iov_putmsg+0x118/0x1a0 [intel_qat]\n[    7.183541]  adf_vf2pf_shutdown+0x4d/0x7b [intel_qat]\n[    7.183834]  adf_dev_shutdown+0x172/0x2b0 [intel_qat]\n[    7.184127]  adf_probe+0x5e9/0x600 [qat_dh895xccvf](CVE-2021-47056)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Stop looking for coalesced MMIO zones if the bus is destroyed\r\n\r\nAbort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev()\nfails to allocate memory for the new instance of the bus.  If it can\u0026apos;t\ninstantiate a new bus, unregister_dev() destroys all devices _except_ the\ntarget device.   But, it doesn\u0026apos;t tell the caller that it obliterated the\nbus and invoked the destructor for all devices that were on the bus.  In\nthe coalesced MMIO case, this can result in a deleted list entry\ndereference due to attempting to continue iterating on coalesced_zones\nafter future entries (in the walk) have been deleted.\r\n\r\nOpportunistically add curly braces to the for-loop, which encompasses\nmany lines but sneaks by without braces due to the guts being a single\nif statement.(CVE-2021-47060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: Destroy I/O bus devices on unregister failure _after_ sync\u0026apos;ing SRCU\r\n\r\nIf allocating a new instance of an I/O bus fails when unregistering a\ndevice, wait to destroy the device until after all readers are guaranteed\nto see the new null bus.  Destroying devices before the bus is nullified\ncould lead to use-after-free since readers expect the devices on their\nreference of the bus to remain valid.(CVE-2021-47061)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm: bridge/panel: Cleanup connector on bridge detach\r\n\r\nIf we don\u0026apos;t call drm_connector_cleanup() manually in\npanel_bridge_detach(), the connector will be cleaned up with the other\nDRM objects in the call to drm_mode_config_cleanup(). However, since our\ndrm_connector is devm-allocated, by the time drm_mode_config_cleanup()\nwill be called, our connector will be long gone. Therefore, the\nconnector must be cleaned up when the bridge is detached to avoid\nuse-after-free conditions.\r\n\r\nv2: Cleanup connector only if it was created\r\n\r\nv3: Add FIXME\r\n\r\nv4: (Use connector-\u0026gt;dev) directly in if() block(CVE-2021-47063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix a memory leak in error handling paths\r\n\r\nIf \u0026apos;vmbus_establish_gpadl()\u0026apos; fails, the (recv|send)_gpadl will not be\nupdated and \u0026apos;hv_uio_cleanup()\u0026apos; in the error handling path will not be\nable to free the corresponding buffer.\r\n\r\nIn such a case, we need to free the buffer explicitly.(CVE-2021-47071)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme-loop: fix memory leak in nvme_loop_create_ctrl()\r\n\r\nWhen creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()\nfails, the loop ctrl should be freed before jumping to the \u0026quot;out\u0026quot; label.(CVE-2021-47074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qedf: Add pointer checks in qedf_update_link_speed()\r\n\r\nThe following trace was observed:\r\n\r\n [   14.042059] Call Trace:\n [   14.042061]  \u0026lt;IRQ\u0026gt;\n [   14.042068]  qedf_link_update+0x144/0x1f0 [qedf]\n [   14.042117]  qed_link_update+0x5c/0x80 [qed]\n [   14.042135]  qed_mcp_handle_link_change+0x2d2/0x410 [qed]\n [   14.042155]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042170]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042186]  ? qed_rd+0x13/0x40 [qed]\n [   14.042205]  qed_mcp_handle_events+0x437/0x690 [qed]\n [   14.042221]  ? qed_set_ptt+0x70/0x80 [qed]\n [   14.042239]  qed_int_sp_dpc+0x3a6/0x3e0 [qed]\n [   14.042245]  tasklet_action_common.isra.14+0x5a/0x100\n [   14.042250]  __do_softirq+0xe4/0x2f8\n [   14.042253]  irq_exit+0xf7/0x100\n [   14.042255]  do_IRQ+0x7f/0xd0\n [   14.042257]  common_interrupt+0xf/0xf\n [   14.042259]  \u0026lt;/IRQ\u0026gt;\r\n\r\nAPI qedf_link_update() is getting called from QED but by that time\nshost_data is not initialised. This results in a NULL pointer dereference\nwhen we try to dereference shost_data while updating supported_speeds.\r\n\r\nAdd a NULL pointer check before dereferencing shost_data.(CVE-2021-47077)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/rxe: Clear all QP fields if creation failed\r\n\r\nrxe_qp_do_cleanup() relies on valid pointer values in QP for the properly\ncreated ones, but in case rxe_qp_from_init() failed it was filled with\ngarbage and caused tot the following error.\r\n\r\n  refcount_t: underflow; use-after-free.\n  WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28\n  Modules linked in:\n  CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0\n  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\n  RIP: 0010:refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28\n  Code: e9 db fe ff ff 48 89 df e8 2c c2 ea fd e9 8a fe ff ff e8 72 6a a7 fd 48 c7 c7 e0 b2 c1 89 c6 05 dc 3a e6 09 01 e8 ee 74 fb 04 \u0026lt;0f\u0026gt; 0b e9 af fe ff ff 0f 1f 84 00 00 00 00 00 41 56 41 55 41 54 55\n  RSP: 0018:ffffc900097ceba8 EFLAGS: 00010286\n  RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000\n  RDX: 0000000000040000 RSI: ffffffff815bb075 RDI: fffff520012f9d67\n  RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000\n  R10: ffffffff815b4eae R11: 0000000000000000 R12: ffff8880322a4800\n  R13: ffff8880322a4940 R14: ffff888033044e00 R15: 0000000000000000\n  FS:  00007f6eb2be3700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fdbe5d41000 CR3: 000000001d181000 CR4: 00000000001506e0\n  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n  Call Trace:\n   __refcount_sub_and_test include/linux/refcount.h:283 [inline]\n   __refcount_dec_and_test include/linux/refcount.h:315 [inline]\n   refcount_dec_and_test include/linux/refcount.h:333 [inline]\n   kref_put include/linux/kref.h:64 [inline]\n   rxe_qp_do_cleanup+0x96f/0xaf0 drivers/infiniband/sw/rxe/rxe_qp.c:805\n   execute_in_process_context+0x37/0x150 kernel/workqueue.c:3327\n   rxe_elem_release+0x9f/0x180 drivers/infiniband/sw/rxe/rxe_pool.c:391\n   kref_put include/linux/kref.h:65 [inline]\n   rxe_create_qp+0x2cd/0x310 drivers/infiniband/sw/rxe/rxe_verbs.c:425\n   _ib_create_qp drivers/infiniband/core/core_priv.h:331 [inline]\n   ib_create_named_qp+0x2ad/0x1370 drivers/infiniband/core/verbs.c:1231\n   ib_create_qp include/rdma/ib_verbs.h:3644 [inline]\n   create_mad_qp+0x177/0x2d0 drivers/infiniband/core/mad.c:2920\n   ib_mad_port_open drivers/infiniband/core/mad.c:3001 [inline]\n   ib_mad_init_device+0xd6f/0x1400 drivers/infiniband/core/mad.c:3092\n   add_client_context+0x405/0x5e0 drivers/infiniband/core/device.c:717\n   enable_device_and_get+0x1cd/0x3b0 drivers/infiniband/core/device.c:1331\n   ib_register_device drivers/infiniband/core/device.c:1413 [inline]\n   ib_register_device+0x7c7/0xa50 drivers/infiniband/core/device.c:1365\n   rxe_register_device+0x3d5/0x4a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1147\n   rxe_add+0x12fe/0x16d0 drivers/infiniband/sw/rxe/rxe.c:247\n   rxe_net_add+0x8c/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:503\n   rxe_newlink drivers/infiniband/sw/rxe/rxe.c:269 [inline]\n   rxe_newlink+0xb7/0xe0 drivers/infiniband/sw/rxe/rxe.c:250\n   nldev_newlink+0x30e/0x550 drivers/infiniband/core/nldev.c:1555\n   rdma_nl_rcv_msg+0x36d/0x690 drivers/infiniband/core/netlink.c:195\n   rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n   rdma_nl_rcv+0x2ee/0x430 drivers/infiniband/core/netlink.c:259\n   netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]\n   netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338\n   netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927\n   sock_sendmsg_nosec net/socket.c:654 [inline]\n   sock_sendmsg+0xcf/0x120 net/socket.c:674\n   ____sys_sendmsg+0x6e8/0x810 net/socket.c:2350\n   ___sys_sendmsg+0xf3/0x170 net/socket.c:2404\n   __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433\n   do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47\n   entry_SYSCALL_64_after_hwframe+0\n---truncated---(CVE-2021-47078)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nasix: fix uninit-value in asix_mdio_read()\r\n\r\nasix_read_cmd() may read less than sizeof(smsr) bytes and in this case\nsmsr will be uninitialized.\r\n\r\nFail log:\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\nBUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\n asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/tls: Fix use-after-free after the TLS device goes down and up\r\n\r\nWhen a netdev with active TLS offload goes down, tls_device_down is\ncalled to stop the offload and tear down the TLS context. However, the\nsocket stays alive, and it still points to the TLS context, which is now\ndeallocated. If a netdev goes up, while the connection is still active,\nand the data flow resumes after a number of TCP retransmissions, it will\nlead to a use-after-free of the TLS context.\r\n\r\nThis commit addresses this bug by keeping the context alive until its\nnormal destruction, and implements the necessary fallbacks, so that the\nconnection can resume in software (non-offloaded) kTLS mode.\r\n\r\nOn the TX side tls_sw_fallback is used to encrypt all packets. The RX\nside already has all the necessary fallbacks, because receiving\nnon-decrypted packets is supported. The thing needed on the RX side is\nto block resync requests, which are normally produced after receiving\nnon-decrypted packets.\r\n\r\nThe necessary synchronization is implemented for a graceful teardown:\nfirst the fallbacks are deployed, then the driver resources are released\n(it used to be possible to have a tls_dev_resync after tls_dev_del).\r\n\r\nA new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback\nmode. It\u0026apos;s used to skip the RX resync logic completely, as it becomes\nuseless, and some objects may be released (for example, resync_async,\nwhich is allocated and freed by the driver).(CVE-2021-47131)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix a use-after-free\r\n\r\nlooks like we forget to set ttm-\u0026gt;sg to NULL.\nHit panic below\r\n\r\n[ 1235.844104] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7b4b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI\n[ 1235.989074] Call Trace:\n[ 1235.991751]  sg_free_table+0x17/0x20\n[ 1235.995667]  amdgpu_ttm_backend_unbind.cold+0x4d/0xf7 [amdgpu]\n[ 1236.002288]  amdgpu_ttm_backend_destroy+0x29/0x130 [amdgpu]\n[ 1236.008464]  ttm_tt_destroy+0x1e/0x30 [ttm]\n[ 1236.013066]  ttm_bo_cleanup_memtype_use+0x51/0xa0 [ttm]\n[ 1236.018783]  ttm_bo_release+0x262/0xa50 [ttm]\n[ 1236.023547]  ttm_bo_put+0x82/0xd0 [ttm]\n[ 1236.027766]  amdgpu_bo_unref+0x26/0x50 [amdgpu]\n[ 1236.032809]  amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu+0x7aa/0xd90 [amdgpu]\n[ 1236.040400]  kfd_ioctl_alloc_memory_of_gpu+0xe2/0x330 [amdgpu]\n[ 1236.046912]  kfd_ioctl+0x463/0x690 [amdgpu](CVE-2021-47142)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/smc: remove device from smcd_dev_list after failed device_add()\r\n\r\nIf the device_add() for a smcd_dev fails, there\u0026apos;s no cleanup step that\nrolls back the earlier list_add(). The device subsequently gets freed,\nand we end up with a corrupted list.\r\n\r\nAdd some error handling that removes the device from the list.(CVE-2021-47143)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/amdgpu: fix refcount leak\r\n\r\n[Why]\nthe gem object rfb-\u0026gt;base.obj[0] is get according to num_planes\nin amdgpufb_create, but is not put according to num_planes\r\n\r\n[How]\nput rfb-\u0026gt;base.obj[0] in amdgpu_fbdev_destroy according to num_planes(CVE-2021-47144)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: do not BUG_ON in link_to_fixup_dir\r\n\r\nWhile doing error injection testing I got the following panic\r\n\r\n  kernel BUG at fs/btrfs/tree-log.c:1862!\n  invalid opcode: 0000 [#1] SMP NOPTI\n  CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014\n  RIP: 0010:link_to_fixup_dir+0xd5/0xe0\n  RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216\n  RAX: fffffffffffffffb RBX: 00000000fffffffb RCX: ffff8f595287faf0\n  RDX: ffffb5800180fa37 RSI: ffff8f5954978800 RDI: 0000000000000000\n  RBP: ffff8f5953af9450 R08: 0000000000000019 R09: 0000000000000001\n  R10: 000151f408682970 R11: 0000000120021001 R12: ffff8f5954978800\n  R13: ffff8f595287faf0 R14: ffff8f5953c77dd0 R15: 0000000000000065\n  FS:  00007fc5284c8c40(0000) GS:ffff8f59bbd00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fc5287f47c0 CR3: 000000011275e002 CR4: 0000000000370ee0\n  Call Trace:\n   replay_one_buffer+0x409/0x470\n   ? btree_read_extent_buffer_pages+0xd0/0x110\n   walk_up_log_tree+0x157/0x1e0\n   walk_log_tree+0xa6/0x1d0\n   btrfs_recover_log_trees+0x1da/0x360\n   ? replay_one_extent+0x7b0/0x7b0\n   open_ctree+0x1486/0x1720\n   btrfs_mount_root.cold+0x12/0xea\n   ? __kmalloc_track_caller+0x12f/0x240\n   legacy_get_tree+0x24/0x40\n   vfs_get_tree+0x22/0xb0\n   vfs_kern_mount.part.0+0x71/0xb0\n   btrfs_mount+0x10d/0x380\n   ? vfs_parse_fs_string+0x4d/0x90\n   legacy_get_tree+0x24/0x40\n   vfs_get_tree+0x22/0xb0\n   path_mount+0x433/0xa10\n   __x64_sys_mount+0xe3/0x120\n   do_syscall_64+0x3d/0x80\n   entry_SYSCALL_64_after_hwframe+0x44/0xae\r\n\r\nWe can get -EIO or any number of legitimate errors from\nbtrfs_search_slot(), panicing here is not the appropriate response.  The\nerror path for this code handles errors properly, simply return the\nerror.(CVE-2021-47145)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmld: fix panic in mld_newpack()\r\n\r\nmld_newpack() doesn\u0026apos;t allow to allocate high order page,\nonly order-0 allocation is allowed.\nIf headroom size is too large, a kernel panic could occur in skb_put().\r\n\r\nTest commands:\n    ip netns del A\n    ip netns del B\n    ip netns add A\n    ip netns add B\n    ip link add veth0 type veth peer name veth1\n    ip link set veth0 netns A\n    ip link set veth1 netns B\r\n\r\n    ip netns exec A ip link set lo up\n    ip netns exec A ip link set veth0 up\n    ip netns exec A ip -6 a a 2001:db8:0::1/64 dev veth0\n    ip netns exec B ip link set lo up\n    ip netns exec B ip link set veth1 up\n    ip netns exec B ip -6 a a 2001:db8:0::2/64 dev veth1\n    for i in {1..99}\n    do\n        let A=$i-1\n        ip netns exec A ip link add ip6gre$i type ip6gre \\\n\tlocal 2001:db8:$A::1 remote 2001:db8:$A::2 encaplimit 100\n        ip netns exec A ip -6 a a 2001:db8:$i::1/64 dev ip6gre$i\n        ip netns exec A ip link set ip6gre$i up\r\n\r\n        ip netns exec B ip link add ip6gre$i type ip6gre \\\n\tlocal 2001:db8:$A::2 remote 2001:db8:$A::1 encaplimit 100\n        ip netns exec B ip -6 a a 2001:db8:$i::2/64 dev ip6gre$i\n        ip netns exec B ip link set ip6gre$i up\n    done\r\n\r\nSplat looks like:\nkernel BUG at net/core/skbuff.c:110!\ninvalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.12.0+ #891\nWorkqueue: ipv6_addrconf addrconf_dad_work\nRIP: 0010:skb_panic+0x15d/0x15f\nCode: 92 fe 4c 8b 4c 24 10 53 8b 4d 70 45 89 e0 48 c7 c7 00 ae 79 83\n41 57 41 56 41 55 48 8b 54 24 a6 26 f9 ff \u0026lt;0f\u0026gt; 0b 48 8b 6c 24 20 89\n34 24 e8 4a 4e 92 fe 8b 34 24 48 c7 c1 20\nRSP: 0018:ffff88810091f820 EFLAGS: 00010282\nRAX: 0000000000000089 RBX: ffff8881086e9000 RCX: 0000000000000000\nRDX: 0000000000000089 RSI: 0000000000000008 RDI: ffffed1020123efb\nRBP: ffff888005f6eac0 R08: ffffed1022fc0031 R09: ffffed1022fc0031\nR10: ffff888117e00187 R11: ffffed1022fc0030 R12: 0000000000000028\nR13: ffff888008284eb0 R14: 0000000000000ed8 R15: 0000000000000ec0\nFS:  0000000000000000(0000) GS:ffff888117c00000(0000)\nknlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8b801c5640 CR3: 0000000033c2c006 CR4: 00000000003706f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n ? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n ? ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n skb_put.cold.104+0x22/0x22\n ip6_mc_hdr.isra.26.constprop.46+0x12a/0x600\n ? rcu_read_lock_sched_held+0x91/0xc0\n mld_newpack+0x398/0x8f0\n ? ip6_mc_hdr.isra.26.constprop.46+0x600/0x600\n ? lock_contended+0xc40/0xc40\n add_grhead.isra.33+0x280/0x380\n add_grec+0x5ca/0xff0\n ? mld_sendpack+0xf40/0xf40\n ? lock_downgrade+0x690/0x690\n mld_send_initial_cr.part.34+0xb9/0x180\n ipv6_mc_dad_complete+0x15d/0x1b0\n addrconf_dad_completed+0x8d2/0xbb0\n ? lock_downgrade+0x690/0x690\n ? addrconf_rs_timer+0x660/0x660\n ? addrconf_dad_work+0x73c/0x10e0\n addrconf_dad_work+0x73c/0x10e0\r\n\r\nAllowing high order page allocation could fix this problem.(CVE-2021-47146)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: i801: Don\u0026apos;t generate an interrupt on bus reset\r\n\r\nNow that the i2c-i801 driver supports interrupts, setting the KILL bit\nin a attempt to recover from a timed out transaction triggers an\ninterrupt. Unfortunately, the interrupt handler (i801_isr) is not\nprepared for this situation and will try to process the interrupt as\nif it was signaling the end of a successful transaction. In the case\nof a block transaction, this can result in an out-of-range memory\naccess.\r\n\r\nThis condition was reproduced several times by syzbot:\nhttps://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e\nhttps://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e\nhttps://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e\nhttps://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb\nhttps://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a\nhttps://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79\r\n\r\nSo disable interrupts while trying to reset the bus. Interrupts will\nbe enabled again for the following transaction.(CVE-2021-47153)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: fix a crash if -\u0026gt;get_sset_count() fails\r\n\r\nIf ds-\u0026gt;ops-\u0026gt;get_sset_count() fails then it \u0026quot;count\u0026quot; is a negative error\ncode such as -EOPNOTSUPP.  Because \u0026quot;i\u0026quot; is an unsigned int, the negative\nerror code is type promoted to a very high value and the loop will\ncorrupt memory until the system crashes.\r\n\r\nFix this by checking for error codes and changing the type of \u0026quot;i\u0026quot; to\njust int.(CVE-2021-47159)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: dsa: mt7530: fix VLAN traffic leaks\r\n\r\nPCR_MATRIX field was set to all 1\u0026apos;s when VLAN filtering is enabled, but\nwas not reset when it is disabled, which may cause traffic leaks:\r\n\r\n\tip link add br0 type bridge vlan_filtering 1\n\tip link add br1 type bridge vlan_filtering 1\n\tip link set swp0 master br0\n\tip link set swp1 master br1\n\tip link set br0 type bridge vlan_filtering 0\n\tip link set br1 type bridge vlan_filtering 0\n\t# traffic in br0 and br1 will start leaking to each other\r\n\r\nAs port_bridge_{add,del} have set up PCR_MATRIX properly, remove the\nPCR_MATRIX write from mt7530_port_set_vlan_aware.(CVE-2021-47160)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: spi-fsl-dspi: Fix a resource leak in an error handling path\r\n\r\n\u0026apos;dspi_request_dma()\u0026apos; should be undone by a \u0026apos;dspi_release_dma()\u0026apos; call in the\nerror handling path of the probe function, as already done in the remove\nfunction(CVE-2021-47161)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: skb_linearize the head skb when reassembling msgs\r\n\r\nIt\u0026apos;s not a good idea to append the frag skb to a skb\u0026apos;s frag_list if\nthe frag_list already has skbs from elsewhere, such as this skb was\ncreated by pskb_copy() where the frag_list was cloned (all the skbs\nin it were skb_get\u0026apos;ed) and shared by multiple skbs.\r\n\r\nHowever, the new appended frag skb should have been only seen by the\ncurrent skb. Otherwise, it will cause use after free crashes as this\nappended frag skb are seen by multiple skbs but it only got skb_get\ncalled once.\r\n\r\nThe same thing happens with a skb updated by pskb_may_pull() with a\nskb_cloned skb. Li Shuang has reported quite a few crashes caused\nby this when doing testing over macvlan devices:\r\n\r\n  [] kernel BUG at net/core/skbuff.c:1970!\n  [] Call Trace:\n  []  skb_clone+0x4d/0xb0\n  []  macvlan_broadcast+0xd8/0x160 [macvlan]\n  []  macvlan_process_broadcast+0x148/0x150 [macvlan]\n  []  process_one_work+0x1a7/0x360\n  []  worker_thread+0x30/0x390\r\n\r\n  [] kernel BUG at mm/usercopy.c:102!\n  [] Call Trace:\n  []  __check_heap_object+0xd3/0x100\n  []  __check_object_size+0xff/0x16b\n  []  simple_copy_to_iter+0x1c/0x30\n  []  __skb_datagram_iter+0x7d/0x310\n  []  __skb_datagram_iter+0x2a5/0x310\n  []  skb_copy_datagram_iter+0x3b/0x90\n  []  tipc_recvmsg+0x14a/0x3a0 [tipc]\n  []  ____sys_recvmsg+0x91/0x150\n  []  ___sys_recvmsg+0x7b/0xc0\r\n\r\n  [] kernel BUG at mm/slub.c:305!\n  [] Call Trace:\n  []  \u0026lt;IRQ\u0026gt;\n  []  kmem_cache_free+0x3ff/0x400\n  []  __netif_receive_skb_core+0x12c/0xc40\n  []  ? kmem_cache_alloc+0x12e/0x270\n  []  netif_receive_skb_internal+0x3d/0xb0\n  []  ? get_rx_page_info+0x8e/0xa0 [be2net]\n  []  be_poll+0x6ef/0xd00 [be2net]\n  []  ? irq_exit+0x4f/0x100\n  []  net_rx_action+0x149/0x3b0\r\n\r\n  ...\r\n\r\nThis patch is to fix it by linearizing the head skb if it has frag_list\nset in tipc_buf_append(). Note that we choose to do this before calling\nskb_unshare(), as __skb_linearize() will avoid skb_copy(). Also, we can\nnot just drop the frag_list either as the early time.(CVE-2021-47162)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: wait and exit until all work queues are done\r\n\r\nOn some host, a crash could be triggered simply by repeating these\ncommands several times:\r\n\r\n  # modprobe tipc\n  # tipc bearer enable media udp name UDP1 localip 127.0.0.1\n  # rmmod tipc\r\n\r\n  [] BUG: unable to handle kernel paging request at ffffffffc096bb00\n  [] Workqueue: events 0xffffffffc096bb00\n  [] Call Trace:\n  []  ? process_one_work+0x1a7/0x360\n  []  ? worker_thread+0x30/0x390\n  []  ? create_worker+0x1a0/0x1a0\n  []  ? kthread+0x116/0x130\n  []  ? kthread_flush_work_fn+0x10/0x10\n  []  ? ret_from_fork+0x35/0x40\r\n\r\nWhen removing the TIPC module, the UDP tunnel sock will be delayed to\nrelease in a work queue as sock_release() can\u0026apos;t be done in rtnl_lock().\nIf the work queue is schedule to run after the TIPC module is removed,\nkernel will crash as the work queue function cleanup_beareri() code no\nlonger exists when trying to invoke it.\r\n\r\nTo fix it, this patch introduce a member wq_count in tipc_net to track\nthe numbers of work queues in schedule, and  wait and exit until all\nwork queues are done in tipc_exit_net().(CVE-2021-47163)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFS: Fix an Oopsable condition in __nfs_pageio_add_request()\r\n\r\nEnsure that nfs_pageio_error_cleanup() resets the mirror array contents,\nso that the structure reflects the fact that it is now empty.\nAlso change the test in nfs_pageio_do_add_request() to be more robust by\nchecking whether or not the list is empty rather than relying on the\nvalue of pg_count.(CVE-2021-47167)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nUSB: usbfs: Don\u0026apos;t WARN about excessively large memory allocations\r\n\r\nSyzbot found that the kernel generates a WARNing if the user tries to\nsubmit a bulk transfer through usbfs with a buffer that is way too\nlarge.  This isn\u0026apos;t a bug in the kernel; it\u0026apos;s merely an invalid request\nfrom the user and the usbfs code does handle it correctly.\r\n\r\nIn theory the same thing can happen with async transfers, or with the\npacket descriptor table for isochronous transfers.\r\n\r\nTo prevent the MM subsystem from complaining about these bad\nallocation requests, add the __GFP_NOWARN flag to the kmalloc calls\nfor these buffers.(CVE-2021-47170)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: usb: fix memory leak in smsc75xx_bind\r\n\r\nSyzbot reported memory leak in smsc75xx_bind().\nThe problem was is non-freed memory in case of\nerrors after memory allocation.\r\n\r\nbacktrace:\n  [\u0026lt;ffffffff84245b62\u0026gt;] kmalloc include/linux/slab.h:556 [inline]\n  [\u0026lt;ffffffff84245b62\u0026gt;] kzalloc include/linux/slab.h:686 [inline]\n  [\u0026lt;ffffffff84245b62\u0026gt;] smsc75xx_bind+0x7a/0x334 drivers/net/usb/smsc75xx.c:1460\n  [\u0026lt;ffffffff82b5b2e6\u0026gt;] usbnet_probe+0x3b6/0xc30 drivers/net/usb/usbnet.c:1728(CVE-2021-47171)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmisc/uss720: fix memory leak in uss720_probe\r\n\r\nuss720_probe forgets to decrease the refcount of usbdev in uss720_probe.\nFix this by decreasing the refcount of usbdev by usb_put_dev.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888101113800 (size 2048):\n  comm \u0026quot;kworker/0:1\u0026quot;, pid 7, jiffies 4294956777 (age 28.870s)\n  hex dump (first 32 bytes):\n    ff ff ff ff 31 00 00 00 00 00 00 00 00 00 00 00  ....1...........\n    00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00  ................\n  backtrace:\n    [\u0026lt;ffffffff82b8e822\u0026gt;] kmalloc include/linux/slab.h:554 [inline]\n    [\u0026lt;ffffffff82b8e822\u0026gt;] kzalloc include/linux/slab.h:684 [inline]\n    [\u0026lt;ffffffff82b8e822\u0026gt;] usb_alloc_dev+0x32/0x450 drivers/usb/core/usb.c:582\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_port_connect drivers/usb/core/hub.c:5129 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_port_connect_change drivers/usb/core/hub.c:5363 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] port_event drivers/usb/core/hub.c:5509 [inline]\n    [\u0026lt;ffffffff82b98441\u0026gt;] hub_event+0x1171/0x20c0 drivers/usb/core/hub.c:5591\n    [\u0026lt;ffffffff81259229\u0026gt;] process_one_work+0x2c9/0x600 kernel/workqueue.c:2275\n    [\u0026lt;ffffffff81259b19\u0026gt;] worker_thread+0x59/0x5d0 kernel/workqueue.c:2421\n    [\u0026lt;ffffffff81261228\u0026gt;] kthread+0x178/0x1b0 kernel/kthread.c:292\n    [\u0026lt;ffffffff8100227f\u0026gt;] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294(CVE-2021-47173)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nNFC: nci: fix memory leak in nci_allocate_device\r\n\r\nnfcmrvl_disconnect fails to free the hci_dev field in struct nci_dev.\nFix this by freeing hci_dev in nci_free_device.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888111ea6800 (size 1024):\n  comm \u0026quot;kworker/1:0\u0026quot;, pid 19, jiffies 4294942308 (age 13.580s)\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 60 fd 0c 81 88 ff ff  .........`......\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [\u0026lt;000000004bc25d43\u0026gt;] kmalloc include/linux/slab.h:552 [inline]\n    [\u0026lt;000000004bc25d43\u0026gt;] kzalloc include/linux/slab.h:682 [inline]\n    [\u0026lt;000000004bc25d43\u0026gt;] nci_hci_allocate+0x21/0xd0 net/nfc/nci/hci.c:784\n    [\u0026lt;00000000c59cff92\u0026gt;] nci_allocate_device net/nfc/nci/core.c:1170 [inline]\n    [\u0026lt;00000000c59cff92\u0026gt;] nci_allocate_device+0x10b/0x160 net/nfc/nci/core.c:1132\n    [\u0026lt;00000000006e0a8e\u0026gt;] nfcmrvl_nci_register_dev+0x10a/0x1c0 drivers/nfc/nfcmrvl/main.c:153\n    [\u0026lt;000000004da1b57e\u0026gt;] nfcmrvl_probe+0x223/0x290 drivers/nfc/nfcmrvl/usb.c:345\n    [\u0026lt;00000000d506aed9\u0026gt;] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396\n    [\u0026lt;00000000bc632c92\u0026gt;] really_probe+0x159/0x4a0 drivers/base/dd.c:554\n    [\u0026lt;00000000f5009125\u0026gt;] driver_probe_device+0x84/0x100 drivers/base/dd.c:740\n    [\u0026lt;000000000ce658ca\u0026gt;] __device_attach_driver+0xee/0x110 drivers/base/dd.c:846\n    [\u0026lt;000000007067d05f\u0026gt;] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:431\n    [\u0026lt;00000000f8e13372\u0026gt;] __device_attach+0x122/0x250 drivers/base/dd.c:914\n    [\u0026lt;000000009cf68860\u0026gt;] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:491\n    [\u0026lt;00000000359c965a\u0026gt;] device_add+0x5be/0xc30 drivers/base/core.c:3109\n    [\u0026lt;00000000086e4bd3\u0026gt;] usb_set_configuration+0x9d9/0xb90 drivers/usb/core/message.c:2164\n    [\u0026lt;00000000ca036872\u0026gt;] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238\n    [\u0026lt;00000000d40d36f6\u0026gt;] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293\n    [\u0026lt;00000000bc632c92\u0026gt;] really_probe+0x159/0x4a0 drivers/base/dd.c:554(CVE-2021-47180)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nEDAC/thunderx: Fix possible out-of-bounds string access\r\n\r\nEnabling -Wstringop-overflow globally exposes a warning for a common bug\nin the usage of strncat():\r\n\r\n  drivers/edac/thunderx_edac.c: In function \u0026apos;thunderx_ocx_com_threaded_isr\u0026apos;:\n  drivers/edac/thunderx_edac.c:1136:17: error: \u0026apos;strncat\u0026apos; specified bound 1024 equals destination size [-Werror=stringop-overflow=]\n   1136 |                 strncat(msg, other, OCX_MESSAGE_SIZE);\n        |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n   ...\n   1145 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\n   ...\n   1150 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\r\n\r\n   ...\r\n\r\nApparently the author of this driver expected strncat() to behave the\nway that strlcat() does, which uses the size of the destination buffer\nas its third argument rather than the length of the source buffer. The\nresult is that there is no check on the size of the allocated buffer.\r\n\r\nChange it to strlcat().\r\n\r\n  [ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nInput: powermate - fix use-after-free in powermate_config_complete\r\n\r\nsyzbot has found a use-after-free bug [1] in the powermate driver. This\nhappens when the device is disconnected, which leads to a memory free from\nthe powermate_device struct.  When an asynchronous control message\ncompletes after the kfree and its callback is invoked, the lock does not\nexist anymore and hence the bug.\r\n\r\nUse usb_kill_urb() on pm-\u0026gt;config to cancel any in-progress requests upon\ndevice disconnection.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command\r\n\r\nTags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed\nwhen we receive the response.(CVE-2023-52500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: assert requested protocol is valid\r\n\r\nThe protocol is used in a bit mask to determine if the protocol is\nsupported. Assert the provided protocol is less than the maximum\ndefined so it doesn\u0026apos;t potentially perform a shift-out-of-bounds and\nprovide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nieee802154: ca8210: Fix a potential UAF in ca8210_probe\r\n\r\nIf of_clk_add_provider() fails in ca8210_register_ext_clock(),\nit calls clk_unregister() to release priv-\u0026gt;clk and returns an\nerror. However, the caller ca8210_probe() then calls ca8210_remove(),\nwhere priv-\u0026gt;clk is freed again in ca8210_unregister_ext_clock(). In\nthis case, a use-after-free may happen in the second time we call\nclk_unregister().\r\n\r\nFix this by removing the first clk_unregister(). Also, priv-\u0026gt;clk could\nbe an error code on failure of clk_register_fixed_rate(). Use\nIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/srp: Do not call scsi_done() from srp_abort()\r\n\r\nAfter scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler\ncallback, it performs one of the following actions:\n* Call scsi_queue_insert().\n* Call scsi_finish_command().\n* Call scsi_eh_scmd_add().\nHence, SCSI abort handlers must not call scsi_done(). Otherwise all\nthe above actions would trigger a use-after-free. Hence remove the\nscsi_done() call from srp_abort(). Keep the srp_free_req() call\nbefore returning SUCCESS because we may not see the command again if\nSUCCESS is returned.(CVE-2023-52515)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix possible store tearing in neigh_periodic_work()\r\n\r\nWhile looking at a related syzbot report involving neigh_periodic_work(),\nI found that I forgot to add an annotation when deleting an\nRCU protected item from a list.\r\n\r\nReaders use rcu_deference(*np), we need to use either\nrcu_assign_pointer() or WRITE_ONCE() on writer side\nto prevent store tearing.\r\n\r\nI use rcu_assign_pointer() to have lockdep support,\nthis was the choice made in neigh_flush_dev().(CVE-2023-52522)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: fix potential key use-after-free\r\n\r\nWhen ieee80211_key_link() is called by ieee80211_gtk_rekey_add()\nbut returns 0 due to KRACK protection (identical key reinstall),\nieee80211_gtk_rekey_add() will still return a pointer into the\nkey, in a potential use-after-free. This normally doesn\u0026apos;t happen\nsince it\u0026apos;s only called by iwlwifi in case of WoWLAN rekey offload\nwhich has its own KRACK protection, but still better to fix, do\nthat by returning an error code and converting that to success on\nthe cfg80211 boundary only, leaving the error for bad callers of\nieee80211_gtk_rekey_add().(CVE-2023-52530)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential use after free in nilfs_gccache_submit_read_data()\r\n\r\nIn nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the\nreference count of bh when the call to nilfs_dat_translate() fails.  If\nthe reference count hits 0 and its owner page gets unlocked, bh may be\nfreed.  However, bh-\u0026gt;b_page is dereferenced to put the page after that,\nwhich may result in a use-after-free bug.  This patch moves the release\noperation after unlocking and putting the page.\r\n\r\nNOTE: The function in question is only called in GC, and in combination\nwith current userland tools, address translation using DAT does not occur\nin that function, so the code path that causes this issue will not be\nexecuted.  However, it is possible to run that code path by intentionally\nmodifying the userland GC library or by calling the GC ioctl directly.\r\n\r\n[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: use DEV_STATS_INC()\r\n\r\nsyzbot/KCSAN reported data-races in br_handle_frame_finish() [1]\nThis function can run from multiple cpus without mutual exclusion.\r\n\r\nAdopt SMP safe DEV_STATS_INC() to update dev-\u0026gt;stats fields.\r\n\r\nHandles updates to dev-\u0026gt;stats.tx_dropped while we are at it.\r\n\r\n[1]\nBUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\nrun_ksoftirqd+0x17/0x20 kernel/softirq.c:921\nsmpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\ndo_softirq+0x5e/0x90 kernel/softirq.c:454\n__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381\n__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210\nspin_unlock_bh include/linux/spinlock.h:396 [inline]\nbatadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356\nbatadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560\nprocess_one_work kernel/workqueue.c:2630 [inline]\nprocess_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703\nworker_thread+0x525/0x730 kernel/workqueue.c:2784\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nvalue changed: 0x00000000000d7190 -\u0026gt; 0x00000000000d7191\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nceph: fix deadlock or deadcode of misusing dget()\r\n\r\nThe lock order is incorrect between denty and its parent, we should\nalways make sure that the parent get the lock first.\r\n\r\nBut since this deadcode is never used and the parent dir will always\nbe set from the callers, let\u0026apos;s just remove it.(CVE-2023-52583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/ipoib: Fix mcast list locking\r\n\r\nReleasing the `priv-\u0026gt;lock` while iterating the `priv-\u0026gt;multicast_list` in\n`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to\nremove the items while in the middle of iteration. If the mcast is removed\nwhile the lock was dropped, the for loop spins forever resulting in a hard\nlockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):\r\n\r\n    Task A (kworker/u72:2 below)       | Task B (kworker/u72:0 below)\n    -----------------------------------+-----------------------------------\n    ipoib_mcast_join_task(work)        | ipoib_ib_dev_flush_light(work)\n      spin_lock_irq(\u0026amp;priv-\u0026gt;lock)       | __ipoib_ib_dev_flush(priv, ...)\n      list_for_each_entry(mcast,       | ipoib_mcast_dev_flush(dev = priv-\u0026gt;dev)\n          \u0026amp;priv-\u0026gt;multicast_list, list) |\n        ipoib_mcast_join(dev, mcast)   |\n          spin_unlock_irq(\u0026amp;priv-\u0026gt;lock) |\n                                       |   spin_lock_irqsave(\u0026amp;priv-\u0026gt;lock, flags)\n                                       |   list_for_each_entry_safe(mcast, tmcast,\n                                       |                  \u0026amp;priv-\u0026gt;multicast_list, list)\n                                       |     list_del(\u0026amp;mcast-\u0026gt;list);\n                                       |     list_add_tail(\u0026amp;mcast-\u0026gt;list, \u0026amp;remove_list)\n                                       |   spin_unlock_irqrestore(\u0026amp;priv-\u0026gt;lock, flags)\n          spin_lock_irq(\u0026amp;priv-\u0026gt;lock)   |\n                                       |   ipoib_mcast_remove_list(\u0026amp;remove_list)\n   (Here, `mcast` is no longer on the  |     list_for_each_entry_safe(mcast, tmcast,\n    `priv-\u0026gt;multicast_list` and we keep |                            remove_list, list)\n    spinning on the `remove_list` of   |  \u0026gt;\u0026gt;\u0026gt;  wait_for_completion(\u0026amp;mcast-\u0026gt;done)\n    the other thread which is blocked  |\n    and the list is still valid on     |\n    it\u0026apos;s stack.)\r\n\r\nFix this by keeping the lock held and changing to GFP_ATOMIC to prevent\neventual sleeps.\nUnfortunately we could not reproduce the lockup and confirm this fix but\nbased on the code review I think this fix should address such lockups.\r\n\r\ncrash\u0026gt; bc 31\nPID: 747      TASK: ff1c6a1a007e8000  CPU: 31   COMMAND: \u0026quot;kworker/u72:2\u0026quot;\n--\n    [exception RIP: ipoib_mcast_join_task+0x1b1]\n    RIP: ffffffffc0944ac1  RSP: ff646f199a8c7e00  RFLAGS: 00000002\n    RAX: 0000000000000000  RBX: ff1c6a1a04dc82f8  RCX: 0000000000000000\n                                  work (\u0026amp;priv-\u0026gt;mcast_task{,.work})\n    RDX: ff1c6a192d60ac68  RSI: 0000000000000286  RDI: ff1c6a1a04dc8000\n           \u0026amp;mcast-\u0026gt;list\n    RBP: ff646f199a8c7e90   R8: ff1c699980019420   R9: ff1c6a1920c9a000\n    R10: ff646f199a8c7e00  R11: ff1c6a191a7d9800  R12: ff1c6a192d60ac00\n                                                         mcast\n    R13: ff1c6a1d82200000  R14: ff1c6a1a04dc8000  R15: ff1c6a1a04dc82d8\n           dev                    priv (\u0026amp;priv-\u0026gt;lock)     \u0026amp;priv-\u0026gt;multicast_list (aka head)\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n--- \u0026lt;NMI exception stack\u0026gt; ---\n #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]\n #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967\r\n\r\ncrash\u0026gt; rx ff646f199a8c7e68\nff646f199a8c7e68:  ff1c6a1a04dc82f8 \u0026lt;\u0026lt;\u0026lt; work = \u0026amp;priv-\u0026gt;mcast_task.work\r\n\r\ncrash\u0026gt; list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000\n(empty)\r\n\r\ncrash\u0026gt; ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000\n  mcast_task.work.func = 0xffffffffc0944910 \u0026lt;ipoib_mcast_join_task\u0026gt;,\n  mcast_mutex.owner.counter = 0xff1c69998efec000\r\n\r\ncrash\u0026gt; b 8\nPID: 8        TASK: ff1c69998efec000  CPU: 33   COMMAND: \u0026quot;kworker/u72:0\u0026quot;\n--\n #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646\n #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]\n #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]\n #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]\n #7 [ff\n---truncated---(CVE-2023-52587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()\r\n\r\nFix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug\noccurs when txs-\u0026gt;cnt, data from a URB provided by a USB device, is\nbigger than the size of the array txs-\u0026gt;txstatus, which is\nHTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug\nhandling code after the check. Make the function return if that is the\ncase.\r\n\r\nFound by a modified version of syzkaller.\r\n\r\nUBSAN: array-index-out-of-bounds in htc_drv_txrx.c\nindex 13 is out of range for type \u0026apos;__wmi_event_txstatus [12]\u0026apos;\nCall Trace:\n ath9k_htc_txstatus\n ath9k_wmi_event_tasklet\n tasklet_action_common\n __do_softirq\n irq_exit_rxu\n sysvec_apic_timer_interrupt(CVE-2023-52594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rt2x00: restart beacon queue when hardware reset\r\n\r\nWhen a hardware reset is triggered, all registers are reset, so all\nqueues are forced to stop in hardware interface. However, mac80211\nwill not automatically stop the queue. If we don\u0026apos;t manually stop the\nbeacon queue, the queue will be deadlocked and unable to start again.\nThis patch fixes the issue where Apple devices cannot connect to the\nAP after calling ieee80211_restart_hw().(CVE-2023-52595)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: s390: fix setting of fpc register\r\n\r\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\r\n\r\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\r\n\r\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\r\n\r\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/ptrace: handle setting of fpc register correctly\r\n\r\nIf the content of the floating point control (fpc) register of a traced\nprocess is modified with the ptrace interface the new value is tested for\nvalidity by temporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the tracing process:\nif an interrupt happens while the value is temporarily loaded into the\nfpc register, and within interrupt context floating point or vector\nregisters are used, the current fp/vx registers are saved with\nsave_fpu_regs() assuming they belong to user space and will be loaded into\nfp/vx registers when returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space fpc register value, however\nit will be discarded, when returning to user space.\r\n\r\nIn result the tracer will incorrectly continue to run with the value that\nwas supposed to be used for the traced process.\r\n\r\nFix this by saving fpu register contents with save_fpu_regs() before using\ntest_fp_ctl().(CVE-2023-52598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: avoid online resizing failures due to oversized flex bg\r\n\r\nWhen we online resize an ext4 filesystem with a oversized flexbg_size,\r\n\r\n     mkfs.ext4 -F -G 67108864 $dev -b 4096 100M\n     mount $dev $dir\n     resize2fs $dev 16G\r\n\r\nthe following WARN_ON is triggered:\n==================================================================\nWARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550\nModules linked in: sg(E)\nCPU: 0 PID: 427 Comm: resize2fs Tainted: G  E  6.6.0-rc5+ #314\nRIP: 0010:__alloc_pages+0x411/0x550\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __kmalloc_large_node+0xa2/0x200\n __kmalloc+0x16e/0x290\n ext4_resize_fs+0x481/0xd80\n __ext4_ioctl+0x1616/0x1d90\n ext4_ioctl+0x12/0x20\n __x64_sys_ioctl+0xf0/0x150\n do_syscall_64+0x3b/0x90\n==================================================================\r\n\r\nThis is because flexbg_size is too large and the size of the new_group_data\narray to be allocated exceeds MAX_ORDER. Currently, the minimum value of\nMAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding\nmaximum number of groups that can be allocated is:\r\n\r\n (PAGE_SIZE \u0026lt;\u0026lt; MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845\r\n\r\nAnd the value that is down-aligned to the power of 2 is 16384. Therefore,\nthis value is defined as MAX_RESIZE_BG, and the number of groups added\neach time does not exceed this value during resizing, and is added multiple\ntimes to complete the online resizing. The difference is that the metadata\nin a flex_bg may be more dispersed.(CVE-2023-52622)","status":"published","published":"2024-04-19T11:06:55Z","modified":"2026-08-18T01:18:25.302720118Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.095407Z"},{"id":"OESA-2024-1485","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix another memory leak in error handling paths\r\n\r\nMemory allocated by \u0026apos;vmbus_alloc_ring()\u0026apos; at the beginning of the probe\nfunction is never freed in the error handling path.\r\n\r\nAdd the missing \u0026apos;vmbus_free_ring()\u0026apos; call.\r\n\r\nNote that it is already freed in the .remove function.(CVE-2021-47070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nasix: fix uninit-value in asix_mdio_read()\r\n\r\nasix_read_cmd() may read less than sizeof(smsr) bytes and in this case\nsmsr will be uninitialized.\r\n\r\nFail log:\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\nBUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\n asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nEDAC/thunderx: Fix possible out-of-bounds string access\r\n\r\nEnabling -Wstringop-overflow globally exposes a warning for a common bug\nin the usage of strncat():\r\n\r\n  drivers/edac/thunderx_edac.c: In function \u0026apos;thunderx_ocx_com_threaded_isr\u0026apos;:\n  drivers/edac/thunderx_edac.c:1136:17: error: \u0026apos;strncat\u0026apos; specified bound 1024 equals destination size [-Werror=stringop-overflow=]\n   1136 |                 strncat(msg, other, OCX_MESSAGE_SIZE);\n        |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n   ...\n   1145 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\n   ...\n   1150 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\r\n\r\n   ...\r\n\r\nApparently the author of this driver expected strncat() to behave the\nway that strlcat() does, which uses the size of the destination buffer\nas its third argument rather than the length of the source buffer. The\nresult is that there is no check on the size of the allocated buffer.\r\n\r\nChange it to strlcat().\r\n\r\n  [ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nInput: powermate - fix use-after-free in powermate_config_complete\r\n\r\nsyzbot has found a use-after-free bug [1] in the powermate driver. This\nhappens when the device is disconnected, which leads to a memory free from\nthe powermate_device struct.  When an asynchronous control message\ncompletes after the kfree and its callback is invoked, the lock does not\nexist anymore and hence the bug.\r\n\r\nUse usb_kill_urb() on pm-\u0026gt;config to cancel any in-progress requests upon\ndevice disconnection.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command\r\n\r\nTags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed\nwhen we receive the response.(CVE-2023-52500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: assert requested protocol is valid\r\n\r\nThe protocol is used in a bit mask to determine if the protocol is\nsupported. Assert the provided protocol is less than the maximum\ndefined so it doesn\u0026apos;t potentially perform a shift-out-of-bounds and\nprovide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nieee802154: ca8210: Fix a potential UAF in ca8210_probe\r\n\r\nIf of_clk_add_provider() fails in ca8210_register_ext_clock(),\nit calls clk_unregister() to release priv-\u0026gt;clk and returns an\nerror. However, the caller ca8210_probe() then calls ca8210_remove(),\nwhere priv-\u0026gt;clk is freed again in ca8210_unregister_ext_clock(). In\nthis case, a use-after-free may happen in the second time we call\nclk_unregister().\r\n\r\nFix this by removing the first clk_unregister(). Also, priv-\u0026gt;clk could\nbe an error code on failure of clk_register_fixed_rate(). Use\nIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/srp: Do not call scsi_done() from srp_abort()\r\n\r\nAfter scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler\ncallback, it performs one of the following actions:\n* Call scsi_queue_insert().\n* Call scsi_finish_command().\n* Call scsi_eh_scmd_add().\nHence, SCSI abort handlers must not call scsi_done(). Otherwise all\nthe above actions would trigger a use-after-free. Hence remove the\nscsi_done() call from srp_abort(). Keep the srp_free_req() call\nbefore returning SUCCESS because we may not see the command again if\nSUCCESS is returned.(CVE-2023-52515)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-debug: don\u0026apos;t call __dma_entry_alloc_check_leak() under free_entries_lock\r\n\r\n__dma_entry_alloc_check_leak() calls into printk -\u0026gt; serial console\noutput (qcom geni) and grabs port-\u0026gt;lock under free_entries_lock\nspin lock, which is a reverse locking dependency chain as qcom_geni\nIRQ handler can call into dma-debug code and grab free_entries_lock\nunder port-\u0026gt;lock.\r\n\r\nMove __dma_entry_alloc_check_leak() call out of free_entries_lock\nscope so that we don\u0026apos;t acquire serial console\u0026apos;s port-\u0026gt;lock under it.\r\n\r\nTrimmed-down lockdep splat:\r\n\r\n The existing dependency chain (in reverse order) is:\r\n\r\n               -\u0026gt; #2 (free_entries_lock){-.-.}-{2:2}:\n        _raw_spin_lock_irqsave+0x60/0x80\n        dma_entry_alloc+0x38/0x110\n        debug_dma_map_page+0x60/0xf8\n        dma_map_page_attrs+0x1e0/0x230\n        dma_map_single_attrs.constprop.0+0x6c/0xc8\n        geni_se_rx_dma_prep+0x40/0xcc\n        qcom_geni_serial_isr+0x310/0x510\n        __handle_irq_event_percpu+0x110/0x244\n        handle_irq_event_percpu+0x20/0x54\n        handle_irq_event+0x50/0x88\n        handle_fasteoi_irq+0xa4/0xcc\n        handle_irq_desc+0x28/0x40\n        generic_handle_domain_irq+0x24/0x30\n        gic_handle_irq+0xc4/0x148\n        do_interrupt_handler+0xa4/0xb0\n        el1_interrupt+0x34/0x64\n        el1h_64_irq_handler+0x18/0x24\n        el1h_64_irq+0x64/0x68\n        arch_local_irq_enable+0x4/0x8\n        ____do_softirq+0x18/0x24\n        ...\r\n\r\n               -\u0026gt; #1 (\u0026amp;port_lock_key){-.-.}-{2:2}:\n        _raw_spin_lock_irqsave+0x60/0x80\n        qcom_geni_serial_console_write+0x184/0x1dc\n        console_flush_all+0x344/0x454\n        console_unlock+0x94/0xf0\n        vprintk_emit+0x238/0x24c\n        vprintk_default+0x3c/0x48\n        vprintk+0xb4/0xbc\n        _printk+0x68/0x90\n        register_console+0x230/0x38c\n        uart_add_one_port+0x338/0x494\n        qcom_geni_serial_probe+0x390/0x424\n        platform_probe+0x70/0xc0\n        really_probe+0x148/0x280\n        __driver_probe_device+0xfc/0x114\n        driver_probe_device+0x44/0x100\n        __device_attach_driver+0x64/0xdc\n        bus_for_each_drv+0xb0/0xd8\n        __device_attach+0xe4/0x140\n        device_initial_probe+0x1c/0x28\n        bus_probe_device+0x44/0xb0\n        device_add+0x538/0x668\n        of_device_add+0x44/0x50\n        of_platform_device_create_pdata+0x94/0xc8\n        of_platform_bus_create+0x270/0x304\n        of_platform_populate+0xac/0xc4\n        devm_of_platform_populate+0x60/0xac\n        geni_se_probe+0x154/0x160\n        platform_probe+0x70/0xc0\n        ...\r\n\r\n               -\u0026gt; #0 (console_owner){-...}-{0:0}:\n        __lock_acquire+0xdf8/0x109c\n        lock_acquire+0x234/0x284\n        console_flush_all+0x330/0x454\n        console_unlock+0x94/0xf0\n        vprintk_emit+0x238/0x24c\n        vprintk_default+0x3c/0x48\n        vprintk+0xb4/0xbc\n        _printk+0x68/0x90\n        dma_entry_alloc+0xb4/0x110\n        debug_dma_map_sg+0xdc/0x2f8\n        __dma_map_sg_attrs+0xac/0xe4\n        dma_map_sgtable+0x30/0x4c\n        get_pages+0x1d4/0x1e4 [msm]\n        msm_gem_pin_pages_locked+0x38/0xac [msm]\n        msm_gem_pin_vma_locked+0x58/0x88 [msm]\n        msm_ioctl_gem_submit+0xde4/0x13ac [msm]\n        drm_ioctl_kernel+0xe0/0x15c\n        drm_ioctl+0x2e8/0x3f4\n        vfs_ioctl+0x30/0x50\n        ...\r\n\r\n Chain exists of:\n   console_owner --\u0026gt; \u0026amp;port_lock_key --\u0026gt; free_entries_lock\r\n\r\n  Possible unsafe locking scenario:\r\n\r\n        CPU0                    CPU1\n        ----                    ----\n   lock(free_entries_lock);\n                                lock(\u0026amp;port_lock_key);\n                                lock(free_entries_lock);\n   lock(console_owner);\r\n\r\n                *** DEADLOCK ***\r\n\r\n Call trace:\n  dump_backtrace+0xb4/0xf0\n  show_stack+0x20/0x30\n  dump_stack_lvl+0x60/0x84\n  dump_stack+0x18/0x24\n  print_circular_bug+0x1cc/0x234\n  check_noncircular+0x78/0xac\n  __lock_acquire+0xdf8/0x109c\n  lock_acquire+0x234/0x284\n  console_flush_all+0x330/0x454\n  consol\n---truncated---(CVE-2023-52516)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix possible store tearing in neigh_periodic_work()\r\n\r\nWhile looking at a related syzbot report involving neigh_periodic_work(),\nI found that I forgot to add an annotation when deleting an\nRCU protected item from a list.\r\n\r\nReaders use rcu_deference(*np), we need to use either\nrcu_assign_pointer() or WRITE_ONCE() on writer side\nto prevent store tearing.\r\n\r\nI use rcu_assign_pointer() to have lockdep support,\nthis was the choice made in neigh_flush_dev().(CVE-2023-52522)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: fix potential key use-after-free\r\n\r\nWhen ieee80211_key_link() is called by ieee80211_gtk_rekey_add()\nbut returns 0 due to KRACK protection (identical key reinstall),\nieee80211_gtk_rekey_add() will still return a pointer into the\nkey, in a potential use-after-free. This normally doesn\u0026apos;t happen\nsince it\u0026apos;s only called by iwlwifi in case of WoWLAN rekey offload\nwhich has its own KRACK protection, but still better to fix, do\nthat by returning an error code and converting that to success on\nthe cfg80211 boundary only, leaving the error for bad callers of\nieee80211_gtk_rekey_add().(CVE-2023-52530)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions()\r\n\r\nWhen CONFIG_DAMON_VADDR_KUNIT_TEST=y and making CONFIG_DEBUG_KMEMLEAK=y\nand CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN=y, the below memory leak is detected.\r\n\r\nSince commit 9f86d624292c (\u0026quot;mm/damon/vaddr-test: remove unnecessary\nvariables\u0026quot;), the damon_destroy_ctx() is removed, but still call\ndamon_new_target() and damon_new_region(), the damon_region which is\nallocated by kmem_cache_alloc() in damon_new_region() and the damon_target\nwhich is allocated by kmalloc in damon_new_target() are not freed.  And\nthe damon_region which is allocated in damon_new_region() in\ndamon_set_regions() is also not freed.\r\n\r\nSo use damon_destroy_target to free all the damon_regions and damon_target.\r\n\r\n    unreferenced object 0xffff888107c9a940 (size 64):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1069, jiffies 4294670592 (age 732.761s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 06 00 00 00 6b 6b 6b 6b  ............kkkk\n        60 c7 9c 07 81 88 ff ff f8 cb 9c 07 81 88 ff ff  `...............\n      backtrace:\n        [\u0026lt;ffffffff817e0167\u0026gt;] kmalloc_trace+0x27/0xa0\n        [\u0026lt;ffffffff819c11cf\u0026gt;] damon_new_target+0x3f/0x1b0\n        [\u0026lt;ffffffff819c7d55\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0x95/0x3e0\n        [\u0026lt;ffffffff819c82be\u0026gt;] damon_test_apply_three_regions1+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff8881079cc740 (size 56):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1069, jiffies 4294670592 (age 732.761s)\n      hex dump (first 32 bytes):\n        05 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00  ................\n        6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 6b 6b 6b 6b  kkkkkkkk....kkkk\n      backtrace:\n        [\u0026lt;ffffffff819bc492\u0026gt;] damon_new_region+0x22/0x1c0\n        [\u0026lt;ffffffff819c7d91\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0xd1/0x3e0\n        [\u0026lt;ffffffff819c82be\u0026gt;] damon_test_apply_three_regions1+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff888107c9ac40 (size 64):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1071, jiffies 4294670595 (age 732.843s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 06 00 00 00 6b 6b 6b 6b  ............kkkk\n        a0 cc 9c 07 81 88 ff ff 78 a1 76 07 81 88 ff ff  ........x.v.....\n      backtrace:\n        [\u0026lt;ffffffff817e0167\u0026gt;] kmalloc_trace+0x27/0xa0\n        [\u0026lt;ffffffff819c11cf\u0026gt;] damon_new_target+0x3f/0x1b0\n        [\u0026lt;ffffffff819c7d55\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0x95/0x3e0\n        [\u0026lt;ffffffff819c851e\u0026gt;] damon_test_apply_three_regions2+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff8881079ccc80 (size 56):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1071, jiffies 4294670595 (age 732.843s)\n      hex dump (first 32 bytes):\n        05 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00  ................\n        6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 6b 6b 6b 6b  kkkkkkkk....kkkk\n      backtrace:\n        [\u0026lt;ffffffff819bc492\u0026gt;] damon_new_region+0x22/0x1c0\n        [\u0026lt;ffffffff819c7d91\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0xd1/0x3e0\n        [\u0026lt;ffffffff819c851e\u0026gt;] damon_test_apply_three_regions2+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffff\n---truncated---(CVE-2023-52560)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\narm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved\r\n\r\nAdding a reserved memory region for the framebuffer memory\n(the splash memory region set up by the bootloader).\r\n\r\nIt fixes a kernel panic (arm-smmu: Unhandled context fault\nat this particular memory region) reported on DB845c running\nv5.10.y.(CVE-2023-52561)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential use after free in nilfs_gccache_submit_read_data()\r\n\r\nIn nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the\nreference count of bh when the call to nilfs_dat_translate() fails.  If\nthe reference count hits 0 and its owner page gets unlocked, bh may be\nfreed.  However, bh-\u0026gt;b_page is dereferenced to put the page after that,\nwhich may result in a use-after-free bug.  This patch moves the release\noperation after unlocking and putting the page.\r\n\r\nNOTE: The function in question is only called in GC, and in combination\nwith current userland tools, address translation using DAT does not occur\nin that function, so the code path that causes this issue will not be\nexecuted.  However, it is possible to run that code path by intentionally\nmodifying the userland GC library or by calling the GC ioctl directly.\r\n\r\n[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: rds: Fix possible NULL-pointer dereference\r\n\r\nIn rds_rdma_cm_event_handler_cmn() check, if conn pointer exists\nbefore dereferencing it as rdma_set_service_type() argument\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2023-52573)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: use DEV_STATS_INC()\r\n\r\nsyzbot/KCSAN reported data-races in br_handle_frame_finish() [1]\nThis function can run from multiple cpus without mutual exclusion.\r\n\r\nAdopt SMP safe DEV_STATS_INC() to update dev-\u0026gt;stats fields.\r\n\r\nHandles updates to dev-\u0026gt;stats.tx_dropped while we are at it.\r\n\r\n[1]\nBUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\nrun_ksoftirqd+0x17/0x20 kernel/softirq.c:921\nsmpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\ndo_softirq+0x5e/0x90 kernel/softirq.c:454\n__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381\n__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210\nspin_unlock_bh include/linux/spinlock.h:396 [inline]\nbatadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356\nbatadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560\nprocess_one_work kernel/workqueue.c:2630 [inline]\nprocess_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703\nworker_thread+0x525/0x730 kernel/workqueue.c:2784\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nvalue changed: 0x00000000000d7190 -\u0026gt; 0x00000000000d7191\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nceph: fix deadlock or deadcode of misusing dget()\r\n\r\nThe lock order is incorrect between denty and its parent, we should\nalways make sure that the parent get the lock first.\r\n\r\nBut since this deadcode is never used and the parent dir will always\nbe set from the callers, let\u0026apos;s just remove it.(CVE-2023-52583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/ipoib: Fix mcast list locking\r\n\r\nReleasing the `priv-\u0026gt;lock` while iterating the `priv-\u0026gt;multicast_list` in\n`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to\nremove the items while in the middle of iteration. If the mcast is removed\nwhile the lock was dropped, the for loop spins forever resulting in a hard\nlockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):\r\n\r\n    Task A (kworker/u72:2 below)       | Task B (kworker/u72:0 below)\n    -----------------------------------+-----------------------------------\n    ipoib_mcast_join_task(work)        | ipoib_ib_dev_flush_light(work)\n      spin_lock_irq(\u0026amp;priv-\u0026gt;lock)       | __ipoib_ib_dev_flush(priv, ...)\n      list_for_each_entry(mcast,       | ipoib_mcast_dev_flush(dev = priv-\u0026gt;dev)\n          \u0026amp;priv-\u0026gt;multicast_list, list) |\n        ipoib_mcast_join(dev, mcast)   |\n          spin_unlock_irq(\u0026amp;priv-\u0026gt;lock) |\n                                       |   spin_lock_irqsave(\u0026amp;priv-\u0026gt;lock, flags)\n                                       |   list_for_each_entry_safe(mcast, tmcast,\n                                       |                  \u0026amp;priv-\u0026gt;multicast_list, list)\n                                       |     list_del(\u0026amp;mcast-\u0026gt;list);\n                                       |     list_add_tail(\u0026amp;mcast-\u0026gt;list, \u0026amp;remove_list)\n                                       |   spin_unlock_irqrestore(\u0026amp;priv-\u0026gt;lock, flags)\n          spin_lock_irq(\u0026amp;priv-\u0026gt;lock)   |\n                                       |   ipoib_mcast_remove_list(\u0026amp;remove_list)\n   (Here, `mcast` is no longer on the  |     list_for_each_entry_safe(mcast, tmcast,\n    `priv-\u0026gt;multicast_list` and we keep |                            remove_list, list)\n    spinning on the `remove_list` of   |  \u0026gt;\u0026gt;\u0026gt;  wait_for_completion(\u0026amp;mcast-\u0026gt;done)\n    the other thread which is blocked  |\n    and the list is still valid on     |\n    it\u0026apos;s stack.)\r\n\r\nFix this by keeping the lock held and changing to GFP_ATOMIC to prevent\neventual sleeps.\nUnfortunately we could not reproduce the lockup and confirm this fix but\nbased on the code review I think this fix should address such lockups.\r\n\r\ncrash\u0026gt; bc 31\nPID: 747      TASK: ff1c6a1a007e8000  CPU: 31   COMMAND: \u0026quot;kworker/u72:2\u0026quot;\n--\n    [exception RIP: ipoib_mcast_join_task+0x1b1]\n    RIP: ffffffffc0944ac1  RSP: ff646f199a8c7e00  RFLAGS: 00000002\n    RAX: 0000000000000000  RBX: ff1c6a1a04dc82f8  RCX: 0000000000000000\n                                  work (\u0026amp;priv-\u0026gt;mcast_task{,.work})\n    RDX: ff1c6a192d60ac68  RSI: 0000000000000286  RDI: ff1c6a1a04dc8000\n           \u0026amp;mcast-\u0026gt;list\n    RBP: ff646f199a8c7e90   R8: ff1c699980019420   R9: ff1c6a1920c9a000\n    R10: ff646f199a8c7e00  R11: ff1c6a191a7d9800  R12: ff1c6a192d60ac00\n                                                         mcast\n    R13: ff1c6a1d82200000  R14: ff1c6a1a04dc8000  R15: ff1c6a1a04dc82d8\n           dev                    priv (\u0026amp;priv-\u0026gt;lock)     \u0026amp;priv-\u0026gt;multicast_list (aka head)\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n--- \u0026lt;NMI exception stack\u0026gt; ---\n #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]\n #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967\r\n\r\ncrash\u0026gt; rx ff646f199a8c7e68\nff646f199a8c7e68:  ff1c6a1a04dc82f8 \u0026lt;\u0026lt;\u0026lt; work = \u0026amp;priv-\u0026gt;mcast_task.work\r\n\r\ncrash\u0026gt; list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000\n(empty)\r\n\r\ncrash\u0026gt; ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000\n  mcast_task.work.func = 0xffffffffc0944910 \u0026lt;ipoib_mcast_join_task\u0026gt;,\n  mcast_mutex.owner.counter = 0xff1c69998efec000\r\n\r\ncrash\u0026gt; b 8\nPID: 8        TASK: ff1c69998efec000  CPU: 33   COMMAND: \u0026quot;kworker/u72:0\u0026quot;\n--\n #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646\n #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]\n #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]\n #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]\n #7 [ff\n---truncated---(CVE-2023-52587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()\r\n\r\nFix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug\noccurs when txs-\u0026gt;cnt, data from a URB provided by a USB device, is\nbigger than the size of the array txs-\u0026gt;txstatus, which is\nHTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug\nhandling code after the check. Make the function return if that is the\ncase.\r\n\r\nFound by a modified version of syzkaller.\r\n\r\nUBSAN: array-index-out-of-bounds in htc_drv_txrx.c\nindex 13 is out of range for type \u0026apos;__wmi_event_txstatus [12]\u0026apos;\nCall Trace:\n ath9k_htc_txstatus\n ath9k_wmi_event_tasklet\n tasklet_action_common\n __do_softirq\n irq_exit_rxu\n sysvec_apic_timer_interrupt(CVE-2023-52594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rt2x00: restart beacon queue when hardware reset\r\n\r\nWhen a hardware reset is triggered, all registers are reset, so all\nqueues are forced to stop in hardware interface. However, mac80211\nwill not automatically stop the queue. If we don\u0026apos;t manually stop the\nbeacon queue, the queue will be deadlocked and unable to start again.\nThis patch fixes the issue where Apple devices cannot connect to the\nAP after calling ieee80211_restart_hw().(CVE-2023-52595)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: s390: fix setting of fpc register\r\n\r\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\r\n\r\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\r\n\r\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\r\n\r\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/ptrace: handle setting of fpc register correctly\r\n\r\nIf the content of the floating point control (fpc) register of a traced\nprocess is modified with the ptrace interface the new value is tested for\nvalidity by temporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the tracing process:\nif an interrupt happens while the value is temporarily loaded into the\nfpc register, and within interrupt context floating point or vector\nregisters are used, the current fp/vx registers are saved with\nsave_fpu_regs() assuming they belong to user space and will be loaded into\nfp/vx registers when returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space fpc register value, however\nit will be discarded, when returning to user space.\r\n\r\nIn result the tracer will incorrectly continue to run with the value that\nwas supposed to be used for the traced process.\r\n\r\nFix this by saving fpu register contents with save_fpu_regs() before using\ntest_fp_ctl().(CVE-2023-52598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: avoid online resizing failures due to oversized flex bg\r\n\r\nWhen we online resize an ext4 filesystem with a oversized flexbg_size,\r\n\r\n     mkfs.ext4 -F -G 67108864 $dev -b 4096 100M\n     mount $dev $dir\n     resize2fs $dev 16G\r\n\r\nthe following WARN_ON is triggered:\n==================================================================\nWARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550\nModules linked in: sg(E)\nCPU: 0 PID: 427 Comm: resize2fs Tainted: G  E  6.6.0-rc5+ #314\nRIP: 0010:__alloc_pages+0x411/0x550\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __kmalloc_large_node+0xa2/0x200\n __kmalloc+0x16e/0x290\n ext4_resize_fs+0x481/0xd80\n __ext4_ioctl+0x1616/0x1d90\n ext4_ioctl+0x12/0x20\n __x64_sys_ioctl+0xf0/0x150\n do_syscall_64+0x3b/0x90\n==================================================================\r\n\r\nThis is because flexbg_size is too large and the size of the new_group_data\narray to be allocated exceeds MAX_ORDER. Currently, the minimum value of\nMAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding\nmaximum number of groups that can be allocated is:\r\n\r\n (PAGE_SIZE \u0026lt;\u0026lt; MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845\r\n\r\nAnd the value that is down-aligned to the power of 2 is 16384. Therefore,\nthis value is defined as MAX_RESIZE_BG, and the number of groups added\neach time does not exceed this value during resizing, and is added multiple\ntimes to complete the online resizing. The difference is that the metadata\nin a flex_bg may be more dispersed.(CVE-2023-52622)","status":"published","published":"2024-04-19T11:06:55Z","modified":"2026-08-18T01:18:25.307614135Z","cvss":[{"version":"3.1","score":6.7,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","level":"medium"}],"updated_at":"2026-11-02T15:52:41.095407Z"},{"id":"OESA-2024-1486","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix another memory leak in error handling paths\r\n\r\nMemory allocated by \u0026apos;vmbus_alloc_ring()\u0026apos; at the beginning of the probe\nfunction is never freed in the error handling path.\r\n\r\nAdd the missing \u0026apos;vmbus_free_ring()\u0026apos; call.\r\n\r\nNote that it is already freed in the .remove function.(CVE-2021-47070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nasix: fix uninit-value in asix_mdio_read()\r\n\r\nasix_read_cmd() may read less than sizeof(smsr) bytes and in this case\nsmsr will be uninitialized.\r\n\r\nFail log:\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\nBUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\n asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nEDAC/thunderx: Fix possible out-of-bounds string access\r\n\r\nEnabling -Wstringop-overflow globally exposes a warning for a common bug\nin the usage of strncat():\r\n\r\n  drivers/edac/thunderx_edac.c: In function \u0026apos;thunderx_ocx_com_threaded_isr\u0026apos;:\n  drivers/edac/thunderx_edac.c:1136:17: error: \u0026apos;strncat\u0026apos; specified bound 1024 equals destination size [-Werror=stringop-overflow=]\n   1136 |                 strncat(msg, other, OCX_MESSAGE_SIZE);\n        |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n   ...\n   1145 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\n   ...\n   1150 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\r\n\r\n   ...\r\n\r\nApparently the author of this driver expected strncat() to behave the\nway that strlcat() does, which uses the size of the destination buffer\nas its third argument rather than the length of the source buffer. The\nresult is that there is no check on the size of the allocated buffer.\r\n\r\nChange it to strlcat().\r\n\r\n  [ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nInput: powermate - fix use-after-free in powermate_config_complete\r\n\r\nsyzbot has found a use-after-free bug [1] in the powermate driver. This\nhappens when the device is disconnected, which leads to a memory free from\nthe powermate_device struct.  When an asynchronous control message\ncompletes after the kfree and its callback is invoked, the lock does not\nexist anymore and hence the bug.\r\n\r\nUse usb_kill_urb() on pm-\u0026gt;config to cancel any in-progress requests upon\ndevice disconnection.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command\r\n\r\nTags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed\nwhen we receive the response.(CVE-2023-52500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: assert requested protocol is valid\r\n\r\nThe protocol is used in a bit mask to determine if the protocol is\nsupported. Assert the provided protocol is less than the maximum\ndefined so it doesn\u0026apos;t potentially perform a shift-out-of-bounds and\nprovide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nieee802154: ca8210: Fix a potential UAF in ca8210_probe\r\n\r\nIf of_clk_add_provider() fails in ca8210_register_ext_clock(),\nit calls clk_unregister() to release priv-\u0026gt;clk and returns an\nerror. However, the caller ca8210_probe() then calls ca8210_remove(),\nwhere priv-\u0026gt;clk is freed again in ca8210_unregister_ext_clock(). In\nthis case, a use-after-free may happen in the second time we call\nclk_unregister().\r\n\r\nFix this by removing the first clk_unregister(). Also, priv-\u0026gt;clk could\nbe an error code on failure of clk_register_fixed_rate(). Use\nIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/srp: Do not call scsi_done() from srp_abort()\r\n\r\nAfter scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler\ncallback, it performs one of the following actions:\n* Call scsi_queue_insert().\n* Call scsi_finish_command().\n* Call scsi_eh_scmd_add().\nHence, SCSI abort handlers must not call scsi_done(). Otherwise all\nthe above actions would trigger a use-after-free. Hence remove the\nscsi_done() call from srp_abort(). Keep the srp_free_req() call\nbefore returning SUCCESS because we may not see the command again if\nSUCCESS is returned.(CVE-2023-52515)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-debug: don\u0026apos;t call __dma_entry_alloc_check_leak() under free_entries_lock\r\n\r\n__dma_entry_alloc_check_leak() calls into printk -\u0026gt; serial console\noutput (qcom geni) and grabs port-\u0026gt;lock under free_entries_lock\nspin lock, which is a reverse locking dependency chain as qcom_geni\nIRQ handler can call into dma-debug code and grab free_entries_lock\nunder port-\u0026gt;lock.\r\n\r\nMove __dma_entry_alloc_check_leak() call out of free_entries_lock\nscope so that we don\u0026apos;t acquire serial console\u0026apos;s port-\u0026gt;lock under it.\r\n\r\nTrimmed-down lockdep splat:\r\n\r\n The existing dependency chain (in reverse order) is:\r\n\r\n               -\u0026gt; #2 (free_entries_lock){-.-.}-{2:2}:\n        _raw_spin_lock_irqsave+0x60/0x80\n        dma_entry_alloc+0x38/0x110\n        debug_dma_map_page+0x60/0xf8\n        dma_map_page_attrs+0x1e0/0x230\n        dma_map_single_attrs.constprop.0+0x6c/0xc8\n        geni_se_rx_dma_prep+0x40/0xcc\n        qcom_geni_serial_isr+0x310/0x510\n        __handle_irq_event_percpu+0x110/0x244\n        handle_irq_event_percpu+0x20/0x54\n        handle_irq_event+0x50/0x88\n        handle_fasteoi_irq+0xa4/0xcc\n        handle_irq_desc+0x28/0x40\n        generic_handle_domain_irq+0x24/0x30\n        gic_handle_irq+0xc4/0x148\n        do_interrupt_handler+0xa4/0xb0\n        el1_interrupt+0x34/0x64\n        el1h_64_irq_handler+0x18/0x24\n        el1h_64_irq+0x64/0x68\n        arch_local_irq_enable+0x4/0x8\n        ____do_softirq+0x18/0x24\n        ...\r\n\r\n               -\u0026gt; #1 (\u0026amp;port_lock_key){-.-.}-{2:2}:\n        _raw_spin_lock_irqsave+0x60/0x80\n        qcom_geni_serial_console_write+0x184/0x1dc\n        console_flush_all+0x344/0x454\n        console_unlock+0x94/0xf0\n        vprintk_emit+0x238/0x24c\n        vprintk_default+0x3c/0x48\n        vprintk+0xb4/0xbc\n        _printk+0x68/0x90\n        register_console+0x230/0x38c\n        uart_add_one_port+0x338/0x494\n        qcom_geni_serial_probe+0x390/0x424\n        platform_probe+0x70/0xc0\n        really_probe+0x148/0x280\n        __driver_probe_device+0xfc/0x114\n        driver_probe_device+0x44/0x100\n        __device_attach_driver+0x64/0xdc\n        bus_for_each_drv+0xb0/0xd8\n        __device_attach+0xe4/0x140\n        device_initial_probe+0x1c/0x28\n        bus_probe_device+0x44/0xb0\n        device_add+0x538/0x668\n        of_device_add+0x44/0x50\n        of_platform_device_create_pdata+0x94/0xc8\n        of_platform_bus_create+0x270/0x304\n        of_platform_populate+0xac/0xc4\n        devm_of_platform_populate+0x60/0xac\n        geni_se_probe+0x154/0x160\n        platform_probe+0x70/0xc0\n        ...\r\n\r\n               -\u0026gt; #0 (console_owner){-...}-{0:0}:\n        __lock_acquire+0xdf8/0x109c\n        lock_acquire+0x234/0x284\n        console_flush_all+0x330/0x454\n        console_unlock+0x94/0xf0\n        vprintk_emit+0x238/0x24c\n        vprintk_default+0x3c/0x48\n        vprintk+0xb4/0xbc\n        _printk+0x68/0x90\n        dma_entry_alloc+0xb4/0x110\n        debug_dma_map_sg+0xdc/0x2f8\n        __dma_map_sg_attrs+0xac/0xe4\n        dma_map_sgtable+0x30/0x4c\n        get_pages+0x1d4/0x1e4 [msm]\n        msm_gem_pin_pages_locked+0x38/0xac [msm]\n        msm_gem_pin_vma_locked+0x58/0x88 [msm]\n        msm_ioctl_gem_submit+0xde4/0x13ac [msm]\n        drm_ioctl_kernel+0xe0/0x15c\n        drm_ioctl+0x2e8/0x3f4\n        vfs_ioctl+0x30/0x50\n        ...\r\n\r\n Chain exists of:\n   console_owner --\u0026gt; \u0026amp;port_lock_key --\u0026gt; free_entries_lock\r\n\r\n  Possible unsafe locking scenario:\r\n\r\n        CPU0                    CPU1\n        ----                    ----\n   lock(free_entries_lock);\n                                lock(\u0026amp;port_lock_key);\n                                lock(free_entries_lock);\n   lock(console_owner);\r\n\r\n                *** DEADLOCK ***\r\n\r\n Call trace:\n  dump_backtrace+0xb4/0xf0\n  show_stack+0x20/0x30\n  dump_stack_lvl+0x60/0x84\n  dump_stack+0x18/0x24\n  print_circular_bug+0x1cc/0x234\n  check_noncircular+0x78/0xac\n  __lock_acquire+0xdf8/0x109c\n  lock_acquire+0x234/0x284\n  console_flush_all+0x330/0x454\n  consol\n---truncated---(CVE-2023-52516)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix possible store tearing in neigh_periodic_work()\r\n\r\nWhile looking at a related syzbot report involving neigh_periodic_work(),\nI found that I forgot to add an annotation when deleting an\nRCU protected item from a list.\r\n\r\nReaders use rcu_deference(*np), we need to use either\nrcu_assign_pointer() or WRITE_ONCE() on writer side\nto prevent store tearing.\r\n\r\nI use rcu_assign_pointer() to have lockdep support,\nthis was the choice made in neigh_flush_dev().(CVE-2023-52522)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: fix potential key use-after-free\r\n\r\nWhen ieee80211_key_link() is called by ieee80211_gtk_rekey_add()\nbut returns 0 due to KRACK protection (identical key reinstall),\nieee80211_gtk_rekey_add() will still return a pointer into the\nkey, in a potential use-after-free. This normally doesn\u0026apos;t happen\nsince it\u0026apos;s only called by iwlwifi in case of WoWLAN rekey offload\nwhich has its own KRACK protection, but still better to fix, do\nthat by returning an error code and converting that to success on\nthe cfg80211 boundary only, leaving the error for bad callers of\nieee80211_gtk_rekey_add().(CVE-2023-52530)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions()\r\n\r\nWhen CONFIG_DAMON_VADDR_KUNIT_TEST=y and making CONFIG_DEBUG_KMEMLEAK=y\nand CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN=y, the below memory leak is detected.\r\n\r\nSince commit 9f86d624292c (\u0026quot;mm/damon/vaddr-test: remove unnecessary\nvariables\u0026quot;), the damon_destroy_ctx() is removed, but still call\ndamon_new_target() and damon_new_region(), the damon_region which is\nallocated by kmem_cache_alloc() in damon_new_region() and the damon_target\nwhich is allocated by kmalloc in damon_new_target() are not freed.  And\nthe damon_region which is allocated in damon_new_region() in\ndamon_set_regions() is also not freed.\r\n\r\nSo use damon_destroy_target to free all the damon_regions and damon_target.\r\n\r\n    unreferenced object 0xffff888107c9a940 (size 64):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1069, jiffies 4294670592 (age 732.761s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 06 00 00 00 6b 6b 6b 6b  ............kkkk\n        60 c7 9c 07 81 88 ff ff f8 cb 9c 07 81 88 ff ff  `...............\n      backtrace:\n        [\u0026lt;ffffffff817e0167\u0026gt;] kmalloc_trace+0x27/0xa0\n        [\u0026lt;ffffffff819c11cf\u0026gt;] damon_new_target+0x3f/0x1b0\n        [\u0026lt;ffffffff819c7d55\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0x95/0x3e0\n        [\u0026lt;ffffffff819c82be\u0026gt;] damon_test_apply_three_regions1+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff8881079cc740 (size 56):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1069, jiffies 4294670592 (age 732.761s)\n      hex dump (first 32 bytes):\n        05 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00  ................\n        6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 6b 6b 6b 6b  kkkkkkkk....kkkk\n      backtrace:\n        [\u0026lt;ffffffff819bc492\u0026gt;] damon_new_region+0x22/0x1c0\n        [\u0026lt;ffffffff819c7d91\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0xd1/0x3e0\n        [\u0026lt;ffffffff819c82be\u0026gt;] damon_test_apply_three_regions1+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff888107c9ac40 (size 64):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1071, jiffies 4294670595 (age 732.843s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 06 00 00 00 6b 6b 6b 6b  ............kkkk\n        a0 cc 9c 07 81 88 ff ff 78 a1 76 07 81 88 ff ff  ........x.v.....\n      backtrace:\n        [\u0026lt;ffffffff817e0167\u0026gt;] kmalloc_trace+0x27/0xa0\n        [\u0026lt;ffffffff819c11cf\u0026gt;] damon_new_target+0x3f/0x1b0\n        [\u0026lt;ffffffff819c7d55\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0x95/0x3e0\n        [\u0026lt;ffffffff819c851e\u0026gt;] damon_test_apply_three_regions2+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff8881079ccc80 (size 56):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1071, jiffies 4294670595 (age 732.843s)\n      hex dump (first 32 bytes):\n        05 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00  ................\n        6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 6b 6b 6b 6b  kkkkkkkk....kkkk\n      backtrace:\n        [\u0026lt;ffffffff819bc492\u0026gt;] damon_new_region+0x22/0x1c0\n        [\u0026lt;ffffffff819c7d91\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0xd1/0x3e0\n        [\u0026lt;ffffffff819c851e\u0026gt;] damon_test_apply_three_regions2+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffff\n---truncated---(CVE-2023-52560)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\narm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved\r\n\r\nAdding a reserved memory region for the framebuffer memory\n(the splash memory region set up by the bootloader).\r\n\r\nIt fixes a kernel panic (arm-smmu: Unhandled context fault\nat this particular memory region) reported on DB845c running\nv5.10.y.(CVE-2023-52561)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential use after free in nilfs_gccache_submit_read_data()\r\n\r\nIn nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the\nreference count of bh when the call to nilfs_dat_translate() fails.  If\nthe reference count hits 0 and its owner page gets unlocked, bh may be\nfreed.  However, bh-\u0026gt;b_page is dereferenced to put the page after that,\nwhich may result in a use-after-free bug.  This patch moves the release\noperation after unlocking and putting the page.\r\n\r\nNOTE: The function in question is only called in GC, and in combination\nwith current userland tools, address translation using DAT does not occur\nin that function, so the code path that causes this issue will not be\nexecuted.  However, it is possible to run that code path by intentionally\nmodifying the userland GC library or by calling the GC ioctl directly.\r\n\r\n[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nx86/sgx: Resolves SECS reclaim vs. page fault for EAUG race\r\n\r\nThe SGX EPC reclaimer (ksgxd) may reclaim the SECS EPC page for an\nenclave and set secs.epc_page to NULL. The SECS page is used for EAUG\nand ELDU in the SGX page fault handler. However, the NULL check for\nsecs.epc_page is only done for ELDU, not EAUG before being used.\r\n\r\nFix this by doing the same NULL check and reloading of the SECS page as\nneeded for both EAUG and ELDU.\r\n\r\nThe SECS page holds global enclave metadata. It can only be reclaimed\nwhen there are no other enclave pages remaining. At that point,\nvirtually nothing can be done with the enclave until the SECS page is\npaged back in.\r\n\r\nAn enclave can not run nor generate page faults without a resident SECS\npage. But it is still possible for a #PF for a non-SECS page to race\nwith paging out the SECS page: when the last resident non-SECS page A\ntriggers a #PF in a non-resident page B, and then page A and the SECS\nboth are paged out before the #PF on B is handled.\r\n\r\nHitting this bug requires that race triggered with a #PF for EAUG.\nFollowing is a trace when it happens.\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nRIP: 0010:sgx_encl_eaug_page+0xc7/0x210\nCall Trace:\n ? __kmem_cache_alloc_node+0x16a/0x440\n ? xa_load+0x6e/0xa0\n sgx_vma_fault+0x119/0x230\n __do_fault+0x36/0x140\n do_fault+0x12f/0x400\n __handle_mm_fault+0x728/0x1110\n handle_mm_fault+0x105/0x310\n do_user_addr_fault+0x1ee/0x750\n ? __this_cpu_preempt_check+0x13/0x20\n exc_page_fault+0x76/0x180\n asm_exc_page_fault+0x27/0x30(CVE-2023-52568)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: rds: Fix possible NULL-pointer dereference\r\n\r\nIn rds_rdma_cm_event_handler_cmn() check, if conn pointer exists\nbefore dereferencing it as rdma_set_service_type() argument\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2023-52573)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: use DEV_STATS_INC()\r\n\r\nsyzbot/KCSAN reported data-races in br_handle_frame_finish() [1]\nThis function can run from multiple cpus without mutual exclusion.\r\n\r\nAdopt SMP safe DEV_STATS_INC() to update dev-\u0026gt;stats fields.\r\n\r\nHandles updates to dev-\u0026gt;stats.tx_dropped while we are at it.\r\n\r\n[1]\nBUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\nrun_ksoftirqd+0x17/0x20 kernel/softirq.c:921\nsmpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\ndo_softirq+0x5e/0x90 kernel/softirq.c:454\n__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381\n__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210\nspin_unlock_bh include/linux/spinlock.h:396 [inline]\nbatadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356\nbatadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560\nprocess_one_work kernel/workqueue.c:2630 [inline]\nprocess_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703\nworker_thread+0x525/0x730 kernel/workqueue.c:2784\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nvalue changed: 0x00000000000d7190 -\u0026gt; 0x00000000000d7191\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nceph: fix deadlock or deadcode of misusing dget()\r\n\r\nThe lock order is incorrect between denty and its parent, we should\nalways make sure that the parent get the lock first.\r\n\r\nBut since this deadcode is never used and the parent dir will always\nbe set from the callers, let\u0026apos;s just remove it.(CVE-2023-52583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/ipoib: Fix mcast list locking\r\n\r\nReleasing the `priv-\u0026gt;lock` while iterating the `priv-\u0026gt;multicast_list` in\n`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to\nremove the items while in the middle of iteration. If the mcast is removed\nwhile the lock was dropped, the for loop spins forever resulting in a hard\nlockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):\r\n\r\n    Task A (kworker/u72:2 below)       | Task B (kworker/u72:0 below)\n    -----------------------------------+-----------------------------------\n    ipoib_mcast_join_task(work)        | ipoib_ib_dev_flush_light(work)\n      spin_lock_irq(\u0026amp;priv-\u0026gt;lock)       | __ipoib_ib_dev_flush(priv, ...)\n      list_for_each_entry(mcast,       | ipoib_mcast_dev_flush(dev = priv-\u0026gt;dev)\n          \u0026amp;priv-\u0026gt;multicast_list, list) |\n        ipoib_mcast_join(dev, mcast)   |\n          spin_unlock_irq(\u0026amp;priv-\u0026gt;lock) |\n                                       |   spin_lock_irqsave(\u0026amp;priv-\u0026gt;lock, flags)\n                                       |   list_for_each_entry_safe(mcast, tmcast,\n                                       |                  \u0026amp;priv-\u0026gt;multicast_list, list)\n                                       |     list_del(\u0026amp;mcast-\u0026gt;list);\n                                       |     list_add_tail(\u0026amp;mcast-\u0026gt;list, \u0026amp;remove_list)\n                                       |   spin_unlock_irqrestore(\u0026amp;priv-\u0026gt;lock, flags)\n          spin_lock_irq(\u0026amp;priv-\u0026gt;lock)   |\n                                       |   ipoib_mcast_remove_list(\u0026amp;remove_list)\n   (Here, `mcast` is no longer on the  |     list_for_each_entry_safe(mcast, tmcast,\n    `priv-\u0026gt;multicast_list` and we keep |                            remove_list, list)\n    spinning on the `remove_list` of   |  \u0026gt;\u0026gt;\u0026gt;  wait_for_completion(\u0026amp;mcast-\u0026gt;done)\n    the other thread which is blocked  |\n    and the list is still valid on     |\n    it\u0026apos;s stack.)\r\n\r\nFix this by keeping the lock held and changing to GFP_ATOMIC to prevent\neventual sleeps.\nUnfortunately we could not reproduce the lockup and confirm this fix but\nbased on the code review I think this fix should address such lockups.\r\n\r\ncrash\u0026gt; bc 31\nPID: 747      TASK: ff1c6a1a007e8000  CPU: 31   COMMAND: \u0026quot;kworker/u72:2\u0026quot;\n--\n    [exception RIP: ipoib_mcast_join_task+0x1b1]\n    RIP: ffffffffc0944ac1  RSP: ff646f199a8c7e00  RFLAGS: 00000002\n    RAX: 0000000000000000  RBX: ff1c6a1a04dc82f8  RCX: 0000000000000000\n                                  work (\u0026amp;priv-\u0026gt;mcast_task{,.work})\n    RDX: ff1c6a192d60ac68  RSI: 0000000000000286  RDI: ff1c6a1a04dc8000\n           \u0026amp;mcast-\u0026gt;list\n    RBP: ff646f199a8c7e90   R8: ff1c699980019420   R9: ff1c6a1920c9a000\n    R10: ff646f199a8c7e00  R11: ff1c6a191a7d9800  R12: ff1c6a192d60ac00\n                                                         mcast\n    R13: ff1c6a1d82200000  R14: ff1c6a1a04dc8000  R15: ff1c6a1a04dc82d8\n           dev                    priv (\u0026amp;priv-\u0026gt;lock)     \u0026amp;priv-\u0026gt;multicast_list (aka head)\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n--- \u0026lt;NMI exception stack\u0026gt; ---\n #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]\n #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967\r\n\r\ncrash\u0026gt; rx ff646f199a8c7e68\nff646f199a8c7e68:  ff1c6a1a04dc82f8 \u0026lt;\u0026lt;\u0026lt; work = \u0026amp;priv-\u0026gt;mcast_task.work\r\n\r\ncrash\u0026gt; list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000\n(empty)\r\n\r\ncrash\u0026gt; ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000\n  mcast_task.work.func = 0xffffffffc0944910 \u0026lt;ipoib_mcast_join_task\u0026gt;,\n  mcast_mutex.owner.counter = 0xff1c69998efec000\r\n\r\ncrash\u0026gt; b 8\nPID: 8        TASK: ff1c69998efec000  CPU: 33   COMMAND: \u0026quot;kworker/u72:0\u0026quot;\n--\n #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646\n #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]\n #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]\n #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]\n #7 [ff\n---truncated---(CVE-2023-52587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()\r\n\r\nFix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug\noccurs when txs-\u0026gt;cnt, data from a URB provided by a USB device, is\nbigger than the size of the array txs-\u0026gt;txstatus, which is\nHTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug\nhandling code after the check. Make the function return if that is the\ncase.\r\n\r\nFound by a modified version of syzkaller.\r\n\r\nUBSAN: array-index-out-of-bounds in htc_drv_txrx.c\nindex 13 is out of range for type \u0026apos;__wmi_event_txstatus [12]\u0026apos;\nCall Trace:\n ath9k_htc_txstatus\n ath9k_wmi_event_tasklet\n tasklet_action_common\n __do_softirq\n irq_exit_rxu\n sysvec_apic_timer_interrupt(CVE-2023-52594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rt2x00: restart beacon queue when hardware reset\r\n\r\nWhen a hardware reset is triggered, all registers are reset, so all\nqueues are forced to stop in hardware interface. However, mac80211\nwill not automatically stop the queue. If we don\u0026apos;t manually stop the\nbeacon queue, the queue will be deadlocked and unable to start again.\nThis patch fixes the issue where Apple devices cannot connect to the\nAP after calling ieee80211_restart_hw().(CVE-2023-52595)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: s390: fix setting of fpc register\r\n\r\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\r\n\r\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\r\n\r\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\r\n\r\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/ptrace: handle setting of fpc register correctly\r\n\r\nIf the content of the floating point control (fpc) register of a traced\nprocess is modified with the ptrace interface the new value is tested for\nvalidity by temporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the tracing process:\nif an interrupt happens while the value is temporarily loaded into the\nfpc register, and within interrupt context floating point or vector\nregisters are used, the current fp/vx registers are saved with\nsave_fpu_regs() assuming they belong to user space and will be loaded into\nfp/vx registers when returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space fpc register value, however\nit will be discarded, when returning to user space.\r\n\r\nIn result the tracer will incorrectly continue to run with the value that\nwas supposed to be used for the traced process.\r\n\r\nFix this by saving fpu register contents with save_fpu_regs() before using\ntest_fp_ctl().(CVE-2023-52598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: avoid online resizing failures due to oversized flex bg\r\n\r\nWhen we online resize an ext4 filesystem with a oversized flexbg_size,\r\n\r\n     mkfs.ext4 -F -G 67108864 $dev -b 4096 100M\n     mount $dev $dir\n     resize2fs $dev 16G\r\n\r\nthe following WARN_ON is triggered:\n==================================================================\nWARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550\nModules linked in: sg(E)\nCPU: 0 PID: 427 Comm: resize2fs Tainted: G  E  6.6.0-rc5+ #314\nRIP: 0010:__alloc_pages+0x411/0x550\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __kmalloc_large_node+0xa2/0x200\n __kmalloc+0x16e/0x290\n ext4_resize_fs+0x481/0xd80\n __ext4_ioctl+0x1616/0x1d90\n ext4_ioctl+0x12/0x20\n __x64_sys_ioctl+0xf0/0x150\n do_syscall_64+0x3b/0x90\n==================================================================\r\n\r\nThis is because flexbg_size is too large and the size of the new_group_data\narray to be allocated exceeds MAX_ORDER. Currently, the minimum value of\nMAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding\nmaximum number of groups that can be allocated is:\r\n\r\n (PAGE_SIZE \u0026lt;\u0026lt; MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845\r\n\r\nAnd the value that is down-aligned to the power of 2 is 16384. Therefore,\nthis value is defined as MAX_RESIZE_BG, and the number of groups added\neach time does not exceed this value during resizing, and is added multiple\ntimes to complete the online resizing. The difference is that the metadata\nin a flex_bg may be more dispersed.(CVE-2023-52622)","status":"published","published":"2024-04-19T11:06:55Z","modified":"2026-08-18T01:18:25.318158829Z","cvss":[{"version":"3.1","score":6.7,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","level":"medium"}],"updated_at":"2026-11-02T15:52:41.095407Z"},{"id":"OESA-2024-1487","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nuio_hv_generic: Fix another memory leak in error handling paths\r\n\r\nMemory allocated by \u0026apos;vmbus_alloc_ring()\u0026apos; at the beginning of the probe\nfunction is never freed in the error handling path.\r\n\r\nAdd the missing \u0026apos;vmbus_free_ring()\u0026apos; call.\r\n\r\nNote that it is already freed in the .remove function.(CVE-2021-47070)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nasix: fix uninit-value in asix_mdio_read()\r\n\r\nasix_read_cmd() may read less than sizeof(smsr) bytes and in this case\nsmsr will be uninitialized.\r\n\r\nFail log:\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\nBUG: KMSAN: uninit-value in asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\nBUG: KMSAN: uninit-value in asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline]\n asix_check_host_enable drivers/net/usb/asix_common.c:82 [inline] drivers/net/usb/asix_common.c:497\n asix_mdio_read+0x3c1/0xb00 drivers/net/usb/asix_common.c:497 drivers/net/usb/asix_common.c:497(CVE-2021-47101)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nEDAC/thunderx: Fix possible out-of-bounds string access\r\n\r\nEnabling -Wstringop-overflow globally exposes a warning for a common bug\nin the usage of strncat():\r\n\r\n  drivers/edac/thunderx_edac.c: In function \u0026apos;thunderx_ocx_com_threaded_isr\u0026apos;:\n  drivers/edac/thunderx_edac.c:1136:17: error: \u0026apos;strncat\u0026apos; specified bound 1024 equals destination size [-Werror=stringop-overflow=]\n   1136 |                 strncat(msg, other, OCX_MESSAGE_SIZE);\n        |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n   ...\n   1145 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\n   ...\n   1150 |                                 strncat(msg, other, OCX_MESSAGE_SIZE);\r\n\r\n   ...\r\n\r\nApparently the author of this driver expected strncat() to behave the\nway that strlcat() does, which uses the size of the destination buffer\nas its third argument rather than the length of the source buffer. The\nresult is that there is no check on the size of the allocated buffer.\r\n\r\nChange it to strlcat().\r\n\r\n  [ bp: Trim compiler output, fixup commit message. ](CVE-2023-52464)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nInput: powermate - fix use-after-free in powermate_config_complete\r\n\r\nsyzbot has found a use-after-free bug [1] in the powermate driver. This\nhappens when the device is disconnected, which leads to a memory free from\nthe powermate_device struct.  When an asynchronous control message\ncompletes after the kfree and its callback is invoked, the lock does not\nexist anymore and hence the bug.\r\n\r\nUse usb_kill_urb() on pm-\u0026gt;config to cancel any in-progress requests upon\ndevice disconnection.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e(CVE-2023-52475)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: pm80xx: Avoid leaking tags when processing OPC_INB_SET_CONTROLLER_CONFIG command\r\n\r\nTags allocated for OPC_INB_SET_CONTROLLER_CONFIG command need to be freed\nwhen we receive the response.(CVE-2023-52500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnfc: nci: assert requested protocol is valid\r\n\r\nThe protocol is used in a bit mask to determine if the protocol is\nsupported. Assert the provided protocol is less than the maximum\ndefined so it doesn\u0026apos;t potentially perform a shift-out-of-bounds and\nprovide a clearer error for undefined protocols vs unsupported ones.(CVE-2023-52507)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nieee802154: ca8210: Fix a potential UAF in ca8210_probe\r\n\r\nIf of_clk_add_provider() fails in ca8210_register_ext_clock(),\nit calls clk_unregister() to release priv-\u0026gt;clk and returns an\nerror. However, the caller ca8210_probe() then calls ca8210_remove(),\nwhere priv-\u0026gt;clk is freed again in ca8210_unregister_ext_clock(). In\nthis case, a use-after-free may happen in the second time we call\nclk_unregister().\r\n\r\nFix this by removing the first clk_unregister(). Also, priv-\u0026gt;clk could\nbe an error code on failure of clk_register_fixed_rate(). Use\nIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().(CVE-2023-52510)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/srp: Do not call scsi_done() from srp_abort()\r\n\r\nAfter scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler\ncallback, it performs one of the following actions:\n* Call scsi_queue_insert().\n* Call scsi_finish_command().\n* Call scsi_eh_scmd_add().\nHence, SCSI abort handlers must not call scsi_done(). Otherwise all\nthe above actions would trigger a use-after-free. Hence remove the\nscsi_done() call from srp_abort(). Keep the srp_free_req() call\nbefore returning SUCCESS because we may not see the command again if\nSUCCESS is returned.(CVE-2023-52515)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma-debug: don\u0026apos;t call __dma_entry_alloc_check_leak() under free_entries_lock\r\n\r\n__dma_entry_alloc_check_leak() calls into printk -\u0026gt; serial console\noutput (qcom geni) and grabs port-\u0026gt;lock under free_entries_lock\nspin lock, which is a reverse locking dependency chain as qcom_geni\nIRQ handler can call into dma-debug code and grab free_entries_lock\nunder port-\u0026gt;lock.\r\n\r\nMove __dma_entry_alloc_check_leak() call out of free_entries_lock\nscope so that we don\u0026apos;t acquire serial console\u0026apos;s port-\u0026gt;lock under it.\r\n\r\nTrimmed-down lockdep splat:\r\n\r\n The existing dependency chain (in reverse order) is:\r\n\r\n               -\u0026gt; #2 (free_entries_lock){-.-.}-{2:2}:\n        _raw_spin_lock_irqsave+0x60/0x80\n        dma_entry_alloc+0x38/0x110\n        debug_dma_map_page+0x60/0xf8\n        dma_map_page_attrs+0x1e0/0x230\n        dma_map_single_attrs.constprop.0+0x6c/0xc8\n        geni_se_rx_dma_prep+0x40/0xcc\n        qcom_geni_serial_isr+0x310/0x510\n        __handle_irq_event_percpu+0x110/0x244\n        handle_irq_event_percpu+0x20/0x54\n        handle_irq_event+0x50/0x88\n        handle_fasteoi_irq+0xa4/0xcc\n        handle_irq_desc+0x28/0x40\n        generic_handle_domain_irq+0x24/0x30\n        gic_handle_irq+0xc4/0x148\n        do_interrupt_handler+0xa4/0xb0\n        el1_interrupt+0x34/0x64\n        el1h_64_irq_handler+0x18/0x24\n        el1h_64_irq+0x64/0x68\n        arch_local_irq_enable+0x4/0x8\n        ____do_softirq+0x18/0x24\n        ...\r\n\r\n               -\u0026gt; #1 (\u0026amp;port_lock_key){-.-.}-{2:2}:\n        _raw_spin_lock_irqsave+0x60/0x80\n        qcom_geni_serial_console_write+0x184/0x1dc\n        console_flush_all+0x344/0x454\n        console_unlock+0x94/0xf0\n        vprintk_emit+0x238/0x24c\n        vprintk_default+0x3c/0x48\n        vprintk+0xb4/0xbc\n        _printk+0x68/0x90\n        register_console+0x230/0x38c\n        uart_add_one_port+0x338/0x494\n        qcom_geni_serial_probe+0x390/0x424\n        platform_probe+0x70/0xc0\n        really_probe+0x148/0x280\n        __driver_probe_device+0xfc/0x114\n        driver_probe_device+0x44/0x100\n        __device_attach_driver+0x64/0xdc\n        bus_for_each_drv+0xb0/0xd8\n        __device_attach+0xe4/0x140\n        device_initial_probe+0x1c/0x28\n        bus_probe_device+0x44/0xb0\n        device_add+0x538/0x668\n        of_device_add+0x44/0x50\n        of_platform_device_create_pdata+0x94/0xc8\n        of_platform_bus_create+0x270/0x304\n        of_platform_populate+0xac/0xc4\n        devm_of_platform_populate+0x60/0xac\n        geni_se_probe+0x154/0x160\n        platform_probe+0x70/0xc0\n        ...\r\n\r\n               -\u0026gt; #0 (console_owner){-...}-{0:0}:\n        __lock_acquire+0xdf8/0x109c\n        lock_acquire+0x234/0x284\n        console_flush_all+0x330/0x454\n        console_unlock+0x94/0xf0\n        vprintk_emit+0x238/0x24c\n        vprintk_default+0x3c/0x48\n        vprintk+0xb4/0xbc\n        _printk+0x68/0x90\n        dma_entry_alloc+0xb4/0x110\n        debug_dma_map_sg+0xdc/0x2f8\n        __dma_map_sg_attrs+0xac/0xe4\n        dma_map_sgtable+0x30/0x4c\n        get_pages+0x1d4/0x1e4 [msm]\n        msm_gem_pin_pages_locked+0x38/0xac [msm]\n        msm_gem_pin_vma_locked+0x58/0x88 [msm]\n        msm_ioctl_gem_submit+0xde4/0x13ac [msm]\n        drm_ioctl_kernel+0xe0/0x15c\n        drm_ioctl+0x2e8/0x3f4\n        vfs_ioctl+0x30/0x50\n        ...\r\n\r\n Chain exists of:\n   console_owner --\u0026gt; \u0026amp;port_lock_key --\u0026gt; free_entries_lock\r\n\r\n  Possible unsafe locking scenario:\r\n\r\n        CPU0                    CPU1\n        ----                    ----\n   lock(free_entries_lock);\n                                lock(\u0026amp;port_lock_key);\n                                lock(free_entries_lock);\n   lock(console_owner);\r\n\r\n                *** DEADLOCK ***\r\n\r\n Call trace:\n  dump_backtrace+0xb4/0xf0\n  show_stack+0x20/0x30\n  dump_stack_lvl+0x60/0x84\n  dump_stack+0x18/0x24\n  print_circular_bug+0x1cc/0x234\n  check_noncircular+0x78/0xac\n  __lock_acquire+0xdf8/0x109c\n  lock_acquire+0x234/0x284\n  console_flush_all+0x330/0x454\n  consol\n---truncated---(CVE-2023-52516)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix possible store tearing in neigh_periodic_work()\r\n\r\nWhile looking at a related syzbot report involving neigh_periodic_work(),\nI found that I forgot to add an annotation when deleting an\nRCU protected item from a list.\r\n\r\nReaders use rcu_deference(*np), we need to use either\nrcu_assign_pointer() or WRITE_ONCE() on writer side\nto prevent store tearing.\r\n\r\nI use rcu_assign_pointer() to have lockdep support,\nthis was the choice made in neigh_flush_dev().(CVE-2023-52522)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: mac80211: fix potential key use-after-free\r\n\r\nWhen ieee80211_key_link() is called by ieee80211_gtk_rekey_add()\nbut returns 0 due to KRACK protection (identical key reinstall),\nieee80211_gtk_rekey_add() will still return a pointer into the\nkey, in a potential use-after-free. This normally doesn\u0026apos;t happen\nsince it\u0026apos;s only called by iwlwifi in case of WoWLAN rekey offload\nwhich has its own KRACK protection, but still better to fix, do\nthat by returning an error code and converting that to success on\nthe cfg80211 boundary only, leaving the error for bad callers of\nieee80211_gtk_rekey_add().(CVE-2023-52530)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions()\r\n\r\nWhen CONFIG_DAMON_VADDR_KUNIT_TEST=y and making CONFIG_DEBUG_KMEMLEAK=y\nand CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN=y, the below memory leak is detected.\r\n\r\nSince commit 9f86d624292c (\u0026quot;mm/damon/vaddr-test: remove unnecessary\nvariables\u0026quot;), the damon_destroy_ctx() is removed, but still call\ndamon_new_target() and damon_new_region(), the damon_region which is\nallocated by kmem_cache_alloc() in damon_new_region() and the damon_target\nwhich is allocated by kmalloc in damon_new_target() are not freed.  And\nthe damon_region which is allocated in damon_new_region() in\ndamon_set_regions() is also not freed.\r\n\r\nSo use damon_destroy_target to free all the damon_regions and damon_target.\r\n\r\n    unreferenced object 0xffff888107c9a940 (size 64):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1069, jiffies 4294670592 (age 732.761s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 06 00 00 00 6b 6b 6b 6b  ............kkkk\n        60 c7 9c 07 81 88 ff ff f8 cb 9c 07 81 88 ff ff  `...............\n      backtrace:\n        [\u0026lt;ffffffff817e0167\u0026gt;] kmalloc_trace+0x27/0xa0\n        [\u0026lt;ffffffff819c11cf\u0026gt;] damon_new_target+0x3f/0x1b0\n        [\u0026lt;ffffffff819c7d55\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0x95/0x3e0\n        [\u0026lt;ffffffff819c82be\u0026gt;] damon_test_apply_three_regions1+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff8881079cc740 (size 56):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1069, jiffies 4294670592 (age 732.761s)\n      hex dump (first 32 bytes):\n        05 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00  ................\n        6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 6b 6b 6b 6b  kkkkkkkk....kkkk\n      backtrace:\n        [\u0026lt;ffffffff819bc492\u0026gt;] damon_new_region+0x22/0x1c0\n        [\u0026lt;ffffffff819c7d91\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0xd1/0x3e0\n        [\u0026lt;ffffffff819c82be\u0026gt;] damon_test_apply_three_regions1+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff888107c9ac40 (size 64):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1071, jiffies 4294670595 (age 732.843s)\n      hex dump (first 32 bytes):\n        00 00 00 00 00 00 00 00 06 00 00 00 6b 6b 6b 6b  ............kkkk\n        a0 cc 9c 07 81 88 ff ff 78 a1 76 07 81 88 ff ff  ........x.v.....\n      backtrace:\n        [\u0026lt;ffffffff817e0167\u0026gt;] kmalloc_trace+0x27/0xa0\n        [\u0026lt;ffffffff819c11cf\u0026gt;] damon_new_target+0x3f/0x1b0\n        [\u0026lt;ffffffff819c7d55\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0x95/0x3e0\n        [\u0026lt;ffffffff819c851e\u0026gt;] damon_test_apply_three_regions2+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffffffff81003791\u0026gt;] ret_from_fork_asm+0x11/0x20\n    unreferenced object 0xffff8881079ccc80 (size 56):\n      comm \u0026quot;kunit_try_catch\u0026quot;, pid 1071, jiffies 4294670595 (age 732.843s)\n      hex dump (first 32 bytes):\n        05 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00  ................\n        6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 6b 6b 6b 6b  kkkkkkkk....kkkk\n      backtrace:\n        [\u0026lt;ffffffff819bc492\u0026gt;] damon_new_region+0x22/0x1c0\n        [\u0026lt;ffffffff819c7d91\u0026gt;] damon_do_test_apply_three_regions.constprop.0+0xd1/0x3e0\n        [\u0026lt;ffffffff819c851e\u0026gt;] damon_test_apply_three_regions2+0x21e/0x260\n        [\u0026lt;ffffffff829fce6a\u0026gt;] kunit_generic_run_threadfn_adapter+0x4a/0x90\n        [\u0026lt;ffffffff81237cf6\u0026gt;] kthread+0x2b6/0x380\n        [\u0026lt;ffffffff81097add\u0026gt;] ret_from_fork+0x2d/0x70\n        [\u0026lt;ffff\n---truncated---(CVE-2023-52560)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\narm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved\r\n\r\nAdding a reserved memory region for the framebuffer memory\n(the splash memory region set up by the bootloader).\r\n\r\nIt fixes a kernel panic (arm-smmu: Unhandled context fault\nat this particular memory region) reported on DB845c running\nv5.10.y.(CVE-2023-52561)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix potential use after free in nilfs_gccache_submit_read_data()\r\n\r\nIn nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the\nreference count of bh when the call to nilfs_dat_translate() fails.  If\nthe reference count hits 0 and its owner page gets unlocked, bh may be\nfreed.  However, bh-\u0026gt;b_page is dereferenced to put the page after that,\nwhich may result in a use-after-free bug.  This patch moves the release\noperation after unlocking and putting the page.\r\n\r\nNOTE: The function in question is only called in GC, and in combination\nwith current userland tools, address translation using DAT does not occur\nin that function, so the code path that causes this issue will not be\nexecuted.  However, it is possible to run that code path by intentionally\nmodifying the userland GC library or by calling the GC ioctl directly.\r\n\r\n[konishi.ryusuke@gmail.com: NOTE added to the commit log](CVE-2023-52566)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nx86/sgx: Resolves SECS reclaim vs. page fault for EAUG race\r\n\r\nThe SGX EPC reclaimer (ksgxd) may reclaim the SECS EPC page for an\nenclave and set secs.epc_page to NULL. The SECS page is used for EAUG\nand ELDU in the SGX page fault handler. However, the NULL check for\nsecs.epc_page is only done for ELDU, not EAUG before being used.\r\n\r\nFix this by doing the same NULL check and reloading of the SECS page as\nneeded for both EAUG and ELDU.\r\n\r\nThe SECS page holds global enclave metadata. It can only be reclaimed\nwhen there are no other enclave pages remaining. At that point,\nvirtually nothing can be done with the enclave until the SECS page is\npaged back in.\r\n\r\nAn enclave can not run nor generate page faults without a resident SECS\npage. But it is still possible for a #PF for a non-SECS page to race\nwith paging out the SECS page: when the last resident non-SECS page A\ntriggers a #PF in a non-resident page B, and then page A and the SECS\nboth are paged out before the #PF on B is handled.\r\n\r\nHitting this bug requires that race triggered with a #PF for EAUG.\nFollowing is a trace when it happens.\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nRIP: 0010:sgx_encl_eaug_page+0xc7/0x210\nCall Trace:\n ? __kmem_cache_alloc_node+0x16a/0x440\n ? xa_load+0x6e/0xa0\n sgx_vma_fault+0x119/0x230\n __do_fault+0x36/0x140\n do_fault+0x12f/0x400\n __handle_mm_fault+0x728/0x1110\n handle_mm_fault+0x105/0x310\n do_user_addr_fault+0x1ee/0x750\n ? __this_cpu_preempt_check+0x13/0x20\n exc_page_fault+0x76/0x180\n asm_exc_page_fault+0x27/0x30(CVE-2023-52568)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: rds: Fix possible NULL-pointer dereference\r\n\r\nIn rds_rdma_cm_event_handler_cmn() check, if conn pointer exists\nbefore dereferencing it as rdma_set_service_type() argument\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2023-52573)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: use DEV_STATS_INC()\r\n\r\nsyzbot/KCSAN reported data-races in br_handle_frame_finish() [1]\nThis function can run from multiple cpus without mutual exclusion.\r\n\r\nAdopt SMP safe DEV_STATS_INC() to update dev-\u0026gt;stats fields.\r\n\r\nHandles updates to dev-\u0026gt;stats.tx_dropped while we are at it.\r\n\r\n[1]\nBUG: KCSAN: data-race in br_handle_frame_finish / br_handle_frame_finish\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 1:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\nrun_ksoftirqd+0x17/0x20 kernel/softirq.c:921\nsmpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nread-write to 0xffff8881374b2178 of 8 bytes by interrupt on cpu 0:\nbr_handle_frame_finish+0xd4f/0xef0 net/bridge/br_input.c:189\nbr_nf_hook_thresh+0x1ed/0x220\nbr_nf_pre_routing_finish_ipv6+0x50f/0x540\nNF_HOOK include/linux/netfilter.h:304 [inline]\nbr_nf_pre_routing_ipv6+0x1e3/0x2a0 net/bridge/br_netfilter_ipv6.c:178\nbr_nf_pre_routing+0x526/0xba0 net/bridge/br_netfilter_hooks.c:508\nnf_hook_entry_hookfn include/linux/netfilter.h:144 [inline]\nnf_hook_bridge_pre net/bridge/br_input.c:272 [inline]\nbr_handle_frame+0x4c9/0x940 net/bridge/br_input.c:417\n__netif_receive_skb_core+0xa8a/0x21e0 net/core/dev.c:5417\n__netif_receive_skb_one_core net/core/dev.c:5521 [inline]\n__netif_receive_skb+0x57/0x1b0 net/core/dev.c:5637\nprocess_backlog+0x21f/0x380 net/core/dev.c:5965\n__napi_poll+0x60/0x3b0 net/core/dev.c:6527\nnapi_poll net/core/dev.c:6594 [inline]\nnet_rx_action+0x32b/0x750 net/core/dev.c:6727\n__do_softirq+0xc1/0x265 kernel/softirq.c:553\ndo_softirq+0x5e/0x90 kernel/softirq.c:454\n__local_bh_enable_ip+0x64/0x70 kernel/softirq.c:381\n__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]\n_raw_spin_unlock_bh+0x36/0x40 kernel/locking/spinlock.c:210\nspin_unlock_bh include/linux/spinlock.h:396 [inline]\nbatadv_tt_local_purge+0x1a8/0x1f0 net/batman-adv/translation-table.c:1356\nbatadv_tt_purge+0x2b/0x630 net/batman-adv/translation-table.c:3560\nprocess_one_work kernel/workqueue.c:2630 [inline]\nprocess_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703\nworker_thread+0x525/0x730 kernel/workqueue.c:2784\nkthread+0x1d7/0x210 kernel/kthread.c:388\nret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147\nret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304\r\n\r\nvalue changed: 0x00000000000d7190 -\u0026gt; 0x00000000000d7191\r\n\r\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 14848 Comm: kworker/u4:11 Not tainted 6.6.0-rc1-syzkaller-00236-gad8a69f361b9 #0(CVE-2023-52578)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nceph: fix deadlock or deadcode of misusing dget()\r\n\r\nThe lock order is incorrect between denty and its parent, we should\nalways make sure that the parent get the lock first.\r\n\r\nBut since this deadcode is never used and the parent dir will always\nbe set from the callers, let\u0026apos;s just remove it.(CVE-2023-52583)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/ipoib: Fix mcast list locking\r\n\r\nReleasing the `priv-\u0026gt;lock` while iterating the `priv-\u0026gt;multicast_list` in\n`ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to\nremove the items while in the middle of iteration. If the mcast is removed\nwhile the lock was dropped, the for loop spins forever resulting in a hard\nlockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel):\r\n\r\n    Task A (kworker/u72:2 below)       | Task B (kworker/u72:0 below)\n    -----------------------------------+-----------------------------------\n    ipoib_mcast_join_task(work)        | ipoib_ib_dev_flush_light(work)\n      spin_lock_irq(\u0026amp;priv-\u0026gt;lock)       | __ipoib_ib_dev_flush(priv, ...)\n      list_for_each_entry(mcast,       | ipoib_mcast_dev_flush(dev = priv-\u0026gt;dev)\n          \u0026amp;priv-\u0026gt;multicast_list, list) |\n        ipoib_mcast_join(dev, mcast)   |\n          spin_unlock_irq(\u0026amp;priv-\u0026gt;lock) |\n                                       |   spin_lock_irqsave(\u0026amp;priv-\u0026gt;lock, flags)\n                                       |   list_for_each_entry_safe(mcast, tmcast,\n                                       |                  \u0026amp;priv-\u0026gt;multicast_list, list)\n                                       |     list_del(\u0026amp;mcast-\u0026gt;list);\n                                       |     list_add_tail(\u0026amp;mcast-\u0026gt;list, \u0026amp;remove_list)\n                                       |   spin_unlock_irqrestore(\u0026amp;priv-\u0026gt;lock, flags)\n          spin_lock_irq(\u0026amp;priv-\u0026gt;lock)   |\n                                       |   ipoib_mcast_remove_list(\u0026amp;remove_list)\n   (Here, `mcast` is no longer on the  |     list_for_each_entry_safe(mcast, tmcast,\n    `priv-\u0026gt;multicast_list` and we keep |                            remove_list, list)\n    spinning on the `remove_list` of   |  \u0026gt;\u0026gt;\u0026gt;  wait_for_completion(\u0026amp;mcast-\u0026gt;done)\n    the other thread which is blocked  |\n    and the list is still valid on     |\n    it\u0026apos;s stack.)\r\n\r\nFix this by keeping the lock held and changing to GFP_ATOMIC to prevent\neventual sleeps.\nUnfortunately we could not reproduce the lockup and confirm this fix but\nbased on the code review I think this fix should address such lockups.\r\n\r\ncrash\u0026gt; bc 31\nPID: 747      TASK: ff1c6a1a007e8000  CPU: 31   COMMAND: \u0026quot;kworker/u72:2\u0026quot;\n--\n    [exception RIP: ipoib_mcast_join_task+0x1b1]\n    RIP: ffffffffc0944ac1  RSP: ff646f199a8c7e00  RFLAGS: 00000002\n    RAX: 0000000000000000  RBX: ff1c6a1a04dc82f8  RCX: 0000000000000000\n                                  work (\u0026amp;priv-\u0026gt;mcast_task{,.work})\n    RDX: ff1c6a192d60ac68  RSI: 0000000000000286  RDI: ff1c6a1a04dc8000\n           \u0026amp;mcast-\u0026gt;list\n    RBP: ff646f199a8c7e90   R8: ff1c699980019420   R9: ff1c6a1920c9a000\n    R10: ff646f199a8c7e00  R11: ff1c6a191a7d9800  R12: ff1c6a192d60ac00\n                                                         mcast\n    R13: ff1c6a1d82200000  R14: ff1c6a1a04dc8000  R15: ff1c6a1a04dc82d8\n           dev                    priv (\u0026amp;priv-\u0026gt;lock)     \u0026amp;priv-\u0026gt;multicast_list (aka head)\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n--- \u0026lt;NMI exception stack\u0026gt; ---\n #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib]\n #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967\r\n\r\ncrash\u0026gt; rx ff646f199a8c7e68\nff646f199a8c7e68:  ff1c6a1a04dc82f8 \u0026lt;\u0026lt;\u0026lt; work = \u0026amp;priv-\u0026gt;mcast_task.work\r\n\r\ncrash\u0026gt; list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000\n(empty)\r\n\r\ncrash\u0026gt; ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000\n  mcast_task.work.func = 0xffffffffc0944910 \u0026lt;ipoib_mcast_join_task\u0026gt;,\n  mcast_mutex.owner.counter = 0xff1c69998efec000\r\n\r\ncrash\u0026gt; b 8\nPID: 8        TASK: ff1c69998efec000  CPU: 33   COMMAND: \u0026quot;kworker/u72:0\u0026quot;\n--\n #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646\n #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib]\n #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib]\n #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib]\n #7 [ff\n---truncated---(CVE-2023-52587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()\r\n\r\nFix an array-index-out-of-bounds read in ath9k_htc_txstatus(). The bug\noccurs when txs-\u0026gt;cnt, data from a URB provided by a USB device, is\nbigger than the size of the array txs-\u0026gt;txstatus, which is\nHTC_MAX_TX_STATUS. WARN_ON() already checks it, but there is no bug\nhandling code after the check. Make the function return if that is the\ncase.\r\n\r\nFound by a modified version of syzkaller.\r\n\r\nUBSAN: array-index-out-of-bounds in htc_drv_txrx.c\nindex 13 is out of range for type \u0026apos;__wmi_event_txstatus [12]\u0026apos;\nCall Trace:\n ath9k_htc_txstatus\n ath9k_wmi_event_tasklet\n tasklet_action_common\n __do_softirq\n irq_exit_rxu\n sysvec_apic_timer_interrupt(CVE-2023-52594)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: rt2x00: restart beacon queue when hardware reset\r\n\r\nWhen a hardware reset is triggered, all registers are reset, so all\nqueues are forced to stop in hardware interface. However, mac80211\nwill not automatically stop the queue. If we don\u0026apos;t manually stop the\nbeacon queue, the queue will be deadlocked and unable to start again.\nThis patch fixes the issue where Apple devices cannot connect to the\nAP after calling ieee80211_restart_hw().(CVE-2023-52595)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: s390: fix setting of fpc register\r\n\r\nkvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control\n(fpc) register of a guest cpu. The new value is tested for validity by\ntemporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the host process:\nif an interrupt happens while the value is temporarily loaded into the fpc\nregister, and within interrupt context floating point or vector registers\nare used, the current fp/vx registers are saved with save_fpu_regs()\nassuming they belong to user space and will be loaded into fp/vx registers\nwhen returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space / host process fpc register\nvalue, however it will be discarded, when returning to user space.\r\n\r\nIn result the host process will incorrectly continue to run with the value\nthat was supposed to be used for a guest cpu.\r\n\r\nFix this by simply removing the test. There is another test right before\nthe SIE context is entered which will handles invalid values.\r\n\r\nThis results in a change of behaviour: invalid values will now be accepted\ninstead of that the ioctl fails with -EINVAL. This seems to be acceptable,\ngiven that this interface is most likely not used anymore, and this is in\naddition the same behaviour implemented with the memory mapped interface\n(replace invalid values with zero) - see sync_regs() in kvm-s390.c.(CVE-2023-52597)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/ptrace: handle setting of fpc register correctly\r\n\r\nIf the content of the floating point control (fpc) register of a traced\nprocess is modified with the ptrace interface the new value is tested for\nvalidity by temporarily loading it into the fpc register.\r\n\r\nThis may lead to corruption of the fpc register of the tracing process:\nif an interrupt happens while the value is temporarily loaded into the\nfpc register, and within interrupt context floating point or vector\nregisters are used, the current fp/vx registers are saved with\nsave_fpu_regs() assuming they belong to user space and will be loaded into\nfp/vx registers when returning to user space.\r\n\r\ntest_fp_ctl() restores the original user space fpc register value, however\nit will be discarded, when returning to user space.\r\n\r\nIn result the tracer will incorrectly continue to run with the value that\nwas supposed to be used for the traced process.\r\n\r\nFix this by saving fpu register contents with save_fpu_regs() before using\ntest_fp_ctl().(CVE-2023-52598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: avoid online resizing failures due to oversized flex bg\r\n\r\nWhen we online resize an ext4 filesystem with a oversized flexbg_size,\r\n\r\n     mkfs.ext4 -F -G 67108864 $dev -b 4096 100M\n     mount $dev $dir\n     resize2fs $dev 16G\r\n\r\nthe following WARN_ON is triggered:\n==================================================================\nWARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550\nModules linked in: sg(E)\nCPU: 0 PID: 427 Comm: resize2fs Tainted: G  E  6.6.0-rc5+ #314\nRIP: 0010:__alloc_pages+0x411/0x550\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __kmalloc_large_node+0xa2/0x200\n __kmalloc+0x16e/0x290\n ext4_resize_fs+0x481/0xd80\n __ext4_ioctl+0x1616/0x1d90\n ext4_ioctl+0x12/0x20\n __x64_sys_ioctl+0xf0/0x150\n do_syscall_64+0x3b/0x90\n==================================================================\r\n\r\nThis is because flexbg_size is too large and the size of the new_group_data\narray to be allocated exceeds MAX_ORDER. Currently, the minimum value of\nMAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding\nmaximum number of groups that can be allocated is:\r\n\r\n (PAGE_SIZE \u0026lt;\u0026lt; MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845\r\n\r\nAnd the value that is down-aligned to the power of 2 is 16384. Therefore,\nthis value is defined as MAX_RESIZE_BG, and the number of groups added\neach time does not exceed this value during resizing, and is added multiple\ntimes to complete the online resizing. The difference is that the metadata\nin a flex_bg may be more dispersed.(CVE-2023-52622)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: regenerate buddy after block freeing failed if under fc replay\r\n\r\nThis mostly reverts commit 6bd97bf273bd (\u0026quot;ext4: remove redundant\nmb_regenerate_buddy()\u0026quot;) and reintroduces mb_regenerate_buddy(). Based on\ncode in mb_free_blocks(), fast commit replay can end up marking as free\nblocks that are already marked as such. This causes corruption of the\nbuddy bitmap so we need to regenerate it in that case.(CVE-2024-26601)","status":"published","published":"2024-04-19T11:06:56Z","modified":"2026-08-18T01:18:25.297262976Z","cvss":[{"version":"3.1","score":6.7,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","level":"medium"}],"updated_at":"2026-11-02T15:52:41.095407Z"},{"id":"RHSA-2024:2394","title":"Red Hat Security Advisory: kernel security, bug fix, and enhancement update","status":"published","published":"2024-09-24T08:51:43Z","modified":"2026-10-17T10:03:05Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:13.30378Z"},{"id":"RHSA-2024:2950","title":"Red Hat Security Advisory: kernel-rt security and bug fix update","status":"published","published":"2024-09-24T08:36:38Z","modified":"2026-10-17T10:30:24.321500459Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:13.30378Z"},{"id":"RHSA-2024:3138","title":"Red Hat Security Advisory: kernel security, bug fix, and enhancement update","status":"published","published":"2024-09-24T08:36:26Z","modified":"2026-10-17T10:30:24.646926996Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:13.30378Z"},{"id":"RXSA-2024:3138","title":"Moderate: kernel security, bug fix, and enhancement update","description":"The kernel packages contain the Linux kernel, the core of any Linux operating system.\n\nSecurity Fix(es):\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nAdditional Changes:\n\nFor detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.","status":"published","published":"2026-05-29T18:07:16.639878Z","modified":"2026-05-29T18:23:14.2973982Z","cvss":[{"version":"3.1","score":8,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:40.430679Z"},{"id":"UBUNTU-CVE-2023-52597","description":"In the Linux kernel, the following vulnerability has been resolved: KVM: s390: fix setting of fpc register kvm_arch_vcpu_ioctl_set_fpu() allows to set the floating point control (fpc) register of a guest cpu. The new value is tested for validity by temporarily loading it into the fpc register. This may lead to corruption of the fpc register of the host process: if an interrupt happens while the value is temporarily loaded into the fpc register, and within interrupt context floating point or vector registers are used, the current fp/vx registers are saved with save_fpu_regs() assuming they belong to user space and will be loaded into fp/vx registers when returning to user space. test_fp_ctl() restores the original user space / host process fpc register value, however it will be discarded, when returning to user space. In result the host process will incorrectly continue to run with the value that was supposed to be used for a guest cpu. Fix this by simply removing the test. There is another test right before the SIE context is entered which will handles invalid values. This results in a change of behaviour: invalid values will now be accepted instead of that the ioctl fails with -EINVAL. This seems to be acceptable, given that this interface is most likely not used anymore, and this is in addition the same behaviour implemented with the memory mapped interface (replace invalid values with zero) - see sync_regs() in kvm-s390.c.","status":"published","published":"2024-03-06T07:15:00Z","modified":"2026-11-11T09:36:43.258437156Z","cvss":[{"version":"4.0","score":1.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","level":"low"},{"version":"3.1","score":4,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-11T09:59:24.867216Z"},{"id":"ALSA-2024:2394","title":"Important: kernel security, bug fix, and enhancement update","description":"The kernel packages contain the Linux kernel, the core of any Linux operating system.  \n\nSecurity Fix(es):  \n\n  * kernel: GSM multiplexing race condition leads to privilege escalation (CVE-2023-6546)\n  * kernel: multiple use-after-free vulnerabilities (CVE-2024-1086, CVE-2023-3567, CVE-2023-4133, CVE-2023-6932, CVE-2023-39198, CVE-2023-51043, CVE-2023-51779, CVE-2023-51780, CVE-2024-1085, CVE-2024-26582)\n  * kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack (CVE-2020-26555)\n  * kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion (CVE-2022-0480)\n  * kernel: multiple NULL pointer dereference vulnerabilities (CVE-2022-38096, CVE-2023-6622, CVE-2023-6915, CVE-2023-42754, CVE-2023-46862, CVE-2023-52574, CVE-2024-0841, CVE-2023-52448)\n  * kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c (CVE-2022-45934)\n  * kernel: netfilter: nf_tables: out-of-bounds access in nf_tables_newtable() (CVE-2023-6040)\n  * kernel: GC's deletion of an SKB races with unix_stream_read_generic() leading to UAF (CVE-2023-6531)\n  * kernel: Out of boundary write in perf_read_group() as result of overflow a perf_event's read_size (CVE-2023-6931)\n  * kernel: Bluetooth Forward and Future Secrecy Attacks and Defenses (CVE-2023-24023)\n  * kernel: irdma: Improper access control (CVE-2023-25775)\n  * Kernel: double free in hci_conn_cleanup of the bluetooth subsystem (CVE-2023-28464)\n  * kernel: Bluetooth: HCI: global out-of-bounds access in net/bluetooth/hci_sync.c (CVE-2023-28866)\n  * kernel: race condition between HCIUARTSETPROTO and HCIUARTGETPROTO in hci_uart_tty_ioctl (CVE-2023-31083)\n  * kernel: multiple out-of-bounds read vulnerabilities (CVE-2023-37453, CVE-2023-39189, CVE-2023-39193, CVE-2023-6121, CVE-2023-39194)\n  * kernel: netfilter: race condition between IPSET_CMD_ADD and IPSET_CMD_SWAP (CVE-2023-42756)\n  * kernel: lib/kobject.c vulnerable to fill_kobj_path out-of-bounds write (CVE-2023-45863)\n  * kernel: smb: client: fix potential OOBs in smb2_parse_contexts() (CVE-2023-52434)\n  * kernel: mm/sparsemem: fix race in accessing memory_section-\u003eusage (CVE-2023-52489)\n  * kernel: net: fix possible store tearing in neigh_periodic_work() (CVE-2023-52522)\n  * kernel: multiple memory leak vulnerabilities (CVE-2023-52529, CVE-2023-52581)\n  * kernel: net: bridge: data races indata-races in br_handle_frame_finish() (CVE-2023-52578)\n  * kernel: net/core: kernel crash in ETH_P_1588 flow dissector (CVE-2023-52580)\n  * kernel: net/sched: act_ct: fix skb leak and crash on ooo frags (CVE-2023-52610)\n  * kernel: CIFS Filesystem Decryption Improper Input Validation Remote Code Execution Vulnerability in function receive_encrypted_standard of client (CVE-2024-0565)\n  * kernel: tls: race between async notify and socket close (CVE-2024-26583)\n  * kernel: tls: handle backlogging of crypto requests (CVE-2024-26584)\n  * kernel: tls: race between tx work scheduling and socket close (CVE-2024-26585)\n  * kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption (CVE-2024-26586)\n  * kernel: i2c: i801: Fix block process call transactions (CVE-2024-26593)\n  * kernel: sched/membarrier: reduce the ability to hammer on sys_membarrier (CVE-2024-26602)\n  * kernel: netfilter: nf_tables: reject QUEUE/DROP verdict parameters (CVE-2024-26609)\n  * kernel: local dos vulnerability in scatterwalk_copychunks (CVE-2023-6176)\n  * kernel: perf/x86/lbr: Filter vsyscall addresses (CVE-2023-52476)\n  * kernel: netfilter: nf_tables: disallow timeout for anonymous sets (CVE-2023-52620)\n  * kernel: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (CVE-2024-26633)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.  \n\nAdditional Changes:  \n\nFor detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.\n","status":"published","published":"2024-04-30T00:00:00Z","modified":"2026-10-29T11:42:21.143786434Z","updated_at":"2026-11-02T15:27:52.553233Z"},{"id":"DLA-3842-1","title":"linux-5.10 - security update","status":"published","published":"2024-06-25T00:00:00Z","modified":"2026-03-09T01:22:14.203921Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"DSA-5681-1","title":"linux - security update","status":"published","published":"2024-05-06T00:00:00Z","modified":"2026-03-09T02:09:16.152175Z","updated_at":"2026-11-02T15:46:17.892347Z"},{"id":"SUSE-SU-2024:0856-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2021-47078: Fixed a bug by clearing all QP fields if creation failed (bsc#1220863)\n- CVE-2021-47076: Fixed a bug by returning CQE error if invalid lkey was supplied (bsc#1220860)\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2023-52569: Fixed a bug in btrfs by remoning BUG() after failure to insert delayed dir index item (bsc#1220918).\n- CVE-2023-52482: Fixed a bug by adding SRSO mitigation for Hygon processors (bsc#1220735).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2022-48627: Fixed a memory overlapping when deleting chars in the buffer (bsc#1220845).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2021-46934: Fixed a bug by validating user data in compat ioctl (bsc#1220469).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52530: Fixed a potential key use-after-free in wifi mac80211 (bsc#1220930).\n- CVE-2023-52531: Fixed a memory corruption issue in iwlwifi (bsc#1220931).\n- CVE-2021-47083: Fixed a global-out-of-bounds issue in mediatek: (bsc#1220917).\n- CVE-2024-26607: Fixed a probing race issue in sii902x: (bsc#1220736).\n- CVE-2024-26589: Fixed out of bounds read due to variable offset alu on PTR_TO_FLOW_KEYS (bsc#1220255).\n- CVE-2021-47005: Fixed a NULL pointer dereference for -\u003eget_features() (bsc#1220660).\n- CVE-2024-26585: Fixed race between tx work scheduling and socket close  (bsc#1220187).\n- CVE-2023-52340: Fixed ICMPv6 “Packet Too Big” packets force a DoS of the Linux kernel by forcing 100% CPU (bsc#1219295).\n- CVE-2024-0607: Fixed 64-bit load issue in  nft_byteorder_eval() (bsc#1218915).\n- CVE-2021-47060: Fixed a bug in KVM by stop looking for coalesced MMIO zones if the bus is destroyed (bsc#1220742).\n- CVE-2023-6817: Fixed use-after-free in nft_pipapo_walk (bsc#1218195).\n- CVE-2024-26622: Fixed UAF write bug in tomoyo_write_control() (bsc#1220825).\n- CVE-2023-52451: Fixed access beyond end of drmem array  (bsc#1220250).\n- CVE-2021-46932: Fixed missing work initialization before device registration (bsc#1220444)\n- CVE-2023-52463: Fixed null pointer dereference in efivarfs (bsc#1220328).\n- CVE-2021-47012: Fixed a use after free in siw_alloc_mr (bsc#1220627).\n- CVE-2023-52449: Fixed gluebi NULL pointer dereference caused by ftl notifier  (bsc#1220238).\n- CVE-2023-52475: Fixed use-after-free in powermate_config_complete (bsc#1220649)\n- CVE-2023-52478: Fixed kernel crash on receiver USB disconnect (bsc#1220796)\n- CVE-2021-46989: Fixed a bug by preventing corruption in shrinking truncate in hfsplus (bsc#1220737).\n- CVE-2021-46915: Fixed a bug to avoid possible divide error in nft_limit_init (bsc#1220436).\n- CVE-2021-46924: Fixed fix memory leak in device probe and remove (bsc#1220459)\n- CVE-2019-25162: Fixed a potential use after free (bsc#1220409).\n- CVE-2020-36784: Fixed reference leak when pm_runtime_get_sync fails (bsc#1220570).\n- CVE-2021-47061: Fixed a bug in KVM by destroy I/O bus devices on unregister failure _after_  sync'ing SRCU (bsc#1220745).\n- CVE-2023-52445: Fixed use after free on context disconnection (bsc#1220241).\n- CVE-2023-46343: Fixed a NULL pointer dereference in send_acknowledge() (CVE-2023-46343).\n- CVE-2023-52439: Fixed use-after-free in uio_open (bsc#1220140).\n- CVE-2023-52443: Fixed crash when parsed profile name is empty  (bsc#1220240).\n- CVE-2024-26602: Fixed overall slowdowns with sys_membarrier (bsc1220398).\n- CVE-2024-26593: Fixed block process call transactions (bsc#1220009).\n- CVE-2021-47013: Fixed a use after free in emac_mac_tx_buf_send (bsc#1220641).\n- CVE-2024-26586: Fixed stack corruption (bsc#1220243).\n- CVE-2024-26595: Fixed NULL pointer dereference in  error path (bsc#1220344).\n- CVE-2023-52448: Fixed kernel NULL pointer dereference in gfs2_rgrp_dump  (bsc#1220253).\n- CVE-2024-1151: Fixed unlimited number of recursions from action  sets (bsc#1219835).\n- CVE-2024-23849: Fixed array-index-out-of-bounds in rds_cmsg_recv  (bsc#1219127).\n- CVE-2024-0340: Fixed information disclosure in vhost/vhost.c:vhost_new_msg() (bsc#1218689).\n- CVE-2023-51042: Fixed use-after-free in amdgpu_cs_wait_all_fences in drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c (bsc#1219128).\n\nThe following non-security bugs were fixed:\n\n- EDAC/thunderx: Fix possible out-of-bounds string access (bsc#1220330)\n- ext4: fix deadlock due to mbcache entry corruption (bsc#1207653 bsc#1219915).\n- ibmvfc: make 'max_sectors' a module option (bsc#1216223).\n- KVM: Destroy target device if coalesced MMIO unregistration fails (git-fixes).\n- KVM: mmio: Fix use-after-free Read in kvm_vm_ioctl_unregister_coalesced_mmio (git-fixes).\n- KVM: VMX: Move VERW closer to VMentry for MDS mitigation (git-fixes).\n- KVM: VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH (git-fixes).\n- KVM: x86: add support for CPUID leaf 0x80000021 (git-fixes).\n- KVM: x86: Move open-coded CPUID leaf 0x80000021 EAX bit propagation code (git-fixes).\n- KVM: x86: synthesize CPUID leaf 0x80000021h if useful (git-fixes).\n- KVM: x86: work around QEMU issue with synthetic CPUID leaves (git-fixes).\n- mbcache: Fixup kABI of mb_cache_entry (bsc#1207653 bsc#1219915).\n- scsi: Update max_hw_sectors on rescan (bsc#1216223).\n- x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix (git-fixes).\n- x86/bugs: Add asm helpers for executing VERW (git-fixes).\n- x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key (git-fixes).\n- x86/cpu, kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf (git-fixes).\n- x86/entry_32: Add VERW just before userspace transition (git-fixes).\n- x86/entry_64: Add VERW just before userspace transition (git-fixes).\n","status":"published","published":"2024-03-13T00:04:28Z","modified":"2025-05-02T04:30:12.998825Z","updated_at":"2026-11-02T15:53:54.239786Z"},{"id":"SUSE-SU-2024:0857-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2024-26589: Fixed out of bounds read due to variable offset alu on PTR_TO_FLOW_KEYS (bsc#1220255).\n- CVE-2024-26585: Fixed race between tx work scheduling and socket close  (bsc#1220187).\n- CVE-2023-52340: Fixed ICMPv6 “Packet Too Big” packets force a DoS of the Linux kernel by forcing 100% CPU (bsc#1219295).\n- CVE-2024-0607: Fixed 64-bit load issue in  nft_byteorder_eval() (bsc#1218915).\n- CVE-2023-6817: Fixed use-after-free in nft_pipapo_walk (bsc#1218195).\n- CVE-2024-26622: Fixed UAF write bug in tomoyo_write_control() (bsc#1220825).\n- CVE-2023-52451: Fixed access beyond end of drmem array  (bsc#1220250).\n- CVE-2021-46932: Fixed missing work initialization before device registration (bsc#1220444)\n- CVE-2023-52463: Fixed null pointer dereference in efivarfs (bsc#1220328).\n- CVE-2023-52449: Fixed gluebi NULL pointer dereference caused by ftl notifier  (bsc#1220238).\n- CVE-2023-52475: Fixed use-after-free in powermate_config_complete (bsc#1220649)\n- CVE-2023-52478: Fixed kernel crash on receiver USB disconnect (bsc#1220796)\n- CVE-2021-46915: Fixed a bug to avoid possible divide error in nft_limit_init (bsc#1220436).\n- CVE-2021-46924: Fixed fix memory leak in device probe and remove (bsc#1220459)\n- CVE-2019-25162: Fixed a potential use after free (bsc#1220409).\n- CVE-2020-36784: Fixed reference leak when pm_runtime_get_sync fails (bsc#1220570).\n- CVE-2023-52445: Fixed use after free on context disconnection (bsc#1220241).\n- CVE-2023-46343: Fixed a NULL pointer dereference in send_acknowledge() (CVE-2023-46343).\n- CVE-2023-52439: Fixed use-after-free in uio_open (bsc#1220140).\n- CVE-2023-52443: Fixed crash when parsed profile name is empty  (bsc#1220240).\n- CVE-2024-26602: Fixed overall slowdowns with sys_membarrier (bsc1220398).\n- CVE-2024-26593: Fixed block process call transactions (bsc#1220009).\n- CVE-2021-47013: Fixed a use after free in emac_mac_tx_buf_send (bsc#1220641).\n- CVE-2024-26586: Fixed stack corruption (bsc#1220243).\n- CVE-2024-26595: Fixed NULL pointer dereference in  error path (bsc#1220344).\n- CVE-2023-52448: Fixed kernel NULL pointer dereference in gfs2_rgrp_dump  (bsc#1220253).\n- CVE-2024-1151: Fixed unlimited number of recursions from action  sets (bsc#1219835).\n- CVE-2024-23849: Fixed array-index-out-of-bounds in rds_cmsg_recv  (bsc#1219127).\n- CVE-2024-0340: Fixed information disclosure in vhost/vhost.c:vhost_new_msg() (bsc#1218689).\n- CVE-2023-51042: Fixed use-after-free in amdgpu_cs_wait_all_fences in drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c (bsc#1219128).\n- CVE-2021-47078: Fixed a bug by clearing all QP fields if creation failed (bsc#1220863)\n- CVE-2021-47076: Fixed a bug by returning CQE error if invalid lkey was supplied (bsc#1220860)\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-52569: Fixed a bug in btrfs by remoning BUG() after failure to insert delayed dir index item (bsc#1220918).\n- CVE-2023-52482: Fixex a bug by adding SRSO mitigation for Hygon processors (bsc#1220735).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2022-48627: Fixed a memory overlapping when deleting chars in the buffer (bsc#1220845).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2021-46934: Fixed a bug by validating user data in compat ioctl (bsc#1220469).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52530: Fixed a potential key use-after-free in wifi mac80211 (bsc#1220930).\n- CVE-2023-52531: Fixed a memory corruption issue in iwlwifi (bsc#1220931).\n- CVE-2021-47083: Fixed a global-out-of-bounds issue in mediatek: (bsc#1220917).\n- CVE-2024-26607: Fixed a probing race issue in sii902x: (bsc#1220736).\n- CVE-2021-47005: Fixed a NULL pointer dereference for -\u003eget_features() (bsc#1220660).\n- CVE-2021-47060: Fixed a bug in KVM by stop looking for coalesced MMIO zones if the bus is destroyed (bsc#1220742).\n- CVE-2021-47012: Fixed a use after free in siw_alloc_mr (bsc#1220627).\n- CVE-2021-46989: Fixed a bug by preventing corruption in shrinking truncate in hfsplus (bsc#1220737).\n- CVE-2021-47061: Fixed a bug in KVM by destroy I/O bus devices on unregister failure _after_  sync'ing SRCU (bsc#1220745).\n\nThe following non-security bugs were fixed:\n\n- EDAC/thunderx: Fix possible out-of-bounds string access (bsc#1220330)\n- ext4: fix deadlock due to mbcache entry corruption (bsc#1207653 bsc#1219915).\n- ibmvfc: make 'max_sectors' a module option (bsc#1216223).\n- KVM: Destroy target device if coalesced MMIO unregistration fails (git-fixes).\n- KVM: mmio: Fix use-after-free Read in kvm_vm_ioctl_unregister_coalesced_mmio (git-fixes).\n- KVM: VMX: Move VERW closer to VMentry for MDS mitigation (git-fixes).\n- KVM: VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH (git-fixes).\n- KVM: x86: add support for CPUID leaf 0x80000021 (git-fixes).\n- KVM: x86: Move open-coded CPUID leaf 0x80000021 EAX bit propagation code (git-fixes).\n- KVM: x86: synthesize CPUID leaf 0x80000021h if useful (git-fixes).\n- KVM: x86: work around QEMU issue with synthetic CPUID leaves (git-fixes).\n- mbcache: Fixup kABI of mb_cache_entry (bsc#1207653 bsc#1219915).\n- scsi: Update max_hw_sectors on rescan (bsc#1216223).\n- x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix (git-fixes).\n- x86/bugs: Add asm helpers for executing VERW (git-fixes).\n- x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key (git-fixes). Also add the removed mds_user_clear symbol to kABI severities as it is exposed just for KVM module and is generally a core kernel component so removing it is low risk.\n- x86/cpu, kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf (git-fixes).\n- x86/entry_32: Add VERW just before userspace transition (git-fixes).\n- x86/entry_64: Add VERW just before userspace transition (git-fixes).\n","status":"published","published":"2024-03-13T00:08:00Z","modified":"2025-05-02T04:30:13.066618Z","updated_at":"2026-11-02T15:53:54.239786Z"},{"id":"SUSE-SU-2024:0925-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2021-47078: Fixed a bug by clearing all QP fields if creation failed (bsc#1220863)\n- CVE-2021-47076: Fixed a bug by returning CQE error if invalid lkey was supplied (bsc#1220860)\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2023-52482: Fixed a bug by adding SRSO mitigation for Hygon processors (bsc#1220735).\n- CVE-2022-48627: Fixed a memory overlapping when deleting chars in the buffer (bsc#1220845).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2021-47077: Fixed a NULL pointer dereference when in shost_data (bsc#1220861).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work (bsc#1212514).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52530: Fixed a potential key use-after-free in wifi mac80211 (bsc#1220930).\n- CVE-2023-52531: Fixed a memory corruption issue in iwlwifi (bsc#1220931).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get and nfc_llcp_sock_get_sn (bsc#1220831).\n- CVE-2024-26585: Fixed race between tx work scheduling and socket close (bsc#1220187).\n- CVE-2023-52340: Fixed ICMPv6 “Packet Too Big” packets force a DoS of the Linux kernel by forcing 100% CPU (bsc#1219295).\n- CVE-2024-0607: Fixed 64-bit load issue in  nft_byteorder_eval (bsc#1218915).\n- CVE-2024-26622: Fixed UAF write bug in tomoyo_write_control (bsc#1220825).\n- CVE-2021-46921: Fixed ordering in queued_write_lock_slowpath (bsc#1220468).\n- CVE-2021-46932: Fixed missing work initialization before device registration (bsc#1220444)\n- CVE-2023-52451: Fixed access beyond end of drmem array (bsc#1220250).\n- CVE-2021-46953: Fixed a corruption in interrupt mappings on watchdow probe failure (bsc#1220599).\n- CVE-2023-52449: Fixed gluebi NULL pointer dereference caused by ftl notifier (bsc#1220238).\n- CVE-2023-52475: Fixed use-after-free in powermate_config_complete (bsc#1220649)\n- CVE-2023-52478: Fixed kernel crash on receiver USB disconnect (bsc#1220796)\n- CVE-2019-25162: Fixed a potential use after free (bsc#1220409).\n- CVE-2020-36784: Fixed reference leak when pm_runtime_get_sync fails (bsc#1220570).\n- CVE-2021-47054: Fixed a bug to put child node before return (bsc#1220767).\n- CVE-2021-46924: Fixed fix memory leak in device probe and remove (bsc#1220459)\n- CVE-2021-46915: Fixed a bug to avoid possible divide error in nft_limit_init (bsc#1220436).\n- CVE-2021-46906: Fixed an info leak in hid_submit_ctrl (bsc#1220421).\n- CVE-2023-52445: Fixed use after free on context disconnection (bsc#1220241).\n- CVE-2020-36777: Fixed a memory leak in dvb_media_device_free (bsc#1220526).\n- CVE-2023-52443: Fixed crash when parsed profile name is empty (bsc#1220240).\n- CVE-2023-46343: Fixed a NULL pointer dereference in send_acknowledge (CVE-2023-46343).\n- CVE-2021-46992: Fixed a bug to avoid overflows in nft_hash_buckets (bsc#1220638).\n- CVE-2021-47013: Fixed a use after free in emac_mac_tx_buf_send (bsc#1220641).\n- CVE-2021-46991: Fixed a use-after-free in i40e_client_subtask (bsc#1220575).\n- CVE-2024-26595: Fixed NULL pointer dereference in  error path (bsc#1220344).\n- CVE-2024-1151: Fixed unlimited number of recursions from action sets (bsc#1219835).\n- CVE-2023-52464: Fixed possible out-of-bounds string access (bsc#1220330)\n- CVE-2024-23849: Fixed array-index-out-of-bounds in rds_cmsg_recv (bsc#1219127).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n\nThe following non-security bugs were fixed:\n\n- ASN.1: Fix check for strdup() success (git-fixes).\n- audit: fix possible soft lockup in __audit_inode_child() (git-fixes).\n- Bluetooth: hci_bcsp: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- Bluetooth: hci_h5: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- Bluetooth: hci_ll: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- Bluetooth: hci_qca: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- bnx2x: Fix PF-VF communication over multi-cos queues (git-fixes).\n- e1000: fix memory leaks (git-fixes).\n- gve: Fix skb truesize underestimation (git-fixes).\n- igb: clean up in all error paths when enabling SR-IOV (git-fixes).\n- igb: Fix constant media auto sense switching when no cable is connected (git-fixes).\n- ipv6: Fix handling of LLA with VRF and sockets bound to VRF (git-fixes).\n- ipv6: fix typos in __ip6_finish_output() (git-fixes).\n- ixgbe: protect TX timestamping from API misuse (git-fixes).\n- kcm: Call strp_stop before strp_done in kcm_attach (git-fixes).\n- kcm: fix strp_init() order and cleanup (git-fixes).\n- KVM: s390: vsie: fix race during shadow creation (git-fixes bsc#1220613).\n- KVM: VMX: Move VERW closer to VMentry for MDS mitigation (git-fixes).\n- KVM: VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH (git-fixes).\n- KVM: x86: add support for CPUID leaf 0x80000021 (git-fixes).\n- KVM: x86: Move open-coded CPUID leaf 0x80000021 EAX bit propagation code (git-fixes).\n- KVM: x86: synthesize CPUID leaf 0x80000021h if useful (git-fixes).\n- KVM: x86: work around QEMU issue with synthetic CPUID leaves (git-fixes).\n- locking/barriers: Introduce smp_cond_load_relaxed() and atomic_cond_read_relaxed() (bsc#1220468 bsc#1050549).\n- md: bypass block throttle for superblock update (git-fixes).\n- media: coda: constify platform_device_id (git-fixes).\n- media: coda: explicitly request exclusive reset control (git-fixes).\n- media: coda: reduce iram size to leave space for suspend to ram (git-fixes).\n- media: coda: reuse coda_s_fmt_vid_cap to propagate format in coda_s_fmt_vid_out (git-fixes).\n- media: coda: set min_buffers_needed (git-fixes).\n- media: coda: wake up capture queue on encoder stop after output streamoff (git-fixes).\n- media: dvb-usb: Add memory free on error path in dw2102_probe() (git-fixes).\n- media: dvb-usb: dw2102: fix uninit-value in su3000_read_mac_address (git-fixes).\n- media: dvb-usb: m920x: Fix a potential memory leak in m920x_i2c_xfer() (git-fixes).\n- media: dw2102: Fix memleak on sequence of probes (git-fixes).\n- media: dw2102: Fix use after free (git-fixes).\n- media: dw2102: make dvb_usb_device_description structures const (git-fixes).\n- media: m920x: do not use stack on USB reads (git-fixes).\n- media: rc: do not remove first bit if leader pulse is present (git-fixes).\n- media: rc: ir-rc6-decoder: enable toggle bit for Kathrein RCU-676 remote (git-fixes).\n- media: usb: dvd-usb: fix uninit-value bug in dibusb_read_eeprom_byte() (git-fixes).\n- media: uvcvideo: Set capability in s_param (git-fixes).\n- net: bonding: debug: avoid printing debug logs when bond is not notifying peers (git-fixes).\n- net: fec: add missed clk_disable_unprepare in remove (git-fixes).\n- net: fec: Better handle pm_runtime_get() failing in .remove() (git-fixes).\n- net: fec: fix clock count mis-match (git-fixes).\n- net: fec: fix use-after-free in fec_drv_remove (git-fixes).\n- net: hisilicon: Fix dma_map_single failed on arm64 (git-fixes).\n- net: hisilicon: fix hip04-xmit never return TX_BUSY (git-fixes).\n- net: hisilicon: Fix usage of uninitialized variable in function mdio_sc_cfg_reg_write() (git-fixes).\n- net: hisilicon: make hip04_tx_reclaim non-reentrant (git-fixes).\n- net: hns3: add compatible handling for MAC VLAN switch parameter configuration (git-fixes).\n- net: hns3: not allow SSU loopback while execute ethtool -t dev (git-fixes).\n- net: lpc-enet: fix printk format strings (git-fixes).\n- net: nfc: llcp: Add lock when modifying device list (git-fixes).\n- net: phy: dp83867: enable robust auto-mdix (git-fixes).\n- net: phy: initialise phydev speed and duplex sanely (git-fixes).\n- net: sfp: add mutex to prevent concurrent state checks (git-fixes).\n- net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ context (git-fixes).\n- net: usb: dm9601: fix wrong return value in dm9601_mdio_read (git-fixes).\n- net/mlx5e: ethtool, Avoid setting speed to 56GBASE when autoneg off (git-fixes).\n- net/sched: tcindex: search key must be 16 bits (git-fixes).\n- nfsd: Do not refuse to serve out of cache (bsc#1220957).\n- PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device (git-fixes).\n- Revert 'md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d' (git-fixes).\n- Revert 'wcn36xx: Disable bmps when encryption is disabled' (git-fixes).\n- s390: use the correct count for __iowrite64_copy() (git-fixes bsc#1220607).\n- stmmac: fix potential division by 0 (git-fixes).\n- tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd (bsc#1218450).\n- usb: host: fotg210: fix the actual_length of an iso packet (git-fixes).\n- usb: host: fotg210: fix the endpoint's transactional opportunities calculation (git-fixes).\n- usb: hub: check for alternate port before enabling A_ALT_HNP_SUPPORT (bsc#1218527).\n- usb: musb: dsps: Fix the probe error path (git-fixes).\n- usb: musb: musb_dsps: request_irq() after initializing musb (git-fixes).\n- usb: musb: tusb6010: check return value after calling platform_get_resource() (git-fixes).\n- usb: typec: tcpci: clear the fault status bit (git-fixes).\n- wcn36xx: Fix (QoS) null data frame bitrate/modulation (git-fixes).\n- wcn36xx: Fix discarded frames due to wrong sequence number (git-fixes).\n- wcn36xx: fix RX BD rate mapping for 5GHz legacy rates (git-fixes).\n- x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix (git-fixes).\n- x86/bugs: Add asm helpers for executing VERW (bsc#1213456).\n- x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key (git-fixes). Also add mds_user_clear to kABI severity as it's used purely for mitigation so it's low risk.\n- x86/cpu, kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf (git-fixes).\n- x86/entry_32: Add VERW just before userspace transition (git-fixes).\n- x86/entry_64: Add VERW just before userspace transition (git-fixes).\n","status":"published","published":"2024-03-18T14:06:14Z","modified":"2026-02-04T02:31:11.762395Z","updated_at":"2026-11-02T15:53:54.239786Z"},{"id":"SUSE-SU-2024:0926-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP2 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2021-47078: Fixed a bug by clearing all QP fields if creation failed (bsc#1220863)\n- CVE-2021-47076: Fixed a bug by returning CQE error if invalid lkey was supplied (bsc#1220860)\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2023-52569: Fixed a bug in btrfs by remoning BUG() after failure to insert delayed dir index item (bsc#1220918).\n- CVE-2023-52482: Fixed a bug by adding SRSO mitigation for Hygon processors (bsc#1220735).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2022-48627: Fixed a memory overlapping when deleting chars in the buffer (bsc#1220845).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2021-46934: Fixed a bug by validating user data in compat ioctl (bsc#1220469).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52530: Fixed a potential key use-after-free in wifi mac80211 (bsc#1220930).\n- CVE-2023-52531: Fixed a memory corruption issue in iwlwifi (bsc#1220931).\n- CVE-2021-47083: Fixed a global-out-of-bounds issue in mediatek: (bsc#1220917).\n- CVE-2024-26607: Fixed a probing race issue in sii902x: (bsc#1220736).\n- CVE-2024-26589: Fixed out of bounds read due to variable offset alu on PTR_TO_FLOW_KEYS (bsc#1220255).\n- CVE-2021-47005: Fixed a NULL pointer dereference for -\u003eget_features() (bsc#1220660).\n- CVE-2024-26585: Fixed race between tx work scheduling and socket close  (bsc#1220187).\n- CVE-2023-52340: Fixed ICMPv6 “Packet Too Big” packets force a DoS of the Linux kernel by forcing 100% CPU (bsc#1219295).\n- CVE-2024-0607: Fixed 64-bit load issue in  nft_byteorder_eval() (bsc#1218915).\n- CVE-2021-47060: Fixed a bug in KVM by stop looking for coalesced MMIO zones if the bus is destroyed (bsc#1220742).\n- CVE-2024-26622: Fixed UAF write bug in tomoyo_write_control() (bsc#1220825).\n- CVE-2023-52451: Fixed access beyond end of drmem array  (bsc#1220250).\n- CVE-2021-46932: Fixed missing work initialization before device registration (bsc#1220444)\n- CVE-2023-52463: Fixed null pointer dereference in efivarfs (bsc#1220328).\n- CVE-2021-47012: Fixed a use after free in siw_alloc_mr (bsc#1220627).\n- CVE-2023-52449: Fixed gluebi NULL pointer dereference caused by ftl notifier  (bsc#1220238).\n- CVE-2023-52475: Fixed use-after-free in powermate_config_complete (bsc#1220649)\n- CVE-2023-52478: Fixed kernel crash on receiver USB disconnect (bsc#1220796)\n- CVE-2021-46989: Fixed a bug by preventing corruption in shrinking truncate in hfsplus (bsc#1220737).\n- CVE-2021-46915: Fixed a bug to avoid possible divide error in nft_limit_init (bsc#1220436).\n- CVE-2021-46924: Fixed fix memory leak in device probe and remove (bsc#1220459)\n- CVE-2019-25162: Fixed a potential use after free (bsc#1220409).\n- CVE-2020-36784: Fixed reference leak when pm_runtime_get_sync fails (bsc#1220570).\n- CVE-2021-47061: Fixed a bug in KVM by destroy I/O bus devices on unregister failure _after_  sync'ing SRCU (bsc#1220745).\n- CVE-2023-52445: Fixed use after free on context disconnection (bsc#1220241).\n- CVE-2023-46343: Fixed a NULL pointer dereference in send_acknowledge() (CVE-2023-46343).\n- CVE-2023-52439: Fixed use-after-free in uio_open (bsc#1220140).\n- CVE-2023-52443: Fixed crash when parsed profile name is empty  (bsc#1220240).\n- CVE-2024-26602: Fixed overall slowdowns with sys_membarrier (bsc1220398).\n- CVE-2024-26593: Fixed block process call transactions (bsc#1220009).\n- CVE-2021-47013: Fixed a use after free in emac_mac_tx_buf_send (bsc#1220641).\n- CVE-2024-26586: Fixed stack corruption (bsc#1220243).\n- CVE-2024-26595: Fixed NULL pointer dereference in  error path (bsc#1220344).\n- CVE-2023-52448: Fixed kernel NULL pointer dereference in gfs2_rgrp_dump  (bsc#1220253).\n- CVE-2024-1151: Fixed unlimited number of recursions from action  sets (bsc#1219835).\n- CVE-2024-23849: Fixed array-index-out-of-bounds in rds_cmsg_recv  (bsc#1219127).\n- CVE-2024-0340: Fixed information disclosure in vhost/vhost.c:vhost_new_msg() (bsc#1218689).\n- CVE-2023-51042: Fixed use-after-free in amdgpu_cs_wait_all_fences in drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c (bsc#1219128).\n\nThe following non-security bugs were fixed:\n\n- EDAC/thunderx: Fix possible out-of-bounds string access (bsc#1220330)\n- KVM: Destroy target device if coalesced MMIO unregistration fails (git-fixes).\n- KVM: mmio: Fix use-after-free Read in kvm_vm_ioctl_unregister_coalesced_mmio (git-fixes).\n- KVM: VMX: Move VERW closer to VMentry for MDS mitigation (git-fixes).\n- KVM: VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH (git-fixes).\n- KVM: x86: add support for CPUID leaf 0x80000021 (git-fixes).\n- KVM: x86: Move open-coded CPUID leaf 0x80000021 EAX bit propagation code (git-fixes).\n- KVM: x86: synthesize CPUID leaf 0x80000021h if useful (git-fixes).\n- KVM: x86: work around QEMU issue with synthetic CPUID leaves (git-fixes).\n- x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix (git-fixes).\n- x86/bugs: Add asm helpers for executing VERW (git-fixes).\n- x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key (git-fixes).\n- x86/cpu, kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf (git-fixes).\n- x86/entry_32: Add VERW just before userspace transition (git-fixes).\n- x86/entry_64: Add VERW just before userspace transition (git-fixes).\n","status":"published","published":"2024-03-18T14:07:16Z","modified":"2026-02-04T04:11:41.369688Z","updated_at":"2026-11-02T15:53:54.239786Z"},{"id":"SUSE-SU-2024:0975-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 Azure kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP (bsc#1220340).\n- CVE-2021-47078: Fixed a bug by clearing all QP fields if creation failed (bsc#1220863)\n- CVE-2021-47076: Fixed a bug by returning CQE error if invalid lkey was supplied (bsc#1220860)\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2023-52482: Fixed a bug by adding SRSO mitigation for Hygon processors (bsc#1220735).\n- CVE-2022-48627: Fixed a memory overlapping when deleting chars in the buffer (bsc#1220845).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2021-47077: Fixed a NULL pointer dereference when in shost_data (bsc#1220861).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2021-33200: Fixed a leakage of uninitialized bpf stack under speculation. (bsc#1186484)\n- CVE-2023-52530: Fixed a potential key use-after-free in wifi mac80211 (bsc#1220930).\n- CVE-2023-52531: Fixed a memory corruption issue in iwlwifi (bsc#1220931).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2024-26585: Fixed race between tx work scheduling and socket close (bsc#1220187).\n- CVE-2023-52340: Fixed ICMPv6 “Packet Too Big” packets force a DoS of the Linux kernel by forcing 100% CPU (bsc#1219295).\n- CVE-2024-0607: Fixed 64-bit load issue in  nft_byteorder_eval() (bsc#1218915).\n- CVE-2024-26622: Fixed UAF write bug in tomoyo_write_control() (bsc#1220825).\n- CVE-2021-46921: Fixed ordering in queued_write_lock_slowpath (bsc#1220468).\n- CVE-2021-46932: Fixed missing work initialization before device registration (bsc#1220444)\n- CVE-2023-52451: Fixed access beyond end of drmem array  (bsc#1220250).\n- CVE-2021-46953: Fixed a corruption in interrupt mappings on watchdow probe failure (bsc#1220599).\n- CVE-2023-52449: Fixed gluebi NULL pointer dereference caused by ftl notifier  (bsc#1220238).\n- CVE-2023-52475: Fixed use-after-free in powermate_config_complete (bsc#1220649)\n- CVE-2023-52478: Fixed kernel crash on receiver USB disconnect (bsc#1220796)\n- CVE-2019-25162: Fixed a potential use after free (bsc#1220409).\n- CVE-2020-36784: Fixed reference leak when pm_runtime_get_sync fails (bsc#1220570).\n- CVE-2021-47054: Fixed a bug to put child node before return (bsc#1220767).\n- CVE-2021-46924: Fixed fix memory leak in device probe and remove (bsc#1220459)\n- CVE-2021-46915: Fixed a bug to avoid possible divide error in nft_limit_init (bsc#1220436).\n- CVE-2021-46906: Fixed an info leak in hid_submit_ctrl (bsc#1220421).\n- CVE-2023-52445: Fixed use after free on context disconnection (bsc#1220241).\n- CVE-2020-36777: Fixed a memory leak in dvb_media_device_free (bsc#1220526).\n- CVE-2023-52443: Fixed crash when parsed profile name is empty (bsc#1220240).\n- CVE-2023-46343: Fixed a NULL pointer dereference in send_acknowledge() (CVE-2023-46343).\n- CVE-2021-46992: Fixed a bug to avoid overflows in nft_hash_buckets (bsc#1220638).\n- CVE-2021-47013: Fixed a use after free in emac_mac_tx_buf_send (bsc#1220641).\n- CVE-2021-46991: Fixed a use-after-free in i40e_client_subtask (bsc#1220575).\n- CVE-2024-26595: Fixed NULL pointer dereference in  error path (bsc#1220344).\n- CVE-2024-1151: Fixed unlimited number of recursions from action sets (bsc#1219835).\n- CVE-2023-52464: Fixed possible out-of-bounds string access (bsc#1220330)\n- CVE-2024-23849: Fixed array-index-out-of-bounds in rds_cmsg_recv (bsc#1219127).\n\nThe following non-security bugs were fixed:\n\n- ASN.1: Fix check for strdup() success (git-fixes).\n- audit: fix possible soft lockup in __audit_inode_child() (git-fixes).\n- Bluetooth: hci_bcsp: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- Bluetooth: hci_h5: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- Bluetooth: hci_ll: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- Bluetooth: hci_qca: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- bnx2x: Fix PF-VF communication over multi-cos queues (git-fixes).\n- doc/README.KSYMS: Add to repo.\n- e1000: fix memory leaks (git-fixes).\n- gve: Fix skb truesize underestimation (git-fixes).\n- igb: clean up in all error paths when enabling SR-IOV (git-fixes).\n- igb: Fix constant media auto sense switching when no cable is connected (git-fixes).\n- ipv6: Fix handling of LLA with VRF and sockets bound to VRF (git-fixes).\n- ipv6: fix typos in __ip6_finish_output() (git-fixes).\n- ixgbe: protect TX timestamping from API misuse (git-fixes).\n- kcm: Call strp_stop before strp_done in kcm_attach (git-fixes).\n- kcm: fix strp_init() order and cleanup (git-fixes).\n- KVM: s390: vsie: fix race during shadow creation (git-fixes bsc#1220613).\n- KVM: VMX: Move VERW closer to VMentry for MDS mitigation (git-fixes).\n- KVM: VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH (git-fixes).\n- KVM: x86: add support for CPUID leaf 0x80000021 (git-fixes).\n- KVM: x86: Move open-coded CPUID leaf 0x80000021 EAX bit propagation code (git-fixes).\n- KVM: x86: synthesize CPUID leaf 0x80000021h if useful (git-fixes).\n- KVM: x86: work around QEMU issue with synthetic CPUID leaves (git-fixes).\n- locking/barriers: Introduce smp_cond_load_relaxed() and atomic_cond_read_relaxed() (bsc#1220468 bsc#1050549).\n- md: bypass block throttle for superblock update (git-fixes).\n- media: coda: constify platform_device_id (git-fixes).\n- media: coda: explicitly request exclusive reset control (git-fixes).\n- media: coda: reduce iram size to leave space for suspend to ram (git-fixes).\n- media: coda: reuse coda_s_fmt_vid_cap to propagate format in coda_s_fmt_vid_out (git-fixes).\n- media: coda: set min_buffers_needed (git-fixes).\n- media: coda: wake up capture queue on encoder stop after output streamoff (git-fixes).\n- media: dvb-usb: Add memory free on error path in dw2102_probe() (git-fixes).\n- media: dvb-usb: dw2102: fix uninit-value in su3000_read_mac_address (git-fixes).\n- media: dvb-usb: m920x: Fix a potential memory leak in m920x_i2c_xfer() (git-fixes).\n- media: dw2102: Fix memleak on sequence of probes (git-fixes).\n- media: dw2102: Fix use after free (git-fixes).\n- media: dw2102: make dvb_usb_device_description structures const (git-fixes).\n- media: m920x: do not use stack on USB reads (git-fixes).\n- media: rc: do not remove first bit if leader pulse is present (git-fixes).\n- media: rc: ir-rc6-decoder: enable toggle bit for Kathrein RCU-676 remote (git-fixes).\n- media: usb: dvd-usb: fix uninit-value bug in dibusb_read_eeprom_byte() (git-fixes).\n- media: uvcvideo: Set capability in s_param (git-fixes).\n- net: bonding: debug: avoid printing debug logs when bond is not notifying peers (git-fixes).\n- net: fec: add missed clk_disable_unprepare in remove (git-fixes).\n- net: fec: Better handle pm_runtime_get() failing in .remove() (git-fixes).\n- net: fec: fix clock count mis-match (git-fixes).\n- net: fec: fix use-after-free in fec_drv_remove (git-fixes).\n- net: hisilicon: Fix dma_map_single failed on arm64 (git-fixes).\n- net: hisilicon: fix hip04-xmit never return TX_BUSY (git-fixes).\n- net: hisilicon: Fix usage of uninitialized variable in function mdio_sc_cfg_reg_write() (git-fixes).\n- net: hisilicon: make hip04_tx_reclaim non-reentrant (git-fixes).\n- net: hns3: add compatible handling for MAC VLAN switch parameter configuration (git-fixes).\n- net: hns3: not allow SSU loopback while execute ethtool -t dev (git-fixes).\n- net: lpc-enet: fix printk format strings (git-fixes).\n- net: nfc: llcp: Add lock when modifying device list (git-fixes).\n- net: phy: dp83867: enable robust auto-mdix (git-fixes).\n- net: phy: initialise phydev speed and duplex sanely (git-fixes).\n- net: sfp: add mutex to prevent concurrent state checks (git-fixes).\n- net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ context (git-fixes).\n- net: usb: dm9601: fix wrong return value in dm9601_mdio_read (git-fixes).\n- net/mlx5e: ethtool, Avoid setting speed to 56GBASE when autoneg off (git-fixes).\n- net/sched: tcindex: search key must be 16 bits (git-fixes).\n- nfsd: Do not refuse to serve out of cache (bsc#1220957).\n- PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device (git-fixes).\n- s390: use the correct count for __iowrite64_copy() (git-fixes bsc#1220607).\n- stmmac: fix potential division by 0 (git-fixes).\n- tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd (bsc#1218450).\n- usb: host: fotg210: fix the actual_length of an iso packet (git-fixes).\n- usb: host: fotg210: fix the endpoint's transactional opportunities calculation (git-fixes).\n- usb: hub: check for alternate port before enabling A_ALT_HNP_SUPPORT (bsc#1218527).\n- usb: musb: dsps: Fix the probe error path (git-fixes).\n- usb: musb: musb_dsps: request_irq() after initializing musb (git-fixes).\n- usb: musb: tusb6010: check return value after calling platform_get_resource() (git-fixes).\n- usb: typec: tcpci: clear the fault status bit (git-fixes).\n- wcn36xx: Fix (QoS) null data frame bitrate/modulation (git-fixes).\n- wcn36xx: Fix discarded frames due to wrong sequence number (git-fixes).\n- wcn36xx: fix RX BD rate mapping for 5GHz legacy rates (git-fixes).\n- x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix (git-fixes).\n- x86/bugs: Add asm helpers for executing VERW (bsc#1213456).\n- x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key (git-fixes). Also add mds_user_clear to kABI severity as it's used purely for mitigation so it's low risk.\n- x86/cpu, kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf (git-fixes).\n- x86/entry_32: Add VERW just before userspace transition (git-fixes).\n- x86/entry_64: Add VERW just before userspace transition (git-fixes).\n","status":"published","published":"2024-03-22T11:01:39Z","modified":"2026-02-04T03:57:37.504419Z","updated_at":"2026-11-02T15:53:54.239786Z"},{"id":"SUSE-SU-2024:0976-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise SLE12SP5 RT kernel was updated to receive various security and bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2019-25162: Fixed a potential use after free (bsc#1220409).\n- CVE-2020-36777: Fixed a memory leak in dvb_media_device_free() (bsc#1220526).\n- CVE-2020-36784: Fixed reference leak when pm_runtime_get_sync fails (bsc#1220570).\n- CVE-2021-46906: Fixed an info leak in hid_submit_ctrl (bsc#1220421).\n- CVE-2021-46915: Fixed a bug to avoid possible divide error in nft_limit_init (bsc#1220436).\n- CVE-2021-46921: Fixed ordering in queued_write_lock_slowpath (bsc#1220468).\n- CVE-2021-46924: Fixed fix memory leak in device probe and remove (bsc#1220459)\n- CVE-2021-46932: Fixed missing work initialization before device registration (bsc#1220444)\n- CVE-2021-46953: Fixed a corruption in interrupt mappings on watchdow probe failure (bsc#1220599).\n- CVE-2021-46991: Fixed a use-after-free in i40e_client_subtask (bsc#1220575).\n- CVE-2021-46992: Fixed a bug to avoid overflows in nft_hash_buckets (bsc#1220638).\n- CVE-2021-47013: Fixed a use after free in emac_mac_tx_buf_send (bsc#1220641).\n- CVE-2021-47054: Fixed a bug to put child node before return (bsc#1220767).\n- CVE-2021-47076: Fixed a bug by returning CQE error if invalid lkey was supplied (bsc#1220860)\n- CVE-2021-47077: Fixed a NULL pointer dereference when in shost_data (bsc#1220861).\n- CVE-2021-47078: Fixed a bug by clearing all QP fields if creation failed (bsc#1220863)\n- CVE-2022-48627: Fixed a memory overlapping when deleting chars in the buffer (bsc#1220845).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-46343: Fixed a NULL pointer dereference in send_acknowledge() (CVE-2023-46343).\n- CVE-2023-52340: Fixed ICMPv6 “Packet Too Big” packets force a DoS of the Linux kernel by forcing 100% CPU (bsc#1219295).\n- CVE-2023-52429: Fixed potential DoS in dm_table_create in drivers/md/dm-table.c (bsc#1219827).\n- CVE-2023-52443: Fixed crash when parsed profile name is empty  (bsc#1220240).\n- CVE-2023-52445: Fixed use after free on context disconnection (bsc#1220241).\n- CVE-2023-52449: Fixed gluebi NULL pointer dereference caused by ftl notifier  (bsc#1220238).\n- CVE-2023-52451: Fixed access beyond end of drmem array  (bsc#1220250).\n- CVE-2023-52464: Fixed possible out-of-bounds string access (bsc#1220330)\n- CVE-2023-52475: Fixed use-after-free in powermate_config_complete (bsc#1220649)\n- CVE-2023-52478: Fixed kernel crash on receiver USB disconnect (bsc#1220796)\n- CVE-2023-52482: Fixed a bug by adding SRSO mitigation for Hygon processors (bsc#1220735).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2023-52530: Fixed a potential key use-after-free in wifi mac80211 (bsc#1220930).\n- CVE-2023-52531: Fixed a memory corruption issue in iwlwifi (bsc#1220931).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2024-0607: Fixed 64-bit load issue in  nft_byteorder_eval() (bsc#1218915).\n- CVE-2024-1151: Fixed unlimited number of recursions from action  sets (bsc#1219835).\n- CVE-2024-23849: Fixed array-index-out-of-bounds in rds_cmsg_recv  (bsc#1219127).\n- CVE-2024-23851: Fixed crash in copy_params in drivers/md/dm-ioctl.c (bsc#1219146).\n- CVE-2024-26585: Fixed race between tx work scheduling and socket close  (bsc#1220187).\n- CVE-2024-26595: Fixed NULL pointer dereference in  error path (bsc#1220344).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n- CVE-2024-26622: Fixed UAF write bug in tomoyo_write_control() (bsc#1220825).\n\nThe following non-security bugs were fixed:\n\n- [media] coda: simplify optional reset handling (git-fixes).\n- [media] media drivers: annotate fall-through (git-fixes).\n- [media] media: platform: coda: remove variable self assignment (git-fixes).\n- asn.1: fix check for strdup() success (git-fixes).\n- audit: fix possible soft lockup in __audit_inode_child() (git-fixes).\n- bluetooth: hci_bcsp: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- bluetooth: hci_h5: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- bluetooth: hci_ll: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- bluetooth: hci_qca: do not call kfree_skb() under spin_lock_irqsave() (git-fixes).\n- bnx2x: fix pf-vf communication over multi-cos queues (git-fixes).\n- doc/readme.ksyms: add to repo.++ kernel-source-rt.spec (revision 4)%define git_commit 1431ee6e1c7fc02206d6bd539f8bd8ec4ce61801release:    \u0026lt;release\u003e.g1431ee6this package provides the rpm macros and templates for kernel module packages++ kernel-source.spec.in (revision 4)this package provides the rpm macros and templates for kernel module packages\n- e1000: fix memory leaks (git-fixes).\n- gve: fix skb truesize underestimation (git-fixes).\n- igb: clean up in all error paths when enabling sr-iov (git-fixes).\n- igb: fix constant media auto sense switching when no cable is connected (git-fixes).\n- ipv6: fix handling of lla with vrf and sockets bound to vrf (git-fixes).\n- ipv6: fix typos in __ip6_finish_output() (git-fixes).\n- ixgbe: protect tx timestamping from api misuse (git-fixes).\n- kcm: call strp_stop before strp_done in kcm_attach (git-fixes).\n- kcm: fix strp_init() order and cleanup (git-fixes).\n- kernel-source: fix description typo\n- kvm: s390: vsie: fix race during shadow creation (git-fixes bsc#1220613).\n- kvm: vmx: move verw closer to vmentry for mds mitigation (git-fixes).\n- kvm: vmx: use bt+jnc, i.e. eflags.cf to select vmresume vs. vmlaunch (git-fixes).\n- kvm: x86: add support for cpuid leaf 0x80000021 (git-fixes).\n- kvm: x86: move open-coded cpuid leaf 0x80000021 eax bit propagation code (git-fixes).\n- kvm: x86: synthesize cpuid leaf 0x80000021h if useful (git-fixes).\n- kvm: x86: work around qemu issue with synthetic cpuid leaves (git-fixes).\n- locking/barriers: introduce smp_cond_load_relaxed() and atomic_cond_read_relaxed() (bsc#1220468 bsc#1050549).\n- media: coda: constify platform_device_id (git-fixes).\n- media: coda: explicitly request exclusive reset control (git-fixes).\n- media: coda: reduce iram size to leave space for suspend to ram (git-fixes).\n- media: coda: reuse coda_s_fmt_vid_cap to propagate format in coda_s_fmt_vid_out (git-fixes).\n- media: coda: set min_buffers_needed (git-fixes).\n- media: coda: wake up capture queue on encoder stop after output streamoff (git-fixes).\n- media: dvb-usb: add memory free on error path in dw2102_probe() (git-fixes).\n- media: dvb-usb: dw2102: fix uninit-value in su3000_read_mac_address (git-fixes).\n- media: dvb-usb: m920x: fix a potential memory leak in m920x_i2c_xfer() (git-fixes).\n- media: dw2102: fix memleak on sequence of probes (git-fixes).\n- media: dw2102: fix use after free (git-fixes).\n- media: dw2102: make dvb_usb_device_description structures const (git-fixes).\n- media: m920x: do not use stack on usb reads (git-fixes).\n- media: rc: do not remove first bit if leader pulse is present (git-fixes).\n- media: rc: ir-rc6-decoder: enable toggle bit for kathrein rcu-676 remote (git-fixes).\n- media: usb: dvd-usb: fix uninit-value bug in dibusb_read_eeprom_byte() (git-fixes).\n- media: uvcvideo: set capability in s_param (git-fixes).\n- mkspec: use variant in constraints template constraints are not applied consistently with kernel package variants. add variant to the constraints template as appropriate, and expand it in mkspec.\n- net/mlx5e: ethtool, avoid setting speed to 56gbase when autoneg off (git-fixes).\n- net/sched: tcindex: search key must be 16 bits (git-fixes).\n- net: bonding: debug: avoid printing debug logs when bond is not notifying peers (git-fixes).\n- net: fec: add missed clk_disable_unprepare in remove (git-fixes).\n- net: fec: better handle pm_runtime_get() failing in .remove() (git-fixes).\n- net: fec: fix clock count mis-match (git-fixes).\n- net: fec: fix use-after-free in fec_drv_remove (git-fixes).\n- net: hisilicon: fix dma_map_single failed on arm64 (git-fixes).\n- net: hisilicon: fix hip04-xmit never return tx_busy (git-fixes).\n- net: hisilicon: fix usage of uninitialized variable in function mdio_sc_cfg_reg_write() (git-fixes).\n- net: hisilicon: make hip04_tx_reclaim non-reentrant (git-fixes).\n- net: hns3: add compatible handling for mac vlan switch parameter configuration (git-fixes).\n- net: hns3: not allow ssu loopback while execute ethtool -t dev (git-fixes).\n- net: lpc-enet: fix printk format strings (git-fixes).\n- net: nfc: llcp: add lock when modifying device list (git-fixes).\n- net: phy: dp83867: enable robust auto-mdix (git-fixes).\n- net: phy: initialise phydev speed and duplex sanely (git-fixes).\n- net: sfp: add mutex to prevent concurrent state checks (git-fixes).\n- net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in irq context (git-fixes).\n- net: usb: dm9601: fix wrong return value in dm9601_mdio_read (git-fixes).\n- nfsd: do not refuse to serve out of cache (bsc#1220957).\n- pci: prevent xhci driver from claiming amd vangogh usb3 drd device (git-fixes).\n- revert 'md/raid5: wait for md_sb_change_pending in raid5d' (git-fixes).\n- revert 'wcn36xx: disable bmps when encryption is disabled' (git-fixes).\n- rpm/constraints.in: set jobs for riscv to 8 the same workers are used for x86 and riscv and the riscv builds take ages. so align the riscv jobs count to x86.\n- rpm/kernel-binary.spec.in: install scripts/gdb when enabled in config (bsc#1219653) they are put into -devel subpackage. and a proper link to /usr/share/gdb/auto-load/ is created.\n- rpm/mkspec: sort entries in _multibuild otherwise it creates unnecessary diffs when tar-up-ing. it's of course due to readdir() using 'random' order as served by the underlying filesystem. see for example: https://build.opensuse.org/request/show/1144457/changes\n- rpm: use run_if_exists for all external scriptlets with that the scriptlets do not need to be installed for build.\n- s390: use the correct count for __iowrite64_copy() (git-fixes bsc#1220607).\n- stmmac: fix potential division by 0 (git-fixes).\n- tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd (bsc#1218450).\n- usb: host: fotg210: fix the actual_length of an iso packet (git-fixes).\n- usb: host: fotg210: fix the endpoint's transactional opportunities calculation (git-fixes).\n- usb: hub: check for alternate port before enabling a_alt_hnp_support (bsc#1218527).\n- usb: musb: dsps: fix the probe error path (git-fixes).\n- usb: musb: musb_dsps: request_irq() after initializing musb (git-fixes).\n- usb: musb: tusb6010: check return value after calling platform_get_resource() (git-fixes).\n- usb: typec: tcpci: clear the fault status bit (git-fixes).\n- wcn36xx: fix (qos) null data frame bitrate/modulation (git-fixes).\n- wcn36xx: fix discarded frames due to wrong sequence number (git-fixes).\n- wcn36xx: fix rx bd rate mapping for 5ghz legacy rates (git-fixes).\n- x86/asm: add _asm_rip() macro for x86-64 (%rip) suffix (git-fixes).\n- x86/bugs: add asm helpers for executing verw (bsc#1213456).\n- x86/bugs: use alternative() instead of mds_user_clear static key (git-fixes). also add mds_user_clear to kabi severity as it's used purely for mitigation so it's low risk.\n- x86/cpu, kvm: move x86_feature_lfence_rdtsc to its native leaf (git-fixes).\n- x86/entry_32: add verw just before userspace transition (git-fixes).\n- x86/entry_64: Add VERW just before userspace transition (git-fixes).\n","status":"published","published":"2024-03-22T11:19:37Z","modified":"2026-02-04T03:43:57.908146Z","updated_at":"2026-11-02T15:53:54.239786Z"},{"id":"SUSE-SU-2024:1320-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2021-46925: Fixed kernel panic caused by race of smc_sock (bsc#1220466).\n- CVE-2021-46926: Fixed bug when detecting controllers in ALSA/hda/intel-sdw-acpi (bsc#1220478).\n- CVE-2021-46927: Fixed assertion bug in nitro_enclaves: Use get_user_pages_unlocked() (bsc#1220443).\n- CVE-2021-46929: Fixed use-after-free issue in sctp_sock_dump() (bsc#1220482).\n- CVE-2021-46930: Fixed usb/mtu3 list_head check warning (bsc#1220484).\n- CVE-2021-46931: Fixed wrong type casting in mlx5e_tx_reporter_dump_sq() (bsc#1220486).\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47082: Fixed ouble free in tun_free_netdev() (bsc#1220969).\n- CVE-2021-47087: Fixed incorrect page free bug in tee/optee (bsc#1220954).\n- CVE-2021-47091: Fixed locking in ieee80211_start_ap()) error path (bsc#1220959).\n- CVE-2021-47093: Fixed memleak on registration failure in intel_pmc_core (bsc#1220978).\n- CVE-2021-47094: Fixed possible memory leak in KVM x86/mmu (bsc#1221551).\n- CVE-2021-47095: Fixed missing initialization in ipmi/ssif (bsc#1220979).\n- CVE-2021-47096: Fixed uninitalized user_pversion in ALSA rawmidi (bsc#1220981).\n- CVE-2021-47097: Fixed stack out of bound access in elantech_change_report_id() (bsc#1220982).\n- CVE-2021-47098: Fixed integer overflow/underflow in hysteresis calculations hwmon: (lm90) (bsc#1220983).\n- CVE-2021-47099: Fixed BUG_ON assertion in veth when skb entering GRO are cloned (bsc#1220955).\n- CVE-2021-47100: Fixed UAF when uninstall in ipmi (bsc#1220985).\n- CVE-2021-47101: Fixed uninit-value in asix_mdio_read() (bsc#1220987).\n- CVE-2021-47102: Fixed incorrect structure access In line: upper = info-\u003eupper_dev in net/marvell/prestera (bsc#1221009).\n- CVE-2021-47104: Fixed memory leak in qib_user_sdma_queue_pkts() (bsc#1220960).\n- CVE-2021-47105: Fixed potential memory leak in ice/xsk (bsc#1220961).\n- CVE-2021-47107: Fixed READDIR buffer overflow in NFSD (bsc#1220965).\n- CVE-2021-47108: Fixed possible NULL pointer dereference for mtk_hdmi_conf in drm/mediatek (bsc#1220986).\n- CVE-2022-48626: Fixed a potential use-after-free on remove path moxart (bsc#1220366).\n- CVE-2022-48629: Fixed possible memory leak in qcom-rng (bsc#1220989).\n- CVE-2022-48630: Fixed infinite loop on requests not multiple of WORD_SZ in crypto: qcom-rng (bsc#1220990).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-52450: Fixed NULL pointer dereference issue in upi_fill_topology() (bsc#1220237).\n- CVE-2023-52454: Fixed a kernel panic when host sends an invalid H2C PDU length (bsc#1220320).\n- CVE-2023-52469: Fixed a use-after-free in kv_parse_power_table (bsc#1220411).\n- CVE-2023-52470: Fixed null-ptr-deref in radeon_crtc_init() (bsc#1220413).\n- CVE-2023-52474: Fixed a vulnerability with non-PAGE_SIZE-end multi-iovec user SDMA requests (bsc#1220445).\n- CVE-2023-52477: Fixed USB Hub accesses to uninitialized BOS descriptors (bsc#1220790).\n- CVE-2023-52492: Fixed a null-pointer-dereference in channel unregistration function __dma_async_device_channel_register() (bsc#1221276).\n- CVE-2023-52497: Fixed data corruption in erofs (bsc#1220879).\n- CVE-2023-52501: Fixed possible memory corruption in ring-buffer (bsc#1220885).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2023-52504: Fixed possible out-of bounds in apply_alternatives() on a 5-level paging machine (bsc#1221553).\n- CVE-2023-52507: Fixed possible shift-out-of-bounds in nfc/nci (bsc#1220833).\n- CVE-2023-52508: Fixed null pointer dereference in nvme_fc_io_getuuid() (bsc#1221015).\n- CVE-2023-52509: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1220836).\n- CVE-2023-52510: Fixed a potential UAF in ca8210_probe() (bsc#1220898).\n- CVE-2023-52511: Fixed possible memory corruption in spi/sun6i (bsc#1221012).\n- CVE-2023-52513: Fixed connection failure handling  in RDMA/siw (bsc#1221022).\n- CVE-2023-52515: Fixed possible use-after-free in RDMA/srp (bsc#1221048).\n- CVE-2023-52517: Fixed race between DMA RX transfer completion and RX FIFO drain in spi/sun6i (bsc#1221055).\n- CVE-2023-52519: Fixed possible overflow in HID/intel-ish-hid/ipc (bsc#1220920).\n- CVE-2023-52520: Fixed reference leak in platform/x86/think-lmi (bsc#1220921).\n- CVE-2023-52523: Fixed wrong redirects to non-TCP sockets in bpf (bsc#1220926).\n- CVE-2023-52524: Fixed possible corruption in nfc/llcp (bsc#1220927).\n- CVE-2023-52525: Fixed out of bounds check mwifiex_process_rx_packet() (bsc#1220840).\n- CVE-2023-52528: Fixed uninit-value access in __smsc75xx_read_reg() (bsc#1220843).\n- CVE-2023-52529: Fixed a potential memory leak in sony_probe() (bsc#1220929).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52564: Reverted invalid fix for UAF in gsm_cleanup_mux() (bsc#1220938).\n- CVE-2023-52566: Fixed potential use after free in nilfs_gccache_submit_read_data() (bsc#1220940).\n- CVE-2023-52567: Fixed possible Oops in  serial/8250_port: when using IRQ polling (irq = 0) (bsc#1220839).\n- CVE-2023-52569: Fixed a bug in btrfs by remoning BUG() after failure to insert delayed dir index item (bsc#1220918).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2023-52575: Fixed SBPB enablement for spec_rstack_overflow=off (bsc#1220871).\n- CVE-2023-52576: Fixed potential use after free in memblock_isolate_range() (bsc#1220872).\n- CVE-2023-52582: Fixed possible oops in netfs (bsc#1220878).\n- CVE-2023-52583: Fixed deadlock or deadcode of misusing dget() inside ceph (bsc#1221058).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-52621: Fixed missing asserion in bpf (bsc#1222073).\n- CVE-2024-25742: Fixed insufficient validation during #VC instruction emulation in x86/sev (bsc#1221725).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n\nThe following non-security bugs were fixed:\n\n- doc/README.SUSE: Update information about module support status (jsc#PED-5759)\n- group-source-files.pl: Quote filenames (boo#1221077).\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (bsc#1222619).\n","status":"published","published":"2024-04-16T16:04:08Z","modified":"2026-02-04T03:54:32.205955Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1321-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-25742: Fixed insufficient validation during #VC instruction emulation in x86/sev (bsc#1221725).\n- CVE-2023-52519: Fixed possible overflow in HID/intel-ish-hid/ipc (bsc#1220920).\n- CVE-2023-52529: Fixed a potential memory leak in sony_probe() (bsc#1220929).\n- CVE-2023-52474: Fixed a vulnerability with non-PAGE_SIZE-end multi-iovec user SDMA requests (bsc#1220445).\n- CVE-2023-52513: Fixed connection failure handling  in RDMA/siw (bsc#1221022).\n- CVE-2023-52515: Fixed possible use-after-free in RDMA/srp (bsc#1221048).\n- CVE-2023-52564: Reverted invalid fix for UAF in gsm_cleanup_mux() (bsc#1220938).\n- CVE-2023-52447: Fixed map_fd_put_ptr() signature kABI workaround  (bsc#1220251).\n- CVE-2023-52510: Fixed a potential UAF in ca8210_probe() (bsc#1220898).\n- CVE-2023-52524: Fixed possible corruption in nfc/llcp (bsc#1220927).\n- CVE-2023-52528: Fixed uninit-value access in __smsc75xx_read_reg() (bsc#1220843).\n- CVE-2023-52507: Fixed possible shift-out-of-bounds in nfc/nci (bsc#1220833).\n- CVE-2023-52566: Fixed potential use after free in nilfs_gccache_submit_read_data() (bsc#1220940).\n- CVE-2023-52508: Fixed null pointer dereference in nvme_fc_io_getuuid() (bsc#1221015).\n- CVE-2023-6535: Fixed a NULL pointer dereference in nvmet_tcp_execute_request (bsc#1217988).\n- CVE-2023-6536: Fixed a NULL pointer dereference in __nvmet_req_complete (bsc#1217989).\n- CVE-2023-6356: Fixed a NULL pointer dereference in nvmet_tcp_build_pdu_iovec (bsc#1217987).\n- CVE-2023-52454: Fixed a kernel panic when host sends an invalid H2C PDU length (bsc#1220320).\n- CVE-2023-52520: Fixed reference leak in platform/x86/think-lmi (bsc#1220921).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-52509: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1220836).\n- CVE-2023-52501: Fixed possible memory corruption in ring-buffer (bsc#1220885).\n- CVE-2023-52567: Fixed possible Oops in  serial/8250_port: when using IRQ polling (irq = 0) (bsc#1220839).\n- CVE-2023-52517: Fixed race between DMA RX transfer completion and RX FIFO drain in spi/sun6i (bsc#1221055).\n- CVE-2023-52511: Fixed possible memory corruption in spi/sun6i (bsc#1221012).\n- CVE-2023-52525: Fixed out of bounds check mwifiex_process_rx_packet() (bsc#1220840).\n- CVE-2023-52504: Fixed possible out-of bounds in apply_alternatives() on a 5-level paging machine (bsc#1221553).\n- CVE-2023-52575: Fixed SBPB enablement for spec_rstack_overflow=off (bsc#1220871).\n- CVE-2022-48626: Fixed a potential use-after-free on remove path moxart (bsc#1220366).\n- CVE-2022-48629: Fixed possible memory leak in qcom-rng (bsc#1220989).\n- CVE-2022-48630: Fixed infinite loop on requests not multiple of WORD_SZ in crypto: qcom-rng (bsc#1220990).\n- CVE-2021-46926: Fixed bug when detecting controllers in ALSA/hda/intel-sdw-acpi (bsc#1220478).\n- CVE-2021-47096: Fixed uninitalized user_pversion in ALSA rawmidi (bsc#1220981).\n- CVE-2021-47104: Fixed memory leak in qib_user_sdma_queue_pkts() (bsc#1220960).\n- CVE-2021-47097: Fixed stack out of bound access in elantech_change_report_id() (bsc#1220982).\n- CVE-2021-47094: Fixed possible memory leak in KVM x86/mmu (bsc#1221551).\n- CVE-2021-47107: Fixed READDIR buffer overflow in NFSD (bsc#1220965).\n- CVE-2021-47101: Fixed uninit-value in asix_mdio_read() (bsc#1220987).\n- CVE-2021-47108: Fixed possible NULL pointer dereference for mtk_hdmi_conf in drm/mediatek (bsc#1220986).\n- CVE-2021-47098: Fixed integer overflow/underflow in hysteresis calculations hwmon: (lm90) (bsc#1220983).\n- CVE-2021-47100: Fixed UAF when uninstall in ipmi (bsc#1220985).\n- CVE-2021-47095: Fixed missing initialization in ipmi/ssif (bsc#1220979).\n- CVE-2021-47091: Fixed locking in ieee80211_start_ap()) error path (bsc#1220959).\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47102: Fixed incorrect structure access In line: upper = info-\u003eupper_dev in net/marvell/prestera (bsc#1221009).\n- CVE-2021-46925: Fixed kernel panic caused by race of smc_sock (bsc#1220466).\n- CVE-2021-46927: Fixed assertion bug in nitro_enclaves: Use get_user_pages_unlocked() (bsc#1220443).\n- CVE-2021-47093: Fixed memleak on registration failure in intel_pmc_core (bsc#1220978).\n- CVE-2022-20154: Fixed a use after free due to a race condition in lock_sock_nested of sock.c. This could lead to local escalation of privilege with System execution privileges needed (bsc#1200599).\n- CVE-2021-46929: Fixed use-after-free issue in sctp_sock_dump() (bsc#1220482).\n- CVE-2021-47087: Fixed incorrect page free bug in tee/optee (bsc#1220954).\n- CVE-2022-4744: Fixed double-free that could lead to DoS or privilege escalation in TUN/TAP device driver functionality (bsc#1209635).\n- CVE-2021-47082: Fixed ouble free in tun_free_netdev() (bsc#1220969).\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2021-46930: Fixed usb/mtu3 list_head check warning (bsc#1220484).\n- CVE-2021-47099: Fixed BUG_ON assertion in veth when skb entering GRO are cloned (bsc#1220955).\n- CVE-2023-52492: Fixed a null-pointer-dereference in channel unregistration function __dma_async_device_channel_register() (bsc#1221276).\n- CVE-2023-52450: Fixed NULL pointer dereference issue in upi_fill_topology() (bsc#1220237).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-52583: Fixed deadlock or deadcode of misusing dget() inside ceph (bsc#1221058).\n- CVE-2023-52582: Fixed possible oops in netfs (bsc#1220878).\n- CVE-2023-52477: Fixed USB Hub accesses to uninitialized BOS descriptors (bsc#1220790).\n- CVE-2023-52470: Fixed null-ptr-deref in radeon_crtc_init() (bsc#1220413).\n- CVE-2023-52469: Fixed a use-after-free in kv_parse_power_table (bsc#1220411).\n- CVE-2023-52576: Fixed potential use after free in memblock_isolate_range() (bsc#1220872).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n- CVE-2023-52497: Fixed data corruption in erofs (bsc#1220879).\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-52569: Fixed a bug in btrfs by remoning BUG() after failure to insert delayed dir index item (bsc#1220918).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2023-52523: Fixed wrong redirects to non-TCP sockets in bpf (bsc#1220926).\n- CVE-2021-47105: Fixed potential memory leak in ice/xsk (bsc#1220961).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2021-46931: Fixed wrong type casting in mlx5e_tx_reporter_dump_sq() (bsc#1220486).\n\nThe following non-security bugs were fixed:\n\n- doc/README.SUSE: Update information about module support status (jsc#PED-5759)\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (bsc#1222619).\n","status":"published","published":"2024-04-16T22:45:55Z","modified":"2025-05-02T04:32:03.132756Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1466-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.\n\nNOTE: This update has been retracted due to a bug in the BHI CPU sidechannel mitigation, which led to incorrect selection of other CPU mitigations.\n\nThe following security bugs were fixed:\n\n- CVE-2021-46925: Fixed kernel panic caused by race of smc_sock (bsc#1220466).\n- CVE-2021-46926: Fixed bug when detecting controllers in ALSA/hda/intel-sdw-acpi (bsc#1220478).\n- CVE-2021-46927: Fixed assertion bug in nitro_enclaves: Use get_user_pages_unlocked() (bsc#1220443).\n- CVE-2021-46929: Fixed use-after-free issue in sctp_sock_dump() (bsc#1220482).\n- CVE-2021-46930: Fixed usb/mtu3 list_head check warning (bsc#1220484).\n- CVE-2021-46931: Fixed wrong type casting in mlx5e_tx_reporter_dump_sq() (bsc#1220486).\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2021-46934: Fixed a bug by validating user data in compat ioctl (bsc#1220469).\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47082: Fixed ouble free in tun_free_netdev() (bsc#1220969).\n- CVE-2021-47083: Fixed a global-out-of-bounds issue in mediatek: (bsc#1220917).\n- CVE-2021-47087: Fixed incorrect page free bug in tee/optee (bsc#1220954).\n- CVE-2021-47091: Fixed locking in ieee80211_start_ap()) error path (bsc#1220959).\n- CVE-2021-47093: Fixed memleak on registration failure in intel_pmc_core (bsc#1220978).\n- CVE-2021-47094: Fixed possible memory leak in KVM x86/mmu (bsc#1221551).\n- CVE-2021-47095: Fixed missing initialization in ipmi/ssif (bsc#1220979).\n- CVE-2021-47096: Fixed uninitalized user_pversion in ALSA rawmidi (bsc#1220981).\n- CVE-2021-47097: Fixed stack out of bound access in elantech_change_report_id() (bsc#1220982).\n- CVE-2021-47098: Fixed integer overflow/underflow in hysteresis calculations hwmon: (lm90) (bsc#1220983).\n- CVE-2021-47099: Fixed BUG_ON assertion in veth when skb entering GRO are cloned (bsc#1220955).\n- CVE-2021-47100: Fixed UAF when uninstall in ipmi (bsc#1220985).\n- CVE-2021-47101: Fixed uninit-value in asix_mdio_read() (bsc#1220987).\n- CVE-2021-47102: Fixed incorrect structure access In line: upper = info-\u003eupper_dev in net/marvell/prestera (bsc#1221009).\n- CVE-2021-47104: Fixed memory leak in qib_user_sdma_queue_pkts() (bsc#1220960).\n- CVE-2021-47105: Fixed potential memory leak in ice/xsk (bsc#1220961).\n- CVE-2021-47107: Fixed READDIR buffer overflow in NFSD (bsc#1220965).\n- CVE-2021-47108: Fixed possible NULL pointer dereference for mtk_hdmi_conf in drm/mediatek (bsc#1220986).\n- CVE-2022-4744: Fixed double-free that could lead to DoS or privilege escalation in TUN/TAP device driver functionality (bsc#1209635).\n- CVE-2022-48626: Fixed a potential use-after-free on remove path moxart (bsc#1220366).\n- CVE-2022-48627: Fixed a memory overlapping when deleting chars in the buffer (bsc#1220845).\n- CVE-2022-48628: Fixed possible lock in ceph (bsc#1220848).\n- CVE-2022-48629: Fixed possible memory leak in qcom-rng (bsc#1220989).\n- CVE-2022-48630: Fixed infinite loop on requests not multiple of WORD_SZ in crypto: qcom-rng (bsc#1220990).\n- CVE-2023-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system (bsc#1209657).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-4881: Fixed a out-of-bounds write flaw in the netfilter subsystem that could lead to potential information disclosure or a denial of service (bsc#1215221).\n- CVE-2023-52447: Fixed map_fd_put_ptr() signature kABI workaround  (bsc#1220251).\n- CVE-2023-52450: Fixed NULL pointer dereference issue in upi_fill_topology() (bsc#1220237).\n- CVE-2023-52453: Fixed data corruption in hisi_acc_vfio_pci (bsc#1220337).\n- CVE-2023-52454: Fixed a kernel panic when host sends an invalid H2C PDU length (bsc#1220320).\n- CVE-2023-52462: Fixed check for attempt to corrupt spilled pointer (bsc#1220325).\n- CVE-2023-52463: Fixed null pointer dereference in efivarfs (bsc#1220328).\n- CVE-2023-52467: Fixed a null pointer dereference in of_syscon_register (bsc#1220433).\n- CVE-2023-52469: Fixed a use-after-free in kv_parse_power_table (bsc#1220411).\n- CVE-2023-52470: Fixed null-ptr-deref in radeon_crtc_init() (bsc#1220413).\n- CVE-2023-52474: Fixed a vulnerability with non-PAGE_SIZE-end multi-iovec user SDMA requests (bsc#1220445).\n- CVE-2023-52476: Fixed possible unhandled page fault via perf sampling NMI during vsyscall (bsc#1220703).\n- CVE-2023-52477: Fixed USB Hub accesses to uninitialized BOS descriptors (bsc#1220790).\n- CVE-2023-52481: Fixed speculative unprivileged load in Cortex-A520 (bsc#1220887).\n- CVE-2023-52482: Fixed a bug by adding SRSO mitigation for Hygon processors (bsc#1220735).\n- CVE-2023-52484: Fixed a soft lockup triggered by arm_smmu_mm_invalidate_range (bsc#1220797).\n- CVE-2023-52486: Fixed possible use-after-free in drm (bsc#1221277).\n- CVE-2023-52492: Fixed a null-pointer-dereference in channel unregistration function __dma_async_device_channel_register() (bsc#1221276).\n- CVE-2023-52493: Fixed possible soft lockup in bus/mhi/host (bsc#1221274).\n- CVE-2023-52494: Fixed missing alignment check for event ring read pointer in bus/mhi/host (bsc#1221273).\n- CVE-2023-52497: Fixed data corruption in erofs (bsc#1220879).\n- CVE-2023-52500: Fixed information leaking when processing OPC_INB_SET_CONTROLLER_CONFIG command (bsc#1220883).\n- CVE-2023-52501: Fixed possible memory corruption in ring-buffer (bsc#1220885).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2023-52504: Fixed possible out-of bounds in apply_alternatives() on a 5-level paging machine (bsc#1221553).\n- CVE-2023-52507: Fixed possible shift-out-of-bounds in nfc/nci (bsc#1220833).\n- CVE-2023-52508: Fixed null pointer dereference in nvme_fc_io_getuuid() (bsc#1221015).\n- CVE-2023-52509: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1220836).\n- CVE-2023-52510: Fixed a potential UAF in ca8210_probe() (bsc#1220898).\n- CVE-2023-52511: Fixed possible memory corruption in spi/sun6i (bsc#1221012).\n- CVE-2023-52513: Fixed connection failure handling  in RDMA/siw (bsc#1221022).\n- CVE-2023-52515: Fixed possible use-after-free in RDMA/srp (bsc#1221048).\n- CVE-2023-52517: Fixed race between DMA RX transfer completion and RX FIFO drain in spi/sun6i (bsc#1221055).\n- CVE-2023-52518: Fixed information leak in bluetooth/hci_codec (bsc#1221056).\n- CVE-2023-52519: Fixed possible overflow in HID/intel-ish-hid/ipc (bsc#1220920).\n- CVE-2023-52520: Fixed reference leak in platform/x86/think-lmi (bsc#1220921).\n- CVE-2023-52523: Fixed wrong redirects to non-TCP sockets in bpf (bsc#1220926).\n- CVE-2023-52524: Fixed possible corruption in nfc/llcp (bsc#1220927).\n- CVE-2023-52525: Fixed out of bounds check mwifiex_process_rx_packet() (bsc#1220840).\n- CVE-2023-52528: Fixed uninit-value access in __smsc75xx_read_reg() (bsc#1220843).\n- CVE-2023-52529: Fixed a potential memory leak in sony_probe() (bsc#1220929).\n- CVE-2023-52530: Fixed a potential key use-after-free in wifi mac80211 (bsc#1220930).\n- CVE-2023-52531: Fixed a memory corruption issue in iwlwifi (bsc#1220931).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52559: Fixed a bug by avoiding memory allocation in iommu_suspend (bsc#1220933).\n- CVE-2023-52563: Fixed memory leak on -\u003ehpd_notify callback() in drm/meson (bsc#1220937).\n- CVE-2023-52564: Reverted invalid fix for UAF in gsm_cleanup_mux() (bsc#1220938).\n- CVE-2023-52566: Fixed potential use after free in nilfs_gccache_submit_read_data() (bsc#1220940).\n- CVE-2023-52567: Fixed possible Oops in  serial/8250_port: when using IRQ polling (irq = 0) (bsc#1220839).\n- CVE-2023-52569: Fixed a bug in btrfs by remoning BUG() after failure to insert delayed dir index item (bsc#1220918).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2023-52575: Fixed SBPB enablement for spec_rstack_overflow=off (bsc#1220871).\n- CVE-2023-52576: Fixed potential use after free in memblock_isolate_range() (bsc#1220872).\n- CVE-2023-52582: Fixed possible oops in netfs (bsc#1220878).\n- CVE-2023-52583: Fixed deadlock or deadcode of misusing dget() inside ceph (bsc#1221058).\n- CVE-2023-52587: Fixed mcast list locking in IB/ipoib (bsc#1221082).\n- CVE-2023-52591: Fixed a possible reiserfs filesystem corruption via directory renaming (bsc#1221044).\n- CVE-2023-52594: Fixed potential array-index-out-of-bounds read in ath9k_htc_txstatus() (bsc#1221045).\n- CVE-2023-52595: Fixed possible deadlock in wifi/rt2x00 (bsc#1221046).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2023-52598: Fixed wrong setting of fpc register in s390/ptrace (bsc#1221060).\n- CVE-2023-52599: Fixed array-index-out-of-bounds in diNewExt() in jfs (bsc#1221062).\n- CVE-2023-52600: Fixed uaf in jfs_evict_inode() (bsc#1221071).\n- CVE-2023-52601: Fixed array-index-out-of-bounds in dbAdjTree() in jfs (bsc#1221068).\n- CVE-2023-52602: Fixed slab-out-of-bounds Read in dtSearch() in jfs (bsc#1221070).\n- CVE-2023-52603: Fixed array-index-out-of-bounds in dtSplitRoot() (bsc#1221066).\n- CVE-2023-52604: Fixed array-index-out-of-bounds in dbAdjTree() (bsc#1221067).\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-52606: Fixed possible kernel stack corruption in powerpc/lib (bsc#1221069).\n- CVE-2023-52607: Fixed a null-pointer-dereference in pgtable_cache_add kasprintf() (bsc#1221061).\n- CVE-2023-52608: Fixed possible race condition in firmware/arm_scmi (bsc#1221375).\n- CVE-2023-52612: Fixed req-\u003edst buffer overflow in crypto/scomp (bsc#1221616).\n- CVE-2023-52615: Fixed page fault dead lock on mmap-ed hwrng (bsc#1221614).\n- CVE-2023-52617: Fixed stdev_release() crash after surprise hot remove (bsc#1221613).\n- CVE-2023-52619: Fixed possible crash when setting number of cpus to an odd number in pstore/ram (bsc#1221618).\n- CVE-2023-52621: Fixed missing asserion in bpf (bsc#1222073).\n- CVE-2023-52623: Fixed suspicious RCU usage in SUNRPC (bsc#1222060).\n- CVE-2023-52628: Fixed 4-byte stack OOB write in nftables (bsc#1222117).\n- CVE-2023-52632: Fixed lock dependency warning with srcu in drm/amdkfd (bsc#1222274).\n- CVE-2023-52637: Fixed UAF in j1939_sk_match_filter() in can/k1939 (bsc#1222291).\n- CVE-2023-52639: Fixed race during shadow creation in KVM/s390/vsie Fixed (bsc#1222300).\n- CVE-2023-6270: Fixed a use-after-free issue in aoecmd_cfg_pkts (bsc#1218562).\n- CVE-2023-6356: Fixed a NULL pointer dereference in nvmet_tcp_build_pdu_iovec (bsc#1217987).\n- CVE-2023-6535: Fixed a NULL pointer dereference in nvmet_tcp_execute_request (bsc#1217988).\n- CVE-2023-6536: Fixed a NULL pointer dereference in __nvmet_req_complete (bsc#1217989).\n- CVE-2023-7042: Fixed a null-pointer-dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() (bsc#1218336).\n- CVE-2023-7192: Fixed a memory leak problem in ctnetlink_create_conntrack in net/netfilter/nf_conntrack_netlink.c (bsc#1218479).\n- CVE-2024-0841: Fixed a null pointer dereference in the hugetlbfs_fill_super function in hugetlbfs (HugeTLB pages) functionality (bsc#1219264).\n- CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).\n- CVE-2024-22099: Fixed a null-pointer-dereference in rfcomm_check_security (bsc#1219170).\n- CVE-2024-23307: Fixed Integer Overflow or Wraparound vulnerability in x86 and ARM md, raid, raid5 modules (bsc#1219169).\n- CVE-2024-25739: Fixed possible crash in create_empty_lvol() in drivers/mtd/ubi/vtbl.c (bsc#1219834).\n- CVE-2024-25742: Fixed insufficient validation during #VC instruction emulation in x86/sev (bsc#1221725).\n- CVE-2024-26599: Fixed out-of-bounds access in of_pwm_single_xlate() (bsc#1220365).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n- CVE-2024-26602: Fixed overall slowdowns with sys_membarrier (bsc1220398).\n- CVE-2024-26607: Fixed a probing race issue in sii902x: (bsc#1220736).\n- CVE-2024-26612: Fixed Oops in fscache_put_cache() This function dereferences  (bsc#1221291).\n- CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).\n- CVE-2024-26620: Fixed possible device model violation in s390/vfio-ap (bsc#1221298).\n- CVE-2024-26627: Fixed possible hard lockup in scsi (bsc#1221090).\n- CVE-2024-26629: Fixed possible protocol violation via RELEASE_LOCKOWNER in nfsd (bsc#1221379).\n- CVE-2024-26642: Fixed the set of anonymous timeout flag in netfilter nf_tables (bsc#1221830).\n- CVE-2024-26645: Fixed missing visibility when inserting an element into tracing_map (bsc#1222056).\n- CVE-2024-26646: Fixed potential memory corruption when resuming from suspend or hibernation in thermal/intel/hfi (bsc#1222070).\n- CVE-2024-26651: Fixed possible oops via malicious devices in sr9800 (bsc#1221337).\n- CVE-2024-26654: Fixed use after free in ALSA/sh/aica (bsc#1222304).\n- CVE-2024-26659: Fixed wrong handling of isoc Babble and Buffer Overrun events in xhci (bsc#1222317).\n- CVE-2024-26664: Fixed out-of-bounds memory access in create_core_data() in hwmon coretemp (bsc#1222355).\n- CVE-2024-26667: Fixed null pointer reference in dpu_encoder_helper_phys_cleanup in drm/msm/dpu (bsc#1222331).\n- CVE-2024-26670: Fixed ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround in kernel arm64 (bsc#1222356).\n- CVE-2024-26695: Fixed null pointer dereference in __sev_platform_shutdown_locked in crypto ccp (bsc#1222373).\n- CVE-2024-26717: Fixed null pointer dereference on failed power up in HID i2c-hid-of (bsc#1222360).\n\n\nThe following non-security bugs were fixed:\n\n- acpi: CPPC: enable AMD CPPC V2 support for family 17h processors (git-fixes).\n- acpi: processor_idle: Fix memory leak in acpi_processor_power_exit() (git-fixes).\n- acpi: resource: Add Infinity laptops to irq1_edge_low_force_override (stable-fixes).\n- acpi: resource: Add MAIBENBEN X577 to irq1_edge_low_force_override (git-fixes).\n- acpi: resource: Do IRQ override on Lunnen Ground laptops (stable-fixes).\n- acpi: scan: Fix device check notification handling (git-fixes).\n- acpica: debugger: check status of acpi_evaluate_object() in acpi_db_walk_for_fields() (git-fixes).\n- alsa: aaci: Delete unused variable in aaci_do_suspend (git-fixes).\n- alsa: aoa: avoid false-positive format truncation warning (git-fixes).\n- alsa: aw2: avoid casting function pointers (git-fixes).\n- alsa: ctxfi: avoid casting function pointers (git-fixes).\n- alsa: hda/realtek - ALC285 reduce pop noise from Headphone port (stable-fixes).\n- alsa: hda/realtek - Add Headset Mic supported Acer NB platform (stable-fixes).\n- alsa: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform (git-fixes).\n- alsa: hda/realtek: Enable Mute LED on HP 840 G8 (MB 8AB8) (git-fixes).\n- alsa: hda/realtek: Update Panasonic CF-SZ6 quirk to support headset with microphone (git-fixes).\n- alsa: hda/realtek: fix ALC285 issues on HP Envy x360 laptops (stable-fixes).\n- alsa: hda/realtek: fix mute/micmute LED For HP mt440 (git-fixes).\n- alsa: hda/realtek: fix mute/micmute LEDs for HP EliteBook (stable-fixes).\n- alsa: seq: fix function cast warnings (git-fixes).\n- alsa: sh: aica: reorder cleanup operations to avoid UAF bugs (git-fixes).\n- alsa: usb-audio: Stop parsing channels bits when all channels are found (git-fixes).\n- arm64: dts: allwinner: h6: Add RX DMA channel for SPDIF (git-fixes)\n- arm64: dts: broadcom: bcmbca: bcm4908: drop invalid switch cells (git-fixes)\n- arm64: dts: imx8mm-kontron: Add support for ultra high speed modes on (git-fixes)\n- arm64: dts: imx8mm-venice-gw71xx: fix USB OTG VBUS (git-fixes)\n- arm64: dts: marvell: reorder crypto interrupts on Armada SoCs (git-fixes)\n- arm64: dts: rockchip: add ES8316 codec for ROCK Pi 4 (git-fixes)\n- arm64: dts: rockchip: add SPDIF node for ROCK Pi 4 (git-fixes)\n- arm64: dts: rockchip: fix regulator name on rk3399-rock-4 (git-fixes)\n- arm64: dts: rockchip: set num-cs property for spi on px30 (git-fixes)\n- arm64: mm: fix VA-range sanity check (git-fixes)\n- arm64: set __exception_irq_entry with __irq_entry as a default (git-fixes)\n- asoc: Intel: bytcr_rt5640: Add an extra entry for the Chuwi Vi8 tablet (stable-fixes).\n- asoc: amd: acp: Add missing error handling in sof-mach (git-fixes).\n- asoc: amd: acp: fix for acp_init function error handling (git-fixes).\n- asoc: madera: Fix typo in madera_set_fll_clks shift value (git-fixes).\n- asoc: meson: Use dev_err_probe() helper (stable-fixes).\n- asoc: meson: aiu: fix function pointer type mismatch (git-fixes).\n- asoc: meson: axg-tdm-interface: add frame rate constraint (git-fixes).\n- asoc: meson: axg-tdm-interface: fix mclk setup without mclk-fs (git-fixes).\n- asoc: meson: t9015: fix function pointer type mismatch (git-fixes).\n- asoc: ops: Fix wraparound for mask in snd_soc_get_volsw (git-fixes).\n- asoc: rcar: adg: correct TIMSEL setting for SSI9 (git-fixes).\n- asoc: rt5645: Make LattePanda board DMI match more precise (stable-fixes).\n- asoc: rt5682-sdw: fix locking sequence (git-fixes).\n- asoc: rt711-sdca: fix locking sequence (git-fixes).\n- asoc: rt711-sdw: fix locking sequence (git-fixes).\n- asoc: wm8962: Enable both SPKOUTR_ENA and SPKOUTL_ENA in mono mode (stable-fixes).\n- asoc: wm8962: Enable oscillator if selecting WM8962_FLL_OSC (stable-fixes).\n- asoc: wm8962: Fix up incorrect error message in wm8962_set_fll (stable-fixes).\n- ata: sata_mv: Fix PCI device ID table declaration compilation warning (git-fixes).\n- ata: sata_sx4: fix pdc20621_get_from_dimm() on 64-bit (git-fixes).\n- backlight: da9052: Fully initialize backlight_properties during probe (git-fixes).\n- backlight: lm3630a: Do not set bl-\u003eprops.brightness in get_brightness (git-fixes).\n- backlight: lm3630a: Initialize backlight_properties on init (git-fixes).\n- backlight: lm3639: Fully initialize backlight_properties during probe (git-fixes).\n- backlight: lp8788: Fully initialize backlight_properties during probe (git-fixes).\n- blocklayoutdriver: Fix reference leak of pnfs_device_node (git-fixes).\n- bluetooth: Remove HCI_POWER_OFF_TIMEOUT (git-fixes).\n- bluetooth: Remove superfluous call to hci_conn_check_pending() (git-fixes).\n- bluetooth: hci_core: Fix possible buffer overflow (git-fixes).\n- bluetooth: mgmt: Remove leftover queuing of power_off work (git-fixes).\n- bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security (stable-fixes).\n- bpf, scripts: Correct GPL license name (git-fixes).\n- bpf, sockmap: Fix preempt_rt splat when using raw_spin_lock_t (git-fixes).\n- can: softing: remove redundant NULL check (git-fixes).\n- clk: zynq: Prevent null pointer dereference caused by kmalloc failure (git-fixes).\n- comedi: comedi_test: Prevent timers rescheduling during deletion (git-fixes).\n- coresight: etm4x: Do not access TRCIDR1 for identification (bsc#1220775)\n- coresight: etm4x: Fix accesses to TRCSEQRSTEVR and TRCSEQSTR (bsc#1220775)\n- coresight: etm: Override TRCIDR3.CCITMIN on errata affected cpus (bsc#1220775)\n- cpufreq: amd-pstate: Fix min_perf assignment in amd_pstate_adjust_perf() (git-fixes).\n- cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value (git-fixes).\n- crypto: arm/sha - fix function cast warnings (git-fixes).\n- crypto: qat - avoid division by zero (git-fixes).\n- crypto: qat - fix deadlock in backlog processing (git-fixes).\n- crypto: qat - fix double free during reset (git-fixes).\n- crypto: qat - fix state machines cleanup paths (bsc#1218321).\n- crypto: qat - fix unregistration of compression algorithms (git-fixes).\n- crypto: qat - fix unregistration of crypto algorithms (git-fixes).\n- crypto: qat - ignore subsequent state up commands (git-fixes).\n- crypto: qat - increase size of buffers (git-fixes).\n- crypto: qat - resolve race condition during AER recovery (git-fixes).\n- crypto: xilinx - call finalize with bh disabled (git-fixes).\n- doc-guide: kernel-doc: tell about object-like macros (git-fixes).\n- doc/README.SUSE: Update information about module support status (jsc#PED-5759)\n- drivers: hv: vmbus: Calculate ring buffer size for more efficient use of memory (git-fixes).\n- drm/amd/display: Add FAMS validation before trying to use it (git-fixes).\n- drm/amd/display: Add function for validate and update new stream (git-fixes).\n- drm/amd/display: Avoid ABM when ODM combine is enabled for eDP (git-fixes).\n- drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN31 (git-fixes).\n- drm/amd/display: Check if link state is valid (git-fixes).\n- drm/amd/display: Copy DC context in the commit streams (git-fixes).\n- drm/amd/display: Disable PSR-SU on Parade 0803 TCON again (git-fixes).\n- drm/amd/display: Enable fast plane updates on DCN3.2 and above (git-fixes).\n- drm/amd/display: Enable new commit sequence only for DCN32x (git-fixes).\n- drm/amd/display: Exit idle optimizations before attempt to access PHY (git-fixes).\n- drm/amd/display: Expand kernel doc for DC (git-fixes).\n- drm/amd/display: Fix a bug when searching for insert_above_mpcc (git-fixes).\n- drm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()' (git-fixes).\n- drm/amd/display: Fix possible underflow for displays with large vblank (git-fixes).\n- drm/amd/display: Fix the delta clamping for shaper LUT (git-fixes).\n- drm/amd/display: Fix underflow issue on 175hz timing (git-fixes).\n- drm/amd/display: For prefetch mode \u003e 0, extend prefetch if possible (git-fixes).\n- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family (git-fixes).\n- drm/amd/display: Guard against invalid RPTR/WPTR being set (git-fixes).\n- drm/amd/display: Handle seamless boot stream (git-fixes).\n- drm/amd/display: Handle virtual hardware detect (git-fixes).\n- drm/amd/display: Include surface of unaffected streams (git-fixes).\n- drm/amd/display: Include udelay when waiting for INBOX0 ACK (git-fixes).\n- drm/amd/display: Increase frame warning limit with KASAN or KCSAN in dml (git-fixes).\n- drm/amd/display: Keep PHY active for dp config (git-fixes).\n- drm/amd/display: Prevent vtotal from being set to 0 (git-fixes).\n- drm/amd/display: Remove min_dst_y_next_start check for Z8 (git-fixes).\n- drm/amd/display: Restore rptr/wptr for DMCUB as workaround (git-fixes).\n- drm/amd/display: Return the correct HDCP error code (stable-fixes).\n- drm/amd/display: Revert vblank change that causes null pointer crash (git-fixes).\n- drm/amd/display: Rework comments on dc file (git-fixes).\n- drm/amd/display: Rework context change check (git-fixes).\n- drm/amd/display: Set minimum requirement for using PSR-SU on Phoenix (git-fixes).\n- drm/amd/display: Set minimum requirement for using PSR-SU on Rembrandt (git-fixes).\n- drm/amd/display: Update OTG instance in the commit stream (git-fixes).\n- drm/amd/display: Update correct DCN314 register header (git-fixes).\n- drm/amd/display: Update min Z8 residency time to 2100 for DCN314 (git-fixes).\n- drm/amd/display: Use DRAM speed from validation for dummy p-state (git-fixes).\n- drm/amd/display: Use DTBCLK as refclk instead of DPREFCLK (git-fixes).\n- drm/amd/display: Use min transition for all SubVP plane add/remove (git-fixes).\n- drm/amd/display: Write to correct dirty_rect (git-fixes).\n- drm/amd/display: Wrong colorimetry workaround (git-fixes).\n- drm/amd/display: add FB_DAMAGE_CLIPS support (git-fixes).\n- drm/amd/display: add ODM case when looking for first split pipe (git-fixes).\n- drm/amd/display: always switch off ODM before committing more streams (git-fixes).\n- drm/amd/display: clean code-style issues in dcn30_set_mpc_shaper_3dlut (git-fixes).\n- drm/amd/display: dc.h: eliminate kernel-doc warnings (git-fixes).\n- drm/amd/display: ensure async flips are only accepted for fast updates (git-fixes).\n- drm/amd/display: fix ABM disablement (git-fixes).\n- drm/amd/display: fix a NULL pointer dereference in amdgpu_dm_i2c_xfer() (git-fixes).\n- drm/amd/display: fix dc/core/dc.c kernel-doc (git-fixes).\n- drm/amd/display: fix hw rotated modes when PSR-SU is enabled (git-fixes).\n- drm/amd/display: fix kernel-doc issues in dc.h (git-fixes).\n- drm/amd/display: fix unbounded requesting for high pixel rate modes on dcn315 (git-fixes).\n- drm/amd/display: handle range offsets in VRR ranges (stable-fixes).\n- drm/amd/display: perform a bounds check before filling dirty rectangles (git-fixes).\n- drm/amd/display: set per pipe dppclk to 0 when dpp is off (git-fixes).\n- drm/amd/display: update extended blank for dcn314 onwards (git-fixes).\n- drm/amd/display: use low clocks for no plane configs (git-fixes).\n- drm/amd/pm: Fix error of MACO flag setting code (git-fixes).\n- drm/amd/pm: fix a memleak in aldebaran_tables_init (git-fixes).\n- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr Clock (git-fixes).\n- drm/amd: Enable PCIe PME from D3 (git-fixes).\n- drm/amdgpu/pm: Fix the error of pwm1_enable setting (stable-fixes).\n- drm/amdgpu/pm: make gfxclock consistent for sienna cichlid (git-fixes).\n- drm/amdgpu/pm: make mclk consistent for smu 13.0.7 (git-fixes).\n- drm/amdgpu/smu13: drop compute workload workaround (git-fixes).\n- drm/amdgpu: Enable gpu reset for S3 abort cases on Raven series (stable-fixes).\n- drm/amdgpu: Fix missing break in ATOM_ARG_IMM Case of atom_get_src_int() (git-fixes).\n- drm/amdgpu: Force order between a read and write to the same address (git-fixes).\n- drm/amdgpu: Match against exact bootloader status (git-fixes).\n- drm/amdgpu: Unset context priority is now invalid (git-fixes).\n- drm/amdgpu: Update min() to min_t() in 'amdgpu_info_ioctl' (git-fixes).\n- drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag (stable-fixes).\n- drm/amdgpu: lower CS errors to debug severity (git-fixes).\n- drm/amdkfd: fix TLB flush after unmap for GFX9.4.2 (stable-fixes).\n- drm/bridge: tc358762: Instruct DSI host to generate HSE packets (git-fixes).\n- drm/display: fix typo (git-fixes).\n- drm/edid: Add quirk for OSVR HDK 2.0 (git-fixes).\n- drm/etnaviv: Restore some id values (git-fixes).\n- drm/exynos: do not return negative values from .get_modes() (stable-fixes).\n- drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable() (git-fixes).\n- drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode() (stable-fixes).\n- drm/i915/gt: Do not generate the command streamer for all the CCS (git-fixes).\n- drm/i915/gt: Reset queue_priority_hint on parking (git-fixes).\n- drm/i915/gt: Use i915_vm_put on ppgtt_create error paths (git-fixes).\n- drm/i915/selftests: Fix dependency of some timeouts on HZ (git-fixes).\n- drm/i915: Add missing CCS documentation (git-fixes).\n- drm/i915: Call intel_pre_plane_updates() also for pipes getting enabled (git-fixes).\n- drm/i915: Check before removing mm notifier (git-fixes).\n- drm/lima: fix a memleak in lima_heap_alloc (git-fixes).\n- drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip (git-fixes).\n- drm/mediatek: dsi: Fix DSI RGB666 formats and definitions (git-fixes).\n- drm/msm/dpu: Only enable DSC_MODE_MULTIPLEX if dsc_merge is enabled (git-fixes).\n- drm/msm/dpu: add division of drm_display_mode's hskew parameter (git-fixes).\n- drm/msm/dpu: fix the programming of INTF_CFG2_DATA_HCTL_EN (git-fixes).\n- drm/msm/dpu: improve DSC allocation (git-fixes).\n- drm/panel-edp: use put_sync in unprepare (git-fixes).\n- drm/panel: Move AUX B116XW03 out of panel-edp back to panel-simple (git-fixes).\n- drm/panel: auo,b101uan08.3: Fine tune the panel power sequence (git-fixes).\n- drm/panel: boe-tv101wum-nl6: Fine tune the panel power sequence (git-fixes).\n- drm/panel: do not return negative error codes from drm_panel_get_modes() (stable-fixes).\n- drm/panfrost: fix power transition timeout warnings (git-fixes).\n- drm/probe-helper: warn about negative .get_modes() (stable-fixes).\n- drm/qxl: remove unused `count` variable from `qxl_surface_id_alloc()` (git-fixes).\n- drm/qxl: remove unused variable from `qxl_process_single_command()` (git-fixes).\n- drm/radeon/ni: Fix wrong firmware size logging in ni_init_microcode() (git-fixes).\n- drm/radeon/ni_dpm: remove redundant NULL check (git-fixes).\n- drm/radeon: remove dead code in ni_mc_load_microcode() (git-fixes).\n- drm/rockchip: dsi: Clean up 'usage_mode' when failing to attach (git-fixes).\n- drm/rockchip: inno_hdmi: Fix video timing (git-fixes).\n- drm/rockchip: lvds: do not overwrite error code (git-fixes).\n- drm/rockchip: lvds: do not print scary message when probing defer (git-fixes).\n- drm/tegra: dpaux: Fix PM disable depth imbalance in tegra_dpaux_probe (git-fixes).\n- drm/tegra: dsi: Add missing check for of_find_device_by_node (git-fixes).\n- drm/tegra: dsi: Fix missing pm_runtime_disable() in the error handling path of tegra_dsi_probe() (git-fixes).\n- drm/tegra: dsi: Fix some error handling paths in tegra_dsi_probe() (git-fixes).\n- drm/tegra: dsi: Make use of the helper function dev_err_probe() (stable-fixes).\n- drm/tegra: hdmi: Convert to devm_platform_ioremap_resource() (stable-fixes).\n- drm/tegra: hdmi: Fix some error handling paths in tegra_hdmi_probe() (git-fixes).\n- drm/tegra: output: Fix missing i2c_put_adapter() in the error handling paths of tegra_output_probe() (git-fixes).\n- drm/tegra: put drm_gem_object ref on error in tegra_fb_create (git-fixes).\n- drm/tegra: rgb: Fix missing clk_put() in the error handling paths of tegra_dc_rgb_probe() (git-fixes).\n- drm/tegra: rgb: Fix some error handling paths in tegra_dc_rgb_probe() (git-fixes).\n- drm/tidss: Fix initial plane zpos values (git-fixes).\n- drm/tidss: Fix sync-lost issue with two displays (git-fixes).\n- drm/ttm: Do not leak a resource on eviction error (git-fixes).\n- drm/ttm: Do not print error message if eviction was interrupted (git-fixes).\n- drm/vc4: Add module dependency on hdmi-codec (git-fixes).\n- drm/vmwgfx: Create debugfs ttm_resource_manager entry only if needed (git-fixes).\n- drm/vmwgfx: Fix possible null pointer derefence with invalid contexts (git-fixes).\n- drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node (git-fixes).\n- drm: Do not treat 0 as -1 in drm_fixp2int_ceil (git-fixes).\n- drm: Fix drm_fixp2int_round() making it add 0.5 (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017) (git-fixes).\n- firewire: core: use long bus reset on gap count error (stable-fixes).\n- fix 'coresight: etm4x: Change etm4_platform_driver driver for MMIO devices' (bsc#1220775) Hunk with clk_put(drvdata-\u003epclk) was incorrectly moved to another function.\n- hid: amd_sfh: Update HPD sensor structure elements (git-fixes).\n- hid: lenovo: Add middleclick_workaround sysfs knob for cptkbd (git-fixes).\n- hid: multitouch: Add required quirk for Synaptics 0xcddc device (stable-fixes).\n- hv_netvsc: Calculate correct ring size when PAGE_SIZE is not 4 Kbytes (git-fixes).\n- hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove (git-fixes).\n- hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed (git-fixes).\n- i2c: aspeed: Fix the dummy irq expected print (git-fixes).\n- i2c: i801: Avoid potential double call to gpiod_remove_lookup_table (git-fixes).\n- i2c: wmt: Fix an error handling path in wmt_i2c_probe() (git-fixes).\n- ib/ipoib: Fix mcast list locking (git-fixes)\n- iio: dummy_evgen: remove Excess kernel-doc comments (git-fixes).\n- iio: pressure: dlhl60d: Initialize empty DLH bytes (git-fixes).\n- input: gpio_keys_polled - suppress deferred probe error for gpio (stable-fixes).\n- input: i8042 - add Fujitsu Lifebook E5411 to i8042 quirk table (git-fixes).\n- input: i8042 - add Fujitsu Lifebook U728 to i8042 quirk table (git-fixes).\n- input: i8042 - add quirk for Fujitsu Lifebook A574/H (git-fixes).\n- input: i8042 - fix strange behavior of touchpad on Clevo NS70PU (git-fixes).\n- input: pm8941-powerkey - fix debounce on gen2+ PMICs (git-fixes).\n- input: pm8941-pwrkey - add software key press debouncing support (git-fixes).\n- input: pm8941-pwrkey - add support for PON GEN3 base addresses (git-fixes).\n- input: synaptics-rmi4 - fix UAF of IRQ domain on driver removal (git-fixes).\n- input: xpad - add Lenovo Legion Go controllers (git-fixes).\n- iommu/amd: Mark interrupt as managed (git-fixes).\n- iommu/dma: Trace bounce buffer usage when mapping buffers (git-fixes).\n- iommu/mediatek-v1: Fix an error handling path in mtk_iommu_v1_probe() (git-fixes).\n- iommu/mediatek: Fix forever loop in error handling (git-fixes).\n- iommu/vt-d: Allow to use flush-queue when first level is default (git-fixes).\n- iommu/vt-d: Do not issue ATS Invalidation request when device is disconnected (git-fixes).\n- iommu/vt-d: Fix PASID directory pointer coherency (git-fixes).\n- iommu/vt-d: Set No Execute Enable bit in PASID table entry (git-fixes).\n- kabi: PCI: Add locking to RMW PCI Express Capability Register accessors (kabi).\n- kconfig: fix infinite loop when expanding a macro at the end of file (git-fixes).\n- kvm: s390: only deliver the set service event bits (git-fixes bsc#1221631).\n- lan78xx: enable auto speed configuration for LAN7850 if no EEPROM is detected (git-commit).\n- leds: aw2013: Unlock mutex before destroying it (git-fixes).\n- lib/cmdline: Fix an invalid format specifier in an assertion msg (git-fixes).\n- make NVIDIA Grace-Hopper TPM related drivers build-ins (bsc#1221156)\n- md/raid10: check slab-out-of-bounds in md_bitmap_get_counter (git-fixes).\n- md/raid5: release batch_last before waiting for another stripe_head (git-fixes).\n- md/raid6: use valid sector values to determine if an I/O should wait on the reshape (git-fixes).\n- md: Do not ignore suspended array in md_check_recovery() (git-fixes).\n- md: Make sure md_do_sync() will set MD_RECOVERY_DONE (git-fixes).\n- md: Whenassemble the array, consult the superblock of the freshest device (git-fixes).\n- md: do not leave 'MD_RECOVERY_FROZEN' in error path of md_set_readonly() (git-fixes).\n- md: fix data corruption for raid456 when reshape restart while grow up (git-fixes).\n- md: introduce md_ro_state (git-fixes).\n- media: dvb-frontends: avoid stack overflow warnings with clang (git-fixes).\n- media: edia: dvbdev: fix a use-after-free (git-fixes).\n- media: em28xx: annotate unchecked call to media_device_register() (git-fixes).\n- media: go7007: add check of return value of go7007_read_addr() (git-fixes).\n- media: go7007: fix a memleak in go7007_load_encoder (git-fixes).\n- media: imx: csc/scaler: fix v4l2_ctrl_handler memory leak (git-fixes).\n- media: pvrusb2: fix pvr2_stream_callback casts (git-fixes).\n- media: pvrusb2: fix uaf in pvr2_context_set_notify (git-fixes).\n- media: pvrusb2: remove redundant NULL check (git-fixes).\n- media: staging: ipu3-imgu: Set fields before media_entity_pads_init() (git-fixes).\n- media: sun8i-di: Fix chroma difference threshold (git-fixes).\n- media: sun8i-di: Fix coefficient writes (git-fixes).\n- media: sun8i-di: Fix power on/off sequences (git-fixes).\n- media: tc358743: register v4l2 async device only after successful setup (git-fixes).\n- media: ttpci: fix two memleaks in budget_av_attach (git-fixes).\n- media: usbtv: Remove useless locks in usbtv_video_free() (git-fixes).\n- media: v4l2-mem2mem: fix a memleak in v4l2_m2m_register_entity (git-fixes).\n- media: v4l2-tpg: fix some memleaks in tpg_alloc (git-fixes).\n- media: xc4000: Fix atomicity violation in xc4000_get_frequency (git-fixes).\n- mfd: altera-sysmgr: Call of_node_put() only when of_parse_phandle() takes a ref (git-fixes).\n- mfd: syscon: Call of_node_put() only when of_parse_phandle() takes a ref (git-fixes).\n- mm,page_owner: Defer enablement of static branch (bsc#1222366).\n- mm,page_owner: Fix accounting of pages when migrating (bsc#1222366).\n- mm,page_owner: Fix printing of stack records (bsc#1222366).\n- mm,page_owner: Fix refcount imbalance (bsc#1222366).\n- mm,page_owner: Update metadata for tail pages (bsc#1222366).\n- mm,page_owner: check for null stack_record before bumping its refcount (bsc#1222366).\n- mm,page_owner: drop unnecessary check (bsc#1222366).\n- mm,page_owner: fix recursion (bsc#1222366).\n- mm/vmalloc: huge vmalloc backing pages should be split rather than compound (bsc#1217829).\n- mmc: core: Avoid negative index with array access (git-fixes).\n- mmc: core: Fix switch on gp3 partition (git-fixes).\n- mmc: core: Initialize mmc_blk_ioc_data (git-fixes).\n- mmc: mmci: stm32: fix DMA API overlapping mappings warning (git-fixes).\n- mmc: mmci: stm32: use a buffer for unaligned DMA requests (git-fixes).\n- mmc: tmio: avoid concurrent runs of mmc_request_done() (git-fixes).\n- mmc: wmt-sdmmc: remove an incorrect release_mem_region() call in the .remove function (git-fixes).\n- mtd: maps: physmap-core: fix flash size larger than 32-bit (git-fixes).\n- mtd: rawnand: lpc32xx_mlc: fix irq handler prototype (git-fixes).\n- mtd: rawnand: meson: fix scrambling mode value in command macro (git-fixes).\n- net/bnx2x: Prevent access to a freed page in page_pool (bsc#1215322).\n- net/x25: fix incorrect parameter validation in the x25_getsockopt() function (git-fixes).\n- net: Fix features skip in for_each_netdev_feature() (git-fixes).\n- net: lan78xx: fix runtime PM count underflow on link stop (git-fixes).\n- net: ll_temac: platform_get_resource replaced by wrong function (git-fixes).\n- net: mana: Fix Rx DMA datasize and skb_over_panic (git-fixes).\n- net: phy: fix phy_get_internal_delay accessing an empty array (git-fixes).\n- net: sunrpc: Fix an off by one in rpc_sockaddr2uaddr() (git-fixes).\n- net: usb: dm9601: fix wrong return value in dm9601_mdio_read (git-fixes).\n- nfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet (git-fixes).\n- nfs: fix an off by one in root_nfs_cat() (git-fixes).\n- nfs: rename nfs_client_kset to nfs_kset (git-fixes).\n- nfsd: change LISTXATTRS cookie encoding to big-endian (git-fixes).\n- nfsd: convert the callback workqueue to use delayed_work (git-fixes).\n- nfsd: do not take fi_lock in nfsd_break_deleg_cb() (git-fixes).\n- nfsd: fix LISTXATTRS returning a short list with eof=TRUE (git-fixes).\n- nfsd: fix LISTXATTRS returning more bytes than maxcount (git-fixes).\n- nfsd: fix file memleak on client_opens_release (git-fixes).\n- nfsd: fix nfsd4_listxattr_validate_cookie (git-fixes).\n- nfsd: lock_rename() needs both directories to live on the same fs (git-fixes).\n- nfsd: reschedule CB operations when backchannel rpc_clnt is shut down (git-fixes).\n- nfsd: reset cb_seq_status after NFS4ERR_DELAY (git-fixes).\n- nfsd: retransmit callbacks after client reconnects (git-fixes).\n- nfsd: use vfs setgid helper (git-fixes).\n- nfsv4.1/pnfs: Ensure we handle the error NFS4ERR_RETURNCONFLICT (git-fixes).\n- nfsv4.1: fix SP4_MACH_CRED protection for pnfs IO (git-fixes).\n- nfsv4.1: fixup use EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nfsv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nfsv4.2: fix listxattr maximum XDR buffer size (git-fixes).\n- nfsv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 (git-fixes).\n- nfsv4.2: fix wrong shrinker_id (git-fixes).\n- nfsv4: fix a nfs4_state_manager() race (git-fixes).\n- nfsv4: fix a state manager thread deadlock regression (git-fixes).\n- nilfs2: fix failure to detect DAT corruption in btree and direct mappings (git-fixes).\n- nilfs2: prevent kernel bug at submit_bh_wbc() (git-fixes).\n- nouveau/dmem: handle kcalloc() allocation failure (git-fixes).\n- nouveau: reset the bo resource bus info after an eviction (git-fixes).\n- ntfs: fix use-after-free in ntfs_ucsncmp() (bsc#1221713).\n- nvme-fc: do not wait in vain when unloading module (git-fixes).\n- nvme: fix reconnection fail due to reserved tag allocation (git-fixes).\n- nvmet-fc: abort command when there is no binding (git-fixes).\n- nvmet-fc: avoid deadlock on delete association path (git-fixes).\n- nvmet-fc: defer cleanup using RCU properly (git-fixes).\n- nvmet-fc: hold reference on hostport match (git-fixes).\n- nvmet-fc: release reference on target port (git-fixes).\n- nvmet-fc: take ref count on tgtport before delete assoc (git-fixes).\n- nvmet-fcloop: swap the list_add_tail arguments (git-fixes).\n- nvmet-tcp: fix nvme tcp ida memory leak (git-fixes).\n- pci/aer: fix rootport attribute paths in ABI docs (git-fixes).\n- pci/aspm: Use RMW accessors for changing LNKCTL (git-fixes).\n- pci/dpc: print all TLP Prefixes, not just the first (git-fixes).\n- pci/msi: prevent MSI hardware interrupt number truncation (bsc#1218777)\n- pci/p2pdma: Fix a sleeping issue in a RCU read section (git-fixes).\n- pci: add locking to RMW PCI Express Capability Register accessors (git-fixes).\n- pci: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq() (git-fixes).\n- pci: dwc: endpoint: Fix advertised resizable BAR size (git-fixes).\n- pci: dwc: endpoint: Fix dw_pcie_ep_raise_msix_irq() alignment support (git-fixes).\n- pci: fu740: Set the number of MSI vectors (git-fixes).\n- pci: lengthen reset delay for VideoPropulsion Torrent QN16e card (git-fixes).\n- pci: make link retraining use RMW accessors for changing LNKCTL (git-fixes).\n- pci: mark 3ware-9650SE Root Port Extended Tags as broken (git-fixes).\n- pci: mediatek-gen3: Fix translation window size calculation (git-fixes).\n- pci: mediatek: Clear interrupt status before dispatching handler (git-fixes).\n- pci: qcom: Enable BDF to SID translation properly (git-fixes).\n- pci: qcom: Use DWC helpers for modifying the read-only DBI registers (git-fixes).\n- pci: rockchip: Do not advertise MSI-X in PCIe capabilities (git-fixes).\n- pci: rockchip: Fix window mapping and address translation for endpoint (git-fixes).\n- pci: rockchip: Use 64-bit mask on MSI 64-bit PCI address (git-fixes).\n- pci: switchtec: Fix an error handling path in switchtec_pci_probe() (git-fixes).\n- pinctrl: mediatek: Drop bogus slew rate register range for MT8192 (git-fixes).\n- platform/mellanox: mlxreg-hotplug: Remove redundant NULL-check (git-fixes).\n- pm: suspend: Set mem_sleep_current during kernel command line setup (git-fixes).\n- pnfs/flexfiles: Check the layout validity in ff_layout_mirror_prepare_stats (git-fixes).\n- pnfs: Fix a hang in nfs4_evict_inode() (git-fixes).\n- pnfs: Fix the pnfs block driver's calculation of layoutget size (git-fixes).\n- powerpc/64s: POWER10 CPU Kconfig build option (bsc#1194869).\n- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment (bsc#1194869).\n- powerpc/boot: Fix boot wrapper code generation with CONFIG_POWER10_CPU (bsc#1194869).\n- powerpc/lib/sstep: Do not use __{get/put}_user() on kernel addresses (bsc#1194869).\n- powerpc/lib/sstep: Remove unneeded #ifdef __powerpc64__ (bsc#1194869).\n- powerpc/lib/sstep: Use l1_dcache_bytes() instead of opencoding (bsc#1194869).\n- powerpc/lib/sstep: use truncate_if_32bit() (bsc#1194869).\n- powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV (bsc#1220492 ltc#205270).\n- powerpc/pseries: Fix potential memleak in papr_get_attr() (bsc#1200465 ltc#197256 jsc#SLE-18130 git-fixes).\n- powerpc/sstep: Use bitwise instead of arithmetic operator for flags (bsc#1194869).\n- powerpc: add compile-time support for lbarx, lharx (bsc#1194869).\n- pwm: mediatek: Update kernel doc for struct pwm_mediatek_of_data (git-fixes).\n- qedf: Do not process stag work during unload (bsc#1214852).\n- qedf: Wait for stag work during unload (bsc#1214852).\n- raid1: fix use-after-free for original bio in raid1_write_request() (bsc#1221097).\n- ras/amd/fmpm: Add debugfs interface to print record entries (jsc#PED-7619).\n- ras/amd/fmpm: Avoid NULL ptr deref in get_saved_records() (jsc#PED-7619).\n- ras/amd/fmpm: Fix build when debugfs is not enabled (jsc#PED-7619).\n- ras/amd/fmpm: Fix off by one when unwinding on error (jsc#PED-7619).\n- ras/amd/fmpm: Safely handle saved records of various sizes (jsc#PED-7619).\n- ras/amd/fmpm: Save SPA values (jsc#PED-7619).\n- ras: Avoid build errors when CONFIG_DEBUG_FS=n (git-fixes).\n- ras: export helper to get ras_debugfs_dir (jsc#PED-7619).\n- rdma/device: Fix a race between mad_client and cm_client init (git-fixes)\n- rdma/hns: fix mis-modifying default congestion control algorithm (git-fixes)\n- rdma/ipoib: Fix error code return in ipoib_mcast_join (git-fixes)\n- rdma/irdma: Remove duplicate assignment (git-fixes)\n- rdma/mana_ib: Fix bug in creation of dma regions (git-fixes).\n- rdma/mlx5: fix fortify source warning while accessing Eth segment (git-fixes)\n- rdma/mlx5: relax DEVX access upon modify commands (git-fixes)\n- rdma/rtrs-clt: Check strnlen return len in sysfs mpath_policy_store() (git-fixes)\n- rdma/srpt: do not register event handler until srpt device is fully setup (git-fixes)\n- revert 'PCI: tegra194: Enable support for 256 Byte payload' (git-fixes).\n- revert 'Revert 'drm/amdgpu/display: change pipe policy for DCN 2.0'' (git-fixes).\n- revert 'SUNRPC dont update timeout value on connection reset' (git-fixes).\n- revert 'drm/amd: Disable PSR-SU on Parade 0803 TCON' (git-fixes).\n- revert 'drm/amd: Disable S/G for APUs when 64GB or more host memory' (git-fixes).\n- revert 'drm/amdgpu/display: change pipe policy for DCN 2.0' (git-fixes).\n- revert 'drm/amdgpu/display: change pipe policy for DCN 2.1' (git-fixes).\n- revert 'drm/vc4: hdmi: Enforce the minimum rate at runtime_resume' (git-fixes).\n- revert 'fbdev: flush deferred IO before closing (git-fixes).' (bsc#1221814)\n- ring-buffer: Clean ring_buffer_poll_wait() error return (git-fixes).\n- rtc: mt6397: select IRQ_DOMAIN instead of depending on it (git-fixes).\n- s390/pai: fix attr_event_free upper limit for pai device drivers (git-fixes bsc#1221633).\n- s390/vfio-ap: realize the VFIO_DEVICE_GET_IRQ_INFO ioctl (bsc#1205316).\n- s390/vfio-ap: realize the VFIO_DEVICE_SET_IRQS ioctl (bsc#1205316).\n- s390/vfio-ap: wire in the vfio_device_ops request callback (bsc#1205316).\n- s390/vtime: fix average steal time calculation (git-fixes bsc#1221951).\n- sched/rt: Disallow writing invalid values to sched_rt_period_us (bsc#1220176).\n- sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset (bsc#1220176).\n- scsi: lpfc: Copyright updates for 14.4.0.1 patches (bsc#1221777).\n- scsi: lpfc: Correct size for cmdwqe/rspwqe for memset() (bsc#1221777).\n- scsi: lpfc: Correct size for wqe for memset() (bsc#1221777).\n- scsi: lpfc: Define lpfc_dmabuf type for ctx_buf ptr (bsc#1221777).\n- scsi: lpfc: Define lpfc_nodelist type for ctx_ndlp ptr (bsc#1221777).\n- scsi: lpfc: Define types in a union for generic void *context3 ptr (bsc#1221777).\n- scsi: lpfc: Move NPIV's transport unregistration to after resource clean up (bsc#1221777).\n- scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1221777).\n- scsi: lpfc: Remove IRQF_ONESHOT flag from threaded IRQ handling (bsc#1221777 bsc#1217959).\n- scsi: lpfc: Remove unnecessary log message in queuecommand path (bsc#1221777).\n- scsi: lpfc: Replace hbalock with ndlp lock in lpfc_nvme_unregister_port() (bsc#1221777).\n- scsi: lpfc: Update lpfc version to 14.4.0.1 (bsc#1221777).\n- scsi: lpfc: Update lpfc_ramp_down_queue_handler() logic (bsc#1221777).\n- scsi: lpfc: Use a dedicated lock for ras_fwlog state (bsc#1221777).\n- scsi: qedf: Remove set but unused variable 'page' (bsc#1214852).\n- scsi: qedf: Remove unused 'num_handled' variable (bsc#1214852).\n- scsi: qedf: Remove unused declaration (bsc#1214852).\n- scsi: qla2xxx: Change debug message during driver unload (bsc1221816).\n- scsi: qla2xxx: Delay I/O Abort on PCI error (bsc1221816).\n- scsi: qla2xxx: Fix N2N stuck connection (bsc1221816).\n- scsi: qla2xxx: Fix command flush on cable pull (bsc1221816).\n- scsi: qla2xxx: Fix double free of fcport (bsc1221816).\n- scsi: qla2xxx: Fix double free of the ha-\u003evp_map pointer (bsc1221816).\n- scsi: qla2xxx: NVME|FCP prefer flag not being honored (bsc1221816).\n- scsi: qla2xxx: Prevent command send on chip reset (bsc1221816).\n- scsi: qla2xxx: Split FCE|EFT trace control (bsc1221816).\n- scsi: qla2xxx: Update manufacturer detail (bsc1221816).\n- scsi: qla2xxx: Update version to 10.02.09.200-k (bsc1221816).\n- scsi: storvsc: Fix ring buffer size calculation (git-fixes).\n- scsi: target: core: Silence the message about unknown VPD pages (bsc#1221252).\n- selftests/bpf: add generic BPF program tester-loader (bsc#1222033).\n- serial: 8250_exar: Do not remove GPIO device on suspend (git-fixes).\n- serial: max310x: fix syntax error in IRQ error message (git-fixes).\n- slimbus: core: Remove usage of the deprecated ida_simple_xx() API (git-fixes).\n- soc: fsl: qbman: Always disable interrupts when taking cgr_lock (git-fixes).\n- spi: lm70llp: fix links in doc and comments (git-fixes).\n- spi: spi-mt65xx: Fix NULL pointer access in interrupt handler (git-fixes).\n- sr9800: Add check for usbnet_get_endpoints (git-fixes).\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- staging: vc04_services: fix information leak in create_component() (git-fixes).\n- sunrpc: Add an IS_ERR() check back to where it was (git-fixes).\n- sunrpc: ECONNRESET might require a rebind (git-fixes).\n- sunrpc: Fix RPC client cleaned up the freed pipefs dentries (git-fixes).\n- sunrpc: Fix a suspicious RCU usage warning (git-fixes).\n- sunrpc: fix a memleak in gss_import_v2_context (git-fixes).\n- sunrpc: fix some memleaks in gssx_dec_option_array (git-fixes).\n- svcrdma: Drop connection after an RDMA Read error (git-fixes).\n- topology/sysfs: Hide PPIN on systems that do not support it (jsc#PED-7618).\n- topology: Fix up build warning in topology_is_visible() (jsc#PED-7618).\n- tracing/probes: Fix to show a parse error for bad type for $comm (git-fixes).\n- tracing: Fix wasted memory in saved_cmdlines logic (git-fixes).\n- tracing: Inform kmemleak of saved_cmdlines allocation (git-fixes).\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (bsc#1222619).\n- tty: serial: fsl_lpuart: avoid idle preamble pending if CTS is enabled (git-fixes).\n- tty: serial: samsung: fix tx_empty() to return TIOCSER_TEMT (git-fixes).\n- tty: vt: fix 20 vs 0x20 typo in EScsiignore (git-fixes).\n- ubifs: Queue up space reservation tasks if retrying many times (git-fixes).\n- ubifs: Remove unreachable code in dbg_check_ltab_lnum (git-fixes).\n- ubifs: Set page uptodate in the correct place (git-fixes).\n- ubifs: dbg_check_idx_size: Fix kmemleak if loading znode failed (git-fixes).\n- ubifs: fix sort function prototype (git-fixes).\n- usb: audio-v2: Correct comments for struct uac_clock_selector_descriptor (git-fixes).\n- usb: cdc-wdm: close race between read and workqueue (git-fixes).\n- usb: core: Fix deadlock in usb_deauthorize_interface() (git-fixes).\n- usb: dwc2: gadget: Fix exiting from clock gating (git-fixes).\n- usb: dwc2: gadget: LPM flow fix (git-fixes).\n- usb: dwc2: host: Fix ISOC flow in DDMA mode (git-fixes).\n- usb: dwc2: host: Fix hibernation flow (git-fixes).\n- usb: dwc2: host: Fix remote wakeup from hibernation (git-fixes).\n- usb: dwc3: Properly set system wakeup (git-fixes).\n- usb: f_mass_storage: forbid async queue when shutdown happen (git-fixes).\n- usb: gadget: ncm: Fix handling of zero block length packets (git-fixes).\n- usb: gadget: net2272: Use irqflags in the call to net2272_probe_fin (git-fixes).\n- usb: hub: Replace hardcoded quirk value with BIT() macro (git-fixes).\n- usb: port: Do not try to peer unused USB ports based on location (git-fixes).\n- usb: typec: Return size of buffer if pd_set operation succeeds (git-fixes).\n- usb: typec: ucsi: Check for notifications after init (git-fixes).\n- usb: typec: ucsi: Clean up UCSI_CABLE_PROP macros (git-fixes).\n- usb: typec: ucsi: Clear EVENT_PENDING under PPM lock (git-fixes).\n- usb: usb-storage: Prevent divide-by-0 error in isd200_ata_command (git-fixes).\n- usb: xhci: Add error handling in xhci_map_urb_for_dma (git-fixes).\n- vboxsf: Avoid an spurious warning if load_nls_xxx() fails (git-fixes).\n- vt: fix unicode buffer corruption when deleting characters (git-fixes).\n- watchdog: stm32_iwdg: initialize default timeout (git-fixes).\n- wifi: ath10k: fix NULL pointer dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() (git-fixes).\n- wifi: ath11k: decrease MHI channel buffer length to 8KB (bsc#1207948).\n- wifi: ath11k: initialize rx_mcs_80 and rx_mcs_160 before use (git-fixes).\n- wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete (git-fixes).\n- wifi: b43: Disable QoS for bcm4331 (git-fixes).\n- wifi: b43: Stop correct queue in DMA worker when QoS is disabled (git-fixes).\n- wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled (git-fixes).\n- wifi: b43: Stop/wake correct queue in PIO Tx path when QoS is disabled (git-fixes).\n- wifi: brcmfmac: fix copyright year mentioned in platform_data header (git-fixes).\n- wifi: brcmsmac: avoid function pointer casts (git-fixes).\n- wifi: iwlwifi: dbg-tlv: ensure NUL termination (git-fixes).\n- wifi: iwlwifi: fix EWRD table validity check (git-fixes).\n- wifi: iwlwifi: fw: do not always use FW dump trig (git-fixes).\n- wifi: iwlwifi: mvm: do not set replay counters to 0xff (git-fixes).\n- wifi: iwlwifi: mvm: report beacon protection failures (git-fixes).\n- wifi: iwlwifi: mvm: rfi: fix potential response leaks (git-fixes).\n- wifi: iwlwifi: mvm: use FW rate for non-data only on new devices (git-fixes).\n- wifi: libertas: fix some memleaks in lbs_allocate_cmd_buffer() (git-fixes).\n- wifi: mwifiex: debugfs: Drop unnecessary error check for debugfs_create_dir() (git-fixes).\n- wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work (git-fixes).\n- wifi: rtw88: 8821c: Fix false alarm count (git-fixes).\n- wifi: wilc1000: fix RCU usage in connect path (git-fixes).\n- wifi: wilc1000: fix declarations ordering (stable-fixes).\n- wifi: wilc1000: fix multi-vif management when deleting a vif (git-fixes).\n- wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces (git-fixes).\n- x86/CPU/AMD: Update the Zenbleed microcode revisions (git-fixes).\n- x86/bugs: Fix the SRSO mitigation on Zen3/4 (git-fixes).\n- x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (git-fixes).\n- xhci: handle isoc Babble and Buffer Overrun events properly (git-fixes).\n- xhci: process isoc TD properly when there was a transaction error mid TD (git-fixes).\n","status":"published","published":"2024-04-29T12:58:00Z","modified":"2026-02-04T03:01:15.405094Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1480-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2021-46925: Fixed kernel panic caused by race of smc_sock (bsc#1220466).\n- CVE-2021-46926: Fixed bug when detecting controllers in ALSA/hda/intel-sdw-acpi (bsc#1220478).\n- CVE-2021-46927: Fixed assertion bug in nitro_enclaves: Use get_user_pages_unlocked() (bsc#1220443).\n- CVE-2021-46929: Fixed use-after-free issue in sctp_sock_dump() (bsc#1220482).\n- CVE-2021-46930: Fixed usb/mtu3 list_head check warning (bsc#1220484).\n- CVE-2021-46931: Fixed wrong type casting in mlx5e_tx_reporter_dump_sq() (bsc#1220486).\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2021-46934: Fixed a bug by validating user data in compat ioctl (bsc#1220469).\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47082: Fixed ouble free in tun_free_netdev() (bsc#1220969).\n- CVE-2021-47083: Fixed a global-out-of-bounds issue in mediatek: (bsc#1220917).\n- CVE-2021-47087: Fixed incorrect page free bug in tee/optee (bsc#1220954).\n- CVE-2021-47091: Fixed locking in ieee80211_start_ap()) error path (bsc#1220959).\n- CVE-2021-47093: Fixed memleak on registration failure in intel_pmc_core (bsc#1220978).\n- CVE-2021-47094: Fixed possible memory leak in KVM x86/mmu (bsc#1221551).\n- CVE-2021-47095: Fixed missing initialization in ipmi/ssif (bsc#1220979).\n- CVE-2021-47096: Fixed uninitalized user_pversion in ALSA rawmidi (bsc#1220981).\n- CVE-2021-47097: Fixed stack out of bound access in elantech_change_report_id() (bsc#1220982).\n- CVE-2021-47098: Fixed integer overflow/underflow in hysteresis calculations hwmon: (lm90) (bsc#1220983).\n- CVE-2021-47099: Fixed BUG_ON assertion in veth when skb entering GRO are cloned (bsc#1220955).\n- CVE-2021-47100: Fixed UAF when uninstall in ipmi (bsc#1220985).\n- CVE-2021-47101: Fixed uninit-value in asix_mdio_read() (bsc#1220987).\n- CVE-2021-47102: Fixed incorrect structure access In line: upper = info-\u003eupper_dev in net/marvell/prestera (bsc#1221009).\n- CVE-2021-47104: Fixed memory leak in qib_user_sdma_queue_pkts() (bsc#1220960).\n- CVE-2021-47105: Fixed potential memory leak in ice/xsk (bsc#1220961).\n- CVE-2021-47107: Fixed READDIR buffer overflow in NFSD (bsc#1220965).\n- CVE-2021-47108: Fixed possible NULL pointer dereference for mtk_hdmi_conf in drm/mediatek (bsc#1220986).\n- CVE-2022-4744: Fixed double-free that could lead to DoS or privilege escalation in TUN/TAP device driver functionality (bsc#1209635).\n- CVE-2022-48626: Fixed a potential use-after-free on remove path moxart (bsc#1220366).\n- CVE-2022-48627: Fixed a memory overlapping when deleting chars in the buffer (bsc#1220845).\n- CVE-2022-48628: Fixed possible lock in ceph (bsc#1220848).\n- CVE-2022-48629: Fixed possible memory leak in qcom-rng (bsc#1220989).\n- CVE-2022-48630: Fixed infinite loop on requests not multiple of WORD_SZ in crypto: qcom-rng (bsc#1220990).\n- CVE-2023-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system (bsc#1209657).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-4881: Fixed a out-of-bounds write flaw in the netfilter subsystem that could lead to potential information disclosure or a denial of service (bsc#1215221).\n- CVE-2023-52447: Fixed map_fd_put_ptr() signature kABI workaround  (bsc#1220251).\n- CVE-2023-52450: Fixed NULL pointer dereference issue in upi_fill_topology() (bsc#1220237).\n- CVE-2023-52453: Fixed data corruption in hisi_acc_vfio_pci (bsc#1220337).\n- CVE-2023-52454: Fixed a kernel panic when host sends an invalid H2C PDU length (bsc#1220320).\n- CVE-2023-52462: Fixed check for attempt to corrupt spilled pointer (bsc#1220325).\n- CVE-2023-52463: Fixed null pointer dereference in efivarfs (bsc#1220328).\n- CVE-2023-52467: Fixed a null pointer dereference in of_syscon_register (bsc#1220433).\n- CVE-2023-52469: Fixed a use-after-free in kv_parse_power_table (bsc#1220411).\n- CVE-2023-52470: Fixed null-ptr-deref in radeon_crtc_init() (bsc#1220413).\n- CVE-2023-52474: Fixed a vulnerability with non-PAGE_SIZE-end multi-iovec user SDMA requests (bsc#1220445).\n- CVE-2023-52476: Fixed possible unhandled page fault via perf sampling NMI during vsyscall (bsc#1220703).\n- CVE-2023-52477: Fixed USB Hub accesses to uninitialized BOS descriptors (bsc#1220790).\n- CVE-2023-52481: Fixed speculative unprivileged load in Cortex-A520 (bsc#1220887).\n- CVE-2023-52482: Fixed a bug by adding SRSO mitigation for Hygon processors (bsc#1220735).\n- CVE-2023-52484: Fixed a soft lockup triggered by arm_smmu_mm_invalidate_range (bsc#1220797).\n- CVE-2023-52486: Fixed possible use-after-free in drm (bsc#1221277).\n- CVE-2023-52492: Fixed a null-pointer-dereference in channel unregistration function __dma_async_device_channel_register() (bsc#1221276).\n- CVE-2023-52493: Fixed possible soft lockup in bus/mhi/host (bsc#1221274).\n- CVE-2023-52494: Fixed missing alignment check for event ring read pointer in bus/mhi/host (bsc#1221273).\n- CVE-2023-52497: Fixed data corruption in erofs (bsc#1220879).\n- CVE-2023-52500: Fixed information leaking when processing OPC_INB_SET_CONTROLLER_CONFIG command (bsc#1220883).\n- CVE-2023-52501: Fixed possible memory corruption in ring-buffer (bsc#1220885).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2023-52504: Fixed possible out-of bounds in apply_alternatives() on a 5-level paging machine (bsc#1221553).\n- CVE-2023-52507: Fixed possible shift-out-of-bounds in nfc/nci (bsc#1220833).\n- CVE-2023-52508: Fixed null pointer dereference in nvme_fc_io_getuuid() (bsc#1221015).\n- CVE-2023-52509: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1220836).\n- CVE-2023-52510: Fixed a potential UAF in ca8210_probe() (bsc#1220898).\n- CVE-2023-52511: Fixed possible memory corruption in spi/sun6i (bsc#1221012).\n- CVE-2023-52513: Fixed connection failure handling  in RDMA/siw (bsc#1221022).\n- CVE-2023-52515: Fixed possible use-after-free in RDMA/srp (bsc#1221048).\n- CVE-2023-52517: Fixed race between DMA RX transfer completion and RX FIFO drain in spi/sun6i (bsc#1221055).\n- CVE-2023-52518: Fixed information leak in bluetooth/hci_codec (bsc#1221056).\n- CVE-2023-52519: Fixed possible overflow in HID/intel-ish-hid/ipc (bsc#1220920).\n- CVE-2023-52520: Fixed reference leak in platform/x86/think-lmi (bsc#1220921).\n- CVE-2023-52523: Fixed wrong redirects to non-TCP sockets in bpf (bsc#1220926).\n- CVE-2023-52524: Fixed possible corruption in nfc/llcp (bsc#1220927).\n- CVE-2023-52525: Fixed out of bounds check mwifiex_process_rx_packet() (bsc#1220840).\n- CVE-2023-52528: Fixed uninit-value access in __smsc75xx_read_reg() (bsc#1220843).\n- CVE-2023-52529: Fixed a potential memory leak in sony_probe() (bsc#1220929).\n- CVE-2023-52530: Fixed a potential key use-after-free in wifi mac80211 (bsc#1220930).\n- CVE-2023-52531: Fixed a memory corruption issue in iwlwifi (bsc#1220931).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52559: Fixed a bug by avoiding memory allocation in iommu_suspend (bsc#1220933).\n- CVE-2023-52563: Fixed memory leak on -\u003ehpd_notify callback() in drm/meson (bsc#1220937).\n- CVE-2023-52564: Reverted invalid fix for UAF in gsm_cleanup_mux() (bsc#1220938).\n- CVE-2023-52566: Fixed potential use after free in nilfs_gccache_submit_read_data() (bsc#1220940).\n- CVE-2023-52567: Fixed possible Oops in  serial/8250_port: when using IRQ polling (irq = 0) (bsc#1220839).\n- CVE-2023-52569: Fixed a bug in btrfs by remoning BUG() after failure to insert delayed dir index item (bsc#1220918).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2023-52575: Fixed SBPB enablement for spec_rstack_overflow=off (bsc#1220871).\n- CVE-2023-52576: Fixed potential use after free in memblock_isolate_range() (bsc#1220872).\n- CVE-2023-52582: Fixed possible oops in netfs (bsc#1220878).\n- CVE-2023-52583: Fixed deadlock or deadcode of misusing dget() inside ceph (bsc#1221058).\n- CVE-2023-52587: Fixed mcast list locking in IB/ipoib (bsc#1221082).\n- CVE-2023-52591: Fixed a possible reiserfs filesystem corruption via directory renaming (bsc#1221044).\n- CVE-2023-52594: Fixed potential array-index-out-of-bounds read in ath9k_htc_txstatus() (bsc#1221045).\n- CVE-2023-52595: Fixed possible deadlock in wifi/rt2x00 (bsc#1221046).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2023-52598: Fixed wrong setting of fpc register in s390/ptrace (bsc#1221060).\n- CVE-2023-52599: Fixed array-index-out-of-bounds in diNewExt() in jfs (bsc#1221062).\n- CVE-2023-52600: Fixed uaf in jfs_evict_inode() (bsc#1221071).\n- CVE-2023-52601: Fixed array-index-out-of-bounds in dbAdjTree() in jfs (bsc#1221068).\n- CVE-2023-52602: Fixed slab-out-of-bounds Read in dtSearch() in jfs (bsc#1221070).\n- CVE-2023-52603: Fixed array-index-out-of-bounds in dtSplitRoot() (bsc#1221066).\n- CVE-2023-52604: Fixed array-index-out-of-bounds in dbAdjTree() (bsc#1221067).\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-52606: Fixed possible kernel stack corruption in powerpc/lib (bsc#1221069).\n- CVE-2023-52607: Fixed a null-pointer-dereference in pgtable_cache_add kasprintf() (bsc#1221061).\n- CVE-2023-52608: Fixed possible race condition in firmware/arm_scmi (bsc#1221375).\n- CVE-2023-52612: Fixed req-\u003edst buffer overflow in crypto/scomp (bsc#1221616).\n- CVE-2023-52615: Fixed page fault dead lock on mmap-ed hwrng (bsc#1221614).\n- CVE-2023-52617: Fixed stdev_release() crash after surprise hot remove (bsc#1221613).\n- CVE-2023-52619: Fixed possible crash when setting number of cpus to an odd number in pstore/ram (bsc#1221618).\n- CVE-2023-52621: Fixed missing asserion in bpf (bsc#1222073).\n- CVE-2023-52623: Fixed suspicious RCU usage in SUNRPC (bsc#1222060).\n- CVE-2023-52628: Fixed 4-byte stack OOB write in nftables (bsc#1222117).\n- CVE-2023-52632: Fixed lock dependency warning with srcu in drm/amdkfd (bsc#1222274).\n- CVE-2023-52637: Fixed UAF in j1939_sk_match_filter() in can/k1939 (bsc#1222291).\n- CVE-2023-52639: Fixed race during shadow creation in KVM/s390/vsie Fixed (bsc#1222300).\n- CVE-2023-6270: Fixed a use-after-free issue in aoecmd_cfg_pkts (bsc#1218562).\n- CVE-2023-6356: Fixed a NULL pointer dereference in nvmet_tcp_build_pdu_iovec (bsc#1217987).\n- CVE-2023-6535: Fixed a NULL pointer dereference in nvmet_tcp_execute_request (bsc#1217988).\n- CVE-2023-6536: Fixed a NULL pointer dereference in __nvmet_req_complete (bsc#1217989).\n- CVE-2023-7042: Fixed a null-pointer-dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() (bsc#1218336).\n- CVE-2023-7192: Fixed a memory leak problem in ctnetlink_create_conntrack in net/netfilter/nf_conntrack_netlink.c (bsc#1218479).\n- CVE-2024-0841: Fixed a null pointer dereference in the hugetlbfs_fill_super function in hugetlbfs (HugeTLB pages) functionality (bsc#1219264).\n- CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).\n- CVE-2024-22099: Fixed a null-pointer-dereference in rfcomm_check_security (bsc#1219170).\n- CVE-2024-23307: Fixed Integer Overflow or Wraparound vulnerability in x86 and ARM md, raid, raid5 modules (bsc#1219169).\n- CVE-2024-25739: Fixed possible crash in create_empty_lvol() in drivers/mtd/ubi/vtbl.c (bsc#1219834).\n- CVE-2024-25742: Fixed insufficient validation during #VC instruction emulation in x86/sev (bsc#1221725).\n- CVE-2024-25743: Fixed insufficient validation during #VC instruction emulation in x86/sev (bsc#1221725).\n- CVE-2024-26599: Fixed out-of-bounds access in of_pwm_single_xlate() (bsc#1220365).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n- CVE-2024-26602: Fixed overall slowdowns with sys_membarrier (bsc1220398).\n- CVE-2024-26607: Fixed a probing race issue in sii902x: (bsc#1220736).\n- CVE-2024-26612: Fixed Oops in fscache_put_cache() This function dereferences  (bsc#1221291).\n- CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).\n- CVE-2024-26620: Fixed possible device model violation in s390/vfio-ap (bsc#1221298).\n- CVE-2024-26627: Fixed possible hard lockup in scsi (bsc#1221090).\n- CVE-2024-26629: Fixed possible protocol violation via RELEASE_LOCKOWNER in nfsd (bsc#1221379).\n- CVE-2024-26642: Fixed the set of anonymous timeout flag in netfilter nf_tables (bsc#1221830).\n- CVE-2024-26645: Fixed missing visibility when inserting an element into tracing_map (bsc#1222056).\n- CVE-2024-26646: Fixed potential memory corruption when resuming from suspend or hibernation in thermal/intel/hfi (bsc#1222070).\n- CVE-2024-26651: Fixed possible oops via malicious devices in sr9800 (bsc#1221337).\n- CVE-2024-26654: Fixed use after free in ALSA/sh/aica (bsc#1222304).\n- CVE-2024-26659: Fixed wrong handling of isoc Babble and Buffer Overrun events in xhci (bsc#1222317).\n- CVE-2024-26664: Fixed out-of-bounds memory access in create_core_data() in hwmon coretemp (bsc#1222355).\n- CVE-2024-26667: Fixed null pointer reference in dpu_encoder_helper_phys_cleanup in drm/msm/dpu (bsc#1222331).\n- CVE-2024-26670: Fixed ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround in kernel arm64 (bsc#1222356).\n- CVE-2024-26695: Fixed null pointer dereference in __sev_platform_shutdown_locked in crypto ccp (bsc#1222373).\n- CVE-2024-26717: Fixed null pointer dereference on failed power up in HID i2c-hid-of (bsc#1222360).\n\nThe following non-security bugs were fixed:\n\n- acpi: CPPC: enable AMD CPPC V2 support for family 17h processors (git-fixes).\n- acpi: processor_idle: Fix memory leak in acpi_processor_power_exit() (git-fixes).\n- acpi: resource: Add Infinity laptops to irq1_edge_low_force_override (stable-fixes).\n- acpi: resource: Add MAIBENBEN X577 to irq1_edge_low_force_override (git-fixes).\n- acpi: resource: Do IRQ override on Lunnen Ground laptops (stable-fixes).\n- acpi: scan: Fix device check notification handling (git-fixes).\n- acpica: debugger: check status of acpi_evaluate_object() in acpi_db_walk_for_fields() (git-fixes).\n- alsa: aaci: Delete unused variable in aaci_do_suspend (git-fixes).\n- alsa: aoa: avoid false-positive format truncation warning (git-fixes).\n- alsa: aw2: avoid casting function pointers (git-fixes).\n- alsa: ctxfi: avoid casting function pointers (git-fixes).\n- alsa: hda/realtek - ALC285 reduce pop noise from Headphone port (stable-fixes).\n- alsa: hda/realtek - Add Headset Mic supported Acer NB platform (stable-fixes).\n- alsa: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform (git-fixes).\n- alsa: hda/realtek: Enable Mute LED on HP 840 G8 (MB 8AB8) (git-fixes).\n- alsa: hda/realtek: Update Panasonic CF-SZ6 quirk to support headset with microphone (git-fixes).\n- alsa: hda/realtek: fix ALC285 issues on HP Envy x360 laptops (stable-fixes).\n- alsa: hda/realtek: fix mute/micmute LED For HP mt440 (git-fixes).\n- alsa: hda/realtek: fix mute/micmute LEDs for HP EliteBook (stable-fixes).\n- alsa: seq: fix function cast warnings (git-fixes).\n- alsa: sh: aica: reorder cleanup operations to avoid UAF bugs (git-fixes).\n- alsa: usb-audio: Stop parsing channels bits when all channels are found (git-fixes).\n- arm64: dts: allwinner: h6: add rx dma channel for spdif (git-fixes)\n- arm64: dts: broadcom: bcmbca: bcm4908: drop invalid switch cells (git-fixes)\n- arm64: dts: imx8mm-kontron: add support for ultra high speed modes on (git-fixes)\n- arm64: dts: imx8mm-venice-gw71xx: fix usb otg vbus (git-fixes)\n- arm64: dts: marvell: reorder crypto interrupts on armada socs (git-fixes)\n- arm64: dts: rockchip: add es8316 codec for rock pi 4 (git-fixes)\n- arm64: dts: rockchip: add spdif node for rock pi 4 (git-fixes)\n- arm64: dts: rockchip: fix regulator name on rk3399-rock-4 (git-fixes)\n- arm64: dts: rockchip: set num-cs property for spi on px30 (git-fixes)\n- arm64: mm: fix va-range sanity check (git-fixes)\n- arm64: set __exception_irq_entry with __irq_entry as a default (git-fixes)\n- asoc: Intel: bytcr_rt5640: Add an extra entry for the Chuwi Vi8 tablet (stable-fixes).\n- asoc: amd: acp: Add missing error handling in sof-mach (git-fixes).\n- asoc: amd: acp: fix for acp_init function error handling (git-fixes).\n- asoc: madera: Fix typo in madera_set_fll_clks shift value (git-fixes).\n- asoc: meson: Use dev_err_probe() helper (stable-fixes).\n- asoc: meson: aiu: fix function pointer type mismatch (git-fixes).\n- asoc: meson: axg-tdm-interface: add frame rate constraint (git-fixes).\n- asoc: meson: axg-tdm-interface: fix mclk setup without mclk-fs (git-fixes).\n- asoc: meson: t9015: fix function pointer type mismatch (git-fixes).\n- asoc: ops: Fix wraparound for mask in snd_soc_get_volsw (git-fixes).\n- asoc: rcar: adg: correct TIMSEL setting for SSI9 (git-fixes).\n- asoc: rt5645: Make LattePanda board DMI match more precise (stable-fixes).\n- asoc: rt5682-sdw: fix locking sequence (git-fixes).\n- asoc: rt711-sdca: fix locking sequence (git-fixes).\n- asoc: rt711-sdw: fix locking sequence (git-fixes).\n- asoc: wm8962: Enable both SPKOUTR_ENA and SPKOUTL_ENA in mono mode (stable-fixes).\n- asoc: wm8962: Enable oscillator if selecting WM8962_FLL_OSC (stable-fixes).\n- asoc: wm8962: Fix up incorrect error message in wm8962_set_fll (stable-fixes).\n- ata: sata_mv: fix pci device id table declaration compilation warning (git-fixes).\n- ata: sata_sx4: fix pdc20621_get_from_dimm() on 64-bit (git-fixes).\n- backlight: da9052: fully initialize backlight_properties during probe (git-fixes).\n- backlight: lm3630a: do not set bl-\u003eprops.brightness in get_brightness (git-fixes).\n- backlight: lm3630a: initialize backlight_properties on init (git-fixes).\n- backlight: lm3639: fully initialize backlight_properties during probe (git-fixes).\n- backlight: lp8788: fully initialize backlight_properties during probe (git-fixes).\n- blocklayoutdriver: fix reference leak of pnfs_device_node (git-fixes).\n- bluetooth: Remove HCI_POWER_OFF_TIMEOUT (git-fixes).\n- bluetooth: Remove superfluous call to hci_conn_check_pending() (git-fixes).\n- bluetooth: hci_core: Fix possible buffer overflow (git-fixes).\n- bluetooth: mgmt: Remove leftover queuing of power_off work (git-fixes).\n- bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security (stable-fixes).\n- bpf, scripts: correct gpl license name (git-fixes).\n- bpf, sockmap: fix preempt_rt splat when using raw_spin_lock_t (git-fixes).\n- can: softing: remove redundant null check (git-fixes).\n- clk: zynq: prevent null pointer dereference caused by kmalloc failure (git-fixes).\n- comedi: comedi_test: prevent timers rescheduling during deletion (git-fixes).\n- coresight: etm4x: do not access trcidr1 for identification (bsc#1220775)\n- coresight: etm4x: fix accesses to trcseqrstevr and trcseqstr (bsc#1220775)\n- coresight: etm: override trcidr3.ccitmin on errata affected cpus (bsc#1220775)\n- cpufreq: amd-pstate: fix min_perf assignment in amd_pstate_adjust_perf() (git-fixes).\n- cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value (git-fixes).\n- crypto: arm/sha - fix function cast warnings (git-fixes).\n- crypto: qat - avoid division by zero (git-fixes).\n- crypto: qat - fix deadlock in backlog processing (git-fixes).\n- crypto: qat - fix double free during reset (git-fixes).\n- crypto: qat - fix state machines cleanup paths (bsc#1218321).\n- crypto: qat - fix unregistration of compression algorithms (git-fixes).\n- crypto: qat - fix unregistration of crypto algorithms (git-fixes).\n- crypto: qat - ignore subsequent state up commands (git-fixes).\n- crypto: qat - increase size of buffers (git-fixes).\n- crypto: qat - resolve race condition during aer recovery (git-fixes).\n- crypto: xilinx - call finalize with bh disabled (git-fixes).\n- doc-guide: kernel-doc: tell about object-like macros (git-fixes).\n- doc/readme.suse: update information about module support status (jsc#ped-5759)\n- drivers: hv: vmbus: Calculate ring buffer size for more efficient use of memory (git-fixes).\n- drm/amd/display: add fams validation before trying to use it (git-fixes).\n- drm/amd/display: add fb_damage_clips support (git-fixes).\n- drm/amd/display: add function for validate and update new stream (git-fixes).\n- drm/amd/display: add odm case when looking for first split pipe (git-fixes).\n- drm/amd/display: always switch off odm before committing more streams (git-fixes).\n- drm/amd/display: avoid abm when odm combine is enabled for edp (git-fixes).\n- drm/amd/display: blocking invalid 420 modes on hdmi tmds for dcn31 (git-fixes).\n- drm/amd/display: check if link state is valid (git-fixes).\n- drm/amd/display: clean code-style issues in dcn30_set_mpc_shaper_3dlut (git-fixes).\n- drm/amd/display: copy dc context in the commit streams (git-fixes).\n- drm/amd/display: dc.h: eliminate kernel-doc warnings (git-fixes).\n- drm/amd/display: disable psr-su on parade 0803 tcon again (git-fixes).\n- drm/amd/display: enable fast plane updates on dcn3.2 and above (git-fixes).\n- drm/amd/display: enable new commit sequence only for dcn32x (git-fixes).\n- drm/amd/display: ensure async flips are only accepted for fast updates (git-fixes).\n- drm/amd/display: exit idle optimizations before attempt to access phy (git-fixes).\n- drm/amd/display: expand kernel doc for dc (git-fixes).\n- drm/amd/display: fix a bug when searching for insert_above_mpcc (git-fixes).\n- drm/amd/display: fix a null pointer dereference in amdgpu_dm_i2c_xfer() (git-fixes).\n- drm/amd/display: fix a potential buffer overflow in 'dp_dsc_clock_en_read()' (git-fixes).\n- drm/amd/display: fix abm disablement (git-fixes).\n- drm/amd/display: fix dc/core/dc.c kernel-doc (git-fixes).\n- drm/amd/display: fix hw rotated modes when psr-su is enabled (git-fixes).\n- drm/amd/display: fix kernel-doc issues in dc.h (git-fixes).\n- drm/amd/display: fix possible underflow for displays with large vblank (git-fixes).\n- drm/amd/display: fix the delta clamping for shaper lut (git-fixes).\n- drm/amd/display: fix unbounded requesting for high pixel rate modes on dcn315 (git-fixes).\n- drm/amd/display: fix underflow issue on 175hz timing (git-fixes).\n- drm/amd/display: for prefetch mode \u003e 0, extend prefetch if possible (git-fixes).\n- drm/amd/display: guard against invalid rptr/wptr being set (git-fixes).\n- drm/amd/display: guard dcn31 phyd32clk logic against chip family (git-fixes).\n- drm/amd/display: handle range offsets in vrr ranges (stable-fixes).\n- drm/amd/display: handle seamless boot stream (git-fixes).\n- drm/amd/display: handle virtual hardware detect (git-fixes).\n- drm/amd/display: include surface of unaffected streams (git-fixes).\n- drm/amd/display: include udelay when waiting for inbox0 ack (git-fixes).\n- drm/amd/display: increase frame warning limit with kasan or kcsan in dml (git-fixes).\n- drm/amd/display: keep phy active for dp config (git-fixes).\n- drm/amd/display: perform a bounds check before filling dirty rectangles (git-fixes).\n- drm/amd/display: prevent vtotal from being set to 0 (git-fixes).\n- drm/amd/display: remove min_dst_y_next_start check for z8 (git-fixes).\n- drm/amd/display: restore rptr/wptr for dmcub as workaround (git-fixes).\n- drm/amd/display: return the correct hdcp error code (stable-fixes).\n- drm/amd/display: revert vblank change that causes null pointer crash (git-fixes).\n- drm/amd/display: rework comments on dc file (git-fixes).\n- drm/amd/display: rework context change check (git-fixes).\n- drm/amd/display: set minimum requirement for using psr-su on phoenix (git-fixes).\n- drm/amd/display: set minimum requirement for using psr-su on rembrandt (git-fixes).\n- drm/amd/display: set per pipe dppclk to 0 when dpp is off (git-fixes).\n- drm/amd/display: update correct dcn314 register header (git-fixes).\n- drm/amd/display: update extended blank for dcn314 onwards (git-fixes).\n- drm/amd/display: update min z8 residency time to 2100 for dcn314 (git-fixes).\n- drm/amd/display: update otg instance in the commit stream (git-fixes).\n- drm/amd/display: use dram speed from validation for dummy p-state (git-fixes).\n- drm/amd/display: use dtbclk as refclk instead of dprefclk (git-fixes).\n- drm/amd/display: use low clocks for no plane configs (git-fixes).\n- drm/amd/display: use min transition for all subvp plane add/remove (git-fixes).\n- drm/amd/display: write to correct dirty_rect (git-fixes).\n- drm/amd/display: wrong colorimetry workaround (git-fixes).\n- drm/amd/pm: fix a memleak in aldebaran_tables_init (git-fixes).\n- drm/amd/pm: fix error of maco flag setting code (git-fixes).\n- drm/amd/smu: use averagegfxclkfrequency* to replace previous gfx curr clock (git-fixes).\n- drm/amd: enable pcie pme from d3 (git-fixes).\n- drm/amdgpu/pm: fix the error of pwm1_enable setting (stable-fixes).\n- drm/amdgpu/pm: make gfxclock consistent for sienna cichlid (git-fixes).\n- drm/amdgpu/pm: make mclk consistent for smu 13.0.7 (git-fixes).\n- drm/amdgpu/smu13: drop compute workload workaround (git-fixes).\n- drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag (stable-fixes).\n- drm/amdgpu: enable gpu reset for s3 abort cases on raven series (stable-fixes).\n- drm/amdgpu: fix missing break in atom_arg_imm case of atom_get_src_int() (git-fixes).\n- drm/amdgpu: force order between a read and write to the same address (git-fixes).\n- drm/amdgpu: lower cs errors to debug severity (git-fixes).\n- drm/amdgpu: match against exact bootloader status (git-fixes).\n- drm/amdgpu: unset context priority is now invalid (git-fixes).\n- drm/amdgpu: update min() to min_t() in 'amdgpu_info_ioctl' (git-fixes).\n- drm/amdkfd: fix tlb flush after unmap for gfx9.4.2 (stable-fixes).\n- drm/bridge: tc358762: instruct dsi host to generate hse packets (git-fixes).\n- drm/display: fix typo (git-fixes).\n- drm/edid: add quirk for osvr hdk 2.0 (git-fixes).\n- drm/etnaviv: restore some id values (git-fixes).\n- drm/exynos: do not return negative values from .get_modes() (stable-fixes).\n- drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable() (git-fixes).\n- drm/i915/bios: tolerate devdata==null in intel_bios_encoder_supports_dp_dual_mode() (stable-fixes).\n- drm/i915/gt: do not generate the command streamer for all the ccs (git-fixes).\n- drm/i915/gt: reset queue_priority_hint on parking (git-fixes).\n- drm/i915/gt: use i915_vm_put on ppgtt_create error paths (git-fixes).\n- drm/i915/selftests: fix dependency of some timeouts on hz (git-fixes).\n- drm/i915: add missing ccs documentation (git-fixes).\n- drm/i915: call intel_pre_plane_updates() also for pipes getting enabled (git-fixes).\n- drm/i915: check before removing mm notifier (git-fixes).\n- drm/lima: fix a memleak in lima_heap_alloc (git-fixes).\n- drm/mediatek: dsi: fix dsi rgb666 formats and definitions (git-fixes).\n- drm/mediatek: fix a null pointer crash in mtk_drm_crtc_finish_page_flip (git-fixes).\n- drm/msm/dpu: add division of drm_display_mode's hskew parameter (git-fixes).\n- drm/msm/dpu: fix the programming of intf_cfg2_data_hctl_en (git-fixes).\n- drm/msm/dpu: improve dsc allocation (git-fixes).\n- drm/msm/dpu: only enable dsc_mode_multiplex if dsc_merge is enabled (git-fixes).\n- drm/panel-edp: use put_sync in unprepare (git-fixes).\n- drm/panel: auo,b101uan08.3: fine tune the panel power sequence (git-fixes).\n- drm/panel: boe-tv101wum-nl6: fine tune the panel power sequence (git-fixes).\n- drm/panel: do not return negative error codes from drm_panel_get_modes() (stable-fixes).\n- drm/panel: move aux b116xw03 out of panel-edp back to panel-simple (git-fixes).\n- drm/panfrost: fix power transition timeout warnings (git-fixes).\n- drm/probe-helper: warn about negative .get_modes() (stable-fixes).\n- drm/qxl: remove unused `count` variable from `qxl_surface_id_alloc()` (git-fixes).\n- drm/qxl: remove unused variable from `qxl_process_single_command()` (git-fixes).\n- drm/radeon/ni: fix wrong firmware size logging in ni_init_microcode() (git-fixes).\n- drm/radeon/ni_dpm: remove redundant null check (git-fixes).\n- drm/radeon: remove dead code in ni_mc_load_microcode() (git-fixes).\n- drm/rockchip: dsi: clean up 'usage_mode' when failing to attach (git-fixes).\n- drm/rockchip: inno_hdmi: fix video timing (git-fixes).\n- drm/rockchip: lvds: do not overwrite error code (git-fixes).\n- drm/rockchip: lvds: do not print scary message when probing defer (git-fixes).\n- drm/tegra: dpaux: fix pm disable depth imbalance in tegra_dpaux_probe (git-fixes).\n- drm/tegra: dsi: add missing check for of_find_device_by_node (git-fixes).\n- drm/tegra: dsi: fix missing pm_runtime_disable() in the error handling path of tegra_dsi_probe() (git-fixes).\n- drm/tegra: dsi: fix some error handling paths in tegra_dsi_probe() (git-fixes).\n- drm/tegra: dsi: make use of the helper function dev_err_probe() (stable-fixes).\n- drm/tegra: hdmi: convert to devm_platform_ioremap_resource() (stable-fixes).\n- drm/tegra: hdmi: fix some error handling paths in tegra_hdmi_probe() (git-fixes).\n- drm/tegra: output: fix missing i2c_put_adapter() in the error handling paths of tegra_output_probe() (git-fixes).\n- drm/tegra: put drm_gem_object ref on error in tegra_fb_create (git-fixes).\n- drm/tegra: rgb: fix missing clk_put() in the error handling paths of tegra_dc_rgb_probe() (git-fixes).\n- drm/tegra: rgb: fix some error handling paths in tegra_dc_rgb_probe() (git-fixes).\n- drm/tidss: fix initial plane zpos values (git-fixes).\n- drm/tidss: fix sync-lost issue with two displays (git-fixes).\n- drm/ttm: do not leak a resource on eviction error (git-fixes).\n- drm/ttm: do not print error message if eviction was interrupted (git-fixes).\n- drm/vc4: add module dependency on hdmi-codec (git-fixes).\n- drm/vmwgfx: create debugfs ttm_resource_manager entry only if needed (git-fixes).\n- drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node (git-fixes).\n- drm/vmwgfx: fix possible null pointer derefence with invalid contexts (git-fixes).\n- drm: do not treat 0 as -1 in drm_fixp2int_ceil (git-fixes).\n- drm: fix drm_fixp2int_round() making it add 0.5 (git-fixes).\n- drm: panel-orientation-quirks: add quirk for acer switch v 10 (sw5-017) (git-fixes).\n- firewire: core: use long bus reset on gap count error (stable-fixes).\n- fix 'coresight: etm4x: Change etm4_platform_driver driver for MMIO devices' (bsc#1220775)\n- hid: amd_sfh: Update HPD sensor structure elements (git-fixes).\n- hid: lenovo: Add middleclick_workaround sysfs knob for cptkbd (git-fixes).\n- hid: multitouch: Add required quirk for Synaptics 0xcddc device (stable-fixes).\n- hv_netvsc: calculate correct ring size when page_size is not 4 kbytes (git-fixes).\n- hv_netvsc: fix race condition between netvsc_probe and netvsc_remove (git-fixes).\n- hv_netvsc: register vf in netvsc_probe if net_device_register missed (git-fixes).\n- i2c: aspeed: fix the dummy irq expected print (git-fixes).\n- i2c: i801: avoid potential double call to gpiod_remove_lookup_table (git-fixes).\n- i2c: wmt: fix an error handling path in wmt_i2c_probe() (git-fixes).\n- ib/ipoib: Fix mcast list locking (git-fixes)\n- iio: dummy_evgen: remove excess kernel-doc comments (git-fixes).\n- iio: pressure: dlhl60d: initialize empty dlh bytes (git-fixes).\n- input: gpio_keys_polled - suppress deferred probe error for gpio (stable-fixes).\n- input: i8042 - add Fujitsu Lifebook E5411 to i8042 quirk table (git-fixes).\n- input: i8042 - add Fujitsu Lifebook U728 to i8042 quirk table (git-fixes).\n- input: i8042 - add quirk for Fujitsu Lifebook A574/H (git-fixes).\n- input: i8042 - fix strange behavior of touchpad on Clevo NS70PU (git-fixes).\n- input: pm8941-powerkey - fix debounce on gen2+ PMICs (git-fixes).\n- input: pm8941-pwrkey - add software key press debouncing support (git-fixes).\n- input: pm8941-pwrkey - add support for PON GEN3 base addresses (git-fixes).\n- input: synaptics-rmi4 - fix UAF of IRQ domain on driver removal (git-fixes).\n- input: xpad - add Lenovo Legion Go controllers (git-fixes).\n- iommu/amd: mark interrupt as managed (git-fixes).\n- iommu/dma: trace bounce buffer usage when mapping buffers (git-fixes).\n- iommu/mediatek-v1: fix an error handling path in mtk_iommu_v1_probe() (git-fixes).\n- iommu/mediatek: fix forever loop in error handling (git-fixes).\n- iommu/vt-d: allow to use flush-queue when first level is default (git-fixes).\n- iommu/vt-d: do not issue ats invalidation request when device is disconnected (git-fixes).\n- iommu/vt-d: fix pasid directory pointer coherency (git-fixes).\n- iommu/vt-d: set no execute enable bit in pasid table entry (git-fixes).\n- kabi: pci: add locking to rmw pci express capability register accessors (kabi).\n- kconfig: fix infinite loop when expanding a macro at the end of file (git-fixes).\n- kvm: s390: only deliver the set service event bits (git-fixes bsc#1221631).\n- lan78xx: enable auto speed configuration for lan7850 if no eeprom is detected (git-commit).\n- leds: aw2013: unlock mutex before destroying it (git-fixes).\n- lib/cmdline: fix an invalid format specifier in an assertion msg (git-fixes).\n- make nvidiA Grace-Hopper TPM related drivers build-ins (bsc#1221156)\n- md/raid10: check slab-out-of-bounds in md_bitmap_get_counter (git-fixes).\n- md/raid5: release batch_last before waiting for another stripe_head (git-fixes).\n- md/raid6: use valid sector values to determine if an i/o should wait on the reshape (git-fixes).\n- md: do not ignore suspended array in md_check_recovery() (git-fixes).\n- md: do not leave 'md_recovery_frozen' in error path of md_set_readonly() (git-fixes).\n- md: fix data corruption for raid456 when reshape restart while grow up (git-fixes).\n- md: introduce md_ro_state (git-fixes).\n- md: make sure md_do_sync() will set md_recovery_done (git-fixes).\n- md: whenassemble the array, consult the superblock of the freshest device (git-fixes).\n- media: dvb-frontends: avoid stack overflow warnings with clang (git-fixes).\n- media: edia: dvbdev: fix a use-after-free (git-fixes).\n- media: em28xx: annotate unchecked call to media_device_register() (git-fixes).\n- media: go7007: add check of return value of go7007_read_addr() (git-fixes).\n- media: go7007: fix a memleak in go7007_load_encoder (git-fixes).\n- media: imx: csc/scaler: fix v4l2_ctrl_handler memory leak (git-fixes).\n- media: pvrusb2: fix pvr2_stream_callback casts (git-fixes).\n- media: pvrusb2: fix uaf in pvr2_context_set_notify (git-fixes).\n- media: pvrusb2: remove redundant null check (git-fixes).\n- media: staging: ipu3-imgu: set fields before media_entity_pads_init() (git-fixes).\n- media: sun8i-di: fix chroma difference threshold (git-fixes).\n- media: sun8i-di: fix coefficient writes (git-fixes).\n- media: sun8i-di: fix power on/off sequences (git-fixes).\n- media: tc358743: register v4l2 async device only after successful setup (git-fixes).\n- media: ttpci: fix two memleaks in budget_av_attach (git-fixes).\n- media: usbtv: remove useless locks in usbtv_video_free() (git-fixes).\n- media: v4l2-mem2mem: fix a memleak in v4l2_m2m_register_entity (git-fixes).\n- media: v4l2-tpg: fix some memleaks in tpg_alloc (git-fixes).\n- media: xc4000: fix atomicity violation in xc4000_get_frequency (git-fixes).\n- mfd: altera-sysmgr: call of_node_put() only when of_parse_phandle() takes a ref (git-fixes).\n- mfd: syscon: call of_node_put() only when of_parse_phandle() takes a ref (git-fixes).\n- mm,page_owner: Defer enablement of static branch (bsc#1222366).\n- mm,page_owner: check for null stack_record before bumping its refcount (bsc#1222366).\n- mm,page_owner: drop unnecessary check (bsc#1222366).\n- mm,page_owner: fix accounting of pages when migrating (bsc#1222366).\n- mm,page_owner: fix printing of stack records (bsc#1222366).\n- mm,page_owner: fix recursion (bsc#1222366).\n- mm,page_owner: fix refcount imbalance (bsc#1222366).\n- mm,page_owner: update metadata for tail pages (bsc#1222366).\n- mm/vmalloc: huge vmalloc backing pages should be split rather than compound (bsc#1217829).\n- mmc: core: avoid negative index with array access (git-fixes).\n- mmc: core: fix switch on gp3 partition (git-fixes).\n- mmc: core: initialize mmc_blk_ioc_data (git-fixes).\n- mmc: mmci: stm32: fix dma api overlapping mappings warning (git-fixes).\n- mmc: mmci: stm32: use a buffer for unaligned dma requests (git-fixes).\n- mmc: tmio: avoid concurrent runs of mmc_request_done() (git-fixes).\n- mmc: wmt-sdmmc: remove an incorrect release_mem_region() call in the .remove function (git-fixes).\n- mtd: maps: physmap-core: fix flash size larger than 32-bit (git-fixes).\n- mtd: rawnand: lpc32xx_mlc: fix irq handler prototype (git-fixes).\n- mtd: rawnand: meson: fix scrambling mode value in command macro (git-fixes).\n- net/bnx2x: prevent access to a freed page in page_pool (bsc#1215322).\n- net/x25: fix incorrect parameter validation in the x25_getsockopt() function (git-fixes).\n- net: fix features skip in for_each_netdev_feature() (git-fixes).\n- net: lan78xx: fix runtime pm count underflow on link stop (git-fixes).\n- net: ll_temac: platform_get_resource replaced by wrong function (git-fixes).\n- net: mana: fix rx dma datasize and skb_over_panic (git-fixes).\n- net: phy: fix phy_get_internal_delay accessing an empty array (git-fixes).\n- net: sunrpc: fix an off by one in rpc_sockaddr2uaddr() (git-fixes).\n- net: usb: dm9601: fix wrong return value in dm9601_mdio_read (git-fixes).\n- nfc: nci: fix uninit-value in nci_dev_up and nci_ntf_packet (git-fixes).\n- nfs: fix an off by one in root_nfs_cat() (git-fixes).\n- nfs: rename nfs_client_kset to nfs_kset (git-fixes).\n- nfsd: change LISTXATTRS cookie encoding to big-endian (git-fixes).\n- nfsd: convert the callback workqueue to use delayed_work (git-fixes).\n- nfsd: do not take fi_lock in nfsd_break_deleg_cb() (git-fixes).\n- nfsd: fix LISTXATTRS returning a short list with eof=TRUE (git-fixes).\n- nfsd: fix LISTXATTRS returning more bytes than maxcount (git-fixes).\n- nfsd: fix file memleak on client_opens_release (git-fixes).\n- nfsd: fix nfsd4_listxattr_validate_cookie (git-fixes).\n- nfsd: lock_rename() needs both directories to live on the same fs (git-fixes).\n- nfsd: reschedule CB operations when backchannel rpc_clnt is shut down (git-fixes).\n- nfsd: reset cb_seq_status after NFS4ERR_DELAY (git-fixes).\n- nfsd: retransmit callbacks after client reconnects (git-fixes).\n- nfsd: use vfs setgid helper (git-fixes).\n- nfsv4.1/pnfs: Ensure we handle the error NFS4ERR_RETURNCONFLICT (git-fixes).\n- nfsv4.1: fix SP4_MACH_CRED protection for pnfs IO (git-fixes).\n- nfsv4.1: fixup use EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nfsv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nfsv4.2: fix listxattr maximum XDR buffer size (git-fixes).\n- nfsv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 (git-fixes).\n- nfsv4.2: fix wrong shrinker_id (git-fixes).\n- nfsv4: fix a nfs4_state_manager() race (git-fixes).\n- nfsv4: fix a state manager thread deadlock regression (git-fixes).\n- nilfs2: fix failure to detect dat corruption in btree and direct mappings (git-fixes).\n- nilfs2: prevent kernel bug at submit_bh_wbc() (git-fixes).\n- nouveau/dmem: handle kcalloc() allocation failure (git-fixes).\n- nouveau: reset the bo resource bus info after an eviction (git-fixes).\n- ntfs: fix use-after-free in ntfs_ucsncmp() (bsc#1221713).\n- nvme-fc: do not wait in vain when unloading module (git-fixes).\n- nvme: fix reconnection fail due to reserved tag allocation (git-fixes).\n- nvmet-fc: abort command when there is no binding (git-fixes).\n- nvmet-fc: avoid deadlock on delete association path (git-fixes).\n- nvmet-fc: defer cleanup using rcu properly (git-fixes).\n- nvmet-fc: hold reference on hostport match (git-fixes).\n- nvmet-fc: release reference on target port (git-fixes).\n- nvmet-fc: take ref count on tgtport before delete assoc (git-fixes).\n- nvmet-fcloop: swap the list_add_tail arguments (git-fixes).\n- nvmet-tcp: fix nvme tcp ida memory leak (git-fixes).\n- pci/aer: fix rootport attribute paths in ABI docs (git-fixes).\n- pci/aspm: Use RMW accessors for changing LNKCTL (git-fixes).\n- pci/dpc: print all TLP Prefixes, not just the first (git-fixes).\n- pci/msi: prevent MSI hardware interrupt number truncation (bsc#1218777)\n- pci/p2pdma: Fix a sleeping issue in a RCU read section (git-fixes).\n- pci: add locking to RMW PCI Express Capability Register accessors (git-fixes).\n- pci: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq() (git-fixes).\n- pci: dwc: endpoint: Fix advertised resizable BAR size (git-fixes).\n- pci: dwc: endpoint: Fix dw_pcie_ep_raise_msix_irq() alignment support (git-fixes).\n- pci: fu740: Set the number of MSI vectors (git-fixes).\n- pci: lengthen reset delay for VideoPropulsion Torrent QN16e card (git-fixes).\n- pci: make link retraining use RMW accessors for changing LNKCTL (git-fixes).\n- pci: mark 3ware-9650SE Root Port Extended Tags as broken (git-fixes).\n- pci: mediatek-gen3: Fix translation window size calculation (git-fixes).\n- pci: mediatek: Clear interrupt status before dispatching handler (git-fixes).\n- pci: qcom: Enable BDF to SID translation properly (git-fixes).\n- pci: qcom: Use DWC helpers for modifying the read-only DBI registers (git-fixes).\n- pci: rockchip: Do not advertise MSI-X in PCIe capabilities (git-fixes).\n- pci: rockchip: Fix window mapping and address translation for endpoint (git-fixes).\n- pci: rockchip: Use 64-bit mask on MSI 64-bit PCI address (git-fixes).\n- pci: switchtec: Fix an error handling path in switchtec_pci_probe() (git-fixes).\n- pinctrl: mediatek: drop bogus slew rate register range for mt8192 (git-fixes).\n- platform/mellanox: mlxreg-hotplug: Remove redundant NULL-check (git-fixes).\n- pm: suspend: Set mem_sleep_current during kernel command line setup (git-fixes).\n- pnfs/flexfiles: check the layout validity in ff_layout_mirror_prepare_stats (git-fixes).\n- pnfs: fix a hang in nfs4_evict_inode() (git-fixes).\n- pnfs: fix the pnfs block driver's calculation of layoutget size (git-fixes).\n- powerpc/64s: POWER10 CPU Kconfig build option (bsc#1194869).\n- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment (bsc#1194869).\n- powerpc/boot: Fix boot wrapper code generation with CONFIG_POWER10_CPU (bsc#1194869).\n- powerpc/lib/sstep: Do not use __{get/put}_user() on kernel addresses (bsc#1194869).\n- powerpc/lib/sstep: Remove unneeded #ifdef __powerpc64__ (bsc#1194869).\n- powerpc/lib/sstep: Use l1_dcache_bytes() instead of opencoding (bsc#1194869).\n- powerpc/lib/sstep: use truncate_if_32bit() (bsc#1194869).\n- powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV (bsc#1220492 ltc#205270).\n- powerpc/pseries: Fix potential memleak in papr_get_attr() (bsc#1200465 ltc#197256 jsc#SLE-18130 git-fixes).\n- powerpc/sstep: Use bitwise instead of arithmetic operator for flags (bsc#1194869).\n- powerpc: add compile-time support for lbarx, lharx (bsc#1194869).\n- pwm: mediatek: Update kernel doc for struct pwm_mediatek_of_data (git-fixes).\n- qedf: Do not process stag work during unload (bsc#1214852).\n- qedf: Wait for stag work during unload (bsc#1214852).\n- raid1: fix use-after-free for original bio in raid1_write_request() (bsc#1221097).\n- ras/amd/fmpm: Add debugfs interface to print record entries (jsc#PED-7619).\n- ras/amd/fmpm: Avoid NULL ptr deref in get_saved_records() (jsc#PED-7619).\n- ras/amd/fmpm: Fix build when debugfs is not enabled (jsc#PED-7619).\n- ras/amd/fmpm: Fix off by one when unwinding on error (jsc#PED-7619).\n- ras/amd/fmpm: Safely handle saved records of various sizes (jsc#PED-7619).\n- ras/amd/fmpm: Save SPA values (jsc#PED-7619).\n- ras: Avoid build errors when CONFIG_DEBUG_FS=n (git-fixes).\n- ras: export helper to get ras_debugfs_dir (jsc#PED-7619).\n- rdma/device: fix a race between mad_client and cm_client init (git-fixes)\n- rdma/hns: fix mis-modifying default congestion control algorithm (git-fixes)\n- rdma/ipoib: fix error code return in ipoib_mcast_join (git-fixes)\n- rdma/irdma: remove duplicate assignment (git-fixes)\n- rdma/mana_ib: fix bug in creation of dma regions (git-fixes).\n- rdma/mlx5: fix fortify source warning while accessing eth segment (git-fixes)\n- rdma/mlx5: relax devx access upon modify commands (git-fixes)\n- rdma/rtrs-clt: check strnlen return len in sysfs mpath_policy_store() (git-fixes)\n- rdma/srpt: do not register event handler until srpt device is fully setup (git-fixes)\n- revert 'drm/amd: disable psr-su on parade 0803 tcon' (git-fixes).\n- revert 'drm/amd: disable s/g for apus when 64gb or more host memory' (git-fixes).\n- revert 'drm/amdgpu/display: change pipe policy for dcn 2.0' (git-fixes).\n- revert 'drm/amdgpu/display: change pipe policy for dcn 2.1' (git-fixes).\n- revert 'drm/vc4: hdmi: enforce the minimum rate at runtime_resume' (git-fixes).\n- revert 'fbdev: flush deferred io before closing (git-fixes).' (bsc#1221814)\n- revert 'pci: tegra194: enable support for 256 byte payload' (git-fixes).\n- revert 'revert 'drm/amdgpu/display: change pipe policy for dcn 2.0'' (git-fixes).\n- revert 'sunrpc dont update timeout value on connection reset' (git-fixes).\n- ring-buffer: Clean ring_buffer_poll_wait() error return (git-fixes).\n- rtc: mt6397: select IRQ_DOMAIN instead of depending on it (git-fixes).\n- s390/pai: fix attr_event_free upper limit for pai device drivers (git-fixes bsc#1221633).\n- s390/vfio-ap: realize the VFIO_DEVICE_GET_IRQ_INFO ioctl (bsc#1205316).\n- s390/vfio-ap: realize the VFIO_DEVICE_SET_IRQS ioctl (bsc#1205316).\n- s390/vfio-ap: wire in the vfio_device_ops request callback (bsc#1205316).\n- s390/vtime: fix average steal time calculation (git-fixes bsc#1221951).\n- sched/rt: Disallow writing invalid values to sched_rt_period_us (bsc#1220176).\n- sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset (bsc#1220176).\n- scsi: lpfc: Correct size for cmdwqe/rspwqe for memset() (bsc#1221777).\n- scsi: lpfc: Correct size for wqe for memset() (bsc#1221777).\n- scsi: lpfc: Define lpfc_dmabuf type for ctx_buf ptr (bsc#1221777).\n- scsi: lpfc: Define lpfc_nodelist type for ctx_ndlp ptr (bsc#1221777).\n- scsi: lpfc: Define types in a union for generic void *context3 ptr (bsc#1221777).\n- scsi: lpfc: Move NPIV's transport unregistration to after resource clean up (bsc#1221777).\n- scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1221777).\n- scsi: lpfc: Remove IRQF_ONESHOT flag from threaded IRQ handling (bsc#1221777 bsc#1217959).\n- scsi: lpfc: Remove unnecessary log message in queuecommand path (bsc#1221777).\n- scsi: lpfc: Replace hbalock with ndlp lock in lpfc_nvme_unregister_port() (bsc#1221777).\n- scsi: lpfc: Update lpfc version to 14.4.0.1 (bsc#1221777).\n- scsi: lpfc: Update lpfc_ramp_down_queue_handler() logic (bsc#1221777).\n- scsi: lpfc: Use a dedicated lock for ras_fwlog state (bsc#1221777).\n- scsi: qedf: Remove set but unused variable 'page' (bsc#1214852).\n- scsi: qedf: Remove unused 'num_handled' variable (bsc#1214852).\n- scsi: qedf: Remove unused declaration (bsc#1214852).\n- scsi: qla2xxx: Change debug message during driver unload (bsc1221816).\n- scsi: qla2xxx: Delay I/O Abort on PCI error (bsc1221816).\n- scsi: qla2xxx: Fix N2N stuck connection (bsc1221816).\n- scsi: qla2xxx: Fix command flush on cable pull (bsc1221816).\n- scsi: qla2xxx: Fix double free of fcport (bsc1221816).\n- scsi: qla2xxx: Fix double free of the ha-\u003evp_map pointer (bsc1221816).\n- scsi: qla2xxx: NVME|FCP prefer flag not being honored (bsc1221816).\n- scsi: qla2xxx: Prevent command send on chip reset (bsc1221816).\n- scsi: qla2xxx: Split FCE|EFT trace control (bsc1221816).\n- scsi: qla2xxx: Update manufacturer detail (bsc1221816).\n- scsi: qla2xxx: Update version to 10.02.09.200-k (bsc1221816).\n- scsi: storvsc: Fix ring buffer size calculation (git-fixes).\n- scsi: target: core: Silence the message about unknown VPD pages (bsc#1221252).\n- selftests/bpf: add generic BPF program tester-loader (bsc#1222033).\n- serial: 8250_exar: Do not remove GPIO device on suspend (git-fixes).\n- serial: max310x: fix syntax error in IRQ error message (git-fixes).\n- slimbus: core: Remove usage of the deprecated ida_simple_xx() API (git-fixes).\n- soc: fsl: qbman: Always disable interrupts when taking cgr_lock (git-fixes).\n- spi: lm70llp: fix links in doc and comments (git-fixes).\n- spi: spi-mt65xx: Fix NULL pointer access in interrupt handler (git-fixes).\n- sr9800: Add check for usbnet_get_endpoints (git-fixes).\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- staging: vc04_services: fix information leak in create_component() (git-fixes).\n- sunrpc: add an is_err() check back to where it was (git-fixes).\n- sunrpc: econnreset might require a rebind (git-fixes).\n- sunrpc: fix a memleak in gss_import_v2_context (git-fixes).\n- sunrpc: fix a suspicious rcu usage warning (git-fixes).\n- sunrpc: fix rpc client cleaned up the freed pipefs dentries (git-fixes).\n- sunrpc: fix some memleaks in gssx_dec_option_array (git-fixes).\n- svcrdma: Drop connection after an RDMA Read error (git-fixes).\n- topology/sysfs: Hide PPIN on systems that do not support it (jsc#PED-7618).\n- topology: Fix up build warning in topology_is_visible() (jsc#PED-7618).\n- tracing/probes: Fix to show a parse error for bad type for $comm (git-fixes).\n- tracing: Fix wasted memory in saved_cmdlines logic (git-fixes).\n- tracing: Inform kmemleak of saved_cmdlines allocation (git-fixes).\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (bsc#1222619).\n- tty: serial: fsl_lpuart: avoid idle preamble pending if CTS is enabled (git-fixes).\n- tty: serial: samsung: fix tx_empty() to return TIOCSER_TEMT (git-fixes).\n- tty: vt: fix 20 vs 0x20 typo in EScsiignore (git-fixes).\n- ubifs: Queue up space reservation tasks if retrying many times (git-fixes).\n- ubifs: Remove unreachable code in dbg_check_ltab_lnum (git-fixes).\n- ubifs: Set page uptodate in the correct place (git-fixes).\n- ubifs: dbg_check_idx_size: Fix kmemleak if loading znode failed (git-fixes).\n- ubifs: fix sort function prototype (git-fixes).\n- usb: audio-v2: Correct comments for struct uac_clock_selector_descriptor (git-fixes).\n- usb: cdc-wdm: close race between read and workqueue (git-fixes).\n- usb: core: fix deadlock in usb_deauthorize_interface() (git-fixes).\n- usb: dwc2: gadget: Fix exiting from clock gating (git-fixes).\n- usb: dwc2: gadget: LPM flow fix (git-fixes).\n- usb: dwc2: host: Fix ISOC flow in DDMA mode (git-fixes).\n- usb: dwc2: host: Fix hibernation flow (git-fixes).\n- usb: dwc2: host: Fix remote wakeup from hibernation (git-fixes).\n- usb: dwc3: Properly set system wakeup (git-fixes).\n- usb: f_mass_storage: forbid async queue when shutdown happen (git-fixes).\n- usb: gadget: ncm: Fix handling of zero block length packets (git-fixes).\n- usb: gadget: net2272: Use irqflags in the call to net2272_probe_fin (git-fixes).\n- usb: hub: Replace hardcoded quirk value with BIT() macro (git-fixes).\n- usb: port: Do not try to peer unused USB ports based on location (git-fixes).\n- usb: typec: Return size of buffer if pd_set operation succeeds (git-fixes).\n- usb: typec: ucsi: Check for notifications after init (git-fixes).\n- usb: typec: ucsi: Clean up UCSI_CABLE_PROP macros (git-fixes).\n- usb: typec: ucsi: Clear EVENT_PENDING under PPM lock (git-fixes).\n- usb: usb-storage: prevent divide-by-0 error in isd200_ata_command (git-fixes).\n- usb: xhci: Add error handling in xhci_map_urb_for_dma (git-fixes).\n- vboxsf: Avoid an spurious warning if load_nls_xxx() fails (git-fixes).\n- vt: fix unicode buffer corruption when deleting characters (git-fixes).\n- watchdog: stm32_iwdg: initialize default timeout (git-fixes).\n- wifi: ath10k: fix NULL pointer dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() (git-fixes).\n- wifi: ath11k: decrease MHI channel buffer length to 8KB (bsc#1207948).\n- wifi: ath11k: initialize rx_mcs_80 and rx_mcs_160 before use (git-fixes).\n- wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete (git-fixes).\n- wifi: b43: Disable QoS for bcm4331 (git-fixes).\n- wifi: b43: Stop correct queue in DMA worker when QoS is disabled (git-fixes).\n- wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled (git-fixes).\n- wifi: b43: Stop/wake correct queue in PIO Tx path when QoS is disabled (git-fixes).\n- wifi: brcmfmac: fix copyright year mentioned in platform_data header (git-fixes).\n- wifi: brcmsmac: avoid function pointer casts (git-fixes).\n- wifi: iwlwifi: dbg-tlv: ensure NUL termination (git-fixes).\n- wifi: iwlwifi: fix EWRD table validity check (git-fixes).\n- wifi: iwlwifi: fw: do not always use FW dump trig (git-fixes).\n- wifi: iwlwifi: mvm: do not set replay counters to 0xff (git-fixes).\n- wifi: iwlwifi: mvm: report beacon protection failures (git-fixes).\n- wifi: iwlwifi: mvm: rfi: fix potential response leaks (git-fixes).\n- wifi: iwlwifi: mvm: use FW rate for non-data only on new devices (git-fixes).\n- wifi: libertas: fix some memleaks in lbs_allocate_cmd_buffer() (git-fixes).\n- wifi: mwifiex: debugfs: Drop unnecessary error check for debugfs_create_dir() (git-fixes).\n- wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work (git-fixes).\n- wifi: rtw88: 8821c: Fix false alarm count (git-fixes).\n- wifi: wilc1000: fix RCU usage in connect path (git-fixes).\n- wifi: wilc1000: fix declarations ordering (stable-fixes).\n- wifi: wilc1000: fix multi-vif management when deleting a vif (git-fixes).\n- wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces (git-fixes).\n- x86/CPU/AMD: Update the Zenbleed microcode revisions (git-fixes).\n- x86/bugs: Fix the SRSO mitigation on Zen3/4 (git-fixes).\n- x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (git-fixes).\n- xhci: handle isoc Babble and Buffer Overrun events properly (git-fixes).\n- xhci: process isoc TD properly when there was a transaction error mid TD (git-fixes).\n","status":"published","published":"2024-04-30T14:02:00Z","modified":"2026-02-04T03:48:09.931728Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1490-1","title":"Security update for the Linux Kernel","description":"\n\nThe SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2021-46925: Fixed kernel panic caused by race of smc_sock (bsc#1220466).\n- CVE-2021-46926: Fixed bug when detecting controllers in ALSA/hda/intel-sdw-acpi (bsc#1220478).\n- CVE-2021-46927: Fixed assertion bug in nitro_enclaves: Use get_user_pages_unlocked() (bsc#1220443).\n- CVE-2021-46929: Fixed use-after-free issue in sctp_sock_dump() (bsc#1220482).\n- CVE-2021-46930: Fixed usb/mtu3 list_head check warning (bsc#1220484).\n- CVE-2021-46931: Fixed wrong type casting in mlx5e_tx_reporter_dump_sq() (bsc#1220486).\n- CVE-2021-46933: Fixed possible underflow in ffs_data_clear() (bsc#1220487).\n- CVE-2021-46936: Fixed use-after-free in tw_timer_handler() (bsc#1220439).\n- CVE-2021-47082: Fixed ouble free in tun_free_netdev() (bsc#1220969).\n- CVE-2021-47087: Fixed incorrect page free bug in tee/optee (bsc#1220954).\n- CVE-2021-47091: Fixed locking in ieee80211_start_ap()) error path (bsc#1220959).\n- CVE-2021-47093: Fixed memleak on registration failure in intel_pmc_core (bsc#1220978).\n- CVE-2021-47094: Fixed possible memory leak in KVM x86/mmu (bsc#1221551).\n- CVE-2021-47095: Fixed missing initialization in ipmi/ssif (bsc#1220979).\n- CVE-2021-47096: Fixed uninitalized user_pversion in ALSA rawmidi (bsc#1220981).\n- CVE-2021-47097: Fixed stack out of bound access in elantech_change_report_id() (bsc#1220982).\n- CVE-2021-47098: Fixed integer overflow/underflow in hysteresis calculations hwmon: (lm90) (bsc#1220983).\n- CVE-2021-47099: Fixed BUG_ON assertion in veth when skb entering GRO are cloned (bsc#1220955).\n- CVE-2021-47100: Fixed UAF when uninstall in ipmi (bsc#1220985).\n- CVE-2021-47101: Fixed uninit-value in asix_mdio_read() (bsc#1220987).\n- CVE-2021-47102: Fixed incorrect structure access In line: upper = info-\u003eupper_dev in net/marvell/prestera (bsc#1221009).\n- CVE-2021-47104: Fixed memory leak in qib_user_sdma_queue_pkts() (bsc#1220960).\n- CVE-2021-47105: Fixed potential memory leak in ice/xsk (bsc#1220961).\n- CVE-2021-47107: Fixed READDIR buffer overflow in NFSD (bsc#1220965).\n- CVE-2021-47108: Fixed possible NULL pointer dereference for mtk_hdmi_conf in drm/mediatek (bsc#1220986).\n- CVE-2021-47181: Fixed a null pointer dereference caused by calling platform_get_resource()  (bsc#1222660).\n- CVE-2021-47182: Fixed buffer length handling in scsi_mode_sense() in scsi core (bsc#1222662).\n- CVE-2021-47183: Fixed a null pointer dereference during link down processing in scsi lpfc (bsc#1192145, bsc#1222664).\n- CVE-2021-47185: Fixed a softlockup issue in flush_to_ldisc in tty tty_buffer (bsc#1222669).\n- CVE-2021-47189: Fixed denial of service due to memory ordering issues between normal and ordered work functions in btrfs (bsc#1222706).\n- CVE-2022-4744: Fixed double-free that could lead to DoS or privilege escalation in TUN/TAP device driver functionality (bsc#1209635).\n- CVE-2022-48626: Fixed a potential use-after-free on remove path moxart (bsc#1220366).\n- CVE-2022-48629: Fixed possible memory leak in qcom-rng (bsc#1220989).\n- CVE-2022-48630: Fixed infinite loop on requests not multiple of WORD_SZ in crypto: qcom-rng (bsc#1220990).\n- CVE-2023-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system (bsc#1209657).\n- CVE-2023-28746: Fixed Register File Data Sampling (bsc#1213456).\n- CVE-2023-35827: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1212514).\n- CVE-2023-4881: Fixed a out-of-bounds write flaw in the netfilter subsystem that could lead to potential information disclosure or a denial of service (bsc#1215221).\n- CVE-2023-52447: Fixed map_fd_put_ptr() signature kABI workaround  (bsc#1220251).\n- CVE-2023-52450: Fixed NULL pointer dereference issue in upi_fill_topology() (bsc#1220237).\n- CVE-2023-52453: Fixed data corruption in hisi_acc_vfio_pci (bsc#1220337).\n- CVE-2023-52454: Fixed a kernel panic when host sends an invalid H2C PDU length (bsc#1220320).\n- CVE-2023-52469: Fixed a use-after-free in kv_parse_power_table (bsc#1220411).\n- CVE-2023-52470: Fixed null-ptr-deref in radeon_crtc_init() (bsc#1220413).\n- CVE-2023-52474: Fixed a vulnerability with non-PAGE_SIZE-end multi-iovec user SDMA requests (bsc#1220445).\n- CVE-2023-52476: Fixed possible unhandled page fault via perf sampling NMI during vsyscall (bsc#1220703).\n- CVE-2023-52477: Fixed USB Hub accesses to uninitialized BOS descriptors (bsc#1220790).\n- CVE-2023-52481: Fixed speculative unprivileged load in Cortex-A520 (bsc#1220887).\n- CVE-2023-52484: Fixed a soft lockup triggered by arm_smmu_mm_invalidate_range (bsc#1220797).\n- CVE-2023-52486: Fixed possible use-after-free in drm (bsc#1221277).\n- CVE-2023-52488: Fixed data corruption due to error on incrementing register address in regmap functions for FIFO in serial sc16is7xx (bsc#1221162).\n- CVE-2023-52492: Fixed a null-pointer-dereference in channel unregistration function __dma_async_device_channel_register() (bsc#1221276).\n- CVE-2023-52493: Fixed possible soft lockup in bus/mhi/host (bsc#1221274).\n- CVE-2023-52494: Fixed missing alignment check for event ring read pointer in bus/mhi/host (bsc#1221273).\n- CVE-2023-52497: Fixed data corruption in erofs (bsc#1220879).\n- CVE-2023-52500: Fixed information leaking when processing OPC_INB_SET_CONTROLLER_CONFIG command (bsc#1220883).\n- CVE-2023-52501: Fixed possible memory corruption in ring-buffer (bsc#1220885).\n- CVE-2023-52502: Fixed a race condition in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() (bsc#1220831).\n- CVE-2023-52503: Fixed use-after-free in amdtee_close_session due to race condition with amdtee_open_session in tee amdtee (bsc#1220915).\n- CVE-2023-52504: Fixed possible out-of bounds in apply_alternatives() on a 5-level paging machine (bsc#1221553).\n- CVE-2023-52507: Fixed possible shift-out-of-bounds in nfc/nci (bsc#1220833).\n- CVE-2023-52508: Fixed null pointer dereference in nvme_fc_io_getuuid() (bsc#1221015).\n- CVE-2023-52509: Fixed a use-after-free issue in ravb_tx_timeout_work() (bsc#1220836).\n- CVE-2023-52510: Fixed a potential UAF in ca8210_probe() (bsc#1220898).\n- CVE-2023-52511: Fixed possible memory corruption in spi/sun6i (bsc#1221012).\n- CVE-2023-52513: Fixed connection failure handling  in RDMA/siw (bsc#1221022).\n- CVE-2023-52515: Fixed possible use-after-free in RDMA/srp (bsc#1221048).\n- CVE-2023-52517: Fixed race between DMA RX transfer completion and RX FIFO drain in spi/sun6i (bsc#1221055).\n- CVE-2023-52518: Fixed information leak in bluetooth/hci_codec (bsc#1221056).\n- CVE-2023-52519: Fixed possible overflow in HID/intel-ish-hid/ipc (bsc#1220920).\n- CVE-2023-52520: Fixed reference leak in platform/x86/think-lmi (bsc#1220921).\n- CVE-2023-52523: Fixed wrong redirects to non-TCP sockets in bpf (bsc#1220926).\n- CVE-2023-52524: Fixed possible corruption in nfc/llcp (bsc#1220927).\n- CVE-2023-52525: Fixed out of bounds check mwifiex_process_rx_packet() (bsc#1220840).\n- CVE-2023-52528: Fixed uninit-value access in __smsc75xx_read_reg() (bsc#1220843).\n- CVE-2023-52529: Fixed a potential memory leak in sony_probe() (bsc#1220929).\n- CVE-2023-52532: Fixed a bug in TX CQE error handling (bsc#1220932).\n- CVE-2023-52561: Fixed denial of service due to missing reserved attribute on cont splash memory region in arm64 dts qcom sdm845-db845c (bsc#1220935).\n- CVE-2023-52563: Fixed memory leak on -\u003ehpd_notify callback() in drm/meson (bsc#1220937).\n- CVE-2023-52564: Reverted invalid fix for UAF in gsm_cleanup_mux() (bsc#1220938).\n- CVE-2023-52566: Fixed potential use after free in nilfs_gccache_submit_read_data() (bsc#1220940).\n- CVE-2023-52567: Fixed possible Oops in  serial/8250_port: when using IRQ polling (irq = 0) (bsc#1220839).\n- CVE-2023-52569: Fixed a bug in btrfs by remoning BUG() after failure to insert delayed dir index item (bsc#1220918).\n- CVE-2023-52574: Fixed a bug by hiding new member header_ops (bsc#1220870).\n- CVE-2023-52575: Fixed SBPB enablement for spec_rstack_overflow=off (bsc#1220871).\n- CVE-2023-52576: Fixed potential use after free in memblock_isolate_range() (bsc#1220872).\n- CVE-2023-52582: Fixed possible oops in netfs (bsc#1220878).\n- CVE-2023-52583: Fixed deadlock or deadcode of misusing dget() inside ceph (bsc#1221058).\n- CVE-2023-52587: Fixed mcast list locking in IB/ipoib (bsc#1221082).\n- CVE-2023-52591: Fixed a possible reiserfs filesystem corruption via directory renaming (bsc#1221044).\n- CVE-2023-52594: Fixed potential array-index-out-of-bounds read in ath9k_htc_txstatus() (bsc#1221045).\n- CVE-2023-52595: Fixed possible deadlock in wifi/rt2x00 (bsc#1221046).\n- CVE-2023-52597: Fixed a setting of fpc register in KVM (bsc#1221040).\n- CVE-2023-52598: Fixed wrong setting of fpc register in s390/ptrace (bsc#1221060).\n- CVE-2023-52599: Fixed array-index-out-of-bounds in diNewExt() in jfs (bsc#1221062).\n- CVE-2023-52600: Fixed uaf in jfs_evict_inode() (bsc#1221071).\n- CVE-2023-52601: Fixed array-index-out-of-bounds in dbAdjTree() in jfs (bsc#1221068).\n- CVE-2023-52602: Fixed slab-out-of-bounds Read in dtSearch() in jfs (bsc#1221070).\n- CVE-2023-52603: Fixed array-index-out-of-bounds in dtSplitRoot() (bsc#1221066).\n- CVE-2023-52604: Fixed array-index-out-of-bounds in dbAdjTree() (bsc#1221067).\n- CVE-2023-52605: Fixed a NULL pointer dereference check (bsc#1221039)\n- CVE-2023-52606: Fixed possible kernel stack corruption in powerpc/lib (bsc#1221069).\n- CVE-2023-52607: Fixed a null-pointer-dereference in pgtable_cache_add kasprintf() (bsc#1221061).\n- CVE-2023-52608: Fixed possible race condition in firmware/arm_scmi (bsc#1221375).\n- CVE-2023-52612: Fixed req-\u003edst buffer overflow in crypto/scomp (bsc#1221616).\n- CVE-2023-52615: Fixed page fault dead lock on mmap-ed hwrng (bsc#1221614).\n- CVE-2023-52617: Fixed stdev_release() crash after surprise hot remove (bsc#1221613).\n- CVE-2023-52619: Fixed possible crash when setting number of cpus to an odd number in pstore/ram (bsc#1221618).\n- CVE-2023-52621: Fixed missing asserion in bpf (bsc#1222073).\n- CVE-2023-52623: Fixed suspicious RCU usage in SUNRPC (bsc#1222060).\n- CVE-2023-52627: Fixed null pointer dereference due to lack of callback functions in iio adc ad7091r (bsc#1222051)\n- CVE-2023-52628: Fixed 4-byte stack OOB write in nftables (bsc#1222117).\n- CVE-2023-52632: Fixed lock dependency warning with srcu in drm/amdkfd (bsc#1222274).\n- CVE-2023-52636: Fixed denial of service due to wrongly init the cursor when preparing sparse read in msgr2 in libceph  (bsc#1222247).\n- CVE-2023-52637: Fixed UAF in j1939_sk_match_filter() in can/k1939 (bsc#1222291).\n- CVE-2023-52639: Fixed race during shadow creation in KVM/s390/vsie Fixed (bsc#1222300).\n- CVE-2023-6356: Fixed a NULL pointer dereference in nvmet_tcp_build_pdu_iovec (bsc#1217987).\n- CVE-2023-6535: Fixed a NULL pointer dereference in nvmet_tcp_execute_request (bsc#1217988).\n- CVE-2023-6536: Fixed a NULL pointer dereference in __nvmet_req_complete (bsc#1217989).\n- CVE-2023-7042: Fixed a null-pointer-dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() (bsc#1218336).\n- CVE-2023-7192: Fixed a memory leak problem in ctnetlink_create_conntrack in net/netfilter/nf_conntrack_netlink.c (bsc#1218479).\n- CVE-2024-0841: Fixed null pointer dereference in hugetlbfs_fill_super() (bsc#1219264).\n- CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).\n- CVE-2024-22099: Fixed a null-pointer-dereference in rfcomm_check_security (bsc#1219170).\n- CVE-2024-23307: Fixed Integer Overflow or Wraparound vulnerability in x86 and ARM md, raid, raid5 modules (bsc#1219169).\n- CVE-2024-23850: Fixed denial of service due to assertion failure due to subvolume readed before root item insertion in btrfs_get_root_ref in btrfs (bsc#1219126).\n- CVE-2024-23850: Fixed double free of anonymous device after snapshot  creation failure (bsc#1219126).\n- CVE-2024-25739: Fixed possible crash in create_empty_lvol() in drivers/mtd/ubi/vtbl.c (bsc#1219834).\n- CVE-2024-25742: Fixed insufficient validation during #VC instruction emulation in x86/sev (bsc#1221725).\n- CVE-2024-26599: Fixed out-of-bounds access in of_pwm_single_xlate() (bsc#1220365).\n- CVE-2024-26600: Fixed NULL pointer dereference for SRP in phy-omap-usb2 (bsc#1220340).\n- CVE-2024-26602: Fixed overall slowdowns with sys_membarrier (bsc1220398).\n- CVE-2024-26612: Fixed Oops in fscache_put_cache() This function dereferences  (bsc#1221291).\n- CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).\n- CVE-2024-26620: Fixed possible device model violation in s390/vfio-ap (bsc#1221298).\n- CVE-2024-26627: Fixed possible hard lockup in scsi (bsc#1221090).\n- CVE-2024-26629: Fixed possible protocol violation via RELEASE_LOCKOWNER in nfsd (bsc#1221379).\n- CVE-2024-26642: Fixed the set of anonymous timeout flag in netfilter nf_tables (bsc#1221830).\n- CVE-2024-26645: Fixed missing visibility when inserting an element into tracing_map (bsc#1222056).\n- CVE-2024-26646: Fixed potential memory corruption when resuming from suspend or hibernation in thermal/intel/hfi (bsc#1222070).\n- CVE-2024-26651: Fixed possible oops via malicious devices in sr9800 (bsc#1221337).\n- CVE-2024-26654: Fixed use after free in ALSA/sh/aica (bsc#1222304).\n- CVE-2024-26659: Fixed wrong handling of isoc Babble and Buffer Overrun events in xhci (bsc#1222317).\n- CVE-2024-26660: Fixed buffer overflow in dcn301_stream_encoder_create in drm amd display (bsc#1222266)\n- CVE-2024-26664: Fixed out-of-bounds memory access in create_core_data() in hwmon coretemp (bsc#1222355).\n- CVE-2024-26667: Fixed null pointer reference in dpu_encoder_helper_phys_cleanup in drm/msm/dpu (bsc#1222331).\n- CVE-2024-26670: Fixed ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround in kernel arm64 (bsc#1222356).\n- CVE-2024-26680: Fixed denial of service due to DMA mapping for PTP hwts ring in net atlantic (bsc#1222427).\n- CVE-2024-26681: Fixed denial of service in nsim_dev_trap_report_work() in netdevsim (bsc#1222431).\n- CVE-2024-26684: Fixed handling of DPP safety error for DMA channels in net stmmac xgmac (bsc#1222445).\n- CVE-2024-26685: Fixed denial of service in end_buffer_async_write() in nilfs2 (bsc#1222437).\n- CVE-2024-26689: Fixed use-after-free in encode_cap_msg() in ceph (bsc#1222503).\n- CVE-2024-26695: Fixed null pointer dereference in __sev_platform_shutdown_locked in crypto ccp (bsc#1222373).\n- CVE-2024-26696: Fixed denial of service in nilfs_lookup_dirty_data_buffers() in nilfs2 (bsc#1222549).\n- CVE-2024-26697: Fixed data corruption in dsync block recovery for small block sizes in nilfs2 (bsc#1222550).\n- CVE-2024-26704: Fixed a double-free of blocks due to wrong extents moved_len in ext4 (bsc#1222422).\n- CVE-2024-26717: Fixed null pointer dereference on failed power up in HID i2c-hid-of (bsc#1222360).\n- CVE-2024-26718: Fixed memory corruption in tasklet_unlock via disabling tasklets in dm-crypt and dm-verify (bsc#1222416).\n- CVE-2024-26722: Fixed denial of service in rt5645_jack_detect_work() due to mutex left locked forever in ASoC rt5645 (bsc#1222520).\n- CVE-2024-26727: Fixed denial of service due to assertion failure during subvolume creation (bsc#1222536).\n- CVE-2024-26733: Fixed an overflow in arp_req_get() in arp (bsc#1222585).\n- CVE-2024-26736: Fixed buffer overflow in afs_update_volume_status() in afs (bsc#1222586).\n- CVE-2024-26737: Fixed use-after-free due to race between bpf_timer_cancel_and_free and bpf_timer_cancel in bpf (bsc#1222557).\n- CVE-2024-26743: Fixed memory leak in qedr_create_user_qp error flow in rdma/qedr (bsc#1222677)\n- CVE-2024-26744: Fixed null pointer dereference in srpt_service_guid parameter in rdma/srpt (bsc#1222449)\n- CVE-2024-26745: Fixed null pointer dereference due to IOMMU table not initialized for kdump over SR-IOV (bsc#1220492, bsc#1222678).\n- CVE-2024-26747: Fixed null pointer issue when put module's reference in usb roles  (bsc#1222609).\n- CVE-2024-26749: Fixed use-after-free at cdns3_gadget_ep_disable() in usb cdns3 (bsc#1222680).\n- CVE-2024-26751: Fixed denial of service due to gpiod_lookup_table search loop not ending correctly (bsc#1222724)\n- CVE-2024-26754: Fixed an use-after-free and null-ptr-deref in gtp_genl_dump_pdp() in gtp  (bsc#1222632).\n- CVE-2024-26760: Fixed null pointer dereference on error case in bio_put() in scsi target pscsi (bsc#1222596)\n- CVE-2024-26763: Fixed user corruption via by writing data with O_DIRECT on device in dm-crypt (bsc#1222720).\n- CVE-2024-26766: Fixed off-by-one error in sdma.h tx-\u003enum_descs in ib/hfi1 (bsc#1222726)\n- CVE-2024-26769: Fixed deadlock on delete association path in nvmet-fc  (bsc#1222727).\n- CVE-2024-26771: Fixed a null pointer dereference on edma_probe in dmaengine ti edma  (bsc#1222610)\n- CVE-2024-26776: Fixed null pointer dereference due to null value returned by interrupt handler in spi hisi-sfc-v3xx (bsc#1222764)\n- CVE-2024-26779: Fixed denial of service due to race condition on enabling fast-xmit in wifi mac80211  (bsc#1222772).\n- CVE-2024-26787: Fixed DMA API overlapping mappings in mmc mmci stm32 (bsc#1222781)\n- CVE-2024-26790: Fixed denial of service on 16 bytes unaligned read in dmaengine fsl-qdma (bsc#1222784)\n- CVE-2024-26793: Fixed an use-after-free and null-ptr-deref in gtp_newlink() in gtp  (bsc#1222428).\n- CVE-2024-26798: Fixed denial of service due to wrongly restore fond data upon failure in fbcon (bsc#1222798).\n- CVE-2024-26805: Fixed a kernel-infoleak-after-free in __skb_datagram_iter in netlink  (bsc#1222630).\n- CVE-2024-26807: Fixed memory corruption due to wrong pointer reference in spi cadence-qspi (bsc#1222801)\n- CVE-2024-26848: Fixed denial of service due to endless loop in directory parsing in afs (bsc#1223030).\n\nThe following non-security bugs were fixed:\n\n- Revert 'PCI: tegra194: Enable support for 256 Byte payload' (git-fixes).\n- Revert 'Revert 'drm/amdgpu/display: change pipe policy for DCN 2.0'' (git-fixes).\n- Revert 'SUNRPC dont update timeout value on connection reset' (git-fixes).\n- Revert 'drm/amd: Disable PSR-SU on Parade 0803 TCON' (git-fixes).\n- Revert 'drm/amd: Disable S/G for APUs when 64GB or more host memory' (git-fixes).\n- Revert 'drm/amdgpu/display: change pipe policy for DCN 2.0' (git-fixes).\n- Revert 'drm/amdgpu/display: change pipe policy for DCN 2.1' (git-fixes).\n- Revert 'drm/vc4: hdmi: Enforce the minimum rate at runtime_resume' (git-fixes).\n- Revert 'fbdev: flush deferred IO before closing (git-fixes).' (bsc#1221814)\n- acpi: CPPC: enable AMD CPPC V2 support for family 17h processors (git-fixes).\n- acpi: processor_idle: Fix memory leak in acpi_processor_power_exit() (git-fixes).\n- acpi: resource: Add Infinity laptops to irq1_edge_low_force_override (stable-fixes).\n- acpi: resource: Add MAIBENBEN X577 to irq1_edge_low_force_override (git-fixes).\n- acpi: resource: Do IRQ override on Lunnen Ground laptops (stable-fixes).\n- acpi: scan: Fix device check notification handling (git-fixes).\n- acpica: debugger: check status of acpi_evaluate_object() in acpi_db_walk_for_fields() (git-fixes).\n- alsa: aaci: Delete unused variable in aaci_do_suspend (git-fixes).\n- alsa: aoa: avoid false-positive format truncation warning (git-fixes).\n- alsa: aw2: avoid casting function pointers (git-fixes).\n- alsa: ctxfi: avoid casting function pointers (git-fixes).\n- alsa: hda/realtek - ALC285 reduce pop noise from Headphone port (stable-fixes).\n- alsa: hda/realtek - Add Headset Mic supported Acer NB platform (stable-fixes).\n- alsa: hda/realtek - Fix headset Mic no show at resume back for Lenovo ALC897 platform (git-fixes).\n- alsa: hda/realtek: Enable Mute LED on HP 840 G8 (MB 8AB8) (git-fixes).\n- alsa: hda/realtek: Update Panasonic CF-SZ6 quirk to support headset with microphone (git-fixes).\n- alsa: hda/realtek: fix ALC285 issues on HP Envy x360 laptops (stable-fixes).\n- alsa: hda/realtek: fix mute/micmute LED For HP mt440 (git-fixes).\n- alsa: hda/realtek: fix mute/micmute LEDs for HP EliteBook (stable-fixes).\n- alsa: seq: fix function cast warnings (git-fixes).\n- alsa: sh: aica: reorder cleanup operations to avoid UAF bugs (git-fixes).\n- alsa: usb-audio: Stop parsing channels bits when all channels are found (git-fixes).\n- arm64: dts: allwinner: h6: Add RX DMA channel for SPDIF (git-fixes)\n- arm64: dts: broadcom: bcmbca: bcm4908: drop invalid switch cells (git-fixes)\n- arm64: dts: imx8mm-kontron: Add support for ultra high speed modes on (git-fixes)\n- arm64: dts: imx8mm-venice-gw71xx: fix USB OTG VBUS (git-fixes)\n- arm64: dts: marvell: reorder crypto interrupts on Armada SoCs (git-fixes)\n- arm64: dts: rockchip: add ES8316 codec for ROCK Pi 4 (git-fixes)\n- arm64: dts: rockchip: add SPDIF node for ROCK Pi 4 (git-fixes)\n- arm64: dts: rockchip: fix regulator name on rk3399-rock-4 (git-fixes)\n- arm64: dts: rockchip: set num-cs property for spi on px30 (git-fixes)\n- arm64: mm: fix VA-range sanity check (git-fixes)\n- arm64: set __exception_irq_entry with __irq_entry as a default (git-fixes)\n- asoc: Intel: bytcr_rt5640: Add an extra entry for the Chuwi Vi8 tablet (stable-fixes).\n- asoc: amd: acp: Add missing error handling in sof-mach (git-fixes).\n- asoc: amd: acp: fix for acp_init function error handling (git-fixes).\n- asoc: madera: Fix typo in madera_set_fll_clks shift value (git-fixes).\n- asoc: meson: Use dev_err_probe() helper (stable-fixes).\n- asoc: meson: aiu: fix function pointer type mismatch (git-fixes).\n- asoc: meson: axg-tdm-interface: add frame rate constraint (git-fixes).\n- asoc: meson: axg-tdm-interface: fix mclk setup without mclk-fs (git-fixes).\n- asoc: meson: t9015: fix function pointer type mismatch (git-fixes).\n- asoc: ops: Fix wraparound for mask in snd_soc_get_volsw (git-fixes).\n- asoc: rcar: adg: correct TIMSEL setting for SSI9 (git-fixes).\n- asoc: rt5645: Make LattePanda board DMI match more precise (stable-fixes).\n- asoc: rt5682-sdw: fix locking sequence (git-fixes).\n- asoc: rt711-sdca: fix locking sequence (git-fixes).\n- asoc: rt711-sdw: fix locking sequence (git-fixes).\n- asoc: wm8962: Enable both SPKOUTR_ENA and SPKOUTL_ENA in mono mode (stable-fixes).\n- asoc: wm8962: Enable oscillator if selecting WM8962_FLL_OSC (stable-fixes).\n- asoc: wm8962: Fix up incorrect error message in wm8962_set_fll (stable-fixes).\n- ata: sata_mv: Fix PCI device ID table declaration compilation warning (git-fixes).\n- ata: sata_sx4: fix pdc20621_get_from_dimm() on 64-bit (git-fixes).\n- backlight: da9052: Fully initialize backlight_properties during probe (git-fixes).\n- backlight: lm3630a: Do not set bl-\u003eprops.brightness in get_brightness (git-fixes).\n- backlight: lm3630a: Initialize backlight_properties on init (git-fixes).\n- backlight: lm3639: Fully initialize backlight_properties during probe (git-fixes).\n- backlight: lp8788: Fully initialize backlight_properties during probe (git-fixes).\n- bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent (git-fixes).\n- bcache: Remove dead references to cache_readaheads (git-fixes).\n- bcache: Remove unnecessary NULL point check in node allocations (git-fixes).\n- bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() (git-fixes).\n- bcache: avoid NULL checking to c-\u003eroot in run_cache_set() (git-fixes).\n- bcache: avoid oversize memory allocation by small stripe_size (git-fixes).\n- bcache: bset: Fix comment typos (git-fixes).\n- bcache: check return value from btree_node_alloc_replacement() (git-fixes).\n- bcache: fix NULL pointer reference in cached_dev_detach_finish (git-fixes).\n- bcache: fix error info in register_bcache() (git-fixes).\n- bcache: fixup bcache_dev_sectors_dirty_add() multithreaded CPU false sharing (git-fixes).\n- bcache: fixup btree_cache_wait list damage (git-fixes).\n- bcache: fixup init dirty data errors (git-fixes).\n- bcache: fixup lock c-\u003eroot error (git-fixes).\n- bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race (git-fixes).\n- bcache: move calc_cached_dev_sectors to proper place on backing device detach (git-fixes).\n- bcache: move uapi header bcache.h to bcache code directory (git-fixes).\n- bcache: prevent potential division by zero error (git-fixes).\n- bcache: remove EXPERIMENTAL for Kconfig option 'Asynchronous device registration' (git-fixes).\n- bcache: remove bch_crc64_update (git-fixes).\n- bcache: remove redundant assignment to variable cur_idx (git-fixes).\n- bcache: remove the backing_dev_name field from struct cached_dev (git-fixes).\n- bcache: remove the cache_dev_name field from struct cache (git-fixes).\n- bcache: remove unnecessary flush_workqueue (git-fixes).\n- bcache: remove unused bch_mark_cache_readahead function def in stats.h (git-fixes).\n- bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce() (git-fixes).\n- bcache: replace snprintf in show functions with sysfs_emit (git-fixes).\n- bcache: revert replacing IS_ERR_OR_NULL with IS_ERR (git-fixes).\n- bcache: use bvec_kmap_local in bch_data_verify (git-fixes).\n- bcache: use bvec_kmap_local in bio_csum (git-fixes).\n- bcache: use default_groups in kobj_type (git-fixes).\n- bcache:: fix repeated words in comments (git-fixes).\n- blocklayoutdriver: Fix reference leak of pnfs_device_node (git-fixes).\n- bluetooth: hci_core: Fix possible buffer overflow (git-fixes).\n- bluetooth: mgmt: Remove leftover queuing of power_off work (git-fixes).\n- bluetooth: remove HCI_POWER_OFF_TIMEOUT (git-fixes).\n- bluetooth: remove superfluous call to hci_conn_check_pending() (git-fixes).\n- bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security (stable-fixes).\n- bpf, scripts: Correct GPL license name (git-fixes).\n- bpf, sockmap: Fix preempt_rt splat when using raw_spin_lock_t (git-fixes).\n- can: softing: remove redundant NULL check (git-fixes).\n- ceph: stop copying to iter at EOF on sync reads (bsc#1223068).\n- ceph: switch to corrected encoding of max_xattr_size in mdsmap (bsc#1223067).\n- clk: zynq: Prevent null pointer dereference caused by kmalloc failure (git-fixes).\n- comedi: comedi_test: Prevent timers rescheduling during deletion (git-fixes).\n- coresight: etm4x: Do not access TRCIDR1 for identification (bsc#1220775)\n- coresight: etm4x: Fix accesses to TRCSEQRSTEVR and TRCSEQSTR (bsc#1220775)\n- coresight: etm: Override TRCIDR3.CCITMIN on errata affected cpus (bsc#1220775)\n- cpufreq: amd-pstate: Fix min_perf assignment in amd_pstate_adjust_perf() (git-fixes).\n- cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value (git-fixes).\n- crypto: arm/sha - fix function cast warnings (git-fixes).\n- crypto: qat - avoid division by zero (git-fixes).\n- crypto: qat - fix deadlock in backlog processing (git-fixes).\n- crypto: qat - fix double free during reset (git-fixes).\n- crypto: qat - fix state machines cleanup paths (bsc#1218321).\n- crypto: qat - fix unregistration of compression algorithms (git-fixes).\n- crypto: qat - fix unregistration of crypto algorithms (git-fixes).\n- crypto: qat - ignore subsequent state up commands (git-fixes).\n- crypto: qat - increase size of buffers (git-fixes).\n- crypto: qat - resolve race condition during AER recovery (git-fixes).\n- crypto: xilinx - call finalize with bh disabled (git-fixes).\n- dm cache policy smq: ensure IO does not prevent cleaner policy progress (git-fixes).\n- dm cache: add cond_resched() to various workqueue loops (git-fixes).\n- dm clone: call kmem_cache_destroy() in dm_clone_init() error path (git-fixes).\n- dm crypt: add cond_resched() to dmcrypt_write() (git-fixes).\n- dm crypt: avoid accessing uninitialized tasklet (git-fixes).\n- dm flakey: do not corrupt the zero page (git-fixes).\n- dm flakey: fix a bug with 32-bit highmem systems (git-fixes).\n- dm flakey: fix a crash with invalid table line (git-fixes).\n- dm flakey: fix logic when corrupting a bio (git-fixes).\n- dm init: add dm-mod.waitfor to wait for asynchronously probed block devices (git-fixes).\n- dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path (git-fixes).\n- dm integrity: fix out-of-range warning (git-fixes).\n- dm integrity: reduce vmalloc space footprint on 32-bit architectures (git-fixes).\n- dm raid: clean up four equivalent goto tags in raid_ctr() (git-fixes).\n- dm raid: fix false positive for requeue needed during reshape (git-fixes).\n- dm raid: fix missing reconfig_mutex unlock in raid_ctr() error paths (git-fixes).\n- dm stats: check for and propagate alloc_percpu failure (git-fixes).\n- dm thin metadata: Fix ABBA deadlock by resetting dm_bufio_client (git-fixes).\n- dm thin metadata: check fail_io before using data_sm (git-fixes).\n- dm thin: add cond_resched() to various workqueue loops (git-fixes).\n- dm thin: fix deadlock when swapping to thin device (bsc#1177529).\n- dm verity: do not perform FEC for failed readahead IO (git-fixes).\n- dm verity: fix error handling for check_at_most_once on FEC (git-fixes).\n- dm zoned: free dmz-\u003eddev array in dmz_put_zoned_devices (git-fixes).\n- dm-delay: fix a race between delay_presuspend and delay_bio (git-fixes).\n- dm-integrity: do not modify bio's immutable bio_vec in integrity_metadata() (git-fixes).\n- dm-raid: fix lockdep waring in 'pers-\u003ehot_add_disk' (git-fixes).\n- dm-verity, dm-crypt: align 'struct bvec_iter' correctly (git-fixes).\n- dm-verity: align struct dm_verity_fec_io properly (git-fixes).\n- dm: add cond_resched() to dm_wq_work() (git-fixes).\n- dm: call the resume method on internal suspend (git-fixes).\n- dm: do not lock fs when the map is NULL during suspend or resume (git-fixes).\n- dm: do not lock fs when the map is NULL in process of resume (git-fixes).\n- dm: remove flush_scheduled_work() during local_exit() (git-fixes).\n- dm: send just one event on resize, not two (git-fixes).\n- doc-guide: kernel-doc: tell about object-like macros (git-fixes).\n- doc/README.SUSE: Update information about module support status (jsc#PED-5759)\n- drivers: hv: vmbus: Calculate ring buffer size for more efficient use of memory (git-fixes).\n- drm/amd/display: Add FAMS validation before trying to use it (git-fixes).\n- drm/amd/display: Add function for validate and update new stream (git-fixes).\n- drm/amd/display: Avoid ABM when ODM combine is enabled for eDP (git-fixes).\n- drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN31 (git-fixes).\n- drm/amd/display: Check if link state is valid (git-fixes).\n- drm/amd/display: Copy DC context in the commit streams (git-fixes).\n- drm/amd/display: Disable PSR-SU on Parade 0803 TCON again (git-fixes).\n- drm/amd/display: Enable fast plane updates on DCN3.2 and above (git-fixes).\n- drm/amd/display: Enable new commit sequence only for DCN32x (git-fixes).\n- drm/amd/display: Exit idle optimizations before attempt to access PHY (git-fixes).\n- drm/amd/display: Expand kernel doc for DC (git-fixes).\n- drm/amd/display: Fix a bug when searching for insert_above_mpcc (git-fixes).\n- drm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()' (git-fixes).\n- drm/amd/display: Fix possible underflow for displays with large vblank (git-fixes).\n- drm/amd/display: Fix the delta clamping for shaper LUT (git-fixes).\n- drm/amd/display: Fix underflow issue on 175hz timing (git-fixes).\n- drm/amd/display: For prefetch mode \u003e 0, extend prefetch if possible (git-fixes).\n- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family (git-fixes).\n- drm/amd/display: Guard against invalid RPTR/WPTR being set (git-fixes).\n- drm/amd/display: Handle seamless boot stream (git-fixes).\n- drm/amd/display: Handle virtual hardware detect (git-fixes).\n- drm/amd/display: Include surface of unaffected streams (git-fixes).\n- drm/amd/display: Include udelay when waiting for INBOX0 ACK (git-fixes).\n- drm/amd/display: Increase frame warning limit with KASAN or KCSAN in dml (git-fixes).\n- drm/amd/display: Keep PHY active for dp config (git-fixes).\n- drm/amd/display: Prevent vtotal from being set to 0 (git-fixes).\n- drm/amd/display: Remove min_dst_y_next_start check for Z8 (git-fixes).\n- drm/amd/display: Restore rptr/wptr for DMCUB as workaround (git-fixes).\n- drm/amd/display: Return the correct HDCP error code (stable-fixes).\n- drm/amd/display: Revert vblank change that causes null pointer crash (git-fixes).\n- drm/amd/display: Rework comments on dc file (git-fixes).\n- drm/amd/display: Rework context change check (git-fixes).\n- drm/amd/display: Set minimum requirement for using PSR-SU on Phoenix (git-fixes).\n- drm/amd/display: Set minimum requirement for using PSR-SU on Rembrandt (git-fixes).\n- drm/amd/display: Update OTG instance in the commit stream (git-fixes).\n- drm/amd/display: Update correct DCN314 register header (git-fixes).\n- drm/amd/display: Update min Z8 residency time to 2100 for DCN314 (git-fixes).\n- drm/amd/display: Use DRAM speed from validation for dummy p-state (git-fixes).\n- drm/amd/display: Use DTBCLK as refclk instead of DPREFCLK (git-fixes).\n- drm/amd/display: Use min transition for all SubVP plane add/remove (git-fixes).\n- drm/amd/display: Write to correct dirty_rect (git-fixes).\n- drm/amd/display: Wrong colorimetry workaround (git-fixes).\n- drm/amd/display: add FB_DAMAGE_CLIPS support (git-fixes).\n- drm/amd/display: add ODM case when looking for first split pipe (git-fixes).\n- drm/amd/display: always switch off ODM before committing more streams (git-fixes).\n- drm/amd/display: clean code-style issues in dcn30_set_mpc_shaper_3dlut (git-fixes).\n- drm/amd/display: dc.h: eliminate kernel-doc warnings (git-fixes).\n- drm/amd/display: ensure async flips are only accepted for fast updates (git-fixes).\n- drm/amd/display: fix ABM disablement (git-fixes).\n- drm/amd/display: fix a NULL pointer dereference in amdgpu_dm_i2c_xfer() (git-fixes).\n- drm/amd/display: fix dc/core/dc.c kernel-doc (git-fixes).\n- drm/amd/display: fix hw rotated modes when PSR-SU is enabled (git-fixes).\n- drm/amd/display: fix kernel-doc issues in dc.h (git-fixes).\n- drm/amd/display: fix unbounded requesting for high pixel rate modes on dcn315 (git-fixes).\n- drm/amd/display: handle range offsets in VRR ranges (stable-fixes).\n- drm/amd/display: perform a bounds check before filling dirty rectangles (git-fixes).\n- drm/amd/display: set per pipe dppclk to 0 when dpp is off (git-fixes).\n- drm/amd/display: update extended blank for dcn314 onwards (git-fixes).\n- drm/amd/display: use low clocks for no plane configs (git-fixes).\n- drm/amd/pm: Fix error of MACO flag setting code (git-fixes).\n- drm/amd/pm: fix a memleak in aldebaran_tables_init (git-fixes).\n- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr Clock (git-fixes).\n- drm/amd: Enable PCIe PME from D3 (git-fixes).\n- drm/amdgpu/pm: Fix the error of pwm1_enable setting (stable-fixes).\n- drm/amdgpu/pm: make gfxclock consistent for sienna cichlid (git-fixes).\n- drm/amdgpu/pm: make mclk consistent for smu 13.0.7 (git-fixes).\n- drm/amdgpu/smu13: drop compute workload workaround (git-fixes).\n- drm/amdgpu: Enable gpu reset for S3 abort cases on Raven series (stable-fixes).\n- drm/amdgpu: Fix missing break in ATOM_ARG_IMM Case of atom_get_src_int() (git-fixes).\n- drm/amdgpu: Force order between a read and write to the same address (git-fixes).\n- drm/amdgpu: Match against exact bootloader status (git-fixes).\n- drm/amdgpu: Unset context priority is now invalid (git-fixes).\n- drm/amdgpu: Update min() to min_t() in 'amdgpu_info_ioctl' (git-fixes).\n- drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag (stable-fixes).\n- drm/amdgpu: lower CS errors to debug severity (git-fixes).\n- drm/amdkfd: fix TLB flush after unmap for GFX9.4.2 (stable-fixes).\n- drm/bridge: tc358762: Instruct DSI host to generate HSE packets (git-fixes).\n- drm/display: fix typo (git-fixes).\n- drm/edid: Add quirk for OSVR HDK 2.0 (git-fixes).\n- drm/etnaviv: Restore some id values (git-fixes).\n- drm/exynos: do not return negative values from .get_modes() (stable-fixes).\n- drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable() (git-fixes).\n- drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode() (stable-fixes).\n- drm/i915/gt: Do not generate the command streamer for all the CCS (git-fixes).\n- drm/i915/gt: Reset queue_priority_hint on parking (git-fixes).\n- drm/i915/gt: Use i915_vm_put on ppgtt_create error paths (git-fixes).\n- drm/i915/selftests: Fix dependency of some timeouts on HZ (git-fixes).\n- drm/i915: Add missing CCS documentation (git-fixes).\n- drm/i915: Call intel_pre_plane_updates() also for pipes getting enabled (git-fixes).\n- drm/i915: Check before removing mm notifier (git-fixes).\n- drm/lima: fix a memleak in lima_heap_alloc (git-fixes).\n- drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip (git-fixes).\n- drm/mediatek: dsi: Fix DSI RGB666 formats and definitions (git-fixes).\n- drm/msm/dpu: Only enable DSC_MODE_MULTIPLEX if dsc_merge is enabled (git-fixes).\n- drm/msm/dpu: add division of drm_display_mode's hskew parameter (git-fixes).\n- drm/msm/dpu: fix the programming of INTF_CFG2_DATA_HCTL_EN (git-fixes).\n- drm/msm/dpu: improve DSC allocation (git-fixes).\n- drm/panel-edp: use put_sync in unprepare (git-fixes).\n- drm/panel: Move AUX B116XW03 out of panel-edp back to panel-simple (git-fixes).\n- drm/panel: auo,b101uan08.3: Fine tune the panel power sequence (git-fixes).\n- drm/panel: boe-tv101wum-nl6: Fine tune the panel power sequence (git-fixes).\n- drm/panel: do not return negative error codes from drm_panel_get_modes() (stable-fixes).\n- drm/panfrost: fix power transition timeout warnings (git-fixes).\n- drm/probe-helper: warn about negative .get_modes() (stable-fixes).\n- drm/qxl: remove unused `count` variable from `qxl_surface_id_alloc()` (git-fixes).\n- drm/qxl: remove unused variable from `qxl_process_single_command()` (git-fixes).\n- drm/radeon/ni: Fix wrong firmware size logging in ni_init_microcode() (git-fixes).\n- drm/radeon/ni_dpm: remove redundant NULL check (git-fixes).\n- drm/radeon: remove dead code in ni_mc_load_microcode() (git-fixes).\n- drm/rockchip: dsi: Clean up 'usage_mode' when failing to attach (git-fixes).\n- drm/rockchip: inno_hdmi: Fix video timing (git-fixes).\n- drm/rockchip: lvds: do not overwrite error code (git-fixes).\n- drm/rockchip: lvds: do not print scary message when probing defer (git-fixes).\n- drm/tegra: dpaux: Fix PM disable depth imbalance in tegra_dpaux_probe (git-fixes).\n- drm/tegra: dsi: Add missing check for of_find_device_by_node (git-fixes).\n- drm/tegra: dsi: Fix missing pm_runtime_disable() in the error handling path of tegra_dsi_probe() (git-fixes).\n- drm/tegra: dsi: Fix some error handling paths in tegra_dsi_probe() (git-fixes).\n- drm/tegra: dsi: Make use of the helper function dev_err_probe() (stable-fixes).\n- drm/tegra: hdmi: Convert to devm_platform_ioremap_resource() (stable-fixes).\n- drm/tegra: hdmi: Fix some error handling paths in tegra_hdmi_probe() (git-fixes).\n- drm/tegra: output: Fix missing i2c_put_adapter() in the error handling paths of tegra_output_probe() (git-fixes).\n- drm/tegra: put drm_gem_object ref on error in tegra_fb_create (git-fixes).\n- drm/tegra: rgb: Fix missing clk_put() in the error handling paths of tegra_dc_rgb_probe() (git-fixes).\n- drm/tegra: rgb: Fix some error handling paths in tegra_dc_rgb_probe() (git-fixes).\n- drm/tidss: Fix initial plane zpos values (git-fixes).\n- drm/tidss: Fix sync-lost issue with two displays (git-fixes).\n- drm/ttm: Do not leak a resource on eviction error (git-fixes).\n- drm/ttm: Do not print error message if eviction was interrupted (git-fixes).\n- drm/vc4: Add module dependency on hdmi-codec (git-fixes).\n- drm/vmwgfx: Create debugfs ttm_resource_manager entry only if needed (git-fixes).\n- drm/vmwgfx: Fix possible null pointer derefence with invalid contexts (git-fixes).\n- drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node (git-fixes).\n- drm: Do not treat 0 as -1 in drm_fixp2int_ceil (git-fixes).\n- drm: Fix drm_fixp2int_round() making it add 0.5 (git-fixes).\n- drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017) (git-fixes).\n- firewire: core: use long bus reset on gap count error (stable-fixes).\n- fix 'coresight: etm4x: Change etm4_platform_driver driver for MMIO devices' (bsc#1220775) Hunk with clk_put(drvdata-\u003epclk) was incorrectly moved to another function.\n- force config_TCG_TIS_CORE=m on aarch64 for workaround kconfig issues\n- group-source-files.pl: Quote filenames (boo#1221077). The kernel source now contains a file with a space in the name. Add quotes in group-source-files.pl to avoid splitting the filename. Also use -print0 / -0 when updating timestamps.\n- hid: amd_sfh: Update HPD sensor structure elements (git-fixes).\n- hid: lenovo: Add middleclick_workaround sysfs knob for cptkbd (git-fixes).\n- hid: multitouch: Add required quirk for Synaptics 0xcddc device (stable-fixes).\n- hv_netvsc: Calculate correct ring size when PAGE_SIZE is not 4 Kbytes (git-fixes).\n- hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove (git-fixes).\n- hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed (git-fixes).\n- i2c: aspeed: Fix the dummy irq expected print (git-fixes).\n- i2c: i801: Avoid potential double call to gpiod_remove_lookup_table (git-fixes).\n- i2c: wmt: Fix an error handling path in wmt_i2c_probe() (git-fixes).\n- ib/ipoib: fix mcast list locking (git-fixes)\n- iio: dummy_evgen: remove Excess kernel-doc comments (git-fixes).\n- iio: pressure: dlhl60d: Initialize empty DLH bytes (git-fixes).\n- input: gpio_keys_polled - suppress deferred probe error for gpio (stable-fixes).\n- input: synaptics-rmi4 - fix UAF of IRQ domain on driver removal (git-fixes).\n- iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter (git-fixes).\n- iommu/amd: Do not block updates to GATag if guest mode is on (git-fixes).\n- iommu/amd: Fix 'Guest Virtual APIC Table Root Pointer' configuration in IRTE (git-fixes).\n- iommu/amd: Fix domain flush size when syncing iotlb (git-fixes).\n- iommu/amd: Fix error handling for pdev_pri_ats_enable() (git-fixes).\n- iommu/amd: Mark interrupt as managed (git-fixes).\n- iommu/arm-smmu-qcom: Limit the SMR groups to 128 (git-fixes).\n- iommu/arm-smmu-v3: Acknowledge pri/event queue overflow if any (git-fixes).\n- iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982 (git-fixes).\n- iommu/dma: Trace bounce buffer usage when mapping buffers (git-fixes).\n- iommu/fsl: fix all kernel-doc warnings in fsl_pamu.c (git-fixes).\n- iommu/iova: Fix alloc iova overflows issue (git-fixes).\n- iommu/mediatek-v1: Fix an error handling path in mtk_iommu_v1_probe() (git-fixes).\n- iommu/mediatek: Fix forever loop in error handling (git-fixes).\n- iommu/mediatek: Flush IOTLB completely only if domain has been attached (git-fixes).\n- iommu/rockchip: Fix unwind goto issue (git-fixes).\n- iommu/sprd: Release dma buffer to avoid memory leak (git-fixes).\n- iommu/vt-d: Allocate local memory for page request queue (git-fixes).\n- iommu/vt-d: Allow to use flush-queue when first level is default (git-fixes).\n- iommu/vt-d: Allow zero SAGAW if second-stage not supported (git-fixes).\n- iommu/vt-d: Do not issue ATS Invalidation request when device is disconnected (git-fixes).\n- iommu/vt-d: Fix PASID directory pointer coherency (git-fixes).\n- iommu/vt-d: Fix error handling in sva enable/disable paths (git-fixes).\n- iommu/vt-d: Set No Execute Enable bit in PASID table entry (git-fixes).\n- iommu: Fix error unwind in iommu_group_alloc() (git-fixes).\n- kABI: PCI: Add locking to RMW PCI Express Capability Register accessors (kabi).\n- kabi: Adjust trace_iterator.wait_index (git-fixes).\n- kconfig: fix infinite loop when expanding a macro at the end of file (git-fixes).\n- kernel-binary: Fix i386 build Fixes: 89eaf4cdce05 ('rpm templates: Move macro definitions below buildrequires')\n- kernel-binary: Move build script to the end All other spec templates have the build script at the end, only kernel-binary has it in the middle. Align with the other templates.\n- kernel-binary: certs: Avoid trailing space\n- kernel-binary: vdso: fix filelist for non-usrmerged kernel Fixes: a6ad8af207e6 ('rpm templates: Always define usrmerged')\n- kprobes: Fix double free of kretprobe_holder (bsc#1220901).\n- kvm: s390: only deliver the set service event bits (git-fixes bsc#1221631).\n- leds: aw2013: Unlock mutex before destroying it (git-fixes).\n- lib/cmdline: Fix an invalid format specifier in an assertion msg (git-fixes).\n- libnvdimm/of_pmem: Use devm_kstrdup instead of kstrdup and check its return value (git-fixes).\n- libnvdimm/region: Allow setting align attribute on regions without mappings (git-fixes).\n- make nvidia Grace-Hopper TPM related drivers build-ins (bsc#1221156)\n- md/raid1: fix choose next idle in read_balance() (git-fixes).\n- md: Do not clear MD_CLOSING when the raid is about to stop (git-fixes).\n- md: do not clear MD_RECOVERY_FROZEN for new dm-raid until resume (git-fixes).\n- md: fix data corruption for raid456 when reshape restart while grow up (git-fixes).\n- media: dvb-frontends: avoid stack overflow warnings with clang (git-fixes).\n- media: edia: dvbdev: fix a use-after-free (git-fixes).\n- media: em28xx: annotate unchecked call to media_device_register() (git-fixes).\n- media: go7007: add check of return value of go7007_read_addr() (git-fixes).\n- media: go7007: fix a memleak in go7007_load_encoder (git-fixes).\n- media: imx: csc/scaler: fix v4l2_ctrl_handler memory leak (git-fixes).\n- media: pvrusb2: fix pvr2_stream_callback casts (git-fixes).\n- media: pvrusb2: fix uaf in pvr2_context_set_notify (git-fixes).\n- media: pvrusb2: remove redundant NULL check (git-fixes).\n- media: staging: ipu3-imgu: Set fields before media_entity_pads_init() (git-fixes).\n- media: sun8i-di: Fix chroma difference threshold (git-fixes).\n- media: sun8i-di: Fix coefficient writes (git-fixes).\n- media: sun8i-di: Fix power on/off sequences (git-fixes).\n- media: tc358743: register v4l2 async device only after successful setup (git-fixes).\n- media: ttpci: fix two memleaks in budget_av_attach (git-fixes).\n- media: usbtv: Remove useless locks in usbtv_video_free() (git-fixes).\n- media: v4l2-mem2mem: fix a memleak in v4l2_m2m_register_entity (git-fixes).\n- media: v4l2-tpg: fix some memleaks in tpg_alloc (git-fixes).\n- media: xc4000: Fix atomicity violation in xc4000_get_frequency (git-fixes).\n- mfd: altera-sysmgr: Call of_node_put() only when of_parse_phandle() takes a ref (git-fixes).\n- mfd: syscon: Call of_node_put() only when of_parse_phandle() takes a ref (git-fixes).\n- mm,page_owner: Defer enablement of static branch (bsc#1222366).\n- mm,page_owner: Fix accounting of pages when migrating (bsc#1222366).\n- mm,page_owner: Fix printing of stack records (bsc#1222366).\n- mm,page_owner: Fix refcount imbalance (bsc#1222366).\n- mm,page_owner: Update metadata for tail pages (bsc#1222366).\n- mm,page_owner: check for null stack_record before bumping its refcount (bsc#1222366).\n- mm,page_owner: drop unnecessary check (bsc#1222366).\n- mm,page_owner: fix recursion (bsc#1222366).\n- mm/vmalloc: huge vmalloc backing pages should be split rather than compound (bsc#1217829).\n- mmc: core: Avoid negative index with array access (git-fixes).\n- mmc: core: Fix switch on gp3 partition (git-fixes).\n- mmc: core: Initialize mmc_blk_ioc_data (git-fixes).\n- mmc: mmci: stm32: fix DMA API overlapping mappings warning (git-fixes).\n- mmc: mmci: stm32: use a buffer for unaligned DMA requests (git-fixes).\n- mmc: tmio: avoid concurrent runs of mmc_request_done() (git-fixes).\n- mmc: wmt-sdmmc: remove an incorrect release_mem_region() call in the .remove function (git-fixes).\n- mtd: maps: physmap-core: fix flash size larger than 32-bit (git-fixes).\n- mtd: rawnand: lpc32xx_mlc: fix irq handler prototype (git-fixes).\n- mtd: rawnand: meson: fix scrambling mode value in command macro (git-fixes).\n- nd_btt: Make BTT lanes preemptible (git-fixes).\n- net/bnx2x: Prevent access to a freed page in page_pool (bsc#1215322).\n- net/x25: fix incorrect parameter validation in the x25_getsockopt() function (git-fixes).\n- net: Fix features skip in for_each_netdev_feature() (git-fixes).\n- net: lan78xx: fix runtime PM count underflow on link stop (git-fixes).\n- net: ll_temac: platform_get_resource replaced by wrong function (git-fixes).\n- net: mana: Fix Rx DMA datasize and skb_over_panic (git-fixes).\n- net: phy: fix phy_get_internal_delay accessing an empty array (git-fixes).\n- net: sunrpc: Fix an off by one in rpc_sockaddr2uaddr() (git-fixes).\n- net: usb: ax88179_178a: avoid the interface always configured as random address (git-fixes).\n- nfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet (git-fixes).\n- nfs: avoid spurious warning of lost lock that is being unlocked (bsc#1221791).\n- nfs: fix an off by one in root_nfs_cat() (git-fixes).\n- nfs: rename nfs_client_kset to nfs_kset (git-fixes).\n- nfsd: change LISTXATTRS cookie encoding to big-endian (git-fixes).\n- nfsd: convert the callback workqueue to use delayed_work (git-fixes).\n- nfsd: do not take fi_lock in nfsd_break_deleg_cb() (git-fixes).\n- nfsd: fix file memleak on client_opens_release (git-fixes).\n- nfsd: fix liSTXATTRS returning a short list with eof=TRUE (git-fixes).\n- nfsd: fix liSTXATTRS returning more bytes than maxcount (git-fixes).\n- nfsd: fix nfsd4_listxattr_validate_cookie (git-fixes).\n- nfsd: lock_rename() needs both directories to live on the same fs (git-fixes).\n- nfsd: reschedule CB operations when backchannel rpc_clnt is shut down (git-fixes).\n- nfsd: reset cb_seq_status after NFS4ERR_DELAY (git-fixes).\n- nfsd: retransmit callbacks after client reconnects (git-fixes).\n- nfsd: use vfs setgid helper (git-fixes).\n- nfsv4.1/pnfs: Ensure we handle the error NFS4ERR_RETURNCONFLICT (git-fixes).\n- nfsv4.1: fix SP4_MACH_CRED protection for pnfs IO (git-fixes).\n- nfsv4.1: fixup use EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nfsv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server (git-fixes).\n- nfsv4.2: fix listxattr maximum XDR buffer size (git-fixes).\n- nfsv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 (git-fixes).\n- nfsv4.2: fix wrong shrinker_id (git-fixes).\n- nfsv4: fix a nfs4_state_manager() race (git-fixes).\n- nfsv4: fix a state manager thread deadlock regression (git-fixes).\n- nilfs2: fix failure to detect DAT corruption in btree and direct mappings (git-fixes).\n- nilfs2: prevent kernel bug at submit_bh_wbc() (git-fixes).\n- nouveau/dmem: handle kcalloc() allocation failure (git-fixes).\n- nouveau: reset the bo resource bus info after an eviction (git-fixes).\n- ntfs: fix use-after-free in ntfs_ucsncmp() (bsc#1221713).\n- nvdimm/namespace: drop nested variable in create_namespace_pmem() (git-fixes).\n- nvdimm: Allow overwrite in the presence of disabled dimms (git-fixes).\n- nvdimm: Fix badblocks clear off-by-one error (git-fixes).\n- nvdimm: Fix dereference after free in register_nvdimm_pmu() (git-fixes).\n- nvdimm: Fix firmware activation deadlock scenarios (git-fixes).\n- nvdimm: Fix memleak of pmu attr_groups in unregister_nvdimm_pmu() (git-fixes).\n- nvme-fc: do not wait in vain when unloading module (git-fixes).\n- nvme: fix reconnection fail due to reserved tag allocation (git-fixes).\n- nvmet-fc: abort command when there is no binding (git-fixes).\n- nvmet-fc: avoid deadlock on delete association path (git-fixes).\n- nvmet-fc: defer cleanup using RCU properly (git-fixes).\n- nvmet-fc: hold reference on hostport match (git-fixes).\n- nvmet-fc: release reference on target port (git-fixes).\n- nvmet-fc: take ref count on tgtport before delete assoc (git-fixes).\n- nvmet-fcloop: swap the list_add_tail arguments (git-fixes).\n- nvmet-tcp: fix nvme tcp ida memory leak (git-fixes).\n- pNFS/flexfiles: Check the layout validity in ff_layout_mirror_prepare_stats (git-fixes).\n- pNFS: Fix a hang in nfs4_evict_inode() (git-fixes).\n- pNFS: Fix the pnfs block driver's calculation of layoutget size (git-fixes).\n- pci/aer: Block runtime suspend when handling errors (git-fixes).\n- pci/aer: fix rootport attribute paths in ABI docs (git-fixes).\n- pci/aspm: use RMW accessors for changing LNKCTL (git-fixes).\n- pci/dpc: Quirk PIO log size for Intel Ice Lake Root Ports (git-fixes).\n- pci/dpc: Quirk PIO log size for Intel Raptor Lake Root Ports (git-fixes).\n- pci/dpc: Quirk PIO log size for certain Intel Root Ports (git-fixes).\n- pci/dpc: print all TLP Prefixes, not just the first (git-fixes).\n- pci/msi: prevent MSI hardware interrupt number truncation (bsc#1218777)\n- pci/p2pdma: Fix a sleeping issue in a RCU read section (git-fixes).\n- pci/pm: Drain runtime-idle callbacks before driver removal (git-fixes).\n- pci: Drop pci_device_remove() test of pci_dev-\u003edriver (git-fixes).\n- pci: add locking to RMW PCI Express Capability Register accessors (git-fixes).\n- pci: dwc: endpoint: Fix advertised resizable BAR size (git-fixes).\n- pci: dwc: endpoint: Fix dw_pcie_ep_raise_msix_irq() alignment support (git-fixes).\n- pci: dwc: fix a 64bit bug in dw_pcie_ep_raise_msix_irq() (git-fixes).\n- pci: fu740: Set the number of MSI vectors (git-fixes).\n- pci: lengthen reset delay for VideoPropulsion Torrent QN16e card (git-fixes).\n- pci: make link retraining use RMW accessors for changing LNKCTL (git-fixes).\n- pci: mark 3ware-9650SE Root Port Extended Tags as broken (git-fixes).\n- pci: mediatek-gen3: Fix translation window size calculation (git-fixes).\n- pci: mediatek: Clear interrupt status before dispatching handler (git-fixes).\n- pci: qcom: enable BDF to SID translation properly (git-fixes).\n- pci: qcom: use DWC helpers for modifying the read-only DBI registers (git-fixes).\n- pci: rockchip: Do not advertise MSI-X in PCIe capabilities (git-fixes).\n- pci: rockchip: Fix window mapping and address translation for endpoint (git-fixes).\n- pci: rockchip: Use 64-bit mask on MSI 64-bit PCI address (git-fixes).\n- pci: switchtec: Fix an error handling path in switchtec_pci_probe() (git-fixes).\n- pci_iounmap(): Fix MMIO mapping leak (git-fixes).\n- pinctrl: mediatek: Drop bogus slew rate register range for MT8192 (git-fixes).\n- platform/mellanox: mlxreg-hotplug: Remove redundant NULL-check (git-fixes).\n- pm: suspend: Set mem_sleep_current during kernel command line setup (git-fixes).\n- powerpc/64s: POWER10 CPU Kconfig build option (bsc#1194869).\n- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment (bsc#1194869).\n- powerpc/boot: Fix boot wrapper code generation with CONFIG_POWER10_CPU (bsc#1194869).\n- powerpc/lib/sstep: Do not use __{get/put}_user() on kernel addresses (bsc#1194869).\n- powerpc/lib/sstep: Remove unneeded #ifdef __powerpc64__ (bsc#1194869).\n- powerpc/lib/sstep: Use l1_dcache_bytes() instead of opencoding (bsc#1194869).\n- powerpc/lib/sstep: use truncate_if_32bit() (bsc#1194869).\n- powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV (bsc#1220492 ltc#205270).\n- powerpc/pseries/iommu: LPAR panics when rebooted with a frozen PE (bsc#1222011 ltc#205900).\n- powerpc/pseries: Fix potential memleak in papr_get_attr() (bsc#1200465 ltc#197256 jsc#SLE-18130 git-fixes).\n- powerpc/sstep: Use bitwise instead of arithmetic operator for flags (bsc#1194869).\n- powerpc: add compile-time support for lbarx, lharx (bsc#1194869).\n- pwm: mediatek: Update kernel doc for struct pwm_mediatek_of_data (git-fixes).\n- qedf: Do not process stag work during unload (bsc#1214852).\n- qedf: Wait for stag work during unload (bsc#1214852).\n- raid1: fix use-after-free for original bio in raid1_write_request() (bsc#1221097).\n- ras/amd/fmpm: Add debugfs interface to print record entries (jsc#PED-7619).\n- ras/amd/fmpm: Avoid NULL ptr deref in get_saved_records() (jsc#PED-7619).\n- ras/amd/fmpm: Fix build when debugfs is not enabled (jsc#PED-7619).\n- ras/amd/fmpm: Fix off by one when unwinding on error (jsc#PED-7619).\n- ras/amd/fmpm: Safely handle saved records of various sizes (jsc#PED-7619).\n- ras/amd/fmpm: Save SPA values (jsc#PED-7619).\n- ras: Avoid build errors when CONFIG_DEBUG_FS=n (git-fixes).\n- ras: Avoid build errors when CONFIG_DEBUG_FS=n (jsc#PED-7619).\n- ras: export helper to get ras_debugfs_dir (jsc#PED-7619).\n- rdma/cm: add timeout to cm_destroy_id wait (git-fixes)\n- rdma/device: Fix a race between mad_client and cm_client init (git-fixes)\n- rdma/hns: fix mis-modifying default congestion control algorithm (git-fixes)\n- rdma/ipoib: Fix error code return in ipoib_mcast_join (git-fixes)\n- rdma/irdma: Remove duplicate assignment (git-fixes)\n- rdma/mana_ib: Fix bug in creation of dma regions (git-fixes).\n- rdma/mlx5: fix fortify source warning while accessing Eth segment (git-fixes)\n- rdma/mlx5: relax DEVX access upon modify commands (git-fixes)\n- rdma/rtrs-clt: Check strnlen return len in sysfs mpath_policy_store() (git-fixes)\n- rdma/srpt: do not register event handler until srpt device is fully setup (git-fixes)\n- ring-buffer: Do not set shortest_full when full target is hit (git-fixes).\n- ring-buffer: Fix full_waiters_pending in poll (git-fixes).\n- ring-buffer: Fix resetting of shortest_full (git-fixes).\n- ring-buffer: Fix waking up ring buffer readers (git-fixes).\n- ring-buffer: Make wake once of ring_buffer_wait() more robust (git-fixes).\n- ring-buffer: Use wait_event_interruptible() in ring_buffer_wait() (git-fixes).\n- rtc: mt6397: select IRQ_DOMAIN instead of depending on it (git-fixes).\n- s390/pai: fix attr_event_free upper limit for pai device drivers (git-fixes bsc#1221633).\n- s390/vfio-ap: realize the VFIO_DEVICE_GET_IRQ_INFO ioctl (bsc#1205316).\n- s390/vfio-ap: realize the VFIO_DEVICE_SET_IRQS ioctl (bsc#1205316).\n- s390/vfio-ap: wire in the vfio_device_ops request callback (bsc#1205316).\n- s390/vtime: fix average steal time calculation (git-fixes bsc#1221951).\n- sched/rt: Disallow writing invalid values to sched_rt_period_us (bsc#1220176).\n- sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset (bsc#1220176).\n- scsi: lpfc: Copyright updates for 14.4.0.1 patches (bsc#1221777).\n- scsi: lpfc: Correct size for cmdwqe/rspwqe for memset() (bsc#1221777).\n- scsi: lpfc: Correct size for wqe for memset() (bsc#1221777).\n- scsi: lpfc: Define lpfc_dmabuf type for ctx_buf ptr (bsc#1221777).\n- scsi: lpfc: Define lpfc_nodelist type for ctx_ndlp ptr (bsc#1221777).\n- scsi: lpfc: Define types in a union for generic void *context3 ptr (bsc#1221777).\n- scsi: lpfc: Move NPIV's transport unregistration to after resource clean up (bsc#1221777).\n- scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1221777).\n- scsi: lpfc: Remove IRQF_ONESHOT flag from threaded IRQ handling (bsc#1221777 bsc#1217959).\n- scsi: lpfc: Remove unnecessary log message in queuecommand path (bsc#1221777).\n- scsi: lpfc: Replace hbalock with ndlp lock in lpfc_nvme_unregister_port() (bsc#1221777).\n- scsi: lpfc: Update lpfc version to 14.4.0.1 (bsc#1221777).\n- scsi: lpfc: Update lpfc_ramp_down_queue_handler() logic (bsc#1221777).\n- scsi: lpfc: Use a dedicated lock for ras_fwlog state (bsc#1221777).\n- scsi: qedf: Remove set but unused variable 'page' (bsc#1214852).\n- scsi: qedf: Remove unused 'num_handled' variable (bsc#1214852).\n- scsi: qedf: Remove unused declaration (bsc#1214852).\n- scsi: qla2xxx: Change debug message during driver unload (bsc1221816).\n- scsi: qla2xxx: Delay I/O Abort on PCI error (bsc1221816).\n- scsi: qla2xxx: Fix N2N stuck connection (bsc1221816).\n- scsi: qla2xxx: Fix command flush on cable pull (bsc1221816).\n- scsi: qla2xxx: Fix double free of fcport (bsc1221816).\n- scsi: qla2xxx: Fix double free of the ha-\u003evp_map pointer (bsc1221816).\n- scsi: qla2xxx: NVME|FCP prefer flag not being honored (bsc1221816).\n- scsi: qla2xxx: Prevent command send on chip reset (bsc1221816).\n- scsi: qla2xxx: Split FCE|EFT trace control (bsc1221816).\n- scsi: qla2xxx: Update manufacturer detail (bsc1221816).\n- scsi: qla2xxx: Update version to 10.02.09.200-k (bsc1221816).\n- scsi: storvsc: Fix ring buffer size calculation (git-fixes).\n- scsi: target: core: Silence the message about unknown VPD pages (bsc#1221252).\n- selftests/bpf: add generic BPF program tester-loader (bsc#1222033).\n- serial: 8250_exar: Do not remove GPIO device on suspend (git-fixes).\n- serial: max310x: fix syntax error in IRQ error message (git-fixes).\n- slimbus: core: Remove usage of the deprecated ida_simple_xx() API (git-fixes).\n- soc: fsl: qbman: Always disable interrupts when taking cgr_lock (git-fixes).\n- spi: lm70llp: fix links in doc and comments (git-fixes).\n- spi: spi-mt65xx: Fix NULL pointer access in interrupt handler (git-fixes).\n- sr9800: Add check for usbnet_get_endpoints (git-fixes).\n- stackdepot: rename pool_index to pool_index_plus_1 (git-fixes).\n- staging: vc04_services: fix information leak in create_component() (git-fixes).\n- sunrpc: Add an IS_ERR() check back to where it was (git-fixes).\n- sunrpc: ECONNRESET might require a rebind (git-fixes).\n- sunrpc: Fix RPC client cleaned up the freed pipefs dentries (git-fixes).\n- sunrpc: Fix a suspicious RCU usage warning (git-fixes).\n- sunrpc: fix a memleak in gss_import_v2_context (git-fixes).\n- sunrpc: fix some memleaks in gssx_dec_option_array (git-fixes).\n- svcrdma: Drop connection after an RDMA Read error (git-fixes).\n- tracing/ring-buffer: Fix wait_on_pipe() race (git-fixes).\n- tracing: Have saved_cmdlines arrays all in one allocation (git-fixes).\n- tracing: Remove precision vsnprintf() check from print event (git-fixes).\n- tracing: Use .flush() call to wake up readers (git-fixes).\n- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc (bsc#1222619).\n- tty: serial: fsl_lpuart: avoid idle preamble pending if CTS is enabled (git-fixes).\n- tty: serial: samsung: fix tx_empty() to return TIOCSER_TEMT (git-fixes).\n- tty: vt: fix 20 vs 0x20 typo in EScsiignore (git-fixes).\n- ubifs: Queue up space reservation tasks if retrying many times (git-fixes).\n- ubifs: Remove unreachable code in dbg_check_ltab_lnum (git-fixes).\n- ubifs: Set page uptodate in the correct place (git-fixes).\n- ubifs: dbg_check_idx_size: Fix kmemleak if loading znode failed (git-fixes).\n- ubifs: fix sort function prototype (git-fixes).\n- usb: audio-v2: Correct comments for struct uac_clock_selector_descriptor (git-fixes).\n- usb: cdc-wdm: close race between read and workqueue (git-fixes).\n- usb: core: Fix deadlock in usb_deauthorize_interface() (git-fixes).\n- usb: dwc2: gadget: Fix exiting from clock gating (git-fixes).\n- usb: dwc2: gadget: LPM flow fix (git-fixes).\n- usb: dwc2: host: Fix ISOC flow in DDMA mode (git-fixes).\n- usb: dwc2: host: Fix hibernation flow (git-fixes).\n- usb: dwc2: host: Fix remote wakeup from hibernation (git-fixes).\n- usb: dwc3: Properly set system wakeup (git-fixes).\n- usb: gadget: ncm: Fix handling of zero block length packets (git-fixes).\n- usb: gadget: net2272: Use irqflags in the call to net2272_probe_fin (git-fixes).\n- usb: port: Do not try to peer unused USB ports based on location (git-fixes).\n- usb: typec: Return size of buffer if pd_set operation succeeds (git-fixes).\n- usb: typec: ucsi: Check for notifications after init (git-fixes).\n- usb: typec: ucsi: Clean up UCSI_CABLE_PROP macros (git-fixes).\n- usb: typec: ucsi: Clear EVENT_PENDING under PPM lock (git-fixes).\n- usb: usb-storage: Prevent divide-by-0 error in isd200_ata_command (git-fixes).\n- usb: xhci: Add error handling in xhci_map_urb_for_dma (git-fixes).\n- vboxsf: Avoid an spurious warning if load_nls_xxx() fails (git-fixes).\n- vdpa/mlx5: Allow CVQ size changes (git-fixes).\n- vt: fix unicode buffer corruption when deleting characters (git-fixes).\n- watchdog: stm32_iwdg: initialize default timeout (git-fixes).\n- wifi: ath10k: fix NULL pointer dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() (git-fixes).\n- wifi: ath11k: decrease MHI channel buffer length to 8KB (bsc#1207948).\n- wifi: ath11k: initialize rx_mcs_80 and rx_mcs_160 before use (git-fixes).\n- wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete (git-fixes).\n- wifi: b43: Disable QoS for bcm4331 (git-fixes).\n- wifi: b43: Stop correct queue in DMA worker when QoS is disabled (git-fixes).\n- wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled (git-fixes).\n- wifi: b43: Stop/wake correct queue in PIO Tx path when QoS is disabled (git-fixes).\n- wifi: brcmfmac: fix copyright year mentioned in platform_data header (git-fixes).\n- wifi: brcmsmac: avoid function pointer casts (git-fixes).\n- wifi: iwlwifi: dbg-tlv: ensure NUL termination (git-fixes).\n- wifi: iwlwifi: fix EWRD table validity check (git-fixes).\n- wifi: iwlwifi: fw: do not always use FW dump trig (git-fixes).\n- wifi: iwlwifi: mvm: do not set replay counters to 0xff (git-fixes).\n- wifi: iwlwifi: mvm: report beacon protection failures (git-fixes).\n- wifi: iwlwifi: mvm: rfi: fix potential response leaks (git-fixes).\n- wifi: iwlwifi: mvm: use FW rate for non-data only on new devices (git-fixes).\n- wifi: libertas: fix some memleaks in lbs_allocate_cmd_buffer() (git-fixes).\n- wifi: mwifiex: debugfs: Drop unnecessary error check for debugfs_create_dir() (git-fixes).\n- wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work (git-fixes).\n- wifi: rtw88: 8821c: Fix false alarm count (git-fixes).\n- wifi: wilc1000: fix RCU usage in connect path (git-fixes).\n- wifi: wilc1000: fix declarations ordering (stable-fixes).\n- wifi: wilc1000: fix multi-vif management when deleting a vif (git-fixes).\n- wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces (git-fixes).\n- x86/CPU/AMD: Update the Zenbleed microcode revisions (git-fixes).\n- x86/bugs: Fix the SRSO mitigation on Zen3/4 (git-fixes).\n- x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (git-fixes).\n- x86/xen: Add some null pointer checking to smp.c (git-fixes).\n- x86/xen: add CPU dependencies for 32-bit build (git-fixes).\n- x86/xen: fix percpu vcpu_info allocation (git-fixes).\n- xen-netback: properly sync TX responses (git-fixes).\n- xen-netfront: Add missing skb_mark_for_recycle (git-fixes).\n- xen/gntdev: Fix the abuse of underlying struct page in DMA-buf import (git-fixes).\n- xen/xenbus: document will_handle argument for xenbus_watch_path() (git-fixes).\n- xhci: handle isoc Babble and Buffer Overrun events properly (git-fixes).\n- xhci: process isoc TD properly when there was a transaction error mid TD (git-fixes).\n","status":"published","published":"2024-05-03T07:54:25Z","modified":"2026-02-04T03:36:21.688453Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"USN-6688-1","title":"linux-oem-6.1 vulnerabilities","description":"Pratyush Yadav discovered that the Xen network backend implementation in\nthe Linux kernel did not properly handle zero length data request, leading\nto a null pointer dereference vulnerability. An attacker in a guest VM\ncould possibly use this to cause a denial of service (host domain crash).\n(CVE-2023-46838)\n\nIt was discovered that the Habana's AI Processors driver in the Linux\nkernel did not properly initialize certain data structures before passing\nthem to user space. A local attacker could use this to expose sensitive\ninformation (kernel memory). (CVE-2023-50431)\n\nMurray McAllister discovered that the VMware Virtual GPU DRM driver in the\nLinux kernel did not properly handle memory objects when storing surfaces,\nleading to a use-after-free vulnerability. A local attacker in a guest VM\ncould use this to cause a denial of service (system crash) or possibly\nexecute arbitrary code. (CVE-2023-5633)\n\nIt was discovered that the CIFS network file system implementation in the\nLinux kernel did not properly validate certain SMB messages, leading to an\nout-of-bounds read vulnerability. An attacker could use this to cause a\ndenial of service (system crash) or possibly expose sensitive information.\n(CVE-2023-6610)\n\nIt was discovered that the VirtIO subsystem in the Linux kernel did not\nproperly initialize memory in some situations. A local attacker could use\nthis to possibly expose sensitive information (kernel memory).\n(CVE-2024-0340)\n\nLonial Con discovered that the netfilter subsystem in the Linux kernel did\nnot properly handle element deactivation in certain cases, leading to a\nuse-after-free vulnerability. A local attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2024-1085)\n\nNotselwyn discovered that the netfilter subsystem in the Linux kernel did\nnot properly handle verdict parameters in certain cases, leading to a use-\nafter-free vulnerability. A local attacker could use this to cause a denial\nof service (system crash) or possibly execute arbitrary code.\n(CVE-2024-1086)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel, leading to a null pointer dereference vulnerability. A\nprivileged local attacker could use this to possibly cause a denial of\nservice (system crash). (CVE-2024-24860)\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  - Architecture specifics;\n  - Block layer;\n  - ACPI drivers;\n  - Android drivers;\n  - EDAC drivers;\n  - GPU drivers;\n  - InfiniBand drivers;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - PWM drivers;\n  - SCSI drivers;\n  - SPMI drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Logical Link Layer;\n  - Netfilter;\n  - Unix domain sockets;\n  - AppArmor security module;\n(CVE-2024-26599, CVE-2023-52604, CVE-2023-52439, CVE-2024-26627,\nCVE-2024-26601, CVE-2024-26628, CVE-2023-52607, CVE-2023-52456,\nCVE-2023-52602, CVE-2023-52443, CVE-2023-52599, CVE-2023-52603,\nCVE-2024-26588, CVE-2024-26581, CVE-2023-52600, CVE-2024-26624,\nCVE-2023-52584, CVE-2024-26625, CVE-2023-52606, CVE-2023-52463,\nCVE-2023-52464, CVE-2023-52597, CVE-2023-52595, CVE-2023-52458,\nCVE-2023-52457, CVE-2023-52438, CVE-2023-52469, CVE-2023-52462,\nCVE-2024-26589, CVE-2024-26592, CVE-2024-26594, CVE-2023-52601,\nCVE-2023-52593, CVE-2023-52436, CVE-2023-52447, CVE-2023-52587,\nCVE-2023-52445, CVE-2023-52454, CVE-2023-52451, CVE-2023-52605,\nCVE-2024-26597, CVE-2023-52448, CVE-2023-52598, CVE-2024-26591,\nCVE-2023-52449, CVE-2023-52444, CVE-2023-52583, CVE-2023-52589,\nCVE-2024-26598, CVE-2023-52470, CVE-2023-52594, CVE-2023-52588,\nCVE-2023-52467, CVE-2024-26600)\n","status":"published","published":"2024-03-11T20:17:36Z","modified":"2026-10-22T23:19:09.218049015Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6766-1","title":"linux, linux-azure, linux-azure-5.15, linux-azure-fde, linux-azure-fde-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-gkeop-5.15, linux-ibm, linux-ibm-5.15, linux-kvm, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-nvidia, linux-oracle, linux-oracle-5.15 vulnerabilities","description":"\nIt was discovered that the Open vSwitch implementation in the Linux kernel\ncould overflow its stack during recursive action operations under certain\nconditions. A local attacker could use this to cause a denial of service\n(system crash). (CVE-2024-1151)\n\nSander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida\ndiscovered that the Linux kernel mitigations for the initial Branch History\nInjection vulnerability (CVE-2022-0001) were insufficient for Intel\nprocessors. A local attacker could potentially use this to expose sensitive\ninformation. (CVE-2024-2201)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\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  - PowerPC architecture;\n  - S390 architecture;\n  - Core kernel;\n  - Block layer subsystem;\n  - Android drivers;\n  - Power management core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Cryptographic API;\n  - Device frequency;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - IIO Magnetometer sensors drivers;\n  - InfiniBand drivers;\n  - Media drivers;\n  - Network drivers;\n  - PCI driver for MicroSemi Switchtec;\n  - PHY drivers;\n  - SCSI drivers;\n  - DesignWare USB3 driver;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - Memory management;\n  - CAN network layer;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Realtek audio codecs;\n(CVE-2023-52594, CVE-2023-52601, CVE-2024-26826, CVE-2023-52622,\nCVE-2024-26665, CVE-2023-52493, CVE-2023-52633, CVE-2024-26684,\nCVE-2024-26663, CVE-2023-52618, CVE-2023-52588, CVE-2023-52637,\nCVE-2024-26825, CVE-2023-52606, CVE-2024-26594, CVE-2024-26625,\nCVE-2024-26720, CVE-2024-26614, CVE-2023-52627, CVE-2023-52602,\nCVE-2024-26673, CVE-2024-26685, CVE-2023-52638, CVE-2023-52498,\nCVE-2023-52619, CVE-2024-26910, CVE-2024-26689, CVE-2023-52583,\nCVE-2024-26676, CVE-2024-26671, CVE-2024-26704, CVE-2024-26608,\nCVE-2024-26610, CVE-2024-26592, CVE-2023-52599, CVE-2023-52595,\nCVE-2024-26660, CVE-2023-52617, CVE-2024-26645, CVE-2023-52486,\nCVE-2023-52631, CVE-2023-52607, CVE-2023-52608, CVE-2024-26722,\nCVE-2024-26615, CVE-2023-52615, CVE-2024-26636, CVE-2023-52642,\nCVE-2023-52587, CVE-2024-26712, CVE-2024-26675, CVE-2023-52614,\nCVE-2024-26606, CVE-2024-26916, CVE-2024-26600, CVE-2024-26679,\nCVE-2024-26829, CVE-2024-26641, CVE-2023-52623, CVE-2024-26627,\nCVE-2024-26696, CVE-2024-26640, CVE-2024-26635, CVE-2023-52491,\nCVE-2024-26664, CVE-2024-26602, CVE-2023-52604, CVE-2024-26717,\nCVE-2023-52643, CVE-2024-26593, CVE-2023-52598, CVE-2024-26668,\nCVE-2023-52435, CVE-2023-52597, CVE-2024-26715, CVE-2024-26707,\nCVE-2023-52635, CVE-2024-26695, CVE-2024-26698, CVE-2023-52494,\nCVE-2024-26920, CVE-2024-26808, CVE-2023-52616, CVE-2023-52492,\nCVE-2024-26702, CVE-2024-26644, CVE-2023-52489, CVE-2024-26697)\n","status":"published","published":"2024-05-07T19:22:43Z","modified":"2026-10-29T20:03:02.990286666Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6766-2","title":"linux-hwe-5.15, linux-raspi vulnerabilities","description":"It was discovered that the Open vSwitch implementation in the Linux kernel\ncould overflow its stack during recursive action operations under certain\nconditions. A local attacker could use this to cause a denial of service\n(system crash). (CVE-2024-1151)\n\nSander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida\ndiscovered that the Linux kernel mitigations for the initial Branch History\nInjection vulnerability (CVE-2022-0001) were insufficient for Intel\nprocessors. A local attacker could potentially use this to expose sensitive\ninformation. (CVE-2024-2201)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\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  - PowerPC architecture;\n  - S390 architecture;\n  - Core kernel;\n  - Block layer subsystem;\n  - Android drivers;\n  - Power management core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Cryptographic API;\n  - Device frequency;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - IIO Magnetometer sensors drivers;\n  - InfiniBand drivers;\n  - Media drivers;\n  - Network drivers;\n  - PCI driver for MicroSemi Switchtec;\n  - PHY drivers;\n  - SCSI drivers;\n  - DesignWare USB3 driver;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - Memory management;\n  - CAN network layer;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Realtek audio codecs;\n(CVE-2023-52594, CVE-2023-52601, CVE-2024-26826, CVE-2023-52622,\nCVE-2024-26665, CVE-2023-52493, CVE-2023-52633, CVE-2024-26684,\nCVE-2024-26663, CVE-2023-52618, CVE-2023-52588, CVE-2023-52637,\nCVE-2024-26825, CVE-2023-52606, CVE-2024-26594, CVE-2024-26625,\nCVE-2024-26720, CVE-2024-26614, CVE-2023-52627, CVE-2023-52602,\nCVE-2024-26673, CVE-2024-26685, CVE-2023-52638, CVE-2023-52498,\nCVE-2023-52619, CVE-2024-26910, CVE-2024-26689, CVE-2023-52583,\nCVE-2024-26676, CVE-2024-26671, CVE-2024-26704, CVE-2024-26608,\nCVE-2024-26610, CVE-2024-26592, CVE-2023-52599, CVE-2023-52595,\nCVE-2024-26660, CVE-2023-52617, CVE-2024-26645, CVE-2023-52486,\nCVE-2023-52631, CVE-2023-52607, CVE-2023-52608, CVE-2024-26722,\nCVE-2024-26615, CVE-2023-52615, CVE-2024-26636, CVE-2023-52642,\nCVE-2023-52587, CVE-2024-26712, CVE-2024-26675, CVE-2023-52614,\nCVE-2024-26606, CVE-2024-26916, CVE-2024-26600, CVE-2024-26679,\nCVE-2024-26829, CVE-2024-26641, CVE-2023-52623, CVE-2024-26627,\nCVE-2024-26696, CVE-2024-26640, CVE-2024-26635, CVE-2023-52491,\nCVE-2024-26664, CVE-2024-26602, CVE-2023-52604, CVE-2024-26717,\nCVE-2023-52643, CVE-2024-26593, CVE-2023-52598, CVE-2024-26668,\nCVE-2023-52435, CVE-2023-52597, CVE-2024-26715, CVE-2024-26707,\nCVE-2023-52635, CVE-2024-26695, CVE-2024-26698, CVE-2023-52494,\nCVE-2024-26920, CVE-2024-26808, CVE-2023-52616, CVE-2023-52492,\nCVE-2024-26702, CVE-2024-26644, CVE-2023-52489, CVE-2024-26697)\n","status":"published","published":"2024-05-15T15:15:08Z","modified":"2026-10-29T20:01:56.015645889Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6766-3","title":"linux-aws, linux-aws-5.15 vulnerabilities","description":"It was discovered that the Open vSwitch implementation in the Linux kernel\ncould overflow its stack during recursive action operations under certain\nconditions. A local attacker could use this to cause a denial of service\n(system crash). (CVE-2024-1151)\n\nSander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida\ndiscovered that the Linux kernel mitigations for the initial Branch History\nInjection vulnerability (CVE-2022-0001) were insufficient for Intel\nprocessors. A local attacker could potentially use this to expose sensitive\ninformation. (CVE-2024-2201)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\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  - PowerPC architecture;\n  - S390 architecture;\n  - Core kernel;\n  - Block layer subsystem;\n  - Android drivers;\n  - Power management core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Cryptographic API;\n  - Device frequency;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - IIO Magnetometer sensors drivers;\n  - InfiniBand drivers;\n  - Media drivers;\n  - Network drivers;\n  - PCI driver for MicroSemi Switchtec;\n  - PHY drivers;\n  - SCSI drivers;\n  - DesignWare USB3 driver;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - Memory management;\n  - CAN network layer;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Realtek audio codecs;\n(CVE-2023-52594, CVE-2023-52601, CVE-2024-26826, CVE-2023-52622,\nCVE-2024-26665, CVE-2023-52493, CVE-2023-52633, CVE-2024-26684,\nCVE-2024-26663, CVE-2023-52618, CVE-2023-52588, CVE-2023-52637,\nCVE-2024-26825, CVE-2023-52606, CVE-2024-26594, CVE-2024-26625,\nCVE-2024-26720, CVE-2024-26614, CVE-2023-52627, CVE-2023-52602,\nCVE-2024-26673, CVE-2024-26685, CVE-2023-52638, CVE-2023-52498,\nCVE-2023-52619, CVE-2024-26910, CVE-2024-26689, CVE-2023-52583,\nCVE-2024-26676, CVE-2024-26671, CVE-2024-26704, CVE-2024-26608,\nCVE-2024-26610, CVE-2024-26592, CVE-2023-52599, CVE-2023-52595,\nCVE-2024-26660, CVE-2023-52617, CVE-2024-26645, CVE-2023-52486,\nCVE-2023-52631, CVE-2023-52607, CVE-2023-52608, CVE-2024-26722,\nCVE-2024-26615, CVE-2023-52615, CVE-2024-26636, CVE-2023-52642,\nCVE-2023-52587, CVE-2024-26712, CVE-2024-26675, CVE-2023-52614,\nCVE-2024-26606, CVE-2024-26916, CVE-2024-26600, CVE-2024-26679,\nCVE-2024-26829, CVE-2024-26641, CVE-2023-52623, CVE-2024-26627,\nCVE-2024-26696, CVE-2024-26640, CVE-2024-26635, CVE-2023-52491,\nCVE-2024-26664, CVE-2024-26602, CVE-2023-52604, CVE-2024-26717,\nCVE-2023-52643, CVE-2024-26593, CVE-2023-52598, CVE-2024-26668,\nCVE-2023-52435, CVE-2023-52597, CVE-2024-26715, CVE-2024-26707,\nCVE-2023-52635, CVE-2024-26695, CVE-2024-26698, CVE-2023-52494,\nCVE-2024-26920, CVE-2024-26808, CVE-2023-52616, CVE-2023-52492,\nCVE-2024-26702, CVE-2024-26644, CVE-2023-52489, CVE-2024-26697)\n","status":"published","published":"2024-05-20T13:05:13Z","modified":"2026-10-29T20:02:33.345781548Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6767-1","title":"linux, linux-aws, linux-aws-5.4, linux-azure, linux-azure-5.4, linux-gcp, linux-gcp-5.4, linux-gkeop, linux-hwe-5.4, linux-ibm, linux-ibm-5.4, linux-iot, linux-kvm, linux-oracle, linux-oracle-5.4, linux-raspi, linux-raspi-5.4, linux-xilinx-zynqmp vulnerabilities","description":"\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\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  - ARM64 architecture;\n  - PowerPC architecture;\n  - S390 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - Hardware random number generator core;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO Magnetometer sensors drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - PCI driver for MicroSemi Switchtec;\n  - PHY drivers;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - Pstore file system;\n  - Core kernel;\n  - Memory management;\n  - CAN network layer;\n  - Networking core;\n  - IPv4 networking;\n  - Logical Link layer;\n  - Netfilter;\n  - NFC subsystem;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Realtek audio codecs;\n(CVE-2024-26696, CVE-2023-52583, CVE-2024-26720, CVE-2023-52615,\nCVE-2023-52599, CVE-2023-52587, CVE-2024-26635, CVE-2024-26704,\nCVE-2024-26625, CVE-2024-26825, CVE-2023-52622, CVE-2023-52435,\nCVE-2023-52617, CVE-2023-52598, CVE-2024-26645, CVE-2023-52619,\nCVE-2024-26593, CVE-2024-26685, CVE-2023-52602, CVE-2023-52486,\nCVE-2024-26697, CVE-2024-26675, CVE-2024-26600, CVE-2023-52604,\nCVE-2024-26664, CVE-2024-26606, CVE-2023-52594, CVE-2024-26671,\nCVE-2024-26598, CVE-2024-26673, CVE-2024-26920, CVE-2024-26722,\nCVE-2023-52601, CVE-2024-26602, CVE-2023-52637, CVE-2023-52623,\nCVE-2024-26702, CVE-2023-52597, CVE-2024-26684, CVE-2023-52606,\nCVE-2024-26679, CVE-2024-26663, CVE-2024-26910, CVE-2024-26615,\nCVE-2023-52595, CVE-2023-52607, CVE-2024-26636)\n","status":"published","published":"2024-05-07T19:36:29Z","modified":"2026-10-22T23:20:42.378176063Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6767-2","title":"linux-bluefield vulnerabilities","description":"Chenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\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  - ARM64 architecture;\n  - PowerPC architecture;\n  - S390 architecture;\n  - Block layer subsystem;\n  - Android drivers;\n  - Hardware random number generator core;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO Magnetometer sensors drivers;\n  - InfiniBand drivers;\n  - Network drivers;\n  - PCI driver for MicroSemi Switchtec;\n  - PHY drivers;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - Pstore file system;\n  - Core kernel;\n  - Memory management;\n  - CAN network layer;\n  - Networking core;\n  - IPv4 networking;\n  - Logical Link layer;\n  - Netfilter;\n  - NFC subsystem;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Realtek audio codecs;\n(CVE-2024-26696, CVE-2023-52583, CVE-2024-26720, CVE-2023-52615,\nCVE-2023-52599, CVE-2023-52587, CVE-2024-26635, CVE-2024-26704,\nCVE-2024-26625, CVE-2024-26825, CVE-2023-52622, CVE-2023-52435,\nCVE-2023-52617, CVE-2023-52598, CVE-2024-26645, CVE-2023-52619,\nCVE-2024-26593, CVE-2024-26685, CVE-2023-52602, CVE-2023-52486,\nCVE-2024-26697, CVE-2024-26675, CVE-2024-26600, CVE-2023-52604,\nCVE-2024-26664, CVE-2024-26606, CVE-2023-52594, CVE-2024-26671,\nCVE-2024-26598, CVE-2024-26673, CVE-2024-26920, CVE-2024-26722,\nCVE-2023-52601, CVE-2024-26602, CVE-2023-52637, CVE-2023-52623,\nCVE-2024-26702, CVE-2023-52597, CVE-2024-26684, CVE-2023-52606,\nCVE-2024-26679, CVE-2024-26663, CVE-2024-26910, CVE-2024-26615,\nCVE-2023-52595, CVE-2023-52607, CVE-2024-26636)\n","status":"published","published":"2024-05-14T09:00:08Z","modified":"2026-10-22T23:19:13.071604436Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6795-1","title":"linux-intel-iotg vulnerabilities","description":"Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux\nkernel contained a race condition during device removal, leading to a use-\nafter-free vulnerability. A physically proximate attacker could possibly\nuse this to cause a denial of service (system crash). (CVE-2023-47233)\n\nIt was discovered that the Open vSwitch implementation in the Linux kernel\ncould overflow its stack during recursive action operations under certain\nconditions. A local attacker could use this to cause a denial of service\n(system crash). (CVE-2024-1151)\n\nSander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida\ndiscovered that the Linux kernel mitigations for the initial Branch History\nInjection vulnerability (CVE-2022-0001) were insufficient for Intel\nprocessors. A local attacker could potentially use this to expose sensitive\ninformation. (CVE-2024-2201)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\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  - PowerPC architecture;\n  - S390 architecture;\n  - Core kernel;\n  - Block layer subsystem;\n  - Android drivers;\n  - Power management core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Cryptographic API;\n  - Device frequency;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - IIO Magnetometer sensors drivers;\n  - InfiniBand drivers;\n  - Media drivers;\n  - Network drivers;\n  - PCI driver for MicroSemi Switchtec;\n  - PHY drivers;\n  - SCSI drivers;\n  - DesignWare USB3 driver;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - SMB network file system;\n  - Memory management;\n  - CAN network layer;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Tomoyo security module;\n  - Realtek audio codecs;\n(CVE-2023-52616, CVE-2024-26679, CVE-2024-26608, CVE-2023-52594,\nCVE-2024-26622, CVE-2023-52643, CVE-2024-26594, CVE-2023-52598,\nCVE-2023-52627, CVE-2023-52491, CVE-2024-26592, CVE-2024-26717,\nCVE-2023-52638, CVE-2024-26704, CVE-2023-52637, CVE-2024-26645,\nCVE-2023-52602, CVE-2024-26722, CVE-2024-26671, CVE-2023-52599,\nCVE-2024-26720, CVE-2023-52631, CVE-2023-52486, CVE-2024-26640,\nCVE-2023-52606, CVE-2023-52633, CVE-2024-26593, CVE-2024-26664,\nCVE-2023-52618, CVE-2024-26625, CVE-2023-52604, CVE-2024-26695,\nCVE-2024-26644, CVE-2024-26826, CVE-2024-26600, CVE-2024-26808,\nCVE-2023-52619, CVE-2023-52597, CVE-2024-26602, CVE-2024-26635,\nCVE-2023-52623, CVE-2024-26665, CVE-2024-26916, CVE-2024-26689,\nCVE-2023-52635, CVE-2024-26712, CVE-2023-52614, CVE-2024-26606,\nCVE-2024-26610, CVE-2024-26675, CVE-2023-52617, CVE-2024-26697,\nCVE-2023-52595, CVE-2023-52494, CVE-2024-26641, CVE-2024-26698,\nCVE-2024-26707, CVE-2024-26673, CVE-2023-52493, CVE-2024-26676,\nCVE-2024-26910, CVE-2023-52601, CVE-2024-26660, CVE-2023-52608,\nCVE-2024-26615, CVE-2023-52587, CVE-2024-26825, CVE-2023-52498,\nCVE-2023-52492, CVE-2024-26668, CVE-2024-26715, CVE-2024-26685,\nCVE-2024-26702, CVE-2024-26663, CVE-2024-26636, CVE-2024-26627,\nCVE-2024-26696, CVE-2023-52583, CVE-2023-52642, CVE-2023-52489,\nCVE-2024-26614, CVE-2024-26829, CVE-2024-26684, CVE-2023-52615,\nCVE-2023-52435, CVE-2023-52530, CVE-2023-52607, CVE-2024-26920,\nCVE-2023-52622, CVE-2023-52588)\n","status":"published","published":"2024-05-28T19:06:59Z","modified":"2026-10-29T20:02:32.661195287Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-6818-1","title":"linux, linux-gcp, linux-gcp-6.5, linux-lowlatency, linux-lowlatency-hwe-6.5, linux-raspi vulnerabilities","description":"Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel\ndid not properly validate H2C PDU data, leading to a null pointer\ndereference vulnerability. A remote attacker could use this to cause a\ndenial of service (system crash). (CVE-2023-6356, CVE-2023-6535,\nCVE-2023-6536)\n\nIt was discovered that the Intel Data Streaming and Intel Analytics\nAccelerator drivers in the Linux kernel allowed direct access to the\ndevices for unprivileged users and virtual machines. A local attacker could\nuse this to cause a denial of service. (CVE-2024-21823)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel, leading to a null pointer dereference vulnerability. A\nprivileged local attacker could use this to possibly cause a denial of\nservice (system crash). (CVE-2024-24860)\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  - ARM64 architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Core kernel;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Drivers core;\n  - Power management core;\n  - Bus devices;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI driver for MicroSemi Switchtec;\n  - Power supply drivers;\n  - RPMSG subsystem;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - SPMI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - VFIO drivers;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system server daemon;\n  - File systems infrastructure;\n  - Pstore file system;\n  - ReiserFS file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Memory management;\n  - TLS protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Network traffic control;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - AppArmor security module;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2023-52598, CVE-2023-52676, CVE-2023-52609, CVE-2024-26620,\nCVE-2023-52487, CVE-2023-52465, CVE-2023-52473, CVE-2023-52467,\nCVE-2024-26583, CVE-2023-52669, CVE-2023-52664, CVE-2023-52449,\nCVE-2023-52614, CVE-2024-26595, CVE-2023-52611, CVE-2023-52696,\nCVE-2023-52591, CVE-2023-52491, CVE-2024-35839, CVE-2023-52679,\nCVE-2024-26607, CVE-2023-52587, CVE-2023-52469, CVE-2023-52608,\nCVE-2023-52617, CVE-2023-52698, CVE-2024-26673, CVE-2024-35835,\nCVE-2024-26808, CVE-2024-26668, CVE-2023-52626, CVE-2023-52621,\nCVE-2024-35837, CVE-2023-52489, CVE-2023-52597, CVE-2024-26649,\nCVE-2024-26615, CVE-2024-35838, CVE-2023-52693, CVE-2023-52497,\nCVE-2024-35842, CVE-2024-26618, CVE-2024-26610, CVE-2024-26631,\nCVE-2024-26644, CVE-2024-26627, CVE-2023-52677, CVE-2023-52472,\nCVE-2023-52627, CVE-2023-52486, CVE-2023-52632, CVE-2023-52494,\nCVE-2023-52468, CVE-2024-26634, CVE-2023-52588, CVE-2024-26646,\nCVE-2024-26584, CVE-2023-52443, CVE-2023-52691, CVE-2024-26612,\nCVE-2023-52595, CVE-2024-26592, CVE-2024-26623, CVE-2023-52492,\nCVE-2024-26670, CVE-2023-52583, CVE-2023-52681, CVE-2023-52635,\nCVE-2023-52457, CVE-2023-52445, CVE-2024-26629, CVE-2024-26594,\nCVE-2023-52675, CVE-2023-52488, CVE-2023-52446, CVE-2024-26625,\nCVE-2023-52697, CVE-2023-52453, CVE-2023-52498, CVE-2023-52686,\nCVE-2023-52593, CVE-2023-52612, CVE-2023-52687, CVE-2023-52470,\nCVE-2023-52455, CVE-2023-52444, CVE-2024-26608, CVE-2024-26633,\nCVE-2024-26645, CVE-2023-52451, CVE-2023-52456, CVE-2024-26640,\nCVE-2023-52670, CVE-2023-52589, CVE-2024-26598, CVE-2024-35841,\nCVE-2024-26647, CVE-2024-26636, CVE-2023-52680, CVE-2023-52616,\nCVE-2023-52685, CVE-2024-26582, CVE-2024-26638, CVE-2023-52694,\nCVE-2024-35840, CVE-2023-52448, CVE-2023-52623, CVE-2023-52462,\nCVE-2023-52452, CVE-2024-26641, CVE-2023-52683, CVE-2023-52682,\nCVE-2023-52594, CVE-2023-52490, CVE-2023-52493, CVE-2023-52633,\nCVE-2023-52606, CVE-2024-26669, CVE-2023-52584, CVE-2024-26585,\nCVE-2023-52610, CVE-2023-52672, CVE-2023-52450, CVE-2023-52666,\nCVE-2023-52458, CVE-2023-52622, CVE-2023-52674, CVE-2023-52619,\nCVE-2024-26586, CVE-2023-52667, CVE-2024-26616, CVE-2023-52463,\nCVE-2024-26632, CVE-2023-52447, CVE-2023-52692, CVE-2023-52678,\nCVE-2023-52607, CVE-2023-52618, CVE-2023-52464, CVE-2024-26671,\nCVE-2023-52599, CVE-2023-52454, CVE-2023-52495, CVE-2023-52690)\n","status":"published","published":"2024-06-07T20:18:53Z","modified":"2026-11-03T21:17:04.651285074Z","updated_at":"2026-11-03T21:44:03.981358Z"},{"id":"USN-6818-3","title":"linux-nvidia-6.5 vulnerabilities","description":"Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel\ndid not properly validate H2C PDU data, leading to a null pointer\ndereference vulnerability. A remote attacker could use this to cause a\ndenial of service (system crash). (CVE-2023-6356, CVE-2023-6535,\nCVE-2023-6536)\n\nIt was discovered that the Intel Data Streaming and Intel Analytics\nAccelerator drivers in the Linux kernel allowed direct access to the\ndevices for unprivileged users and virtual machines. A local attacker could\nuse this to cause a denial of service. (CVE-2024-21823)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel, leading to a null pointer dereference vulnerability. A\nprivileged local attacker could use this to possibly cause a denial of\nservice (system crash). (CVE-2024-24860)\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  - ARM64 architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Core kernel;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Drivers core;\n  - Power management core;\n  - Bus devices;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI driver for MicroSemi Switchtec;\n  - Power supply drivers;\n  - RPMSG subsystem;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - SPMI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - VFIO drivers;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system server daemon;\n  - File systems infrastructure;\n  - Pstore file system;\n  - ReiserFS file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Memory management;\n  - TLS protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Network traffic control;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - AppArmor security module;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2023-52598, CVE-2023-52676, CVE-2023-52609, CVE-2024-26620,\nCVE-2023-52487, CVE-2023-52465, CVE-2023-52473, CVE-2023-52467,\nCVE-2024-26583, CVE-2023-52669, CVE-2023-52664, CVE-2023-52449,\nCVE-2023-52614, CVE-2024-26595, CVE-2023-52611, CVE-2023-52696,\nCVE-2023-52591, CVE-2023-52491, CVE-2024-35839, CVE-2023-52679,\nCVE-2024-26607, CVE-2023-52587, CVE-2023-52469, CVE-2023-52608,\nCVE-2023-52617, CVE-2023-52698, CVE-2024-26673, CVE-2024-35835,\nCVE-2024-26808, CVE-2024-26668, CVE-2023-52626, CVE-2023-52621,\nCVE-2024-35837, CVE-2023-52489, CVE-2023-52597, CVE-2024-26649,\nCVE-2024-26615, CVE-2024-35838, CVE-2023-52693, CVE-2023-52497,\nCVE-2024-35842, CVE-2024-26618, CVE-2024-26610, CVE-2024-26631,\nCVE-2024-26644, CVE-2024-26627, CVE-2023-52677, CVE-2023-52472,\nCVE-2023-52627, CVE-2023-52486, CVE-2023-52632, CVE-2023-52494,\nCVE-2023-52468, CVE-2024-26634, CVE-2023-52588, CVE-2024-26646,\nCVE-2024-26584, CVE-2023-52443, CVE-2023-52691, CVE-2024-26612,\nCVE-2023-52595, CVE-2024-26592, CVE-2024-26623, CVE-2023-52492,\nCVE-2024-26670, CVE-2023-52583, CVE-2023-52681, CVE-2023-52635,\nCVE-2023-52457, CVE-2023-52445, CVE-2024-26629, CVE-2024-26594,\nCVE-2023-52675, CVE-2023-52488, CVE-2023-52446, CVE-2024-26625,\nCVE-2023-52697, CVE-2023-52453, CVE-2023-52498, CVE-2023-52686,\nCVE-2023-52593, CVE-2023-52612, CVE-2023-52687, CVE-2023-52470,\nCVE-2023-52455, CVE-2023-52444, CVE-2024-26608, CVE-2024-26633,\nCVE-2024-26645, CVE-2023-52451, CVE-2023-52456, CVE-2024-26640,\nCVE-2023-52670, CVE-2023-52589, CVE-2024-26598, CVE-2024-35841,\nCVE-2024-26647, CVE-2024-26636, CVE-2023-52680, CVE-2023-52616,\nCVE-2023-52685, CVE-2024-26582, CVE-2024-26638, CVE-2023-52694,\nCVE-2024-35840, CVE-2023-52448, CVE-2023-52623, CVE-2023-52462,\nCVE-2023-52452, CVE-2024-26641, CVE-2023-52683, CVE-2023-52682,\nCVE-2023-52594, CVE-2023-52490, CVE-2023-52493, CVE-2023-52633,\nCVE-2023-52606, CVE-2024-26669, CVE-2023-52584, CVE-2024-26585,\nCVE-2023-52610, CVE-2023-52672, CVE-2023-52450, CVE-2023-52666,\nCVE-2023-52458, CVE-2023-52622, CVE-2023-52674, CVE-2023-52619,\nCVE-2024-26586, CVE-2023-52667, CVE-2024-26616, CVE-2023-52463,\nCVE-2024-26632, CVE-2023-52447, CVE-2023-52692, CVE-2023-52678,\nCVE-2023-52607, CVE-2023-52618, CVE-2023-52464, CVE-2024-26671,\nCVE-2023-52599, CVE-2023-52454, CVE-2023-52495, CVE-2023-52690)\n","status":"published","published":"2024-06-14T15:59:05Z","modified":"2026-11-03T21:17:25.738650589Z","updated_at":"2026-11-03T21:44:00.661154Z"},{"id":"USN-6818-4","title":"linux-hwe-6.5 vulnerabilities","description":"Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel\ndid not properly validate H2C PDU data, leading to a null pointer\ndereference vulnerability. A remote attacker could use this to cause a\ndenial of service (system crash). (CVE-2023-6356, CVE-2023-6535,\nCVE-2023-6536)\n\nIt was discovered that the Intel Data Streaming and Intel Analytics\nAccelerator drivers in the Linux kernel allowed direct access to the\ndevices for unprivileged users and virtual machines. A local attacker could\nuse this to cause a denial of service. (CVE-2024-21823)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel, leading to a null pointer dereference vulnerability. A\nprivileged local attacker could use this to possibly cause a denial of\nservice (system crash). (CVE-2024-24860)\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  - ARM64 architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Core kernel;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Drivers core;\n  - Power management core;\n  - Bus devices;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI driver for MicroSemi Switchtec;\n  - Power supply drivers;\n  - RPMSG subsystem;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - SPMI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - VFIO drivers;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system server daemon;\n  - File systems infrastructure;\n  - Pstore file system;\n  - ReiserFS file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Memory management;\n  - TLS protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Network traffic control;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - AppArmor security module;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2023-52598, CVE-2023-52676, CVE-2023-52609, CVE-2024-26620,\nCVE-2023-52487, CVE-2023-52465, CVE-2023-52473, CVE-2023-52467,\nCVE-2024-26583, CVE-2023-52669, CVE-2023-52664, CVE-2023-52449,\nCVE-2023-52614, CVE-2024-26595, CVE-2023-52611, CVE-2023-52696,\nCVE-2023-52591, CVE-2023-52491, CVE-2024-35839, CVE-2023-52679,\nCVE-2024-26607, CVE-2023-52587, CVE-2023-52469, CVE-2023-52608,\nCVE-2023-52617, CVE-2023-52698, CVE-2024-26673, CVE-2024-35835,\nCVE-2024-26808, CVE-2024-26668, CVE-2023-52626, CVE-2023-52621,\nCVE-2024-35837, CVE-2023-52489, CVE-2023-52597, CVE-2024-26649,\nCVE-2024-26615, CVE-2024-35838, CVE-2023-52693, CVE-2023-52497,\nCVE-2024-35842, CVE-2024-26618, CVE-2024-26610, CVE-2024-26631,\nCVE-2024-26644, CVE-2024-26627, CVE-2023-52677, CVE-2023-52472,\nCVE-2023-52627, CVE-2023-52486, CVE-2023-52632, CVE-2023-52494,\nCVE-2023-52468, CVE-2024-26634, CVE-2023-52588, CVE-2024-26646,\nCVE-2024-26584, CVE-2023-52443, CVE-2023-52691, CVE-2024-26612,\nCVE-2023-52595, CVE-2024-26592, CVE-2024-26623, CVE-2023-52492,\nCVE-2024-26670, CVE-2023-52583, CVE-2023-52681, CVE-2023-52635,\nCVE-2023-52457, CVE-2023-52445, CVE-2024-26629, CVE-2024-26594,\nCVE-2023-52675, CVE-2023-52488, CVE-2023-52446, CVE-2024-26625,\nCVE-2023-52697, CVE-2023-52453, CVE-2023-52498, CVE-2023-52686,\nCVE-2023-52593, CVE-2023-52612, CVE-2023-52687, CVE-2023-52470,\nCVE-2023-52455, CVE-2023-52444, CVE-2024-26608, CVE-2024-26633,\nCVE-2024-26645, CVE-2023-52451, CVE-2023-52456, CVE-2024-26640,\nCVE-2023-52670, CVE-2023-52589, CVE-2024-26598, CVE-2024-35841,\nCVE-2024-26647, CVE-2024-26636, CVE-2023-52680, CVE-2023-52616,\nCVE-2023-52685, CVE-2024-26582, CVE-2024-26638, CVE-2023-52694,\nCVE-2024-35840, CVE-2023-52448, CVE-2023-52623, CVE-2023-52462,\nCVE-2023-52452, CVE-2024-26641, CVE-2023-52683, CVE-2023-52682,\nCVE-2023-52594, CVE-2023-52490, CVE-2023-52493, CVE-2023-52633,\nCVE-2023-52606, CVE-2024-26669, CVE-2023-52584, CVE-2024-26585,\nCVE-2023-52610, CVE-2023-52672, CVE-2023-52450, CVE-2023-52666,\nCVE-2023-52458, CVE-2023-52622, CVE-2023-52674, CVE-2023-52619,\nCVE-2024-26586, CVE-2023-52667, CVE-2024-26616, CVE-2023-52463,\nCVE-2024-26632, CVE-2023-52447, CVE-2023-52692, CVE-2023-52678,\nCVE-2023-52607, CVE-2023-52618, CVE-2023-52464, CVE-2024-26671,\nCVE-2023-52599, CVE-2023-52454, CVE-2023-52495, CVE-2023-52690)\n","status":"published","published":"2024-06-18T23:24:56Z","modified":"2026-11-03T21:17:03.494835513Z","updated_at":"2026-11-03T21:44:03.981358Z"},{"id":"USN-6819-1","title":"linux-azure, linux-azure-6.5, linux-starfive, linux-starfive-6.5 vulnerabilities","description":"Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel\ndid not properly validate H2C PDU data, leading to a null pointer\ndereference vulnerability. A remote attacker could use this to cause a\ndenial of service (system crash). (CVE-2023-6356, CVE-2023-6535,\nCVE-2023-6536)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel, leading to a null pointer dereference vulnerability. A\nprivileged local attacker could use this to possibly cause a denial of\nservice (system crash). (CVE-2024-24860)\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  - ARM64 architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Core kernel;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Drivers core;\n  - Power management core;\n  - Bus devices;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI driver for MicroSemi Switchtec;\n  - Power supply drivers;\n  - RPMSG subsystem;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - SPMI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - VFIO drivers;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system server daemon;\n  - File systems infrastructure;\n  - Pstore file system;\n  - ReiserFS file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Memory management;\n  - TLS protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Network traffic control;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - AppArmor security module;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2023-52612, CVE-2024-26808, CVE-2023-52691, CVE-2023-52618,\nCVE-2023-52463, CVE-2023-52447, CVE-2024-26668, CVE-2023-52454,\nCVE-2024-26670, CVE-2024-26646, CVE-2023-52472, CVE-2024-26586,\nCVE-2023-52681, CVE-2023-52453, CVE-2023-52611, CVE-2023-52622,\nCVE-2024-26641, CVE-2023-52616, CVE-2024-26592, CVE-2023-52606,\nCVE-2024-26620, CVE-2023-52692, CVE-2024-26669, CVE-2023-52623,\nCVE-2023-52588, CVE-2024-26616, CVE-2024-26610, CVE-2024-35839,\nCVE-2023-52490, CVE-2023-52672, CVE-2024-26612, CVE-2023-52617,\nCVE-2023-52697, CVE-2024-26644, CVE-2023-52458, CVE-2023-52598,\nCVE-2024-35841, CVE-2023-52664, CVE-2023-52635, CVE-2023-52676,\nCVE-2023-52669, CVE-2024-26632, CVE-2023-52486, CVE-2024-26625,\nCVE-2023-52608, CVE-2024-26634, CVE-2023-52599, CVE-2024-26618,\nCVE-2024-26640, CVE-2023-52489, CVE-2023-52675, CVE-2023-52678,\nCVE-2024-26583, CVE-2023-52693, CVE-2023-52498, CVE-2024-26649,\nCVE-2023-52670, CVE-2023-52473, CVE-2023-52449, CVE-2023-52667,\nCVE-2023-52467, CVE-2023-52686, CVE-2024-26633, CVE-2023-52666,\nCVE-2024-35840, CVE-2024-26629, CVE-2024-26595, CVE-2023-52593,\nCVE-2023-52687, CVE-2023-52465, CVE-2024-26627, CVE-2023-52493,\nCVE-2023-52491, CVE-2024-26636, CVE-2024-26584, CVE-2023-52587,\nCVE-2023-52597, CVE-2023-52462, CVE-2023-52633, CVE-2023-52696,\nCVE-2024-26585, CVE-2023-52589, CVE-2023-52456, CVE-2023-52470,\nCVE-2024-35838, CVE-2024-26645, CVE-2023-52591, CVE-2023-52464,\nCVE-2023-52609, CVE-2024-26608, CVE-2023-52450, CVE-2023-52584,\nCVE-2023-52469, CVE-2023-52583, CVE-2023-52451, CVE-2023-52495,\nCVE-2023-52626, CVE-2023-52595, CVE-2023-52680, CVE-2023-52632,\nCVE-2024-26582, CVE-2024-35837, CVE-2023-52494, CVE-2023-52614,\nCVE-2023-52443, CVE-2023-52698, CVE-2023-52448, CVE-2024-26615,\nCVE-2023-52452, CVE-2023-52492, CVE-2024-26647, CVE-2023-52468,\nCVE-2023-52594, CVE-2023-52621, CVE-2024-26638, CVE-2024-26594,\nCVE-2024-26673, CVE-2023-52457, CVE-2023-52677, CVE-2023-52607,\nCVE-2024-26623, CVE-2023-52488, CVE-2023-52497, CVE-2023-52445,\nCVE-2024-26607, CVE-2023-52610, CVE-2024-35842, CVE-2023-52690,\nCVE-2023-52683, CVE-2023-52444, CVE-2024-26671, CVE-2023-52455,\nCVE-2023-52679, CVE-2024-26598, CVE-2023-52674, CVE-2023-52627,\nCVE-2023-52619, CVE-2023-52487, CVE-2023-52446, CVE-2024-35835,\nCVE-2023-52682, CVE-2023-52685, CVE-2023-52694, CVE-2024-26631)\n","status":"published","published":"2024-06-07T20:33:17Z","modified":"2026-11-03T21:17:03.729550019Z","updated_at":"2026-11-03T21:44:03.981358Z"},{"id":"USN-6819-3","title":"linux-oem-6.5 vulnerabilities","description":"Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel\ndid not properly validate H2C PDU data, leading to a null pointer\ndereference vulnerability. A remote attacker could use this to cause a\ndenial of service (system crash). (CVE-2023-6356, CVE-2023-6535,\nCVE-2023-6536)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel, leading to a null pointer dereference vulnerability. A\nprivileged local attacker could use this to possibly cause a denial of\nservice (system crash). (CVE-2024-24860)\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  - ARM64 architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Core kernel;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Drivers core;\n  - Power management core;\n  - Bus devices;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI driver for MicroSemi Switchtec;\n  - Power supply drivers;\n  - RPMSG subsystem;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - SPMI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - VFIO drivers;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system server daemon;\n  - File systems infrastructure;\n  - Pstore file system;\n  - ReiserFS file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Memory management;\n  - TLS protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Network traffic control;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - AppArmor security module;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2023-52612, CVE-2024-26808, CVE-2023-52691, CVE-2023-52618,\nCVE-2023-52463, CVE-2023-52447, CVE-2024-26668, CVE-2023-52454,\nCVE-2024-26670, CVE-2024-26646, CVE-2023-52472, CVE-2024-26586,\nCVE-2023-52681, CVE-2023-52453, CVE-2023-52611, CVE-2023-52622,\nCVE-2024-26641, CVE-2023-52616, CVE-2024-26592, CVE-2023-52606,\nCVE-2024-26620, CVE-2023-52692, CVE-2024-26669, CVE-2023-52623,\nCVE-2023-52588, CVE-2024-26616, CVE-2024-26610, CVE-2024-35839,\nCVE-2023-52490, CVE-2023-52672, CVE-2024-26612, CVE-2023-52617,\nCVE-2023-52697, CVE-2024-26644, CVE-2023-52458, CVE-2023-52598,\nCVE-2024-35841, CVE-2023-52664, CVE-2023-52635, CVE-2023-52676,\nCVE-2023-52669, CVE-2024-26632, CVE-2023-52486, CVE-2024-26625,\nCVE-2023-52608, CVE-2024-26634, CVE-2023-52599, CVE-2024-26618,\nCVE-2024-26640, CVE-2023-52489, CVE-2023-52675, CVE-2023-52678,\nCVE-2024-26583, CVE-2023-52693, CVE-2023-52498, CVE-2024-26649,\nCVE-2023-52670, CVE-2023-52473, CVE-2023-52449, CVE-2023-52667,\nCVE-2023-52467, CVE-2023-52686, CVE-2024-26633, CVE-2023-52666,\nCVE-2024-35840, CVE-2024-26629, CVE-2024-26595, CVE-2023-52593,\nCVE-2023-52687, CVE-2023-52465, CVE-2024-26627, CVE-2023-52493,\nCVE-2023-52491, CVE-2024-26636, CVE-2024-26584, CVE-2023-52587,\nCVE-2023-52597, CVE-2023-52462, CVE-2023-52633, CVE-2023-52696,\nCVE-2024-26585, CVE-2023-52589, CVE-2023-52456, CVE-2023-52470,\nCVE-2024-35838, CVE-2024-26645, CVE-2023-52591, CVE-2023-52464,\nCVE-2023-52609, CVE-2024-26608, CVE-2023-52450, CVE-2023-52584,\nCVE-2023-52469, CVE-2023-52583, CVE-2023-52451, CVE-2023-52495,\nCVE-2023-52626, CVE-2023-52595, CVE-2023-52680, CVE-2023-52632,\nCVE-2024-26582, CVE-2024-35837, CVE-2023-52494, CVE-2023-52614,\nCVE-2023-52443, CVE-2023-52698, CVE-2023-52448, CVE-2024-26615,\nCVE-2023-52452, CVE-2023-52492, CVE-2024-26647, CVE-2023-52468,\nCVE-2023-52594, CVE-2023-52621, CVE-2024-26638, CVE-2024-26594,\nCVE-2024-26673, CVE-2023-52457, CVE-2023-52677, CVE-2023-52607,\nCVE-2024-26623, CVE-2023-52488, CVE-2023-52497, CVE-2023-52445,\nCVE-2024-26607, CVE-2023-52610, CVE-2024-35842, CVE-2023-52690,\nCVE-2023-52683, CVE-2023-52444, CVE-2024-26671, CVE-2023-52455,\nCVE-2023-52679, CVE-2024-26598, CVE-2023-52674, CVE-2023-52627,\nCVE-2023-52619, CVE-2023-52487, CVE-2023-52446, CVE-2024-35835,\nCVE-2023-52682, CVE-2023-52685, CVE-2023-52694, CVE-2024-26631)\n","status":"published","published":"2024-06-12T18:10:04Z","modified":"2026-11-03T21:17:04.750848783Z","updated_at":"2026-11-03T21:44:03.981358Z"},{"id":"USN-6819-4","title":"linux-oracle-6.5 vulnerabilities","description":"Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel\ndid not properly validate H2C PDU data, leading to a null pointer\ndereference vulnerability. A remote attacker could use this to cause a\ndenial of service (system crash). (CVE-2023-6356, CVE-2023-6535,\nCVE-2023-6536)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\n\nIt was discovered that a race condition existed in the Bluetooth subsystem\nin the Linux kernel, leading to a null pointer dereference vulnerability. A\nprivileged local attacker could use this to possibly cause a denial of\nservice (system crash). (CVE-2024-24860)\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  - ARM64 architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Core kernel;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Drivers core;\n  - Power management core;\n  - Bus devices;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Multifunction device drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI driver for MicroSemi Switchtec;\n  - Power supply drivers;\n  - RPMSG subsystem;\n  - SCSI drivers;\n  - QCOM SoC drivers;\n  - SPMI drivers;\n  - Thermal drivers;\n  - TTY drivers;\n  - VFIO drivers;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system server daemon;\n  - File systems infrastructure;\n  - Pstore file system;\n  - ReiserFS file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Memory management;\n  - TLS protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Network traffic control;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - AppArmor security module;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2023-52612, CVE-2024-26808, CVE-2023-52691, CVE-2023-52618,\nCVE-2023-52463, CVE-2023-52447, CVE-2024-26668, CVE-2023-52454,\nCVE-2024-26670, CVE-2024-26646, CVE-2023-52472, CVE-2024-26586,\nCVE-2023-52681, CVE-2023-52453, CVE-2023-52611, CVE-2023-52622,\nCVE-2024-26641, CVE-2023-52616, CVE-2024-26592, CVE-2023-52606,\nCVE-2024-26620, CVE-2023-52692, CVE-2024-26669, CVE-2023-52623,\nCVE-2023-52588, CVE-2024-26616, CVE-2024-26610, CVE-2024-35839,\nCVE-2023-52490, CVE-2023-52672, CVE-2024-26612, CVE-2023-52617,\nCVE-2023-52697, CVE-2024-26644, CVE-2023-52458, CVE-2023-52598,\nCVE-2024-35841, CVE-2023-52664, CVE-2023-52635, CVE-2023-52676,\nCVE-2023-52669, CVE-2024-26632, CVE-2023-52486, CVE-2024-26625,\nCVE-2023-52608, CVE-2024-26634, CVE-2023-52599, CVE-2024-26618,\nCVE-2024-26640, CVE-2023-52489, CVE-2023-52675, CVE-2023-52678,\nCVE-2024-26583, CVE-2023-52693, CVE-2023-52498, CVE-2024-26649,\nCVE-2023-52670, CVE-2023-52473, CVE-2023-52449, CVE-2023-52667,\nCVE-2023-52467, CVE-2023-52686, CVE-2024-26633, CVE-2023-52666,\nCVE-2024-35840, CVE-2024-26629, CVE-2024-26595, CVE-2023-52593,\nCVE-2023-52687, CVE-2023-52465, CVE-2024-26627, CVE-2023-52493,\nCVE-2023-52491, CVE-2024-26636, CVE-2024-26584, CVE-2023-52587,\nCVE-2023-52597, CVE-2023-52462, CVE-2023-52633, CVE-2023-52696,\nCVE-2024-26585, CVE-2023-52589, CVE-2023-52456, CVE-2023-52470,\nCVE-2024-35838, CVE-2024-26645, CVE-2023-52591, CVE-2023-52464,\nCVE-2023-52609, CVE-2024-26608, CVE-2023-52450, CVE-2023-52584,\nCVE-2023-52469, CVE-2023-52583, CVE-2023-52451, CVE-2023-52495,\nCVE-2023-52626, CVE-2023-52595, CVE-2023-52680, CVE-2023-52632,\nCVE-2024-26582, CVE-2024-35837, CVE-2023-52494, CVE-2023-52614,\nCVE-2023-52443, CVE-2023-52698, CVE-2023-52448, CVE-2024-26615,\nCVE-2023-52452, CVE-2023-52492, CVE-2024-26647, CVE-2023-52468,\nCVE-2023-52594, CVE-2023-52621, CVE-2024-26638, CVE-2024-26594,\nCVE-2024-26673, CVE-2023-52457, CVE-2023-52677, CVE-2023-52607,\nCVE-2024-26623, CVE-2023-52488, CVE-2023-52497, CVE-2023-52445,\nCVE-2024-26607, CVE-2023-52610, CVE-2024-35842, CVE-2023-52690,\nCVE-2023-52683, CVE-2023-52444, CVE-2024-26671, CVE-2023-52455,\nCVE-2023-52679, CVE-2024-26598, CVE-2023-52674, CVE-2023-52627,\nCVE-2023-52619, CVE-2023-52487, CVE-2023-52446, CVE-2024-35835,\nCVE-2023-52682, CVE-2023-52685, CVE-2023-52694, CVE-2024-26631)\n","status":"published","published":"2024-06-26T13:01:54Z","modified":"2026-11-03T21:17:26.136160432Z","updated_at":"2026-11-03T21:44:00.661154Z"},{"id":"USN-6828-1","title":"linux-intel-iotg-5.15 vulnerabilities","description":"Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux\nkernel contained a race condition during device removal, leading to a use-\nafter-free vulnerability. A physically proximate attacker could possibly\nuse this to cause a denial of service (system crash). (CVE-2023-47233)\n\nIt was discovered that the ATA over Ethernet (AoE) driver in the Linux\nkernel contained a race condition, leading to a use-after-free\nvulnerability. An attacker could use this to cause a denial of service or\npossibly execute arbitrary code. (CVE-2023-6270)\n\nIt was discovered that the Atheros 802.11ac wireless driver did not\nproperly validate certain data structures, leading to a NULL pointer\ndereference. An attacker could possibly use this to cause a denial of\nservice. (CVE-2023-7042)\n\nIt was discovered that the HugeTLB file system component of the Linux\nKernel contained a NULL pointer dereference vulnerability. A privileged\nattacker could possibly use this to to cause a denial of service.\n(CVE-2024-0841)\n\nIt was discovered that the Open vSwitch implementation in the Linux kernel\ncould overflow its stack during recursive action operations under certain\nconditions. A local attacker could use this to cause a denial of service\n(system crash). (CVE-2024-1151)\n\nSander Wiebing, Alvise de Faveri Tron, Herbert Bos, and Cristiano Giuffrida\ndiscovered that the Linux kernel mitigations for the initial Branch History\nInjection vulnerability (CVE-2022-0001) were insufficient for Intel\nprocessors. A local attacker could potentially use this to expose sensitive\ninformation. (CVE-2024-2201)\n\nYuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux\nKernel contained a race condition, leading to a NULL pointer dereference.\nAn attacker could possibly use this to cause a denial of service (system\ncrash). (CVE-2024-22099)\n\nChenyuan Yang discovered that the RDS Protocol implementation in the Linux\nkernel contained an out-of-bounds read vulnerability. An attacker could use\nthis to possibly cause a denial of service (system crash). (CVE-2024-23849)\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  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Core kernel;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - Android drivers;\n  - Power management core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Cryptographic API;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - IIO Magnetometer sensors drivers;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - MMC subsystem;\n  - Network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCI driver for MicroSemi Switchtec;\n  - PHY drivers;\n  - MediaTek PM domains;\n  - Power supply drivers;\n  - SCSI drivers;\n  - SPI subsystem;\n  - Media staging drivers;\n  - TCM subsystem;\n  - USB subsystem;\n  - DesignWare USB3 driver;\n  - Framebuffer layer;\n  - AFS file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system client;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Memory management;\n  - Netfilter;\n  - TLS protocol;\n  - io_uring subsystem;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - Logical Link layer;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netlink;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Packet sockets;\n  - RDS protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - Wireless networking;\n  - Tomoyo security module;\n  - Realtek audio codecs;\n  - USB sound devices;\n(CVE-2024-26910, CVE-2024-27074, CVE-2023-52494, CVE-2023-52594,\nCVE-2024-26915, CVE-2024-26766, CVE-2023-52489, CVE-2024-35845,\nCVE-2024-26846, CVE-2024-26898, CVE-2024-26897, CVE-2024-26826,\nCVE-2024-26798, CVE-2023-52662, CVE-2024-26856, CVE-2023-52608,\nCVE-2024-26782, CVE-2024-27047, CVE-2024-27390, CVE-2024-26610,\nCVE-2024-26804, CVE-2023-52638, CVE-2024-26771, CVE-2024-26752,\nCVE-2024-26585, CVE-2024-26645, CVE-2024-26715, CVE-2024-27028,\nCVE-2024-26809, CVE-2024-26880, CVE-2024-27432, CVE-2024-27065,\nCVE-2024-26717, CVE-2023-52616, CVE-2024-26748, CVE-2024-26795,\nCVE-2024-26671, CVE-2024-26743, CVE-2024-27412, CVE-2024-26802,\nCVE-2024-26733, CVE-2024-26736, CVE-2023-52618, CVE-2024-27046,\nCVE-2024-26688, CVE-2024-26679, CVE-2024-26769, CVE-2024-27051,\nCVE-2024-26603, CVE-2024-26744, CVE-2023-52434, CVE-2024-26697,\nCVE-2024-27075, CVE-2023-52583, CVE-2024-26583, CVE-2024-27403,\nCVE-2024-26907, CVE-2024-26636, CVE-2024-27410, CVE-2023-52530,\nCVE-2024-26840, CVE-2024-26851, CVE-2024-26862, CVE-2023-52640,\nCVE-2024-35829, CVE-2024-26906, CVE-2024-26777, CVE-2024-27419,\nCVE-2024-26664, CVE-2024-26627, CVE-2024-26859, CVE-2023-52486,\nCVE-2023-52652, CVE-2024-26835, CVE-2024-35844, CVE-2024-26702,\nCVE-2024-26635, CVE-2024-26704, CVE-2023-52633, CVE-2024-26816,\nCVE-2024-26894, CVE-2024-26778, CVE-2023-52599, CVE-2024-35828,\nCVE-2024-26776, CVE-2023-52493, CVE-2024-26845, CVE-2024-26594,\nCVE-2024-26885, CVE-2024-26829, CVE-2023-52645, CVE-2024-26695,\nCVE-2023-52615, CVE-2024-26651, CVE-2024-26843, CVE-2023-52606,\nCVE-2024-26675, CVE-2024-26874, CVE-2024-26883, CVE-2024-26772,\nCVE-2024-26673, CVE-2024-26737, CVE-2023-52631, CVE-2024-26640,\nCVE-2023-52598, CVE-2024-26735, CVE-2024-26895, CVE-2024-26592,\nCVE-2023-52492, CVE-2024-26861, CVE-2023-52644, CVE-2024-26920,\nCVE-2024-26877, CVE-2024-26863, CVE-2024-26720, CVE-2024-26722,\nCVE-2024-27045, CVE-2024-27038, CVE-2024-26763, CVE-2024-26833,\nCVE-2024-27417, CVE-2024-26916, CVE-2024-26857, CVE-2024-26875,\nCVE-2024-26606, CVE-2024-27024, CVE-2024-26615, CVE-2023-52614,\nCVE-2023-52641, CVE-2024-26600, CVE-2024-27043, CVE-2023-52635,\nCVE-2024-26787, CVE-2024-26622, CVE-2024-27413, CVE-2024-26791,\nCVE-2023-52622, CVE-2023-52491, CVE-2023-52604, CVE-2024-27037,\nCVE-2024-26881, CVE-2024-26754, CVE-2024-26659, CVE-2024-26663,\nCVE-2024-26747, CVE-2023-52602, CVE-2024-26712, CVE-2024-26839,\nCVE-2024-26749, CVE-2024-26764, CVE-2024-26820, CVE-2024-26882,\nCVE-2024-27039, CVE-2024-27078, CVE-2024-26889, CVE-2024-26870,\nCVE-2024-26788, CVE-2024-26602, CVE-2024-26903, CVE-2024-27044,\nCVE-2024-27073, CVE-2023-52601, CVE-2023-52595, CVE-2024-26707,\nCVE-2024-27415, CVE-2023-52637, CVE-2024-26660, CVE-2024-27414,\nCVE-2024-27054, CVE-2023-52497, CVE-2024-26801, CVE-2023-52435,\nCVE-2023-52620, CVE-2023-52627, CVE-2024-26698, CVE-2023-52597,\nCVE-2024-27077, CVE-2023-52650, CVE-2024-26750, CVE-2024-26852,\nCVE-2024-27053, CVE-2023-52656, CVE-2024-26625, CVE-2024-26779,\nCVE-2024-27431, CVE-2024-26751, CVE-2024-26684, CVE-2024-26803,\nCVE-2024-26593, CVE-2023-52642, CVE-2023-52447, CVE-2024-26790,\nCVE-2024-26825, CVE-2024-26668, CVE-2023-52607, CVE-2024-26872,\nCVE-2024-27030, CVE-2023-52643, CVE-2024-26901, CVE-2024-35830,\nCVE-2024-26855, CVE-2023-52588, CVE-2023-52587, CVE-2024-26891,\nCVE-2024-26644, CVE-2024-26884, CVE-2024-26793, CVE-2024-26805,\nCVE-2024-26584, CVE-2024-27405, CVE-2023-52623, CVE-2024-26608,\nCVE-2024-26878, CVE-2024-27388, CVE-2024-27416, CVE-2024-26685,\nCVE-2024-27034, CVE-2024-26879, CVE-2024-26614, CVE-2024-26792,\nCVE-2023-52617, CVE-2024-26773, CVE-2024-26665, CVE-2024-26641,\nCVE-2023-52619, CVE-2024-35811, CVE-2024-27052, CVE-2024-27076,\nCVE-2024-26838, CVE-2024-26808, CVE-2024-26696, CVE-2024-26676,\nCVE-2024-26689, CVE-2024-26774, CVE-2024-26601, CVE-2023-52498,\nCVE-2024-27436)\n","status":"published","published":"2024-06-11T17:45:43Z","modified":"2026-10-29T20:02:33.692909025Z","updated_at":"2026-11-02T16:58:17.914523Z"}]}}