Duoming Zhou discovered race conditions in the AX.25 amateur radio protocol implementation in the Linux kernel, leading to use-after-free vulnerabilities. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2022-1205) It was discovered that the i.MX clock driver in the Linux kernel did not properly handle certain memory allocation failure conditions, leading to a null pointer dereference vulnerability.
USN-8963-1: Linux kernel (NVIDIA Tegra) vulnerabilities
About this summary. This is a short excerpt from the description that Ubuntu Security published with its article. Cyber Security News did not report or verify the underlying story. Read the original: https://ubuntu.com/security/notices/USN-8963-1
Source attribution: headline and facts are from Ubuntu Security (ubuntu.com). Summary method: excerpt of the source description. See our source attribution policy.
Related coverage
USN-8961-1: Linux kernel vulnerabilities
Duoming Zhou discovered race conditions in the AX.25 amateur radio protocol implementation in the Linux kernel, leading to use-after-free vulnerabilities. A local…
USN-8962-1: Linux kernel (Azure CVM) vulnerabilities
Duoming Zhou discovered race conditions in the AX.25 amateur radio protocol implementation in the Linux kernel, leading to use-after-free vulnerabilities. A local…
USN-8875-2: Linux kernel (NVIDIA) vulnerabilities
It was discovered that the i.MX clock driver in the Linux kernel did not properly handle certain memory allocation failure conditions, leading to a null pointer…
USN-8875-1: Linux kernel vulnerabilities
It was discovered that the i.MX clock driver in the Linux kernel did not properly handle certain memory allocation failure conditions, leading to a null pointer…
USN-8879-1: Linux kernel (Oracle) vulnerabilities
It was discovered that the i.MX clock driver in the Linux kernel did not properly handle certain memory allocation failure conditions, leading to a null pointer…
USN-8878-1: Linux kernel (GCP) vulnerabilities
It was discovered that the i.MX clock driver in the Linux kernel did not properly handle certain memory allocation failure conditions, leading to a null pointer…