CVE-2019-19462
MEDIUM(5.5)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CVSS 5.5 — Mittel
EPSS-Score
0.5%
Exploit-Wahrscheinlichkeit (30 Tage)
CVSS Score
5.5
Technische Schwere
Beschreibung
relay_open in kernel/relay.c in the Linux kernel through 5.4.1 allows local users to cause a denial of service (such as relay blockage) by triggering a NULL alloc_percpu result.
Erkennung & Indikatoren
Ausnutzung
In den geprüften Quellen nicht genannt
Behobene Versionen
- 4.9.210-1+deb9u1~deb8u1
Threat-Hunting-Queries
Detecting attempts by local users to trigger NULL pointer dereferences in the Linux kernel's relay subsystem, which can lead to denial of service or privilege escalation. This query looks for kernel panics or crashes related to relay_open or relay_close_buf functions.
Sentinel/Defender KQL
DeviceEvents
| where ActionType == "KernelPanic" or ActionType == "Crash"
| where InitiatingProcessFileName contains "relay_open" or InitiatingProcessFileName contains "relay_close_buf"
| project Timestamp, DeviceName, InitiatingProcessFileName, ReportId, AdditionalFieldsSplunk SPL
index=linux (sourcetype=syslog OR sourcetype=kern.log) (relay_open OR relay_close_buf) (panic OR crash OR "general protection fault")
| table _time, host, sourcetype, _rawSigma
title: Linux Kernel Relay DoS/PrivEsc
status: experimental
description: Detects attempts to exploit CVE-2019-19462 in the Linux kernel's relay subsystem.
logsource:
product: linux
service: kernel
detection:
selection:
keywords:
- 'relay_open'
- 'relay_close_buf'
- 'general protection fault'
- 'BUG: Unable to handle kernel data access'
- 'kernel panic'
- 'crash'
condition: selection
level: highElastic ES|QL
from logs-system.*
| where message : ("relay_open" or "relay_close_buf") and message : ("general protection fault" or "BUG: Unable to handle kernel data access" or "kernel panic" or "crash")
| select @timestamp, host.name, messageSecBoard-generated · behavioral · requires customization — Von SecBoard erzeugt und nicht in einer Zielumgebung validiert. Vor dem Einsatz an die eigene Protokollierung anpassen.
Indikatoren
Sonstige (4)
- syzbot+1e925b4b836afe85a1c6@syzkaller-ppc64.appspotmail.com
- syzbot+587b2421926808309d21@syzkaller-ppc64.appspotmail.com
- syzbot+58320b7171734bf79d26@syzkaller.appspotmail.com
- syzbot+d6074fb08bdb2e010520@syzkaller.appspotmail.com
Übernommen wurden nur Indikatoren, die wörtlich in einer Hersteller- oder Research-Quelle standen.
Ausgewertete Quellen
Betroffene Produkte
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:active_iq_unified_manager:*:*:*:*:*:vmware_vsphere:*:*
- cpe:2.3:a:netapp:hci_management_node:-:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:solidfire:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:hci_compute_node:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:hci_storage_node:-:*:*:*:*:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:14.04:*:*:*:esm:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:20.04:*:*:*:lts:*:*:*
- cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*
- cpe:2.3:o:opensuse:leap:15.2:*:*:*:*:*:*:*
- cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
- cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
- cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
Referenzen
- http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00022.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00008.html
- https://lists.debian.org/debian-lts-announce/2020/06/msg00012.html
- https://lore.kernel.org/lkml/20191129013745.7168-1-dja%40axtens.net/
- https://security.netapp.com/advisory/ntap-20210129-0004/
- https://syzkaller-ppc64.appspot.com/bug?id=1c09906c83a8ea811a9e318c2a4f8e243becc...
- https://syzkaller-ppc64.appspot.com/bug?id=b05b4d005191cc375cdf848c3d4d980308d50...
- https://syzkaller.appspot.com/bug?id=e4265490d26d6c01cd9bc79dc915ef0a1bf15046
- https://syzkaller.appspot.com/bug?id=f4d1cb4330bd3ddf4a628332b4285407b2eedd7b
- https://usn.ubuntu.com/4414-1/