As the BSI currently reports, a vulnerability has been identified in the Linux kernel. You can read a description of the security vulnerability and a list of the affected operating systems and products here.
The Federal Office for Security in Information Technology (BSI) published a security advisory for the Linux kernel on February 27, 2024. The security vulnerability affects the Linux operating system and the Open Source Linux Kernel product.
The latest manufacturer recommendations regarding updates, workarounds and security patches for this vulnerability can be found here: CVE Announcement on lore.kernel.org (As of February 27, 2024). Other useful links are listed later in this article.
Linux Kernel Security Advisory – Risk: medium
Risk level: 3 (medium)
CVSS Base Score: 5,3
CVSS Temporal Score: 4,6
Remote attack: No
The Common Vulnerability Scoring System (CVSS) is used to assess the severity of security vulnerabilities in computer systems. The CVSS standard makes it possible to compare potential or actual security vulnerabilities based on various metrics in order to create a priority list for taking countermeasures. The attributes “none”, “low”, “medium”, “high” and “critical” are used to determine the severity levels of a vulnerability. The Base Score evaluates the requirements for an attack (including authentication, complexity, privileges, user interaction) and its consequences. The temporal score also takes changes over time in the danger situation into account. According to the CVSS, the severity of the current vulnerability is rated as “medium” with a base score of 5.3.
Linux Kernel Bug: Multiple vulnerabilities allow unspecified attack
The kernel represents the core of the Linux operating system.
A local attacker can exploit multiple vulnerabilities in the Linux kernel to carry out an unspecified attack.
The vulnerabilities were classified by individual serial numbers using the CVE (Common Vulnerabilities and Exposures) referencing system CVE-2021-46975, CVE-2021-46974, CVE-2021-46973, CVE-2021-46972, CVE-2021-46971, CVE-2021-46970, CVE-2021-46969, CVE-2021-46968, CVE-2021-46967, CVE-2021-46966, CVE-2021-46965, CVE-2021-46964, CVE-2021-46963, CVE-2021-46962, CVE-2021-46961, CVE-2021-46960, CVE-2021-46958, CVE-2021-46957, CVE-2021-46956, CVE-2021-46955, CVE-2021-46954, CVE-2021-46945, CVE-2021-46944, CVE-2021-46943 und CVE-2021-46942.
Systems affected by the security gap at a glance
operating system
Linux
Products
Open Source Linux Kernel
General recommendations for dealing with IT security gaps
Users of the affected applications should keep them up to date. When security gaps become known, manufacturers are required to fix them as quickly as possible by developing a patch or a workaround. If security patches are available, install them promptly. For information, consult the sources listed in the next section. These often contain further information about the latest version of the software in question as well as the availability of security patches or information about workarounds. If you have any further questions or uncertainties, please contact your responsible administrator. IT security managers should regularly check the sources mentioned to see whether a new security update is available.
Manufacturer information on updates, patches and workarounds
Here you will find further links with information about bug reports, security fixes and workarounds.
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
CVE Announcement on lore.kernel.org dated 2024-02-27 (27.02.2024)
For more information, see:
Version history of this security alert
This is the initial version of this IT security notice for the Linux kernel. If updates are announced, this text will be updated. You can see the changes made using the version history below.
02/27/2024 – Initial version
+++ Editorial note: This text was generated based on current BSI data and will be updated in a data-driven manner depending on the warning situation. We accept feedback and comments at [email protected]. +++
follow News.de already at Facebook, Twitter, Pinterest and YouTube? Here you will find hot news, current videos and a direct line to the editorial team.
Edited by kns
roj/news.de