Heimdall Security Logo

CVE-2023-53182

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 2.6.12, 5.10.181, 4.14.316, 0, <16359bc02c093b0862e31739c07673340a2106a6, 5.4.244, <=6.3.*, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 6.4, <05bb0167c80b8f93c6a4e0451b7da9b96db990c2, 6.3.4, <=5.10.*, <=4.14.*, 6.1.30, <5a2d0dcb47b16f84880a59571eab8a004e3236d7, <710e09fd116e2fa53e319a416ad4e4f8027682b6, <=5.4.*, <=4.19.*, <35465c7a91c6b46e7c14d0c01d0084349a38ce51, 4.19.284, <3a7a4aa3958ce0c4938a443d65001debe9a9af9c, <8c4a7163b7f1495e3cc58bec7a4100de6612cde9, <=*, <3048c6b84a51e4ba4a89385ed218d19a670edd47, <=5.15.*, 5.15.113

Description

In the Linux kernel, the following vulnerability has been resolved: ACPICA: Avoid undefined behavior: applying zero offset to null pointer ACPICA commit 770653e3ba67c30a629ca7d12e352d83c2541b1e Before this change we see the following UBSAN stack trace in Fuchsia: #0 0x000021e4213b3302 in acpi_ds_init_aml_walk(struct acpi_walk_state*, union acpi_parse_object*, struct acpi_namespace_node*, u8*, u32, struct acpi_evaluate_info*, u8) ../../third_party/acpica/source/components/dispatcher/dswstate.c:682 <platform-bus-x86.so>+0x233302 #1.2 0x000020d0f660777f in ubsan_get_stack_trace() compiler-rt/lib/ubsan/ubsan_diag.cpp:41 <libclang_rt.asan.so>+0x3d77f #1.1 0x000020d0f660777f in maybe_print_stack_trace() compiler-rt/lib/ubsan/ubsan_diag.cpp:51 <libclang_rt.asan.so>+0x3d77f #1 0x000020d0f660777f in ~scoped_report() compiler-rt/lib/ubsan/ubsan_diag.cpp:387 <libclang_rt.asan.so>+0x3d77f #2 0x000020d0f660b96d in handlepointer_overflow_impl() compiler-rt/lib/ubsan/ubsan_handlers.cpp:809 <libclang_rt.asan.so>+0x4196d #3 0x000020d0f660b50d in compiler-rt/lib/ubsan/ubsan_handlers.cpp:815 <libclang_rt.asan.so>+0x4150d #4 0x000021e4213b3302 in acpi_ds_init_aml_walk(struct acpi_walk_state*, union acpi_parse_object*, struct acpi_namespace_node*, u8*, u32, struct acpi_evaluate_info*, u8) ../../third_party/acpica/source/components/dispatcher/dswstate.c:682 <platform-bus-x86.so>+0x233302 #5 0x000021e4213e2369 in acpi_ds_call_control_method(struct acpi_thread_state*, struct acpi_walk_state*, union acpi_parse_object*) ../../third_party/acpica/source/components/dispatcher/dsmethod.c:605 <platform-bus-x86.so>+0x262369 #6 0x000021e421437fac in acpi_ps_parse_aml(struct acpi_walk_state*) ../../third_party/acpica/source/components/parser/psparse.c:550 <platform-bus-x86.so>+0x2b7fac #7 0x000021e4214464d2 in acpi_ps_execute_method(struct acpi_evaluate_info*) ../../third_party/acpica/source/components/parser/psxface.c:244 <platform-bus-x86.so>+0x2c64d2 #8 0x000021e4213aa052 in acpi_ns_evaluate(struct acpi_evaluate_info*) ../../third_party/acpica/source/components/namespace/nseval.c:250 <platform-bus-x86.so>+0x22a052 #9 0x000021e421413dd8 in acpi_ns_init_one_device(acpi_handle, u32, void*, void**) ../../third_party/acpica/source/components/namespace/nsinit.c:735 <platform-bus-x86.so>+0x293dd8 #10 0x000021e421429e98 in acpi_ns_walk_namespace(acpi_object_type, acpi_handle, u32, u32, acpi_walk_callback, acpi_walk_callback, void*, void**) ../../third_party/acpica/source/components/namespace/nswalk.c:298 <platform-bus-x86.so>+0x2a9e98 #11 0x000021e4214131ac in acpi_ns_initialize_devices(u32) ../../third_party/acpica/source/components/namespace/nsinit.c:268 <platform-bus-x86.so>+0x2931ac #12 0x000021e42147c40d in acpi_initialize_objects(u32) ../../third_party/acpica/source/components/utilities/utxfinit.c:304 <platform-bus-x86.so>+0x2fc40d #13 0x000021e42126d603 in acpi::acpi_impl::initialize_acpi(acpi::acpi_impl*) ../../src/devices/board/lib/acpi/acpi-impl.cc:224 <platform-bus-x86.so>+0xed603 Add a simple check that avoids incrementing a pointer by zero, but otherwise behaves as before. Note that our findings are against ACPICA 20221020, but the same code exists on master.

Gravité et risque d'exploitation

CVE-2023-53182 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. 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.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 2.6.12, 5.10.181, 4.14.316, 0, <16359bc02c093b0862e31739c07673340a2106a6, 5.4.244, <=6.3.*, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 6.4, <05bb0167c80b8f93c6a4e0451b7da9b96db990c2, 6.3.4, <=5.10.*, <=4.14.*, 6.1.30, <5a2d0dcb47b16f84880a59571eab8a004e3236d7, <710e09fd116e2fa53e319a416ad4e4f8027682b6, <=5.4.*, <=4.19.*, <35465c7a91c6b46e7c14d0c01d0084349a38ce51, 4.19.284, <3a7a4aa3958ce0c4938a443d65001debe9a9af9c, <8c4a7163b7f1495e3cc58bec7a4100de6612cde9, <=*, <3048c6b84a51e4ba4a89385ed218d19a670edd47, <=5.15.*, 5.15.113) 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