Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
kvm_start_guest() on the other hand is written more like a normal C function, it creates a frame on entry, and also stores CR/LR into its callers frame (per the ABI). The problem is that there is no caller frame on the emergency stack. The emergency stack for a given CPU is allocated with: paca_ptrs[i]->emergency_sp = alloc_stack(limit, i) + THREAD_SIZE; So emergency_sp actually points to the first address above the emergency stack allocation for a given CPU, we must not store above it without first decrementing it to create a frame. This is different to the regular kernel stack, paca->kstack, which is initialised to point at an initial frame that is ready to use. idle_kvm_start_guest() stor
stack, paca->kstack, which is initialised to point at an initial frame that is ready to use. idle_kvm_start_guest() stores the backchain, CR and LR all of which write outside the allocation for the emergency stack. It then creates a stack frame and saves the non-volatile registers. Unfortunately the frame it creates is not large enough to fit the non-volatiles, and so the saving of the non-volatile registers also writes outside the emergency stack allocation. The end result is that we corrupt whatever is at 0-24 bytes, and 112-248 bytes above the emergency stack allocation. In practice this has gone unnoticed because the memory immediately above the emergency stack happens to be used for oth
In practice this has gone unnoticed because the memory immediately above the emergency stack happens to be used for other stack allocations, either another CPUs mc_emergency_sp or an IRQ stack. See the order of calls to irqstack_early_init() and emergency_stack_init(). The low addresses of another stack are the top of that stack, and so are only used if that stack is under extreme pressue, which essentially never happens in practice - and if it did there's a high likelyhood we'd crash due to that stack overflowing. Still, we shouldn't be corrupting someone else's stack, and it is purely luck that we aren't corrupting something else. To fix it we save CR/LR into the caller's frame using the
d it is purely luck that we aren't corrupting something else. To fix it we save CR/LR into the caller's frame using the existing r1 on entry, we then create a SWITCH_FRAME_SIZE frame (which has space for pt_regs) on the emergency stack with the backchain pointing to the existing stack, and then finally we switch to the new frame on the emergency stack. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/80bbb0bc3a0288442f7fe6fc514f4ee1cb06ccb7 - https://git.kernel.org/stable/c/fbd724c49bead048ae9fc1a5b7bff2fb3e54f855 - https://git.kernel.org/stable/c/6d077c37c4643394b1bae9682da48164fc147ea8 - https://git.kernel.org/stable/
f2fb3e54f855 - https://git.kernel.org/stable/c/6d077c37c4643394b1bae9682da48164fc147ea8 - https://git.kernel.org/stable/c/9b4416c5095c20e110c82ae602c254099b83b72f
CVE ID: CVE-2021-47466 State: PUBLISHED Published: 2024-05-22T06:23:25.674Z Last Updated: 2025-05-04T07:11:35.715Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mm, slub: fix potential memoryleak in kmem_cache_open() In error path, the random_seq of slub cache might be leaked. Fix this by using __kmem_cache_release() to release all the relevant resources. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/4f5d1c29cfab5cb0ab885059818751bdef32e2bb - https://git.kernel.org/stable/c/568f906340b43120abd6fcc67c37396482f85930 - https://git.kernel.org/stable/c/42b8
32e2bb - https://git.kernel.org/stable/c/568f906340b43120abd6fcc67c37396482f85930 - https://git.kernel.org/stable/c/42b81946e3ac9ea0372ba16e05160dc11e02694f - https://git.kernel.org/stable/c/9037c57681d25e4dcc442d940d6dbe24dd31f461
CVE ID: CVE-2021-47467 State: PUBLISHED Published: 2024-05-22T06:23:26.324Z Last Updated: 2025-05-04T07:11:37.008Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: kunit: fix reference count leak in kfree_at_end The reference counting issue happens in the normal path of kfree_at_end(). When kunit_alloc_and_get_resource() is invoked, the function forgets to handle the returned resource object, whose refcount increased inside, causing a refcount leak. Fix this issue by calling kunit_alloc_resource() instead of kunit_alloc_and_get_resource(). Fixed the following when applying: Shuah Khan <skhan@linuxfoundation.org> CHECK: Alignment
it_alloc_and_get_resource(). Fixed the following when applying: Shuah Khan <skhan@linuxfoundation.org> CHECK: Alignment should match open parenthesis + kunit_alloc_resource(test, NULL, kfree_res_free, GFP_KERNEL, (void *)to_free); Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/bbdd158b40b66a9403391a517f24ef6613573446 - https://git.kernel.org/stable/c/f62314b1ced25c58b86e044fc951cd6a1ea234cf
CVE ID: CVE-2021-47468 State: PUBLISHED Published: 2024-05-22T06:23:26.982Z Last Updated: 2025-05-04T07:11:38.227Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: isdn: mISDN: Fix sleeping function called from invalid context The driver can call card->isac.release() function from an atomic context. Fix this by calling this function after releasing the lock. The following log reveals it: [ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018 [ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe [ 44.169574 ] INFO: lockdep is turned off. [ 44.169899 ] irq eve
_disabled(): 1, non_block: 0, pid: 5475, name: modprobe [ 44.169574 ] INFO: lockdep is turned off. [ 44.169899 ] irq event stamp: 0 [ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [ 44.170627 ] hardirqs last disabled at (0): [<ffffffff814209ed>] copy_process+0x132d/0x3e00 [ 44.171240 ] softirqs last enabled at (0): [<ffffffff81420a1a>] copy_process+0x135a/0x3e00 [ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0 [ 44.172318 ] Preemption disabled at: [ 44.172320 ] [<ffffffffa009b0a9>] nj_release+0x69/0x500 [netjet] [ 44.174441 ] Call Trace: [ 44.174630 ] dump_stack_lvl+0xa8/0xd1 [ 44.174912 ] dump_stack+0x15/0x17 [ 44.175166 ] ___might_sleep+0x3a2/0x510
race: [ 44.174630 ] dump_stack_lvl+0xa8/0xd1 [ 44.174912 ] dump_stack+0x15/0x17 [ 44.175166 ] ___might_sleep+0x3a2/0x510 [ 44.175459 ] ? nj_release+0x69/0x500 [netjet] [ 44.175791 ] __might_sleep+0x82/0xe0 [ 44.176063 ] ? start_flush_work+0x20/0x7b0 [ 44.176375 ] start_flush_work+0x33/0x7b0 [ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170 [ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0 [ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0 [ 44.177711 ] __flush_work+0x11a/0x1a0 [ 44.177991 ] ? flush_work+0x20/0x20 [ 44.178257 ] ? lock_release+0x13c/0x8f0 [ 44.178550 ] ? __kasan_check_write+0x14/0x20 [ 44.178872 ] ? do_raw_spin_lock+0x148/0x360 [ 44.179187 ] ? read_lock_is_recursive+0x20/0x20 [ 4
_check_write+0x14/0x20 [ 44.178872 ] ? do_raw_spin_lock+0x148/0x360 [ 44.179187 ] ? read_lock_is_recursive+0x20/0x20 [ 44.179530 ] ? __kasan_check_read+0x11/0x20 [ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900 [ 44.180168 ] ? ____kasan_slab_free+0x116/0x140 [ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60 [ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0 [ 44.181189 ] ? kfree+0x13e/0x290 [ 44.181438 ] flush_work+0x17/0x20 [ 44.181695 ] mISDN_freedchannel+0xe8/0x100 [ 44.182006 ] isac_release+0x210/0x260 [mISDNipac] [ 44.182366 ] nj_release+0xf6/0x500 [netjet] [ 44.182685 ] nj_remove+0x48/0x70 [netjet] [ 44.182989 ] pci_device_remove+0xa9/0x250 Additional Analyst Notes: - CVE Program Container:
remove+0x48/0x70 [netjet] [ 44.182989 ] pci_device_remove+0xa9/0x250 Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/6f95c97e0f9d6eb39c3f2cb45e8fa4268d1b372b - https://git.kernel.org/stable/c/ef269a8808cb1759245a98a7fe16fceaebad894c - https://git.kernel.org/stable/c/37e4f57b22cc5ebb3f80cf0f74fdeb487f082367 - https://git.kernel.org/stable/c/a5b34409d3fc52114c828be4adbc30744fa3258b - https://git.kernel.org/stable/c/4054b869dc263228d30a4755800b78f0f2ba0c89 - https://git.kernel.org/stable/c/9f591cbdbed3d7822b2bdba89b34a6d7b434317d - https://git.kernel.org/stable/c/f5966ba53013149bcf94e1536644a958dd00a026 - https://git.kern
822b2bdba89b34a6d7b434317d - https://git.kernel.org/stable/c/f5966ba53013149bcf94e1536644a958dd00a026 - https://git.kernel.org/stable/c/6510e80a0b81b5d814e3aea6297ba42f5e76f73c
CVE ID: CVE-2021-47469 State: REJECTED Published: 2024-05-22T06:23:27.629Z Last Updated: 2025-03-03T08:16:40.401Z Description: No description available.
CVE ID: CVE-2021-47470 State: PUBLISHED Published: 2024-05-22T06:23:28.263Z Last Updated: 2025-05-04T07:11:39.369Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mm, slub: fix potential use-after-free in slab_debugfs_fops When sysfs_slab_add failed, we shouldn't call debugfs_slab_add() for s because s will be freed soon. And slab_debugfs_fops will use s later leading to a use-after-free. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/159d8cfbd0428d487c53be4722f33cdab0d25d83 - https://git.kernel.org/stable/c/67823a544414def2a36c212abadb55b23bcda00c
CVE ID: CVE-2021-47471 State: PUBLISHED Published: 2024-05-22T06:23:28.903Z Last Updated: 2025-05-04T07:11:40.478Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm: mxsfb: Fix NULL pointer dereference crash on unload The mxsfb->crtc.funcs may already be NULL when unloading the driver, in which case calling mxsfb_irq_disable() via drm_irq_uninstall() from mxsfb_unload() leads to NULL pointer dereference. Since all we care about is masking the IRQ and mxsfb->base is still valid, just use that to clear and mask the IRQ. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.o
the IRQ. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/f40c2281d2c0674d32ba732fee45222d76495472 - https://git.kernel.org/stable/c/b0e6db0656ddfd8bb57303c2ef61ee1c1cc694a8 - https://git.kernel.org/stable/c/3cfc183052c3dbf8eae57b6c1685dab00ed3db4a
CVE ID: CVE-2021-47472 State: REJECTED Published: 2024-05-22T06:23:29.555Z Last Updated: 2024-06-17T16:15:59.888Z Description: No description available.
CVE ID: CVE-2021-47473 State: PUBLISHED Published: 2024-05-22T06:23:30.204Z Last Updated: 2025-05-04T07:11:41.717Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix a memory leak in an error path of qla2x00_process_els() Commit 8c0eb596baa5 ("[SCSI] qla2xxx: Fix a memory leak in an error path of qla2x00_process_els()"), intended to change: bsg_job->request->msgcode == FC_BSG_HST_ELS_NOLOGIN bsg_job->request->msgcode != FC_BSG_RPT_ELS but changed it to: bsg_job->request->msgcode == FC_BSG_RPT_ELS instead. Change the == to a != to avoid leaking the fcport structure or freeing unallocated memory. Additional Analyst
S instead. Change the == to a != to avoid leaking the fcport structure or freeing unallocated memory. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/96f0aebf29be25254fa585af43924e34aa21fd9a - https://git.kernel.org/stable/c/a7fbb56e6c941d9f59437b96412a348e66388d3e - https://git.kernel.org/stable/c/7fb223d0ad801f633c78cbe42b1d1b55f5d163ad
CVE ID: CVE-2021-47474 State: PUBLISHED Published: 2024-05-22T08:19:28.759Z Last Updated: 2025-05-04T07:11:42.847Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: comedi: vmk80xx: fix bulk-buffer overflow The driver is using endpoint-sized buffers but must not assume that the tx and rx buffers are of equal size or a malicious device could overflow the slab-allocated receive buffer when doing bulk transfers. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/e0e6a63fd97ad95fe05dfd77268a1952551e11a7 - https://git.kernel.org/stable/c/7cfb35db607760698d299fd1cf74
nel.org/stable/c/e0e6a63fd97ad95fe05dfd77268a1952551e11a7 - https://git.kernel.org/stable/c/7cfb35db607760698d299fd1cf7402dfa8f09973 - https://git.kernel.org/stable/c/0866dcaa828c21bc2f94dac00e086078f11b5772 - https://git.kernel.org/stable/c/063f576c43d589a4c153554b681d32b3f8317c7b - https://git.kernel.org/stable/c/1ae4715121a57bc6fa29fd992127b01907f2f993 - https://git.kernel.org/stable/c/b7fd7f3387f070215e6be341e68eb5c087eeecc0 - https://git.kernel.org/stable/c/7b0e356189327287d0eb98ec081bd6dd97068cd3 - https://git.kernel.org/stable/c/47b4636ebdbeba2044b3db937c4d2b6a4fe3d0f2 - https://git.kernel.org/stable/c/78cdfd62bd54af615fba9e3ca1ba35de39d3871d
CVE ID: CVE-2021-47475 State: PUBLISHED Published: 2024-05-22T08:19:29.423Z Last Updated: 2025-05-04T07:11:43.980Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: comedi: vmk80xx: fix transfer-buffer overflows The driver uses endpoint-sized USB transfer buffers but up until recently had no sanity checks on the sizes. Commit e1f13c879a7c ("staging: comedi: check validity of wMaxPacketSize of usb endpoints found") inadvertently fixed NULL-pointer dereferences when accessing the transfer buffers in case a malicious device has a zero wMaxPacketSize. Make sure to allocate buffers large enough to handle also the other accesses that ar
s device has a zero wMaxPacketSize. Make sure to allocate buffers large enough to handle also the other accesses that are done without a size check (e.g. byte 18 in vmk80xx_cnt_insn_read() for the VMK8061_MODEL) to avoid writing beyond the buffers, for example, when doing descriptor fuzzing. The original driver was for a low-speed device with 8-byte buffers. Support was later added for a device that uses bulk transfers and is presumably a full-speed device with a maximum 64-byte wMaxPacketSize. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/5229159f1d052821007aff1a1beb7873eacf1a9f - https://git.kernel.org/stable/c/ec8
rences: - https://git.kernel.org/stable/c/5229159f1d052821007aff1a1beb7873eacf1a9f - https://git.kernel.org/stable/c/ec85bcff4ed09260243d8f39faba99e1041718ba - https://git.kernel.org/stable/c/40d2a7e278e2e7c0a5fd7e997e7eb63945bf93f7 - https://git.kernel.org/stable/c/7a2021b896de1ad559d33b5c5cdd20b982242088 - https://git.kernel.org/stable/c/199acd8c110e3ae62833c24f632b0bb1c9f012a9 - https://git.kernel.org/stable/c/33d7a470730dfe7c9bfc8da84575cf2cedd60d00 - https://git.kernel.org/stable/c/278484ae93297b1bb1ce755f9d3b6d95a48c7d47 - https://git.kernel.org/stable/c/06ac746d57e6d32b062e220415c607b7e2e0fa50 - https://git.kernel.org/stable/c/a23461c47482fc232ffc9b819539d1f837adf2b1
CVE ID: CVE-2021-47476 State: PUBLISHED Published: 2024-05-22T08:19:30.201Z Last Updated: 2025-05-04T07:11:45.313Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: comedi: ni_usb6501: fix NULL-deref in command paths The driver uses endpoint-sized USB transfer buffers but had no sanity checks on the sizes. This can lead to zero-size-pointer dereferences or overflowed transfer buffers in ni6501_port_command() and ni6501_counter_command() if a (malicious) device has smaller max-packet sizes than expected (or when doing descriptor fuzz testing). Add the missing sanity checks to probe(). Additional Analyst Notes: - CISA ADP Vulnrichme
oing descriptor fuzz testing). Add the missing sanity checks to probe(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/58478143771b20ab219937b1c30a706590a59224 - https://git.kernel.org/stable/c/aa39738423503825625853b643b9e99d11c23816 - https://git.kernel.org/stable/c/df7b1238f3b599a0b9284249772cdfd1ea83a632 - https://git.kernel.org/stable/c/bc51111bf6e8e7b6cc94b133e4c291273a16acd1 - https://git.kernel.org/stable/c/b0156b7c9649d8f55a2ce3d3258509f1b2a181c3 - https://git.kernel.org/stable/c/ef143dc0c3defe56730ecd3a9de7b3e1d7e557c1 - https://git.kernel.org/stable/c/4a9d43cb5d5f39fa39fc1da438517004cc95f7ea - https://git.
defe56730ecd3a9de7b3e1d7e557c1 - https://git.kernel.org/stable/c/4a9d43cb5d5f39fa39fc1da438517004cc95f7ea - https://git.kernel.org/stable/c/d6a727a681a39ae4f73081a9bedb45d14f95bdd1 - https://git.kernel.org/stable/c/907767da8f3a925b060c740e0b5c92ea7dbec440
CVE ID: CVE-2021-47477 State: PUBLISHED Published: 2024-05-22T08:19:30.860Z Last Updated: 2025-05-04T07:11:51.469Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: comedi: dt9812: fix DMA buffers on stack USB transfer buffers are typically mapped for DMA and must not be allocated on the stack or transfers will fail. Allocate proper transfer buffers in the various command helpers and return an error on short transfers instead of acting on random stack data. Note that this also fixes a stack info leak on systems where DMA is not used as 32 bytes are always sent to the device regardless of how short the command is. Additional Analys
here DMA is not used as 32 bytes are always sent to the device regardless of how short the command is. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/a6af69768d5cb4b2528946d53be5fa19ade37723 - https://git.kernel.org/stable/c/365a346cda82f51d835c49136a00a9df8a78c7f2 - https://git.kernel.org/stable/c/8a52bc480992c7c9da3ebfea456af731f50a4b97 - https://git.kernel.org/stable/c/39ea61037ae78f14fa121228dd962ea3280eacf3 - https://git.kernel.org/stable/c/3efb7af8ac437085b6c776e5b54830b149d86efe - https://git.kernel.org/stable/c/786f5b03450454557ff858a8bead5d7c0cbf78d6 - https://git.kernel.org/stable/c/3ac273d154d634e2034508a14
kernel.org/stable/c/786f5b03450454557ff858a8bead5d7c0cbf78d6 - https://git.kernel.org/stable/c/3ac273d154d634e2034508a14db82a95d7ad12ed - https://git.kernel.org/stable/c/20cebb8b620dc987e55ddc46801de986e081757e - https://git.kernel.org/stable/c/536de747bc48262225889a533db6650731ab25d3
CVE ID: CVE-2021-47478 State: PUBLISHED Published: 2024-05-22T08:19:31.521Z Last Updated: 2025-05-04T07:11:52.549Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: isofs: Fix out of bound access for corrupted isofs image When isofs image is suitably corrupted isofs_read_inode() can read data beyond the end of buffer. Sanity-check the directory entry length before using it. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/156ce5bb6cc43a80a743810199defb1dc3f55b7f - https://git.kernel.org/stable/c/9ec33a9b8790c212cc926a88c5e2105f97f3f57e - https://git.kernel.or
3810199defb1dc3f55b7f - https://git.kernel.org/stable/c/9ec33a9b8790c212cc926a88c5e2105f97f3f57e - https://git.kernel.org/stable/c/afbd40f425227e661d991757e11cc4db024e761f - https://git.kernel.org/stable/c/b0ddff8d68f2e43857a84dce54c3deab181c8ae1 - https://git.kernel.org/stable/c/6e80e9314f8bb52d9eabe1907698718ff01120f5 - https://git.kernel.org/stable/c/86d4aedcbc69c0f84551fb70f953c24e396de2d7 - https://git.kernel.org/stable/c/b2fa1f52d22c5455217b294629346ad23a744945 - https://git.kernel.org/stable/c/e7fb722586a2936b37bdff096c095c30ca06404d - https://git.kernel.org/stable/c/e96a1866b40570b5950cda8602c2819189c62a48
CVE ID: CVE-2021-47479 State: PUBLISHED Published: 2024-05-22T08:19:32.174Z Last Updated: 2025-05-04T12:41:33.897Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: staging: rtl8712: fix use-after-free in rtl8712_dl_fw Syzbot reported use-after-free in rtl8712_dl_fw(). The problem was in race condition between r871xu_dev_remove() ->ndo_open() callback. It's easy to see from crash log, that driver accesses released firmware in ->ndo_open() callback. It may happen, since driver was releasing firmware _before_ unregistering netdev. Fix it by moving unregister_netdev() before cleaning up resources. Call Trace: ... rtl871x_open_fw driv
istering netdev. Fix it by moving unregister_netdev() before cleaning up resources. Call Trace: ... rtl871x_open_fw drivers/staging/rtl8712/hal_init.c:83 [inline] rtl8712_dl_fw+0xd95/0xe10 drivers/staging/rtl8712/hal_init.c:170 rtl8712_hal_init drivers/staging/rtl8712/hal_init.c:330 [inline] rtl871x_hal_init+0xae/0x180 drivers/staging/rtl8712/hal_init.c:394 netdev_open+0xe6/0x6c0 drivers/staging/rtl8712/os_intfs.c:380 __dev_open+0x2bc/0x4d0 net/core/dev.c:1484 Freed by task 1306: ... release_firmware+0x1b/0x30 drivers/base/firmware_loader/main.c:1053 r871xu_dev_remove+0xcc/0x2c0 drivers/staging/rtl8712/usb_intf.c:599 usb_unbind_interface+0x1d8/0x8d0 drivers/usb/core/driver.c:458 Additional A
0x2c0 drivers/staging/rtl8712/usb_intf.c:599 usb_unbind_interface+0x1d8/0x8d0 drivers/usb/core/driver.c:458 Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c430094541a80575259a94ff879063ef01473506 - https://git.kernel.org/stable/c/befd23bd3b17f1a3f9c943a8580b47444c7c63ed - https://git.kernel.org/stable/c/a65c9afe9f2f55b7a7fb4a25ab654cd4139683a4 - https://git.kernel.org/stable/c/c052cc1a069c3e575619cf64ec427eb41176ca70
CVE ID: CVE-2021-47480 State: PUBLISHED Published: 2024-05-22T08:19:32.839Z Last Updated: 2025-05-04T07:11:59.967Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: core: Put LLD module refcnt after SCSI device is released SCSI host release is triggered when SCSI device is freed. We have to make sure that the low-level device driver module won't be unloaded before SCSI host instance is released because shost->hostt is required in the release handler. Make sure to put LLD module refcnt after SCSI device is released. Fixes a kernel panic of 'BUG: unable to handle page fault for address' reported by Changhui and Yi. Additional
eleased. Fixes a kernel panic of 'BUG: unable to handle page fault for address' reported by Changhui and Yi. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/1105573d964f7b78734348466b01f5f6ba8a1813 - https://git.kernel.org/stable/c/8e4814a461787e15a31d322d9efbe0d4f6822428 - https://git.kernel.org/stable/c/61a0faa89f21861d1f8d059123b5c285a5d9ffee - https://git.kernel.org/stable/c/c2df161f69fb1c67f63adbd193368b47f511edc0 - https://git.kernel.org/stable/c/1ce287eff9f23181d5644db787f472463a61f68b - https://git.kernel.org/stable/c/7b57c38d12aed1b5d92f74748bed25e0d041729f - https://git.kernel.org/stable/c/f30822c0b4c35ec8618
//git.kernel.org/stable/c/7b57c38d12aed1b5d92f74748bed25e0d041729f - https://git.kernel.org/stable/c/f30822c0b4c35ec86187ab055263943dc71a6836 - https://git.kernel.org/stable/c/f2b85040acec9a928b4eb1b57a989324e8e38d3f
CVE ID: CVE-2021-47481 State: PUBLISHED Published: 2024-05-22T08:19:33.512Z Last Updated: 2025-05-04T12:41:34.908Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Initialize the ODP xarray when creating an ODP MR Normally the zero fill would hide the missing initialization, but an errant set to desc_size in reg_create() causes a crash: BUG: unable to handle page fault for address: 0000000800000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP PTI CPU: 5 PID: 890 Comm: ib_write_bw Not tainted 5.15.0-rc4+ #47 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:mlx