p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de linux-gcp-edge · Page n° 15

Vulnérabilité publiée pour linux-gcp-edge au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 553

  1. CVE-2020-13974

    Élevée · CVSS 7.8EPSS 0,57%Aucun correctif publié

    CVE-2020-13974

    An issue was discovered in the Linux kernel 4.4 through 5.7.1. drivers/tty/vt/keyboard.c has an integer overflow if k_ascii is called several times in a row, aka CID-b86dab054059. NOTE: Members in the community argue that the integer overflow does not lead to a security issue in this case.

    Publication Mise à jour
  2. CVE-2020-10751

    Moyenne · CVSS 6.1EPSS 0,35%Aucun correctif publié

    CVE-2020-10751

    A flaw was found in the Linux kernels SELinux LSM hook implementation before version 5.7, where it incorrectly assumed that an skb would only contain a single netlink message. The hook would incorrectly only validate the first netlink message in the skb and allow or deny the rest of the messages within the skb with the granted permission without further processing.

    Publication Mise à jour
  3. CVE-2020-10711

    Moyenne · CVSS 5.9EPSS 3,08%Aucun correctif publié

    CVE-2020-10711

    A NULL pointer dereference flaw was found in the Linux kernel's SELinux subsystem in versions before 5.7. This flaw occurs while importing the Commercial IP Security Option (CIPSO) protocol's category bitmap into the SELinux extensible bitmap via the' ebitmap_netlbl_import' routine. While processing the CIPSO restricted bitmap tag in the 'cipso_v4_parsetag_rbm' routine, it sets the security attribute to indicate that the category bitmap is present, even if it has not been allocated. This issue leads to a NULL pointer dereference issue while importing the same category bitmap into SELinux. This flaw allows a remote network user to crash the sy

    Publication Mise à jour
  4. CVE-2020-10135

    Moyenne · CVSS 5.4EPSS 2,37%Aucun correctif publié

    Bluetooth devices supporting BR/EDR v5.2 and earlier are vulnerable to impersonation attacks

    Legacy pairing and secure-connections pairing authentication in Bluetooth BR/EDR Core Specification v5.2 and earlier may allow an unauthenticated user to complete authentication without pairing credentials via adjacent access. An unauthenticated, adjacent attacker could impersonate a Bluetooth BR/EDR master or slave to pair with a previously paired remote device to successfully complete the authentication procedure without knowing the link key.

    Publication Mise à jour
  5. CVE-2020-0110

    Élevée · CVSS 7.8EPSS 0,18%Aucun correctif publié

    CVE-2020-0110

    In psi_write of psi.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-148159562References: Upstream kernel

    Publication Mise à jour
  6. CVE-2020-12826

    Moyenne · CVSS 5.3EPSS 0,71%Aucun correctif publié

    CVE-2020-12826

    A signal access-control issue was discovered in the Linux kernel before 5.6.5, aka CID-7395ea4e65c2. Because exec_id in include/linux/sched.h is only 32 bits, an integer overflow can interfere with a do_notify_parent protection mechanism. A child process can send an arbitrary signal to a parent process in a different security domain. Exploitation limitations include the amount of elapsed time before an integer overflow occurs, and the lack of scenarios where signals to a parent process present a substantial operational threat.

    Publication Mise à jour
  7. CVE-2019-20794

    Moyenne · CVSS 4.7EPSS 0,51%Aucun correctif publié

    CVE-2019-20794

    An issue was discovered in the Linux kernel 4.18 through 5.6.11 when unprivileged user namespaces are allowed. A user can create their own PID namespace, and mount a FUSE filesystem. Upon interaction with this FUSE filesystem, if the userspace component is terminated via a kill of the PID namespace's pid 1, it will result in a hung task, and resources being permanently locked up until system reboot. This can result in resource exhaustion.

    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →