CVE-2023-54268

In the Linux kernel, the following vulnerability has been resolved:

debugobjects: Don't wake up kswapd from fill_pool()

syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock.

Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe.

Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.

In the Linux kernel, the following vulnerability has been resolved:

debugobjects: Don't wake up kswapd from fill_pool()

syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock.

Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe.

Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.

In the Linux kernel, the following vulnerability has been resolved:

debugobjects: Don't wake up kswapd from fill_pool()

syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock.

Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe.

Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.

In the Linux kernel, the following vulnerability has been resolved:

debugobjects: Don't wake up kswapd from fill_pool()

syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock.

Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe.

Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.

• rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present
• xfrm: esp: avoid in-place decrypt on shared skb frags
• clk: Fix clk_hw_get_clk() when dev is NULL {CVE-2022-49187}
• x86/sgx: Add overflow check in sgx_validate_offset_length() {CVE-2022-49785}
• ext4: init quota for 'old.inode' in 'ext4_rename' {CVE-2022-50346}
• skbuff: Account for tail adjustment during pull operations {CVE-2022-50365}
• net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory {CVE-2022-50409}
• scsi: qla2xxx: Delay module unload while fabric scan in progress {CVE-2025-71235}
• HID: alps: fix NULL pointer dereference in alps_raw_event() {CVE-2026-31625}
• rxrpc: fix reference count leak in rxrpc_server_keyring() {CVE-2026-31634}
• drm/i915/gt: Check set_default_submission() before deferencing {CVE-2026-31540}
• ACPICA: ACPICA: check null return of ACPI_ALLOCATE_ZEROED in acpi_db_display_objects {CVE-2023-54010}
• drm/amdgpu: fix the waring dereferencing hive {CVE-2024-46805}
• drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func {CVE-2024-49911}
• tracing: Prevent bad count for tracing_cpumask_write {CVE-2024-56763}
• HID: wacom: fix when get product name maybe null pointer {CVE-2024-56629}
• thermal: int340x: Add NULL check for adev {CVE-2025-23136}
• wifi: mac80211: Purge vif txq in ieee80211_do_stop() {CVE-2025-37794}
• Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb {CVE-2026-31510}
• wifi: cfg80211: ocb: don't leave if not joined {CVE-2023-53992}
• mmc: core: Fix kernel panic when remove non-standard SDIO card {CVE-2022-50640}
• EDAC/i10nm: fix refcount leak in pci_get_dev_wrapper() {CVE-2022-50645}
• serial: amba-pl011: avoid SBSA UART accessing DMACR register {CVE-2022-50625}
• inet_diag: Initialize pad field in struct inet_diag_req_v2 {CVE-2024-42106}
• regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt {CVE-2022-49481}
• net/core: Fix ETH_P_1588 flow dissector {CVE-2023-52580}
• mm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions() {CVE-2023-52560}
• af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg {CVE-2024-38596}
• drm/amd/display: Implement bounds check for stream encoder creation in DCN301 {CVE-2024-26660}
• block: prevent division by zero in blk_rq_stat_sum() {CVE-2024-35925}
• netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() {CVE-2024-36286}
• tipc: fix a possible memleak in tipc_buf_append {CVE-2024-36954}
• ipv6: prevent possible NULL deref in fib6_nh_init() {CVE-2024-40961}
• pinctrl: fix deadlock in create_pinctrl() when handling -EPROBE_DEFER {CVE-2024-42090}
• ipv6: prevent possible NULL dereference in rt6_probe() {CVE-2024-40960}
• drm/radeon: check bo_va->bo is non-NULL before using it {CVE-2024-41060}
• dma: fix call order in dmam_free_coherent {CVE-2024-43856}
• scsi: qla2xxx: Fix for possible memory corruption {CVE-2024-42288}
• ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt {CVE-2024-26774}
• netfilter: flowtable: incorrect pppoe tuple {CVE-2024-27015}
• bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() {CVE-2024-40919}
• Bluetooth: btintel: Fix null ptr deref in btintel_read_version {CVE-2024-35933}
• netdevsim: prevent bad user input in nsim_dev_health_break_write() {CVE-2024-56716}
• net/mlx5e: CT: Fix null-ptr-deref in add rule err flow {CVE-2024-53120}
• EDAC/bluefield: Fix potential integer overflow {CVE-2024-53161}
• NFSD: Prevent NULL dereference in nfsd4_process_cb_update() {CVE-2024-53217}
• ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() {CVE-2024-50304}
• blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race {CVE-2024-50082}
• drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse() {CVE-2025-21996}
• HID: appleir: Fix potential NULL dereference at raw event handle {CVE-2025-21948}
• filemap: Fix bounds checking in filemap_read()…

In the Linux kernel, the following vulnerability has been resolved:

debugobjects: Don't wake up kswapd from fill_pool()

syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock.

Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe.

Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.

In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don't wake up kswapd from fill_pool() syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock. Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe. Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.

In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don't wake up kswapd from fill_pool() syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock. Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe. Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.