Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
5] ? drm_privacy_screen_get+0x16d/0x190 [drm] ? acpi_dev_found+0x64/0x80 i915_pci_probe+0xac/0x1b0 [i915] ... According to the definition of sseu_dev_info, eu_mask->hsw is limited to a maximum of GEN_MAX_SS_PER_HSW_SLICE (6) sub-slices, but gen11_sseu_info_init() can potentially set 8 sub-slices, in the !IS_JSL_EHL(gt->i915) case. Fix this by reserving up to 8 slots for max_subslices in the eu_mask struct. (cherry picked from commit 3cba09a6ac86ea1d456909626eb2685596c07822) References: - https://git.kernel.org/stable/c/1a1682abf7399318ac074b1f2ac6a8c992b5b3da - https://git.kernel.org/stable/c/36b076ab6247cf0d2135b2ad6bb337617c3b5a1b - https://git.kernel.org/stable/c/193c41926d152761764894f46
kernel.org/stable/c/36b076ab6247cf0d2135b2ad6bb337617c3b5a1b - https://git.kernel.org/stable/c/193c41926d152761764894f46e23b53c00186a82
CVE ID: CVE-2023-53113 State: PUBLISHED Published: 2025-05-02T15:55:52.393Z Last Updated: 2025-05-04T12:50:26.011Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: nl80211: fix NULL-ptr deref in offchan check If, e.g. in AP mode, the link was already created by userspace but not activated yet, it has a chandef but the chandef isn't valid and has no channel. Check for this and ignore this link. References: - https://git.kernel.org/stable/c/87e80ea4fbc9ce2f2005905fdbcd38baaa47463a - https://git.kernel.org/stable/c/201a836c2385fdd2b9d0a8e7737bba5b26f1863a - https://git.kernel.org/stable/c/f624bb6fad23df3270580b4fcef415c6e7bf77
able/c/201a836c2385fdd2b9d0a8e7737bba5b26f1863a - https://git.kernel.org/stable/c/f624bb6fad23df3270580b4fcef415c6e7bf7705
CVE ID: CVE-2023-53114 State: PUBLISHED Published: 2025-05-02T15:55:53.230Z Last Updated: 2025-05-04T07:50:08.215Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: i40e: Fix kernel crash during reboot when adapter is in recovery mode If the driver detects during probe that firmware is in recovery mode then i40e_init_recovery_mode() is called and the rest of probe function is skipped including pci_set_drvdata(). Subsequent i40e_shutdown() called during shutdown/reboot dereferences NULL pointer as pci_get_drvdata() returns NULL. To fix call pci_set_drvdata() also during entering to recovery mode. Reproducer: 1) Lets have i40e NIC w
) returns NULL. To fix call pci_set_drvdata() also during entering to recovery mode. Reproducer: 1) Lets have i40e NIC with firmware in recovery mode 2) Run reboot Result: [ 139.084698] i40e: Intel(R) Ethernet Connection XL710 Network Driver [ 139.090959] i40e: Copyright (c) 2013 - 2019 Intel Corporation. [ 139.108438] i40e 0000:02:00.0: Firmware recovery mode detected. Limiting functionality. [ 139.116439] i40e 0000:02:00.0: Refer to the Intel(R) Ethernet Adapters and Devices User Guide for details on firmware recovery mode. [ 139.129499] i40e 0000:02:00.0: fw 8.3.64775 api 1.13 nvm 8.30 0x8000b78d 1.3106.0 [8086:1583] [15d9:084a] [ 139.215932] i40e 0000:02:00.0 enp2s0f0: renamed from eth0
i 1.13 nvm 8.30 0x8000b78d 1.3106.0 [8086:1583] [15d9:084a] [ 139.215932] i40e 0000:02:00.0 enp2s0f0: renamed from eth0 [ 139.223292] i40e 0000:02:00.1: Firmware recovery mode detected. Limiting functionality. [ 139.231292] i40e 0000:02:00.1: Refer to the Intel(R) Ethernet Adapters and Devices User Guide for details on firmware recovery mode. [ 139.244406] i40e 0000:02:00.1: fw 8.3.64775 api 1.13 nvm 8.30 0x8000b78d 1.3106.0 [8086:1583] [15d9:084a] [ 139.329209] i40e 0000:02:00.1 enp2s0f1: renamed from eth0 ... [ 156.311376] BUG: kernel NULL pointer dereference, address: 00000000000006c2 [ 156.318330] #PF: supervisor write access in kernel mode [ 156.323546] #PF: error_code(0x0002) - not-pre
000000000006c2 [ 156.318330] #PF: supervisor write access in kernel mode [ 156.323546] #PF: error_code(0x0002) - not-present page [ 156.328679] PGD 0 P4D 0 [ 156.331210] Oops: 0002 [#1] PREEMPT SMP NOPTI [ 156.335567] CPU: 26 PID: 15119 Comm: reboot Tainted: G E 6.2.0+ #1 [ 156.343126] Hardware name: Abacus electric, s.r.o. - servis@abacus.cz Super Server/H12SSW-iN, BIOS 2.4 04/13/2022 [ 156.353369] RIP: 0010:i40e_shutdown+0x15/0x130 [i40e] [ 156.358430] Code: c1 fc ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 55 48 89 fd 53 48 8b 9f 48 01 00 00 <f0> 80 8b c2 06 00 00 04 f0 80 8b c0 06 00 00 08 48 8d bb 08 08 00 [ 156.377168] RSP: 0018:ffffb223c8447d90
8 01 00 00 <f0> 80 8b c2 06 00 00 04 f0 80 8b c0 06 00 00 08 48 8d bb 08 08 00 [ 156.377168] RSP: 0018:ffffb223c8447d90 EFLAGS: 00010282 [ 156.382384] RAX: ffffffffc073ee70 RBX: 0000000000000000 RCX: 0000000000000001 [ 156.389510] RDX: 0000000080000001 RSI: 0000000000000246 RDI: ffff95db49988000 [ 156.396634] RBP: ffff95db49988000 R08: ffffffffffffffff R09: ffffffff8bd17d40 [ 156.403759] R10: 0000000000000001 R11: ffffffff8a5e3d28 R12: ffff95db49988000 [ 156.410882] R13: ffffffff89a6fe17 R14: ffff95db49988150 R15: 0000000000000000 [ 156.418007] FS: 00007fe7c0cc3980(0000) GS:ffff95ea8ee80000(0000) knlGS:0000000000000000 [ 156.426083] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 156.4318
:ffff95ea8ee80000(0000) knlGS:0000000000000000 [ 156.426083] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 156.431819] CR2: 00000000000006c2 CR3: 00000003092fc005 CR4: 0000000000770ee0 [ 156.438944] PKRU: 55555554 [ 156.441647] Call Trace: [ 156.444096] <TASK> [ 156.446199] pci_device_shutdown+0x38/0x60 [ 156.450297] device_shutdown+0x163/0x210 [ 156.454215] kernel_restart+0x12/0x70 [ 156.457872] __do_sys_reboot+0x1ab/0x230 [ 156.461789] ? vfs_writev+0xa6/0x1a0 [ 156.465362] ? __pfx_file_free_rcu+0x10/0x10 [ 156.469635] ? __call_rcu_common.constprop.85+0x109/0x5a0 [ 156.475034] do_syscall_64+0x3e/0x90 [ 156.478611] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 156.483658] RIP: 0033:0x7fe7b
6.475034] do_syscall_64+0x3e/0x90 [ 156.478611] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 156.483658] RIP: 0033:0x7fe7bff37ab7 References: - https://git.kernel.org/stable/c/6e18f66b704bd725196508c1db93bf7338cdc8de - https://git.kernel.org/stable/c/3cbecb1c9085a00155639404f7addbcbfc987ba3 - https://git.kernel.org/stable/c/4ff82695266576a0b4f1077a7100b2451e476df4 - https://git.kernel.org/stable/c/c703362a66ea971905b9dc153fc54d1b6ac05423 - https://git.kernel.org/stable/c/b3826fb3ea14646b3d4e6309bfc384b349f36eb6 - https://git.kernel.org/stable/c/7e4f8a0c495413a50413e8c9f1032ce1bc633bae
CVE ID: CVE-2023-53115 State: PUBLISHED Published: 2025-05-02T15:55:54.148Z Last Updated: 2025-05-04T07:50:09.375Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() Don't allocate memory again when IOC is being reinitialized. References: - https://git.kernel.org/stable/c/5aab9342f12f980b64617a034d121efbbf09100a - https://git.kernel.org/stable/c/7277b4eec2f25a0653646ba95b1f25fa16be1d6c - https://git.kernel.org/stable/c/c798304470cab88723d895726d17fcb96472e0e9
CVE ID: CVE-2023-53116 State: PUBLISHED Published: 2025-05-02T15:55:54.858Z Last Updated: 2025-05-04T07:50:10.667Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nvmet: avoid potential UAF in nvmet_req_complete() An nvme target ->queue_response() operation implementation may free the request passed as argument. Such implementation potentially could result in a use after free of the request pointer when percpu_ref_put() is called in nvmet_req_complete(). Avoid such problem by using a local variable to save the sq pointer before calling __nvmet_req_complete(), thus avoiding dereferencing the req pointer after that function call.
sq pointer before calling __nvmet_req_complete(), thus avoiding dereferencing the req pointer after that function call. References: - https://git.kernel.org/stable/c/e5d99b29012bbf0e86929403209723b2806500c1 - https://git.kernel.org/stable/c/fafcb4b26393870c45462f9af6a48e581dbbcf7e - https://git.kernel.org/stable/c/04c394208831d5e0d5cfee46722eb0f033cd4083 - https://git.kernel.org/stable/c/a6317235da8aa7cb97529ebc8121cc2a4c4c437a - https://git.kernel.org/stable/c/f1d5888a5efe345b63c430b256e95acb0a475642 - https://git.kernel.org/stable/c/bcd535f07c58342302a2cd2bdd8894fe0872c8a9 - https://git.kernel.org/stable/c/8ed9813871038b25a934b21ab76b5b7dbf44fc3a - https://git.kernel.org/stable/c/6173a77b7
9 - https://git.kernel.org/stable/c/8ed9813871038b25a934b21ab76b5b7dbf44fc3a - https://git.kernel.org/stable/c/6173a77b7e9d3e202bdb9897b23f2a8afe7bf286
CVE ID: CVE-2023-53117 State: PUBLISHED Published: 2025-05-02T15:55:55.512Z Last Updated: 2025-05-04T07:50:11.802Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: fs: prevent out-of-bounds array speculation when closing a file descriptor Google-Bug-Id: 114199369 References: - https://git.kernel.org/stable/c/f31cd5da636682caea424fa1c22679016cbfc16b - https://git.kernel.org/stable/c/3d5d9501b634fd268eb56428cda92cd317752d69 - https://git.kernel.org/stable/c/6631c8da02cfad96c53b217cf647b511c7f34faf - https://git.kernel.org/stable/c/a759905de9cd6ec9ca08ceadf0920272772ed830 - https://git.kernel.org/stable/c/f8cd8754a03a3748384ee438c57
rnel.org/stable/c/a759905de9cd6ec9ca08ceadf0920272772ed830 - https://git.kernel.org/stable/c/f8cd8754a03a3748384ee438c572423643c9c315 - https://git.kernel.org/stable/c/cec08b7d1ebcd3138d4658b3868ce26aeb1e8e06 - https://git.kernel.org/stable/c/eea8e4e056a5ffbeb539a13854c017d5d62c756a - https://git.kernel.org/stable/c/609d54441493c99f21c1823dfd66fa7f4c512ff4
CVE ID: CVE-2023-53118 State: PUBLISHED Published: 2025-05-02T15:55:56.177Z Last Updated: 2025-05-04T12:50:27.394Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix a procfs host directory removal regression scsi_proc_hostdir_rm() decreases a reference counter and hence must only be called once per host that is removed. This change does not require a scsi_add_host_with_dma() change since scsi_add_host_with_dma() will return 0 (success) if scsi_proc_host_add() is called. References: - https://git.kernel.org/stable/c/88c3d3bb6469cea929ac68fd326bdcbefcdfdd83 - https://git.kernel.org/stable/c/68c665bb185037e7eb66fb792c
ernel.org/stable/c/88c3d3bb6469cea929ac68fd326bdcbefcdfdd83 - https://git.kernel.org/stable/c/68c665bb185037e7eb66fb792c61da9d7151e99c - https://git.kernel.org/stable/c/2a764d55e938743efa7c2cba7305633bcf227f09 - https://git.kernel.org/stable/c/7e0ae8667fcdd99d1756922e1140cac75f5fa279 - https://git.kernel.org/stable/c/73f030d4ef6d1ad17f824a0a2eb637ef7a9c7d51 - https://git.kernel.org/stable/c/be03df3d4bfe7e8866d4aa43d62e648ffe884f5f
CVE ID: CVE-2023-53119 State: PUBLISHED Published: 2025-05-02T15:55:56.818Z Last Updated: 2025-05-04T07:50:14.684Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: initialize struct pn533_out_arg properly struct pn533_out_arg used as a temporary context for out_urb is not initialized properly. Its uninitialized 'phy' field can be dereferenced in error cases inside pn533_out_complete() callback function. It causes the following failure: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU:
fffc0000000000: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.2.0-rc3-next-20230110-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:pn533_out_complete.cold+0x15/0x44 drivers/nfc/pn533/usb.c:441 Call Trace: <IRQ> __usb_hcd_giveback_urb+0x2b6/0x5c0 drivers/usb/core/hcd.c:1671 usb_hcd_giveback_urb+0x384/0x430 drivers/usb/core/hcd.c:1754 dummy_timer+0x1203/0x32d0 drivers/usb/gadget/udc/dummy_hcd.c:1988 call_timer_fn+0x1da/0x800 kernel/time/timer.c:1700 expire_timers+0x234/0x330 kernel/time/timer.c:1751 __run_timers kernel/time/timer.c:2
1da/0x800 kernel/time/timer.c:1700 expire_timers+0x234/0x330 kernel/time/timer.c:1751 __run_timers kernel/time/timer.c:2022 [inline] __run_timers kernel/time/timer.c:1995 [inline] run_timer_softirq+0x326/0x910 kernel/time/timer.c:2035 __do_softirq+0x1fb/0xaf6 kernel/softirq.c:571 invoke_softirq kernel/softirq.c:445 [inline] __irq_exit_rcu+0x123/0x180 kernel/softirq.c:650 irq_exit_rcu+0x9/0x20 kernel/softirq.c:662 sysvec_apic_timer_interrupt+0x97/0xc0 arch/x86/kernel/apic/apic.c:1107 Initialize the field with the pn533_usb_phy currently used. Found by Linux Verification Center (linuxtesting.org) with Syzkaller. References: - https://git.kernel.org/stable/c/2bd1ed6d607d7013ed4959e86990a04f0285
er (linuxtesting.org) with Syzkaller. References: - https://git.kernel.org/stable/c/2bd1ed6d607d7013ed4959e86990a04f028543ef - https://git.kernel.org/stable/c/4c20a07ed26a71a8ccc9c6d935fc181573f5462e - https://git.kernel.org/stable/c/0f9c1f26d434c32520dfe33326b28c5954bc4299 - https://git.kernel.org/stable/c/2703da78849c47b6b5b4471edb35fc7b7f91dead - https://git.kernel.org/stable/c/2bee84369b76f6c9ef71938069c65a6ebd1a12f7 - https://git.kernel.org/stable/c/a97ef110c491b72c138111a595a3a3af56cbc94c - https://git.kernel.org/stable/c/2cbd4213baf7be5d87d183e2032c54003de0790f - https://git.kernel.org/stable/c/484b7059796e3bc1cb527caa61dfc60da649b4f6
CVE ID: CVE-2023-53120 State: PUBLISHED Published: 2025-05-02T15:55:57.483Z Last Updated: 2025-05-04T07:50:16.091Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix config page DMA memory leak A fix for: DMA-API: pci 0000:83:00.0: device driver has pending DMA allocations while released from device [count=1] References: - https://git.kernel.org/stable/c/dca06ccf13de14e144d34f158f73ae0032f80e63 - https://git.kernel.org/stable/c/5fc4d698ed4b6507be2eb36d040a678adcb89da4 - https://git.kernel.org/stable/c/7d2b02172b6a2ae6aecd7ef6480b9c4bf3dc59f4
CVE ID: CVE-2023-53121 State: PUBLISHED Published: 2025-05-02T15:55:58.123Z Last Updated: 2025-05-04T07:50:17.260Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_make_synack() can be called from process context tcp_rtx_synack() now could be called in process context as explained in 0a375c822497 ("tcp: tcp_rtx_synack() can be called from process context"). tcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU variables with preemption enabled. This causes the following BUG: BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464 caller is tcp_make_synack+0x841/0xac0 Call Trace: <TASK
__this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464 caller is tcp_make_synack+0x841/0xac0 Call Trace: <TASK> dump_stack_lvl+0x10d/0x1a0 check_preemption_disabled+0x104/0x110 tcp_make_synack+0x841/0xac0 tcp_v6_send_synack+0x5c/0x450 tcp_rtx_synack+0xeb/0x1f0 inet_rtx_syn_ack+0x34/0x60 tcp_check_req+0x3af/0x9e0 tcp_rcv_state_process+0x59b/0x2030 tcp_v6_do_rcv+0x5f5/0x700 release_sock+0x3a/0xf0 tcp_sendmsg+0x33/0x40 ____sys_sendmsg+0x2f2/0x490 __sys_sendmsg+0x184/0x230 do_syscall_64+0x3d/0x90 Avoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use TCP_INC_STATS() which is safe to be called from context switch. References: - https://git.kernel.org/stable/c/d493d4fe881
CP_INC_STATS() which is safe to be called from context switch. References: - https://git.kernel.org/stable/c/d493d4fe88195a144d6a277a90062a7534ed2192 - https://git.kernel.org/stable/c/e23ca307745be3df7fe9762f3e2a7e311a57852e - https://git.kernel.org/stable/c/442aa78ed70188b21ccd8669738448702c0a3281 - https://git.kernel.org/stable/c/77ad58bca0119e8cc3e0e9d91a3f22caa66e4dfa - https://git.kernel.org/stable/c/ad07290d63ff6689f50565b02f5b6f34ec15a5ca - https://git.kernel.org/stable/c/9180aa4622a720b433e842b4d3aa34d73eec577a - https://git.kernel.org/stable/c/7613cde8c0c1f02a7ec2e1d536c01b65b135fc1c - https://git.kernel.org/stable/c/bced3f7db95ff2e6ca29dc4d1c9751ab5e736a09
CVE ID: CVE-2023-53122 State: REJECTED Published: 2025-05-02T15:55:58.795Z Last Updated: 2025-05-08T10:26:44.002Z Description: No description available.
CVE ID: CVE-2023-53123 State: PUBLISHED Published: 2025-05-02T15:55:59.580Z Last Updated: 2025-05-04T07:50:19.788Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: PCI: s390: Fix use-after-free of PCI resources with per-function hotplug On s390 PCI functions may be hotplugged individually even when they belong to a multi-function device. In particular on an SR-IOV device VFs may be removed and later re-added. In commit a50297cf8235 ("s390/pci: separate zbus creation from scanning") it was missed however that struct pci_bus and struct zpci_bus's resource list retained a reference to the PCI functions MMIO resources even though tho
uct pci_bus and struct zpci_bus's resource list retained a reference to the PCI functions MMIO resources even though those resources are released and freed on hot-unplug. These stale resources may subsequently be claimed when the PCI function re-appears resulting in use-after-free. One idea of fixing this use-after-free in s390 specific code that was investigated was to simply keep resources around from the moment a PCI function first appeared until the whole virtual PCI bus created for a multi-function device disappears. The problem with this however is that due to the requirement of artificial MMIO addreesses (address cookies) extra logic is then needed to keep the address cookies compatib
uirement of artificial MMIO addreesses (address cookies) extra logic is then needed to keep the address cookies compatible on re-plug. At the same time the MMIO resources semantically belong to the PCI function so tying their lifecycle to the function seems more logical. Instead a simpler approach is to remove the resources of an individually hot-unplugged PCI function from the PCI bus's resource list while keeping the resources of other PCI functions on the PCI bus untouched. This is done by introducing pci_bus_remove_resource() to remove an individual resource. Similarly the resource also needs to be removed from the struct zpci_bus's resource list. It turns out however, that there is real
the resource also needs to be removed from the struct zpci_bus's resource list. It turns out however, that there is really no need to add the MMIO resources to the struct zpci_bus's resource list at all and instead we can simply use the zpci_bar_struct's resource pointer directly. References: - https://git.kernel.org/stable/c/437bb839e36cc9f35adc6d2a2bf113b7a0fc9985 - https://git.kernel.org/stable/c/a2410d0c3d2d714ed968a135dfcbed6aa3ff7027 - https://git.kernel.org/stable/c/b99ebf4b62774e690e73a551cf5fbf6f219bdd96 - https://git.kernel.org/stable/c/ab909509850b27fd39b8ba99e44cda39dbc3858c
CVE ID: CVE-2023-53124 State: PUBLISHED Published: 2025-05-02T15:56:00.500Z Last Updated: 2025-05-04T12:50:29.100Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add() Port is allocated by sas_port_alloc_num() and rphy is allocated by either sas_end_device_alloc() or sas_expander_alloc(), all of which may return NULL. So we need to check the rphy to avoid possible NULL pointer access. If sas_rphy_add() returned with failure, rphy is set to NULL. We would access the rphy in the following lines which would also result NULL pointer access. References: - https://git.k
We would access the rphy in the following lines which would also result NULL pointer access. References: - https://git.kernel.org/stable/c/090305c36185c0547e4441d4c08f1cf096b32134 - https://git.kernel.org/stable/c/6f0c2f70d9929208d8427ec72c3ed91e2251e289 - https://git.kernel.org/stable/c/9937f784a608944107dcc2ba9a9c3333f8330b9e - https://git.kernel.org/stable/c/b5e5bbb3fa5f8412e96c5eda7f4a4af6241d6bd3 - https://git.kernel.org/stable/c/a26c775ccc4cfe46f9b718b51bd24313053c7e0b - https://git.kernel.org/stable/c/d3c57724f1569311e4b81e98fad0931028b9bdcd
CVE ID: CVE-2023-53125 State: PUBLISHED Published: 2025-05-02T15:56:01.140Z Last Updated: 2025-05-04T07:50:22.048Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: usb: smsc75xx: Limit packet length to skb->len Packet length retrieved from skb data may be larger than the actual socket buffer length (up to 9026 bytes). In such case the cloned skb passed up the network stack will leak kernel memory contents. References: - https://git.kernel.org/stable/c/4a4de0a68b18485c68ab4f0cfa665b1633c6d277 - https://git.kernel.org/stable/c/53966d572d056d6b234cfe76a5f9d60049d3c178 - https://git.kernel.org/stable/c/9fabdd79051a9fe51388df099a
ernel.org/stable/c/53966d572d056d6b234cfe76a5f9d60049d3c178 - https://git.kernel.org/stable/c/9fabdd79051a9fe51388df099aff6e4b660fedd2 - https://git.kernel.org/stable/c/e294f0aa47e4844f3d3c8766c02accd5a76a7d4e - https://git.kernel.org/stable/c/105db6574281e1e03fcbf87983f4fee111682306 - https://git.kernel.org/stable/c/c7bdc137ca163b90917c1eeba4f1937684bd4f8b - https://git.kernel.org/stable/c/8ee5df9c039e37b9d8eb5e3de08bfb7f53d31cb6 - https://git.kernel.org/stable/c/d8b228318935044dafe3a5bc07ee71a1f1424b8d
CVE ID: CVE-2023-53126 State: PUBLISHED Published: 2025-05-02T15:56:02.077Z Last Updated: 2025-05-04T07:50:28.192Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() Free mrioc->sas_hba.phy at .remove. References: - https://git.kernel.org/stable/c/480aae2f30637b5140e9c7a9b10298e538df2b5e - https://git.kernel.org/stable/c/c60a7c7508645a9f36e4a18a5f548fb79378acd1 - https://git.kernel.org/stable/c/d4caa1a4255cc44be56bcab3db2c97c632e6cc10
CVE ID: CVE-2023-53127 State: PUBLISHED Published: 2025-05-02T15:56:03.058Z Last Updated: 2025-05-04T07:50:29.544Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() Add a missing resource clean up in .remove. References: - https://git.kernel.org/stable/c/0023972a7593720f8878aed06c03ac9e541078be - https://git.kernel.org/stable/c/cf9777be5683c5e55680c089df02ee27d2226aa8 - https://git.kernel.org/stable/c/ce756daa36e1ba271bb3334267295e447aa57a5c
CVE ID: CVE-2023-53128 State: PUBLISHED Published: 2025-05-02T15:56:03.674Z Last Updated: 2025-05-04T07:50:30.643Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix throttle_groups memory leak Add a missing kfree(). References: - https://git.kernel.org/stable/c/574cc10edaa7dba833764efed8c57ee0e6bf7574 - https://git.kernel.org/stable/c/85349a227eb4a56520adc190c666075f80d4ae70 - https://git.kernel.org/stable/c/f305a7b6ca21a665e8d0cf70b5936991a298c93c
CVE ID: CVE-2023-53129 State: REJECTED Published: 2025-05-02T15:56:04.366Z Last Updated: 2025-05-08T10:27:34.990Z Description: No description available.
CVE ID: CVE-2023-53130 State: REJECTED Published: 2025-05-02T15:56:04.996Z Last Updated: 2025-05-08T10:28:33.229Z Description: No description available.
CVE ID: CVE-2023-53131 State: PUBLISHED Published: 2025-05-02T15:56:05.646Z Last Updated: 2025-05-04T12:50:30.338Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix a server shutdown leak Fix a race where kthread_stop() may prevent the threadfn from ever getting called. If that happens the svc_rqst will not be cleaned up. References: - https://git.kernel.org/stable/c/ce7dd61e004002bc1c48d1ca47c887f3f3cc7370 - https://git.kernel.org/stable/c/ad7e40ee157ba33950a4ccdc284334580da3638d - https://git.kernel.org/stable/c/7a3720361068ab520aed4608bad31ea9a6cc7fe7 - https://git.kernel.org/stable/c/f74b3286859463cd63cc9d4aeaabd8b
.org/stable/c/7a3720361068ab520aed4608bad31ea9a6cc7fe7 - https://git.kernel.org/stable/c/f74b3286859463cd63cc9d4aeaabd8b0c640182a - https://git.kernel.org/stable/c/9ca6705d9d609441d34f8b853e1e4a6369b3b171