Direct naar de inhoud
⚡ Kritieke cyberalerts voor jouw sector & systemen — direct in je inbox. Aanmelden →
cybernieuws.nl Cybersecurity en informatiebeveiling nieuws alerts live · 9 min 165 bronnen 1 kritiek 16 vandaag
CVE's Videos Dagbriefing

← Terug naar CVE-database

CVE-2023-53700

NONE Gepubliceerd:

Beschrijving NL

In the Linux kernel, the following vulnerability has been resolved:

media: max9286: Fix memleak in max9286_v4l2_register()

There is a kmemleak when testing the media/i2c/max9286.c with bpf mock
device:

kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

unreferenced object 0xffff88810defc400 (size 256):
comm "python3", pid 278, jiffies 4294737563 (age 31.978s)
hex dump (first 32 bytes):
28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff (........ ."..... 10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff ................ backtrace:
[] __kmalloc_node+0x44/0x1b0
[] kvmalloc_node+0x34/0x180
[] v4l2_ctrl_new+0x325/0x10f0 [videodev]
[] v4l2_ctrl_new_std+0x16f/0x210 [videodev]
[] max9286_probe+0x76e/0xbff [max9286]
[] i2c_device_probe+0x28d/0x680
[] really_probe+0x17c/0x3f0
[] __driver_probe_device+0xe3/0x170
[] driver_probe_device+0x49/0x120
[] __device_attach_driver+0xf7/0x150
[] bus_for_each_drv+0x114/0x180
[] __device_attach+0x1e5/0x2d0
[] bus _probe_device+0x126/0x140
[] device_add+0x810/0x1130
[] i2c_new_client_device+0x359/0x4f0
[] of_i2c_register_device+0xf1/0x110

max9286_v4l2_register() calls v4l2_ctrl_new_std(), but won't free the
created v412_ctrl when fwnode_graph_get_endpoint_by_id() failed, which
causes the memleak. Call v4l2_ctrl_handler_free() to free the v412_ctrl.

Origineel (Engels) tonen

In the Linux kernel, the following vulnerability has been resolved:

media: max9286: Fix memleak in max9286_v4l2_register()

There is a kmemleak when testing the media/i2c/max9286.c with bpf mock
device:

kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

unreferenced object 0xffff88810defc400 (size 256):
comm "python3", pid 278, jiffies 4294737563 (age 31.978s)
hex dump (first 32 bytes):
28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff (.........".....
10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff ................
backtrace:
[] __kmalloc_node+0x44/0x1b0
[] kvmalloc_node+0x34/0x180
[] v4l2_ctrl_new+0x325/0x10f0 [videodev]
[] v4l2_ctrl_new_std+0x16f/0x210 [videodev]
[] max9286_probe+0x76e/0xbff [max9286]
[] i2c_device_probe+0x28d/0x680
[] really_probe+0x17c/0x3f0
[] __driver_probe_device+0xe3/0x170
[] driver_probe_device+0x49/0x120
[] __device_attach_driver+0xf7/0x150
[] bus_for_each_drv+0x114/0x180
[] __device_attach+0x1e5/0x2d0
[] bus_probe_device+0x126/0x140
[] device_add+0x810/0x1130
[] i2c_new_client_device+0x359/0x4f0
[] of_i2c_register_device+0xf1/0x110

max9286_v4l2_register() calls v4l2_ctrl_new_std(), but won't free the
created v412_ctrl when fwnode_graph_get_endpoint_by_id() failed, which
causes the memleak. Call v4l2_ctrl_handler_free() to free the v412_ctrl.

References