Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
uce a potential performance regression as struct kcm_mux can be shared by multiple KCM sockets. So we have to enforce skb queue lock in requeue_rx_msgs() and handle skb peek case carefully in kcm_wait_data(). Fortunately, skb_recv_datagram() already handles it nicely and is widely used by other sockets, we can just switch to skb_recv_datagram() after getting rid of the unnecessary sock lock in kcm_recvmsg() and kcm_splice_read(). Side note: SOCK_DONE is not used by KCM sockets, so it is safe to get rid of this check too. I ran the original syzbot reproducer for 30 min without seeing any issue. References: - https://git.kernel.org/stable/c/22f6b5d47396b4287662668ee3f5c1f766cb4259 - https://gi
ut seeing any issue. References: - https://git.kernel.org/stable/c/22f6b5d47396b4287662668ee3f5c1f766cb4259 - https://git.kernel.org/stable/c/d9ad4de92e184b19bcae4da10dac0275abf83931 - https://git.kernel.org/stable/c/ce57d6474ae999a3b2d442314087473a646a65c7 - https://git.kernel.org/stable/c/4154b6afa2bd639214ff259d912faad984f7413a - https://git.kernel.org/stable/c/f7b0e95071bb4be4b811af3f0bfc3e200eedeaa3 - https://git.kernel.org/stable/c/bf92e54597d842da127c59833b365d6faeeaf020 - https://git.kernel.org/stable/c/5121197ecc5db58c07da95eb1ff82b98b121a221
CVE ID: CVE-2022-49815 State: PUBLISHED Published: 2025-05-01T14:09:39.016Z Last Updated: 2025-05-04T08:45:56.085Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: erofs: fix missing xas_retry() in fscache mode The xarray iteration only holds the RCU read lock and thus may encounter XA_RETRY_ENTRY if there's process modifying the xarray concurrently. This will cause oops when referring to the invalid entry. Fix this by adding the missing xas_retry(), which will make the iteration wind back to the root node if XA_RETRY_ENTRY is encountered. References: - https://git.kernel.org/stable/c/dbc98fe99e17ed18f2f272d5fe880d844b1c68c3 - ht
_RETRY_ENTRY is encountered. References: - https://git.kernel.org/stable/c/dbc98fe99e17ed18f2f272d5fe880d844b1c68c3 - https://git.kernel.org/stable/c/37020bbb71d911431e16c2c940b97cf86ae4f2f6
CVE ID: CVE-2022-49816 State: REJECTED Published: 2025-05-01T14:09:39.654Z Last Updated: 2025-05-02T05:35:06.465Z Description: No description available.
CVE ID: CVE-2022-49817 State: PUBLISHED Published: 2025-05-01T14:09:40.325Z Last Updated: 2025-05-04T08:45:57.391Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: mhi: Fix memory leak in mhi_net_dellink() MHI driver registers network device without setting the needs_free_netdev flag, and does NOT call free_netdev() when unregisters network device, which causes a memory leak. This patch calls free_netdev() to fix it since netdev_priv is used after unregister. References: - https://git.kernel.org/stable/c/88da008e5e2f9753726ea5a51ef2eb144e9de927 - https://git.kernel.org/stable/c/25a270343b0f16e1f6e65f541a15975a35e238ff - http
da008e5e2f9753726ea5a51ef2eb144e9de927 - https://git.kernel.org/stable/c/25a270343b0f16e1f6e65f541a15975a35e238ff - https://git.kernel.org/stable/c/f7c125bd79f50ec6094761090be81d02726ec6f4
CVE ID: CVE-2022-49818 State: PUBLISHED Published: 2025-05-01T14:09:40.957Z Last Updated: 2025-05-04T08:45:58.787Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mISDN: fix misuse of put_device() in mISDN_register_device() We should not release reference by put_device() before calling device_initialize(). References: - https://git.kernel.org/stable/c/44658d65f6b3118f595a1229d7eed74845a5e2ac - https://git.kernel.org/stable/c/81db4f182744acd004f17d7cc52dde9ea53467e6 - https://git.kernel.org/stable/c/d40b35a7922f4df3767ad6fb8ef3dc86e31d7ba3 - https://git.kernel.org/stable/c/83672c1b83d107b0d4fe0accf1bf64d8988398e6 - https://git.ke
4df3767ad6fb8ef3dc86e31d7ba3 - https://git.kernel.org/stable/c/83672c1b83d107b0d4fe0accf1bf64d8988398e6 - https://git.kernel.org/stable/c/709aa1f73d3e9e9ea16e2c4e44f2874c5d2c382c - https://git.kernel.org/stable/c/596230471da3415e92ae6b9d2a4e26f4a81cac5a - https://git.kernel.org/stable/c/87b336aa158201dc30a318431e63e8c5b26c4156 - https://git.kernel.org/stable/c/2d25107e111a85c56f601a5470f1780ec054e6ac
CVE ID: CVE-2022-49819 State: PUBLISHED Published: 2025-05-01T14:09:41.606Z Last Updated: 2025-05-04T08:46:00.339Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: octeon_ep: fix potential memory leak in octep_device_setup() When occur unsupported_dev and mbox init errors, it did not free oct->conf and iounmap() oct->mmio[i].hw_addr. That would trigger memory leak problem. Add kfree() for oct->conf and iounmap() for oct->mmio[i].hw_addr under unsupported_dev and mbox init errors to fix the problem. References: - https://git.kernel.org/stable/c/67b65a0db8a7fdad43159819f41335497a4bb04f - https://git.kernel.org/stable/c/e4041be97b15
https://git.kernel.org/stable/c/67b65a0db8a7fdad43159819f41335497a4bb04f - https://git.kernel.org/stable/c/e4041be97b15302ebfffda8bbd45f3b2d096048f
CVE ID: CVE-2022-49820 State: PUBLISHED Published: 2025-05-01T14:09:42.252Z Last Updated: 2025-05-04T08:46:02.200Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mctp i2c: don't count unused / invalid keys for flow release We're currently hitting the WARN_ON in mctp_i2c_flow_release: if (midev->release_count > midev->i2c_lock_count) { WARN_ONCE(1, "release count overflow"); This may be hit if we expire a flow before sending the first packet it contains - as we will not be pairing the increment of release_count (performed on flow release) with the i2c lock operation (only performed on actual TX). To fix this, only release a flow
(performed on flow release) with the i2c lock operation (only performed on actual TX). To fix this, only release a flow if we've encountered it previously (ie, dev_flow_state does not indicate NEW), as we will mark the flow as ACTIVE at the same time as accounting for the i2c lock operation. We also need to add an INVALID flow state, to indicate when we've done the release. References: - https://git.kernel.org/stable/c/a5915a9a3ab4067ef8996a57738d156eabeb3a12 - https://git.kernel.org/stable/c/9cbd48d5fa14e4c65f8580de16686077f7cea02b
CVE ID: CVE-2022-49821 State: PUBLISHED Published: 2025-05-01T14:09:42.901Z Last Updated: 2025-05-04T08:46:03.507Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mISDN: fix possible memory leak in mISDN_dsp_element_register() Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically, use put_device() to give up the reference, so that the name can be freed in kobject_cleanup() when the refcount is 0. The 'entry' is going to be freed in mISDN_dsp_dev_release(), so the kfree() is removed. list_del() is called in mISDN_dsp_dev_release(), so it need be initi
mISDN_dsp_dev_release(), so the kfree() is removed. list_del() is called in mISDN_dsp_dev_release(), so it need be initialized. References: - https://git.kernel.org/stable/c/bbd53d05c4c892080ef3b617eff4f57903acecb9 - https://git.kernel.org/stable/c/b119bedbefb7dd9ed8bf8cb9f1056504250d610e - https://git.kernel.org/stable/c/727ed7d28348c026c7ef4d852f3d0e5054d376e8 - https://git.kernel.org/stable/c/0f2c681900a01e3f23789bca26d88268c3d5b51d - https://git.kernel.org/stable/c/083a2c9ef82e184bdf0b9f9a1e5fc38d32afbb47 - https://git.kernel.org/stable/c/7a05e3929668c8cfef495c69752a9e91fac4878f - https://git.kernel.org/stable/c/d4b8394725079670be309f9a35ad88a8cbbaaefd - https://git.kernel.org/stable/c/9
1fac4878f - https://git.kernel.org/stable/c/d4b8394725079670be309f9a35ad88a8cbbaaefd - https://git.kernel.org/stable/c/98a2ac1ca8fd6eca6867726fe238d06e75eb1acd
CVE ID: CVE-2022-49822 State: PUBLISHED Published: 2025-05-01T14:09:43.572Z Last Updated: 2025-05-04T08:46:05.156Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cifs: Fix connections leak when tlink setup failed If the tlink setup failed, lost to put the connections, then the module refcnt leak since the cifsd kthread not exit. Also leak the fscache info, and for next mount with fsc, it will print the follow errors: CIFS: Cache volume key already in use (cifs,127.0.0.1:445,TEST) Let's check the result of tlink setup, and do some cleanup. References: - https://git.kernel.org/stable/c/a9059e338fc000c0b87d8cf29e93c74fd703212e - h
k setup, and do some cleanup. References: - https://git.kernel.org/stable/c/a9059e338fc000c0b87d8cf29e93c74fd703212e - https://git.kernel.org/stable/c/0a087842d10b5daa123ee5291e386cdd78413705 - https://git.kernel.org/stable/c/1dcdf5f5b2137185cbdd5385f29949ab3da4f00c
CVE ID: CVE-2022-49823 State: PUBLISHED Published: 2025-05-01T14:09:44.205Z Last Updated: 2025-05-04T08:46:11.440Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ata: libata-transport: fix error handling in ata_tdev_add() In ata_tdev_add(), the return value of transport_add_device() is not checked. As a result, it causes null-ptr-deref while removing the module, because transport_remove_device() is called to remove the device that was not added. Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0 CPU: 13 PID: 13603 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #36 pstate: 60400009 (nZCv daif
ss 00000000000000d0 CPU: 13 PID: 13603 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #36 pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : device_del+0x48/0x3a0 lr : device_del+0x44/0x3a0 Call trace: device_del+0x48/0x3a0 attribute_container_class_device_del+0x28/0x40 transport_remove_classdev+0x60/0x7c attribute_container_device_trigger+0x118/0x120 transport_remove_device+0x20/0x30 ata_tdev_delete+0x24/0x50 [libata] ata_tlink_delete+0x40/0xa0 [libata] ata_tport_delete+0x2c/0x60 [libata] ata_port_detach+0x148/0x1b0 [libata] ata_pci_remove_one+0x50/0x80 [libata] ahci_remove_one+0x4c/0x8c [ahci] Fix this by checking and handling return value of transport_add_device() in
0 [libata] ahci_remove_one+0x4c/0x8c [ahci] Fix this by checking and handling return value of transport_add_device() in ata_tdev_add(). In the error path, device_del() is called to delete the device which was added earlier in this function, and ata_tdev_free() is called to free ata_dev. References: - https://git.kernel.org/stable/c/ef2ac07ab83163b9a53f45da20e14302591ad9cc - https://git.kernel.org/stable/c/f23058dc2398db1d8faca9a2b1ce30b85cdd8b22 - https://git.kernel.org/stable/c/f54331962883f4fc4bf5e487e6e7cf07c4567fef - https://git.kernel.org/stable/c/1ff36351309e3eadcff297480baf4785e726de9b
CVE ID: CVE-2022-49824 State: PUBLISHED Published: 2025-05-01T14:09:44.852Z Last Updated: 2025-05-04T08:46:12.688Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ata: libata-transport: fix error handling in ata_tlink_add() In ata_tlink_add(), the return value of transport_add_device() is not checked. As a result, it causes null-ptr-deref while removing the module, because transport_remove_device() is called to remove the device that was not added. Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0 CPU: 33 PID: 13850 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #12 pstate: 60400009 (nZCv da
ress 00000000000000d0 CPU: 33 PID: 13850 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #12 pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : device_del+0x48/0x39c lr : device_del+0x44/0x39c Call trace: device_del+0x48/0x39c attribute_container_class_device_del+0x28/0x40 transport_remove_classdev+0x60/0x7c attribute_container_device_trigger+0x118/0x120 transport_remove_device+0x20/0x30 ata_tlink_delete+0x88/0xb0 [libata] ata_tport_delete+0x2c/0x60 [libata] ata_port_detach+0x148/0x1b0 [libata] ata_pci_remove_one+0x50/0x80 [libata] ahci_remove_one+0x4c/0x8c [ahci] Fix this by checking and handling return value of transport_add_device() in ata_tlink_add(). References: - ht
x8c [ahci] Fix this by checking and handling return value of transport_add_device() in ata_tlink_add(). References: - https://git.kernel.org/stable/c/7377a14598f6b04446c54bc4a50cd249470d6c6f - https://git.kernel.org/stable/c/67b219314628b90b3a314528e177335b0cd5c70b - https://git.kernel.org/stable/c/d5234480ca822bdcf03fe4d6a590ddcb854558f7 - https://git.kernel.org/stable/c/cf0816f6322c5c37ee52655f928e91ecf32da103
CVE ID: CVE-2022-49825 State: PUBLISHED Published: 2025-05-01T14:09:45.524Z Last Updated: 2025-05-04T08:46:14.218Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ata: libata-transport: fix error handling in ata_tport_add() In ata_tport_add(), the return value of transport_add_device() is not checked. As a result, it causes null-ptr-deref while removing the module, because transport_remove_device() is called to remove the device that was not added. Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0 CPU: 12 PID: 13605 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #8 pstate: 60400009 (nZCv dai
ress 00000000000000d0 CPU: 12 PID: 13605 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #8 pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : device_del+0x48/0x39c lr : device_del+0x44/0x39c Call trace: device_del+0x48/0x39c attribute_container_class_device_del+0x28/0x40 transport_remove_classdev+0x60/0x7c attribute_container_device_trigger+0x118/0x120 transport_remove_device+0x20/0x30 ata_tport_delete+0x34/0x60 [libata] ata_port_detach+0x148/0x1b0 [libata] ata_pci_remove_one+0x50/0x80 [libata] ahci_remove_one+0x4c/0x8c [ahci] Fix this by checking and handling return value of transport_add_device() in ata_tport_add(). References: - https://git.kernel.org/stable/c/b5362dc
andling return value of transport_add_device() in ata_tport_add(). References: - https://git.kernel.org/stable/c/b5362dc1634d8b8d5f30920f33ac11a3276b7ed9 - https://git.kernel.org/stable/c/e7bb1b7a7bf26f6b7372b7b683daece4a42fda02 - https://git.kernel.org/stable/c/52d9bb0adae9359711a0c5271430afd3754069e7 - https://git.kernel.org/stable/c/3613dbe3909dcc637fe6be00e4dc43b4aa0470ee
CVE ID: CVE-2022-49826 State: PUBLISHED Published: 2025-05-01T14:09:46.145Z Last Updated: 2025-05-04T08:46:15.287Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ata: libata-transport: fix double ata_host_put() in ata_tport_add() In the error path in ata_tport_add(), when calling put_device(), ata_tport_release() is called, it will put the refcount of 'ap->host'. And then ata_host_put() is called again, the refcount is decreased to 0, ata_host_release() is called, all ports are freed and set to null. When unbinding the device after failure, ata_host_stop() is called to release the resources, it leads a null-ptr-deref(), because
nding the device after failure, ata_host_stop() is called to release the resources, it leads a null-ptr-deref(), because all the ports all freed and null. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 CPU: 7 PID: 18671 Comm: modprobe Kdump: loaded Tainted: G E 6.1.0-rc3+ #8 pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ata_host_stop+0x3c/0x84 [libata] lr : release_nodes+0x64/0xd0 Call trace: ata_host_stop+0x3c/0x84 [libata] release_nodes+0x64/0xd0 devres_release_all+0xbc/0x1b0 device_unbind_cleanup+0x20/0x70 really_probe+0x158/0x320 __driver_probe_device+0x84/0x120 driver_probe_device+0x44/0x120 __driver_attach+0xb4/0x220 bus_for_
ly_probe+0x158/0x320 __driver_probe_device+0x84/0x120 driver_probe_device+0x44/0x120 __driver_attach+0xb4/0x220 bus_for_each_dev+0x78/0xdc driver_attach+0x2c/0x40 bus_add_driver+0x184/0x240 driver_register+0x80/0x13c __pci_register_driver+0x4c/0x60 ahci_pci_driver_init+0x30/0x1000 [ahci] Fix this by removing redundant ata_host_put() in the error path. References: - https://git.kernel.org/stable/c/30e12e2be27ac6c4be2af4163c70db381364706f - https://git.kernel.org/stable/c/bec9ded5404cb14e5f5470103d0973a2ff83d6a5 - https://git.kernel.org/stable/c/ac471468f7c16cda2525909946ca13ddbcd14000 - https://git.kernel.org/stable/c/377ff82c33c0cb74562a353361b64b33c09562cf - https://git.kernel.org/stable/c/
ddbcd14000 - https://git.kernel.org/stable/c/377ff82c33c0cb74562a353361b64b33c09562cf - https://git.kernel.org/stable/c/865a6da40ba092c18292ae5f6194756131293745 - https://git.kernel.org/stable/c/8c76310740807ade5ecdab5888f70ecb6d35732e
CVE ID: CVE-2022-49827 State: PUBLISHED Published: 2025-05-01T14:09:46.805Z Last Updated: 2025-05-04T08:46:16.624Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm: Fix potential null-ptr-deref in drm_vblank_destroy_worker() drm_vblank_init() call drmm_add_action_or_reset() with drm_vblank_init_release() as action. If __drmm_add_action() failed, will directly call drm_vblank_init_release() with the vblank whose worker is NULL. As the resule, a null-ptr-deref will happen in kthread_destroy_worker(). Add the NULL check before calling drm_vblank_destroy_worker(). BUG: null-ptr-deref KASAN: null-ptr-deref in range [0x000000000000
ULL check before calling drm_vblank_destroy_worker(). BUG: null-ptr-deref KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f] CPU: 5 PID: 961 Comm: modprobe Not tainted 6.0.0-11331-gd465bff130bf-dirty RIP: 0010:kthread_destroy_worker+0x25/0xb0 Call Trace: <TASK> drm_vblank_init_release+0x124/0x220 [drm] ? drm_crtc_vblank_restore+0x8b0/0x8b0 [drm] __drmm_add_action_or_reset+0x41/0x50 [drm] drm_vblank_init+0x282/0x310 [drm] vkms_init+0x35f/0x1000 [vkms] ? 0xffffffffc4508000 ? lock_is_held_type+0xd7/0x130 ? __kmem_cache_alloc_node+0x1c2/0x2b0 ? lock_is_held_type+0xd7/0x130 ? 0xffffffffc4508000 do_one_initcall+0xd0/0x4f0 ... do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwfra
type+0xd7/0x130 ? 0xffffffffc4508000 do_one_initcall+0xd0/0x4f0 ... do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 References: - https://git.kernel.org/stable/c/1d160dfb3fdf11ba9447e862c548447f91f4e74a - https://git.kernel.org/stable/c/e884a6c2d49a6c12761e5bed851e9fe93bd923a1 - https://git.kernel.org/stable/c/3acd2016421b2e628acad65495d15493bf7a3bc3 - https://git.kernel.org/stable/c/4979524f5a2a8210e87fde2f642b0dc060860821
CVE ID: CVE-2022-49828 State: PUBLISHED Published: 2025-05-01T14:09:47.443Z Last Updated: 2025-05-04T08:46:17.822Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: don't delete error page from pagecache This change is very similar to the change that was made for shmem [1], and it solves the same problem but for HugeTLBFS instead. Currently, when poison is found in a HugeTLB page, the page is removed from the page cache. That means that attempting to map or read that hugepage in the future will result in a new hugepage being allocated instead of notifying the user that the page was poisoned. As [1] states, this is effec
in a new hugepage being allocated instead of notifying the user that the page was poisoned. As [1] states, this is effectively memory corruption. The fix is to leave the page in the page cache. If the user attempts to use a poisoned HugeTLB page with a syscall, the syscall will fail with EIO, the same error code that shmem uses. For attempts to map the page, the thread will get a BUS_MCEERR_AR SIGBUS. [1]: commit a76054266661 ("mm: shmem: don't truncate page if memory failure happens") References: - https://git.kernel.org/stable/c/30571f28bb35c826219971c63bcf60d2517112ed - https://git.kernel.org/stable/c/ec667443b2dbc6cdbbac4073e51a17733158ec6a - https://git.kernel.org/stable/c/8625147cafaa9
https://git.kernel.org/stable/c/ec667443b2dbc6cdbbac4073e51a17733158ec6a - https://git.kernel.org/stable/c/8625147cafaa9ba74713d682f5185eb62cb2aedb
CVE ID: CVE-2022-49829 State: PUBLISHED Published: 2025-05-01T14:09:48.227Z Last Updated: 2025-10-29T10:50:05.545Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/scheduler: fix fence ref counting We leaked dependency fences when processes were beeing killed. Additional to that grab a reference to the last scheduled fence. References: - https://git.kernel.org/stable/c/e5f4b38362df93594cb426b04979d8834122f159 - https://git.kernel.org/stable/c/b3af84383e7abdc5e63435817bb73a268e7c3637
CVE ID: CVE-2022-49830 State: PUBLISHED Published: 2025-05-01T14:09:48.918Z Last Updated: 2025-05-04T08:46:25.368Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/drv: Fix potential memory leak in drm_dev_init() drm_dev_init() will add drm_dev_init_release() as a callback. When drmm_add_action() failed, the release function won't be added. As the result, the ref cnt added by device_get() in drm_dev_init() won't be put by drm_dev_init_release(), which leads to the memleak. Use drmm_add_action_or_reset() instead of drmm_add_action() to prevent memleak. unreferenced object 0xffff88810bc0c800 (size 2048): comm "modprobe", pid 83
ead of drmm_add_action() to prevent memleak. unreferenced object 0xffff88810bc0c800 (size 2048): comm "modprobe", pid 8322, jiffies 4305809845 (age 15.292s) hex dump (first 32 bytes): e8 cc c0 0b 81 88 ff ff ff ff ff ff 00 00 00 00 ................ 20 24 3c 0c 81 88 ff ff 18 c8 c0 0b 81 88 ff ff $<............. backtrace: [<000000007251f72d>] __kmalloc+0x4b/0x1c0 [<0000000045f21f26>] platform_device_alloc+0x2d/0xe0 [<000000004452a479>] platform_device_register_full+0x24/0x1c0 [<0000000089f4ea61>] 0xffffffffa0736051 [<00000000235b2441>] do_one_initcall+0x7a/0x380 [<0000000001a4a177>] do_init_module+0x5c/0x230 [<000000002bf8a8e2>] load_module+0x227d/0x2420 [<00000000637d6d0a>] __do_sys_finit_m
1a4a177>] do_init_module+0x5c/0x230 [<000000002bf8a8e2>] load_module+0x227d/0x2420 [<00000000637d6d0a>] __do_sys_finit_module+0xd5/0x140 [<00000000c99fc324>] do_syscall_64+0x3f/0x90 [<000000004d85aa77>] entry_SYSCALL_64_after_hwframe+0x63/0xcd References: - https://git.kernel.org/stable/c/c47a823ea186263ab69cfb665327b7f72cb5e779 - https://git.kernel.org/stable/c/07e56de8766fe5be67252596244b84ac0ec0de91 - https://git.kernel.org/stable/c/bd8d1335e6e70a396094ef98913b513140c0b86b - https://git.kernel.org/stable/c/ff963634f7b2e0dc011349abb3fb81a0d074f443
CVE ID: CVE-2022-49831 State: PUBLISHED Published: 2025-05-01T14:09:49.617Z Last Updated: 2025-05-04T08:46:26.594Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: initialize device's zone info for seeding When performing seeding on a zoned filesystem it is necessary to initialize each zoned device's btrfs_zoned_device_info structure, otherwise mounting the filesystem will cause a NULL pointer dereference. This was uncovered by fstests' testcase btrfs/163. References: - https://git.kernel.org/stable/c/91c38504e589dadbcde47b1cacdfc5b684154d44 - https://git.kernel.org/stable/c/544f38a738343d7e75f104e5e9d1ade58d8b71bd
e/c/91c38504e589dadbcde47b1cacdfc5b684154d44 - https://git.kernel.org/stable/c/544f38a738343d7e75f104e5e9d1ade58d8b71bd - https://git.kernel.org/stable/c/a8d1b1647bf8244a5f270538e9e636e2657fffa3
CVE ID: CVE-2022-49832 State: PUBLISHED Published: 2025-05-01T14:09:50.435Z Last Updated: 2025-05-04T08:46:28.117Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map Here is the BUG report by KASAN about null pointer dereference: BUG: KASAN: null-ptr-deref in strcmp+0x2e/0x50 Read of size 1 at addr 0000000000000000 by task python3/2640 Call Trace: strcmp __of_find_property of_find_property pinctrl_dt_to_map kasprintf() would return NULL pointer when kmalloc() fail to allocate. So directly return ENOMEM, if kasprintf() return NULL pointer. References: - https:/