In the Linux kernel, the following vulnerability has been resolved:
media: max9286: Fix memleak in max9286v4l2register()
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: [<00000000191de6a7>] _kmallocnode+0x44/0x1b0 [<000000002f4912b7>] kvmallocnode+0x34/0x180 [<0000000057dc4cae>] v4l2ctrlnew+0x325/0x10f0 [videodev] [<0000000026030272>] v4l2ctrlnewstd+0x16f/0x210 [videodev] [<00000000f0d9ea2f>] max9286probe+0x76e/0xbff [max9286] [<00000000ea8f6455>] i2cdeviceprobe+0x28d/0x680 [<0000000087529af3>] reallyprobe+0x17c/0x3f0 [<00000000b08be526>] _driverprobedevice+0xe3/0x170 [<000000004382edea>] driverprobedevice+0x49/0x120 [<000000007bde528a>] _deviceattachdriver+0xf7/0x150 [<000000009f9c6ab4>] busforeachdrv+0x114/0x180 [<00000000c8aaf588>] _deviceattach+0x1e5/0x2d0 [<0000000041cc06b9>] busprobedevice+0x126/0x140 [<000000002309860d>] deviceadd+0x810/0x1130 [<000000002827bf98>] i2cnewclientdevice+0x359/0x4f0 [<00000000593bdc85>] ofi2cregisterdevice+0xf1/0x110
max9286v4l2register() calls v4l2ctrlnewstd(), but won't free the created v412ctrl when fwnodegraphgetendpointbyid() failed, which causes the memleak. Call v4l2ctrlhandlerfree() to free the v412_ctrl.
{
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53700.json"
}