CVE-2022-49532

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.3%
Linux•Linux•Versions : <=5.17.*, <0f8bc147a963686b7351aa35d1701124ffacac08, <4.2, 5.15.46, <c51d00472fa54b9b05c17789ed665c17adf3a25d, <edafcad84c4134ebec4bc24b29ca4497a1184eea, 0, 5.19, <=4.9.*, 5.18.3, <=5.10.*, <=4.14.*, 5.10.121, 5.17.14, 4.19.247, 5.4.198, <=5.18.*, <=5.4.*, 4.14.283, <=4.19.*, dc5698e80cf724770283e10414054662bdf6ccfa, 4.2, <e0828456578cc8ba0a69147f7ae3428392eec287, <194d250cdc4a40ccbd179afd522a9e9846957402, <fadc626cae99aaa1325094edc6a9e2b883f3e562, <=*, <=5.15.*, <f85cb059fad03a3b33a50023be91e944bb065ae8, <848dd072744ea662ab3097e3c8282bee552df218, 4.9.318, <32e10aabc287f09a148ff759bb9ce70b01b0012c

Description

In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes drm_cvt_mode may return NULL and we should check it. This bug is found by syzkaller: FAULT_INJECTION stacktrace: [ 168.567394] FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 1 [ 168.567403] CPU: 1 PID: 6425 Comm: syz Kdump: loaded Not tainted 4.19.90-vhulk2201.1.0.h1035.kasan.eulerosv2r10.aarch64 #1 [ 168.567406] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 168.567408] Call trace: [ 168.567414] dump_backtrace+0x0/0x310 [ 168.567418] show_stack+0x28/0x38 [ 168.567423] dump_stack+0xec/0x15c [ 168.567427] should_fail+0x3ac/0x3d0 [ 168.567437] __should_failslab+0xb8/0x120 [ 168.567441] should_failslab+0x28/0xc0 [ 168.567445] kmem_cache_alloc_trace+0x50/0x640 [ 168.567454] drm_mode_create+0x40/0x90 [ 168.567458] drm_cvt_mode+0x48/0xc78 [ 168.567477] virtio_gpu_conn_get_modes+0xa8/0x140 [virtio_gpu] [ 168.567485] drm_helper_probe_single_connector_modes+0x3a4/0xd80 [ 168.567492] drm_mode_getconnector+0x2e0/0xa70 [ 168.567496] drm_ioctl_kernel+0x11c/0x1d8 [ 168.567514] drm_ioctl+0x558/0x6d0 [ 168.567522] do_vfs_ioctl+0x160/0xf30 [ 168.567525] ksys_ioctl+0x98/0xd8 [ 168.567530] __arm64_sys_ioctl+0x50/0xc8 [ 168.567536] el0_svc_common+0xc8/0x320 [ 168.567540] el0_svc_handler+0xf8/0x160 [ 168.567544] el0_svc+0x10/0x218 KASAN stacktrace: [ 168.567561] BUG: KASAN: null-ptr-deref in virtio_gpu_conn_get_modes+0xb4/0x140 [virtio_gpu] [ 168.567565] Read of size 4 at addr 0000000000000054 by task syz/6425 [ 168.567566] [ 168.567571] CPU: 1 PID: 6425 Comm: syz Kdump: loaded Not tainted 4.19.90-vhulk2201.1.0.h1035.kasan.eulerosv2r10.aarch64 #1 [ 168.567573] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 168.567575] Call trace: [ 168.567578] dump_backtrace+0x0/0x310 [ 168.567582] show_stack+0x28/0x38 [ 168.567586] dump_stack+0xec/0x15c [ 168.567591] kasan_report+0x244/0x2f0 [ 168.567594] __asan_load4+0x58/0xb0 [ 168.567607] virtio_gpu_conn_get_modes+0xb4/0x140 [virtio_gpu] [ 168.567612] drm_helper_probe_single_connector_modes+0x3a4/0xd80 [ 168.567617] drm_mode_getconnector+0x2e0/0xa70 [ 168.567621] drm_ioctl_kernel+0x11c/0x1d8 [ 168.567624] drm_ioctl+0x558/0x6d0 [ 168.567628] do_vfs_ioctl+0x160/0xf30 [ 168.567632] ksys_ioctl+0x98/0xd8 [ 168.567636] __arm64_sys_ioctl+0x50/0xc8 [ 168.567641] el0_svc_common+0xc8/0x320 [ 168.567645] el0_svc_handler+0xf8/0x160 [ 168.567649] el0_svc+0x10/0x218

Gravité et risque d'exploitation

CVE-2022-49532 obtient un score CVSS de 5.5/10, soit une gravité moyenne. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.32 %, ce qui la place devant 23.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=5.17.*, <0f8bc147a963686b7351aa35d1701124ffacac08, <4.2, 5.15.46, <c51d00472fa54b9b05c17789ed665c17adf3a25d, <edafcad84c4134ebec4bc24b29ca4497a1184eea, 0, 5.19, <=4.9.*, 5.18.3, <=5.10.*, <=4.14.*, 5.10.121, 5.17.14, 4.19.247, 5.4.198, <=5.18.*, <=5.4.*, 4.14.283, <=4.19.*, dc5698e80cf724770283e10414054662bdf6ccfa, 4.2, <e0828456578cc8ba0a69147f7ae3428392eec287, <194d250cdc4a40ccbd179afd522a9e9846957402, <fadc626cae99aaa1325094edc6a9e2b883f3e562, <=*, <=5.15.*, <f85cb059fad03a3b33a50023be91e944bb065ae8, <848dd072744ea662ab3097e3c8282bee552df218, 4.9.318, <32e10aabc287f09a148ff759bb9ce70b01b0012c) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références