CVE-2024-50302

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

HID: core: zero-initialize the report buffer

Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.

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

HID: core: zero-initialize the report buffer

Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.

In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() Since '__dev_queue_xmit()' should be called with interrupts enabled, the following backtrace: ieee80211_do_stop() ... spin_lock_irqsave(&local->queue_stop_reason_lock, flags) ... ieee80211_free_txskb() ieee80211_report_used_skb() ieee80211_report_ack_skb() cfg80211_mgmt_tx_status_ext() nl80211_frame_tx_status() genlmsg_multicast_netns() genlmsg_multicast_netns_filtered() nlmsg_multicast_filtered() netlink_broadcast_filtered() do_one_broadcast() netlink_broadcast_deliver() __netlink_sendskb() netlink_deliver_tap() __netlink_deliver_tap_skb() dev_queue_xmit() __dev_queue_xmit() ; with IRQS disabled ... spin_unlock_irqrestore(&local->queue_stop_reason_lock, flags) issues the warning (as reported by syzbot reproducer): WARNING: CPU: 2 PID: 5128 at kernel/softirq.c:362 __local_bh_enable_ip+0xc3/0x120 Fix this by implementing a two-phase skb reclamation in 'ieee80211_do_stop()', where actual work is performed outside of a section with interrupts disabled.(CVE-2024-47713)

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix helper writes to read-only maps Lonial found an issue that despite user- and BPF-side frozen BPF map (like in case of .rodata), it was still possible to write into it from a BPF program side through specific helpers having ARG_PTR_TO_{LONG,INT} as arguments. In check_func_arg() when the argument is as mentioned, the meta->raw_mode is never set. Later, check_helper_mem_access(), under the case of PTR_TO_MAP_VALUE as register base type, it assumes BPF_READ for the subsequent call to check_map_access_type() and given the BPF map is read-only it succeeds. The helpers really need to be annotated as ARG_PTR_TO_{LONG,INT} | MEM_UNINIT when results are written into them as opposed to read out of them. The latter indicates that it's okay to pass a pointer to uninitialized memory as the memory is written to anyway. However, ARG_PTR_TO_{LONG,INT} is a special case of ARG_PTR_TO_FIXED_SIZE_MEM just with additional alignment requirement. So it is better to just get rid of the ARG_PTR_TO_{LONG,INT} special cases altogether and reuse the fixed size memory types. For this, add MEM_ALIGNED to additionally ensure alignment given these helpers write directly into the args via <ptr> = val. The .arg_size has been initialized reflecting the actual sizeof(*<ptr>). MEM_ALIGNED can only be used in combination with MEM_FIXED_SIZE annotated argument types, since in !MEM_FIXED_SIZE cases the verifier does not know the buffer size a priori and therefore cannot blindly write *<ptr> = val.(CVE-2024-49861)

In the Linux kernel, the following vulnerability has been resolved: vhost/scsi: null-ptr-dereference in vhost_scsi_get_req() Since commit 3f8ca2e115e5 ("vhost/scsi: Extract common handling code from control queue handler") a null pointer dereference bug can be triggered when guest sends an SCSI AN request. In vhost_scsi_ctl_handle_vq(), vc.target is assigned with &v_req.tmf.lun[1] within a switch-case block and is then passed to vhost_scsi_get_req() which extracts vc->req and tpg. However, for a VIRTIO_SCSI_T_AN_* request, tpg is not required, so vc.target is set to NULL in this branch. Later, in vhost_scsi_get_req(), vc->target is dereferenced without being checked, leading to a null pointer dereference bug. This bug can be triggered from guest. When this bug occurs, the vhost_worker process is killed while holding vq->mutex and the corresponding tpg will remain occupied indefinitely. Below is the KASAN report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for multiple streams case When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens. This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious). Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again. [Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.] Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all). It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all). > Another fix to solve clearing the caches of all stream rings with > cancelled TDs is needed, but not as urgent. 3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please. Fixes xHC crashes and IOMMU faults with UAS devices when handling errors/faults. Easiest repro is to use hdparm to mark an early sector (e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop. At least in the case of JMicron controllers, the read errors end up having to cancel two TDs (for two queued requests to different streams) and the one that didn't get cleared properly ends up faulting the xHC entirely when it tries to access DMA pages that have since been unmapped, referred to by the stale TDs. This normally happens quickly (after two or three loops). After this fix, I left the cat in a loop running overnight and experienced no xHC failures, with all read errors recovered…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: usb: typec: altmode should keep reference to parent The altmode device release refers to its parent device, but without keeping a reference to it. When registering the altmode, get a reference to the parent and put it in the release function. Before this fix, when using CONFIG_DEBUG_KOBJECT_RELEASE, we see issues like this: [ 43.572860] kobject: 'port0.0' (ffff8880057ba008): kobject_release, parent 0000000000000000 (delayed 3000) [ 43.573532] kobject: 'port0.1' (ffff8880057bd008): kobject_release, parent 0000000000000000 (delayed 1000) [ 43.574407] kobject: 'port0' (ffff8880057b9008): kobject_release, parent 0000000000000000 (delayed 3000) [ 43.575059] kobject: 'port1.0' (ffff8880057ca008): kobject_release, parent 0000000000000000 (delayed 4000) [ 43.575908] kobject: 'port1.1' (ffff8880057c9008): kobject_release, parent 0000000000000000 (delayed 4000) [ 43.576908] kobject: 'typec' (ffff8880062dbc00): kobject_release, parent 0000000000000000 (delayed 4000) [ 43.577769] kobject: 'port1' (ffff8880057bf008): kobject_release, parent 0000000000000000 (delayed 3000) [ 46.612867] ================================================================== [ 46.613402] BUG: KASAN: slab-use-after-free in typec_altmode_release+0x38/0x129 [ 46.614003] Read of size 8 at addr ffff8880057b9118 by task kworker/2:1/48 [ 46.614538] [ 46.614668] CPU: 2 UID: 0 PID: 48 Comm: kworker/2:1 Not tainted 6.12.0-rc1-00138-gedbae730ad31 #535 [ 46.615391] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 46.616042] Workqueue: events kobject_delayed_cleanup [ 46.616446] Call Trace: [ 46.616648] <TASK> [ 46.616820] dump_stack_lvl+0x5b/0x7c [ 46.617112] ? typec_altmode_release+0x38/0x129 [ 46.617470] print_report+0x14c/0x49e [ 46.617769] ? rcu_read_unlock_sched+0x56/0x69 [ 46.618117] ? __virt_addr_valid+0x19a/0x1ab [ 46.618456] ? kmem_cache_debug_flags+0xc/0x1d [ 46.618807] ? typec_altmode_release+0x38/0x129 [ 46.619161] kasan_report+0x8d/0xb4 [ 46.619447] ? typec_altmode_release+0x38/0x129 [ 46.619809] ? process_scheduled_works+0x3cb/0x85f [ 46.620185] typec_altmode_release+0x38/0x129 [ 46.620537] ? process_scheduled_works+0x3cb/0x85f [ 46.620907] device_release+0xaf/0xf2 [ 46.621206] kobject_delayed_cleanup+0x13b/0x17a [ 46.621584] process_scheduled_works+0x4f6/0x85f [ 46.621955] ? __pfx_process_scheduled_works+0x10/0x10 [ 46.622353] ? hlock_class+0x31/0x9a [ 46.622647] ? lock_acquired+0x361/0x3c3 [ 46.622956] ? move_linked_works+0x46/0x7d [ 46.623277] worker_thread+0x1ce/0x291 [ 46.623582] ? __kthread_parkme+0xc8/0xdf [ 46.623900] ? __pfx_worker_thread+0x10/0x10 [ 46.624236] kthread+0x17e/0x190 [ 46.624501] ? kthread+0xfb/0x190 [ 46.624756] ? __pfx_kthread+0x10/0x10 [ 46.625015] ret_from_fork+0x20/0x40 [ 46.625268] ? __pfx_kthread+0x10/0x10 [ 46.625532] ret_from_fork_asm+0x1a/0x30 [ 46.625805] </TASK> [ 46.625953] [ 46.626056] Allocated by task 678: [ 46.626287] kasan_save_stack+0x24/0x44 [ 46.626555] kasan_save_track+0x14/0x2d [ 46.626811] __kasan_kmalloc+0x3f/0x4d [ 46.627049] __kmalloc_noprof+0x1bf/0x1f0 [ 46.627362] typec_register_port+0x23/0x491 [ 46.627698] cros_typec_probe+0x634/0xbb6 [ 46.628026] platform_probe+0x47/0x8c [ 46.628311] really_probe+0x20a/0x47d [ 46.628605] device_driver_attach+0x39/0x72 [ 46.628940] bind_store+0x87/0xd7 [ 46.629213] kernfs_fop_write_iter+0x1aa/0x218 [ 46.629574] vfs_write+0x1d6/0x29b [ 46.629856] ksys_write+0xcd/0x13b [ 46.630128] do_syscall_64+0xd4/0x139 [ 46.630420] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 46.630820] [ 46.630946] Freed by task 48: [ 46.631182] kasan_save_stack+0x24/0x44 [ …

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() Since '__dev_queue_xmit()' should be called with interrupts enabled, the following backtrace: ieee80211_do_stop() ... spin_lock_irqsave(&local->queue_stop_reason_lock, flags) ... ieee80211_free_txskb() ieee80211_report_used_skb() ieee80211_report_ack_skb() cfg80211_mgmt_tx_status_ext() nl80211_frame_tx_status() genlmsg_multicast_netns() genlmsg_multicast_netns_filtered() nlmsg_multicast_filtered() netlink_broadcast_filtered() do_one_broadcast() netlink_broadcast_deliver() __netlink_sendskb() netlink_deliver_tap() __netlink_deliver_tap_skb() dev_queue_xmit() __dev_queue_xmit() ; with IRQS disabled ... spin_unlock_irqrestore(&local->queue_stop_reason_lock, flags) issues the warning (as reported by syzbot reproducer): WARNING: CPU: 2 PID: 5128 at kernel/softirq.c:362 __local_bh_enable_ip+0xc3/0x120 Fix this by implementing a two-phase skb reclamation in 'ieee80211_do_stop()', where actual work is performed outside of a section with interrupts disabled.(CVE-2024-47713)

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix helper writes to read-only maps Lonial found an issue that despite user- and BPF-side frozen BPF map (like in case of .rodata), it was still possible to write into it from a BPF program side through specific helpers having ARG_PTR_TO_{LONG,INT} as arguments. In check_func_arg() when the argument is as mentioned, the meta->raw_mode is never set. Later, check_helper_mem_access(), under the case of PTR_TO_MAP_VALUE as register base type, it assumes BPF_READ for the subsequent call to check_map_access_type() and given the BPF map is read-only it succeeds. The helpers really need to be annotated as ARG_PTR_TO_{LONG,INT} | MEM_UNINIT when results are written into them as opposed to read out of them. The latter indicates that it's okay to pass a pointer to uninitialized memory as the memory is written to anyway. However, ARG_PTR_TO_{LONG,INT} is a special case of ARG_PTR_TO_FIXED_SIZE_MEM just with additional alignment requirement. So it is better to just get rid of the ARG_PTR_TO_{LONG,INT} special cases altogether and reuse the fixed size memory types. For this, add MEM_ALIGNED to additionally ensure alignment given these helpers write directly into the args via <ptr> = val. The .arg_size has been initialized reflecting the actual sizeof(*<ptr>). MEM_ALIGNED can only be used in combination with MEM_FIXED_SIZE annotated argument types, since in !MEM_FIXED_SIZE cases the verifier does not know the buffer size a priori and therefore cannot blindly write *<ptr> = val.(CVE-2024-49861)

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointer before try to access it [why & how] Change the order of the pipe_ctx->plane_state check to ensure that plane_state is not null before accessing it.(CVE-2024-49906)

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Pass non-null to dcn20_validate_apply_pipe_split_flags [WHAT & HOW] "dcn20_validate_apply_pipe_split_flags" dereferences merge, and thus it cannot be a null pointer. Let's pass a valid pointer to avoid null dereference. This fixes 2 FORWARD_NULL issues reported by Coverity.(CVE-2024-49923)

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Fix zero-division error when disabling tc cbs The commit b8c43360f6e4 ("net: stmmac: No need to calculate speed divider when offload is disabled") allows the "port_transmit_rate_kbps" to be set to a value of 0, which is then passed to the "div_s64" function when tc-cbs is disabled.…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for multiple streams case When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens. This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious). Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again. [Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.] Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all). It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all). > Another fix to solve clearing the caches of all stream rings with > cancelled TDs is needed, but not as urgent. 3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please. Fixes xHC crashes and IOMMU faults with UAS devices when handling errors/faults. Easiest repro is to use hdparm to mark an early sector (e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop. At least in the case of JMicron controllers, the read errors end up having to cancel two TDs (for two queued requests to different streams) and the one that didn't get cleared properly ends up faulting the xHC entirely when it tries to access DMA pages that have since been unmapped, referred to by the stale TDs. This normally happens quickly (after two or three loops). After this fix, I left the cat in a loop running overnight and experienced no xHC failures, with all read errors recovered…

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: HID: core: zero-initialize the report buffer (CVE-2024-50302)

• kernel: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (CVE-2024-53197)

• kernel: scsi: megaraid_sas: Fix for a potential deadlock (CVE-2024-57807)

• kernel: pps: Fix a use-after-free (CVE-2024-57979)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: HID: core: zero-initialize the report buffer (CVE-2024-50302)

• kernel: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (CVE-2024-53197)

• kernel: scsi: megaraid_sas: Fix for a potential deadlock (CVE-2024-57807)

• kernel: pps: Fix a use-after-free (CVE-2024-57979)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: HID: core: zero-initialize the report buffer (CVE-2024-50302)
• kernel: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (CVE-2024-53197)
• kernel: scsi: megaraid_sas: Fix for a potential deadlock (CVE-2024-57807)
• kernel: pps: Fix a use-after-free (CVE-2024-57979)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: HID: core: zero-initialize the report buffer (CVE-2024-50302)
• kernel: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (CVE-2024-53197)
• kernel: scsi: megaraid_sas: Fix for a potential deadlock (CVE-2024-57807)
• kernel: pps: Fix a use-after-free (CVE-2024-57979)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: ACPI: extlog: fix NULL pointer dereference check (CVE-2023-52605)
• kernel: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans (CVE-2024-50264)
• kernel: HID: core: zero-initialize the report buffer (CVE-2024-50302)
• kernel: can: bcm: Fix UAF in bcm_proc_show() (CVE-2023-52922)
• kernel: mm: fix NULL pointer dereference in alloc_pages_bulk_noprof (CVE-2024-53113)
• kernel: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (CVE-2024-53197)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

In hid_alloc_report_buf of hid-core.c, there is a possible leak of kernel memory contents to a USB HID due to uninitialized data. This could lead to physical information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

• HID: core: zero-initialize the report buffer {CVE-2024-50302}
• Revert "drm/amdgpu: add missing size check in amdgpu_debugfs_gprwave_read()"
• drm/amd/amdgpu: Fix GPR read from debugfs (v2) {CVE-2024-50282}
• USB: serial: io_edgeport: fix use after free in debug printk {CVE-2024-50267}
• wifi: iwlegacy: Clear stale interrupts before resuming device {CVE-2024-50234}
• udf: fix uninit-value use in udf_get_fileshortad {CVE-2024-50143}
• Update dependency for shim and signing key

• CVE-url: https://ubuntu.com/security/CVE-2024-50180
  • fbdev: sisfb: Fix strbuf array overflow
• CVE-url: https://ubuntu.com/security/CVE-2023-52522
  • net: fix possible store tearing in neigh_periodic_work()
• CVE-url: https://ubuntu.com/security/CVE-2024-40911
  • wifi: cfg80211: Lock wiphy in cfg80211_get_station
• CVE-url: https://ubuntu.com/security/CVE-2024-43863
  • drm/vmwgfx: Fix a deadlock in dma buf fence polling
• CVE-url: https://ubuntu.com/security/CVE-2024-44931
  • gpio: prevent potential speculation leaks in gpio_device_get_desc()
• CVE-url: https://ubuntu.com/security/CVE-2024-23848
  • media: cec: cec-api: add locking in cec_release()
  • media: cec: core: avoid recursive cec_claim_log_addrs
• CVE-url: https://ubuntu.com/security/CVE-2024-50229
  • nilfs2: fix potential deadlock with newly created symlinks
• CVE-url: https://ubuntu.com/security/CVE-2024-50171
  • net: systemport: fix potential memory leak in bcm_sysport_xmit()
• CVE-url: https://ubuntu.com/security/CVE-2024-50233
  • staging: iio: frequency: ad9832: fix division by zero in ad9832_calc_freqreg()
• CVE-url: https://ubuntu.com/security/CVE-2024-50134
  • drm/vboxvideo: Replace fake VLA at end of vbva_mouse_pointer_shape with real VLA
• CVE-url: https://ubuntu.com/security/CVE-2024-44938
  • jfs: Fix shift-out-of-bounds in dbDiscardAG
• CVE-url: https://ubuntu.com/security/CVE-2024-50117
  • drm/amd: Guard against bad data for ATIF ACPI method
• CVE-url: https://ubuntu.com/security/CVE-2024-49902
  • jfs: check if leafidx greater than num leaves per dmap tree
• CVE-url: https://ubuntu.com/security/CVE-2023-52799
  • jfs: fix array-index-out-of-bounds in dbFindLeaf
• CVE-url: https://ubuntu.com/security/CVE-2024-49966
  • ocfs2: cancel dqi_sync_work before freeing oinfo
• CVE-url: https://ubuntu.com/security/CVE-2024-50267
  • USB: serial: io_edgeport: fix use after free in debug printk
• CVE-url: https://ubuntu.com/security/CVE-2024-50230
  • nilfs2: fix kernel bug due to missing clearing of checked flag
• CVE-url: https://ubuntu.com/security/CVE-2024-50302
  • HID: core: zero-initialize the report buffer
• CVE-url: https://ubuntu.com/security/CVE-2024-50278
  • dm cache: fix out-of-bounds access to the dirty bitset when resizing
  • dm cache: fix potential out-of-bounds access on the first resume
• CVE-url: https://ubuntu.com/security/CVE-2024-50234
  • wifi: iwlegacy: Clear stale interrupts before resuming device
• CVE-url: https://ubuntu.com/security/CVE-2024-50301
  • security/keys: fix slab-out-of-bounds in key_task_permission
• CVE-url: https://ubuntu.com/security/CVE-2024-50143
  • overflow: Add _must_check attribute to check*() helpers
  • compiler.h: drop fallback overflow checkers
  • overflow: Allow mixed type arguments
  • udf: fix uninit-value use in udf_get_fileshortad
• CVE-url: https://ubuntu.com/security/CVE-2024-53061
  • media: s5p-jpeg: prevent buffer overflows
• CVE-url: https://ubuntu.com/security/CVE-2024-57798
  • drm/dp-mst-helper: Remove hotplug callback
  • drm/dp_mst: Remove huge conditional in drm_dp_mst_handle_up_req()
  • drm/dp_mst: Refactor drm_dp_mst_handle_up_req()
  • drm/dp_mst: Rename drm_dp_add_port and drm_dp_update_port
  • drm/dp_mst: Handle UP requests asynchronously
  • drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req()
• CVE-url: https://ubuntu.com/security/CVE-2023-52854
  • padata: make padata_do_parallel find alternate callback CPU
  • padata: allocate workqueue internally
  • crypto: pcrypt - remove padata cpumask notifier
  • padata, pcrypt: take CPU hotplug lock internally in padata_alloc_possible
  • padata: use separate workqueues for parallel and serial work
  • padata: unbind parallel jobs from specific CPUs
  • workqueue: Make…

• CVE-url: https://ubuntu.com/security/CVE-2023-52522
  • net: fix possible store tearing in neigh_periodic_work()
• CVE-url: https://ubuntu.com/security/CVE-2024-40911
  • wifi: cfg80211: Lock wiphy in cfg80211_get_station
• CVE-url: https://ubuntu.com/security/CVE-2024-43863
  • drm/vmwgfx: Fix a deadlock in dma buf fence polling
• CVE-url: https://ubuntu.com/security/CVE-2024-44931
  • gpio: prevent potential speculation leaks in gpio_device_get_desc()
• CVE-url: https://ubuntu.com/security/CVE-2024-50229
  • nilfs2: fix potential deadlock with newly created symlinks
• CVE-url: https://ubuntu.com/security/CVE-2024-50171
  • net: systemport: fix potential memory leak in bcm_sysport_xmit()
• CVE-url: https://ubuntu.com/security/CVE-2024-50233
  • staging: iio: frequency: ad9832: fix division by zero in ad9832_calc_freqreg()
• CVE-url: https://ubuntu.com/security/CVE-2024-44938
  • jfs: Fix shift-out-of-bounds in dbDiscardAG
• CVE-url: https://ubuntu.com/security/CVE-2024-50117
  • drm/amd: Guard against bad data for ATIF ACPI method
• CVE-url: https://ubuntu.com/security/CVE-2024-49902
  • jfs: check if leafidx greater than num leaves per dmap tree
• CVE-url: https://ubuntu.com/security/CVE-2023-52799
  • jfs: fix array-index-out-of-bounds in dbFindLeaf
• CVE-url: https://ubuntu.com/security/CVE-2024-41063
  • Bluetooth: fix power_on vs close race
  • Bluetooth: hci_core: cancel all works upon hci_unregister_dev()
• CVE-url: https://ubuntu.com/security/CVE-2024-50267
  • USB: serial: io_edgeport: fix use after free in debug printk
• CVE-url: https://ubuntu.com/security/CVE-2024-50230
  • nilfs2: fix kernel bug due to missing clearing of checked flag
• CVE-url: https://ubuntu.com/security/CVE-2024-50302
  • HID: core: zero-initialize the report buffer
• CVE-url: https://ubuntu.com/security/CVE-2024-50180
  • fbdev: sisfb: Fix strbuf array overflow
• CVE-url: https://ubuntu.com/security/CVE-2024-50278
  • dm cache: fix out-of-bounds access to the dirty bitset when resizing
  • dm cache: fix potential out-of-bounds access on the first resume
• CVE-url: https://ubuntu.com/security/CVE-2024-50234
  • wifi: iwlegacy: Clear stale interrupts before resuming device
• CVE-url: https://ubuntu.com/security/CVE-2024-50301
  • security/keys: fix slab-out-of-bounds in key_task_permission
• CVE-url: https://ubuntu.com/security/CVE-2024-50143
  • overflow: Add _must_check attribute to check*() helpers
  • compiler.h: drop fallback overflow checkers
  • overflow: Allow mixed type arguments
  • udf: fix uninit-value use in udf_get_fileshortad
• Bionic update: upstream stable patchset 2020-11-10 (LP: #1903768) // CVE- url: https://ubuntu.com/security/CVE-2024-50143
  • overflow: Include header file with SIZE_MAX declaration
• Bionic update: upstream stable patchset 2020-09-16 (LP: #1895873) // CVE- url: https://ubuntu.com/security/CVE-2024-50143
  • overflow.h: Add allocation size calculation helpers
• Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) // CVE- url: https://ubuntu.com/security/CVE-2024-50143
  • overflow.h: Add arithmetic shift helper
• CVE-url: https://ubuntu.com/security/CVE-2024-53061
  • media: s5p-jpeg: prevent buffer overflows
• CVE-url: https://ubuntu.com/security/CVE-2024-47809
  • dlm: fix possible lkb_resource null dereference
• CVE-url: https://ubuntu.com/security/CVE-2024-41020
  • filelock: Fix fcntl/close race recovery compat path
• CVE-url: https://ubuntu.com/security/CVE-2024-43892
  • memcg: protect concurrent access to mem_cgroup_idr
• CVE-url: https://ubuntu.com/security/CVE-2021-47379
  • blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd
• CVE-url: https://ubuntu.com/security/CVE-2024-53239
  • ALSA: 6fire: Release resources at card release
• CVE-url:…

• HID: core: zero-initialize the report buffer {CVE-2024-50302}
• Revert "drm/amdgpu: add missing size check in amdgpu_debugfs_gprwave_read()"
• drm/amd/amdgpu: Fix GPR read from debugfs (v2) {CVE-2024-50282}
• USB: serial: io_edgeport: fix use after free in debug printk {CVE-2024-50267}
• wifi: iwlegacy: Clear stale interrupts before resuming device {CVE-2024-50234}
• udf: fix uninit-value use in udf_get_fileshortad {CVE-2024-50143}
• Update dependency for shim and signing key

• net: defer final 'struct net' free in netns dismantle {CVE-2024-56658}
• smb: client: fix potential deadlock when releasing mids {CVE-2023-52757}
• tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). {CVE-2024-50154}
• ALSA: 6fire: Release resources at card release {CVE-2024-53239}
• smb: client: fix use-after-free of signing key {CVE-2024-53179}
• tun: avoid double free in tun_free_netdev {CVE-2022-4744}
• Revert "tun: call dev_get_valid_name() before register_netdevice()" {CVE-2022-4744}
• USB: serial: io_edgeport: fix use after free in debug printk {CVE-2024-50267}
• igb: Fix use-after-free error during reset {CVE-2021-47301}
• HID: core: zero-initialize the report buffer {CVE-2024-50302}
• usb: musb: sunxi: Fix accessing an released usb phy {CVE-2024-50269}
• dm cache: fix potential out-of-bounds access on the first resume {CVE-2024-50278}
• dm cache: fix out-of-bounds access to the dirty bitset when resizing {CVE-2024-50278}
• wifi: iwlegacy: Clear stale interrupts before resuming device {CVE-2024-50234}
• security/keys: fix slab-out-of-bounds in key_task_permission {CVE-2024-50301}
• udf: fix uninit-value use in udf_get_fileshortad {CVE-2024-50143}
• overflow: Allow mixed type arguments {CVE-2024-50143}
• compiler.h: drop fallback overflow checkers {CVE-2024-50143}
• overflow: Add _must_check attribute to check*() helpers {CVE-2024-50143}
• media: s5p-jpeg: prevent buffer overflows {CVE-2024-53061}
• mptcp: fix double-free on socket dismantle {CVE-2024-26782}
• drm/amdgpu: fix usage slab after free {CVE-2024-56551}
• bpf: fix OOB devmap writes when deleting elements {CVE-2024-56615}
• uprobe: avoid out-of-bounds memory access of fetching args {CVE-2024-50067}

• net: defer final 'struct net' free in netns dismantle {CVE-2024-56658}
• smb: client: fix potential deadlock when releasing mids {CVE-2023-52757}
• tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). {CVE-2024-50154}
• ALSA: 6fire: Release resources at card release {CVE-2024-53239}
• smb: client: fix use-after-free of signing key {CVE-2024-53179}
• inet_connection_sock: remove unused parameter of reqsk_queue_unlink func {CVE-2024-50154}
• tun: avoid double free in tun_free_netdev {CVE-2022-4744}
• USB: serial: io_edgeport: fix use after free in debug printk {CVE-2024-50267}
• igb: Fix use-after-free error during reset {CVE-2021-47301}
• HID: core: zero-initialize the report buffer {CVE-2024-50302}
• usb: musb: sunxi: Fix accessing an released usb phy {CVE-2024-50269}
• dm cache: fix potential out-of-bounds access on the first resume {CVE-2024-50278}
• dm cache: fix out-of-bounds access to the dirty bitset when resizing {CVE-2024-50278}
• wifi: iwlegacy: Clear stale interrupts before resuming device {CVE-2024-50234}
• security/keys: fix slab-out-of-bounds in key_task_permission {CVE-2024-50301}
• udf: fix uninit-value use in udf_get_fileshortad {CVE-2024-50143}
• overflow: Allow mixed type arguments {CVE-2024-50143}
• compiler.h: drop fallback overflow checkers {CVE-2024-50143}
• overflow: Add _must_check attribute to check*() helpers {CVE-2024-50143}
• media: s5p-jpeg: prevent buffer overflows {CVE-2024-53061}
• mptcp: fix double-free on socket dismantle {CVE-2024-26782}
• drm/amdgpu: fix usage slab after free {CVE-2024-56551}
• bpf: fix OOB devmap writes when deleting elements {CVE-2024-56615}
• uprobe: avoid out-of-bounds memory access of fetching args {CVE-2024-50067}

• USB: serial: io_edgeport: fix use after free in debug printk {CVE-2024-50267}
• HID: core: zero-initialize the report buffer {CVE-2024-50302}
• dm cache: fix potential out-of-bounds access on the first resume {CVE-2024-50278}
• dm cache: fix out-of-bounds access to the dirty bitset when resizing {CVE-2024-50278}
• wifi: iwlegacy: Clear stale interrupts before resuming device {CVE-2024-50234}
• security/keys: fix slab-out-of-bounds in key_task_permission {CVE-2024-50301}
• udf: fix uninit-value use in udf_get_fileshortad {CVE-2024-50143}
• overflow: Allow mixed type arguments {CVE-2024-50143}
• compiler.h: drop fallback overflow checkers {CVE-2024-50143}
• overflow: Add _must_check attribute to check*() helpers {CVE-2024-50143}
• mptcp: fix double-free on socket dismantle {CVE-2024-26782}
• drm/amdgpu: fix usage slab after free {CVE-2024-56551}
• drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() {CVE-2024-57798}
• drm/dp_mst: Skip CSN if topology probing is not done yet {CVE-2024-57798}

• HID: core: zero-initialize the report buffer {CVE-2024-50302}
• net: defer final 'struct net' free in netns dismantle {CVE-2024-56658}
• bus: mhi: host: Add alignment check for event ring read pointer {CVE-2023-52494}
• net: sched: fix ets qdisc OOB Indexing {CVE-2025-21692}
• parport: Proper fix for array out-of-bounds access {CVE-2024-50074}
• udf: fix uninit-value use in udf_get_fileshortad {CVE-2024-50143}
• security/keys: fix slab-out-of-bounds in key_task_permission {CVE-2024-50301}
• usb: typec: altmode should keep reference to parent {CVE-2024-50150}
• dm cache: fix potential out-of-bounds access on the first resume {CVE-2024-50278}
• dm cache: optimize dirty bit checking with find_next_bit when resizing {CVE-2024-50278}
• dm cache: fix out-of-bounds access to the dirty bitset when resizing {CVE-2024-50279}
• spi: nxp-fspi: fix the KASAN report out-of-bounds bug {CVE-2024-46853}
• smb: client: fix OOBs when building SMB2_IOCTL request {CVE-2024-50151}
• net: sched: fix use-after-free in taprio_change() {CVE-2024-50127}
• USB: serial: io_edgeport: fix use after free in debug printk {CVE-2024-50267}
• wifi: iwlwifi: mvm: Fix response handling in iwl_mvm_send_recovery_cmd() {CVE-2024-53059}
• wifi: iwlwifi: mvm: disconnect station vifs if recovery failed {CVE-2024-53059}
• tracing: Consider the NULL character when validating the event length {CVE-2024-50131}
• crypto: scomp - fix req->dst buffer overflow {CVE-2023-52612}
• NFSD: fix hang in nfsd4_shutdown_callback {CVE-2025-21795}
• NFSD: add courteous server support for thread with only delegation {CVE-2025-21795}
• mptcp: refactor passive socket initialization {CVE-2024-26782}
• mptcp: implement delayed seq generation for passive fastopen {CVE-2024-26782}
• smb: client: fix potential UAF in smb2_is_valid_lease_break() {CVE-2024-35864}
• smb: client: fix potential UAF in cifs_dump_full_key() {CVE-2024-35866}
• cifs: fix session state check in reconnect to avoid use-after-free issue {CVE-2024-35866}
• smb: client: fix potential UAF in smb2_is_network_name_deleted() {CVE-2024-35862}
• smb: client: fix potential UAF in is_valid_oplock_break() {CVE-2024-35863}
• smb: client: fix potential UAF in cifs_stats_proc_show() {CVE-2024-35867}
• bpf: Protect against int overflow for stack access size {CVE-2024-35905}
• bpf: Fix verification of indirect var-off stack access {CVE-2024-35905}
• devlink: fix possible use-after-free and memory leaks in devlink_init() {CVE-2024-26734}
• leds: trigger: Unregister sysfs attributes before calling deactivate() {CVE-2024-43830}
• ionic: fix use after netif_napi_del() {CVE-2024-39502}
• ionic: clean interrupt before enabling queue to avoid credit race {CVE-2024-39502}
• net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink {CVE-2024-44970}
• vt_ioctl: fix array_index_nospec in vt_setactivate {CVE-2022-48804}
• hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() {CVE-2022-49011}
• raid1: fix use-after-free for original bio in raid1_write_request() {CVE-2024-35979}
• md/raid1: free the r1bio before waiting for blocked rdev {CVE-2024-35979}
• drm/amdgpu: fix usage slab after free {CVE-2024-56551}
• drm/amd: Use amdgpu_ucode_* helpers for GPU info bin {CVE-2024-56551}
• drm/amd: Add a new helper for loading/validating microcode {CVE-2024-56551}
• drm/amd: check num of link levels when update pcie param {CVE-2023-52812}
• drm/amd: Update update_pcie_parameters functions to use uint8_t arguments {CVE-2023-52812}
• drm/amd: Disable PP_PCIE_DPM_MASK when dynamic speed switching not supported {CVE-2023-52812}
• drm/amd: Fix logic error in sienna_cichlid_update_pcie_parameters() {CVE-2023-52812}
• drm/amd: Use amdgpu_device_pcie_dynamic_switching_supported() for SMU7 {CVE-2023-52812}
• drm/amd: Align SMU11 SMU_MSG_OverridePcieParameters implementation with SMU13 {CVE-2023-52812}
• drm/amd/pm: conditionally disable pcie lane switching for some sienna_cichlid SKUs {CVE-2023-52812}
• drm/amd: Move helper for dynamic speed switch check out…

• sctp: sysctl: auth_enable: avoid using current->nsproxy
• sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy {CVE-2025-21640}
• bpf: Use preempt_count() directly in bpf_send_signal_common()
• Revert "sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy"
• jfs: fix slab-out-of-bounds read in ea_get()
• serial: 8250_dma: terminate correct DMA in tx_dma_flush()
• Revert "sctp: sysctl: auth_enable: avoid using current->nsproxy"
• net: usb: usbnet: restore usb%d name exception for local mac addresses
• vlan: fix memory leak in vlan_newlink() {CVE-2022-49636}
• rds: ib: Fix NULL ptr deref in rds_ib_cq_follow_affinity
• LTS tag: v5.4.291
• eeprom: digsy_mtc: Make GPIO lookup table match the device
• slimbus: messaging: Free transaction ID in delayed interrupt scenario {CVE-2025-21914}
• intel_th: pci: Add Panther Lake-P/U support
• intel_th: pci: Add Panther Lake-H support
• intel_th: pci: Add Arrow Lake support
• Squashfs: check the inode number is not the invalid value of zero {CVE-2024-26982}
• xhci: pci: Fix indentation in the PCI device ID definitions
• usb: gadget: Check bmAttributes only if configuration is valid
• usb: gadget: Fix setting self-powered state on suspend
• usb: gadget: Set self-powered based on MaxPower and bmAttributes
• usb: typec: tcpci_rt1711h: Unmask alert interrupts to fix functionality
• usb: typec: ucsi: increase timeout for PPM reset operations
• usb: atm: cxacru: fix a flaw in existing endpoint checks {CVE-2025-21916}
• usb: renesas_usbhs: Flush the notify_hotplug_work {CVE-2025-21917}
• usb: quirks: Add DELAY_INIT and NO_LPM for Prolific Mass Storage Card Reader
• usb: renesas_usbhs: Use devm_usb_get_phy()
• usb: renesas_usbhs: Call clk_put()
• Revert "drivers/card_reader/rtsx_usb: Restore interrupt based detection"
• gpio: rcar: Fix missing of_node_put() call
• net: ipv6: fix missing dst ref drop in ila lwtunnel
• net: ipv6: fix dst ref loop in ila lwtunnel
• net-timestamp: support TCP GSO case for a few missing flags
• vlan: enforce underlying device type {CVE-2025-21920}
• ppp: Fix KMSAN uninit-value warning with bpf {CVE-2025-21922}
• be2net: fix sleeping while atomic bugs in be_ndo_bridge_getlink
• drm/sched: Fix preprocessor guard
• hwmon: fix a NULL vs IS_ERR_OR_NULL() check in xgene_hwmon_probe()
• llc: do not use skb_get() before dev_queue_xmit() {CVE-2025-21925}
• hwmon: (ad7314) Validate leading zero bits and return error
• hwmon: (ntc_thermistor) Fix the ncpXXxh103 sensor table
• hwmon: (pmbus) Initialise page count in pmbus_identify()
• caif_virtio: fix wrong pointer check in cfv_probe() {CVE-2025-21904}
• net: gso: fix ownership in __udp_gso_segment {CVE-2025-21926}
• HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() {CVE-2025-21928}
• HID: google: fix unused variable warning under !CONFIG_ACPI
• wifi: iwlwifi: limit printed string from FW file {CVE-2025-21905}
• mm/page_alloc: fix uninitialized variable
• rapidio: fix an API misues when rio_add_net() fails {CVE-2025-21934}
• rapidio: add check for rio_add_net() in rio_scan_alloc_net()
• wifi: nl80211: reject cooked mode if it is set along with other flags {CVE-2025-21909}
• wifi: cfg80211: regulatory: improve invalid hints checking {CVE-2025-21910}
• x86/cpu: Properly parse CPUID leaf 0x2 TLB descriptor 0x63
• x86/cpu: Validate CPUID leaf 0x2 EDX output
• x86/cacheinfo: Validate CPUID leaf 0x2 EDX output
• platform/x86: thinkpad_acpi: Add battery quirk for ThinkPad X131e
• drm/radeon: Fix rs400_gpu_init for ATI mobility radeon Xpress 200M
• ALSA: hda/realtek: update ALC222 depop optimize
• ALSA: hda: intel: Add Dell ALC3271 to power_save denylist
• HID: appleir: Fix potential NULL dereference at raw event handle {CVE-2025-21948}
• Revert "of: reserved-memory: Fix using wrong number of cells to get property 'alignment'"
• drm/amdgpu: disable BAR resize on Dell G5 SE
• drm/amdgpu: Check extended configuration space register when system uses large bar
• drm/amdgpu: skip BAR resizing if the bios already…

• sctp: fix err_chunk memory leaks in INIT handling {CVE-2026-72413}
• ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() {CVE-2026-97455}
• ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() {CVE-2026-97445}
• Bluetooth: L2CAP: validate connectionless PSM length {CVE-2026-97408}
• wifi: libipw: fix key index receive bound checks {CVE-2026-93803}
• netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() {CVE-2026-98077}
• configfs: unhash the dentry before dropping the item in rmdir {CVE-2026-97949}
• reboot: fix cad_pid use-after-free race {CVE-2026-97938}
• ALSA: us122l: Prevent write upgrades for read mappings {CVE-2026-97931}
• net: usb: pegasus: don't rely on id table pointer arithmetic {CVE-2026-97540}
• usb: xusbatm: don't rely on id table pointer arithmetic {CVE-2026-97539}
• scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown {CVE-2026-97536}
• xfrm: hold net_device reference under RCU in bundle creation {CVE-2026-98364}
• wifi: libipw: reject too-short beacon and probe responses {CVE-2026-98349}
• wifi: libipw: reject too-short association responses {CVE-2026-98348}
• net: lock the socket in sock_gettstamp() {CVE-2026-98276}
• ALSA: core: Fix potential UAF after asynchronous card release {CVE-2026-98266}
• wifi: libertas_tf: fix UAF in lbtf_free_adapter() {CVE-2026-98194}
• wifi: libertas_tf: fix use-after-free in lbtf_free_adapter() {CVE-2026-72070}
• netfilter: bridge: make ebt_snat ARP rewrite writable {CVE-2026-53266}
• ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data {CVE-2026-74388}
• PCI: Fix UAF when probe runs concurrent to dyn ID removal {CVE-2026-90421}
• sunrpc: route to a populated pool in svc_pool_for_cpu() {CVE-2026-89549}
• nfsd: validate symlink target length in NFSv4 CREATE {CVE-2026-89699}
• smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2() {CVE-2026-89633}
• KVM: SVM: Bump asid_generation on CPU online to avoid ASID collision after hotplug {CVE-2026-68093}
• inet: frags: strip GSO state from fragments before reassembly {CVE-2026-80590}
• misc: sgi-gru: remove interrupt-context page-table walks {CVE-2026-90383}
• slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() {CVE-2026-90057}
• slip: fix use-after-free in sl_sync() {CVE-2026-81001}
• xfs: bounds-check buffer log item's dirty bitmap {CVE-2026-80536}
• nfsd: gate nfs3 setacl by argp->mask {CVE-2026-89671}
• SUNRPC: svcauth_gss: enforce krb5 token minimum length {CVE-2026-89550}
• ALSA: mtpav: shut down output timer before card teardown {CVE-2026-90116}
• char: tlclk: fix use-after-free in tlclk_cleanup() {CVE-2026-80622}
• net/atm: fix slab-out-of-bounds read in vcc_setsockopt() {CVE-2026-74689}
• sctp: keep chunk->transport in step with the list it is queued on {CVE-2026-74588}
• ALSA: usx2y: bound the hwdep mmap fault offset {CVE-2026-74641}
• scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer {CVE-2026-74556}
• sctp: add INIT verification after cookie unpacking {CVE-2026-72398}
• sctp: validate embedded address parameter length {CVE-2026-74287}
• configfs_lookup(): don't leave ->s_dentry dangling on failure {CVE-2026-74359}
• ALSA: seq: midi: Serialize output teardown with event_input {CVE-2026-74387}
• ipv6: mcast: Fix potential UAF in MLD delayed work {CVE-2026-72322}
• ipv6: prevent in6_dev_get() from resurrecting inet6_dev {CVE-2026-74630}
• USB: serial: io_edgeport: cap received transmit credits {CVE-2026-68365}
• sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid {CVE-2026-68320}
• net/sched: fix packet loop on netem when duplicate is on {CVE-2026-63983}
• fbdev: fix use-after-free in store_modes() {CVE-2026-63826}
• ipv6: exthdrs: refresh nh after handling HAO option {CVE-2026-63922}
• Bluetooth: btusb: fix use-after-free on registration failure {CVE-2026-64471}
• Squashfs: check block offset is not negative {CVE-2026-90203}
• ALSA: usb-audio: fix OOB write in…

• sctp: fix err_chunk memory leaks in INIT handling {CVE-2026-72413}
• ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() {CVE-2026-97455}
• ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() {CVE-2026-97445}
• Bluetooth: L2CAP: validate connectionless PSM length {CVE-2026-97408}
• wifi: libipw: fix key index receive bound checks {CVE-2026-93803}
• netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() {CVE-2026-98077}
• configfs: unhash the dentry before dropping the item in rmdir {CVE-2026-97949}
• reboot: fix cad_pid use-after-free race {CVE-2026-97938}
• ALSA: us122l: Prevent write upgrades for read mappings {CVE-2026-97931}
• net: usb: pegasus: don't rely on id table pointer arithmetic {CVE-2026-97540}
• usb: xusbatm: don't rely on id table pointer arithmetic {CVE-2026-97539}
• scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown {CVE-2026-97536}
• xfrm: hold net_device reference under RCU in bundle creation {CVE-2026-98364}
• wifi: libipw: reject too-short beacon and probe responses {CVE-2026-98349}
• wifi: libipw: reject too-short association responses {CVE-2026-98348}
• net: lock the socket in sock_gettstamp() {CVE-2026-98276}
• ALSA: core: Fix potential UAF after asynchronous card release {CVE-2026-98266}
• wifi: libertas_tf: fix UAF in lbtf_free_adapter() {CVE-2026-98194}
• wifi: libertas_tf: fix use-after-free in lbtf_free_adapter() {CVE-2026-72070}
• netfilter: bridge: make ebt_snat ARP rewrite writable {CVE-2026-53266}
• ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data {CVE-2026-74388}
• PCI: Fix UAF when probe runs concurrent to dyn ID removal {CVE-2026-90421}
• sunrpc: route to a populated pool in svc_pool_for_cpu() {CVE-2026-89549}
• nfsd: validate symlink target length in NFSv4 CREATE {CVE-2026-89699}
• smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2() {CVE-2026-89633}
• KVM: SVM: Bump asid_generation on CPU online to avoid ASID collision after hotplug {CVE-2026-68093}
• inet: frags: strip GSO state from fragments before reassembly {CVE-2026-80590}
• misc: sgi-gru: remove interrupt-context page-table walks {CVE-2026-90383}
• slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() {CVE-2026-90057}
• slip: fix use-after-free in sl_sync() {CVE-2026-81001}
• xfs: bounds-check buffer log item's dirty bitmap {CVE-2026-80536}
• nfsd: gate nfs3 setacl by argp->mask {CVE-2026-89671}
• SUNRPC: svcauth_gss: enforce krb5 token minimum length {CVE-2026-89550}
• ALSA: mtpav: shut down output timer before card teardown {CVE-2026-90116}
• char: tlclk: fix use-after-free in tlclk_cleanup() {CVE-2026-80622}
• net/atm: fix slab-out-of-bounds read in vcc_setsockopt() {CVE-2026-74689}
• sctp: keep chunk->transport in step with the list it is queued on {CVE-2026-74588}
• ALSA: usx2y: bound the hwdep mmap fault offset {CVE-2026-74641}
• scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer {CVE-2026-74556}
• sctp: add INIT verification after cookie unpacking {CVE-2026-72398}
• sctp: validate embedded address parameter length {CVE-2026-74287}
• configfs_lookup(): don't leave ->s_dentry dangling on failure {CVE-2026-74359}
• ALSA: seq: midi: Serialize output teardown with event_input {CVE-2026-74387}
• ipv6: mcast: Fix potential UAF in MLD delayed work {CVE-2026-72322}
• ipv6: prevent in6_dev_get() from resurrecting inet6_dev {CVE-2026-74630}
• USB: serial: io_edgeport: cap received transmit credits {CVE-2026-68365}
• sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid {CVE-2026-68320}
• net/sched: fix packet loop on netem when duplicate is on {CVE-2026-63983}
• fbdev: fix use-after-free in store_modes() {CVE-2026-63826}
• ipv6: exthdrs: refresh nh after handling HAO option {CVE-2026-63922}
• Bluetooth: btusb: fix use-after-free on registration failure {CVE-2026-64471}
• Squashfs: check block offset is not negative {CVE-2026-90203}
• ALSA: usb-audio: fix OOB write in…

It was discovered that the watch_queue event notification system contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service or escalate their privileges.)(CVE-2022-0995)

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in cifs_debug_files_proc_show() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF.)(CVE-2024-26928)

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_is_valid_lease_break() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF.)(CVE-2024-35864)

In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero- initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.)(CVE-2024-50302)

In the Linux kernel, the following vulnerability has been resolved: media: dvbdev: prevent the risk of out of memory access The dvbdev contains a static variable used to store dvb minors. The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set or not. When not set, dvb_register_device() won't check for boundaries, as it will rely that a previous call to dvb_register_adapter() would already be enforcing it. On a similar way, dvb_device_open() uses the assumption that the register functions already did the needed checks. This can be fragile if some device ends using different calls. This also generate warnings on static check analysers like Coverity. So, add explicit guards to prevent potential risk of OOM issues.)(CVE-2024-53063)

In the Linux kernel, the following vulnerability has been resolved: jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree When the value of lp is 0 at the beginning of the for loop, it will become negative in the next assignment and we should bail out.)(CVE-2024-56595)

In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: Fix UAF in blkcg_unpin_online() blkcg_unpin_online() walks up the blkcg hierarchy putting the online pin. To walk up, it uses blkcg_parent(blkcg) but it was calling that after blkcg_destroy_blkgs(blkcg) which could free the blkcg, leading to the following UAF: ================================================================== BUG: KASAN: slab-use-after-free in blkcg_unpin_online+0x15a/0x270 Read of size 8 at addr ffff8881057678c0 by task kworker/9:1/117 CPU: 9 UID: 0 PID: 117 Comm: kworker/9:1 Not tainted 6.13.0-rc1-work-00182-gb8f52214c61a-dirty #48 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 02/02/2022 Workqueue: cgwb_release cgwb_release_workfn Call Trace: <TASK> dump_stack_lvl+0x27/0x80 print_report+0x151/0x710 kasan_report+0xc0/0x100 blkcg_unpin_online+0x15a/0x270 cgwb_release_workfn+0x194/0x480 process_scheduled_works+0x71b/0xe20 worker_thread+0x82a/0xbd0 kthread+0x242/0x2c0 ret_from_fork+0x33/0x70 ret_from_fork_asm+0x1a/0x30 </TASK> ... Freed by task 1944: kasan_save_track+0x2b/0x70 kasan_save_free_info+0x3c/0x50 __kasan_slab_free+0x33/0x50 kfree+0x10c/0x330 css_free_rwork_fn+0xe6/0xb30 process_scheduled_works+0x71b/0xe20 worker_thread+0x82a/0xbd0 kthread+0x242/0x2c0 ret_from_fork+0x33/0x70 ret_from_fork_asm+0x1a/0x30 Note that the UAF is not easy to trigger as the free path is indirected behind a couple RCU grace periods and a work item execution. I could only trigger it with artifical msleep() injected in blkcg_unpin_online(). Fix it by reading the parent pointer before destroying the blkcg's blkg's.)(CVE-2024-56672)

In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() While receiving an MST up request message from one thread in drm_dp_mst_handle_up_req(), the MST topology could be removed from another thread via…

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix use-after-free due to delegation race A delegation break could arrive as soon as we've called vfs_setlease. A delegation break runs a callback which immediately (in nfsd4_cb_recall_prepare) adds the delegation to del_recall_lru. If we then exit nfs4_set_delegation without hashing the delegation, it will be freed as soon as the callback is done with it, without ever being removed from del_recall_lru. Symptoms show up later as use-after-free or list corruption warnings, usually in the laundromat thread. I suspect aba2072f4523 'nfsd: grant read delegations to clients holding writes' made this bug easier to hit, but I looked as far back as v3.0 and it looks to me it already had the same problem. So I'm not sure where the bug was introduced; it may have been there from the beginning.)(CVE-2021-47506)

Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges.)(CVE-2022-0995)

In the Linux kernel, the following vulnerability has been resolved: net: atlantic: eliminate double free in error handling logic Driver has a logic leak in ring data allocation/free, where aq_ring_free could be called multiple times on same ring, if system is under stress and got memory allocation error. Ring pointer was used as an indicator of failure, but this is not correct since only ring data is allocated/deallocated. Ring itself is an array member. Changing ring allocation functions to return error code directly. This simplifies error handling and eliminates aq_ring_free on higher layer.)(CVE-2023-52664)

In the Linux kernel, the following vulnerability has been resolved: ceph: prevent use-after-free in encode_cap_msg() In fs/ceph/caps.c, in encode_cap_msg(), 'use after free' error was caught by KASAN at this line - 'ceph_buffer_get(arg->xattr_buf);'. This implies before the refcount could be increment here, it was freed. In same file, in 'handle_cap_grant()' refcount is decremented by this line - 'ceph_buffer_put(ci->i_xattrs.blob);'. It appears that a race occurred and resource was freed by the latter line before the former line could increment it. encode_cap_msg() is called by __send_cap() and __send_cap() is called by ceph_check_caps() after calling __prep_cap(). __prep_cap() is where arg->xattr_buf is assigned to ci->i_xattrs.blob. This is the spot where the refcount must be increased to prevent 'use after free' error.)(CVE-2024-26689)

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_is_valid_lease_break() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF.)(CVE-2024-35864)

In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero- initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.)(CVE-2024-50302)

In the Linux kernel, the following vulnerability has been resolved: media: dvbdev: prevent the risk of out of memory access The dvbdev contains a static variable used to store dvb minors. The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set or not. When not set, dvb_register_device() won't check for boundaries, as it will rely that a previous call to dvb_register_adapter() would already be enforcing it. On a similar way, dvb_device_open() uses the assumption that the register functions already did the needed checks. This can be fragile if some device ends using different calls. This also generate warnings on static check analysers like Coverity. So, add explicit guards to prevent potential risk of OOM issues.)(CVE-2024-53063)

In the Linux kernel, the following vulnerability has been…