{"id":99696,"date":"2021-04-10T10:23:07","date_gmt":"2021-04-10T08:23:07","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/proekt-freebsd-perevyol-port-arm64-v-chislo-pervichnyh-i-ispravil-tri-uyazvimosti"},"modified":"2021-04-10T10:23:07","modified_gmt":"2021-04-10T08:23:07","slug":"proekt-freebsd-perevyol-port-arm64-v-chislo-pervichnyh-i-ispravil-tri-uyazvimosti","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/proekt-freebsd-perevyol-port-arm64-v-chislo-pervichnyh-i-ispravil-tri-uyazvimosti","title":{"rendered":"The FreeBSD project has elevated the ARM64 port to primary status and fixed three vulnerabilities.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The FreeBSD developers have decided to assign Tier 1 status to the ARM64 (AArch64) port in the new branch of FreeBSD 13, which is expected to be released on April 13. Previously, this level of support was provided for 64-bit x86 systems (the i386 architecture was also primary until January when it was downgraded to Tier 2). <\/p>\n
Tier 1 support implies the creation of installation builds, binary updates, and ready-to-use packages, as well as guarantees to resolve specific issues and to maintain ABI stability for the user environment and the kernel (except for certain subsystems). Tier 1 is supported by teams responsible for addressing vulnerabilities, preparing releases, and maintaining ports. <\/p>\n
Additionally, three vulnerabilities in FreeBSD can be noted: <\/p>\n
\n
CVE-2021-29626 \u2014 An unprivileged local process can read the contents of kernel memory or other processes through manipulation of memory page mapping. The vulnerability is caused by an error in the virtual memory subsystem that provides shared memory between processes, which led to the continued binding of memory to a process after the associated memory page was freed.\n
CVE-2021-29627 \u2014 An unprivileged local user can escalate their privileges within the system or read the contents of kernel memory. The issue is caused by accessing memory after it has been freed (use-after-free) in the implementation of the accept filter mechanism.\n
CVE-2020-25584 \u2014 A potential bypass of the Jail isolation mechanism. A user within an isolated environment who has the right to mount partitions (allow.mount) can change the root directory to a position outside the Jail hierarchy and gain full read and write access to all system files. <\/ul>\n