{"schema_version":"1.7.2","id":"OESA-2023-1143","modified":"2023-03-04T11:05:00Z","published":"2023-03-04T11:05:00Z","upstream":["CVE-2023-0045","CVE-2021-33639"],"summary":"kernel security update","details":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nThe Linux kernel does not correctly mitigate SMT attacks, as discovered\nthrough a strange pattern in the kernel API using STIBP as a mitigation[1\n\u0026lt;https://docs.kernel.org/userspace-api/spec_ctrl.html\u0026gt;], leaving the\nprocess exposed for a short period of time after a syscall. The kernel also\ndoes not issue an IBPB immediately during the syscall.\nThe ib_prctl_set [2\n\u0026lt;https://elixir.bootlin.com/linux/v5.15.56/source/arch/x86/kernel/cpu/bugs.c#L1467\u0026gt;]function\nupdates the Thread Information Flags (TIFs) for the task and updates the\nSPEC_CTRL MSR on the function __speculation_ctrl_update [3\n\u0026lt;https://elixir.bootlin.com/linux/v5.15.56/source/arch/x86/kernel/process.c#L557\u0026gt;],\nbut the IBPB is only issued on the next schedule, when the TIF bits are\nchecked. This leaves the victim vulnerable to values already injected on\nthe BTB, prior to the prctl syscall.\nThe behavior is only corrected after a reschedule of the task happens.\nFurthermore, the kernel entrance (due to the syscall itself), does not\nissue an IBPB in the default scenarios (i.e., when the kernel protects\nitself via retpoline or eIBRS).(CVE-2023-0045)\r\n\r\nREMAP cmd of SVM driver can be used to remap read only memory as read-write, then cause read only memory/file modified..(CVE-2021-33639)","affected":[{"package":{"ecosystem":"openEuler:20.03-LTS-SP3","name":"kernel","purl":"pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP3"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.90-2302.5.0.0190.oe1"}]}],"ecosystem_specific":{"aarch64":["kernel-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","python2-perf-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","kernel-tools-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","kernel-source-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","python2-perf-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","kernel-debugsource-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","bpftool-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","perf-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","bpftool-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","python3-perf-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","kernel-tools-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","perf-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","python3-perf-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","kernel-tools-devel-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","kernel-4.19.90-2302.5.0.0190.oe1.aarch64.rpm","kernel-devel-4.19.90-2302.5.0.0190.oe1.aarch64.rpm"],"src":["kernel-4.19.90-2302.5.0.0190.oe1.src.rpm"],"x86_64":["python3-perf-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","kernel-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","kernel-tools-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","python2-perf-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","perf-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","kernel-debugsource-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","perf-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","kernel-devel-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","python3-perf-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","kernel-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","bpftool-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","python2-perf-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","kernel-source-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","kernel-tools-devel-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","bpftool-4.19.90-2302.5.0.0190.oe1.x86_64.rpm","kernel-tools-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm"]}}],"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1143"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0045"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-33639"}],"database_specific":{"severity":"Medium"}}