p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux · Seite 183

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für linux: 206. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4199

  1. CVE-2022-2380

    Mittel · CVSS 5.5EPSS 0,22%Keine Korrektur veröffentlicht

    CVE-2022-2380

    The Linux kernel was found vulnerable out of bounds memory access in the drivers/video/fbdev/sm712fb.c:smtcfb_read() function. The vulnerability could result in local attackers being able to crash the kernel.

    Veröffentlicht Aktualisiert
  2. CVE-2022-29901

    Mittel · CVSS 5.6EPSS 5,01%Keine Korrektur veröffentlicht

    Arbitrary Memory Disclosure through CPU Side-Channel Attacks (Retbleed)

    Intel microprocessor generations 6 to 8 are affected by a new Spectre variant that is able to bypass their retpoline mitigation in the kernel to leak arbitrary data. An attacker with unprivileged user access can hijack return instructions to achieve arbitrary speculative code execution under certain microarchitecture-dependent conditions.

    Veröffentlicht Aktualisiert
  3. CVE-2022-33742

    Hoch · CVSS 7.1EPSS 0,34%Keine Korrektur veröffentlicht

    CVE-2022-33742

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740). Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend (CVE-2022-33741, CVE-2022-33742).

    Veröffentlicht Aktualisiert
  4. CVE-2022-33741

    Hoch · CVSS 7.1EPSS 0,33%Keine Korrektur veröffentlicht

    CVE-2022-33741

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740). Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend (CVE-2022-33741, CVE-2022-33742).

    Veröffentlicht Aktualisiert
  5. CVE-2022-33740

    Hoch · CVSS 7.1EPSS 0,33%Keine Korrektur veröffentlicht

    CVE-2022-33740

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740). Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend (CVE-2022-33741, CVE-2022-33742).

    Veröffentlicht Aktualisiert
  6. CVE-2022-26365

    Hoch · CVSS 7.1EPSS 0,33%Keine Korrektur veröffentlicht

    CVE-2022-26365

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740). Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend (CVE-2022-33741, CVE-2022-33742).

    Veröffentlicht Aktualisiert
  7. CVE-2022-33744

    Hoch · CVSS 8.9EPSS 0,32%Keine Korrektur veröffentlicht

    CVE-2022-33744

    Arm guests can cause Dom0 DoS via PV devices When mapping pages of guests on Arm, dom0 is using an rbtree to keep track of the foreign mappings. Updating of that rbtree is not always done completely with the related lock held, resulting in a small race window, which can be used by unprivileged guests via PV devices to cause inconsistencies of the rbtree. These inconsistencies can lead to Denial of Service (DoS) of dom0, e.g. by causing crashes or the inability to perform further mappings of other guests' memory pages.

    Veröffentlicht Aktualisiert
  8. CVE-2022-20166

    Mittel · CVSS 6.7EPSS 0,16%Keine Korrektur veröffentlicht

    CVE-2022-20166

    In various methods of kernel base drivers, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-182388481References: Upstream kernel

    Veröffentlicht Aktualisiert
  9. CVE-2022-20141

    Hoch · CVSS 7.3EPSS 0,14%Keine Korrektur veröffentlicht

    CVE-2022-20141

    In ip_check_mc_rcu of igmp.c, there is a possible use after free due to improper locking. This could lead to local escalation of privilege when opening and closing inet sockets with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-112551163References: Upstream kernel

    Veröffentlicht Aktualisiert
  10. CVE-2022-20132

    Mittel · CVSS 4.6EPSS 0,21%Keine Korrektur veröffentlicht

    CVE-2022-20132

    In lg_probe and related functions of hid-lg.c and other USB HID files, there is a possible out of bounds read due to improper input validation. This could lead to local information disclosure if a malicious USB HID device were plugged in, with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-188677105References: Upstream kernel

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →