p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-hwe · Seite 16

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 751

  1. CVE-2019-9456

    Mittel · CVSS 6.7EPSS 0,2%Korrektur verfügbar

    CVE-2019-9456

    In the Android kernel in Pixel C USB monitor driver there is a possible OOB write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

    • Auf 4.15.0-24.26~16.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2019-9454

    Mittel · CVSS 6.7EPSS 0,18%Korrektur verfügbar

    CVE-2019-9454

    In the Android kernel in i2c driver there is a possible out of bounds write due to memory corruption. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

    • Auf 4.15.0-24.26~16.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2019-2182

    Hoch · CVSS 7.8EPSS 0,22%Korrektur verfügbar

    CVE-2019-2182

    In the Android kernel in the kernel MMU code there is a possible execution path leaving some kernel text and rodata pages writable. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    • Auf 4.15.0-91.92~16.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2019-15902

    Mittel · CVSS 5.6EPSS 0,61%Korrektur verfügbar

    CVE-2019-15902

    A backporting error was discovered in the Linux stable/longterm kernel 4.4.x through 4.4.190, 4.9.x through 4.9.190, 4.14.x through 4.14.141, 4.19.x through 4.19.69, and 5.2.x through 5.2.11. Misuse of the upstream "x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()" commit reintroduced the Spectre vulnerability that it aimed to eliminate. This occurred because the backport process depends on cherry picking specific commits, and because two (correctly ordered) code lines were swapped.

    • Auf 4.15.0-66.75~16.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2019-1125

    Mittel · CVSS 5.6EPSS 4,52%Öffentlicher ExploitKorrektur verfügbar

    Windows Kernel Information Disclosure Vulnerability

    An information disclosure vulnerability exists when certain central processing units (CPU) speculatively access memory. An attacker who successfully exploited the vulnerability could read privileged data across trust boundaries. To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to elevate user rights directly, but it could be used to obtain information that could be used to try to compromise the affected system further. On January 3, 2018, Microsoft released an advisory and security updates related to a newly-discovered c

    • Auf 4.15.0-58.64~16.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2019-15666

    Mittel · CVSS 6.9EPSS 1,73%Korrektur verfügbar

    CVE-2019-15666

    An issue was discovered in the Linux kernel before 5.0.19. There is an out-of-bounds array access in __xfrm_policy_unlink, which will cause denial of service, because verify_newpolicy_info in net/xfrm/xfrm_user.c mishandles directory validation.

    • Auf 4.15.0-60.67~16.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2019-15538

    Hoch · CVSS 7.5EPSS 3,92%Korrektur verfügbar

    CVE-2019-15538

    An issue was discovered in xfs_setattr_nonsize in fs/xfs/xfs_iops.c in the Linux kernel through 5.2.9. XFS partially wedges when a chgrp fails on account of being out of disk quota. xfs_setattr_nonsize is failing to unlock the ILOCK after the xfs_qm_vop_chown_reserve call fails. This is primarily a local DoS attack vector, but it might result as well in remote DoS if the XFS filesystem is exported for instance via NFS.

    • Auf 4.15.0-65.74~16.04.1 aktualisieren
    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 →