Heimdall Security Logo

CVE-2023-53234

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 72139dfa2464e43957d330266994740bb7be2535, 0, 5.15.100, f4c36f1999745c2160422fe2f362deadbe3a136b, <4.10, 5.10.173, <c5a21a5501508ae3afa2fe6d5a3e74a37fa48df3, <5.4.235, 4.19.276, <13721a2ac66b246f5802ba1b75ad8637e53eeecc, <23cc41c3f19c4d858c3708f1c0a06e94958e6c3b, <=4.14.*, <=5.10.*, 4.19.93, 6.3, 5.4.8, <ac099d94e0480c937aa9172ab64074981ca1a4d3, <=5.4.*, <5.5, <bf26b0e430ce34261f45959989edaf680b64d538, <=4.19.*, 4.14.182, 4.14.308, 450caf1faa0d7bbbd1da93d3ee8c5edea7bc51a8, <=6.2.*, f76905ce52653e8a821963c35d9013cff19b1399, 5.5, <50808d034e199fe3ff7a9d2068a4eebeb6b4098a, 5.4.235, 6.1.18, <4.19.276, <=*, <=5.15.*, <59e391b3fc507a15b7e8e9d9f4de87cae177c366, 6.2.5, <8c1655600f4f2839fb844fe8c70b2b65fadc7a56, <4.14.308, 4.9.225, ca7851d46de8a8d69022c4e5feed0820483b5f46

Description

In the Linux kernel, the following vulnerability has been resolved: watchdog: Fix kmemleak in watchdog_cdev_register kmemleak reports memory leaks in watchdog_dev_register, as follows: unreferenced object 0xffff888116233000 (size 2048): comm ""modprobe"", pid 28147, jiffies 4353426116 (age 61.741s) hex dump (first 32 bytes): 80 fa b9 05 81 88 ff ff 08 30 23 16 81 88 ff ff .........0#..... 08 30 23 16 81 88 ff ff 00 00 00 00 00 00 00 00 .0#............. backtrace: [<000000007f001ffd>] __kmem_cache_alloc_node+0x157/0x220 [<000000006a389304>] kmalloc_trace+0x21/0x110 [<000000008d640eea>] watchdog_dev_register+0x4e/0x780 [watchdog] [<0000000053c9f248>] __watchdog_register_device+0x4f0/0x680 [watchdog] [<00000000b2979824>] watchdog_register_device+0xd2/0x110 [watchdog] [<000000001f730178>] 0xffffffffc10880ae [<000000007a1a8bcc>] do_one_initcall+0xcb/0x4d0 [<00000000b98be325>] do_init_module+0x1ca/0x5f0 [<0000000046d08e7c>] load_module+0x6133/0x70f0 ... unreferenced object 0xffff888105b9fa80 (size 16): comm ""modprobe"", pid 28147, jiffies 4353426116 (age 61.741s) hex dump (first 16 bytes): 77 61 74 63 68 64 6f 67 31 00 b9 05 81 88 ff ff watchdog1....... backtrace: [<000000007f001ffd>] __kmem_cache_alloc_node+0x157/0x220 [<00000000486ab89b>] __kmalloc_node_track_caller+0x44/0x1b0 [<000000005a39aab0>] kvasprintf+0xb5/0x140 [<0000000024806f85>] kvasprintf_const+0x55/0x180 [<000000009276cb7f>] kobject_set_name_vargs+0x56/0x150 [<00000000a92e820b>] dev_set_name+0xab/0xe0 [<00000000cec812c6>] watchdog_dev_register+0x285/0x780 [watchdog] [<0000000053c9f248>] __watchdog_register_device+0x4f0/0x680 [watchdog] [<00000000b2979824>] watchdog_register_device+0xd2/0x110 [watchdog] [<000000001f730178>] 0xffffffffc10880ae [<000000007a1a8bcc>] do_one_initcall+0xcb/0x4d0 [<00000000b98be325>] do_init_module+0x1ca/0x5f0 [<0000000046d08e7c>] load_module+0x6133/0x70f0 ... The reason is that put_device is not be called if cdev_device_add fails and wdd->id != 0. watchdog_cdev_register wd_data = kzalloc [1] err = dev_set_name [2] .. err = cdev_device_add if (err) { if (wdd->id == 0) { // wdd->id != 0 .. } return err; // [1],[2] would be leaked To fix it, call put_device in all wdd->id cases.

Gravité et risque d'exploitation

CVE-2023-53234 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.16 %, ce qui la place devant 4.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 72139dfa2464e43957d330266994740bb7be2535, 0, 5.15.100, f4c36f1999745c2160422fe2f362deadbe3a136b, <4.10, 5.10.173, <c5a21a5501508ae3afa2fe6d5a3e74a37fa48df3, <5.4.235, 4.19.276, <13721a2ac66b246f5802ba1b75ad8637e53eeecc, <23cc41c3f19c4d858c3708f1c0a06e94958e6c3b, <=4.14.*, <=5.10.*, 4.19.93, 6.3, 5.4.8, <ac099d94e0480c937aa9172ab64074981ca1a4d3, <=5.4.*, <5.5, <bf26b0e430ce34261f45959989edaf680b64d538, <=4.19.*, 4.14.182, 4.14.308, 450caf1faa0d7bbbd1da93d3ee8c5edea7bc51a8, <=6.2.*, f76905ce52653e8a821963c35d9013cff19b1399, 5.5, <50808d034e199fe3ff7a9d2068a4eebeb6b4098a, 5.4.235, 6.1.18, <4.19.276, <=*, <=5.15.*, <59e391b3fc507a15b7e8e9d9f4de87cae177c366, 6.2.5, <8c1655600f4f2839fb844fe8c70b2b65fadc7a56, <4.14.308, 4.9.225, ca7851d46de8a8d69022c4e5feed0820483b5f46) 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

Rechercher une autre CVE