Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2021-47347 State: PUBLISHED Published: 2024-05-21T14:35:52.947Z Last Updated: 2025-05-04T07:09:06.157Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wl1251: Fix possible buffer overflow in wl1251_cmd_scan Function wl1251_cmd_scan calls memcpy without checking the length. Harden by checking the length is within the maximum allowed size. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/57ad99ae3c6738ba87bad259bb57c641ca68ebf6 - https://git.kernel.org/stable/c/d3d8b9c9c7843dce31e284927d4c9904fd5a510a - https://git.kernel.org/stable/c/0f6c0488368c
https://git.kernel.org/stable/c/d3d8b9c9c7843dce31e284927d4c9904fd5a510a - https://git.kernel.org/stable/c/0f6c0488368c9ac1aa685821916fadba32f5d1ef - https://git.kernel.org/stable/c/115103f6e3f1c26c473766c16439c7c8b235529a - https://git.kernel.org/stable/c/d71dddeb5380613f9ef199f3e7368fd78fb1a46e - https://git.kernel.org/stable/c/c5e4a10d7bd5d4f419d8b9705dff60cf69b302a1 - https://git.kernel.org/stable/c/302e2ee34c5f7c5d805b7f835d9a6f2b43474e2a - https://git.kernel.org/stable/c/40af3960a15339e8bbd3be50c3bc7b35e1a0b6ea - https://git.kernel.org/stable/c/d10a87a3535cce2b890897914f5d0d83df669c63
CVE ID: CVE-2021-47348 State: PUBLISHED Published: 2024-05-21T14:35:53.613Z Last Updated: 2025-09-15T12:14:05.400Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid HDCP over-read and corruption Instead of reading the desired 5 bytes of the actual target field, the code was reading 8. This could result in a corrupted value if the trailing 3 bytes were non-zero, so instead use an appropriately sized and zero-initialized bounce buffer, and read only 5 bytes before casting to u64. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c5b518f4b9
nalyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c5b518f4b98dbb2bc31b6a55e6aaa1e0e2948f2e - https://git.kernel.org/stable/c/44c7c901cb368a9f2493748f213b247b5872639f - https://git.kernel.org/stable/c/3b2b93a485fb7a970bc8b5daef16f4cf579d172f - https://git.kernel.org/stable/c/06888d571b513cbfc0b41949948def6cb81021b2
CVE ID: CVE-2021-47349 State: PUBLISHED Published: 2024-05-21T14:35:54.314Z Last Updated: 2025-05-04T07:09:08.342Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mwifiex: bring down link before deleting interface We can deadlock when rmmod'ing the driver or going through firmware reset, because the cfg80211_unregister_wdev() has to bring down the link for us, ... which then grab the same wiphy lock. nl80211_del_interface() already handles a very similar case, with a nice description: /* * We hold RTNL, so this is safe, without RTNL opencount cannot * reach 0, and thus the rdev cannot be deleted. * * We need to do it for the dev
is safe, without RTNL opencount cannot * reach 0, and thus the rdev cannot be deleted. * * We need to do it for the dev_close(), since that will call * the netdev notifiers, and we need to acquire the mutex there * but don't know if we get there from here or from some other * place (e.g. "ip link set ... down"). */ mutex_unlock(&rdev->wiphy.mtx); ... Do similarly for mwifiex teardown, by ensuring we bring the link down first. Sample deadlock trace: [ 247.103516] INFO: task rmmod:2119 blocked for more than 123 seconds. [ 247.110630] Not tainted 5.12.4 #5 [ 247.115796] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.124557] task:rmmod state:D stack: 0 pid: 2119
0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.124557] task:rmmod state:D stack: 0 pid: 2119 ppid: 2114 flags:0x00400208 [ 247.133905] Call trace: [ 247.136644] __switch_to+0x130/0x170 [ 247.140643] __schedule+0x714/0xa0c [ 247.144548] schedule_preempt_disabled+0x88/0xf4 [ 247.149714] __mutex_lock_common+0x43c/0x750 [ 247.154496] mutex_lock_nested+0x5c/0x68 [ 247.158884] cfg80211_netdev_notifier_call+0x280/0x4e0 [cfg80211] [ 247.165769] raw_notifier_call_chain+0x4c/0x78 [ 247.170742] call_netdevice_notifiers_info+0x68/0xa4 [ 247.176305] __dev_close_many+0x7c/0x138 [ 247.180693] dev_close_many+0x7c/0x10c [ 247.184893] unregister_netdevice_many+0xfc/0x654 [ 247.1901
se_many+0x7c/0x138 [ 247.180693] dev_close_many+0x7c/0x10c [ 247.184893] unregister_netdevice_many+0xfc/0x654 [ 247.190158] unregister_netdevice_queue+0xb4/0xe0 [ 247.195424] _cfg80211_unregister_wdev+0xa4/0x204 [cfg80211] [ 247.201816] cfg80211_unregister_wdev+0x20/0x2c [cfg80211] [ 247.208016] mwifiex_del_virtual_intf+0xc8/0x188 [mwifiex] [ 247.214174] mwifiex_uninit_sw+0x158/0x1b0 [mwifiex] [ 247.219747] mwifiex_remove_card+0x38/0xa0 [mwifiex] [ 247.225316] mwifiex_pcie_remove+0xd0/0xe0 [mwifiex_pcie] [ 247.231451] pci_device_remove+0x50/0xe0 [ 247.235849] device_release_driver_internal+0x110/0x1b0 [ 247.241701] driver_detach+0x5c/0x9c [ 247.245704] bus_remove_driver+0x84/0xb8 [ 247.25009
_driver_internal+0x110/0x1b0 [ 247.241701] driver_detach+0x5c/0x9c [ 247.245704] bus_remove_driver+0x84/0xb8 [ 247.250095] driver_unregister+0x3c/0x60 [ 247.254486] pci_unregister_driver+0x2c/0x90 [ 247.259267] cleanup_module+0x18/0xcdc [mwifiex_pcie] Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/a3041d39d3c14da97fa3476835aba043ba810cf0 - https://git.kernel.org/stable/c/35af69c7c0490fdccfc159c6a87e4d1dc070838a - https://git.kernel.org/stable/c/1f9482aa8d412b4ba06ce6ab8e333fb8ca29a06e
CVE ID: CVE-2021-47350 State: PUBLISHED Published: 2024-05-21T14:35:55.154Z Last Updated: 2025-05-04T07:09:09.428Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/mm: Fix lockup on kernel exec fault The powerpc kernel is not prepared to handle exec faults from kernel. Especially, the function is_exec_fault() will return 'false' when an exec fault is taken by kernel, because the check is based on reading current->thread.regs->trap which contains the trap from user. For instance, when provoking a LKDTM EXEC_USERSPACE test, current->thread.regs->trap is set to SYSCALL trap (0xc00), and the fault taken by the kernel is not s
EC_USERSPACE test, current->thread.regs->trap is set to SYSCALL trap (0xc00), and the fault taken by the kernel is not seen as an exec fault by set_access_flags_filter(). Commit d7df2443cd5f ("powerpc/mm: Fix spurious segfaults on radix with autonuma") made it clear and handled it properly. But later on commit d3ca587404b3 ("powerpc/mm: Fix reporting of kernel execute faults") removed that handling, introducing test based on error_code. And here is the problem, because on the 603 all upper bits of SRR1 get cleared when the TLB instruction miss handler bails out to ISI. Until commit cbd7e6ca0210 ("powerpc/fault: Avoid heavy search_exception_tables() verification"), an exec fault from kernel a
l commit cbd7e6ca0210 ("powerpc/fault: Avoid heavy search_exception_tables() verification"), an exec fault from kernel at a userspace address was indirectly caught by the lack of entry for that address in the exception tables. But after that commit the kernel mainly relies on KUAP or on core mm handling to catch wrong user accesses. Here the access is not wrong, so mm handles it. It is a minor fault because PAGE_EXEC is not set, set_access_flags_filter() should set PAGE_EXEC and voila. But as is_exec_fault() returns false as explained in the beginning, set_access_flags_filter() bails out without setting PAGE_EXEC flag, which leads to a forever minor exec fault. As the kernel is not prepared
er() bails out without setting PAGE_EXEC flag, which leads to a forever minor exec fault. As the kernel is not prepared to handle such exec faults, the thing to do is to fire in bad_kernel_fault() for any exec fault taken by the kernel, as it was prior to commit d3ca587404b3. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/a82471a14aad90f79d1608d2bcbb019f0ffb53f0 - https://git.kernel.org/stable/c/d2e52d4664097a6c1f591d869ec594bd7a0d4925 - https://git.kernel.org/stable/c/500f81cec9f1bfa5210aa9dd5ba9a06e22f62a35 - https://git.kernel.org/stable/c/8a96ec5ebf96ad8e2ba7b1b34103a0be5140fc70 - https://git.kernel.org/stable/c/c
e22f62a35 - https://git.kernel.org/stable/c/8a96ec5ebf96ad8e2ba7b1b34103a0be5140fc70 - https://git.kernel.org/stable/c/cd5d5e602f502895e47e18cd46804d6d7014e65c
CVE ID: CVE-2021-47351 State: PUBLISHED Published: 2024-05-21T14:35:55.806Z Last Updated: 2025-05-04T07:09:10.505Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix races between xattr_{set|get} and listxattr operations UBIFS may occur some problems with concurrent xattr_{set|get} and listxattr operations, such as assertion failure, memory corruption, stale xattr value[1]. Fix it by importing a new rw-lock in @ubifs_inode to serilize write operations on xattr, concurrent read operations are still effective, just like ext4. [1] https://lore.kernel.org/linux-mtd/20200630130438.141649-1-houtao1@huawei.com Additional Analys
tive, just like ext4. [1] https://lore.kernel.org/linux-mtd/20200630130438.141649-1-houtao1@huawei.com Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/7adc05b73d91a5e3d4ca7714fa53ad9b70c53d08 - https://git.kernel.org/stable/c/38dde03eb239605f428f3f1e4baa73d4933a4cc6 - https://git.kernel.org/stable/c/9558612cb829f2c022b788f55d6b8437d5234a82 - https://git.kernel.org/stable/c/c0756f75c22149d20fcb7d8409827cee905eb386 - https://git.kernel.org/stable/c/f4e3634a3b642225a530c292fdb1e8a4007507f5
CVE ID: CVE-2021-47352 State: PUBLISHED Published: 2024-05-21T14:35:56.473Z Last Updated: 2025-05-04T07:09:11.539Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: virtio-net: Add validation for used length This adds validation for used length (might come from an untrusted device) to avoid data corruption or loss. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c1b40d1959517ff2ea473d40eeab4691d6d62462 - https://git.kernel.org/stable/c/c92298d228f61589dd21657af2bea95fc866b813 - https://git.kernel.org/stable/c/3133e01514c3c498f2b01ff210ee6134b70c663c - https:
98d228f61589dd21657af2bea95fc866b813 - https://git.kernel.org/stable/c/3133e01514c3c498f2b01ff210ee6134b70c663c - https://git.kernel.org/stable/c/ba710baa1cc1b17a0483f7befe03e696efd17292 - https://git.kernel.org/stable/c/ad993a95c508417acdeb15244109e009e50d8758
CVE ID: CVE-2021-47353 State: PUBLISHED Published: 2024-05-21T14:35:57.122Z Last Updated: 2025-05-04T07:09:12.716Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: udf: Fix NULL pointer dereference in udf_symlink function In function udf_symlink, epos.bh is assigned with the value returned by udf_tgetblk. The function udf_tgetblk is defined in udf/misc.c and returns the value of sb_getblk function that could be NULL. Then, epos.bh is used without any check, causing a possible NULL pointer dereference when sb_getblk fails. This fix adds a check to validate the value of epos.bh. Additional Analyst Notes: - CISA ADP Vulnrichment: -
blk fails. This fix adds a check to validate the value of epos.bh. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/2f3d9ddd32a28803baa547e6274983b67d5e287c - https://git.kernel.org/stable/c/371566f63cbd0bb6fbb25b8fe9d5798268d35af9 - https://git.kernel.org/stable/c/baea588a42d675e35daeaddd10fbc9700550bc4d - https://git.kernel.org/stable/c/3638705ecd5ad2785e996f820121c0ad15ce64b5 - https://git.kernel.org/stable/c/80d505aee6398cf8beb72475c7edcf1733c1c68b - https://git.kernel.org/stable/c/21bf1414580c36ffc8d8de043beb3508cf812238 - https://git.kernel.org/stable/c/aebed6b19e51a34003d998da5ebb1dfdd2cb1d02 - https://git.kernel
c8d8de043beb3508cf812238 - https://git.kernel.org/stable/c/aebed6b19e51a34003d998da5ebb1dfdd2cb1d02 - https://git.kernel.org/stable/c/5150877e4d99f85057a458daac7cd7c01005d5c6 - https://git.kernel.org/stable/c/fa236c2b2d4436d9f19ee4e5d5924e90ffd7bb43
CVE ID: CVE-2021-47354 State: PUBLISHED Published: 2024-05-21T14:35:57.772Z Last Updated: 2025-07-29T13:35:29.481Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/sched: Avoid data corruptions Wait for all dependencies of a job to complete before killing it to avoid data corruptions. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c32d0f0e164ffab2a56c7cf8e612584b4b740e2e - https://git.kernel.org/stable/c/0687411e2a8858262de2fc4a1d576016fd77292e - https://git.kernel.org/stable/c/a8e23e3c1ff9ec598ab1b3a941ace6045027781f - https://git.kernel.org/stable/c/
16fd77292e - https://git.kernel.org/stable/c/a8e23e3c1ff9ec598ab1b3a941ace6045027781f - https://git.kernel.org/stable/c/50d7e03ad487cc45fc85164a299b945a41756ac0 - https://git.kernel.org/stable/c/0b10ab80695d61422337ede6ff496552d8ace99d
CVE ID: CVE-2021-47355 State: PUBLISHED Published: 2024-05-21T14:35:58.434Z Last Updated: 2025-05-04T07:09:14.989Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: atm: nicstar: Fix possible use-after-free in nicstar_cleanup() This module's remove path calls del_timer(). However, that function does not wait until the timer handler finishes. This means that the timer handler may still be running after the driver's remove function has finished, which would result in a use-after-free. Fix by calling del_timer_sync(), which makes sure the timer handler has finished, and unable to re-schedule itself. Additional Analyst Notes: - CISA A
), which makes sure the timer handler has finished, and unable to re-schedule itself. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/99779c9d9ffc7775da6f7fd8a7c93ac61657bed5 - https://git.kernel.org/stable/c/4e2a0848ea2cab0716d46f85a8ccd5fa9a493e51 - https://git.kernel.org/stable/c/c471569632654e57c83512e0fc1ba0dbb4544ad6 - https://git.kernel.org/stable/c/a7a7b2848312cc4c3a42b6e42a8ab2e441857aba - https://git.kernel.org/stable/c/bdf5334250c69fabf555b7322c75249ea7d5f148 - https://git.kernel.org/stable/c/a7f7c42e31157d1f0871d6a8e1a0b73a6b4ea785 - https://git.kernel.org/stable/c/2f958b6f6ba0854b39be748d21dfe71e0fe6580f -
/c/a7f7c42e31157d1f0871d6a8e1a0b73a6b4ea785 - https://git.kernel.org/stable/c/2f958b6f6ba0854b39be748d21dfe71e0fe6580f - https://git.kernel.org/stable/c/5b991df8881088448cb223e769e37cab8dd40706 - https://git.kernel.org/stable/c/34e7434ba4e97f4b85c1423a59b2922ba7dff2ea
CVE ID: CVE-2021-47356 State: PUBLISHED Published: 2024-05-21T14:35:59.097Z Last Updated: 2025-05-04T07:09:16.037Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mISDN: fix possible use-after-free in HFC_cleanup() This module's remove path calls del_timer(). However, that function does not wait until the timer handler finishes. This means that the timer handler may still be running after the driver's remove function has finished, which would result in a use-after-free. Fix by calling del_timer_sync(), which makes sure the timer handler has finished, and unable to re-schedule itself. Additional Analyst Notes: - CISA ADP Vulnrich
kes sure the timer handler has finished, and unable to re-schedule itself. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/49331c07ef0f8fdfa42b30ba6a83a657b29d7fbe - https://git.kernel.org/stable/c/54ff3202928952a100c477248e65ac6db01258a7 - https://git.kernel.org/stable/c/7867ddc5f3de7f289aee63233afc0df4b62834c5 - https://git.kernel.org/stable/c/5f2818185da0fe82a932f0856633038b66faf124 - https://git.kernel.org/stable/c/3ecd228c636ee17c14662729737fa07242a93cb0 - https://git.kernel.org/stable/c/b7ee9ae1e0cf55a037c4a99af2acc5d78cb7802d - https://git.kernel.org/stable/c/61370ff07e0acc657559a8fac02551dfeb9d3020 - https://gi
e0cf55a037c4a99af2acc5d78cb7802d - https://git.kernel.org/stable/c/61370ff07e0acc657559a8fac02551dfeb9d3020 - https://git.kernel.org/stable/c/ed7c3739d0a07e2ec3ccbffe7e93cea01c438cda - https://git.kernel.org/stable/c/009fc857c5f6fda81f2f7dd851b2d54193a8e733
CVE ID: CVE-2021-47357 State: PUBLISHED Published: 2024-05-21T14:35:59.761Z Last Updated: 2025-05-04T07:09:17.214Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: atm: iphase: fix possible use-after-free in ia_module_exit() This module's remove path calls del_timer(). However, that function does not wait until the timer handler finishes. This means that the timer handler may still be running after the driver's remove function has finished, which would result in a use-after-free. Fix by calling del_timer_sync(), which makes sure the timer handler has finished, and unable to re-schedule itself. Additional Analyst Notes: - CVE Prog
which makes sure the timer handler has finished, and unable to re-schedule itself. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/9e161687855175334ca93c6c3ccb221731194479 - https://git.kernel.org/stable/c/a832ee2f2145f57443b2d565f8cb5490e8339f42 - https://git.kernel.org/stable/c/bcdd2be48edd8c6867fb44112cb8d18086beae29 - https://git.kernel.org/stable/c/89ce0b0747f319eb70f85bc820dcc43cebbd5417 - https://git.kernel.org/stable/c/c9172498d4d62c9b64e5fb37c1ee0343e65fe51b - https://git.kernel.org/stable/c/e759ff76ebbbfcdcf83b6634c54dc47828573d8b - https://git.kernel.org/stable/c/b58d246a058ae88484758cd4ab27b3180fd5ecf8 - h
/e759ff76ebbbfcdcf83b6634c54dc47828573d8b - https://git.kernel.org/stable/c/b58d246a058ae88484758cd4ab27b3180fd5ecf8 - https://git.kernel.org/stable/c/d1fb12412874c94ad037e11d0ecdd1140a439297 - https://git.kernel.org/stable/c/1c72e6ab66b9598cac741ed397438a52065a8f1f
CVE ID: CVE-2021-47358 State: PUBLISHED Published: 2024-05-21T14:44:50.221Z Last Updated: 2025-05-04T07:09:18.414Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: staging: greybus: uart: fix tty use after free User space can hold a tty open indefinitely and tty drivers must not release the underlying structures until the last user is gone. Switch to using the tty-port reference counter to manage the life time of the greybus tty state to avoid use after free after a disconnect. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/92b67aaafb7c449db9f0c3dcabc0ff96
DP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/92b67aaafb7c449db9f0c3dcabc0ff967cb3a42d - https://git.kernel.org/stable/c/64062fcaca8872f063ec9da011e7bf30470be33f - https://git.kernel.org/stable/c/a5cfd51f6348e8fd7531461366946039c29c7e69 - https://git.kernel.org/stable/c/4dc56951a8d9d61d364d346c61a5f1d70b4f5e14 - https://git.kernel.org/stable/c/b9e697e60ce9890e9258a73eb061288e7d68e5e6 - https://git.kernel.org/stable/c/9872ff6fdce8b229f01993b611b5d1719cb70ff1 - https://git.kernel.org/stable/c/92dc0b1f46e12cfabd28d709bb34f7a39431b44f
CVE ID: CVE-2021-47359 State: PUBLISHED Published: 2024-05-21T15:03:28.584Z Last Updated: 2025-05-04T07:09:19.487Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cifs: Fix soft lockup during fsstress Below traces are observed during fsstress and system got hung. [ 130.698396] watchdog: BUG: soft lockup - CPU#6 stuck for 26s! Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/9f6c7aff21f81ae8856da1f63847d1362d523409 - https://git.kernel.org/stable/c/71826b068884050d5fdd37fda857ba1539c513d3
CVE ID: CVE-2021-47360 State: PUBLISHED Published: 2024-05-21T15:03:29.234Z Last Updated: 2025-05-04T12:41:23.174Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: binder: make sure fd closes complete During BC_FREE_BUFFER processing, the BINDER_TYPE_FDA object cleanup may close 1 or more fds. The close operations are completed using the task work mechanism -- which means the thread needs to return to userspace or the file object may never be dereferenced -- which can lead to hung processes. Force the binder thread back to userspace if an fd is closed during BC_FREE_BUFFER handling. Additional Analyst Notes: - CISA ADP Vulnrichme
ead back to userspace if an fd is closed during BC_FREE_BUFFER handling. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/aa2c274c279ff365a06a4cba263f04965895166e - https://git.kernel.org/stable/c/d5b0473707fa53b03a5db0256ce62b2874bddbc7 - https://git.kernel.org/stable/c/b95483d8d94b41fa31a84c1d86710b7907a37621 - https://git.kernel.org/stable/c/5fdb55c1ac9585eb23bb2541d5819224429e103d
CVE ID: CVE-2021-47361 State: PUBLISHED Published: 2024-05-21T15:03:29.882Z Last Updated: 2025-05-04T07:09:21.641Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mcb: fix error handling in mcb_alloc_bus() There are two bugs: 1) If ida_simple_get() fails then this code calls put_device(carrier) but we haven't yet called get_device(carrier) and probably that leads to a use after free. 2) After device_initialize() then we need to use put_device() to release the bus. This will free the internal resources tied to the device and call mcb_free_bus() which will free the rest. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Pro
he device and call mcb_free_bus() which will free the rest. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8a558261fa57a6deefb0925ab1829f698b194aea - https://git.kernel.org/stable/c/115b07d9f47e3996430b8f2007edd9768e1f807f - https://git.kernel.org/stable/c/66f74ba9be9daf9c47fface6af3677f602774f6b - https://git.kernel.org/stable/c/7751f609eadf36b1f53712bae430019c53a16eb0 - https://git.kernel.org/stable/c/91e4ad05bf18322b5921d1a6c9b603f6eb1694f0 - https://git.kernel.org/stable/c/9fc198f415dee070a1de957bb5bf5921d8df3499 - https://git.kernel.org/stable/c/25a1433216489de4abc889910f744e952cb6dbae
CVE ID: CVE-2021-47362 State: PUBLISHED Published: 2024-05-21T15:03:30.532Z Last Updated: 2025-05-04T07:09:22.747Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: Update intermediate power state for SI Update the current state as boot state during dpm initialization. During the subsequent initialization, set_power_state gets called to transition to the final power state. set_power_state refers to values from the current state and without current state populated, it could result in NULL pointer dereference. For ex: on platforms where PCI speed change is supported through ACPI ATCS method, the link speed of current sta
erence. For ex: on platforms where PCI speed change is supported through ACPI ATCS method, the link speed of current state needs to be queried before deciding on changing to final power state's link speed. The logic to query ATCS-support was broken on certain platforms. The issue became visible when broken ATCS-support logic got fixed with commit f9b7f3703ff9 ("drm/amdgpu/acpi: make ATPX/ATCS structures global (v2)"). Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1698 Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/68d4fbe6220cd1f3d07cab0a4901e62f8c12cc68 - https://git.kernel.org/stable/c/06a18e64256f7aecb5a27df