{"id":"CVE-2024-56655","aliases":["AZL-55300","BELL-CVE-2024-56655","CLSA-2025-1757963029","DEBIAN-CVE-2024-56655","EUVD-2024-53303","GHSA-4xh3-3533-7mmv","MGASA-2025-0030","MGASA-2025-0032","OESA-2025-1204","OESA-2025-1205","UBUNTU-CVE-2024-56655","USN-7379-1","USN-7381-1","USN-7382-1"],"status":"published","title":"netfilter: nf_tables: do not defer rule destruction via call_rcu","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can't be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u003euse counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn't ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u003cTASK\u003e\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We'd still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.","severity":{"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","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00225,"percentile":0.13322,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2024-12-27T15:06:19Z","modified":"2026-11-02T12:03:09Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.76.1-1"],"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.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.6.67","6.12.6"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.6-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.12.6-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","fixed_in":["6.11.0-21.21~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","fixed_in":["6.11.0-1017.17"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.76.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-container","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-container-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-uek-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"python-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.17-2136.338.4.2.el7uek.tuxcare.els2"}]}],"bundled":194},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.67"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.6"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.6-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.6-1"}]}]},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.74-1.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.24-64.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-70.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"Mageia:9","package":"dwarves","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.29-1.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.74-1.mga9"}]}],"bundled":202},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-79.0.0.72.oe2403"}]}],"bundled":22},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-79.0.0.84.oe2403sp1"}]}],"bundled":22},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-21.21~24.04.1"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1017.17"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-21.21~24.04.1"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1"],"bundled":308},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1011.12~24.04.1"}]}],"versions":["6.11.0-1009.10~24.04.1"],"bundled":311},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.0-1017.17"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16"],"bundled":307}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/5146c27b2780aac59876a887a5f4e793b8949862","tags":["web"]},{"url":"https://git.kernel.org/stable/c/2991dc357a28b61c13ed1f7b59e9251e2b4562fb","tags":["web"]},{"url":"https://git.kernel.org/stable/c/b8d8f53e1858178882b881b8c09f94ef0e83bf76","tags":["web"]},{"url":"https://git.kernel.org/stable/c/b0f013bebf94fe7ae75e5a53be2f2bd1cc1841e3","tags":["web"]},{"url":"https://git.kernel.org/stable/c/27f0574253f6c24c8ee4e3f0a685b75ed3a256ed","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/7cf0bd232b565d9852cb25fd094f77254773e048","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/b04df3da1b5c6f6dc7cdccc37941740c078c4043","tags":["Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56655","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-4xh3-3533-7mmv"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-56655","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/oraclelinux7els/CLSA-2025-1757963029.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48829","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53034","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-28956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38541","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21993","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22045","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23140","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23158","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37765","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37766","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37781","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37789","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37792","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37797","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37810","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37829","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37841","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37850","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37909","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37949","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38024","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38034","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38108","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38174","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38181","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38184","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38203","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38213","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38219","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38222","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38326","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38328","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38332","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38336","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38337","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38415","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38416","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38420","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38424","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38430","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38637","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56655.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-2024-56655","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2025-0030.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33961","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.66","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.67","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.68","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.69","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.70","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.71","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.72","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.73","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.74","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2025-0032.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33968","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53164","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-54680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56607","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56658","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56717","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56767","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57792","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57804","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21704","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1205","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-56655","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56655","tags":["report"]},{"url":"https://git.kernel.org/linus/b04df3da1b5c6f6dc7cdccc37941740c078c4043","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7379-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7380-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7381-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7382-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7379-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-36476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-39282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-43098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-45828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-48881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-51729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-52319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-52332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-54683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-55916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56564","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21655","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-0927","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-56655","title":"netfilter: nf_tables: do not defer rule destruction via call_rcu","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can't be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u003euse counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn't ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u003cTASK\u003e\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We'd still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.","status":"published","published":"2024-12-27T15:06:19.033Z","modified":"2026-08-05T11:45:53.066Z","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","assessor":"cna"}],"updated_at":"2026-11-02T14:33:57.983942Z"}],"euvd":[{"id":"EUVD-2024-53303","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can't be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u003euse counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn't ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u003cTASK\u003e\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We'd still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.","status":"published","published":"2024-12-27T15:06:19Z","modified":"2026-08-05T11:45:53Z","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-02T18:02:14.928856Z"}],"ghsa":[{"id":"GHSA-4xh3-3533-7mmv","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can't be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u003euse counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn't ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u003cTASK\u003e\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We'd still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.","status":"published","published":"2024-12-27T15:31:56Z","modified":"2025-06-04T15:31:27Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:02:33.897794Z"}],"nvd":[{"id":"CVE-2024-56655","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can't be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u003euse counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn't ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u003cTASK\u003e\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We'd still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.","status":"published","published":"2024-12-27T15:15:25.343Z","modified":"2026-08-04T11:22:18.72Z","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","assessor":"secondary"},{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"updated_at":"2026-11-02T14:10:41.091507Z"}],"osv":[{"id":"AZL-55300","title":"CVE-2024-56655 affecting package kernel for versions less than 6.6.76.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can't be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u003euse counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn't ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u003cTASK\u003e\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We'd still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.","status":"published","published":"2024-12-27T15:15:25Z","modified":"2026-04-21T04:54:00.050007Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:06.879785Z"},{"id":"BELL-CVE-2024-56655","status":"published","published":"2024-12-28T05:57:00.899987Z","modified":"2026-06-25T07:16:50.537456845Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:20.963569Z"},{"id":"CVE-2024-56655","title":"netfilter: nf_tables: do not defer rule destruction via call_rcu","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can't be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u003euse counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn't ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u003cTASK\u003e\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We'd still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.","status":"published","published":"2024-12-27T15:06:19.033Z","modified":"2026-10-28T02:31:01.754955412Z","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:44:44.777182Z"},{"id":"DEBIAN-CVE-2024-56655","description":"In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: do not defer rule destruction via call_rcu  nf_tables_chain_destroy can sleep, it can't be used from call_rcu callbacks.  Moreover, nf_tables_rule_release() is only safe for error unwinding, while transaction mutex is held and the to-be-desroyed rule was not exposed to either dataplane or dumps, as it deactives+frees without the required synchronize_rcu() in-between.  nft_rule_expr_deactivate() callbacks will change -\u003euse counters of other chains/sets, see e.g. nft_lookup .deactivate callback, these must be serialized via transaction mutex.  Also add a few lockdep asserts to make this more explicit.  Calling synchronize_rcu() isn't ideal, but fixing this without is hard and way more intrusive.  As-is, we can get:  WARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x.. Workqueue: events nf_tables_trans_destroy_work RIP: 0010:nft_set_destroy+0x3fe/0x5c0 Call Trace:  \u003cTASK\u003e  nf_tables_trans_destroy_work+0x6b7/0xad0  process_one_work+0x64a/0xce0  worker_thread+0x613/0x10d0  In case the synchronize_rcu becomes an issue, we can explore alternatives.  One way would be to allocate nft_trans_rule objects + one nft_trans_chain object, deactivate the rules + the chain and then defer the freeing to the nft destroy workqueue.  We'd still need to keep the synchronize_rcu path as a fallback to handle -ENOMEM corner cases though.","status":"published","published":"2024-12-27T15:15:25.343Z","modified":"2026-11-02T12:03:09.903536989Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:44.429177Z"},{"id":"OESA-2025-1204","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Prevent tailcall infinite loop caused by freplace\n\nThere is a potential infinite loop issue that can occur when using a\ncombination of tail calls and freplace.\n\nIn an upcoming selftest, the attach target for entry_freplace of\ntailcall_freplace.c is subprog_tc of tc_bpf2bpf.c, while the tail call in\nentry_freplace leads to entry_tc. This results in an infinite loop:\n\nentry_tc -\u0026gt; subprog_tc -\u0026gt; entry_freplace --tailcall-\u0026gt; entry_tc.\n\nThe problem arises because the tail_call_cnt in entry_freplace resets to\nzero each time entry_freplace is executed, causing the tail call mechanism\nto never terminate, eventually leading to a kernel panic.\n\nTo fix this issue, the solution is twofold:\n\n1. Prevent updating a program extended by an freplace program to a\n   prog_array map.\n2. Prevent extending a program that is already part of a prog_array map\n   with an freplace program.\n\nThis ensures that:\n\n* If a program or its subprogram has been extended by an freplace program,\n  it can no longer be updated to a prog_array map.\n* If a program has been added to a prog_array map, neither it nor its\n  subprograms can be extended by an freplace program.\n\nMoreover, an extension program should not be tailcalled. As such, return\n-EINVAL if the program has a type of BPF_PROG_TYPE_EXT when adding it to a\nprog_array map.\n\nAdditionally, fix a minor code style issue by replacing eight spaces with a\ntab for proper formatting.(CVE-2024-47794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/thp: fix deferred split unqueue naming and locking\n\nRecent changes are putting more pressure on THP deferred split queues:\nunder load revealing long-standing races, causing list_del corruptions,\n\u0026quot;Bad page state\u0026quot;s and worse (I keep BUGs in both of those, so usually\ndon\u0026apos;t get to see how badly they end up without).  The relevant recent\nchanges being 6.8\u0026apos;s mTHP, 6.10\u0026apos;s mTHP swapout, and 6.12\u0026apos;s mTHP swapin,\nimproved swap allocation, and underused THP splitting.\n\nBefore fixing locking: rename misleading folio_undo_large_rmappable(),\nwhich does not undo large_rmappable, to folio_unqueue_deferred_split(),\nwhich is what it does.  But that and its out-of-line __callee are mm\ninternals of very limited usability: add comment and WARN_ON_ONCEs to\ncheck usage; and return a bool to say if a deferred split was unqueued,\nwhich can then be used in WARN_ON_ONCEs around safety checks (sparing\ncallers the arcane conditionals in __folio_unqueue_deferred_split()).\n\nJust omit the folio_unqueue_deferred_split() from free_unref_folios(), all\nof whose callers now call it beforehand (and if any forget then bad_page()\nwill tell) - except for its caller put_pages_list(), which itself no\nlonger has any callers (and will be deleted separately).\n\nSwapout: mem_cgroup_swapout() has been resetting folio-\u0026gt;memcg_data 0\nwithout checking and unqueueing a THP folio from deferred split list;\nwhich is unfortunate, since the split_queue_lock depends on the memcg\n(when memcg is enabled); so swapout has been unqueueing such THPs later,\nwhen freeing the folio, using the pgdat\u0026apos;s lock instead: potentially\ncorrupting the memcg\u0026apos;s list.  __remove_mapping() has frozen refcount to 0\nhere, so no problem with calling folio_unqueue_deferred_split() before\nresetting memcg_data.\n\nThat goes back to 5.4 commit 87eaceb3faa5 (\u0026quot;mm: thp: make deferred split\nshrinker memcg aware\u0026quot;): which included a check on swapcache before adding\nto deferred queue, but no check on deferred queue before adding THP to\nswapcache.  That worked fine with the usual sequence of events in reclaim\n(though there were a couple of rare ways in which a THP on deferred queue\ncould have been swapped out), but 6.12 commit dafff3f4c850 (\u0026quot;mm: split\nunderused THPs\u0026quot;) avoids splitting underused THPs in reclaim, which makes\nswapcache THPs on deferred queue commonplace.\n\nKeep the check on swapcache before adding to deferred queue?  Yes: it is\nno longer essential, but preserves the existing behaviour, and is likely\nto be a worthwhile optimization (vmstat showed much more traffic on the\nqueue under swapping load if the check was removed); update its comment.\n\nMemcg-v1 move (deprecated): mem_cgroup_move_account() has been changing\nfolio-\u0026gt;memcg_data without checking and unqueueing a THP folio from the\ndeferred list, sometimes corrupting \u0026quot;from\u0026quot; memcg\u0026apos;s list, like swapout. \nRefcount is non-zero here, so folio_unqueue_deferred_split() can only be\nused in a WARN_ON_ONCE to validate the fix, which must be done earlier:\nmem_cgroup_move_charge_pte_range() first try to split the THP (splitting\nof course unqueues), or skip it if that fails.  Not ideal, but moving\ncharge has been requested, and khugepaged should repair the THP later:\nnobody wants new custom unqueueing code just for this deprecated case.\n\nThe 87eaceb3faa5 commit did have the code to move from one deferred list\nto another (but was not conscious of its unsafety while refcount non-0);\nbut that was removed by 5.6 commit fac0516b5534 (\u0026quot;mm: thp: don\u0026apos;t need care\ndeferred split queue in memcg charge move path\u0026quot;), which argued that the\nexistence of a PMD mapping guarantees that the THP cannot be on a deferred\nlist.  As above, false in rare cases, and now commonly false.\n\nBackport to 6.11 should be straightforward.  Earlier backports must take\ncare that other _deferred_list fixes and dependencies are included.  There\nis not a strong case for backports, but they can fix cornercases.(CVE-2024-53079)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sched: fix ordering of qlen adjustment\n\nChanges to sch-\u0026gt;q.qlen around qdisc_tree_reduce_backlog() need to happen\n_before_ a call to said function because otherwise it may fail to notify\nparent qdiscs when the child is about to become empty.(CVE-2024-53164)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen/netfront: fix crash when removing device\n\nWhen removing a netfront device directly after a suspend/resume cycle\nit might happen that the queues have not been setup again, causing a\ncrash during the attempt to stop the queues another time.\n\nFix that by checking the queues are existing before trying to stop\nthem.\n\nThis is XSA-465 / CVE-2024-53240.(CVE-2024-53240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix TCP timers deadlock after rmmod\n\nCommit ef7134c7fc48 (\u0026quot;smb: client: Fix use-after-free of network namespace.\u0026quot;)\nfixed a netns UAF by manually enabled socket refcounting\n(sk-\u0026gt;sk_net_refcnt=1 and sock_inuse_add(net, 1)).\n\nThe reason the patch worked for that bug was because we now hold\nreferences to the netns (get_net_track() gets a ref internally)\nand they\u0026apos;re properly released (internally, on __sk_destruct()),\nbut only because sk-\u0026gt;sk_net_refcnt was set.\n\nProblem:\n(this happens regardless of CONFIG_NET_NS_REFCNT_TRACKER and regardless\nif init_net or other)\n\nSetting sk-\u0026gt;sk_net_refcnt=1 *manually* and *after* socket creation is not\nonly out of cifs scope, but also technically wrong -- it\u0026apos;s set conditionally\nbased on user (=1) vs kernel (=0) sockets.  And net/ implementations\nseem to base their user vs kernel space operations on it.\n\ne.g. upon TCP socket close, the TCP timers are not cleared because\nsk-\u0026gt;sk_net_refcnt=1:\n(cf. commit 151c9c724d05 (\u0026quot;tcp: properly terminate timers for kernel sockets\u0026quot;))\n\nnet/ipv4/tcp.c:\n    void tcp_close(struct sock *sk, long timeout)\n    {\n    \tlock_sock(sk);\n    \t__tcp_close(sk, timeout);\n    \trelease_sock(sk);\n    \tif (!sk-\u0026gt;sk_net_refcnt)\n    \t\tinet_csk_clear_xmit_timers_sync(sk);\n    \tsock_put(sk);\n    }\n\nWhich will throw a lockdep warning and then, as expected, deadlock on\ntcp_write_timer().\n\nA way to reproduce this is by running the reproducer from ef7134c7fc48\nand then \u0026apos;rmmod cifs\u0026apos;.  A few seconds later, the deadlock/lockdep\nwarning shows up.\n\nFix:\nWe shouldn\u0026apos;t mess with socket internals ourselves, so do not set\nsk_net_refcnt manually.\n\nAlso change __sock_create() to sock_create_kern() for explicitness.\n\nAs for non-init_net network namespaces, we deal with it the best way\nwe can -- hold an extra netns reference for server-\u0026gt;ssocket and drop it\nwhen it\u0026apos;s released.  This ensures that the netns still exists whenever\nwe need to create/destroy server-\u0026gt;ssocket, but is not directly tied to\nit.(CVE-2024-54680)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: tun: fix tun_napi_alloc_frags()\n\nsyzbot reported the following crash [1]\n\nIssue came with the blamed commit. Instead of going through\nall the iov components, we keep using the first one\nand end up with a malformed skb.\n\n[1]\n\nkernel BUG at net/core/skbuff.c:2849 !\nOops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 0 UID: 0 PID: 6230 Comm: syz-executor132 Not tainted 6.13.0-rc1-syzkaller-00407-g96b6fcc0ee41 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024\n RIP: 0010:__pskb_pull_tail+0x1568/0x1570 net/core/skbuff.c:2848\nCode: 38 c1 0f 8c 32 f1 ff ff 4c 89 f7 e8 92 96 74 f8 e9 25 f1 ff ff e8 e8 ae 09 f8 48 8b 5c 24 08 e9 eb fb ff ff e8 d9 ae 09 f8 90 \u0026lt;0f\u0026gt; 0b 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90\nRSP: 0018:ffffc90004cbef30 EFLAGS: 00010293\nRAX: ffffffff8995c347 RBX: 00000000fffffff2 RCX: ffff88802cf45a00\nRDX: 0000000000000000 RSI: 00000000fffffff2 RDI: 0000000000000000\nRBP: ffff88807df0c06a R08: ffffffff8995b084 R09: 1ffff1100fbe185c\nR10: dffffc0000000000 R11: ffffed100fbe185d R12: ffff888076e85d50\nR13: ffff888076e85c80 R14: ffff888076e85cf4 R15: ffff888076e85c80\nFS:  00007f0dca6ea6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f0dca6ead58 CR3: 00000000119da000 CR4: 00000000003526f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_cow_data+0x2da/0xcb0 net/core/skbuff.c:5284\n  tipc_aead_decrypt net/tipc/crypto.c:894 [inline]\n  tipc_crypto_rcv+0x402/0x24e0 net/tipc/crypto.c:1844\n  tipc_rcv+0x57e/0x12a0 net/tipc/node.c:2109\n  tipc_l2_rcv_msg+0x2bd/0x450 net/tipc/bearer.c:668\n  __netif_receive_skb_list_ptype net/core/dev.c:5720 [inline]\n  __netif_receive_skb_list_core+0x8b7/0x980 net/core/dev.c:5762\n  __netif_receive_skb_list net/core/dev.c:5814 [inline]\n  netif_receive_skb_list_internal+0xa51/0xe30 net/core/dev.c:5905\n  gro_normal_list include/net/gro.h:515 [inline]\n  napi_complete_done+0x2b5/0x870 net/core/dev.c:6256\n  napi_complete include/linux/netdevice.h:567 [inline]\n  tun_get_user+0x2ea0/0x4890 drivers/net/tun.c:1982\n  tun_chr_write_iter+0x10d/0x1f0 drivers/net/tun.c:2057\n do_iter_readv_writev+0x600/0x880\n  vfs_writev+0x376/0xba0 fs/read_write.c:1050\n  do_writev+0x1b6/0x360 fs/read_write.c:1096\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-56372)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask()\n\nWhen I try to manually set bitrates:\n\niw wlan0 set bitrates legacy-2.4 1\n\nI get sleeping from invalid context error, see below. Fix that by switching to\nuse recently introduced ieee80211_iterate_stations_mtx().\n\nDo note that WCN6855 firmware is still crashing, I\u0026apos;m not sure if that firmware\neven supports bitrate WMI commands and should we consider disabling\nath12k_mac_op_set_bitrate_mask() for WCN6855? But that\u0026apos;s for another patch.\n\nBUG: sleeping function called from invalid context at drivers/net/wireless/ath/ath12k/wmi.c:420\nin_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 2236, name: iw\npreempt_count: 0, expected: 0\nRCU nest depth: 1, expected: 0\n3 locks held by iw/2236:\n #0: ffffffffabc6f1d8 (cb_lock){++++}-{3:3}, at: genl_rcv+0x14/0x40\n #1: ffff888138410810 (\u0026amp;rdev-\u0026gt;wiphy.mtx){+.+.}-{3:3}, at: nl80211_pre_doit+0x54d/0x800 [cfg80211]\n #2: ffffffffab2cfaa0 (rcu_read_lock){....}-{1:2}, at: ieee80211_iterate_stations_atomic+0x2f/0x200 [mac80211]\nCPU: 3 UID: 0 PID: 2236 Comm: iw Not tainted 6.11.0-rc7-wt-ath+ #1772\nHardware name: Intel(R) Client Systems NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0067.2021.0528.1339 05/28/2021\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xa4/0xe0\n dump_stack+0x10/0x20\n __might_resched+0x363/0x5a0\n ? __alloc_skb+0x165/0x340\n __might_sleep+0xad/0x160\n ath12k_wmi_cmd_send+0xb1/0x3d0 [ath12k]\n ? ath12k_wmi_init_wcn7850+0xa40/0xa40 [ath12k]\n ? __netdev_alloc_skb+0x45/0x7b0\n ? __asan_memset+0x39/0x40\n ? ath12k_wmi_alloc_skb+0xf0/0x150 [ath12k]\n ? reacquire_held_locks+0x4d0/0x4d0\n ath12k_wmi_set_peer_param+0x340/0x5b0 [ath12k]\n ath12k_mac_disable_peer_fixed_rate+0xa3/0x110 [ath12k]\n ? ath12k_mac_vdev_stop+0x4f0/0x4f0 [ath12k]\n ieee80211_iterate_stations_atomic+0xd4/0x200 [mac80211]\n ath12k_mac_op_set_bitrate_mask+0x5d2/0x1080 [ath12k]\n ? ath12k_mac_vif_chan+0x320/0x320 [ath12k]\n drv_set_bitrate_mask+0x267/0x470 [mac80211]\n ieee80211_set_bitrate_mask+0x4cc/0x8a0 [mac80211]\n ? __this_cpu_preempt_check+0x13/0x20\n nl80211_set_tx_bitrate_mask+0x2bc/0x530 [cfg80211]\n ? nl80211_parse_tx_bitrate_mask+0x2320/0x2320 [cfg80211]\n ? trace_contention_end+0xef/0x140\n ? rtnl_unlock+0x9/0x10\n ? nl80211_pre_doit+0x557/0x800 [cfg80211]\n genl_family_rcv_msg_doit+0x1f0/0x2e0\n ? genl_family_rcv_msg_attrs_parse.isra.0+0x250/0x250\n ? ns_capable+0x57/0xd0\n genl_family_rcv_msg+0x34c/0x600\n ? genl_family_rcv_msg_dumpit+0x310/0x310\n ? __lock_acquire+0xc62/0x1de0\n ? he_set_mcs_mask.isra.0+0x8d0/0x8d0 [cfg80211]\n ? nl80211_parse_tx_bitrate_mask+0x2320/0x2320 [cfg80211]\n ? cfg80211_external_auth_request+0x690/0x690 [cfg80211]\n genl_rcv_msg+0xa0/0x130\n netlink_rcv_skb+0x14c/0x400\n ? genl_family_rcv_msg+0x600/0x600\n ? netlink_ack+0xd70/0xd70\n ? rwsem_optimistic_spin+0x4f0/0x4f0\n ? genl_rcv+0x14/0x40\n ? down_read_killable+0x580/0x580\n ? netlink_deliver_tap+0x13e/0x350\n ? __this_cpu_preempt_check+0x13/0x20\n genl_rcv+0x23/0x40\n netlink_unicast+0x45e/0x790\n ? netlink_attachskb+0x7f0/0x7f0\n netlink_sendmsg+0x7eb/0xdb0\n ? netlink_unicast+0x790/0x790\n ? __this_cpu_preempt_check+0x13/0x20\n ? selinux_socket_sendmsg+0x31/0x40\n ? netlink_unicast+0x790/0x790\n __sock_sendmsg+0xc9/0x160\n ____sys_sendmsg+0x620/0x990\n ? kernel_sendmsg+0x30/0x30\n ? __copy_msghdr+0x410/0x410\n ? __kasan_check_read+0x11/0x20\n ? mark_lock+0xe6/0x1470\n ___sys_sendmsg+0xe9/0x170\n ? copy_msghdr_from_user+0x120/0x120\n ? __lock_acquire+0xc62/0x1de0\n ? do_fault_around+0x2c6/0x4e0\n ? do_user_addr_fault+0x8c1/0xde0\n ? reacquire_held_locks+0x220/0x4d0\n ? do_user_addr_fault+0x8c1/0xde0\n ? __kasan_check_read+0x11/0x20\n ? __fdget+0x4e/0x1d0\n ? sockfd_lookup_light+0x1a/0x170\n __sys_sendmsg+0xd2/0x180\n ? __sys_sendmsg_sock+0x20/0x20\n ? reacquire_held_locks+0x4d0/0x4d0\n ? debug_smp_processor_id+0x17/0x20\n __x64_sys_sendmsg+0x72/0xb0\n ? lockdep_hardirqs_on+0x7d/0x100\n x64_sys_call+0x894/0x9f0\n do_syscall_64+0x64/0x130\n entry_SYSCALL_64_after_\n---truncated---(CVE-2024-56607)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can\u0026apos;t be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u0026gt;use counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn\u0026apos;t ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We\u0026apos;d still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.(CVE-2024-56655)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: defer final \u0026apos;struct net\u0026apos; free in netns dismantle\n\nIlya reported a slab-use-after-free in dst_destroy [1]\n\nIssue is in xfrm6_net_init() and xfrm4_net_init() :\n\nThey copy xfrm[46]_dst_ops_template into net-\u0026gt;xfrm.xfrm[46]_dst_ops.\n\nBut net structure might be freed before all the dst callbacks are\ncalled. So when dst_destroy() calls later :\n\nif (dst-\u0026gt;ops-\u0026gt;destroy)\n    dst-\u0026gt;ops-\u0026gt;destroy(dst);\n\ndst-\u0026gt;ops points to the old net-\u0026gt;xfrm.xfrm[46]_dst_ops, which has been freed.\n\nSee a relevant issue fixed in :\n\nac888d58869b (\u0026quot;net: do not delay dst_entries_add() in dst_release()\u0026quot;)\n\nA fix is to queue the \u0026apos;struct net\u0026apos; to be freed after one\nanother cleanup_net() round (and existing rcu_barrier())\n\n[1]\n\nBUG: KASAN: slab-use-after-free in dst_destroy (net/core/dst.c:112)\nRead of size 8 at addr ffff8882137ccab0 by task swapper/37/0\nDec 03 05:46:18 kernel:\nCPU: 37 UID: 0 PID: 0 Comm: swapper/37 Kdump: loaded Not tainted 6.12.0 #67\nHardware name: Red Hat KVM/RHEL, BIOS 1.16.1-1.el9 04/01/2014\nCall Trace:\n \u0026lt;IRQ\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:124)\nprint_address_description.constprop.0 (mm/kasan/report.c:378)\n? dst_destroy (net/core/dst.c:112)\nprint_report (mm/kasan/report.c:489)\n? dst_destroy (net/core/dst.c:112)\n? kasan_addr_to_slab (mm/kasan/common.c:37)\nkasan_report (mm/kasan/report.c:603)\n? dst_destroy (net/core/dst.c:112)\n? rcu_do_batch (kernel/rcu/tree.c:2567)\ndst_destroy (net/core/dst.c:112)\nrcu_do_batch (kernel/rcu/tree.c:2567)\n? __pfx_rcu_do_batch (kernel/rcu/tree.c:2491)\n? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4339 kernel/locking/lockdep.c:4406)\nrcu_core (kernel/rcu/tree.c:2825)\nhandle_softirqs (kernel/softirq.c:554)\n__irq_exit_rcu (kernel/softirq.c:589 kernel/softirq.c:428 kernel/softirq.c:637)\nirq_exit_rcu (kernel/softirq.c:651)\nsysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1049 arch/x86/kernel/apic/apic.c:1049)\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\nasm_sysvec_apic_timer_interrupt (./arch/x86/include/asm/idtentry.h:702)\nRIP: 0010:default_idle (./arch/x86/include/asm/irqflags.h:37 ./arch/x86/include/asm/irqflags.h:92 arch/x86/kernel/process.c:743)\nCode: 00 4d 29 c8 4c 01 c7 4c 29 c2 e9 6e ff ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 90 0f 00 2d c7 c9 27 00 fb f4 \u0026lt;fa\u0026gt; c3 cc cc cc cc 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 90\nRSP: 0018:ffff888100d2fe00 EFLAGS: 00000246\nRAX: 00000000001870ed RBX: 1ffff110201a5fc2 RCX: ffffffffb61a3e46\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffb3d4d123\nRBP: 0000000000000000 R08: 0000000000000001 R09: ffffed11c7e1835d\nR10: ffff888e3f0c1aeb R11: 0000000000000000 R12: 0000000000000000\nR13: ffff888100d20000 R14: dffffc0000000000 R15: 0000000000000000\n? ct_kernel_exit.constprop.0 (kernel/context_tracking.c:148)\n? cpuidle_idle_call (kernel/sched/idle.c:186)\ndefault_idle_call (./include/linux/cpuidle.h:143 kernel/sched/idle.c:118)\ncpuidle_idle_call (kernel/sched/idle.c:186)\n? __pfx_cpuidle_idle_call (kernel/sched/idle.c:168)\n? lock_release (kernel/locking/lockdep.c:467 kernel/locking/lockdep.c:5848)\n? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4347 kernel/locking/lockdep.c:4406)\n? tsc_verify_tsc_adjust (arch/x86/kernel/tsc_sync.c:59)\ndo_idle (kernel/sched/idle.c:326)\ncpu_startup_entry (kernel/sched/idle.c:423 (discriminator 1))\nstart_secondary (arch/x86/kernel/smpboot.c:202 arch/x86/kernel/smpboot.c:282)\n? __pfx_start_secondary (arch/x86/kernel/smpboot.c:232)\n? soft_restart_cpu (arch/x86/kernel/head_64.S:452)\ncommon_startup_64 (arch/x86/kernel/head_64.S:414)\n \u0026lt;/TASK\u0026gt;\nDec 03 05:46:18 kernel:\nAllocated by task 12184:\nkasan_save_stack (mm/kasan/common.c:48)\nkasan_save_track (./arch/x86/include/asm/current.h:49 mm/kasan/common.c:60 mm/kasan/common.c:69)\n__kasan_slab_alloc (mm/kasan/common.c:319 mm/kasan/common.c:345)\nkmem_cache_alloc_noprof (mm/slub.c:4085 mm/slub.c:4134 mm/slub.c:4141)\ncopy_net_ns (net/core/net_namespace.c:421 net/core/net_namespace.c:480)\ncreate_new_namespaces\n---truncated---(CVE-2024-56658)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: lapb: increase LAPB_HEADER_LEN\n\nIt is unclear if net/lapb code is supposed to be ready for 8021q.\n\nWe can at least avoid crashes like the following :\n\nskbuff: skb_under_panic: text:ffffffff8aabe1f6 len:24 put:20 head:ffff88802824a400 data:ffff88802824a3fe tail:0x16 end:0x140 dev:nr0.2\n------------[ cut here ]------------\n kernel BUG at net/core/skbuff.c:206 !\nOops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 1 UID: 0 PID: 5508 Comm: dhcpcd Not tainted 6.12.0-rc7-syzkaller-00144-g66418447d27b #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024\n RIP: 0010:skb_panic net/core/skbuff.c:206 [inline]\n RIP: 0010:skb_under_panic+0x14b/0x150 net/core/skbuff.c:216\nCode: 0d 8d 48 c7 c6 2e 9e 29 8e 48 8b 54 24 08 8b 0c 24 44 8b 44 24 04 4d 89 e9 50 41 54 41 57 41 56 e8 1a 6f 37 02 48 83 c4 20 90 \u0026lt;0f\u0026gt; 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3\nRSP: 0018:ffffc90002ddf638 EFLAGS: 00010282\nRAX: 0000000000000086 RBX: dffffc0000000000 RCX: 7a24750e538ff600\nRDX: 0000000000000000 RSI: 0000000000000201 RDI: 0000000000000000\nRBP: ffff888034a86650 R08: ffffffff8174b13c R09: 1ffff920005bbe60\nR10: dffffc0000000000 R11: fffff520005bbe61 R12: 0000000000000140\nR13: ffff88802824a400 R14: ffff88802824a3fe R15: 0000000000000016\nFS:  00007f2a5990d740(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c2631fd CR3: 0000000029504000 CR4: 00000000003526f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_push+0xe5/0x100 net/core/skbuff.c:2636\n  nr_header+0x36/0x320 net/netrom/nr_dev.c:69\n  dev_hard_header include/linux/netdevice.h:3148 [inline]\n  vlan_dev_hard_header+0x359/0x480 net/8021q/vlan_dev.c:83\n  dev_hard_header include/linux/netdevice.h:3148 [inline]\n  lapbeth_data_transmit+0x1f6/0x2a0 drivers/net/wan/lapbether.c:257\n  lapb_data_transmit+0x91/0xb0 net/lapb/lapb_iface.c:447\n  lapb_transmit_buffer+0x168/0x1f0 net/lapb/lapb_out.c:149\n lapb_establish_data_link+0x84/0xd0\n lapb_device_event+0x4e0/0x670\n  notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93\n __dev_notify_flags+0x207/0x400\n  dev_change_flags+0xf0/0x1a0 net/core/dev.c:8922\n  devinet_ioctl+0xa4e/0x1aa0 net/ipv4/devinet.c:1188\n  inet_ioctl+0x3d7/0x4f0 net/ipv4/af_inet.c:1003\n  sock_do_ioctl+0x158/0x460 net/socket.c:1227\n  sock_ioctl+0x626/0x8e0 net/socket.c:1346\n  vfs_ioctl fs/ioctl.c:51 [inline]\n  __do_sys_ioctl fs/ioctl.c:907 [inline]\n  __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83(CVE-2024-56659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic()\n\nPackets injected by the CPU should have a SRC_PORT field equal to the\nCPU port module index in the Analyzer block (ocelot-\u0026gt;num_phys_ports).\n\nThe blamed commit copied the ocelot_ifh_set_basic() call incorrectly\nfrom ocelot_xmit_common() in net/dsa/tag_ocelot.c. Instead of calling\nwith \u0026quot;x\u0026quot;, it calls with BIT_ULL(x), but the field is not a port mask,\nbut rather a single port index.\n\n[ side note: this is the technical debt of code duplication :( ]\n\nThe error used to be silent and doesn\u0026apos;t appear to have other\nuser-visible manifestations, but with new changes in the packing\nlibrary, it now fails loudly as follows:\n\n------------[ cut here ]------------\nCannot store 0x40 inside bits 46-43 - will truncate\nsja1105 spi2.0: xmit timed out\nWARNING: CPU: 1 PID: 102 at lib/packing.c:98 __pack+0x90/0x198\nsja1105 spi2.0: timed out polling for tstamp\nCPU: 1 UID: 0 PID: 102 Comm: felix_xmit\nTainted: G        W        N 6.13.0-rc1-00372-gf706b85d972d-dirty #2605\nCall trace:\n __pack+0x90/0x198 (P)\n __pack+0x90/0x198 (L)\n packing+0x78/0x98\n ocelot_ifh_set_basic+0x260/0x368\n ocelot_port_inject_frame+0xa8/0x250\n felix_port_deferred_xmit+0x14c/0x258\n kthread_worker_fn+0x134/0x350\n kthread+0x114/0x138\n\nThe code path pertains to the ocelot switchdev driver and to the felix\nsecondary DSA tag protocol, ocelot-8021q. Here seen with ocelot-8021q.\n\nThe messenger (packing) is not really to blame, so fix the original\ncommit instead.(CVE-2024-56717)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset\n\nThe at_xdmac_memset_create_desc may return NULL, which will lead to a\nnull pointer dereference. For example, the len input is error, or the\natchan-\u0026gt;free_descs_list is empty and memory is exhausted. Therefore, add\ncheck to avoid this.(CVE-2024-56767)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: gpio-charger: Fix set charge current limits\n\nFix set charge current limits for devices which allow to set the lowest\ncharge current limit to be greater zero. If requested charge current limit\nis below lowest limit, the index equals current_limit_map_size which leads\nto accessing memory beyond allocated memory.(CVE-2024-57792)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs\n\nThe driver, through the SAS transport, exposes a sysfs interface to\nenable/disable PHYs in a controller/expander setup.  When multiple PHYs\nare disabled and enabled in rapid succession, the persistent and current\nconfig pages related to SAS IO unit/SAS Expander pages could get\ncorrupted.\n\nUse separate memory for each config request.(CVE-2024-57804)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: megaraid_sas: Fix for a potential deadlock\n\nThis fixes a \u0026apos;possible circular locking dependency detected\u0026apos; warning\n      CPU0                    CPU1\n      ----                    ----\n lock(\u0026amp;instance-\u0026gt;reset_mutex);\n                              lock(\u0026amp;shost-\u0026gt;scan_mutex);\n                              lock(\u0026amp;instance-\u0026gt;reset_mutex);\n lock(\u0026amp;shost-\u0026gt;scan_mutex);\n\nFix this by temporarily releasing the reset_mutex.(CVE-2024-57807)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Have process_string() also allow arrays\n\nIn order to catch a common bug where a TRACE_EVENT() TP_fast_assign()\nassigns an address of an allocated string to the ring buffer and then\nreferences it in TP_printk(), which can be executed hours later when the\nstring is free, the function test_event_printk() runs on all events as\nthey are registered to make sure there\u0026apos;s no unwanted dereferencing.\n\nIt calls process_string() to handle cases in TP_printk() format that has\n\u0026quot;%s\u0026quot;. It returns whether or not the string is safe. But it can have some\nfalse positives.\n\nFor instance, xe_bo_move() has:\n\n TP_printk(\u0026quot;move_lacks_source:%s, migrate object %p [size %zu] from %s to %s device_id:%s\u0026quot;,\n            __entry-\u0026gt;move_lacks_source ? \u0026quot;yes\u0026quot; : \u0026quot;no\u0026quot;, __entry-\u0026gt;bo, __entry-\u0026gt;size,\n            xe_mem_type_to_name[__entry-\u0026gt;old_placement],\n            xe_mem_type_to_name[__entry-\u0026gt;new_placement], __get_str(device_id))\n\nWhere the \u0026quot;%s\u0026quot; references into xe_mem_type_to_name[]. This is an array of\npointers that should be safe for the event to access. Instead of flagging\nthis as a bad reference, if a reference points to an array, where the\nrecord field is the index, consider it safe.(CVE-2024-57930)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio-blk: don\u0026apos;t keep queue frozen during system suspend\n\nCommit 4ce6e2db00de (\u0026quot;virtio-blk: Ensure no requests in virtqueues before\ndeleting vqs.\u0026quot;) replaces queue quiesce with queue freeze in virtio-blk\u0026apos;s\nPM callbacks. And the motivation is to drain inflight IOs before suspending.\n\nblock layer\u0026apos;s queue freeze looks very handy, but it is also easy to cause\ndeadlock, such as, any attempt to call into bio_queue_enter() may run into\ndeadlock if the queue is frozen in current context. There are all kinds\nof -\u0026gt;suspend() called in suspend context, so keeping queue frozen in the\nwhole suspend context isn\u0026apos;t one good idea. And Marek reported lockdep\nwarning[1] caused by virtio-blk\u0026apos;s freeze queue in virtblk_freeze().\n\n[1] https://lore.kernel.org/linux-block/ca16370e-d646-4eee-b9cc-87277c89c43c@samsung.com/\n\nGiven the motivation is to drain in-flight IOs, it can be done by calling\nfreeze \u0026amp; unfreeze, meantime restore to previous behavior by keeping queue\nquiesced during suspend.(CVE-2024-57946)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock, bfq: fix waker_bfqq UAF after bfq_split_bfqq()\n\nOur syzkaller report a following UAF for v6.6:\n\nBUG: KASAN: slab-use-after-free in bfq_init_rq+0x175d/0x17a0 block/bfq-iosched.c:6958\nRead of size 8 at addr ffff8881b57147d8 by task fsstress/232726\n\nCPU: 2 PID: 232726 Comm: fsstress Not tainted 6.6.0-g3629d1885222 #39\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x91/0xf0 lib/dump_stack.c:106\n print_address_description.constprop.0+0x66/0x300 mm/kasan/report.c:364\n print_report+0x3e/0x70 mm/kasan/report.c:475\n kasan_report+0xb8/0xf0 mm/kasan/report.c:588\n hlist_add_head include/linux/list.h:1023 [inline]\n bfq_init_rq+0x175d/0x17a0 block/bfq-iosched.c:6958\n bfq_insert_request.isra.0+0xe8/0xa20 block/bfq-iosched.c:6271\n bfq_insert_requests+0x27f/0x390 block/bfq-iosched.c:6323\n blk_mq_insert_request+0x290/0x8f0 block/blk-mq.c:2660\n blk_mq_submit_bio+0x1021/0x15e0 block/blk-mq.c:3143\n __submit_bio+0xa0/0x6b0 block/blk-core.c:639\n __submit_bio_noacct_mq block/blk-core.c:718 [inline]\n submit_bio_noacct_nocheck+0x5b7/0x810 block/blk-core.c:747\n submit_bio_noacct+0xca0/0x1990 block/blk-core.c:847\n __ext4_read_bh fs/ext4/super.c:205 [inline]\n ext4_read_bh+0x15e/0x2e0 fs/ext4/super.c:230\n __read_extent_tree_block+0x304/0x6f0 fs/ext4/extents.c:567\n ext4_find_extent+0x479/0xd20 fs/ext4/extents.c:947\n ext4_ext_map_blocks+0x1a3/0x2680 fs/ext4/extents.c:4182\n ext4_map_blocks+0x929/0x15a0 fs/ext4/inode.c:660\n ext4_iomap_begin_report+0x298/0x480 fs/ext4/inode.c:3569\n iomap_iter+0x3dd/0x1010 fs/iomap/iter.c:91\n iomap_fiemap+0x1f4/0x360 fs/iomap/fiemap.c:80\n ext4_fiemap+0x181/0x210 fs/ext4/extents.c:5051\n ioctl_fiemap.isra.0+0x1b4/0x290 fs/ioctl.c:220\n do_vfs_ioctl+0x31c/0x11a0 fs/ioctl.c:811\n __do_sys_ioctl fs/ioctl.c:869 [inline]\n __se_sys_ioctl+0xae/0x190 fs/ioctl.c:857\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x70/0x120 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nAllocated by task 232719:\n kasan_save_stack+0x22/0x50 mm/kasan/common.c:45\n kasan_set_track+0x25/0x30 mm/kasan/common.c:52\n __kasan_slab_alloc+0x87/0x90 mm/kasan/common.c:328\n kasan_slab_alloc include/linux/kasan.h:188 [inline]\n slab_post_alloc_hook mm/slab.h:768 [inline]\n slab_alloc_node mm/slub.c:3492 [inline]\n kmem_cache_alloc_node+0x1b8/0x6f0 mm/slub.c:3537\n bfq_get_queue+0x215/0x1f00 block/bfq-iosched.c:5869\n bfq_get_bfqq_handle_split+0x167/0x5f0 block/bfq-iosched.c:6776\n bfq_init_rq+0x13a4/0x17a0 block/bfq-iosched.c:6938\n bfq_insert_request.isra.0+0xe8/0xa20 block/bfq-iosched.c:6271\n bfq_insert_requests+0x27f/0x390 block/bfq-iosched.c:6323\n blk_mq_insert_request+0x290/0x8f0 block/blk-mq.c:2660\n blk_mq_submit_bio+0x1021/0x15e0 block/blk-mq.c:3143\n __submit_bio+0xa0/0x6b0 block/blk-core.c:639\n __submit_bio_noacct_mq block/blk-core.c:718 [inline]\n submit_bio_noacct_nocheck+0x5b7/0x810 block/blk-core.c:747\n submit_bio_noacct+0xca0/0x1990 block/blk-core.c:847\n __ext4_read_bh fs/ext4/super.c:205 [inline]\n ext4_read_bh_nowait+0x15a/0x240 fs/ext4/super.c:217\n ext4_read_bh_lock+0xac/0xd0 fs/ext4/super.c:242\n ext4_bread_batch+0x268/0x500 fs/ext4/inode.c:958\n __ext4_find_entry+0x448/0x10f0 fs/ext4/namei.c:1671\n ext4_lookup_entry fs/ext4/namei.c:1774 [inline]\n ext4_lookup.part.0+0x359/0x6f0 fs/ext4/namei.c:1842\n ext4_lookup+0x72/0x90 fs/ext4/namei.c:1839\n __lookup_slow+0x257/0x480 fs/namei.c:1696\n lookup_slow fs/namei.c:1713 [inline]\n walk_component+0x454/0x5c0 fs/namei.c:2004\n link_path_walk.part.0+0x773/0xda0 fs/namei.c:2331\n link_path_walk fs/namei.c:3826 [inline]\n path_openat+0x1b9/0x520 fs/namei.c:3826\n do_filp_open+0x1b7/0x400 fs/namei.c:3857\n do_sys_openat2+0x5dc/0x6e0 fs/open.c:1428\n do_sys_open fs/open.c:1443 [inline]\n __do_sys_openat fs/open.c:1459 [inline]\n __se_sys_openat fs/open.c:1454 [inline]\n __x64_sys_openat+0x148/0x200 fs/open.c:1454\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_6\n---truncated---(CVE-2025-21631)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur\n\nscsi_execute_cmd() function can return both negative (linux codes) and\npositive (scsi_cmnd result field) error codes.\n\nCurrently the driver just passes error codes of scsi_execute_cmd() to\nhwmon core, which is incorrect because hwmon only checks for negative\nerror codes. This leads to hwmon reporting uninitialized data to\nuserspace in case of SCSI errors (for example if the disk drive was\ndisconnected).\n\nThis patch checks scsi_execute_cmd() output and returns -EIO if it\u0026apos;s\nerror code is positive.\n\n[groeck: Avoid inline variable declaration for portability](CVE-2025-21656)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb()\n\nThis patch addresses a null-ptr-deref in qt2_process_read_urb() due to\nan incorrect bounds check in the following:\n\n       if (newport \u0026gt; serial-\u0026gt;num_ports) {\n               dev_err(\u0026amp;port-\u0026gt;dev,\n                       \u0026quot;%s - port change to invalid port: %i\\n\u0026quot;,\n                       __func__, newport);\n               break;\n       }\n\nThe condition doesn\u0026apos;t account for the valid range of the serial-\u0026gt;port\nbuffer, which is from 0 to serial-\u0026gt;num_ports - 1. When newport is equal\nto serial-\u0026gt;num_ports, the assignment of \u0026quot;port\u0026quot; in the\nfollowing code is out-of-bounds and NULL:\n\n       serial_priv-\u0026gt;current_port = newport;\n       port = serial-\u0026gt;port[serial_priv-\u0026gt;current_port];\n\nThe fix checks if newport is greater than or equal to serial-\u0026gt;num_ports\nindicating it is out-of-bounds.(CVE-2025-21689)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Truncate address space when flipping GFS2_DIF_JDATA flag\n\nTruncate an inode\u0026apos;s address space when flipping the GFS2_DIF_JDATA flag:\ndepending on that flag, the pages in the address space will either use\nbuffer heads or iomap_folio_state structs, and we cannot mix the two.(CVE-2025-21699)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdc-acm: Check control transfer buffer size before access\n\nIf the first fragment is shorter than struct usb_cdc_notification, we can\u0026apos;t\ncalculate an expected_size. Log an error and discard the notification\ninstead of reading lengths from memory outside the received data, which can\nlead to memory corruption when the expected_size decreases between\nfragments, causing `expected_size - acm-\u0026gt;nb_index` to wrap.\n\nThis issue has been present since the beginning of git history; however,\nit only leads to memory corruption since commit ea2583529cd1\n(\u0026quot;cdc-acm: reassemble fragmented notifications\u0026quot;).\n\nA mitigating factor is that acm_ctrl_irq() can only execute after userspace\nhas opened /dev/ttyACM*; but if ModemManager is running, ModemManager will\ndo that automatically depending on the USB device\u0026apos;s vendor/product IDs and\nits other interfaces.(CVE-2025-21704)","status":"published","published":"2025-02-28T11:08:18Z","modified":"2026-08-18T01:17:50.290529504Z","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:42.253598Z"},{"id":"OESA-2025-1205","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Prevent tailcall infinite loop caused by freplace\n\nThere is a potential infinite loop issue that can occur when using a\ncombination of tail calls and freplace.\n\nIn an upcoming selftest, the attach target for entry_freplace of\ntailcall_freplace.c is subprog_tc of tc_bpf2bpf.c, while the tail call in\nentry_freplace leads to entry_tc. This results in an infinite loop:\n\nentry_tc -\u0026gt; subprog_tc -\u0026gt; entry_freplace --tailcall-\u0026gt; entry_tc.\n\nThe problem arises because the tail_call_cnt in entry_freplace resets to\nzero each time entry_freplace is executed, causing the tail call mechanism\nto never terminate, eventually leading to a kernel panic.\n\nTo fix this issue, the solution is twofold:\n\n1. Prevent updating a program extended by an freplace program to a\n   prog_array map.\n2. Prevent extending a program that is already part of a prog_array map\n   with an freplace program.\n\nThis ensures that:\n\n* If a program or its subprogram has been extended by an freplace program,\n  it can no longer be updated to a prog_array map.\n* If a program has been added to a prog_array map, neither it nor its\n  subprograms can be extended by an freplace program.\n\nMoreover, an extension program should not be tailcalled. As such, return\n-EINVAL if the program has a type of BPF_PROG_TYPE_EXT when adding it to a\nprog_array map.\n\nAdditionally, fix a minor code style issue by replacing eight spaces with a\ntab for proper formatting.(CVE-2024-47794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/thp: fix deferred split unqueue naming and locking\n\nRecent changes are putting more pressure on THP deferred split queues:\nunder load revealing long-standing races, causing list_del corruptions,\n\u0026quot;Bad page state\u0026quot;s and worse (I keep BUGs in both of those, so usually\ndon\u0026apos;t get to see how badly they end up without).  The relevant recent\nchanges being 6.8\u0026apos;s mTHP, 6.10\u0026apos;s mTHP swapout, and 6.12\u0026apos;s mTHP swapin,\nimproved swap allocation, and underused THP splitting.\n\nBefore fixing locking: rename misleading folio_undo_large_rmappable(),\nwhich does not undo large_rmappable, to folio_unqueue_deferred_split(),\nwhich is what it does.  But that and its out-of-line __callee are mm\ninternals of very limited usability: add comment and WARN_ON_ONCEs to\ncheck usage; and return a bool to say if a deferred split was unqueued,\nwhich can then be used in WARN_ON_ONCEs around safety checks (sparing\ncallers the arcane conditionals in __folio_unqueue_deferred_split()).\n\nJust omit the folio_unqueue_deferred_split() from free_unref_folios(), all\nof whose callers now call it beforehand (and if any forget then bad_page()\nwill tell) - except for its caller put_pages_list(), which itself no\nlonger has any callers (and will be deleted separately).\n\nSwapout: mem_cgroup_swapout() has been resetting folio-\u0026gt;memcg_data 0\nwithout checking and unqueueing a THP folio from deferred split list;\nwhich is unfortunate, since the split_queue_lock depends on the memcg\n(when memcg is enabled); so swapout has been unqueueing such THPs later,\nwhen freeing the folio, using the pgdat\u0026apos;s lock instead: potentially\ncorrupting the memcg\u0026apos;s list.  __remove_mapping() has frozen refcount to 0\nhere, so no problem with calling folio_unqueue_deferred_split() before\nresetting memcg_data.\n\nThat goes back to 5.4 commit 87eaceb3faa5 (\u0026quot;mm: thp: make deferred split\nshrinker memcg aware\u0026quot;): which included a check on swapcache before adding\nto deferred queue, but no check on deferred queue before adding THP to\nswapcache.  That worked fine with the usual sequence of events in reclaim\n(though there were a couple of rare ways in which a THP on deferred queue\ncould have been swapped out), but 6.12 commit dafff3f4c850 (\u0026quot;mm: split\nunderused THPs\u0026quot;) avoids splitting underused THPs in reclaim, which makes\nswapcache THPs on deferred queue commonplace.\n\nKeep the check on swapcache before adding to deferred queue?  Yes: it is\nno longer essential, but preserves the existing behaviour, and is likely\nto be a worthwhile optimization (vmstat showed much more traffic on the\nqueue under swapping load if the check was removed); update its comment.\n\nMemcg-v1 move (deprecated): mem_cgroup_move_account() has been changing\nfolio-\u0026gt;memcg_data without checking and unqueueing a THP folio from the\ndeferred list, sometimes corrupting \u0026quot;from\u0026quot; memcg\u0026apos;s list, like swapout. \nRefcount is non-zero here, so folio_unqueue_deferred_split() can only be\nused in a WARN_ON_ONCE to validate the fix, which must be done earlier:\nmem_cgroup_move_charge_pte_range() first try to split the THP (splitting\nof course unqueues), or skip it if that fails.  Not ideal, but moving\ncharge has been requested, and khugepaged should repair the THP later:\nnobody wants new custom unqueueing code just for this deprecated case.\n\nThe 87eaceb3faa5 commit did have the code to move from one deferred list\nto another (but was not conscious of its unsafety while refcount non-0);\nbut that was removed by 5.6 commit fac0516b5534 (\u0026quot;mm: thp: don\u0026apos;t need care\ndeferred split queue in memcg charge move path\u0026quot;), which argued that the\nexistence of a PMD mapping guarantees that the THP cannot be on a deferred\nlist.  As above, false in rare cases, and now commonly false.\n\nBackport to 6.11 should be straightforward.  Earlier backports must take\ncare that other _deferred_list fixes and dependencies are included.  There\nis not a strong case for backports, but they can fix cornercases.(CVE-2024-53079)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sched: fix ordering of qlen adjustment\n\nChanges to sch-\u0026gt;q.qlen around qdisc_tree_reduce_backlog() need to happen\n_before_ a call to said function because otherwise it may fail to notify\nparent qdiscs when the child is about to become empty.(CVE-2024-53164)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen/netfront: fix crash when removing device\n\nWhen removing a netfront device directly after a suspend/resume cycle\nit might happen that the queues have not been setup again, causing a\ncrash during the attempt to stop the queues another time.\n\nFix that by checking the queues are existing before trying to stop\nthem.\n\nThis is XSA-465 / CVE-2024-53240.(CVE-2024-53240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix TCP timers deadlock after rmmod\n\nCommit ef7134c7fc48 (\u0026quot;smb: client: Fix use-after-free of network namespace.\u0026quot;)\nfixed a netns UAF by manually enabled socket refcounting\n(sk-\u0026gt;sk_net_refcnt=1 and sock_inuse_add(net, 1)).\n\nThe reason the patch worked for that bug was because we now hold\nreferences to the netns (get_net_track() gets a ref internally)\nand they\u0026apos;re properly released (internally, on __sk_destruct()),\nbut only because sk-\u0026gt;sk_net_refcnt was set.\n\nProblem:\n(this happens regardless of CONFIG_NET_NS_REFCNT_TRACKER and regardless\nif init_net or other)\n\nSetting sk-\u0026gt;sk_net_refcnt=1 *manually* and *after* socket creation is not\nonly out of cifs scope, but also technically wrong -- it\u0026apos;s set conditionally\nbased on user (=1) vs kernel (=0) sockets.  And net/ implementations\nseem to base their user vs kernel space operations on it.\n\ne.g. upon TCP socket close, the TCP timers are not cleared because\nsk-\u0026gt;sk_net_refcnt=1:\n(cf. commit 151c9c724d05 (\u0026quot;tcp: properly terminate timers for kernel sockets\u0026quot;))\n\nnet/ipv4/tcp.c:\n    void tcp_close(struct sock *sk, long timeout)\n    {\n    \tlock_sock(sk);\n    \t__tcp_close(sk, timeout);\n    \trelease_sock(sk);\n    \tif (!sk-\u0026gt;sk_net_refcnt)\n    \t\tinet_csk_clear_xmit_timers_sync(sk);\n    \tsock_put(sk);\n    }\n\nWhich will throw a lockdep warning and then, as expected, deadlock on\ntcp_write_timer().\n\nA way to reproduce this is by running the reproducer from ef7134c7fc48\nand then \u0026apos;rmmod cifs\u0026apos;.  A few seconds later, the deadlock/lockdep\nwarning shows up.\n\nFix:\nWe shouldn\u0026apos;t mess with socket internals ourselves, so do not set\nsk_net_refcnt manually.\n\nAlso change __sock_create() to sock_create_kern() for explicitness.\n\nAs for non-init_net network namespaces, we deal with it the best way\nwe can -- hold an extra netns reference for server-\u0026gt;ssocket and drop it\nwhen it\u0026apos;s released.  This ensures that the netns still exists whenever\nwe need to create/destroy server-\u0026gt;ssocket, but is not directly tied to\nit.(CVE-2024-54680)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: tun: fix tun_napi_alloc_frags()\n\nsyzbot reported the following crash [1]\n\nIssue came with the blamed commit. Instead of going through\nall the iov components, we keep using the first one\nand end up with a malformed skb.\n\n[1]\n\nkernel BUG at net/core/skbuff.c:2849 !\nOops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 0 UID: 0 PID: 6230 Comm: syz-executor132 Not tainted 6.13.0-rc1-syzkaller-00407-g96b6fcc0ee41 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024\n RIP: 0010:__pskb_pull_tail+0x1568/0x1570 net/core/skbuff.c:2848\nCode: 38 c1 0f 8c 32 f1 ff ff 4c 89 f7 e8 92 96 74 f8 e9 25 f1 ff ff e8 e8 ae 09 f8 48 8b 5c 24 08 e9 eb fb ff ff e8 d9 ae 09 f8 90 \u0026lt;0f\u0026gt; 0b 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90\nRSP: 0018:ffffc90004cbef30 EFLAGS: 00010293\nRAX: ffffffff8995c347 RBX: 00000000fffffff2 RCX: ffff88802cf45a00\nRDX: 0000000000000000 RSI: 00000000fffffff2 RDI: 0000000000000000\nRBP: ffff88807df0c06a R08: ffffffff8995b084 R09: 1ffff1100fbe185c\nR10: dffffc0000000000 R11: ffffed100fbe185d R12: ffff888076e85d50\nR13: ffff888076e85c80 R14: ffff888076e85cf4 R15: ffff888076e85c80\nFS:  00007f0dca6ea6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f0dca6ead58 CR3: 00000000119da000 CR4: 00000000003526f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_cow_data+0x2da/0xcb0 net/core/skbuff.c:5284\n  tipc_aead_decrypt net/tipc/crypto.c:894 [inline]\n  tipc_crypto_rcv+0x402/0x24e0 net/tipc/crypto.c:1844\n  tipc_rcv+0x57e/0x12a0 net/tipc/node.c:2109\n  tipc_l2_rcv_msg+0x2bd/0x450 net/tipc/bearer.c:668\n  __netif_receive_skb_list_ptype net/core/dev.c:5720 [inline]\n  __netif_receive_skb_list_core+0x8b7/0x980 net/core/dev.c:5762\n  __netif_receive_skb_list net/core/dev.c:5814 [inline]\n  netif_receive_skb_list_internal+0xa51/0xe30 net/core/dev.c:5905\n  gro_normal_list include/net/gro.h:515 [inline]\n  napi_complete_done+0x2b5/0x870 net/core/dev.c:6256\n  napi_complete include/linux/netdevice.h:567 [inline]\n  tun_get_user+0x2ea0/0x4890 drivers/net/tun.c:1982\n  tun_chr_write_iter+0x10d/0x1f0 drivers/net/tun.c:2057\n do_iter_readv_writev+0x600/0x880\n  vfs_writev+0x376/0xba0 fs/read_write.c:1050\n  do_writev+0x1b6/0x360 fs/read_write.c:1096\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-56372)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask()\n\nWhen I try to manually set bitrates:\n\niw wlan0 set bitrates legacy-2.4 1\n\nI get sleeping from invalid context error, see below. Fix that by switching to\nuse recently introduced ieee80211_iterate_stations_mtx().\n\nDo note that WCN6855 firmware is still crashing, I\u0026apos;m not sure if that firmware\neven supports bitrate WMI commands and should we consider disabling\nath12k_mac_op_set_bitrate_mask() for WCN6855? But that\u0026apos;s for another patch.\n\nBUG: sleeping function called from invalid context at drivers/net/wireless/ath/ath12k/wmi.c:420\nin_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 2236, name: iw\npreempt_count: 0, expected: 0\nRCU nest depth: 1, expected: 0\n3 locks held by iw/2236:\n #0: ffffffffabc6f1d8 (cb_lock){++++}-{3:3}, at: genl_rcv+0x14/0x40\n #1: ffff888138410810 (\u0026amp;rdev-\u0026gt;wiphy.mtx){+.+.}-{3:3}, at: nl80211_pre_doit+0x54d/0x800 [cfg80211]\n #2: ffffffffab2cfaa0 (rcu_read_lock){....}-{1:2}, at: ieee80211_iterate_stations_atomic+0x2f/0x200 [mac80211]\nCPU: 3 UID: 0 PID: 2236 Comm: iw Not tainted 6.11.0-rc7-wt-ath+ #1772\nHardware name: Intel(R) Client Systems NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0067.2021.0528.1339 05/28/2021\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xa4/0xe0\n dump_stack+0x10/0x20\n __might_resched+0x363/0x5a0\n ? __alloc_skb+0x165/0x340\n __might_sleep+0xad/0x160\n ath12k_wmi_cmd_send+0xb1/0x3d0 [ath12k]\n ? ath12k_wmi_init_wcn7850+0xa40/0xa40 [ath12k]\n ? __netdev_alloc_skb+0x45/0x7b0\n ? __asan_memset+0x39/0x40\n ? ath12k_wmi_alloc_skb+0xf0/0x150 [ath12k]\n ? reacquire_held_locks+0x4d0/0x4d0\n ath12k_wmi_set_peer_param+0x340/0x5b0 [ath12k]\n ath12k_mac_disable_peer_fixed_rate+0xa3/0x110 [ath12k]\n ? ath12k_mac_vdev_stop+0x4f0/0x4f0 [ath12k]\n ieee80211_iterate_stations_atomic+0xd4/0x200 [mac80211]\n ath12k_mac_op_set_bitrate_mask+0x5d2/0x1080 [ath12k]\n ? ath12k_mac_vif_chan+0x320/0x320 [ath12k]\n drv_set_bitrate_mask+0x267/0x470 [mac80211]\n ieee80211_set_bitrate_mask+0x4cc/0x8a0 [mac80211]\n ? __this_cpu_preempt_check+0x13/0x20\n nl80211_set_tx_bitrate_mask+0x2bc/0x530 [cfg80211]\n ? nl80211_parse_tx_bitrate_mask+0x2320/0x2320 [cfg80211]\n ? trace_contention_end+0xef/0x140\n ? rtnl_unlock+0x9/0x10\n ? nl80211_pre_doit+0x557/0x800 [cfg80211]\n genl_family_rcv_msg_doit+0x1f0/0x2e0\n ? genl_family_rcv_msg_attrs_parse.isra.0+0x250/0x250\n ? ns_capable+0x57/0xd0\n genl_family_rcv_msg+0x34c/0x600\n ? genl_family_rcv_msg_dumpit+0x310/0x310\n ? __lock_acquire+0xc62/0x1de0\n ? he_set_mcs_mask.isra.0+0x8d0/0x8d0 [cfg80211]\n ? nl80211_parse_tx_bitrate_mask+0x2320/0x2320 [cfg80211]\n ? cfg80211_external_auth_request+0x690/0x690 [cfg80211]\n genl_rcv_msg+0xa0/0x130\n netlink_rcv_skb+0x14c/0x400\n ? genl_family_rcv_msg+0x600/0x600\n ? netlink_ack+0xd70/0xd70\n ? rwsem_optimistic_spin+0x4f0/0x4f0\n ? genl_rcv+0x14/0x40\n ? down_read_killable+0x580/0x580\n ? netlink_deliver_tap+0x13e/0x350\n ? __this_cpu_preempt_check+0x13/0x20\n genl_rcv+0x23/0x40\n netlink_unicast+0x45e/0x790\n ? netlink_attachskb+0x7f0/0x7f0\n netlink_sendmsg+0x7eb/0xdb0\n ? netlink_unicast+0x790/0x790\n ? __this_cpu_preempt_check+0x13/0x20\n ? selinux_socket_sendmsg+0x31/0x40\n ? netlink_unicast+0x790/0x790\n __sock_sendmsg+0xc9/0x160\n ____sys_sendmsg+0x620/0x990\n ? kernel_sendmsg+0x30/0x30\n ? __copy_msghdr+0x410/0x410\n ? __kasan_check_read+0x11/0x20\n ? mark_lock+0xe6/0x1470\n ___sys_sendmsg+0xe9/0x170\n ? copy_msghdr_from_user+0x120/0x120\n ? __lock_acquire+0xc62/0x1de0\n ? do_fault_around+0x2c6/0x4e0\n ? do_user_addr_fault+0x8c1/0xde0\n ? reacquire_held_locks+0x220/0x4d0\n ? do_user_addr_fault+0x8c1/0xde0\n ? __kasan_check_read+0x11/0x20\n ? __fdget+0x4e/0x1d0\n ? sockfd_lookup_light+0x1a/0x170\n __sys_sendmsg+0xd2/0x180\n ? __sys_sendmsg_sock+0x20/0x20\n ? reacquire_held_locks+0x4d0/0x4d0\n ? debug_smp_processor_id+0x17/0x20\n __x64_sys_sendmsg+0x72/0xb0\n ? lockdep_hardirqs_on+0x7d/0x100\n x64_sys_call+0x894/0x9f0\n do_syscall_64+0x64/0x130\n entry_SYSCALL_64_after_\n---truncated---(CVE-2024-56607)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: do not defer rule destruction via call_rcu\n\nnf_tables_chain_destroy can sleep, it can\u0026apos;t be used from call_rcu\ncallbacks.\n\nMoreover, nf_tables_rule_release() is only safe for error unwinding,\nwhile transaction mutex is held and the to-be-desroyed rule was not\nexposed to either dataplane or dumps, as it deactives+frees without\nthe required synchronize_rcu() in-between.\n\nnft_rule_expr_deactivate() callbacks will change -\u0026gt;use counters\nof other chains/sets, see e.g. nft_lookup .deactivate callback, these\nmust be serialized via transaction mutex.\n\nAlso add a few lockdep asserts to make this more explicit.\n\nCalling synchronize_rcu() isn\u0026apos;t ideal, but fixing this without is hard\nand way more intrusive.  As-is, we can get:\n\nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..\nWorkqueue: events nf_tables_trans_destroy_work\nRIP: 0010:nft_set_destroy+0x3fe/0x5c0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n nf_tables_trans_destroy_work+0x6b7/0xad0\n process_one_work+0x64a/0xce0\n worker_thread+0x613/0x10d0\n\nIn case the synchronize_rcu becomes an issue, we can explore alternatives.\n\nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain\nobject, deactivate the rules + the chain and then defer the freeing to the\nnft destroy workqueue.  We\u0026apos;d still need to keep the synchronize_rcu path as\na fallback to handle -ENOMEM corner cases though.(CVE-2024-56655)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: defer final \u0026apos;struct net\u0026apos; free in netns dismantle\n\nIlya reported a slab-use-after-free in dst_destroy [1]\n\nIssue is in xfrm6_net_init() and xfrm4_net_init() :\n\nThey copy xfrm[46]_dst_ops_template into net-\u0026gt;xfrm.xfrm[46]_dst_ops.\n\nBut net structure might be freed before all the dst callbacks are\ncalled. So when dst_destroy() calls later :\n\nif (dst-\u0026gt;ops-\u0026gt;destroy)\n    dst-\u0026gt;ops-\u0026gt;destroy(dst);\n\ndst-\u0026gt;ops points to the old net-\u0026gt;xfrm.xfrm[46]_dst_ops, which has been freed.\n\nSee a relevant issue fixed in :\n\nac888d58869b (\u0026quot;net: do not delay dst_entries_add() in dst_release()\u0026quot;)\n\nA fix is to queue the \u0026apos;struct net\u0026apos; to be freed after one\nanother cleanup_net() round (and existing rcu_barrier())\n\n[1]\n\nBUG: KASAN: slab-use-after-free in dst_destroy (net/core/dst.c:112)\nRead of size 8 at addr ffff8882137ccab0 by task swapper/37/0\nDec 03 05:46:18 kernel:\nCPU: 37 UID: 0 PID: 0 Comm: swapper/37 Kdump: loaded Not tainted 6.12.0 #67\nHardware name: Red Hat KVM/RHEL, BIOS 1.16.1-1.el9 04/01/2014\nCall Trace:\n \u0026lt;IRQ\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:124)\nprint_address_description.constprop.0 (mm/kasan/report.c:378)\n? dst_destroy (net/core/dst.c:112)\nprint_report (mm/kasan/report.c:489)\n? dst_destroy (net/core/dst.c:112)\n? kasan_addr_to_slab (mm/kasan/common.c:37)\nkasan_report (mm/kasan/report.c:603)\n? dst_destroy (net/core/dst.c:112)\n? rcu_do_batch (kernel/rcu/tree.c:2567)\ndst_destroy (net/core/dst.c:112)\nrcu_do_batch (kernel/rcu/tree.c:2567)\n? __pfx_rcu_do_batch (kernel/rcu/tree.c:2491)\n? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4339 kernel/locking/lockdep.c:4406)\nrcu_core (kernel/rcu/tree.c:2825)\nhandle_softirqs (kernel/softirq.c:554)\n__irq_exit_rcu (kernel/softirq.c:589 kernel/softirq.c:428 kernel/softirq.c:637)\nirq_exit_rcu (kernel/softirq.c:651)\nsysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1049 arch/x86/kernel/apic/apic.c:1049)\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\nasm_sysvec_apic_timer_interrupt (./arch/x86/include/asm/idtentry.h:702)\nRIP: 0010:default_idle (./arch/x86/include/asm/irqflags.h:37 ./arch/x86/include/asm/irqflags.h:92 arch/x86/kernel/process.c:743)\nCode: 00 4d 29 c8 4c 01 c7 4c 29 c2 e9 6e ff ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 90 0f 00 2d c7 c9 27 00 fb f4 \u0026lt;fa\u0026gt; c3 cc cc cc cc 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 90\nRSP: 0018:ffff888100d2fe00 EFLAGS: 00000246\nRAX: 00000000001870ed RBX: 1ffff110201a5fc2 RCX: ffffffffb61a3e46\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffb3d4d123\nRBP: 0000000000000000 R08: 0000000000000001 R09: ffffed11c7e1835d\nR10: ffff888e3f0c1aeb R11: 0000000000000000 R12: 0000000000000000\nR13: ffff888100d20000 R14: dffffc0000000000 R15: 0000000000000000\n? ct_kernel_exit.constprop.0 (kernel/context_tracking.c:148)\n? cpuidle_idle_call (kernel/sched/idle.c:186)\ndefault_idle_call (./include/linux/cpuidle.h:143 kernel/sched/idle.c:118)\ncpuidle_idle_call (kernel/sched/idle.c:186)\n? __pfx_cpuidle_idle_call (kernel/sched/idle.c:168)\n? lock_release (kernel/locking/lockdep.c:467 kernel/locking/lockdep.c:5848)\n? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4347 kernel/locking/lockdep.c:4406)\n? tsc_verify_tsc_adjust (arch/x86/kernel/tsc_sync.c:59)\ndo_idle (kernel/sched/idle.c:326)\ncpu_startup_entry (kernel/sched/idle.c:423 (discriminator 1))\nstart_secondary (arch/x86/kernel/smpboot.c:202 arch/x86/kernel/smpboot.c:282)\n? __pfx_start_secondary (arch/x86/kernel/smpboot.c:232)\n? soft_restart_cpu (arch/x86/kernel/head_64.S:452)\ncommon_startup_64 (arch/x86/kernel/head_64.S:414)\n \u0026lt;/TASK\u0026gt;\nDec 03 05:46:18 kernel:\nAllocated by task 12184:\nkasan_save_stack (mm/kasan/common.c:48)\nkasan_save_track (./arch/x86/include/asm/current.h:49 mm/kasan/common.c:60 mm/kasan/common.c:69)\n__kasan_slab_alloc (mm/kasan/common.c:319 mm/kasan/common.c:345)\nkmem_cache_alloc_noprof (mm/slub.c:4085 mm/slub.c:4134 mm/slub.c:4141)\ncopy_net_ns (net/core/net_namespace.c:421 net/core/net_namespace.c:480)\ncreate_new_namespaces\n---truncated---(CVE-2024-56658)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: lapb: increase LAPB_HEADER_LEN\n\nIt is unclear if net/lapb code is supposed to be ready for 8021q.\n\nWe can at least avoid crashes like the following :\n\nskbuff: skb_under_panic: text:ffffffff8aabe1f6 len:24 put:20 head:ffff88802824a400 data:ffff88802824a3fe tail:0x16 end:0x140 dev:nr0.2\n------------[ cut here ]------------\n kernel BUG at net/core/skbuff.c:206 !\nOops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 1 UID: 0 PID: 5508 Comm: dhcpcd Not tainted 6.12.0-rc7-syzkaller-00144-g66418447d27b #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024\n RIP: 0010:skb_panic net/core/skbuff.c:206 [inline]\n RIP: 0010:skb_under_panic+0x14b/0x150 net/core/skbuff.c:216\nCode: 0d 8d 48 c7 c6 2e 9e 29 8e 48 8b 54 24 08 8b 0c 24 44 8b 44 24 04 4d 89 e9 50 41 54 41 57 41 56 e8 1a 6f 37 02 48 83 c4 20 90 \u0026lt;0f\u0026gt; 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3\nRSP: 0018:ffffc90002ddf638 EFLAGS: 00010282\nRAX: 0000000000000086 RBX: dffffc0000000000 RCX: 7a24750e538ff600\nRDX: 0000000000000000 RSI: 0000000000000201 RDI: 0000000000000000\nRBP: ffff888034a86650 R08: ffffffff8174b13c R09: 1ffff920005bbe60\nR10: dffffc0000000000 R11: fffff520005bbe61 R12: 0000000000000140\nR13: ffff88802824a400 R14: ffff88802824a3fe R15: 0000000000000016\nFS:  00007f2a5990d740(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c2631fd CR3: 0000000029504000 CR4: 00000000003526f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_push+0xe5/0x100 net/core/skbuff.c:2636\n  nr_header+0x36/0x320 net/netrom/nr_dev.c:69\n  dev_hard_header include/linux/netdevice.h:3148 [inline]\n  vlan_dev_hard_header+0x359/0x480 net/8021q/vlan_dev.c:83\n  dev_hard_header include/linux/netdevice.h:3148 [inline]\n  lapbeth_data_transmit+0x1f6/0x2a0 drivers/net/wan/lapbether.c:257\n  lapb_data_transmit+0x91/0xb0 net/lapb/lapb_iface.c:447\n  lapb_transmit_buffer+0x168/0x1f0 net/lapb/lapb_out.c:149\n lapb_establish_data_link+0x84/0xd0\n lapb_device_event+0x4e0/0x670\n  notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93\n __dev_notify_flags+0x207/0x400\n  dev_change_flags+0xf0/0x1a0 net/core/dev.c:8922\n  devinet_ioctl+0xa4e/0x1aa0 net/ipv4/devinet.c:1188\n  inet_ioctl+0x3d7/0x4f0 net/ipv4/af_inet.c:1003\n  sock_do_ioctl+0x158/0x460 net/socket.c:1227\n  sock_ioctl+0x626/0x8e0 net/socket.c:1346\n  vfs_ioctl fs/ioctl.c:51 [inline]\n  __do_sys_ioctl fs/ioctl.c:907 [inline]\n  __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893\n  do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83(CVE-2024-56659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic()\n\nPackets injected by the CPU should have a SRC_PORT field equal to the\nCPU port module index in the Analyzer block (ocelot-\u0026gt;num_phys_ports).\n\nThe blamed commit copied the ocelot_ifh_set_basic() call incorrectly\nfrom ocelot_xmit_common() in net/dsa/tag_ocelot.c. Instead of calling\nwith \u0026quot;x\u0026quot;, it calls with BIT_ULL(x), but the field is not a port mask,\nbut rather a single port index.\n\n[ side note: this is the technical debt of code duplication :( ]\n\nThe error used to be silent and doesn\u0026apos;t appear to have other\nuser-visible manifestations, but with new changes in the packing\nlibrary, it now fails loudly as follows:\n\n------------[ cut here ]------------\nCannot store 0x40 inside bits 46-43 - will truncate\nsja1105 spi2.0: xmit timed out\nWARNING: CPU: 1 PID: 102 at lib/packing.c:98 __pack+0x90/0x198\nsja1105 spi2.0: timed out polling for tstamp\nCPU: 1 UID: 0 PID: 102 Comm: felix_xmit\nTainted: G        W        N 6.13.0-rc1-00372-gf706b85d972d-dirty #2605\nCall trace:\n __pack+0x90/0x198 (P)\n __pack+0x90/0x198 (L)\n packing+0x78/0x98\n ocelot_ifh_set_basic+0x260/0x368\n ocelot_port_inject_frame+0xa8/0x250\n felix_port_deferred_xmit+0x14c/0x258\n kthread_worker_fn+0x134/0x350\n kthread+0x114/0x138\n\nThe code path pertains to the ocelot switchdev driver and to the felix\nsecondary DSA tag protocol, ocelot-8021q. Here seen with ocelot-8021q.\n\nThe messenger (packing) is not really to blame, so fix the original\ncommit instead.(CVE-2024-56717)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset\n\nThe at_xdmac_memset_create_desc may return NULL, which will lead to a\nnull pointer dereference. For example, the len input is error, or the\natchan-\u0026gt;free_descs_list is empty and memory is exhausted. Therefore, add\ncheck to avoid this.(CVE-2024-56767)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: gpio-charger: Fix set charge current limits\n\nFix set charge current limits for devices which allow to set the lowest\ncharge current limit to be greater zero. If requested charge current limit\nis below lowest limit, the index equals current_limit_map_size which leads\nto accessing memory beyond allocated memory.(CVE-2024-57792)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs\n\nThe driver, through the SAS transport, exposes a sysfs interface to\nenable/disable PHYs in a controller/expander setup.  When multiple PHYs\nare disabled and enabled in rapid succession, the persistent and current\nconfig pages related to SAS IO unit/SAS Expander pages could get\ncorrupted.\n\nUse separate memory for each config request.(CVE-2024-57804)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: megaraid_sas: Fix for a potential deadlock\n\nThis fixes a \u0026apos;possible circular locking dependency detected\u0026apos; warning\n      CPU0                    CPU1\n      ----                    ----\n lock(\u0026amp;instance-\u0026gt;reset_mutex);\n                              lock(\u0026amp;shost-\u0026gt;scan_mutex);\n                              lock(\u0026amp;instance-\u0026gt;reset_mutex);\n lock(\u0026amp;shost-\u0026gt;scan_mutex);\n\nFix this by temporarily releasing the reset_mutex.(CVE-2024-57807)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Have process_string() also allow arrays\n\nIn order to catch a common bug where a TRACE_EVENT() TP_fast_assign()\nassigns an address of an allocated string to the ring buffer and then\nreferences it in TP_printk(), which can be executed hours later when the\nstring is free, the function test_event_printk() runs on all events as\nthey are registered to make sure there\u0026apos;s no unwanted dereferencing.\n\nIt calls process_string() to handle cases in TP_printk() format that has\n\u0026quot;%s\u0026quot;. It returns whether or not the string is safe. But it can have some\nfalse positives.\n\nFor instance, xe_bo_move() has:\n\n TP_printk(\u0026quot;move_lacks_source:%s, migrate object %p [size %zu] from %s to %s device_id:%s\u0026quot;,\n            __entry-\u0026gt;move_lacks_source ? \u0026quot;yes\u0026quot; : \u0026quot;no\u0026quot;, __entry-\u0026gt;bo, __entry-\u0026gt;size,\n            xe_mem_type_to_name[__entry-\u0026gt;old_placement],\n            xe_mem_type_to_name[__entry-\u0026gt;new_placement], __get_str(device_id))\n\nWhere the \u0026quot;%s\u0026quot; references into xe_mem_type_to_name[]. This is an array of\npointers that should be safe for the event to access. Instead of flagging\nthis as a bad reference, if a reference points to an array, where the\nrecord field is the index, consider it safe.(CVE-2024-57930)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio-blk: don\u0026apos;t keep queue frozen during system suspend\n\nCommit 4ce6e2db00de (\u0026quot;virtio-blk: Ensure no requests in virtqueues before\ndeleting vqs.\u0026quot;) replaces queue quiesce with queue freeze in virtio-blk\u0026apos;s\nPM callbacks. And the motivation is to drain inflight IOs before suspending.\n\nblock layer\u0026apos;s queue freeze looks very handy, but it is also easy to cause\ndeadlock, such as, any attempt to call into bio_queue_enter() may run into\ndeadlock if the queue is frozen in current context. There are all kinds\nof -\u0026gt;suspend() called in suspend context, so keeping queue frozen in the\nwhole suspend context isn\u0026apos;t one good idea. And Marek reported lockdep\nwarning[1] caused by virtio-blk\u0026apos;s freeze queue in virtblk_freeze().\n\n[1] https://lore.kernel.org/linux-block/ca16370e-d646-4eee-b9cc-87277c89c43c@samsung.com/\n\nGiven the motivation is to drain in-flight IOs, it can be done by calling\nfreeze \u0026amp; unfreeze, meantime restore to previous behavior by keeping queue\nquiesced during suspend.(CVE-2024-57946)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock, bfq: fix waker_bfqq UAF after bfq_split_bfqq()\n\nOur syzkaller report a following UAF for v6.6:\n\nBUG: KASAN: slab-use-after-free in bfq_init_rq+0x175d/0x17a0 block/bfq-iosched.c:6958\nRead of size 8 at addr ffff8881b57147d8 by task fsstress/232726\n\nCPU: 2 PID: 232726 Comm: fsstress Not tainted 6.6.0-g3629d1885222 #39\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x91/0xf0 lib/dump_stack.c:106\n print_address_description.constprop.0+0x66/0x300 mm/kasan/report.c:364\n print_report+0x3e/0x70 mm/kasan/report.c:475\n kasan_report+0xb8/0xf0 mm/kasan/report.c:588\n hlist_add_head include/linux/list.h:1023 [inline]\n bfq_init_rq+0x175d/0x17a0 block/bfq-iosched.c:6958\n bfq_insert_request.isra.0+0xe8/0xa20 block/bfq-iosched.c:6271\n bfq_insert_requests+0x27f/0x390 block/bfq-iosched.c:6323\n blk_mq_insert_request+0x290/0x8f0 block/blk-mq.c:2660\n blk_mq_submit_bio+0x1021/0x15e0 block/blk-mq.c:3143\n __submit_bio+0xa0/0x6b0 block/blk-core.c:639\n __submit_bio_noacct_mq block/blk-core.c:718 [inline]\n submit_bio_noacct_nocheck+0x5b7/0x810 block/blk-core.c:747\n submit_bio_noacct+0xca0/0x1990 block/blk-core.c:847\n __ext4_read_bh fs/ext4/super.c:205 [inline]\n ext4_read_bh+0x15e/0x2e0 fs/ext4/super.c:230\n __read_extent_tree_block+0x304/0x6f0 fs/ext4/extents.c:567\n ext4_find_extent+0x479/0xd20 fs/ext4/extents.c:947\n ext4_ext_map_blocks+0x1a3/0x2680 fs/ext4/extents.c:4182\n ext4_map_blocks+0x929/0x15a0 fs/ext4/inode.c:660\n ext4_iomap_begin_report+0x298/0x480 fs/ext4/inode.c:3569\n iomap_iter+0x3dd/0x1010 fs/iomap/iter.c:91\n iomap_fiemap+0x1f4/0x360 fs/iomap/fiemap.c:80\n ext4_fiemap+0x181/0x210 fs/ext4/extents.c:5051\n ioctl_fiemap.isra.0+0x1b4/0x290 fs/ioctl.c:220\n do_vfs_ioctl+0x31c/0x11a0 fs/ioctl.c:811\n __do_sys_ioctl fs/ioctl.c:869 [inline]\n __se_sys_ioctl+0xae/0x190 fs/ioctl.c:857\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x70/0x120 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nAllocated by task 232719:\n kasan_save_stack+0x22/0x50 mm/kasan/common.c:45\n kasan_set_track+0x25/0x30 mm/kasan/common.c:52\n __kasan_slab_alloc+0x87/0x90 mm/kasan/common.c:328\n kasan_slab_alloc include/linux/kasan.h:188 [inline]\n slab_post_alloc_hook mm/slab.h:768 [inline]\n slab_alloc_node mm/slub.c:3492 [inline]\n kmem_cache_alloc_node+0x1b8/0x6f0 mm/slub.c:3537\n bfq_get_queue+0x215/0x1f00 block/bfq-iosched.c:5869\n bfq_get_bfqq_handle_split+0x167/0x5f0 block/bfq-iosched.c:6776\n bfq_init_rq+0x13a4/0x17a0 block/bfq-iosched.c:6938\n bfq_insert_request.isra.0+0xe8/0xa20 block/bfq-iosched.c:6271\n bfq_insert_requests+0x27f/0x390 block/bfq-iosched.c:6323\n blk_mq_insert_request+0x290/0x8f0 block/blk-mq.c:2660\n blk_mq_submit_bio+0x1021/0x15e0 block/blk-mq.c:3143\n __submit_bio+0xa0/0x6b0 block/blk-core.c:639\n __submit_bio_noacct_mq block/blk-core.c:718 [inline]\n submit_bio_noacct_nocheck+0x5b7/0x810 block/blk-core.c:747\n submit_bio_noacct+0xca0/0x1990 block/blk-core.c:847\n __ext4_read_bh fs/ext4/super.c:205 [inline]\n ext4_read_bh_nowait+0x15a/0x240 fs/ext4/super.c:217\n ext4_read_bh_lock+0xac/0xd0 fs/ext4/super.c:242\n ext4_bread_batch+0x268/0x500 fs/ext4/inode.c:958\n __ext4_find_entry+0x448/0x10f0 fs/ext4/namei.c:1671\n ext4_lookup_entry fs/ext4/namei.c:1774 [inline]\n ext4_lookup.part.0+0x359/0x6f0 fs/ext4/namei.c:1842\n ext4_lookup+0x72/0x90 fs/ext4/namei.c:1839\n __lookup_slow+0x257/0x480 fs/namei.c:1696\n lookup_slow fs/namei.c:1713 [inline]\n walk_component+0x454/0x5c0 fs/namei.c:2004\n link_path_walk.part.0+0x773/0xda0 fs/namei.c:2331\n link_path_walk fs/namei.c:3826 [inline]\n path_openat+0x1b9/0x520 fs/namei.c:3826\n do_filp_open+0x1b7/0x400 fs/namei.c:3857\n do_sys_openat2+0x5dc/0x6e0 fs/open.c:1428\n do_sys_open fs/open.c:1443 [inline]\n __do_sys_openat fs/open.c:1459 [inline]\n __se_sys_openat fs/open.c:1454 [inline]\n __x64_sys_openat+0x148/0x200 fs/open.c:1454\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_6\n---truncated---(CVE-2025-21631)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur\n\nscsi_execute_cmd() function can return both negative (linux codes) and\npositive (scsi_cmnd result field) error codes.\n\nCurrently the driver just passes error codes of scsi_execute_cmd() to\nhwmon core, which is incorrect because hwmon only checks for negative\nerror codes. This leads to hwmon reporting uninitialized data to\nuserspace in case of SCSI errors (for example if the disk drive was\ndisconnected).\n\nThis patch checks scsi_execute_cmd() output and returns -EIO if it\u0026apos;s\nerror code is positive.\n\n[groeck: Avoid inline variable declaration for portability](CVE-2025-21656)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb()\n\nThis patch addresses a null-ptr-deref in qt2_process_read_urb() due to\nan incorrect bounds check in the following:\n\n       if (newport \u0026gt; serial-\u0026gt;num_ports) {\n               dev_err(\u0026amp;port-\u0026gt;dev,\n                       \u0026quot;%s - port change to invalid port: %i\\n\u0026quot;,\n                       __func__, newport);\n               break;\n       }\n\nThe condition doesn\u0026apos;t account for the valid range of the serial-\u0026gt;port\nbuffer, which is from 0 to serial-\u0026gt;num_ports - 1. When newport is equal\nto serial-\u0026gt;num_ports, the assignment of \u0026quot;port\u0026quot; in the\nfollowing code is out-of-bounds and NULL:\n\n       serial_priv-\u0026gt;current_port = newport;\n       port = serial-\u0026gt;port[serial_priv-\u0026gt;current_port];\n\nThe fix checks if newport is greater than or equal to serial-\u0026gt;num_ports\nindicating it is out-of-bounds.(CVE-2025-21689)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Truncate address space when flipping GFS2_DIF_JDATA flag\n\nTruncate an inode\u0026apos;s address space when flipping the GFS2_DIF_JDATA flag:\ndepending on that flag, the pages in the address space will either use\nbuffer heads or iomap_folio_state structs, and we cannot mix the two.(CVE-2025-21699)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdc-acm: Check control transfer buffer size before access\n\nIf the first fragment is shorter than struct usb_cdc_notification, we can\u0026apos;t\ncalculate an expected_size. Log an error and discard the notification\ninstead of reading lengths from memory outside the received data, which can\nlead to memory corruption when the expected_size decreases between\nfragments, causing `expected_size - acm-\u0026gt;nb_index` to wrap.\n\nThis issue has been present since the beginning of git history; however,\nit only leads to memory corruption since commit ea2583529cd1\n(\u0026quot;cdc-acm: reassemble fragmented notifications\u0026quot;).\n\nA mitigating factor is that acm_ctrl_irq() can only execute after userspace\nhas opened /dev/ttyACM*; but if ModemManager is running, ModemManager will\ndo that automatically depending on the USB device\u0026apos;s vendor/product IDs and\nits other interfaces.(CVE-2025-21704)","status":"published","published":"2025-02-28T11:08:18Z","modified":"2026-08-18T01:18:40.204031792Z","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:42.253598Z"},{"id":"UBUNTU-CVE-2024-56655","description":"In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: do not defer rule destruction via call_rcu nf_tables_chain_destroy can sleep, it can't be used from call_rcu callbacks. Moreover, nf_tables_rule_release() is only safe for error unwinding, while transaction mutex is held and the to-be-desroyed rule was not exposed to either dataplane or dumps, as it deactives+frees without the required synchronize_rcu() in-between. nft_rule_expr_deactivate() callbacks will change -\u003euse counters of other chains/sets, see e.g. nft_lookup .deactivate callback, these must be serialized via transaction mutex. Also add a few lockdep asserts to make this more explicit. Calling synchronize_rcu() isn't ideal, but fixing this without is hard and way more intrusive.  As-is, we can get: WARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x.. Workqueue: events nf_tables_trans_destroy_work RIP: 0010:nft_set_destroy+0x3fe/0x5c0 Call Trace:  \u003cTASK\u003e  nf_tables_trans_destroy_work+0x6b7/0xad0  process_one_work+0x64a/0xce0  worker_thread+0x613/0x10d0 In case the synchronize_rcu becomes an issue, we can explore alternatives. One way would be to allocate nft_trans_rule objects + one nft_trans_chain object, deactivate the rules + the chain and then defer the freeing to the nft destroy workqueue.  We'd still need to keep the synchronize_rcu path as a fallback to handle -ENOMEM corner cases though.","status":"published","published":"2024-12-27T15:15:00Z","modified":"2026-08-06T03:08:31.234845164Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"},{"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-02T16:55:15.331356Z"},{"id":"CLSA-2025-1757963029","title":"kernel-uek: Fix of 195 CVEs","description":"- rds: tcp: block BH in TCP callbacks\n- kexec: Improve \u0026 fix crash_exclude_mem_range() to handle overlapping ranges\n- module: correctly exit module_kallsyms_on_each_symbol when fn() != 0\n- module: potential uninitialized return in module_kallsyms_on_each_symbol()\n- module: use RCU to synchronize find_module\n- kallsyms: refactor {,module_}kallsyms_on_each_symbol\n- LTS tag: v5.4.295\n- scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops\n- arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth() {CVE-2025-38320}\n- perf: Fix sample vs do_exit() {CVE-2025-38424}\n- s390/pci: Fix __pcilg_mio_inuser() inline assembly\n- rtc: test: Fix invalid format specifier.\n- jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() {CVE-2025-38337}\n- mm/huge_memory: fix dereferencing invalid pmd migration entry {CVE-2025-37958}\n- rtc: Make rtc_time64_to_tm() support dates before 1970\n- rtc: Improve performance of rtc_time64_to_tm(). Add tests.\n- xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create {CVE-2022-48773}\n- posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() {CVE-2025-38352}\n- ARM: dts: am335x-bone-common: Increase MDIO reset deassert delay to 50ms\n- ARM: dts: am335x-bone-common: Increase MDIO reset deassert time\n- ARM: dts: am335x-bone-common: Add GPIO PHY reset on revision C3 board\n- net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}\n- net: atm: add lec_mutex {CVE-2025-38323}\n- calipso: Fix null-ptr-deref in calipso_req_{set,del}attr(). {CVE-2025-38181}\n- tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer {CVE-2025-38184}\n- tcp: fix tcp_packet_delayed() for tcp_is_non_sack_preventing_reopen() behavior\n- atm: atmtcp: Free invalid length skb in atmtcp_c_send(). {CVE-2025-38185}\n- mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu(). {CVE-2025-38324}\n- wifi: carl9170: do not ping device which has failed to load firmware {CVE-2025-38420}\n- aoe: clean device rq_list in aoedev_downdev() {CVE-2025-38326}\n- hwmon: (occ) fix unaligned accesses\n- drm/nouveau/bl: increase buffer size to avoid truncate warning\n- erofs: remove unused trace event erofs_destroy_inode\n- ALSA: hda/realtek: enable headset mic on Latitude 5420 Rugged\n- ALSA: hda/intel: Add Thinkpad E15 to PM deny list\n- Input: sparcspkr - avoid unannotated fall-through\n- HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() {CVE-2025-38103}\n- atm: Revert atm_account_tx() if copy_from_iter_full() fails. {CVE-2025-38190}\n- selinux: fix selinux_xfrm_alloc_user() to set correct ctx_len\n- scsi: s390: zfcp: Ensure synchronous unit_add\n- scsi: storvsc: Increase the timeouts to storvsc_timeout\n- jffs2: check jffs2_prealloc_raw_node_refs() result in few other places {CVE-2025-38328}\n- jffs2: check that raw node were preallocated before writing summary {CVE-2025-38194}\n- drivers/rapidio/rio_cm.c: prevent possible heap overwrite {CVE-2025-38090}\n- powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery\n- platform/x86: dell_rbu: Stop overwriting data buffer\n- platform: Add Surface platform directory\n- Revert \"bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first\"\n- tee: Prevent size calculation wraparound on 32-bit kernels\n- ARM: OMAP2+: Fix l4ls clk domain handling in STANDBY\n- bus: fsl-mc: increase MC_CMD_COMPLETION_TIMEOUT_MS value\n- watchdog: da9052_wdt: respect TWDMIN\n- i40e: fix MMIO write access to an invalid page in i40e_clear_hw {CVE-2025-38200}\n- sock: Correct error checking condition for (assign|release)_proto_idx()\n- scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}\n- vxlan: Do not treat dst cache initialization errors as fatal\n- clk: rockchip: rk3036: mark ddrphy as critical\n- wifi: mac80211: do not offer a mesh path if forwarding is disabled\n- net: mlx4: add SOF_TIMESTAMPING_TX_SOFTWARE flag when getting ts info\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get()\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_gpio_set_direction()\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get_direction()\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_set_by_name()\n- ipv4/route: Use this_cpu_inc() for stats on PREEMPT_RT\n- tcp: fix initial tp-\u003ercvq_space.space value for passive TS enabled flows\n- tcp: always seek for minimal rtt in tcp_rcv_rtt_update()\n- net: dlink: add synchronization for stats update\n- sctp: Do not wake readers in __sctp_write_space()\n- emulex/benet: correct command version selection in be_cmd_get_stats()\n- i2c: designware: Invoke runtime suspend on quick slave re-registration\n- net: macb: Check return value of dma_set_mask_and_coherent()\n- cpufreq: Force sync policy boost with global boost on sysfs update\n- nios2: force update_mmu_cache on spurious tlb-permission--related pagefaults\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() {CVE-2025-38237}\n- media: tc358743: ignore video while HPD is low\n- drm/amdkfd: Set SDMA_RLCx_IB_CNTL/SWITCH_INSIDE_IB\n- jfs: Fix null-ptr-deref in jfs_ioc_trim {CVE-2025-38203}\n- drm/amdgpu/gfx9: fix CSIB handling\n- drm/amdgpu/gfx8: fix CSIB handling\n- jfs: fix array-index-out-of-bounds read in add_missing_indices {CVE-2025-38204}\n- drm/amdgpu/gfx7: fix CSIB handling\n- drm/amdgpu/gfx10: fix CSIB handling\n- drm/msm/a6xx: Increase HFI response timeout\n- drm/amd/display: Add NULL pointer checks in dm_force_atomic_commit()\n- media: uapi: v4l: Fix V4L2_TYPE_IS_OUTPUT condition\n- drm/msm/hdmi: add runtime PM calls to DDC transfer function\n- drm/bridge: analogix_dp: Add irq flag IRQF_NO_AUTOEN instead of calling disable_irq()\n- sunrpc: update nextcheck time when adding new cache entries\n- drm/amdgpu/gfx6: fix CSIB handling\n- ACPI: battery: negate current when discharging\n- PM: runtime: fix denying of auto suspend in pm_suspend_timer_fn()\n- power: supply: bq27xxx: Retrieve again when busy\n- ACPICA: fix acpi parse and parseext cache leaks {CVE-2025-38344}\n- ACPICA: Avoid sequence overread in call to strncmp()\n- ACPICA: fix acpi operand cache leak in dswstate.c {CVE-2025-38345}\n- iio: adc: ad7606_spi: fix reg write value mask\n- PCI: Fix lock symmetry in pci_slot_unlock()\n- PCI: Add ACS quirk for Loongson PCIe\n- uio_hv_generic: Use correct size for interrupt and monitor pages\n- regulator: max14577: Add error check for max14577_read_reg()\n- mips: Add -std= flag specified in KBUILD_CFLAGS to vdso CFLAGS\n- staging: iio: ad5933: Correct settling cycles encoding per datasheet\n- net: ch9200: fix uninitialised access during mii_nway_restart {CVE-2025-38086}\n- ftrace: Fix UAF when lookup kallsym after ftrace disabled {CVE-2025-38346}\n- dm-mirror: fix a tiny race condition\n- mtd: nand: sunxi: Add randomizer configuration before randomizer enable\n- mtd: rawnand: sunxi: Add randomizer configuration in sunxi_nfc_hw_ecc_write_chunk\n- mm: fix ratelimit_pages update error in dirty_ratio_handler()\n- ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}\n- parisc: fix building with gcc-15\n- vgacon: Add check for vc_origin address range in vgacon_scroll() {CVE-2025-38213}\n- fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var {CVE-2025-38214}\n- EDAC/altera: Use correct write width with the INTTEST register\n- NFC: nci: uart: Set tty-\u003edisc_data only in success path {CVE-2025-38416}\n- f2fs: prevent kernel warning due to negative i_nlink from corrupted image {CVE-2025-38219}\n- Input: ims-pcu - check record size in ims_pcu_flash_firmware() {CVE-2025-38428}\n- ext4: fix calculation of credits for extent tree modification\n- ext4: inline: fix len overflow in ext4_prepare_inline_data {CVE-2025-38222}\n- bus: fsl-mc: do not add a device-link for the UAPI used DPMCP device\n- ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 {CVE-2025-38336}\n- ARM: 9447/1: arm/memremap: fix arch_memremap_can_ram_remap()\n- media: v4l2-dev: fix error handling in __video_register_device()\n- media: gspca: Add error handling for stv06xx_read_sensor()\n- wifi: rtlwifi: disable ASPM for RTL8723BE with subsystem ID 11ad:1723\n- nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request {CVE-2025-38430}\n- wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback() {CVE-2025-38348}\n- gfs2: move msleep to sleepable context\n- configfs: Do not override creating attribute file failure in populate_attrs()\n- net: usb: aqc111: debug info before sanitation\n- calipso: unlock rcu before returning -EAFNOSUPPORT\n- xen/arm: call uaccess_ttbr0_enable for dm_op hypercall\n- usb: Flush altsetting 0 endpoints before reinitializating them after reset.\n- fs/filesystems: Fix potential unsigned integer underflow in fs_name()\n- net/mdiobus: Fix potential out-of-bounds read/write access {CVE-2025-38111}\n- drm/amd/display: Do not add '-mhard-float' to dcn2{1,0}_resource.o for clang\n- drm/amd/display: Do not add '-mhard-float' to dml_ccflags for clang\n- MIPS: Move '-Wa,-msoft-float' check from as-option to cc-option\n- x86/boot/compressed: prefer cc-option for CFLAGS additions\n- net: mdio: C22 is now optional, EOPNOTSUPP if not provided\n- net_sched: tbf: fix a race in tbf_change()\n- net_sched: red: fix a race in __red_change() {CVE-2025-38108}\n- net_sched: prio: fix a race in prio_tune() {CVE-2025-38083}\n- net/mlx5: Fix return value when searching for existing flow group\n- net/mlx5: Wait for inactive autogroups\n- i40e: retry VFLR handling if there is ongoing VF reset\n- i40e: return false from i40e_reset_vf if reset is in progress\n- net_sched: sch_sfq: fix a potential crash on gso_skb handling {CVE-2025-38115}\n- scsi: iscsi: Fix incorrect error path labels for flashnode operations\n- NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes {CVE-2022-48829}\n- NFSD: Fix ia_size underflow {CVE-2022-48828}\n- Input: synaptics-rmi - fix crash with unsupported versions of F34\n- Input: synaptics-rmi4 - convert to use sysfs_emit() APIs\n- pmdomain: core: Fix error checking in genpd_dev_pm_attach_by_id()\n- do_change_type(): refuse to operate on unmounted/not ours mounts {CVE-2025-38498}\n- ice: create new Tx scheduler nodes for new queues only\n- Bluetooth: L2CAP: Fix not responding with L2CAP_CR_LE_ENCRYPTION\n- net/mlx4_en: Prevent potential integer overflow calculating Hz\n- vt: remove VT_RESIZE and VT_RESIZEX from vt_compat_ioctl()\n- serial: Fix potential null-ptr-deref in mlb_usio_probe() {CVE-2025-38135}\n- usb: renesas_usbhs: Reorder clock handling and power management in probe {CVE-2025-38136}\n- rtc: Fix offset calculation for .start_secs \u003c 0\n- rtc: sh: assign correct interrupts with DT\n- perf record: Fix incorrect --user-regs comments\n- perf tests switch-tracking: Fix timestamp comparison\n- mfd: stmpe-spi: Correct the name used in MODULE_DEVICE_TABLE\n- mfd: exynos-lpass: Avoid calling exynos_lpass_disable() twice in exynos_lpass_remove()\n- rpmsg: qcom_smd: Fix uninitialized return variable in __qcom_smd_send()\n- perf scripts python: exported-sql-viewer.py: Fix pattern matching with Python 3\n- perf ui browser hists: Set actions-\u003ethread before calling do_zoom_thread()\n- fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod() {CVE-2025-38312}\n- soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop() {CVE-2025-38145}\n- soc: aspeed: lpc: Fix impossible judgment condition\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on RK3399 Puma with Haikou\n- ARM: dts: qcom: apq8064 merge hw splinlock into corresponding syscon device\n- bus: fsl-mc: fix double-free on mc_dev {CVE-2025-38313}\n- nilfs2: do not propagate ENOENT error from nilfs_btree_propagate()\n- nilfs2: add pointer check for nilfs_direct_propagate()\n- Squashfs: check return result of sb_min_blocksize {CVE-2025-38415}\n- ARM: dts: at91: at91sam9263: fix NAND chip selects\n- ARM: dts: at91: usb_a9263: fix GPIO for Dataflash chip select\n- f2fs: fix to correct check conditions in f2fs_cross_rename\n- f2fs: use d_inode(dentry) cleanup dentry-\u003ed_inode\n- calipso: Don't call calipso functions for AF_INET sk. {CVE-2025-38147}\n- net: lan743x: rename lan743x_reset_phy to lan743x_hw_reset_phy\n- net: usb: aqc111: fix error handling of usbnet read calls {CVE-2025-38153}\n- netfilter: nf_tables: nft_fib_ipv6: fix VRF ipv4/ipv6 result discrepancy\n- wifi: ath9k_htc: Abort software beacon handling if disabled {CVE-2025-38157}\n- bpf: Fix WARN() in get_bpf_raw_tp_regs {CVE-2025-38285}\n- pinctrl: at91: Fix possible out-of-boundary access {CVE-2025-38286}\n- ktls, sockmap: Fix missing uncharge operation\n- netfilter: bridge: Move specific fragmented packet to slow_path instead of dropping it\n- f2fs: clean up w/ fscrypt_is_bounce_page()\n- RDMA/hns: Include hnae3.h in hns_roce_hw_v2.h\n- wifi: rtw88: do not ignore hardware read error during DPK\n- net: ncsi: Fix GCPS 64-bit member variables\n- f2fs: fix to do sanity check on sbi-\u003etotal_valid_block_count {CVE-2025-38163}\n- drm/tegra: rgb: Fix the unbound reference count\n- drm/vkms: Adjust vkms_state-\u003eactive_planes allocation type\n- drm: rcar-du: Fix memory leak in rcar_du_vsps_init()\n- selftests/seccomp: fix syscall_restart test for arm compat\n- firmware: psci: Fix refcount leak in psci_dt_init\n- m68k: mac: Fix macintosh_config for Mac II\n- drm/vmwgfx: Add seqno waiter for sync_files\n- spi: sh-msiof: Fix maximum DMA transfer size\n- ACPI: OSI: Stop advertising support for \"3.0 _SCP Extensions\"\n- x86/mtrr: Check if fixed-range MTRRs exist in mtrr_save_fixed_ranges()\n- PM: wakeup: Delete space in the end of string shown by pm_show_wakelocks()\n- EDAC/skx_common: Fix general protection fault {CVE-2025-38298}\n- crypto: marvell/cesa - Avoid empty transfer descriptor\n- crypto: marvell/cesa - Handle zero-length skcipher requests {CVE-2025-38173}\n- x86/cpu: Sanitize CPUID(0x80000000) output\n- perf/core: Fix broken throttling when max_samples_per_tick=1\n- gfs2: gfs2_create_inode error handling fix\n- netfilter: nft_socket: fix sk refcount leaks {CVE-2024-46855}\n- thunderbolt: Do not double dequeue a configuration request {CVE-2025-38174}\n- usb: usbtmc: Fix timeout value in get_stb\n- usb: storage: Ignore UAS driver for SanDisk 3.2 Gen2 storage device\n- usb: quirks: Add NO_LPM quirk for SanDisk Extreme 55AE\n- pinctrl: armada-37xx: set GPIO output value before setting direction\n- pinctrl: armada-37xx: use correct OUTPUT_VAL register for GPIOs \u003e 31\n- net/mlx5: Add poll-eq API to be used by ULP's\n- net/rds: poll eq during user-reset\n- perf: Fix perf_event_validate_size() lockdep splat {CVE-2023-6931}\n- perf: Fix perf_event_validate_size() {CVE-2023-6931}\n- net/mlx5: set graceful_period to 0 to allow multiple transmission queue recovery\n- pwm: mediatek: Ensure to disable clocks in error path\n- Revert \"mmc: sdhci: Disable SD card clock before changing parameters\"\n- net/sched: Always pass notifications when child class becomes empty {CVE-2025-38350}\n- x86/bpf: Classic BPF program can fail when BHB barrier is used\n- Add Zen34 clients {CVE-2024-36350}\n- x86/process: Move the buffer clearing before MONITOR {CVE-2024-36350}\n- KVM: SVM: Advertize TSA CPUID bits to guests {CVE-2024-36350}\n- x86/bugs: Add a Transient Scheduler Attacks mitigation {CVE-2024-36350}\n- KVM: x86: add support for CPUID leaf 0x80000021 {CVE-2024-36350}\n- x86/bugs: Rename MDS machinery to something more generic {CVE-2024-36350}\n- x86/CPU/AMD: Add ZenX generations flags {CVE-2024-36350}\n- x86/bugs: Free X86_BUG_AMD_APIC_C1E and X86_BUG_AMD_E400 bits {CVE-2024-36350}\n- Revert \"x86/bugs: Make spectre user default depend on MITIGATION_SPECTRE_V2\" on v6.6 and older\n- tracing: Fix compilation warning on arm32\n- PM: sleep: Fix power.is_suspended cleanup for direct-complete devices\n- LTS tag: v5.4.294\n- platform/x86: thinkpad_acpi: Ignore battery threshold change event notification\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys\n- spi: spi-sun4i: fix early activation\n- um: let 'make clean' properly clean underlying SUBARCH as well\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS\n- nfs: don't share pNFS DS connections between net namespaces\n- HID: quirks: Add ADATA XPG alpha wireless mouse support\n- coredump: hand a pidfd to the usermode coredump helper\n- fork: use pidfd_prepare()\n- pid: add pidfd_prepare()\n- pidfd: check pid has attached task in fdinfo\n- coredump: fix error handling for replace_fd()\n- net_sched: hfsc: Address reentrant enqueue adding class to eltree twice {CVE-2025-38001}\n- smb: client: Reset all search buffer pointers when releasing buffer\n- smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}\n- drm/i915/gvt: fix unterminated-string-initialization warning\n- netfilter: nf_tables: do not defer rule destruction via call_rcu {CVE-2024-56655}\n- netfilter: nf_tables: wait for rcu grace period on net_device removal {CVE-2024-56655}\n- netfilter: nf_tables: pass nft_chain to destroy function, not nft_ctx\n- kbuild: Disable -Wdefault-const-init-unsafe\n- spi: spi-fsl-dspi: restrict register range for regmap access\n- mm/page_alloc.c: avoid infinite retries caused by cpuset race\n- drm/edid: fixed the bug that hdr metadata was not reset\n- llc: fix data loss when reading from a socket in llc_ui_recvmsg()\n- ALSA: pcm: Fix race of buffer access at PCM OSS layer {CVE-2025-38078}\n- can: bcm: add missing rcu read protection for procfs content {CVE-2025-38003}\n- can: bcm: add locking for bcm_op runtime updates {CVE-2025-38004}\n- crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}\n- sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() {CVE-2025-38000}\n- net: dwmac-sun8i: Use parsed internal PHY address instead of 1\n- bridge: netfilter: Fix forwarding of fragmented packets\n- xfrm: Sanitize marks before insert\n- __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock {CVE-2025-38058}\n- xenbus: Allow PVH dom0 a non-local xenstore\n- btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref {CVE-2025-38034}\n- nvmet-tcp: don't restore null sk_state_change {CVE-2025-38035}\n- ASoC: Intel: bytcr_rt5640: Add DMI quirk for Acer Aspire SW3-013\n- pinctrl: meson: define the pull up/down resistor value as 60 kOhm\n- drm: Add valid clones check\n- drm/atomic: clarify the rules around drm_atomic_state-\u003eallow_modeset\n- regulator: ad5398: Add device tree support\n- wifi: rtw88: Don't use static local variable in rtw8822b_set_tx_power_index_by_rate\n- bpftool: Fix readlink usage in get_fd_type\n- HID: usbkbd: Fix the bit shift number for LED_KANA\n- scsi: st: Restore some drive settings after reset\n- scsi: lpfc: Handle duplicate D_IDs in ndlp search-by D_ID routine\n- rcu: fix header guard for rcu_all_qs()\n- rcu: handle quiescent states for PREEMPT_RCU=n, PREEMPT_COUNT=y\n- vxlan: Annotate FDB data races {CVE-2025-38037}\n- hwmon: (xgene-hwmon) use appropriate type for the latency value\n- ip: fib_rules: Fetch net from fib_rule in fib[46]_rule_configure().\n- net/mlx5e: reduce rep rxq depth to 256 for ECPF\n- net/mlx5e: set the tx_queue_len for pfifo_fast\n- net/mlx5: Extend Ethtool loopback selftest to support non-linear SKB\n- phy: core: don't require set_mode() callback for phy_get_mode() to work\n- net/mlx4_core: Avoid impossible mlx4_db_alloc() order value\n- smack: recognize ipv4 CIPSO w/o categories\n- pinctrl: devicetree: do not goto err when probing hogs in pinctrl_dt_to_map\n- ASoC: ops: Enforce platform maximum on initial value\n- net/mlx5: Apply rate-limiting to high temperature warning\n- net/mlx5: Modify LSB bitmask in temperature event to include only the first bit\n- ACPI: HED: Always initialize before evged\n- PCI: Fix old_size lower bound in calculate_iosize() too\n- EDAC/ie31200: work around false positive build warning\n- net: pktgen: fix access outside of user given buffer in pktgen_thread_write() {CVE-2025-38061}\n- wifi: rtw88: Fix rtw_init_ht_cap() for RTL8814AU\n- scsi: mpt3sas: Send a diag reset if target reset fails\n- MIPS: pm-cps: Use per-CPU variables as per-CPU, not per-core\n- MIPS: Use arch specific syscall name match function\n- cpuidle: menu: Avoid discarding useful information\n- x86/nmi: Add an emergency handler in nmi_desc \u0026 use it in nmi_shootdown_cpus()\n- bonding: report duplicate MAC address in all situations\n- net: xgene-v2: remove incorrect ACPI_PTR annotation\n- drm/amdkfd: KFD release_work possible circular locking\n- net/mlx5: Avoid report two health errors on same syndrome\n- fpga: altera-cvp: Increase credit timeout\n- drm/mediatek: mtk_dpi: Add checks for reg_h_fre_con existence\n- hwmon: (gpio-fan) Add missing mutex locks\n- x86/bugs: Make spectre user default depend on MITIGATION_SPECTRE_V2\n- net: pktgen: fix mpls maximum labels list parsing\n- pinctrl: bcm281xx: Use \"unsigned int\" instead of bare \"unsigned\"\n- media: cx231xx: set device_caps for 417 {CVE-2025-38044}\n- orangefs: Do not truncate file size {CVE-2025-38065}\n- dm cache: prevent BUG_ON by blocking retries on failed device resumes {CVE-2025-38066}\n- media: c8sectpfe: Call of_node_put(i2c_bus) only once in c8sectpfe_probe()\n- ARM: tegra: Switch DSI-B clock parent to PLLD on Tegra114\n- ieee802154: ca8210: Use proper setters and getters for bitwise types\n- rtc: ds1307: stop disabling alarms on probe\n- powerpc/prom_init: Fixup missing #size-cells on PowerBook6,7\n- mmc: sdhci: Disable SD card clock before changing parameters\n- netfilter: conntrack: Bound nf_conntrack sysctl writes\n- posix-timers: Add cond_resched() to posix_timer_add() search loop\n- xen: Add support for XenServer 6.1 platform device {CVE-2025-38046}\n- dm: restrict dm device size to 2^63-512 bytes\n- kbuild: fix argument parsing in scripts/config\n- scsi: st: ERASE does not change tape location\n- scsi: st: Tighten the page format heuristics with MODE SELECT\n- ext4: reorder capability check last\n- um: Update min_low_pfn to match changes in uml_reserved\n- um: Store full CSGSFS and SS register from mcontext\n- btrfs: send: return -ENAMETOOLONG when attempting a path that is too long\n- btrfs: avoid linker error in btrfs_find_create_tree_block()\n- i2c: pxa: fix call balance of i2c-\u003eclk handling routines\n- mmc: host: Wait for Vdd to settle on card power off\n- libnvdimm/labels: Fix divide error in nd_label_data_init() {CVE-2025-38072}\n- pNFS/flexfiles: Report ENETDOWN as a connection error\n- tools/build: Don't pass test log files to linker\n- dql: Fix dql-\u003elimit value when reset.\n- SUNRPC: rpc_clnt_set_transport() must not change the autobind setting\n- NFSv4: Treat ENETUNREACH errors as fatal for state recovery\n- fbdev: core: tileblit: Implement missing margin clearing for tileblit\n- fbdev: fsl-diu-fb: add missing device_remove_file()\n- mailbox: use error ret code of of_parse_phandle_with_args()\n- kconfig: merge_config: use an empty file as initfile\n- cgroup: Fix compilation issue due to cgroup_mutex not being exported\n- dma-mapping: avoid potential unused data compilation warning\n- scsi: target: iscsi: Fix timeout on deleted connection {CVE-2025-38075}\n- openvswitch: Fix unsafe attribute parsing in output_userspace() {CVE-2025-37998}\n- Input: synaptics - enable InterTouch on TUXEDO InfinityBook Pro 14 v5\n- Input: synaptics - enable SMBus for HP Elitebook 850 G1\n- clocksource/i8253: Use raw_spinlock_irqsave() in clockevent_i8253_disable()\n- phy: renesas: rcar-gen3-usb2: Set timing registers only once\n- phy: Fix error handling in tegra_xusb_port_init\n- ALSA: es1968: Add error handling for snd_pcm_hw_constraint_pow2()\n- NFSv4/pnfs: Reset the layout state after a layoutreturn\n- NFSv4/pnfs: pnfs_set_layout_stateid() should update the layout cred\n- qlcnic: fix memory leak in qlcnic_sriov_channel_cfg_cmd()\n- ALSA: sh: SND_AICA should depend on SH_DMA_API\n- net: dsa: sja1105: discard incoming frames in BR_STATE_LISTENING\n- spi: loopback-test: Do not split 1024-byte hexdumps\n- nfs: handle failure of nfs_get_lock_context in unlock path {CVE-2025-38023}\n- RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug {CVE-2025-38024}\n- iio: chemical: sps30: use aligned_s64 for timestamp\n- iio: adc: ad7768-1: Fix insufficient alignment of timestamp.\n- staging: axis-fifo: Correct handling of tx_fifo_depth for size validation\n- staging: axis-fifo: avoid parsing ignored device tree properties\n- staging: axis-fifo: Remove hardware resets for user errors\n- staging: axis-fifo: replace spinlock with mutex\n- platform/x86: asus-wmi: Fix wlan_ctrl_by_user detection\n- do_umount(): add missing barrier before refcount checks in sync case\n- MIPS: Fix MAX_REG_OFFSET\n- iio: adc: dln2: Use aligned_s64 for timestamp\n- types: Complement the aligned types with signed 64-bit one\n- usb: usbtmc: Fix erroneous generic_read ioctl return\n- usb: usbtmc: Fix erroneous wait_srq ioctl return\n- usb: usbtmc: Fix erroneous get_stb ioctl error returns\n- USB: usbtmc: use interruptible sleep in usbtmc_read\n- usb: typec: ucsi: displayport: Fix NULL pointer access {CVE-2025-37994}\n- usb: typec: tcpm: delay SNK_TRY_WAIT_DEBOUNCE to SRC_TRYWAIT transition\n- ocfs2: stop quota recovery before disabling quotas\n- ocfs2: implement handshaking with ocfs2 recovery thread\n- ocfs2: switch osb-\u003edisable_recovery to enum\n- module: ensure that kobject_put() is safe for module type kobjects {CVE-2025-37995}\n- xenbus: Use kref to track req lifetime {CVE-2025-37949}\n- usb: uhci-platform: Make the clock really optional\n- iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_tagged_fifo {CVE-2025-37969}\n- iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_fifo {CVE-2025-37970}\n- iio: adis16201: Correct inclinometer channel resolution\n- iio: adc: ad7606: fix serial register access\n- staging: iio: adc: ad7816: Correct conditional logic for store mode\n- Input: synaptics - enable InterTouch on Dell Precision M3800\n- Input: synaptics - enable InterTouch on Dynabook Portege X30L-G\n- Input: synaptics - enable InterTouch on Dynabook Portege X30-D\n- net: dsa: b53: fix learning on VLAN unaware bridges\n- netfilter: ipset: fix region locking in hash types {CVE-2025-37997}\n- sch_htb: make htb_deactivate() idempotent {CVE-2025-37953}\n- dm: fix copying after src array boundaries {CVE-2025-37902}\n- iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid {CVE-2025-37927}\n- arm64: dts: rockchip: fix iface clock-name on px30 iommus\n- usb: chipidea: ci_hdrc_imx: implement usb_phy_init() error handling\n- usb: chipidea: ci_hdrc_imx: use dev_err_probe()\n- usb: chipidea: imx: refine the error handling for hsic\n- usb: chipidea: imx: change hsic power regulator as optional\n- irqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode() {CVE-2025-37819}\n- irqchip/gic-v2m: Mark a few functions __init\n- irqchip/gic-v2m: Add const to of_device_id\n- sch_htb: make htb_qlen_notify() idempotent {CVE-2025-37953}\n- of: module: add buffer overflow check in of_modalias() {CVE-2024-38541}\n- PCI: imx6: Skip controller_id generation logic for i.MX7D\n- net: fec: ERR007885 Workaround for conventional TX\n- net: lan743x: Fix memleak issue when GSO enabled {CVE-2025-37909}\n- lan743x: fix endianness when accessing descriptors\n- lan743x: remove redundant initialization of variable current_head_index\n- nvme-tcp: fix premature queue removal and I/O failover\n- net: dlink: Correct endianness handling of led_mode\n- net_sched: qfq: Fix double list add in class with netem as child qdisc {CVE-2025-37913}\n- net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc {CVE-2025-37890}\n- net_sched: drr: Fix double list add in class with netem as child qdisc {CVE-2025-37915}\n- net/mlx5: E-Switch, Initialize MAC Address for Default GID\n- tracing: Fix oob write in trace_seq_to_buffer() {CVE-2025-37923}\n- dm: always update the array size in realloc_argv on success {CVE-2025-37902}\n- dm-integrity: fix a warning on invalid table line\n- wifi: brcm80211: fmac: Add error handling for brcmf_usb_dl_writeimage() {CVE-2025-37990}\n- amd-xgbe: Fix to ensure dependent features are toggled with RX checksum offload\n- parisc: Fix double SIGFPE crash {CVE-2025-37991}\n- i2c: imx-lpi2c: Fix clock count when probe defers\n- EDAC/altera: Set DDR and SDMMC interrupt mask before registration\n- EDAC/altera: Test the correct error reg offset\n- scsi: qedf: Wait for stag work during unload\n- scsi: qedf: Don't process stag work during unload and recovery\n- rds: ib: Add cm_id generation scheme in order to detect new ones\n- x86/its: BPF can crash in bpf_jit_comp.c when ITS is enabled\n- shmem: add support to ignore swap\n- shmem: update documentation\n- mm: hold the source mmap write lock when copying PTEs\n- mm: do not write protect COW mappings when preserving across exec\n- mm: differentiate copying PTEs for preservation from copying for fork\n- mm/fork: Pass new vma pointer into copy_page_range()\n- xen/swiotlb: relax alignment requirements\n- Reapply \"xen/swiotlb: add alignment check for dma buffers\"\n- dmaengine: Revert \"dmaengine: dmatest: Fix dmatest waiting less when interrupted\"\n- nvme: unblock ctrl state transition for firmware update\n- memcg: always call cond_resched() after fn()\n- ACPI: PPTT: Fix processor subtable walk\n- LTS tag: v5.4.293\n- MIPS: cm: Fix warning if MIPS_CM is disabled\n- crypto: atmel-sha204a - Set hwrng quality to lowest possible\n- comedi: jr3_pci: Fix synchronous deletion of timer\n- md/raid1: Add check for missing source disk in process_checks()\n- scsi: pm80xx: Set phy_attached to zero when device is gone\n- ACPI PPTT: Fix coding mistakes in a couple of sizeof() calls\n- selftests: ublk: fix test_stripe_04\n- udmabuf: fix a buf size overflow issue during udmabuf creation {CVE-2025-37803}\n- KVM: s390: Don't use %pK through tracepoints\n- sched/isolation: Make CONFIG_CPU_ISOLATION depend on CONFIG_SMP\n- ntb: reduce stack usage in idt_scan_mws\n- qibfs: fix _another_ leak {CVE-2025-37983}\n- usb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev() {CVE-2025-37881}\n- dmaengine: dmatest: Fix dmatest waiting less when interrupted\n- usb: host: max3421-hcd: Add missing spi_device_id table\n- parisc: PDT: Fix missing prototype warning\n- clk: check for disabled clock-provider in of_clk_get_hw_from_clkspec()\n- crypto: null - Use spin lock instead of mutex {CVE-2025-37808}\n- MIPS: cm: Detect CM quirks from device tree\n- USB: VLI disk crashes if LPM is used\n- usb: quirks: Add delay init quirk for SanDisk 3.2Gen1 Flash Drive\n- usb: quirks: add DELAY_INIT quirk for Silicon Motion Flash Drive\n- usb: dwc3: gadget: check that event count does not exceed event buffer length {CVE-2025-37810}\n- USB: OHCI: Add quirk for LS7A OHCI controller (rev 0x02)\n- usb: cdns3: Fix deadlock when using NCM gadget {CVE-2025-37812}\n- USB: serial: simple: add OWON HDS200 series oscilloscope support\n- USB: serial: option: add Sierra Wireless EM9291\n- USB: serial: ftdi_sio: add support for Abacus Electrics Optical Probe\n- serial: sifive: lock port in startup()/shutdown() callbacks\n- USB: storage: quirk for ADATA Portable HDD CH94\n- mcb: fix a double free bug in chameleon_parse_gdd() {CVE-2025-37817}\n- virtio_console: fix missing byte order handling for cols and rows\n- net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}\n- net_sched: hfsc: Fix a UAF vulnerability in class handling {CVE-2025-37797}\n- tipc: fix NULL pointer dereference in tipc_mon_reinit_self() {CVE-2025-37824}\n- net: phy: leds: fix memory leak {CVE-2025-37989}\n- cpufreq: scpi: Fix null-ptr-deref in scpi_cpufreq_get_rate() {CVE-2025-37829}\n- drm/amd/pm: Prevent division by zero {CVE-2025-37766}\n- misc: pci_endpoint_test: Fix displaying 'irq_type' after 'request_irq' error\n- misc: pci_endpoint_test: Use INTX instead of LEGACY\n- PCI: Rename PCI_IRQ_LEGACY to PCI_IRQ_INTX\n- iio: adc: ad7768-1: Fix conversion result sign\n- iio: adc: ad7768-1: Move setting of val a bit later to avoid unnecessary return value check\n- net: dsa: mv88e6xxx: fix VTU methods for 6320 family\n- media: vim2m: print device name after registering device\n- ext4: fix OOB read when checking dotdot dir {CVE-2025-37785}\n- ext4: optimize __ext4_check_dir_entry()\n- ext4: don't over-report free space or inodes in statvfs\n- ext4: code cleanup for ext4_statfs_project()\n- ext4: simplify checking quota limits in ext4_statfs()\n- platform/x86: ISST: Correct command storage data length\n- MIPS: ds1287: Match ds1287_set_base_clock() function types\n- MIPS: cevt-ds1287: Add missing ds1287.h include\n- MIPS: dec: Declare which_prom() as static\n- virtio-net: Add validation for used length {CVE-2021-47352}\n- RDMA/srpt: Support specifying the srpt_service_guid parameter {CVE-2024-26744}\n- openvswitch: fix lockup on tx to unregistering netdev with carrier {CVE-2025-21681}\n- net: openvswitch: fix race on port output {CVE-2025-21681}\n- mmc: cqhci: Fix checking of CQHCI_HALT state\n- nvmet-fc: Remove unused functions\n- usb: dwc3: support continuous runtime PM with dual role\n- misc: pci_endpoint_test: Fix 'irq_type' to convey the correct type\n- misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error {CVE-2025-23140}\n- tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). {CVE-2024-50154}\n- powerpc/prom_init: Use -ffreestanding to avoid a reference to bcmp\n- kbuild: Add '-fno-builtin-wcslen'\n- cpufreq: Reference count policy in cpufreq_update_limits()\n- drm/sti: remove duplicate object names\n- drm/nouveau: prime: fix ttm_bo_delayed_delete oops {CVE-2025-37765}\n- drm/repaper: fix integer overflows in repeat functions\n- module: sign with sha512 instead of sha1 by default\n- perf/x86/intel/uncore: Fix the scale of IIO free running counters on SNR\n- perf/x86/intel: Allow to update user space GPRs from PEBS records\n- virtiofs: add filesystem context source name check {CVE-2025-37773}\n- riscv: Avoid fortify warning in syscall_get_arguments()\n- isofs: Prevent the use of too small fid {CVE-2025-37780}\n- i2c: cros-ec-tunnel: defer probe if parent EC is not present {CVE-2025-37781}\n- hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key {CVE-2025-37782}\n- btrfs: correctly escape subvol in btrfs_show_options()\n- nfs: add missing selections of CONFIG_CRC32\n- nfs: move nfs_fhandle_hash to common include file\n- NFSD: Constify @fh argument of knfsd_fh_hash()\n- asus-laptop: Fix an uninitialized variable\n- writeback: fix false warning in inode_to_wb()\n- net: b53: enable BPDU reception for management port\n- net: openvswitch: fix nested key length validation in the set() action {CVE-2025-37789}\n- Revert \"wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()\" {CVE-2025-37795}\n- Bluetooth: btrtl: Prevent potential NULL dereference {CVE-2025-37792}\n- Bluetooth: hci_event: Fix sending MGMT_EV_DEVICE_FOUND for invalid address\n- RDMA/usnic: Fix passing zero to PTR_ERR in usnic_ib_pci_probe()\n- scsi: iscsi: Fix missing scsi_host_put() in error path\n- wifi: wl1251: fix memory leak in wl1251_tx_work {CVE-2025-37982}\n- wifi: mac80211: Purge vif txq in ieee80211_do_stop() {CVE-2025-37794}\n- wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue() {CVE-2025-37795}\n- wifi: at76c50x: fix use after free access in at76_disconnect {CVE-2025-37796}\n- HSI: ssi_protocol: Fix use after free vulnerability in ssi_protocol Driver Due to Race Condition {CVE-2025-37838}\n- pwm: mediatek: always use bus clock for PWM on MT7622\n- Bluetooth: hci_uart: Fix another race during initialization {CVE-2025-23139}\n- x86/e820: Fix handling of subpage regions when calculating nosave ranges in e820__register_nosave_regions()\n- PCI: Fix reference leak in pci_alloc_child_bus()\n- of/irq: Fix device node refcount leakages in of_irq_init()\n- of/irq: Fix device node refcount leakage in API irq_of_parse_and_map()\n- of/irq: Fix device node refcount leakages in of_irq_count()\n- ntb: use 64-bit arithmetic for the MSI doorbell mask\n- gpio: zynq: Fix wakeup source leaks on device unbind\n- ftrace: Add cond_resched() to ftrace_graph_set_hash() {CVE-2025-37940}\n- dm-integrity: set ti-\u003eerror on memory allocation failure\n- crypto: ccp - Fix check for the primary ASP device\n- thermal/drivers/rockchip: Add missing rk3328 mapping entry\n- sctp: detect and prevent references to a freed transport in sendmsg {CVE-2025-23142}\n- mm: add missing release barrier on PGDAT_RECLAIM_LOCKED unlock\n- sparc/mm: disable preemption in lazy mmu mode\n- arm64: dts: mediatek: mt8173: Fix disp-pwm compatible string\n- mtd: rawnand: Add status chack in r852_ready()\n- mtd: inftlcore: Add error check for inftl_read_oob() {CVE-2025-37892}\n- lib: scatterlist: fix sg_split_phys to preserve original scatterlist offsets\n- locking/lockdep: Decrease nr_unused_locks if lock unused in zap_class()\n- jbd2: remove wrong sb-\u003es_sequence check {CVE-2025-37839}\n- i3c: Add NULL pointer check in i3c_master_queue_ibi() {CVE-2025-23147}\n- ext4: fix off-by-one error in do_split {CVE-2025-23150}\n- wifi: mac80211: fix integer overflow in hwmp_route_info_get()\n- net: dsa: mv88e6xxx: workaround RGMII transmit delay erratum for 6320 family\n- media: venus: hfi_parser: add check to avoid out of bound access {CVE-2025-23157}\n- media: i2c: ov7251: Introduce 1 ms delay between regulators and en GPIO\n- media: i2c: ov7251: Set enable GPIO low in probe\n- media: v4l2-dv-timings: prevent possible overflow in v4l2_detect_gtf()\n- media: streamzap: prevent processing IR data on URB failure\n- mtd: rawnand: brcmnand: fix PM resume warning {CVE-2025-37840}\n- arm64: cputype: Add MIDR_CORTEX_A76AE\n- xenfs/xensyms: respect hypervisor's \"next\" indication\n- media: siano: Fix error handling in smsdvb_module_init()\n- media: venus: hfi: add check to handle incorrect queue size {CVE-2025-23158}\n- media: venus: hfi: add a check to handle OOB in sfr region {CVE-2025-23159}\n- media: i2c: adv748x: Fix test pattern selection mask\n- ext4: don't treat fhandle lookup of ea_inode as FS corruption\n- ext4: reject casefold inode flag without casefold feature\n- bpf: support SKF_NET_OFF and SKF_LL_OFF on skb frags\n- bpf: Add endian modifiers to fix endian warnings\n- pwm: fsl-ftm: Handle clk_get_rate() returning 0\n- pwm: mediatek: Prevent divide-by-zero in pwm_mediatek_config() {CVE-2025-37850}\n- pwm: mediatek: Always use bus clock\n- fbdev: omapfb: Add 'plane' value check {CVE-2025-37851}\n- drm/mediatek: mtk_dpi: Explicitly manage TVD clock in power on/off\n- drm/amdkfd: Fix pqm_destroy_queue race with GPU reset\n- drm/amdkfd: clamp queue size to minimum\n- drm: panel-orientation-quirks: Add new quirk for GPD Win 2\n- drm: panel-orientation-quirks: Add support for AYANEO 2S\n- drm: allow encoder mode_set even when connectors change for crtc\n- Bluetooth: hci_uart: fix race during initialization {CVE-2025-23139}\n- tracing: fix return value in __ftrace_event_enable_disable for TRACE_REG_UNREGISTER\n- net: vlan: don't propagate flags on open {CVE-2025-23163}\n- wifi: mt76: mt76x2u: add TP-Link TL-WDN6200 ID to device table\n- scsi: st: Fix array overflow in st_setup() {CVE-2025-37857}\n- ext4: ignore xattrs past end {CVE-2025-37738}\n- ext4: protect ext4_release_dquot against freezing\n- ahci: add PCI ID for Marvell 88SE9215 SATA Controller\n- ata: libata-eh: Do not use ATAPI DMA for a device limited to PIO mode\n- jfs: add sanity check for agwidth in dbMount {CVE-2025-37740}\n- jfs: Prevent copying of nlink with value 0 from disk inode {CVE-2025-37741}\n- fs/jfs: Prevent integer overflow in AG size calculation {CVE-2025-37858}\n- fs/jfs: cast inactags to s64 to prevent potential overflow\n- page_pool: avoid infinite loop to schedule delayed worker {CVE-2025-37859}\n- ALSA: usb-audio: Fix CME quirk for UF series keyboards\n- ALSA: hda: intel: Fix Optimus when GPU has no sound\n- HID: pidff: Fix null pointer dereference in pidff_find_fields {CVE-2025-37862}\n- HID: pidff: Do not send effect envelope if it's empty\n- HID: pidff: Convert infinite length from Linux API to PID standard\n- xen/mcelog: Add __nonstring annotations for unterminated strings\n- perf: arm_pmu: Don't disable counter in armpmu_add()\n- x86/cpu: Don't clear X86_FEATURE_LAHF_LM flag in init_amd_k8() on AMD when running in a virtual machine\n- pm: cpupower: bench: Prevent NULL dereference on malloc failure {CVE-2025-37841}\n- net: ppp: Add bound checking for skb data on ppp_sync_txmung {CVE-2025-37749}\n- ata: sata_sx4: Add error handling in pdc20621_i2c_read()\n- ata: sata_sx4: Drop pointless VPRINTK() calls and convert the remaining ones\n- tipc: fix memory leak in tipc_link_xmit {CVE-2025-37757}\n- ata: pata_pxa: Fix potential NULL pointer dereference in pxa_ata_probe() {CVE-2025-37758}\n- x86/bhi: Do not set BHI_DIS_S in 32-bit mode\n- x86/bpf: Add IBHF call at end of classic BPF\n- x86/bpf: Call branch history clearing sequence on exit\n- certs: Reference revocation list for all keyrings\n- RDS: use get_user_pages_fast() in rdma_pin_pages()\n- x86/bugs: Enabling Retbleed and SRSO mitigation can taint the kernel\n- selftest/x86/bugs: Add selftests for ITS {CVE-2024-28956}\n- x86/its: Align RETs in BHB clear sequence to avoid thunking {CVE-2024-28956}\n- x86/its: Add \"vmexit\" option to skip mitigation on some CPUs {CVE-2024-28956}\n- x86/its: Enable Indirect Target Selection mitigation {CVE-2024-28956}\n- x86/its: Add support for ITS-safe return thunk {CVE-2024-28956}\n- x86/its: Add support for ITS-safe indirect thunk {CVE-2024-28956}\n- x86/its: Enumerate Indirect Target Selection (ITS) bug {CVE-2024-28956}\n- Documentation: x86/bugs/its: Add ITS documentation {CVE-2024-28956}\n- certs: Add new Oracle Linux Driver Signing (key 1) certificate\n- net/mlx5e: Don't call cleanup on profile rollback failure {CVE-2024-50146}\n- net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() {CVE-2024-50000}\n- net/mlx5: Fix error path in multi-packet WQE transmit {CVE-2024-50001}\n- net/mlx5: Discard command completions in internal error {CVE-2024-38555}\n- net/mlx5e: fix a potential double-free in fs_any_create_groups {CVE-2023-52667}\n- net/mlx5: Reclaim max 50K pages at once\n- LTS tag: v5.4.292\n- jfs: add index corruption check to DT_GETPAGE()\n- tracing: Fix use-after-free in print_graph_function_flags during tracer switching {CVE-2025-22035}\n- mmc: sdhci-pxav3: set NEED_RSP_BUSY capability\n- ACPI: resource: Skip IRQ override on ASUS Vivobook 14 X1404VAP\n- x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs {CVE-2025-22045}\n- x86/tsc: Always save/restore TSC sched_clock() on suspend/resume\n- ntb_perf: Delete duplicate dmaengine_unmap_put() call in perf_copy_chunk()\n- can: flexcan: only change CAN state when link up in system PM\n- arcnet: Add NULL check in com20020pci_probe() {CVE-2025-22054}\n- net: dsa: mv88e6xxx: propperly shutdown PPU re-enable timer on destroy\n- ipv6: fix omitted netlink attributes when using RTEXT_FILTER_SKIP_STATS\n- vsock: avoid timeout during connect() if the socket is closing\n- net_sched: skbprio: Remove overly strict queue assertions {CVE-2025-38637}\n- netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets {CVE-2025-22063}\n- ntb: intel: Fix using link status DB's\n- ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans {CVE-2023-53034}\n- spufs: fix a leak in spufs_create_context() {CVE-2025-22071}\n- spufs: fix a leak on spufs_new_file() failure {CVE-2025-22073}\n- hwmon: (nct6775-core) Fix out of bounds access for NCT679{8,9}\n- can: statistics: use atomic access in hot path\n- locking/semaphore: Use wake_q to wake up processes outside lock critical section\n- sched/deadline: Use online cpus for validating runtime\n- affs: don't write overlarge OFS data block size fields\n- affs: generate OFS sequence numbers starting at 1\n- wifi: iwlwifi: fw: allocate chained SG tables for dump\n- sched/smt: Always inline sched_smt_active()\n- octeontx2-af: Fix mbox INTR handler when num VFs \u003e 64\n- ring-buffer: Fix bytes_dropped calculation issue\n- objtool, media: dib8000: Prevent divide-by-zero in dib8000_set_dds() {CVE-2025-37937}\n- fs/procfs: fix the comment above proc_pid_wchan()\n- perf python: Check if there is space to copy all the event\n- perf python: Decrement the refcount of just created event on failure\n- perf python: Fixup description of sample.id event member\n- ocfs2: validate l_tree_depth to avoid out-of-bounds access {CVE-2025-22079}\n- kexec: initialize ELF lowest address to ULONG_MAX\n- perf units: Fix insufficient array space\n- iio: accel: mma8452: Ensure error return on failure to matching oversampling ratio\n- coresight: catu: Fix number of pages while using 64k pages\n- isofs: fix KMSAN uninit-value bug in do_isofs_readdir()\n- x86/dumpstack: Fix inaccurate unwinding from exception stacks due to misplaced assignment\n- mfd: sm501: Switch to BIT() to mitigate integer overflows\n- RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow {CVE-2025-22086}\n- power: supply: max77693: Fix wrong conversion of charge input threshold value\n- x86/entry: Fix ORC unwinder for PUSH_REGS with save_ret=1\n- clk: amlogic: g12a: fix mmc A peripheral clock\n- clk: amlogic: gxbb: drop non existing 32k clock parent\n- clk: amlogic: g12b: fix cluster A parent data\n- IB/mad: Check available slots before posting receive WRs\n- clk: rockchip: rk3328: fix wrong clk_ref_usb3otg parent\n- pinctrl: renesas: rza2: Fix missing of_node_put() call\n- lib: 842: Improve error handling in sw842_compress()\n- clk: amlogic: gxbb: drop incorrect flag on 32k clock\n- fbdev: sm501fb: Add some geometry checks.\n- mdacon: rework dependency list\n- fbdev: au1100fb: Move a variable assignment behind a null pointer check\n- PCI: pciehp: Don't enable HPIE when resuming in poll mode\n- PCI: Remove stray put_device() in pci_register_host_bridge()\n- PCI/portdrv: Only disable pciehp interrupts early when needed\n- PCI/ASPM: Fix link state exit during switch upstream function removal {CVE-2024-58093}\n- drm/mediatek: mtk_hdmi: Fix typo for aud_sampe_size member\n- ALSA: hda/realtek: Always honor no_shutup_pins\n- perf/ring_buffer: Allow the EPOLLRDNORM flag for poll\n- lockdep: Don't disable interrupts on RT in disable_irq_nosync_lockdep.*()\n- PM: sleep: Fix handling devices with direct_complete set on errors\n- thermal: int340x: Add NULL check for adev {CVE-2025-23136}\n- EDAC/ie31200: Fix the error path order of ie31200_init()\n- EDAC/ie31200: Fix the DIMM size mask for several SoCs\n- EDAC/ie31200: Fix the size of EDAC_MC_LAYER_CHIP_SELECT layer\n- selinux: Chain up tool resolving errors in install_policy.sh\n- x86/platform: Only allow CONFIG_EISA for 32-bit\n- x86/fpu: Avoid copying dynamic FP state from init_task in arch_dup_task_struct()\n- cpufreq: governor: Fix negative 'idle_time' handling in dbs_update()\n- x86/mm/pat: cpa-test: fix length for CPA_ARRAY test\n- memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove {CVE-2025-22020}\n- net: usb: qmi_wwan: add Telit Cinterion FE990B composition\n- net: usb: qmi_wwan: add Telit Cinterion FN990B composition\n- tty: serial: 8250: Add some more device IDs\n- counter: stm32-lptimer-cnt: fix error handling when enabling\n- netfilter: socket: Lookup orig tuple for IPv6 SNAT {CVE-2025-22021}\n- ARM: Remove address checking for MMUless devices\n- ARM: 9351/1: fault: Add \"cut here\" line for prefetch aborts\n- ARM: 9350/1: fault: Implement copy_from_kernel_nofault_allowed()\n- atm: Fix NULL pointer dereference {CVE-2025-22018}\n- HID: hid-plantronics: Add mic mute mapping and generalize quirks\n- ALSA: usb-audio: Add quirk for Plantronics headsets to fix control names\n- drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse() {CVE-2025-21996}\n- batman-adv: Ignore own maximum aggregation size during RX\n- ARM: shmobile: smp: Enforce shmobile_smp_* alignment\n- mmc: atmel-mci: Add missing clk_disable_unprepare()\n- drm/v3d: Don't run jobs that have errors flagged in its fence\n- i2c: omap: fix IRQ storms\n- net/neighbor: add missing policy for NDTPA_QUEUE_LENBYTES\n- net: atm: fix use after free in lec_send() {CVE-2025-22004}\n- ipv6: Set errno after ip_fib_metrics_init() in ip6_route_info_create().\n- ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw(). {CVE-2025-22005}\n- Bluetooth: Fix error code in chan_alloc_skb_cb() {CVE-2025-22007}\n- RDMA/hns: Fix wrong value of max_sge_rd\n- RDMA/bnxt_re: Avoid clearing VLAN_ID mask in modify qp path\n- xfrm_output: Force software GSO only in tunnel mode\n- firmware: imx-scu: fix OF node leak in .probe()\n- i2c: sis630: Fix an error handling path in sis630_probe()\n- i2c: ali15x3: Fix an error handling path in ali15x3_probe()\n- i2c: ali1535: Fix an error handling path in ali1535_probe()\n- ASoC: codecs: wm0010: Fix error handling path in wm0010_spi_probe()\n- drm/gma500: Add NULL check for pci_gfx_root in mid_get_vbt_data()\n- qlcnic: fix memory leak issues in qlcnic_sriov_common.c\n- drm/amd/display: Assign normalized_pix_clk when color depth = 14 {CVE-2025-21956}\n- drm/atomic: Filter out redundant DPMS calls\n- x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes {CVE-2025-21991}\n- USB: serial: option: match on interface class for Telit FN990B\n- USB: serial: option: fix Telit Cinterion FE990A name\n- USB: serial: option: add Telit Cinterion FE990B compositions\n- USB: serial: ftdi_sio: add support for Altera USB Blaster 3\n- block: fix 'kmem_cache of name 'bio-108' already exists'\n- drm/nouveau: Do not override forced connector status\n- x86/irq: Define trace events conditionally\n- fuse: don't truncate cached, mutated symlink\n- nvme: only allow entering LIVE from CONNECTING state\n- sctp: Fix undefined behavior in left shift operation\n- nvmet-rdma: recheck queue state is LIVE in state lock in recv done\n- ASoC: rsnd: don't indicate warning on rsnd_kctrl_accept_runtime()\n- s390/cio: Fix CHPID \"configure\" attribute caching\n- HID: ignore non-functional sensor in HP 5MP Camera {CVE-2025-21992}\n- HID: intel-ish-hid: fix the length of MNG_SYNC_FW_CLOCK in doorbell\n- ACPI: resource: IRQ override for Eluktronics MECH-17\n- scsi: qla1280: Fix kernel oops when debug level \u003e 2 {CVE-2025-21957}\n- iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic() {CVE-2025-21993}\n- powercap: call put_device() on an error path in powercap_register_control_type()\n- hrtimers: Mark is_migration_base() with __always_inline\n- nvme-fc: go straight to connecting state when initializing\n- net/mlx5e: Prevent bridge link show failure for non-eswitch-allowed devices\n- netfilter: nft_exthdr: fix offset with ipv4_find_option()\n- net_sched: Prevent creation of classes with TC_H_ROOT {CVE-2025-21971}\n- ipvs: prevent integer overflow in do_ip_vs_get_ctl()\n- netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree() {CVE-2025-21959}\n- Drivers: hv: vmbus: Don't release fb_mmio resource in vmbus_free_mmio()\n- drivers/hv: Replace binary semaphore with mutex\n- netpoll: hold rcu read lock in __netpoll_send_skb()\n- netpoll: netpoll_send_skb() returns transmit status\n- netpoll: move netpoll_send_skb() out of line\n- netpoll: remove dev argument from netpoll_send_skb_on_dev()\n- netpoll: Fix use correct return type for ndo_start_xmit()\n- pinctrl: bcm281xx: Fix incorrect regmap max_registers value\n- sched/isolation: Prevent boot crash when the boot CPU is nohz_full\n- clockevents/drivers/i8253: Fix stop sequence for timer 0\n- RDS: avoid using offlined CPU during reconnect\n- x86/microcode/AMD: Clean the cache if update did not load microcode\n- x86/microcode/AMD: Add finalize_late_load() microcode_op\n- x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any unreleased standalone Zen5 microcode patches\n- x86/microcode/AMD: Add some forgotten models to the SHA check\n- x86/microcode/AMD: Load only SHA256-checksummed patches {CVE-2025-22047}\n- x86/microcode/AMD: Flush patch buffer mapping after application\n- x86/microcode/AMD: Stash BSP's CPUID(1).EAX and patch size\n- nvme: fix deadlock between reset and scan","status":"published","published":"2026-07-25T14:26:33Z","modified":"2026-10-26T09:31:54.525489963Z","updated_at":"2026-11-02T15:43:42.025438Z"},{"id":"MGASA-2025-0030","title":"Updated kernel, kmod-virtualbox, kmod-xtables-addons \u0026 dwarves packages fix security vulnerabilities","description":"Upstream kernel version 6.6.74 fixes bugs and vulnerabilities.\nThe kmod-virtualbox and kmod-xtables-addons packages have been\nupdated to work with this new kernel.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2025-01-31T20:54:03Z","modified":"2026-04-16T04:41:37.04829169Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"MGASA-2025-0032","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.74 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2025-01-31T20:54:03Z","modified":"2026-04-16T04:44:17.127966836Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"USN-7379-1","title":"linux, linux-aws, linux-azure, linux-gcp, linux-hwe-6.11, linux-oracle, linux-realtime vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Bluetooth drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - SPI subsystem;\n  - UFS subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - Overlay file system;\n  - Diskquota system;\n  - SMB network file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - VLANs driver;\n  - KASAN memory debugging framework;\n  - Memory management;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - LAPB network protocol;\n  - Netfilter;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Scheduler infrastructure;\n  - Seccomp subsystem;\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - KUnit library;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Wireless networking;\n  - eXpress Data Path;\n  - SELinux security module;\n  - ALSA framework;\n  - Intel ASoC drivers;\n  - SOF drivers;\n(CVE-2024-57921, CVE-2024-56614, CVE-2024-56558, CVE-2024-56589,\nCVE-2024-56662, CVE-2024-56610, CVE-2024-56717, CVE-2024-57890,\nCVE-2024-55639, CVE-2024-56562, CVE-2025-21633, CVE-2024-56598,\nCVE-2024-47794, CVE-2024-41935, CVE-2024-57901, CVE-2024-56587,\nCVE-2024-56581, CVE-2024-56783, CVE-2024-57888, CVE-2024-57809,\nCVE-2024-57926, CVE-2025-21650, CVE-2024-56634, CVE-2025-21639,\nCVE-2025-21656, CVE-2024-56578, CVE-2025-21632, CVE-2024-56784,\nCVE-2025-21644, CVE-2024-56776, CVE-2024-56764, CVE-2024-56652,\nCVE-2024-56550, CVE-2024-56569, CVE-2024-57904, CVE-2024-49569,\nCVE-2024-56770, CVE-2024-56606, CVE-2024-57806, CVE-2024-56646,\nCVE-2024-57895, CVE-2024-57880, CVE-2024-56650, CVE-2024-56591,\nCVE-2024-56590, CVE-2024-56642, CVE-2024-56713, CVE-2025-21663,\nCVE-2024-57938, CVE-2024-56760, CVE-2024-56583, CVE-2025-21662,\nCVE-2024-56629, CVE-2024-47408, CVE-2024-57850, CVE-2024-56777,\nCVE-2024-56626, CVE-2024-56773, CVE-2024-56647, CVE-2025-21664,\nCVE-2024-56564, CVE-2024-56597, CVE-2024-56623, CVE-2024-57897,\nCVE-2024-56670, CVE-2024-56567, CVE-2024-57931, CVE-2024-56761,\nCVE-2024-57935, CVE-2024-53690, CVE-2025-21640, CVE-2024-56608,\nCVE-2024-57878, CVE-2025-21648, CVE-2024-57898, CVE-2024-57889,\nCVE-2024-56644, CVE-2024-56763, CVE-2024-57900, CVE-2024-56575,\nCVE-2024-56786, CVE-2025-21635, CVE-2024-56559, CVE-2024-56659,\nCVE-2024-56621, CVE-2024-57908, CVE-2024-52319, CVE-2024-43098,\nCVE-2024-57838, CVE-2024-56782, CVE-2025-21631, CVE-2024-36476,\nCVE-2025-21649, CVE-2024-56667, CVE-2024-49571, CVE-2024-55916,\nCVE-2024-57887, CVE-2024-56640, CVE-2024-57801, CVE-2024-57886,\nCVE-2024-56582, CVE-2024-56561, CVE-2024-56665, CVE-2024-57805,\nCVE-2024-51729, CVE-2024-57857, CVE-2024-57876, CVE-2024-57896,\nCVE-2024-57799, CVE-2024-57925, CVE-2024-57917, CVE-2024-56664,\nCVE-2024-57913, CVE-2025-21660, CVE-2024-56596, CVE-2024-56671,\nCVE-2024-56595, CVE-2024-56781, CVE-2024-57912, CVE-2024-56638,\nCVE-2024-56636, CVE-2024-56669, CVE-2024-57945, CVE-2024-56633,\nCVE-2024-56605, CVE-2024-57882, CVE-2025-21652, CVE-2024-53179,\nCVE-2024-56599, CVE-2024-57892, CVE-2025-21647, CVE-2024-57910,\nCVE-2024-57792, CVE-2024-56768, CVE-2024-56711, CVE-2024-47143,\nCVE-2024-56577, CVE-2024-56574, CVE-2024-56765, CVE-2024-58087,\nCVE-2024-53685, CVE-2024-56787, CVE-2024-56592, CVE-2024-56368,\nCVE-2024-56615, CVE-2024-56712, CVE-2024-56648, CVE-2024-57874,\nCVE-2024-56653, CVE-2024-56656, CVE-2024-56641, CVE-2024-56719,\nCVE-2025-21658, CVE-2024-56637, CVE-2024-56709, CVE-2024-57843,\nCVE-2024-56588, CVE-2024-57807, CVE-2024-57939, CVE-2024-56594,\nCVE-2024-55642, CVE-2024-57841, CVE-2024-50051, CVE-2024-56663,\nCVE-2024-56654, CVE-2024-56369, CVE-2024-57885, CVE-2024-56779,\nCVE-2024-56772, CVE-2024-56617, CVE-2024-56624, CVE-2024-56570,\nCVE-2024-56639, CVE-2025-21642, CVE-2024-56603, CVE-2024-56604,\nCVE-2024-57875, CVE-2025-21653, CVE-2025-21654, CVE-2024-56645,\nCVE-2024-56775, CVE-2024-52332, CVE-2024-48875, CVE-2024-41932,\nCVE-2024-57804, CVE-2025-21661, CVE-2024-57932, CVE-2024-53681,\nCVE-2024-56563, CVE-2024-56609, CVE-2024-57798, CVE-2025-21637,\nCVE-2024-57940, CVE-2024-56675, CVE-2024-56630, CVE-2024-56565,\nCVE-2024-54460, CVE-2024-56573, CVE-2025-21645, CVE-2024-56715,\nCVE-2024-56632, CVE-2024-56622, CVE-2024-56673, CVE-2024-48881,\nCVE-2024-56593, CVE-2024-56620, CVE-2024-48876, CVE-2025-21643,\nCVE-2024-56657, CVE-2024-57905, CVE-2024-57802, CVE-2024-56766,\nCVE-2024-57893, CVE-2024-57894, CVE-2024-57903, CVE-2024-57902,\nCVE-2024-57934, CVE-2024-57881, CVE-2024-56602, CVE-2024-47809,\nCVE-2024-56580, CVE-2024-57899, CVE-2024-56759, CVE-2024-56586,\nCVE-2024-57839, CVE-2024-49568, CVE-2024-56660, CVE-2024-53687,\nCVE-2024-57907, CVE-2024-56601, CVE-2024-56767, CVE-2024-57916,\nCVE-2024-56616, CVE-2024-56557, CVE-2024-56566, CVE-2024-56643,\nCVE-2025-21638, CVE-2024-57879, CVE-2025-21655, CVE-2024-56618,\nCVE-2024-56758, CVE-2024-56576, CVE-2024-57849, CVE-2024-56372,\nCVE-2024-45828, CVE-2024-57795, CVE-2024-56710, CVE-2024-56568,\nCVE-2024-56769, CVE-2025-21834, CVE-2024-56716, CVE-2024-56613,\nCVE-2024-56584, CVE-2024-56552, CVE-2025-21659, CVE-2024-57929,\nCVE-2024-57946, CVE-2025-21646, CVE-2024-56572, CVE-2024-55881,\nCVE-2025-21651, CVE-2024-57924, CVE-2025-21634, CVE-2024-53682,\nCVE-2024-57872, CVE-2024-53680, CVE-2024-54680, CVE-2024-57918,\nCVE-2024-56780, CVE-2025-21636, CVE-2024-57906, CVE-2024-55641,\nCVE-2024-54455, CVE-2024-57919, CVE-2024-54683, CVE-2024-54193,\nCVE-2024-56635, CVE-2024-57933, CVE-2024-56611, CVE-2024-56551,\nCVE-2024-57883, CVE-2024-57793, CVE-2024-56631, CVE-2024-56600,\nCVE-2024-56651, CVE-2024-56714, CVE-2024-39282, CVE-2024-56627,\nCVE-2024-56649, CVE-2024-56579, CVE-2024-57791, CVE-2024-56774,\nCVE-2024-57944, CVE-2024-57911, CVE-2024-48873, CVE-2024-57884,\nCVE-2025-21629, CVE-2024-56778, CVE-2024-56619, CVE-2024-54191,\nCVE-2024-56771, CVE-2024-47141, CVE-2024-56757, CVE-2024-56718,\nCVE-2024-56655, CVE-2024-56607, CVE-2024-56785, CVE-2024-56625)\n","status":"published","published":"2025-03-27T16:18:31Z","modified":"2026-10-29T20:02:56.402454662Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7381-1","title":"linux-lowlatency-hwe-6.11 vulnerabilities","description":"\nAttila Szász discovered that the HFS+ file system implementation in the\nLinux Kernel contained a heap overflow vulnerability. An attacker could use\na specially crafted file system image that, when mounted, could cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2025-0927)\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  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Bluetooth drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - SPI subsystem;\n  - UFS subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - Overlay file system;\n  - Diskquota system;\n  - SMB network file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - VLANs driver;\n  - KASAN memory debugging framework;\n  - Memory management;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - LAPB network protocol;\n  - Network namespace;\n  - Netfilter;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Scheduler infrastructure;\n  - Seccomp subsystem;\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - KUnit library;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Wireless networking;\n  - eXpress Data Path;\n  - SELinux security module;\n  - ALSA framework;\n  - Intel ASoC drivers;\n  - SOF drivers;\n(CVE-2024-56712, CVE-2024-56761, CVE-2025-21661, CVE-2024-56565,\nCVE-2024-57804, CVE-2024-57887, CVE-2025-21642, CVE-2024-56779,\nCVE-2025-21656, CVE-2024-57890, CVE-2024-36476, CVE-2024-57843,\nCVE-2024-56594, CVE-2024-41932, CVE-2025-21653, CVE-2024-56567,\nCVE-2024-56665, CVE-2024-54191, CVE-2024-57893, CVE-2024-57932,\nCVE-2024-56656, CVE-2024-57945, CVE-2024-57931, CVE-2024-56599,\nCVE-2024-57897, CVE-2024-57903, CVE-2024-57918, CVE-2024-57795,\nCVE-2024-56662, CVE-2025-21639, CVE-2024-55881, CVE-2024-57889,\nCVE-2024-57884, CVE-2024-57934, CVE-2024-39282, CVE-2024-56718,\nCVE-2024-56644, CVE-2024-56760, CVE-2024-43098, CVE-2024-47143,\nCVE-2024-55642, CVE-2024-56634, CVE-2024-56564, CVE-2024-56768,\nCVE-2024-56649, CVE-2024-57919, CVE-2024-56620, CVE-2024-56625,\nCVE-2024-56655, CVE-2024-56772, CVE-2025-21637, CVE-2024-56617,\nCVE-2024-57879, CVE-2024-56715, CVE-2024-56550, CVE-2024-50051,\nCVE-2024-56673, CVE-2024-51729, CVE-2025-21664, CVE-2025-21649,\nCVE-2024-56605, CVE-2024-56622, CVE-2024-56591, CVE-2024-56782,\nCVE-2024-57801, CVE-2024-56664, CVE-2024-57916, CVE-2024-53680,\nCVE-2024-57926, CVE-2024-56637, CVE-2024-56769, CVE-2024-57924,\nCVE-2024-56648, CVE-2024-57872, CVE-2024-56593, CVE-2024-57913,\nCVE-2024-53682, CVE-2024-56670, CVE-2024-56767, CVE-2024-56778,\nCVE-2024-56777, CVE-2025-21658, CVE-2025-21646, CVE-2024-48875,\nCVE-2024-56758, CVE-2024-56604, CVE-2024-56787, CVE-2024-56581,\nCVE-2025-21635, CVE-2024-56641, CVE-2024-56608, CVE-2024-57885,\nCVE-2024-56716, CVE-2024-56671, CVE-2024-56559, CVE-2025-21633,\nCVE-2024-56372, CVE-2024-57888, CVE-2024-56623, CVE-2025-21638,\nCVE-2024-56600, CVE-2024-56647, CVE-2025-21659, CVE-2024-41935,\nCVE-2024-56624, CVE-2024-56574, CVE-2025-21648, CVE-2024-56621,\nCVE-2024-54460, CVE-2024-56659, CVE-2024-47141, CVE-2024-57805,\nCVE-2024-57792, CVE-2024-45828, CVE-2024-53681, CVE-2024-56568,\nCVE-2024-56764, CVE-2025-21650, CVE-2024-56601, CVE-2024-56663,\nCVE-2025-21660, CVE-2025-21629, CVE-2024-56595, CVE-2024-57917,\nCVE-2024-53685, CVE-2024-57882, CVE-2024-57894, CVE-2024-56651,\nCVE-2024-56657, CVE-2024-57876, CVE-2024-56717, CVE-2024-57935,\nCVE-2024-56667, CVE-2024-57910, CVE-2024-57793, CVE-2024-56631,\nCVE-2024-56638, CVE-2025-21640, CVE-2024-56710, CVE-2024-56583,\nCVE-2024-56557, CVE-2024-56658, CVE-2025-21632, CVE-2024-56645,\nCVE-2024-56646, CVE-2024-56640, CVE-2024-57944, CVE-2024-56598,\nCVE-2024-57857, CVE-2024-56709, CVE-2024-56654, CVE-2024-57809,\nCVE-2024-57895, CVE-2025-21834, CVE-2024-56763, CVE-2024-48881,\nCVE-2024-57841, CVE-2024-57878, CVE-2024-56774, CVE-2024-57791,\nCVE-2024-56575, CVE-2024-56619, CVE-2024-56570, CVE-2024-56616,\nCVE-2024-56569, CVE-2025-21636, CVE-2024-56572, CVE-2024-56552,\nCVE-2024-56596, CVE-2025-21654, CVE-2024-56573, CVE-2024-56784,\nCVE-2024-56626, CVE-2024-56642, CVE-2024-56643, CVE-2024-56719,\nCVE-2024-56632, CVE-2024-57839, CVE-2024-56578, CVE-2024-53690,\nCVE-2024-56609, CVE-2024-56562, CVE-2024-56589, CVE-2024-56781,\nCVE-2024-56672, CVE-2024-56775, CVE-2024-56713, CVE-2024-56580,\nCVE-2024-57874, CVE-2024-56369, CVE-2024-56711, CVE-2025-21651,\nCVE-2024-56584, CVE-2024-57904, CVE-2024-54680, CVE-2024-56577,\nCVE-2024-56558, CVE-2024-56780, CVE-2024-58087, CVE-2024-57892,\nCVE-2025-21644, CVE-2024-57911, CVE-2024-56579, CVE-2025-21663,\nCVE-2024-56618, CVE-2024-56766, CVE-2024-56653, CVE-2025-21655,\nCVE-2024-56669, CVE-2024-56759, CVE-2024-48876, CVE-2025-21631,\nCVE-2024-56765, CVE-2024-56770, CVE-2024-57838, CVE-2025-21634,\nCVE-2024-56650, CVE-2024-57939, CVE-2024-56606, CVE-2024-56610,\nCVE-2025-21662, CVE-2024-56785, CVE-2024-55916, CVE-2025-21643,\nCVE-2024-56586, CVE-2024-56582, CVE-2024-56614, CVE-2024-49571,\nCVE-2024-49569, CVE-2024-57798, CVE-2024-56633, CVE-2024-55641,\nCVE-2025-21647, CVE-2025-21652, CVE-2024-56757, CVE-2024-56597,\nCVE-2024-47794, CVE-2024-57902, CVE-2024-57925, CVE-2024-54683,\nCVE-2024-57938, CVE-2024-56615, CVE-2024-57906, CVE-2024-53687,\nCVE-2024-57899, CVE-2024-56783, CVE-2024-56786, CVE-2024-56635,\nCVE-2024-56551, CVE-2024-53179, CVE-2024-56588, CVE-2024-47408,\nCVE-2024-57849, CVE-2024-52319, CVE-2024-56576, CVE-2024-57905,\nCVE-2024-57946, CVE-2024-56607, CVE-2024-57806, CVE-2024-57933,\nCVE-2024-55639, CVE-2024-56561, CVE-2024-48873, CVE-2024-52332,\nCVE-2025-21645, CVE-2024-56602, CVE-2024-56590, CVE-2024-57799,\nCVE-2024-57929, CVE-2024-56639, CVE-2024-56613, CVE-2024-56675,\nCVE-2024-57912, CVE-2024-57883, CVE-2024-56636, CVE-2024-56592,\nCVE-2024-57802, CVE-2024-54455, CVE-2024-57908, CVE-2024-56603,\nCVE-2024-57875, CVE-2024-56773, CVE-2024-47809, CVE-2024-56630,\nCVE-2024-56587, CVE-2024-56627, CVE-2024-57921, CVE-2024-56660,\nCVE-2024-56771, CVE-2024-57886, CVE-2024-57896, CVE-2024-57807,\nCVE-2024-57907, CVE-2024-49568, CVE-2024-54193, CVE-2024-56652,\nCVE-2024-57940, CVE-2024-57898, CVE-2024-57901, CVE-2024-56714,\nCVE-2024-56566, CVE-2024-56563, CVE-2024-56368, CVE-2024-56611,\nCVE-2024-56776, CVE-2024-57850, CVE-2024-56629, CVE-2024-57881,\nCVE-2024-57880, CVE-2024-57900)\n","status":"published","published":"2025-03-27T17:07:06Z","modified":"2026-06-03T14:03:54.171720088Z","updated_at":"2026-11-02T16:58:19.988474Z"},{"id":"USN-7382-1","title":"linux-oem-6.11 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Ublk userspace block driver;\n  - Virtio block driver;\n  - Bluetooth drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - I3C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Microchip PCI driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - i.MX SoC drivers;\n  - SPI subsystem;\n  - UFS subsystem;\n  - USB Gadget drivers;\n  - TDX Guest driver;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - F2FS file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - Overlay file system;\n  - Diskquota system;\n  - SMB network file system;\n  - DRM display driver;\n  - BPF subsystem;\n  - VLANs driver;\n  - KASAN memory debugging framework;\n  - Memory management;\n  - StackDepot library;\n  - Bluetooth subsystem;\n  - LAPB network protocol;\n  - Netfilter;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - DMA mapping infrastructure;\n  - KCSAN framework;\n  - Scheduler infrastructure;\n  - Seccomp subsystem;\n  - Tracing infrastructure;\n  - Workqueue subsystem;\n  - KUnit library;\n  - CAN network layer;\n  - Networking core;\n  - DCCP (Datagram Congestion Control Protocol);\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - Wireless networking;\n  - eXpress Data Path;\n  - SELinux security module;\n  - ALSA framework;\n  - Intel ASoC drivers;\n  - SOF drivers;\n(CVE-2024-47794, CVE-2025-21653, CVE-2024-55642, CVE-2024-56580,\nCVE-2024-36476, CVE-2024-56623, CVE-2024-56773, CVE-2024-48873,\nCVE-2024-47141, CVE-2024-57910, CVE-2024-56759, CVE-2024-54460,\nCVE-2024-57839, CVE-2024-56625, CVE-2024-55916, CVE-2025-21664,\nCVE-2025-21652, CVE-2024-56624, CVE-2024-56574, CVE-2024-50051,\nCVE-2025-21655, CVE-2024-56578, CVE-2024-56782, CVE-2024-57939,\nCVE-2024-57935, CVE-2024-56647, CVE-2024-57905, CVE-2024-57921,\nCVE-2024-56660, CVE-2025-21650, CVE-2025-21631, CVE-2024-56642,\nCVE-2024-56552, CVE-2024-57934, CVE-2024-56621, CVE-2024-57881,\nCVE-2024-41932, CVE-2024-56770, CVE-2024-57897, CVE-2024-56785,\nCVE-2024-56664, CVE-2024-57945, CVE-2024-57938, CVE-2024-56636,\nCVE-2024-56572, CVE-2024-43098, CVE-2024-56760, CVE-2024-57916,\nCVE-2024-56714, CVE-2025-21660, CVE-2024-57906, CVE-2025-21638,\nCVE-2024-53687, CVE-2024-56652, CVE-2024-51729, CVE-2024-49571,\nCVE-2024-57883, CVE-2024-54191, CVE-2024-56712, CVE-2024-49568,\nCVE-2024-57932, CVE-2024-57893, CVE-2024-56645, CVE-2024-56719,\nCVE-2024-56641, CVE-2024-57802, CVE-2024-56775, CVE-2024-56627,\nCVE-2024-56638, CVE-2024-57929, CVE-2024-56615, CVE-2024-56566,\nCVE-2024-56620, CVE-2024-56577, CVE-2025-21656, CVE-2024-57887,\nCVE-2024-52319, CVE-2024-56657, CVE-2024-57872, CVE-2024-56607,\nCVE-2024-56562, CVE-2025-21645, CVE-2025-21634, CVE-2024-56567,\nCVE-2024-56637, CVE-2025-21646, CVE-2024-57918, CVE-2024-56646,\nCVE-2024-57849, CVE-2025-21633, CVE-2025-21639, CVE-2024-56644,\nCVE-2024-56618, CVE-2024-56564, CVE-2024-56369, CVE-2024-56766,\nCVE-2024-56635, CVE-2024-57907, CVE-2024-56778, CVE-2024-57880,\nCVE-2024-57885, CVE-2024-56591, CVE-2024-56780, CVE-2024-57913,\nCVE-2024-54680, CVE-2025-21632, CVE-2024-54683, CVE-2025-21654,\nCVE-2024-58087, CVE-2024-56772, CVE-2024-56758, CVE-2024-57795,\nCVE-2025-21644, CVE-2024-56586, CVE-2024-56663, CVE-2024-56558,\nCVE-2024-57882, CVE-2024-56651, CVE-2024-56783, CVE-2024-53681,\nCVE-2024-57911, CVE-2024-57879, CVE-2024-56649, CVE-2024-56563,\nCVE-2024-56639, CVE-2024-56605, CVE-2024-57888, CVE-2024-56640,\nCVE-2024-57841, CVE-2024-56656, CVE-2024-48875, CVE-2024-48876,\nCVE-2024-57919, CVE-2024-57940, CVE-2024-56630, CVE-2024-53685,\nCVE-2024-56604, CVE-2024-47809, CVE-2024-57889, CVE-2024-56619,\nCVE-2024-57806, CVE-2024-56583, CVE-2024-56715, CVE-2025-21640,\nCVE-2025-21662, CVE-2024-56662, CVE-2024-55639, CVE-2024-56711,\nCVE-2024-56372, CVE-2024-54455, CVE-2024-56771, CVE-2024-56368,\nCVE-2024-57892, CVE-2024-57843, CVE-2025-21636, CVE-2024-56650,\nCVE-2024-56613, CVE-2024-56716, CVE-2024-57793, CVE-2024-56634,\nCVE-2024-56595, CVE-2024-57878, CVE-2024-56598, CVE-2024-39282,\nCVE-2024-57908, CVE-2024-57917, CVE-2024-56763, CVE-2024-56629,\nCVE-2024-56710, CVE-2024-56671, CVE-2024-56667, CVE-2024-57924,\nCVE-2024-57926, CVE-2025-21658, CVE-2024-56594, CVE-2024-56584,\nCVE-2024-53179, CVE-2024-56587, CVE-2024-57946, CVE-2024-56717,\nCVE-2025-21635, CVE-2024-56779, CVE-2024-57944, CVE-2024-56767,\nCVE-2024-56781, CVE-2024-56765, CVE-2024-56609, CVE-2024-54193,\nCVE-2024-57804, CVE-2024-56599, CVE-2024-56602, CVE-2024-57901,\nCVE-2024-53680, CVE-2024-57801, CVE-2024-57912, CVE-2024-56606,\nCVE-2024-56579, CVE-2024-56588, CVE-2024-57895, CVE-2024-56601,\nCVE-2024-55641, CVE-2024-56559, CVE-2024-56557, CVE-2025-21661,\nCVE-2024-57799, CVE-2024-57850, CVE-2024-57876, CVE-2024-47408,\nCVE-2024-57899, CVE-2024-56597, CVE-2024-57890, CVE-2024-56670,\nCVE-2024-56603, CVE-2024-56654, CVE-2025-21834, CVE-2024-56590,\nCVE-2024-49569, CVE-2024-56616, CVE-2024-56659, CVE-2024-56596,\nCVE-2025-21642, CVE-2025-21663, CVE-2025-21648, CVE-2024-56614,\nCVE-2024-56673, CVE-2024-56787, CVE-2024-56713, CVE-2024-56573,\nCVE-2024-56589, CVE-2024-56764, CVE-2024-56655, CVE-2024-56617,\nCVE-2024-56669, CVE-2024-56576, CVE-2024-57792, CVE-2024-57904,\nCVE-2024-52332, CVE-2024-57900, CVE-2024-57933, CVE-2024-55881,\nCVE-2024-56626, CVE-2024-57894, CVE-2024-56582, CVE-2024-57838,\nCVE-2025-21629, CVE-2025-21659, CVE-2024-57809, CVE-2024-47143,\nCVE-2024-57925, CVE-2024-41935, CVE-2025-21649, CVE-2024-57884,\nCVE-2024-57875, CVE-2025-21647, CVE-2024-56581, CVE-2024-57886,\nCVE-2024-57896, CVE-2025-21651, CVE-2024-56611, CVE-2024-56575,\nCVE-2024-57807, CVE-2024-56561, CVE-2024-53690, CVE-2024-56761,\nCVE-2024-57902, CVE-2024-56600, CVE-2024-56593, CVE-2024-57805,\nCVE-2024-56568, CVE-2024-56632, CVE-2024-56622, CVE-2025-21637,\nCVE-2024-45828, CVE-2024-56709, CVE-2024-56631, CVE-2025-21643,\nCVE-2024-56786, CVE-2024-56565, CVE-2024-57903, CVE-2024-56592,\nCVE-2024-56569, CVE-2024-56718, CVE-2024-57791, CVE-2024-56665,\nCVE-2024-56774, CVE-2024-56608, CVE-2024-56643, CVE-2024-57931,\nCVE-2024-57857, CVE-2024-56777, CVE-2024-53682, CVE-2024-56648,\nCVE-2024-56769, CVE-2024-48881, CVE-2024-56776, CVE-2024-57798,\nCVE-2024-57874, CVE-2024-56633, CVE-2024-56768, CVE-2024-56653,\nCVE-2024-56784, CVE-2024-56550, CVE-2024-56610, CVE-2024-56570,\nCVE-2024-56675, CVE-2024-57898, CVE-2024-56551)\n","status":"published","published":"2025-03-27T17:21:41Z","modified":"2026-10-29T20:02:40.007032312Z","updated_at":"2026-11-02T16:58:19.988474Z"}]}}