Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2023-53446 State: PUBLISHED Published: 2025-09-18T16:04:21.939Z Last Updated: 2025-09-18T16:04:21.939Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free Struct pcie_link_state->downstream is a pointer to the pci_dev of function 0. Previously we retained that pointer when removing function 0, and subsequent ASPM policy changes dereferenced it, resulting in a use-after-free warning from KASAN, e.g.: # echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove # echo powersave > /sys/module/pcie_aspm/parameters/policy BUG: KASAN: slab-use-after-free in pcie_con
00:03:00.0/remove # echo powersave > /sys/module/pcie_aspm/parameters/policy BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500 Call Trace: kasan_report+0xae/0xe0 pcie_config_aspm_link+0x42d/0x500 pcie_aspm_set_policy+0x8e/0x1a0 param_attr_store+0x162/0x2c0 module_attr_store+0x3e/0x80 PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM Control value in all functions of multi-function devices. Disable ASPM and free the pcie_link_state when any child function is removed so we can discard the dangling pcie_link_state->downstream pointer and maintain the same ASPM Control configuration for all functions. [bhelgaas: commit log and comment] References: - h
r and maintain the same ASPM Control configuration for all functions. [bhelgaas: commit log and comment] References: - https://git.kernel.org/stable/c/666e7f9d60cee23077ea3e6331f6f8a19f7ea03f - https://git.kernel.org/stable/c/7badf4d6f49a358a01ab072bbff88d3ee886c33b - https://git.kernel.org/stable/c/9856c0de49052174ab474113f4ba40c02aaee086 - https://git.kernel.org/stable/c/7aecdd47910c51707696e8b0e045b9f88bd4230f - https://git.kernel.org/stable/c/d51d2eeae4ce54d542909c4d9d07bf371a78592c - https://git.kernel.org/stable/c/4203722d51afe3d239e03f15cc73efdf023a7103 - https://git.kernel.org/stable/c/456d8aa37d0f56fc9e985e812496e861dcd6f2f2
CVE ID: CVE-2023-53447 State: PUBLISHED Published: 2025-09-18T16:04:22.649Z Last Updated: 2025-09-19T15:21:41.293Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: f2fs: don't reset unchangable mount option in f2fs_remount() syzbot reports a bug as below: general protection fault, probably for non-canonical address 0xdffffc0000000009: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:__lock_acquire+0x69/0x2000 kernel/locking/lockdep.c:4942 Call Trace: lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5691 __raw_write_lock include/linux/rwlock_api_smp.h:209 [inline] _raw_write_lock+0x2e/0x40 kernel/locking/spinlock.c:300 __drop_extent_tree+0x
nclude/linux/rwlock_api_smp.h:209 [inline] _raw_write_lock+0x2e/0x40 kernel/locking/spinlock.c:300 __drop_extent_tree+0x3ac/0x660 fs/f2fs/extent_cache.c:1100 f2fs_drop_extent_tree+0x17/0x30 fs/f2fs/extent_cache.c:1116 f2fs_insert_range+0x2d5/0x3c0 fs/f2fs/file.c:1664 f2fs_fallocate+0x4e4/0x6d0 fs/f2fs/file.c:1838 vfs_fallocate+0x54b/0x6b0 fs/open.c:324 ksys_fallocate fs/open.c:347 [inline] __do_sys_fallocate fs/open.c:355 [inline] __se_sys_fallocate fs/open.c:353 [inline] __x64_sys_fallocate+0xbd/0x100 fs/open.c:353 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd The root cause is race condition as
all_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd The root cause is race condition as below: - since it tries to remount rw filesystem, so that do_remount won't call sb_prepare_remount_readonly to block fallocate, there may be race condition in between remount and fallocate. - in f2fs_remount(), default_options() will reset mount option to default one, and then update it based on result of parse_options(), so there is a hole which race condition can happen. Thread A Thread B - f2fs_fill_super - parse_options - clear_opt(READ_EXTENT_CACHE) - f2fs_remount - default_options - set_opt(READ_EXTENT_CACHE) - f2fs_fallocate - f2fs_insert_range - f2fs_drop_extent_tr
- f2fs_remount - default_options - set_opt(READ_EXTENT_CACHE) - f2fs_fallocate - f2fs_insert_range - f2fs_drop_extent_tree - __drop_extent_tree - __may_extent_tree - test_opt(READ_EXTENT_CACHE) return true - write_lock(&et->lock) access NULL pointer - parse_options - clear_opt(READ_EXTENT_CACHE) References: - https://git.kernel.org/stable/c/115557cc226a927924f2d7d1980ccbf6e3b3bb36 - https://git.kernel.org/stable/c/458c15dfbce62c35fefd9ca637b20a051309c9f1
CVE ID: CVE-2023-53448 State: PUBLISHED Published: 2025-10-01T11:42:20.557Z Last Updated: 2025-10-01T11:42:20.557Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: fbdev: imxfb: Removed unneeded release_mem_region Remove unnecessary release_mem_region from the error path to prevent mem region from being released twice, which could avoid resource leak or other unexpected issues. References: - https://git.kernel.org/stable/c/6aa851f6276fa08cd59b044bc2b803c49edf58a2 - https://git.kernel.org/stable/c/38282a92c30422836d49e519bd109237f86a0888 - https://git.kernel.org/stable/c/45fcc058a75bf5d65cf4c32da44a252fbe873cd4
CVE ID: CVE-2023-53449 State: PUBLISHED Published: 2025-10-01T11:42:21.371Z Last Updated: 2025-10-01T11:42:21.371Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: s390/dasd: Fix potential memleak in dasd_eckd_init() `dasd_reserve_req` is allocated before `dasd_vol_info_req`, and it also needs to be freed before the error returns, just like the other cases in this function. References: - https://git.kernel.org/stable/c/ee986d80acdef710a886be404308188ea11000c8 - https://git.kernel.org/stable/c/a50e28d433acf22258f9f34831057387f04ef074 - https://git.kernel.org/stable/c/544a552be0869231799784279d52704c4d314d33 - https://git.kernel.or
9f34831057387f04ef074 - https://git.kernel.org/stable/c/544a552be0869231799784279d52704c4d314d33 - https://git.kernel.org/stable/c/ef3a7ffc0a6f833578bc8d1dcb79d0633c7e4ec3 - https://git.kernel.org/stable/c/aede5230d154b6b237985ec9df7ebbd1dce96810 - https://git.kernel.org/stable/c/460e9bed82e49db1b823dcb4e421783854d86c40
CVE ID: CVE-2023-53450 State: PUBLISHED Published: 2025-10-01T11:42:22.074Z Last Updated: 2025-10-01T11:42:22.074Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ext4: remove a BUG_ON in ext4_mb_release_group_pa() If a malicious fuzzer overwrites the ext4 superblock while it is mounted such that the s_first_data_block is set to a very large number, the calculation of the block group can underflow, and trigger a BUG_ON check. Change this to be an ext4_warning so that we don't crash the kernel. References: - https://git.kernel.org/stable/c/d5bf8f7fb3ee3d99d1303ceb54599ea0599a4a5b - https://git.kernel.org/stable/c/ef16d8a1798db1a1
ps://git.kernel.org/stable/c/d5bf8f7fb3ee3d99d1303ceb54599ea0599a4a5b - https://git.kernel.org/stable/c/ef16d8a1798db1a1604ac44ca1bd73ec6bebf483 - https://git.kernel.org/stable/c/185062a21976fbc38f2efd296951b02c4500cf65 - https://git.kernel.org/stable/c/b0fc279de4bf17e1710bb7e83906538ff8f11111 - https://git.kernel.org/stable/c/978e5e9111af18741449b81fefd531a622dd969a - https://git.kernel.org/stable/c/d87a4e4094c9879fc8acdff8ce59fdffa979c8e0 - https://git.kernel.org/stable/c/bf2a16eb4e6d06124bd8436d4546f61539a65f29 - https://git.kernel.org/stable/c/53c14e7cc2257191ba15425c15638fc4f8abb92b - https://git.kernel.org/stable/c/463808f237cf73e98a1a45ff7460c2406a150a0b
CVE ID: CVE-2023-53451 State: PUBLISHED Published: 2025-10-01T11:42:22.857Z Last Updated: 2025-10-01T11:42:22.857Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix potential NULL pointer dereference Klocwork tool reported 'cur_dsd' may be dereferenced. Add fix to validate pointer before dereferencing the pointer. References: - https://git.kernel.org/stable/c/02405f4023866ae91a611b5b85cb2e074ec2de5a - https://git.kernel.org/stable/c/ee4c9a93238b9ce3703942500cb1aeacf77090d2 - https://git.kernel.org/stable/c/4f90a8b0481615622bd0558aa8cf361bea872045 - https://git.kernel.org/stable/c/2bea9c1c983152c5411f5a2f1113cb79
org/stable/c/4f90a8b0481615622bd0558aa8cf361bea872045 - https://git.kernel.org/stable/c/2bea9c1c983152c5411f5a2f1113cb790ce1389d - https://git.kernel.org/stable/c/5a52a2e14fe866541bbc0033058e44bf0bf0c580 - https://git.kernel.org/stable/c/ce2cdbe530b0066bae1f98dbab590a232d507eaa - https://git.kernel.org/stable/c/af7affc0f6b82a5bde430fc4f0dcf70963442fbc - https://git.kernel.org/stable/c/464ea494a40c6e3e0e8f91dd325408aaf21515ba
CVE ID: CVE-2023-53452 State: PUBLISHED Published: 2025-10-01T11:42:23.831Z Last Updated: 2025-10-01T11:42:23.831Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: fix potential race condition between napi_init and napi_enable A race condition can happen if netdev is registered, but NAPI isn't initialized yet, and meanwhile user space starts the netdev that will enable NAPI. Then, it hits BUG_ON(): kernel BUG at net/core/dev.c:6423! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 417 Comm: iwd Not tainted 6.2.7-slab-dirty #3 eb0f5a8a9d91 Hardware name: LENOVO 21DL/LNVNB161216, BIOS JPCN20WW(V1.06) 09/20/2022
wd Not tainted 6.2.7-slab-dirty #3 eb0f5a8a9d91 Hardware name: LENOVO 21DL/LNVNB161216, BIOS JPCN20WW(V1.06) 09/20/2022 RIP: 0010:napi_enable+0x3f/0x50 Code: 48 89 c2 48 83 e2 f6 f6 81 89 08 00 00 02 74 0d 48 83 ... RSP: 0018:ffffada1414f3548 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffa01425802080 RCX: 0000000000000000 RDX: 00000000000002ff RSI: ffffada14e50c614 RDI: ffffa01425808dc0 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000100 R12: ffffa01425808f58 R13: 0000000000000000 R14: ffffa01423498940 R15: 0000000000000001 FS: 00007f5577c0a740(0000) GS:ffffa0169fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 00
000000001 FS: 00007f5577c0a740(0000) GS:ffffa0169fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f5577a19972 CR3: 0000000125a7a000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> rtw89_pci_ops_start+0x1c/0x70 [rtw89_pci 6cbc75429515c181cbc386478d5cfb32ffc5a0f8] rtw89_core_start+0xbe/0x160 [rtw89_core fe07ecb874820b6d778370d4acb6ef8a37847f22] rtw89_ops_start+0x26/0x40 [rtw89_core fe07ecb874820b6d778370d4acb6ef8a37847f22] drv_start+0x42/0x100 [mac80211 c07fa22af8c3cf3f7d7ab3884ca990784d72e2d2] ieee80211_do_open+0x311/0x7d0 [mac80211 c07fa22af8c3cf3f7d7ab3884ca990784d72e2d2] ieee80211_open+0x6a/0x90 [mac80211 c07fa22af8c3cf3f7d7ab3884ca990
d0 [mac80211 c07fa22af8c3cf3f7d7ab3884ca990784d72e2d2] ieee80211_open+0x6a/0x90 [mac80211 c07fa22af8c3cf3f7d7ab3884ca990784d72e2d2] __dev_open+0xe0/0x180 __dev_change_flags+0x1da/0x250 dev_change_flags+0x26/0x70 do_setlink+0x37c/0x12c0 ? ep_poll_callback+0x246/0x290 ? __nla_validate_parse+0x61/0xd00 ? __wake_up_common_lock+0x8f/0xd0 To fix this, follow Jonas' suggestion to switch the order of these functions and move register netdev to be the last step of PCI probe. Also, correct the error handling of rtw89_core_register_hw(). References: - https://git.kernel.org/stable/c/39712c8aeb79691bcec8bd6ff658cde1651e0803 - https://git.kernel.org/stable/c/aa48073c2f993e1b0c0bc66b03ae105cac0130bc - htt
9712c8aeb79691bcec8bd6ff658cde1651e0803 - https://git.kernel.org/stable/c/aa48073c2f993e1b0c0bc66b03ae105cac0130bc - https://git.kernel.org/stable/c/b1b90c7df08ef385f95827ee3aee87bddd1ef5c5 - https://git.kernel.org/stable/c/47515664ecfbde11425dff121f298ae4499425c9
CVE ID: CVE-2023-53453 State: PUBLISHED Published: 2025-10-01T11:42:24.649Z Last Updated: 2025-10-01T11:42:24.649Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/radeon: free iio for atombios when driver shutdown Fix below kmemleak when unload radeon driver: unreferenced object 0xffff9f8608ede200 (size 512): comm "systemd-udevd", pid 326, jiffies 4294682822 (age 716.338s) hex dump (first 32 bytes): 00 00 00 00 c4 aa ec aa 14 ab 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<0000000062fadebe>] kmem_cache_alloc_trace+0x2f1/0x500 [<00000000b6883cea>] atom_parse+
00 ................ backtrace: [<0000000062fadebe>] kmem_cache_alloc_trace+0x2f1/0x500 [<00000000b6883cea>] atom_parse+0x117/0x230 [radeon] [<00000000158c23fd>] radeon_atombios_init+0xab/0x170 [radeon] [<00000000683f672e>] si_init+0x57/0x750 [radeon] [<00000000566cc31f>] radeon_device_init+0x559/0x9c0 [radeon] [<0000000046efabb3>] radeon_driver_load_kms+0xc1/0x1a0 [radeon] [<00000000b5155064>] drm_dev_register+0xdd/0x1d0 [<0000000045fec835>] radeon_pci_probe+0xbd/0x100 [radeon] [<00000000e69ecca3>] pci_device_probe+0xe1/0x160 [<0000000019484b76>] really_probe.part.0+0xc1/0x2c0 [<000000003f2649da>] __driver_probe_device+0x96/0x130 [<00000000231c5bb1>] driver_probe_device+0x24/0xf0 [<00000000
x2c0 [<000000003f2649da>] __driver_probe_device+0x96/0x130 [<00000000231c5bb1>] driver_probe_device+0x24/0xf0 [<0000000000a42377>] __driver_attach+0x77/0x190 [<00000000d7574da6>] bus_for_each_dev+0x7f/0xd0 [<00000000633166d2>] driver_attach+0x1e/0x30 [<00000000313b05b8>] bus_add_driver+0x12c/0x1e0 iio was allocated in atom_index_iio() called by atom_parse(), but it doesn't got released when the dirver is shutdown. Fix this kmemleak by free it in radeon_atombios_fini(). References: - https://git.kernel.org/stable/c/cb109cedbba11c33473e6780c256d8442a9e4460 - https://git.kernel.org/stable/c/9cdb96b55651c92fc949cfd54124406c3c912b6b - https://git.kernel.org/stable/c/f9f55fc64928b5e30d78f861c5fc76
l.org/stable/c/9cdb96b55651c92fc949cfd54124406c3c912b6b - https://git.kernel.org/stable/c/f9f55fc64928b5e30d78f861c5fc76db9e769ebb - https://git.kernel.org/stable/c/ce9e9d3dcbb0d1551ffd1a7f16e7c051f3ba4140 - https://git.kernel.org/stable/c/cda2f7efbc2d857220dad32e315a54565b285c1c - https://git.kernel.org/stable/c/107b8b542bb9dab4cbdc3276c85fbdd7f6782313 - https://git.kernel.org/stable/c/e2791f2f4d1d804e45fa91b14295c326b64c65f1 - https://git.kernel.org/stable/c/4773fadedca918faec443daaca5e4ea1c0ced144
CVE ID: CVE-2023-53454 State: PUBLISHED Published: 2025-10-01T11:42:25.760Z Last Updated: 2025-10-01T11:42:25.760Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: HID: multitouch: Correct devm device reference for hidinput input_dev name Reference the HID device rather than the input device for the devm allocation of the input_dev name. Referencing the input_dev would lead to a use-after-free when the input_dev was unregistered and subsequently fires a uevent that depends on the name. At the point of firing the uevent, the name would be freed by devres management. Use devm_kasprintf to simplify the logic for allocating memory an
uevent, the name would be freed by devres management. Use devm_kasprintf to simplify the logic for allocating memory and formatting the input_dev name string. References: - https://git.kernel.org/stable/c/ac0d389402a6ff9ad92cea02c2d8c711483b91ab - https://git.kernel.org/stable/c/39c70c19456e50dcb3abfe53539220dff0490f1d - https://git.kernel.org/stable/c/df7ca43fe090e1a56c216c8ebc106ef5fd49afc6 - https://git.kernel.org/stable/c/15ec7cb55e7d88755aa01d44a7a1015a42bfce86 - https://git.kernel.org/stable/c/dde88ab4e45beb60b217026207aa9c14c88d71ab - https://git.kernel.org/stable/c/2763732ec1e68910719c75b6b896e11b6d3d622b - https://git.kernel.org/stable/c/1d7833db9fd118415dace2ca157bfa603dec9c8c - h
/2763732ec1e68910719c75b6b896e11b6d3d622b - https://git.kernel.org/stable/c/1d7833db9fd118415dace2ca157bfa603dec9c8c - https://git.kernel.org/stable/c/b70ac7849248ec8128fa12f86e3655ba38838f29 - https://git.kernel.org/stable/c/4794394635293a3e74591351fff469cea7ad15a2
CVE ID: CVE-2023-53455 State: PUBLISHED Published: 2025-10-01T11:42:26.791Z Last Updated: 2025-10-01T11:42:26.791Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/vc4: drop all currently held locks if deadlock happens If vc4_hdmi_reset_link() returns -EDEADLK, it means that a deadlock happened in the locking context. This situation should be addressed by dropping all currently held locks and block until the contended lock becomes available. Currently, vc4 is not dealing with the deadlock properly, producing the following output when PROVE_LOCKING is enabled: [ 825.612809] ------------[ cut here ]------------ [ 825.612852] WA
the following output when PROVE_LOCKING is enabled: [ 825.612809] ------------[ cut here ]------------ [ 825.612852] WARNING: CPU: 1 PID: 116 at drivers/gpu/drm/drm_modeset_lock.c:276 drm_modeset_drop_locks+0x60/0x68 [drm] [ 825.613458] Modules linked in: 8021q mrp garp stp llc raspberrypi_cpufreq brcmfmac brcmutil crct10dif_ce hci_uart cfg80211 btqca btbcm bluetooth vc4 raspberrypi_hwmon snd_soc_hdmi_codec cec clk_raspberrypi ecdh_generic drm_display_helper ecc rfkill drm_dma_helper drm_kms_helper pwm_bcm2835 bcm2835_thermal bcm2835_rng rng_core i2c_bcm2835 drm fuse ip_tables x_tables ipv6 [ 825.613735] CPU: 1 PID: 116 Comm: kworker/1:2 Tainted: G W 6.1.0-rc6-01399-g941aae326315 #3 [ 825.6
bles x_tables ipv6 [ 825.613735] CPU: 1 PID: 116 Comm: kworker/1:2 Tainted: G W 6.1.0-rc6-01399-g941aae326315 #3 [ 825.613759] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT) [ 825.613777] Workqueue: events output_poll_execute [drm_kms_helper] [ 825.614038] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 825.614063] pc : drm_modeset_drop_locks+0x60/0x68 [drm] [ 825.614603] lr : drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper] [ 825.614829] sp : ffff800008313bf0 [ 825.614844] x29: ffff800008313bf0 x28: ffffcd7778b8b000 x27: 0000000000000000 [ 825.614883] x26: 0000000000000001 x25: 0000000000000001 x24: ffff677cc35c2758 [ 825.614920] x23: ffffcd7707d01430 x22: ffffcd77
883] x26: 0000000000000001 x25: 0000000000000001 x24: ffff677cc35c2758 [ 825.614920] x23: ffffcd7707d01430 x22: ffffcd7707c3edc7 x21: 0000000000000001 [ 825.614958] x20: 0000000000000000 x19: ffff800008313c10 x18: 000000000000b6d3 [ 825.614995] x17: ffffcd777835e214 x16: ffffcd7777cef870 x15: fffff81000000000 [ 825.615033] x14: 0000000000000000 x13: 0000000000000099 x12: 0000000000000002 [ 825.615070] x11: 72917988020af800 x10: 72917988020af800 x9 : 72917988020af800 [ 825.615108] x8 : ffff677cc665e0a8 x7 : d00a8c180000110c x6 : ffffcd77774c0054 [ 825.615145] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000 [ 825.615181] x2 : ffff677cc55e1880 x1 : ffffcd7777cef8ec x0 : ffff80
000000 x4 : 0000000000000001 x3 : 0000000000000000 [ 825.615181] x2 : ffff677cc55e1880 x1 : ffffcd7777cef8ec x0 : ffff800008313c10 [ 825.615219] Call trace: [ 825.615232] drm_modeset_drop_locks+0x60/0x68 [drm] [ 825.615773] drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper] [ 825.616003] output_poll_execute+0xe4/0x224 [drm_kms_helper] [ 825.616233] process_one_work+0x2b4/0x618 [ 825.616264] worker_thread+0x24c/0x464 [ 825.616288] kthread+0xec/0x110 [ 825.616310] ret_from_fork+0x10/0x20 [ 825.616335] irq event stamp: 7634 [ 825.616349] hardirqs last enabled at (7633): [<ffffcd777831ee90>] _raw_spin_unlock_irq+0x3c/0x78 [ 825.616384] hardirqs last disabled at (7634): [<ffffcd7778315a78>] __s
ffcd777831ee90>] _raw_spin_unlock_irq+0x3c/0x78 [ 825.616384] hardirqs last disabled at (7634): [<ffffcd7778315a78>] __schedule+0x134/0x9f0 [ 825.616411] softirqs last enabled at (7630): [<ffffcd7707aacea0>] local_bh_enable+0x4/0x30 [ipv6] [ 825.617019] softirqs last disabled at (7618): [<ffffcd7707aace70>] local_bh_disable+0x4/0x30 [ipv6] [ 825.617586] ---[ end trace 0000000000000000 ]--- Therefore, deal with the deadlock as suggested by [1], using the function drm_modeset_backoff(). [1] https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking References: - https://git.kernel.org/stable/c/41286a53e7f54202fd277cd516724de3ab7497c7 - https://git.kernel.org/stable/c/f483eda89a2e717daa
://git.kernel.org/stable/c/41286a53e7f54202fd277cd516724de3ab7497c7 - https://git.kernel.org/stable/c/f483eda89a2e717daa7b15c8ca228a209f65617b - https://git.kernel.org/stable/c/479d4f0be4237ba33bc9432787aeb62c90e30f95
CVE ID: CVE-2023-53456 State: PUBLISHED Published: 2025-10-01T11:42:27.821Z Last Updated: 2025-10-01T11:42:27.821Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: qla4xxx: Add length check when parsing nlattrs There are three places that qla4xxx parses nlattrs: - qla4xxx_set_chap_entry() - qla4xxx_iface_set_param() - qla4xxx_sysfs_ddb_set_param() and each of them directly converts the nlattr to specific pointer of structure without length checking. This could be dangerous as those attributes are not validated and a malformed nlattr (e.g., length 0) could result in an OOB read that leaks heap dirty data. Add the nla_len che
ated and a malformed nlattr (e.g., length 0) could result in an OOB read that leaks heap dirty data. Add the nla_len check before accessing the nlattr data and return EINVAL if the length check fails. References: - https://git.kernel.org/stable/c/cfa6a1a79ed6d336fac7a5d87eb5471e4401829f - https://git.kernel.org/stable/c/5925e224cc6edfef57b20447f18323208461309b - https://git.kernel.org/stable/c/47f3be62eab50b8cd7e1ae5fc2c4dae687497c34 - https://git.kernel.org/stable/c/6d65079c69dc1feb817ed71f5bd15e83a7d6832d - https://git.kernel.org/stable/c/f61fc650c47849637fa1771a31a11674c824138a - https://git.kernel.org/stable/c/25feffb3fbd51ae81d92c65cebc0e932663828b3 - https://git.kernel.org/stable/c/4ed
824138a - https://git.kernel.org/stable/c/25feffb3fbd51ae81d92c65cebc0e932663828b3 - https://git.kernel.org/stable/c/4ed21975311247bb84e82298eeb359ec0a0fa84d - https://git.kernel.org/stable/c/b018c0440b871d8b001c996e95fa4538bd292de6 - https://git.kernel.org/stable/c/47cd3770e31df942e2bb925a9a855c79ed0662eb
CVE ID: CVE-2023-53457 State: PUBLISHED Published: 2025-10-01T11:42:28.730Z Last Updated: 2025-10-01T11:42:28.730Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: FS: JFS: Fix null-ptr-deref Read in txBegin Syzkaller reported an issue where txBegin may be called on a superblock in a read-only mounted filesystem which leads to NULL pointer deref. This could be solved by checking if the filesystem is read-only before calling txBegin, and returning with appropiate error code. References: - https://git.kernel.org/stable/c/a7225e9e09519deb7e0c42eb6070029cc456e84d - https://git.kernel.org/stable/c/1b4c144767736221cad92c132f72b3c6ed06a
table/c/a7225e9e09519deb7e0c42eb6070029cc456e84d - https://git.kernel.org/stable/c/1b4c144767736221cad92c132f72b3c6ed06a0ea - https://git.kernel.org/stable/c/a7d17d6bd7cd4f6940b335ea7a6fce5b6d22adc2 - https://git.kernel.org/stable/c/2a3f20efe6c901d4c0871cfd1d8c65e2ade71fc1 - https://git.kernel.org/stable/c/3e94d0d378d2754b26fc54b429582553f7b53e15 - https://git.kernel.org/stable/c/3e5eb6c5ecd8ddb9cfea751cf30f9e23eac97ca3 - https://git.kernel.org/stable/c/fd2db13fb72ff18c633a48229589d42ceb89d1f8 - https://git.kernel.org/stable/c/47cfdc338d674d38f4b2f22b7612cc6a2763ba27
CVE ID: CVE-2023-53458 State: PUBLISHED Published: 2025-10-01T11:42:29.665Z Last Updated: 2025-10-01T11:42:29.665Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: cx23885: Fix a null-ptr-deref bug in buffer_prepare() and buffer_finish() When the driver calls cx23885_risc_buffer() to prepare the buffer, the function call dma_alloc_coherent may fail, resulting in a empty buffer risc->cpu. Later when we free the buffer or access the buffer, null ptr deref is triggered. This bug is similar to the following one: https://git.linuxtv.org/media_stage.git/commit/?id=2b064d91440b33fba5b452f2d1b31f13ae911d71. We believe the bug can