Threat and Vulnerability Intelligence Database

Example Searches:

CVE-2023-52869	pstore/platform: Add check for kstrdup Description: In the Linux kernel, the following vulnerability has been resolved: pstore/platform: Add check for kstrdup Add check for the return value of kstrdup() and return the error if it fails in order to avoid NULL pointer dereference. EPSS Score: 0.04% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52868	thermal: core: prevent potential string overflow Description: In the Linux kernel, the following vulnerability has been resolved: thermal: core: prevent potential string overflow The dev->id value comes from ida_alloc() so it's a number between zero and INT_MAX. If it's too high then these sprintf()s will overflow. EPSS Score: 0.04% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52867	drm/radeon: possible buffer overflow Description: In the Linux kernel, the following vulnerability has been resolved: drm/radeon: possible buffer overflow Buffer 'afmt_status' of size 6 could overflow, since index 'afmt_idx' is checked after access. EPSS Score: 0.04% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52866	HID: uclogic: Fix user-memory-access bug in uclogic_params_ugee_v2_init_event_hooks() Description: In the Linux kernel, the following vulnerability has been resolved: HID: uclogic: Fix user-memory-access bug in uclogic_params_ugee_v2_init_event_hooks() When CONFIG_HID_UCLOGIC=y and CONFIG_KUNIT_ALL_TESTS=y, launch kernel and then the below user-memory-access bug occurs. In hid_test_uclogic_params_cleanup_event_hooks(),it call uclogic_params_ugee_v2_init_event_hooks() with the first arg=NULL, so when it calls uclogic_params_ugee_v2_has_battery(), the hid_get_drvdata() will access hdev->dev with hdev=NULL, which will cause below user-memory-access. So add a fake_device with quirks member and call hid_set_drvdata() to assign hdev->dev->driver_data which avoids the null-ptr-def bug for drvdata->quirks in uclogic_params_ugee_v2_has_battery(). After applying this patch, the below user-memory-access bug never occurs. general protection fault, probably for non-canonical address 0xdffffc0000000329: 0000 [#1] PREEMPT SMP KASAN KASAN: probably user-memory-access in range [0x0000000000001948-0x000000000000194f] CPU: 5 PID: 2189 Comm: kunit_try_catch Tainted: G B W N 6.6.0-rc2+ #30 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:uclogic_params_ugee_v2_init_event_hooks+0x87/0x600 Code: f3 f3 65 48 8b 14 25 28 00 00 00 48 89 54 24 60 31 d2 48 89 fa c7 44 24 30 00 00 00 00 48 c7 44 24 28 02 f8 02 01 48 c1 ea 03 <80> 3c 02 00 0f 85 2c 04 00 00 48 8b 9d 48 19 00 00 48 b8 00 00 00 RSP: 0000:ffff88810679fc88 EFLAGS: 00010202... EPSS Score: 0.05% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52865	clk: mediatek: clk-mt6797: Add check for mtk_alloc_clk_data Description: In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6797: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference. EPSS Score: 0.04% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52864	platform/x86: wmi: Fix opening of char device Description: In the Linux kernel, the following vulnerability has been resolved: platform/x86: wmi: Fix opening of char device Since commit fa1f68db6ca7 ("drivers: misc: pass miscdevice pointer via file private data"), the miscdevice stores a pointer to itself inside filp->private_data, which means that private_data will not be NULL when wmi_char_open() is called. This might cause memory corruption should wmi_char_open() be unable to find its driver, something which can happen when the associated WMI device is deleted in wmi_free_devices(). Fix the problem by using the miscdevice pointer to retrieve the WMI device data associated with a char device using container_of(). This also avoids wmi_char_open() picking a wrong WMI device bound to a driver with the same name as the original driver. EPSS Score: 0.04% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52863	hwmon: (axi-fan-control) Fix possible NULL pointer dereference Description: In the Linux kernel, the following vulnerability has been resolved: hwmon: (axi-fan-control) Fix possible NULL pointer dereference axi_fan_control_irq_handler(), dependent on the private axi_fan_control_data structure, might be called before the hwmon device is registered. That will cause an "Unable to handle kernel NULL pointer dereference" error. EPSS Score: 0.04% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52862	drm/amd/display: Fix null pointer dereference in error message Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix null pointer dereference in error message This patch fixes a null pointer dereference in the error message that is printed when the Display Core (DC) fails to initialize. The original message includes the DC version number, which is undefined if the DC is not initialized. EPSS Score: 0.05% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52861	drm: bridge: it66121: Fix invalid connector dereference Description: In the Linux kernel, the following vulnerability has been resolved: drm: bridge: it66121: Fix invalid connector dereference Fix the NULL pointer dereference when no monitor is connected, and the sound card is opened from userspace. Instead return an empty buffer (of zeroes) as the EDID information to the sound framework if there is no connector attached. EPSS Score: 0.05% Source: CVE December 20th, 2024 (5 months ago)
CVE-2023-52860	drivers/perf: hisi: use cpuhp_state_remove_instance_nocalls() for hisi_hns3_pmu uninit process Description: In the Linux kernel, the following vulnerability has been resolved: drivers/perf: hisi: use cpuhp_state_remove_instance_nocalls() for hisi_hns3_pmu uninit process When tearing down a 'hisi_hns3' PMU, we mistakenly run the CPU hotplug callbacks after the device has been unregistered, leading to fireworks when we try to execute empty function callbacks within the driver: \| Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 \| CPU: 0 PID: 15 Comm: cpuhp/0 Tainted: G W O 5.12.0-rc4+ #1 \| Hardware name: , BIOS KpxxxFPGA 1P B600 V143 04/22/2021 \| pstate: 80400009 (Nzcv daif +PAN -UAO -TCO BTYPE=--) \| pc : perf_pmu_migrate_context+0x98/0x38c \| lr : perf_pmu_migrate_context+0x94/0x38c \| \| Call trace: \| perf_pmu_migrate_context+0x98/0x38c \| hisi_hns3_pmu_offline_cpu+0x104/0x12c [hisi_hns3_pmu] Use cpuhp_state_remove_instance_nocalls() instead of cpuhp_state_remove_instance() so that the notifiers don't execute after the PMU device has been unregistered. [will: Rewrote commit message] EPSS Score: 0.05% Source: CVE December 20th, 2024 (5 months ago)