CVE-2025-22004

In the Linux kernel, the following vulnerability has been resolved: net: atm: fix use after free in lec_send() The ->send() operation frees skb so save the length before calling ->send() to avoid a use after free.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context

If a driver calls can_get_echo_skb() during a hardware IRQ (which is often, but not always, the case), the 'WARN_ON(in_irq)' in net/core/skbuff.c#skb_release_head_state() might be triggered, under network congestion circumstances, together with the potential risk of a NULL pointer dereference.

The root cause of this issue is the call to kfree_skb() instead of dev_kfree_skb_irq() in net/core/dev.c#enqueue_to_backlog().

This patch prevents the skb to be freed within the call to netif_rx() by incrementing its reference count with skb_get(). The skb is finally freed by one of the in-irq-context safe functions: dev_consume_skb_any() or dev_kfree_skb_any(). The "any" version is used because some drivers might call can_get_echo_skb() in a normal context.

The reason for this issue to occur is that initially, in the core network stack, loopback skb were not supposed to be received in hardware IRQ context. The CAN stack is an exeption.

This bug was previously reported back in 2017 in [1] but the proposed patch never got accepted.

While [1] directly modifies net/core/dev.c, we try to propose here a smoother modification local to CAN network stack (the assumption behind is that only CAN devices are affected by this issue).

[1] http://lore.kernel.org/r/[email protected](CVE-2020-36789)

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

video: fbdev: cirrusfb: check pixclock to avoid divide by zero

Do a sanity check on pixclock value to avoid divide by zero.

If the pixclock value is zero, the cirrusfb driver will round up pixclock to get the derived frequency as close to maxclock as possible.

Syzkaller reported a divide error in cirrusfb_check_pixclock.

divide error: 0000 [#1] SMP KASAN PTI CPU: 0 PID: 14938 Comm: cirrusfb_test Not tainted 5.15.0-rc6 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2 RIP: 0010:cirrusfb_check_var+0x6f1/0x1260

Call Trace: fb_set_var+0x398/0xf90 do_fb_ioctl+0x4b8/0x6f0 fb_ioctl+0xeb/0x130 __x64_sys_ioctl+0x19d/0x220 do_syscall_64+0x3a/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae(CVE-2021-47641)

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

can: dev: can_restart: fix use after free bug

After calling netif_rx_ni(skb), dereferencing skb is unsafe. Especially, the can_frame cf which aliases skb memory is accessed after the netif_rx_ni() in: stats->rx_bytes += cf->len;

Reordering the lines solves the issue.(CVE-2021-47668)

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

can: peak_usb: fix use after free bugs

After calling peak_usb_netif_rx_ni(skb), dereferencing skb is unsafe. Especially, the can_frame cf which aliases skb memory is accessed after the peak_usb_netif_rx_ni().

Reordering the lines solves the issue.(CVE-2021-47670)

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

qede: confirm skb is allocated before using

qede_build_skb() assumes build_skb() always works and goes straight to skb_reserve(). However, build_skb() can fail under memory pressure. This results in a kernel panic because the skb to reserve is NULL.

Add a check in case build_skb() failed to allocate and return NULL.

The NULL return is handled correctly in callers to qede_build_skb().(CVE-2022-49084)

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

net: openvswitch: fix leak of nested actions

While parsing user-provided actions, openvswitch module may dynamically allocate memory and store pointers in the internal copy of the actions. So this memory has to be freed while destroying the actions.

Currently there are only two such actions: ct() and set(). However, there are many actions that can hold nested lists…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

bpf: consider that tail calls invalidate packet pointers

Tail-called programs could execute any of the helpers that invalidate packet pointers. Hence, conservatively assume that each tail call invalidates packet pointers.

Making the change in bpf_helper_changes_pkt_data() automatically makes use of check_cfg() logic that computes 'changes_pkt_data' effect for global sub-programs, such that the following program could be rejected:

int tail_call(struct __sk_buff *sk)
{
	bpf_tail_call_static(sk, &jmp_table, 0);
	return 0;
}

SEC("tc")
int not_safe(struct __sk_buff *sk)
{
	int *p = (void *)(long)sk->data;
	... make p valid ...
	tail_call(sk);
	*p = 42; /* this is unsafe */
	...
}

The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that can invalidate packet pointers. Otherwise, it can't be freplaced with tailcall_freplace.c:entry_freplace() that does a tail call.(CVE-2024-58237)

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

RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]"

The Call Trace is as below: " <TASK> ? show_regs.cold+0x1a/0x1f ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __warn+0x84/0xd0 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? report_bug+0x105/0x180 ? handle_bug+0x46/0x80 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __rxe_cleanup+0x124/0x170 [rdma_rxe] rxe_destroy_qp.cold+0x24/0x29 [rdma_rxe] ib_destroy_qp_user+0x118/0x190 [ib_core] rdma_destroy_qp.cold+0x43/0x5e [rdma_cm] rtrs_cq_qp_destroy.cold+0x1d/0x2b [rtrs_core] rtrs_srv_close_work.cold+0x1b/0x31 [rtrs_server] process_one_work+0x21d/0x3f0 worker_thread+0x4a/0x3c0 ? process_one_work+0x3f0/0x3f0 kthread+0xf0/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> " When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly.

Compared with other rdma drivers, a bigger timeout is used.(CVE-2025-21829)

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

net: enetc: VFs do not support HWTSTAMP_TX_ONESTEP_SYNC

Actually ENETC VFs do not support HWTSTAMP_TX_ONESTEP_SYNC because only ENETC PF can access PMa_SINGLE_STEP registers. And there will be a crash if VFs are used to test one-step timestamp, the crash log as follows.

[ 129.110909] Unable to handle kernel paging request at virtual address 00000000000080c0 [ 129.287769] Call trace: [ 129.290219] enetc_port_mac_wr+0x30/0xec (P) [ 129.294504] enetc_start_xmit+0xda4/0xe74 [ 129.298525] enetc_xmit+0x70/0xec [ 129.301848] dev_hard_start_xmit+0x98/0x118(CVE-2025-21894)

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

caif_virtio: fix wrong pointer check in cfv_probe()

del_vqs() frees virtqueues, therefore cfv->vq_tx pointer should be checked for NULL before calling it, not cfv->vdev. Also the current implementation is redundant because the pointer cfv->vdev is dereferenced before it is checked for NULL.

Fix this by checking cfv->vq_tx for NULL instead of cfv->vdev before calling del_vqs().(CVE-2025-21904)

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

eth: bnxt: do not update checksum in bnxt_xdp_build_skb()

The bnxt_rx_pkt() updates ip_summed value at the end if checksum offload is enabled. When the XDP-MB program is attached and it returns XDP_PASS, the bnxt_xdp_build_skb() is called to update skb_shared_info. The main purpose of bnxt_xdp_build_skb() is to update skb_shared_info, but it updates ip_summed value too if checksum offload is enabled. This is actually duplicate work.

When…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

bpf: consider that tail calls invalidate packet pointers

Tail-called programs could execute any of the helpers that invalidate packet pointers. Hence, conservatively assume that each tail call invalidates packet pointers.

Making the change in bpf_helper_changes_pkt_data() automatically makes use of check_cfg() logic that computes 'changes_pkt_data' effect for global sub-programs, such that the following program could be rejected:

int tail_call(struct __sk_buff *sk)
{
	bpf_tail_call_static(sk, &jmp_table, 0);
	return 0;
}

SEC("tc")
int not_safe(struct __sk_buff *sk)
{
	int *p = (void *)(long)sk->data;
	... make p valid ...
	tail_call(sk);
	*p = 42; /* this is unsafe */
	...
}

The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that can invalidate packet pointers. Otherwise, it can't be freplaced with tailcall_freplace.c:entry_freplace() that does a tail call.(CVE-2024-58237)

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

netem: Update sch->q.qlen before qdisc_tree_reduce_backlog()

qdisc_tree_reduce_backlog() notifies parent qdisc only if child qdisc becomes empty, therefore we need to reduce the backlog of the child qdisc before calling it. Otherwise it would miss the opportunity to call cops->qlen_notify(), in the case of DRR, it resulted in UAF since DRR uses ->qlen_notify() to maintain its active list.(CVE-2025-21703)

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

RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]"

The Call Trace is as below: " <TASK> ? show_regs.cold+0x1a/0x1f ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __warn+0x84/0xd0 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? report_bug+0x105/0x180 ? handle_bug+0x46/0x80 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __rxe_cleanup+0x124/0x170 [rdma_rxe] rxe_destroy_qp.cold+0x24/0x29 [rdma_rxe] ib_destroy_qp_user+0x118/0x190 [ib_core] rdma_destroy_qp.cold+0x43/0x5e [rdma_cm] rtrs_cq_qp_destroy.cold+0x1d/0x2b [rtrs_core] rtrs_srv_close_work.cold+0x1b/0x31 [rtrs_server] process_one_work+0x21d/0x3f0 worker_thread+0x4a/0x3c0 ? process_one_work+0x3f0/0x3f0 kthread+0xf0/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> " When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly.

Compared with other rdma drivers, a bigger timeout is used.(CVE-2025-21829)

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

net: enetc: VFs do not support HWTSTAMP_TX_ONESTEP_SYNC

Actually ENETC VFs do not support HWTSTAMP_TX_ONESTEP_SYNC because only ENETC PF can access PMa_SINGLE_STEP registers. And there will be a crash if VFs are used to test one-step timestamp, the crash log as follows.

[ 129.110909] Unable to handle kernel paging request at virtual address 00000000000080c0 [ 129.287769] Call trace: [ 129.290219] enetc_port_mac_wr+0x30/0xec (P) [ 129.294504] enetc_start_xmit+0xda4/0xe74 [ 129.298525] enetc_xmit+0x70/0xec [ 129.301848] dev_hard_start_xmit+0x98/0x118(CVE-2025-21894)

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

caif_virtio: fix wrong pointer check in cfv_probe()

del_vqs() frees virtqueues, therefore cfv->vq_tx pointer should be checked for NULL before calling it, not cfv->vdev. Also the current implementation is redundant because the pointer cfv->vdev is dereferenced before it is checked for NULL.

Fix this by checking cfv->vq_tx for NULL instead of cfv->vdev before calling del_vqs().(CVE-2025-21904)

In the Linux kernel, the…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

bpf: consider that tail calls invalidate packet pointers

Tail-called programs could execute any of the helpers that invalidate packet pointers. Hence, conservatively assume that each tail call invalidates packet pointers.

Making the change in bpf_helper_changes_pkt_data() automatically makes use of check_cfg() logic that computes 'changes_pkt_data' effect for global sub-programs, such that the following program could be rejected:

int tail_call(struct __sk_buff *sk)
{
	bpf_tail_call_static(sk, &jmp_table, 0);
	return 0;
}

SEC("tc")
int not_safe(struct __sk_buff *sk)
{
	int *p = (void *)(long)sk->data;
	... make p valid ...
	tail_call(sk);
	*p = 42; /* this is unsafe */
	...
}

The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that can invalidate packet pointers. Otherwise, it can't be freplaced with tailcall_freplace.c:entry_freplace() that does a tail call.(CVE-2024-58237)

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

eth: bnxt: do not update checksum in bnxt_xdp_build_skb()

The bnxt_rx_pkt() updates ip_summed value at the end if checksum offload is enabled. When the XDP-MB program is attached and it returns XDP_PASS, the bnxt_xdp_build_skb() is called to update skb_shared_info. The main purpose of bnxt_xdp_build_skb() is to update skb_shared_info, but it updates ip_summed value too if checksum offload is enabled. This is actually duplicate work.

When the bnxt_rx_pkt() updates ip_summed value, it checks if ip_summed is CHECKSUM_NONE or not. It means that ip_summed should be CHECKSUM_NONE at this moment. But ip_summed may already be updated to CHECKSUM_UNNECESSARY in the XDP-MB-PASS path. So the by skb_checksum_none_assert() WARNS about it.

This is duplicate work and updating ip_summed in the bnxt_xdp_build_skb() is not needed.

Splat looks like: WARNING: CPU: 3 PID: 5782 at ./include/linux/skbuff.h:5155 bnxt_rx_pkt+0x479b/0x7610 [bnxt_en] Modules linked in: bnxt_re bnxt_en rdma_ucm rdma_cm iw_cm ib_cm ib_uverbs veth xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_] CPU: 3 UID: 0 PID: 5782 Comm: socat Tainted: G W 6.14.0-rc4+ #27 Tainted: [W]=WARN Hardware name: ASUS System Product Name/PRIME Z690-P D4, BIOS 0603 11/01/2021 RIP: 0010:bnxt_rx_pkt+0x479b/0x7610 [bnxt_en] Code: 54 24 0c 4c 89 f1 4c 89 ff c1 ea 1f ff d3 0f 1f 00 49 89 c6 48 85 c0 0f 84 4c e5 ff ff 48 89 c7 e8 ca 3d a0 c8 e9 8f f4 ff ff <0f> 0b f RSP: 0018:ffff88881ba09928 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 00000000c7590303 RCX: 0000000000000000 RDX: 1ffff1104e7d1610 RSI: 0000000000000001 RDI: ffff8881c91300b8 RBP: ffff88881ba09b28 R08: ffff888273e8b0d0 R09: ffff888273e8b070 R10: ffff888273e8b010 R11: ffff888278b0f000 R12: ffff888273e8b080 R13: ffff8881c9130e00 R14: ffff8881505d3800 R15: ffff888273e8b000 FS: 00007f5a2e7be080(0000) GS:ffff88881ba00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fff2e708ff8 CR3: 000000013e3b0000 CR4: 00000000007506f0 PKRU: 55555554 Call Trace: <IRQ> ? __warn+0xcd/0x2f0 ? bnxt_rx_pkt+0x479b/0x7610 ? report_bug+0x326/0x3c0 ? handle_bug+0x53/0xa0 ? exc_invalid_op+0x14/0x50 ? asm_exc_invalid_op+0x16/0x20 ? bnxt_rx_pkt+0x479b/0x7610 ? bnxt_rx_pkt+0x3e41/0x7610 ? __pfx_bnxt_rx_pkt+0x10/0x10 ? napi_complete_done+0x2cf/0x7d0 __bnxt_poll_work+0x4e8/0x1220 ? __pfx___bnxt_poll_work+0x10/0x10 ? __pfx_mark_lock.part.0+0x10/0x10 bnxt_poll_p5+0x36a/0xfa0 ? __pfx_bnxt_poll_p5+0x10/0x10 __napi_poll.constprop.0+0xa0/0x440 net_rx_action+0x899/0xd00 ...

Following ping.py patch adds xdp-mb-pass case. so ping.py is going to be able to reproduce this issue.(CVE-2025-21960)

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

eth: bnxt: fix truesize for…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

vlan: enforce underlying device type

Currently, VLAN devices can be created on top of non-ethernet devices.

Besides the fact that it doesn't make much sense, this also causes a bug which leaks the address of a kernel function to usermode.

When creating a VLAN device, we initialize GARP (garp_init_applicant) and MRP (mrp_init_applicant) for the underlying device.

As part of the initialization process, we add the multicast address of each applicant to the underlying device, by calling dev_mc_add.

__dev_mc_add uses dev->addr_len to determine the length of the new multicast address.

This causes an out-of-bounds read if dev->addr_len is greater than 6, since the multicast addresses provided by GARP and MRP are only 6 bytes long.

This behaviour can be reproduced using the following commands:

ip tunnel add gretest mode ip6gre local ::1 remote ::2 dev lo ip l set up dev gretest ip link add link gretest name vlantest type vlan id 100

Then, the following command will display the address of garp_pdu_rcv:

ip maddr show | grep 01:80:c2:00:00:21

Fix the bug by enforcing the type of the underlying device during VLAN device initialization.(CVE-2025-21920)

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

net: gso: fix ownership in __udp_gso_segment

In __udp_gso_segment the skb destructor is removed before segmenting the skb but the socket reference is kept as-is. This is an issue if the original skb is later orphaned as we can hit the following bug:

kernel BUG at ./include/linux/skbuff.h:3312! (skb_orphan) RIP: 0010:ip_rcv_core+0x8b2/0xca0 Call Trace: ip_rcv+0xab/0x6e0 __netif_receive_skb_one_core+0x168/0x1b0 process_backlog+0x384/0x1100 __napi_poll.constprop.0+0xa1/0x370 net_rx_action+0x925/0xe50

The above can happen following a sequence of events when using OpenVSwitch, when an OVS_ACTION_ATTR_USERSPACE action precedes an OVS_ACTION_ATTR_OUTPUT action:

1. OVS_ACTION_ATTR_USERSPACE is handled (in do_execute_actions): the skb goes through queue_gso_packets and then __udp_gso_segment, where its destructor is removed.
2. The segments' data are copied and sent to userspace.
3. OVS_ACTION_ATTR_OUTPUT is handled (in do_execute_actions) and the same original skb is sent to its path.
4. If it later hits skb_orphan, we hit the bug.

Fix this by also removing the reference to the socket in __udp_gso_segment.(CVE-2025-21926)

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

net: atm: fix use after free in lec_send()

The ->send() operation frees skb so save the length before calling ->send() to avoid a use after free.(CVE-2025-22004)

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

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()

If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand().

If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail.

Add the tsk->exit_state check into run_posix_cpu_timers() to fix this.

This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.(CVE-2025-38352)

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

vlan: enforce underlying device type

Currently, VLAN devices can be created on top of non-ethernet devices.

Besides the fact that it doesn't make much sense, this also causes a bug which leaks the address of a kernel function to usermode.

When creating a VLAN device, we initialize GARP (garp_init_applicant) and MRP (mrp_init_applicant) for the underlying device.

As part of the initialization process, we add the multicast address of each applicant to the underlying device, by calling dev_mc_add.

__dev_mc_add uses dev->addr_len to determine the length of the new multicast address.

This causes an out-of-bounds read if dev->addr_len is greater than 6, since the multicast addresses provided by GARP and MRP are only 6 bytes long.

This behaviour can be reproduced using the following commands:

ip tunnel add gretest mode ip6gre local ::1 remote ::2 dev lo ip l set up dev gretest ip link add link gretest name vlantest type vlan id 100

Then, the following command will display the address of garp_pdu_rcv:

ip maddr show | grep 01:80:c2:00:00:21

Fix the bug by enforcing the type of the underlying device during VLAN device initialization.(CVE-2025-21920)

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

net: gso: fix ownership in __udp_gso_segment

In __udp_gso_segment the skb destructor is removed before segmenting the skb but the socket reference is kept as-is. This is an issue if the original skb is later orphaned as we can hit the following bug:

kernel BUG at ./include/linux/skbuff.h:3312! (skb_orphan) RIP: 0010:ip_rcv_core+0x8b2/0xca0 Call Trace: ip_rcv+0xab/0x6e0 __netif_receive_skb_one_core+0x168/0x1b0 process_backlog+0x384/0x1100 __napi_poll.constprop.0+0xa1/0x370 net_rx_action+0x925/0xe50

The above can happen following a sequence of events when using OpenVSwitch, when an OVS_ACTION_ATTR_USERSPACE action precedes an OVS_ACTION_ATTR_OUTPUT action:

1. OVS_ACTION_ATTR_USERSPACE is handled (in do_execute_actions): the skb goes through queue_gso_packets and then __udp_gso_segment, where its destructor is removed.
2. The segments' data are copied and sent to userspace.
3. OVS_ACTION_ATTR_OUTPUT is handled (in do_execute_actions) and the same original skb is sent to its path.
4. If it later hits skb_orphan, we hit the bug.

Fix this by also removing the reference to the socket in __udp_gso_segment.(CVE-2025-21926)

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

net: atm: fix use after free in lec_send()

The ->send() operation frees skb so save the length before calling ->send() to avoid a use after free.(CVE-2025-22004)

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

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()

If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand().

If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail.

Add the tsk->exit_state check into run_posix_cpu_timers() to fix this.

This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.(CVE-2025-38352)

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

Security Fix(es):

• kernel: ipv6: mcast: extend RCU protection in igmp6_send() (CVE-2025-21759)

• kernel: ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up (CVE-2025-21887)

• kernel: net: atm: fix use after free in lec_send() (CVE-2025-22004)

• kernel: udf: Fix a slab-out-of-bounds write bug in udf_find_entry() (CVE-2022-49846)

• kernel: vmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp (CVE-2025-37799)

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: cifs: potential buffer overflow in handling symlinks (CVE-2022-49058)

• kernel: media: uvcvideo: Remove dangling pointers (CVE-2024-58002)

• kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)

• kernel: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes (CVE-2025-21991)

• kernel: net: atm: fix use after free in lec_send() (CVE-2025-22004)

• kernel: ext4: fix off-by-one error in do_split (CVE-2025-23150)

• kernel: ext4: ignore xattrs past end (CVE-2025-37738)

• kernel: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() (CVE-2022-49788)

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: cifs: potential buffer overflow in handling symlinks (CVE-2022-49058)

• kernel: media: uvcvideo: Remove dangling pointers (CVE-2024-58002)

• kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)

• kernel: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes (CVE-2025-21991)

• kernel: net: atm: fix use after free in lec_send() (CVE-2025-22004)

• kernel: ext4: fix off-by-one error in do_split (CVE-2025-23150)

• kernel: ext4: ignore xattrs past end (CVE-2025-37738)

• kernel: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() (CVE-2022-49788)

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: net: atm: fix use after free in lec_send() The ->send() operation frees skb so save the length before calling ->send() to avoid a use after free.

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

Security Fix(es):

• kernel: ipv6: mcast: extend RCU protection in igmp6_send() (CVE-2025-21759)
• kernel: ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up (CVE-2025-21887)
• kernel: net: atm: fix use after free in lec_send() (CVE-2025-22004)
• kernel: udf: Fix a slab-out-of-bounds write bug in udf_find_entry() (CVE-2022-49846)
• kernel: vmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp (CVE-2025-37799)

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: cifs: potential buffer overflow in handling symlinks (CVE-2022-49058)
• kernel: media: uvcvideo: Remove dangling pointers (CVE-2024-58002)
• kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)
• kernel: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes (CVE-2025-21991)
• kernel: net: atm: fix use after free in lec_send() (CVE-2025-22004)
• kernel: ext4: fix off-by-one error in do_split (CVE-2025-23150)
• kernel: ext4: ignore xattrs past end (CVE-2025-37738)
• kernel: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() (CVE-2022-49788)

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: cifs: potential buffer overflow in handling symlinks (CVE-2022-49058)
• kernel: media: uvcvideo: Remove dangling pointers (CVE-2024-58002)
• kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)
• kernel: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes (CVE-2025-21991)
• kernel: net: atm: fix use after free in lec_send() (CVE-2025-22004)
• kernel: ext4: fix off-by-one error in do_split (CVE-2025-23150)
• kernel: ext4: ignore xattrs past end (CVE-2025-37738)
• kernel: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() (CVE-2022-49788)

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:

net: atm: fix use after free in lec_send()

The ->send() operation frees skb so save the length before calling ->send() to avoid a use after free.

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

net: atm: fix use after free in lec_send()

The ->send() operation frees skb so save the length before calling ->send() to avoid a use after free.

• Focal update: v5.4.292 upstream stable release (LP: #2109357) // CVE-url: https://ubuntu.com/security/CVE-2025-37937
  • objtool, media: dib8000: Prevent divide-by-zero in dib8000_set_dds()
• Focal update: v5.4.287 upstream stable release (LP: #2095145) // CVE-url: https://ubuntu.com/security/CVE-2024-53197
  • ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices
• CVE-url: https://ubuntu.com/security/CVE-2024-46787
  • userfaultfd: fix checks for huge PMDs
• CVE-url: https://ubuntu.com/security/CVE-2025-37798
  • sch_drr: make drr_qlen_notify() idempotent
  • sch_hfsc: make hfsc_qlen_notify() idempotent
  • sch_qfq: make qfq_qlen_notify() idempotent
  • codel: remove sch->q.qlen check before qdisc_tree_reduce_backlog()
• Focal update: v5.4.285 upstream stable release (LP: #2089233) // CVE-2024-50116 // CVE-url: https://ubuntu.com/security/CVE-2024-50116
  • nilfs2: fix kernel bug due to missing clearing of buffer delay flag
• Focal update: v5.4.285 upstream stable release (LP: #2089233) // CVE-2024-49958 // CVE-url: https://ubuntu.com/security/CVE-2024-49958
  • ocfs2: reserve space for inline xattr before attaching reflink tree
• Focal update: v5.4.286 upstream stable release (LP: #2089558) // CVE-url: https://ubuntu.com/security/CVE-2021-47195
  • spi: fix use-after-free of the add_lock mutex
• CVE-url: https://ubuntu.com/security/CVE-2021-47469
  • spi: Fix deadlock when adding SPI controllers on SPI buses
• CVE-url: https://ubuntu.com/security/CVE-2025-39735
  • jfs: fix slab-out-of-bounds read in ea_get()
• CVE-url: https://ubuntu.com/security/CVE-2025-22020
  • memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove
• CVE-url: https://ubuntu.com/security/CVE-2025-22004
  • net: atm: fix use after free in lec_send()
• CVE-url: https://ubuntu.com/security/CVE-2025-39688
  • nfsd: allow SC_STATUS_FREEABLE when searching via nfs4_lookup_stateid()
• CVE-url: https://ubuntu.com/security/CVE-2022-49892
  • ftrace: Fix use-after-free for dynamic ftrace_ops
• CVE-url: https://ubuntu.com/security/CVE-2021-47293
  • net/sched: act_skbmod: Skip non-Ethernet packets
• CVE-url: https://ubuntu.com/security/CVE-2024-50106
  • nfsd: simplify nfs4_put_deleg_lease calls
  • nfsd: factor out common delegation-destruction code
  • nfsd: Fix race to FREE_STATEID and cl_revoked
  • nfsd: don't call functions with side-effecting inside WARN_ON()
  • nfsd: remove fault injection code
  • nfsd: avoid race after unhash_delegation_locked()
  • nfsd4: don't set lock stateid's sc_type to CLOSED
  • nfsd: split sc_status out of sc_type
  • nfsd: fix race between laundromat and free_stateid
• CVE-url: https://ubuntu.com/security/CVE-2024-57982
  • xfrm: state: fix out-of-bounds read during lookup
• CVE-url: https://ubuntu.com/security/CVE-2023-52588
  • f2fs: fix to tag gcing flag on page during block migration
• Miscellaneous Ubuntu changes
  • [Config] updateconfigs for NFSD_FAULT_INJECTION

• udf: Fix a slab-out-of-bounds write bug in udf_find_entry() {CVE-2022-49846}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up {CVE-2025-21887}
• rcutorture: Fix ksoftirqd boosting timing and iteration {CVE-2022-50177}
• tty: n_gsm: add sanity check for gsm->receive in gsm_receive_buf() {CVE-2022-49940}
• selinux: Add boundary check in put_entry() {CVE-2022-50200}
• Squashfs: fix handling and sanity checking of xattr_ids count {CVE-2023-52933}
• net: atlantic: fix aq_vec index out of range error {CVE-2022-50066}
• ext4: ignore xattrs past end {CVE-2025-37738}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• sched/fair: Fix potential memory corruption in child_cfs_rq_on_list {CVE-2025-21919}
• md: fix mddev uaf while iterating all_mddevs list {CVE-2025-22126}
• ndisc: use RCU protection in ndisc_alloc_skb() {CVE-2025-21764}
• md: factor out a helper from mddev_put()
• Fix "Bluetooth: L2CAP: Fix slab-use-after-free Read in l2cap_send_cmd"
• ext4: prevent stale extent cache entries caused by concurrent get es_cache

• net: ch9200: fix uninitialised access during mii_nway_restart {CVE-2025-38086}
• idpf: fix null-ptr-deref in idpf_features_check {CVE-2025-38053}
• ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead {CVE-2022-49977}
• sched/fair: Fix potential memory corruption in child_cfs_rq_on_list {CVE-2025-21919}
• wifi: iwlwifi: limit printed string from FW file {CVE-2025-21905}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes {CVE-2025-21991}
• ext4: ignore xattrs past end {CVE-2025-37738}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• cifs: potential buffer overflow in handling symlinks {CVE-2022-49058}
• media: uvcvideo: Remove dangling pointers {CVE-2024-58002}

• net: ch9200: fix uninitialised access during mii_nway_restart {CVE-2025-38086}
• jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted {CVE-2022-50126}
• kernfs: fix potential NULL dereference in __kernfs_remove {CVE-2022-50148}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• xhci: Fix null pointer dereference in remove if xHC has only one roothub {CVE-2022-49962}
• ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead {CVE-2022-49977}
• wifi: iwlwifi: limit printed string from FW file {CVE-2025-21905}
• udmabuf: Set the DMA mask for the udmabuf device (v2) {CVE-2022-49983}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event {CVE-2022-50136}
• iavf: Fix reset error handling {CVE-2022-50053}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• ext4: ignore xattrs past end {CVE-2025-37738}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• media: uvcvideo: Remove dangling pointers {CVE-2024-58002}
• netfilter: flowtable: fix stuck flows on cleanup due to pending work {CVE-2022-50000}
• netfilter: flowtable: add function to invoke garbage collection immediately {CVE-2022-50000}

• net: ch9200: fix uninitialised access during mii_nway_restart {CVE-2025-38086}
• jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted {CVE-2022-50126}
• kernfs: fix potential NULL dereference in __kernfs_remove {CVE-2022-50148}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• xhci: Fix null pointer dereference in remove if xHC has only one roothub {CVE-2022-49962}
• ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead {CVE-2022-49977}
• wifi: iwlwifi: limit printed string from FW file {CVE-2025-21905}
• iavf: Fix reset error handling {CVE-2022-50053}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• ext4: ignore xattrs past end {CVE-2025-37738}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• media: uvcvideo: Remove dangling pointers {CVE-2024-58002}
• RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event {CVE-2022-50136}
• stmmac: intel: Add a missing clk_disable_unprepare() call in intel_eth_pci_remove() {CVE-2022-50039}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• udmabuf: Set the DMA mask for the udmabuf device (v2) {CVE-2022-49983}
• netfilter: flowtable: fix stuck flows on cleanup due to pending work {CVE-2022-50000}
• netfilter: flowtable: add function to invoke garbage collection immediately {CVE-2022-50000}
• drm/amd/display: clear optc underflow before turn off odm clock {CVE-2022-49969}

• x86/kvm: Disable kvmclock on all CPUs on shutdown {CVE-2021-47110}
• posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() {CVE-2025-38352}
• cifs: fix double free race when mount fails in cifs_get_root() {CVE-2022-48919}
• aio: mark AIO pseudo-fs noexec {CVE-2016-10044}
• cifs: potential buffer overflow in handling symlinks {CVE-2022-49058}
• NFSD: fix race between nfsd registration and exports_proc {CVE-2025-38232}
• nfsd: register pernet ops last, unregister first {CVE-2025-38232}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• net: atlantic: fix aq_vec index out of range error {CVE-2022-50066}
• do_change_type(): refuse to operate on unmounted/not ours mounts {CVE-2025-38498}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• net: atm: add lec_mutex {CVE-2025-38180}
• SUNRPC: make sure cache entry active before cache_show {CVE-2024-53174}
• scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() {CVE-2025-38399}
• scsi: target: Fix crash during SPEC_I_PT handling {CVE-2025-38399}
• mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race {CVE-2025-38085}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• ext4: avoid resizing to a partial cluster size {CVE-2022-50020}
• HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() {CVE-2025-21928}
• net/sched: Abort __tc_modify_qdisc if parent class does not exist {CVE-2025-38457}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• dlm: fix plock invalid read {CVE-2022-49407}
• net: usb: smsc75xx: Limit packet length to skb->len {CVE-2023-53125}
• scsi: libfc: Fix use after free in fc_exch_abts_resp() {CVE-2022-49114}
• crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• HID: core: ensure the allocated report buffer can contain the reserved report ID {CVE-2025-38495}
• ext4: Fix possible corruption when moving a directory {CVE-2023-53137}
• ceph: avoid putting the realm twice when decoding snaps fails {CVE-2022-49770}
• vsock/vmci: Clear the vmci transport packet properly when initializing it {CVE-2025-38403}
• HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}
• sch_hfsc: make hfsc_qlen_notify() idempotent {CVE-2025-38177}
• ext4: check dot and dotdot of dx_root before making dir indexed {CVE-2024-42305}
• ALSA: bcd2000: Fix a UAF bug on the error path of probing {CVE-2022-50229}
• dm ioctl: prevent potential spectre v1 gadget {CVE-2022-49122}
• net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}
• ACPICA: Refuse to evaluate a method if arguments are missing {CVE-2025-38386}
• media: cxusb: no longer judge rbuf when the write fails {CVE-2025-38229}
• ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init {CVE-2025-37878}
• sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() {CVE-2025-38000}
• i40e: fix MMIO write access to an invalid page in i40e_clear_hw {CVE-2025-38200}

• rds: tcp: block BH in TCP callbacks
• kexec: Improve & fix crash_exclude_mem_range() to handle overlapping ranges
• module: correctly exit module_kallsyms_on_each_symbol when fn() != 0
• module: potential uninitialized return in module_kallsyms_on_each_symbol()
• module: use RCU to synchronize find_module
• kallsyms: refactor {,module_}kallsyms_on_each_symbol
• LTS tag: v5.4.295
• scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops
• arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth() {CVE-2025-38320}
• perf: Fix sample vs do_exit() {CVE-2025-38424}
• s390/pci: Fix __pcilg_mio_inuser() inline assembly
• rtc: test: Fix invalid format specifier.
• jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() {CVE-2025-38337}
• mm/huge_memory: fix dereferencing invalid pmd migration entry {CVE-2025-37958}
• rtc: Make rtc_time64_to_tm() support dates before 1970
• rtc: Improve performance of rtc_time64_to_tm(). Add tests.
• xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create {CVE-2022-48773}
• posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() {CVE-2025-38352}
• ARM: dts: am335x-bone-common: Increase MDIO reset deassert delay to 50ms
• ARM: dts: am335x-bone-common: Increase MDIO reset deassert time
• ARM: dts: am335x-bone-common: Add GPIO PHY reset on revision C3 board
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• net: atm: add lec_mutex {CVE-2025-38323}
• calipso: Fix null-ptr-deref in calipso_req_{set,del}attr(). {CVE-2025-38181}
• tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer {CVE-2025-38184}
• tcp: fix tcp_packet_delayed() for tcp_is_non_sack_preventing_reopen() behavior
• atm: atmtcp: Free invalid length skb in atmtcp_c_send(). {CVE-2025-38185}
• mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu(). {CVE-2025-38324}
• wifi: carl9170: do not ping device which has failed to load firmware {CVE-2025-38420}
• aoe: clean device rq_list in aoedev_downdev() {CVE-2025-38326}
• hwmon: (occ) fix unaligned accesses
• drm/nouveau/bl: increase buffer size to avoid truncate warning
• erofs: remove unused trace event erofs_destroy_inode
• ALSA: hda/realtek: enable headset mic on Latitude 5420 Rugged
• ALSA: hda/intel: Add Thinkpad E15 to PM deny list
• Input: sparcspkr - avoid unannotated fall-through
• HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() {CVE-2025-38103}
• atm: Revert atm_account_tx() if copy_from_iter_full() fails. {CVE-2025-38190}
• selinux: fix selinux_xfrm_alloc_user() to set correct ctx_len
• scsi: s390: zfcp: Ensure synchronous unit_add
• scsi: storvsc: Increase the timeouts to storvsc_timeout
• jffs2: check jffs2_prealloc_raw_node_refs() result in few other places {CVE-2025-38328}
• jffs2: check that raw node were preallocated before writing summary {CVE-2025-38194}
• drivers/rapidio/rio_cm.c: prevent possible heap overwrite {CVE-2025-38090}
• powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery
• platform/x86: dell_rbu: Stop overwriting data buffer
• platform: Add Surface platform directory
• Revert "bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first"
• tee: Prevent size calculation wraparound on 32-bit kernels
• ARM: OMAP2+: Fix l4ls clk domain handling in STANDBY
• bus: fsl-mc: increase MC_CMD_COMPLETION_TIMEOUT_MS value
• watchdog: da9052_wdt: respect TWDMIN
• i40e: fix MMIO write access to an invalid page in i40e_clear_hw {CVE-2025-38200}
• sock: Correct error checking condition for (assign|release)_proto_idx()
• scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}
• vxlan: Do not treat dst cache initialization errors as fatal
• clk: rockchip: rk3036: mark ddrphy as critical
• wifi: mac80211: do not offer a mesh path if forwarding is disabled
• net: mlx4: add SOF_TIMESTAMPING_TX_SOFTWARE flag when getting ts info
• pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get()
• pinctrl: armada-37xx:…

• x86/kvm: Disable kvmclock on all CPUs on shutdown {CVE-2021-47110}
• posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() {CVE-2025-38352}
• cifs: fix double free race when mount fails in cifs_get_root() {CVE-2022-48919}
• aio: mark AIO pseudo-fs noexec {CVE-2016-10044}
• cifs: potential buffer overflow in handling symlinks {CVE-2022-49058}
• NFSD: fix race between nfsd registration and exports_proc {CVE-2025-38232}
• nfsd: register pernet ops last, unregister first {CVE-2025-38232}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• net: atlantic: fix aq_vec index out of range error {CVE-2022-50066}
• do_change_type(): refuse to operate on unmounted/not ours mounts {CVE-2025-38498}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• net: atm: add lec_mutex {CVE-2025-38180}
• SUNRPC: make sure cache entry active before cache_show {CVE-2024-53174}
• scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() {CVE-2025-38399}
• scsi: target: Fix crash during SPEC_I_PT handling {CVE-2025-38399}
• mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race {CVE-2025-38085}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• ext4: avoid resizing to a partial cluster size {CVE-2022-50020}
• HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() {CVE-2025-21928}
• net/sched: Abort __tc_modify_qdisc if parent class does not exist {CVE-2025-38457}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• dlm: fix plock invalid read {CVE-2022-49407}
• net: usb: smsc75xx: Limit packet length to skb->len {CVE-2023-53125}
• scsi: libfc: Fix use after free in fc_exch_abts_resp() {CVE-2022-49114}
• crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• HID: core: ensure the allocated report buffer can contain the reserved report ID {CVE-2025-38495}
• ext4: Fix possible corruption when moving a directory {CVE-2023-53137}
• ceph: avoid putting the realm twice when decoding snaps fails {CVE-2022-49770}
• vsock/vmci: Clear the vmci transport packet properly when initializing it {CVE-2025-38403}
• HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}
• sch_hfsc: make hfsc_qlen_notify() idempotent {CVE-2025-38177}
• ext4: check dot and dotdot of dx_root before making dir indexed {CVE-2024-42305}
• ALSA: bcd2000: Fix a UAF bug on the error path of probing {CVE-2022-50229}
• dm ioctl: prevent potential spectre v1 gadget {CVE-2022-49122}
• net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}
• ACPICA: Refuse to evaluate a method if arguments are missing {CVE-2025-38386}
• media: cxusb: no longer judge rbuf when the write fails {CVE-2025-38229}
• ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init {CVE-2025-37878}
• sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() {CVE-2025-38000}
• i40e: fix MMIO write access to an invalid page in i40e_clear_hw {CVE-2025-38200}

• fix: virtio-net: Add validation for used length {CVE-2021-47352}
• xen/netfront: don't use gnttab_query_foreign_access() for mapped status {CVE-2022-23037}
• net/sched: sch_qfq: Fix race condition on qfq_aggregate {CVE-2025-38477}
• net: fix information leakage in /proc/net/ptype {CVE-2022-48757}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• ALSA: oss: Fix PCM OSS buffer allocation overflow {CVE-2022-49292}

• fix: virtio-net: Add validation for used length {CVE-2021-47352}
• xen/netfront: don't use gnttab_query_foreign_access() for mapped status {CVE-2022-23037}
• net/sched: sch_qfq: Fix race condition on qfq_aggregate {CVE-2025-38477}
• net: fix information leakage in /proc/net/ptype {CVE-2022-48757}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• ALSA: oss: Fix PCM OSS buffer allocation overflow {CVE-2022-49292}

• CVE-2026-64375
  • proc: protect ptrace_may_access() with exec_update_lock (FD links) {CVE-2026-64375}
  • exec: Add exec_update_mutex to replace cred_guard_mutex {CVE-2026-64375}
• CVE-2026-53266
  • netfilter: bridge: make ebt_snat ARP rewrite writable {CVE-2026-53266}
• CVE-2025-39964
  • crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg {CVE-2025-39964}
• CVE-2025-38068
  • crypto: lzo - Fix compression buffer overrun {CVE-2025-38068}
• CVE-2024-56570
  • ovl: Filter invalid inodes with missing lookup function {CVE-2024-56570}
• CVE-2025-21753
  • btrfs: fix use-after-free when attempting to join an aborted transaction {CVE-2025-21753}
• CVE-2026-46116
  • xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete {CVE-2026-46116}
• CVE-2022-49811
  • drbd: use after free in drbd_create_device() {CVE-2022-49811}
• CVE-2022-49059
  • nfc: nci: add flush_workqueue to prevent uaf {CVE-2022-49059}
• CVE-2025-22004
  • net: atm: fix use after free in lec_send() {CVE-2025-22004}
• CVE-2025-21764
  • ndisc: use RCU protection in ndisc_alloc_skb() {CVE-2025-21764}
• CVE-2025-21762
  • arp: use RCU protection in arp_xmit() {CVE-2025-21762}
• CVE-2026-52934
  • batman-adv: tvlv: reject oversized TVLV packets {CVE-2026-52934}
• CVE-2026-46090
  • ALSA: aloop: Fix peer runtime UAF during format-change stop {CVE-2026-46090}
• CVE-2026-53131
  • netfilter: require Ethernet MAC header before using eth_hdr() {CVE-2026-53131}
• CVE-2026-53091
  • net: pull headers in qdisc_pkt_len_init() {CVE-2026-53091}
• CVE-2026-52986
  • netfilter: nf_conntrack_sip: don't use simple_strtoul {CVE-2026-52986}
• CVE-2025-71116
  • libceph: make decode_pool() more resilient against corrupted osdmaps {CVE-2025-71116}
• CVE-2026-43493
  • crypto: pcrypt - Fix handling of MAY_BACKLOG requests {CVE-2026-43493}
• CVE-2026-31597
  • ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY {CVE-2026-31597}
• CVE-2026-43116
  • netfilter: ctnetlink: ensure safe access to master conntrack {CVE-2026-43116}
• CVE-2026-43458
  • serial: caif: hold tty->link reference in ldisc_open and ser_release {CVE-2026-43458}
• CVE-2026-53002
  • netfilter: conntrack: remove sprintf usage {CVE-2026-53002}
• CVE-2026-46212
  • batman-adv: bla: prevent use-after-free when deleting claims {CVE-2026-46212}
• CVE-2026-31787
  • xen/privcmd: fix double free via VMA splitting {CVE-2026-31787}
• CVE-2023-53357
  • md/raid10: check slab-out-of-bounds in md_bitmap_get_counter {CVE-2023-53357}
• CVE-2026-43075
  • ocfs2: fix out-of-bounds write in ocfs2_write_end_inline {CVE-2026-43075}
• CVE-2026-43076
  • ocfs2: validate inline data i_size during inode read {CVE-2026-43076}
• CVE-2025-38464
  • tipc: Fix use-after-free in tipc_conn_close(). {CVE-2025-38464}
• CVE-2026-23269
  • apparmor: validate DFA start states are in bounds in unpack_pdb {CVE-2026-23269}
• CVE-2026-43279
  • ALSA: usb-audio: Add sanity check for OOB writes at silencing {CVE-2026-43279}
• CVE-2024-36013
  • Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect() {CVE-2024-36013}
• CVE-2026-53228
  • ipv6: sit: reload inner IPv6 header after GSO offloads {CVE-2026-53228}
• CVE-2026-45970
  • bonding: alb: fix UAF in rlb_arp_recv during bond up/down {CVE-2026-45970}
• CVE-2026-52920
  • netfilter: xt_policy: fix strict mode inbound policy matching {CVE-2026-52920}
• CVE-2026-46270
  • power: supply: rt9455: Fix use-after-free in power_supply_changed() {CVE-2026-46270}
• CVE-2026-46259
  • procfs: fix missing RCU protection when reading real_parent in do_task_stat() {CVE-2026-46259}
• CVE-2026-52998
  • netfilter: xt_osf: fix potential NULL…

Upstream kernel version 6.6.87 fixes bugs and vulnerabilities. The kmod-virtualbox and kmod-xtables-addons packages have been updated to work with this new kernel. For information about the vulnerabilities see the links.

Vanilla upstream kernel version 6.6.88 fixes bugs and vulnerabilities. For information about the vulnerabilities see the links.

Root has patched CVE-2025-22004 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.

The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

• CVE-2021-47659: drm/plane: Move range check for format_count earlier (bsc#1237839).
• CVE-2022-49044: dm integrity: fix memory corruption when tag_size is less than digest size (bsc#1237840).
• CVE-2022-49055: drm/amdkfd: Check for potential null return of kmalloc_array() (bsc#1237868).
• CVE-2022-49060: net/smc: Fix NULL pointer dereference in smc_pnet_find_ib() (bsc#1237845).
• CVE-2022-49086: net: openvswitch: fix leak of nested actions (bsc#1238037).
• CVE-2022-49111: Bluetooth: Fix use after free in hci_send_acl (bsc#1237984).
• CVE-2022-49118: scsi: hisi_sas: Free irq vectors in order for v3 HW (bsc#1237979).
• CVE-2022-49121: scsi: pm8001: Fix tag leaks on error (bsc#1237926).
• CVE-2022-49137: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj (bsc#1238155).
• CVE-2022-49175: PM: core: keep irq flags in device_pm_check_callbacks() (bsc#1238099).
• CVE-2022-49176: bfq: fix use-after-free in bfq_dispatch_request (bsc#1238097).
• CVE-2022-49179: block, bfq: do not move oom_bfqq (bsc#1238092).
• CVE-2022-49188: remoteproc: qcom_q6v5_mss: Fix some leaks in q6v5_alloc_memory_region (bsc#1238138).
• CVE-2022-49197: af_netlink: Fix shift out of bounds in group mask calculation (bsc#1238455).
• CVE-2022-49205: bpf, sockmap: Fix double uncharge the mem of sk_msg (bsc#1238335).
• CVE-2022-49232: drm/amd/display: Fix a NULL pointer dereference in amdgpu_dm_connector_add_common_modes() (bsc#1238139).
• CVE-2022-49290: mac80211: fix potential double free on mesh join (bsc#1238156).
• CVE-2022-49305: drivers: staging: rtl8192u: Fix deadlock in ieee80211_beacons_stop() (bsc#1238645).
• CVE-2022-49325: tcp: add accessors to read/set tp->snd_cwnd (bsc#1238398).
• CVE-2022-49335: drm/amdgpu/cs: make commands with 0 chunks illegal behaviour (bsc#1238377).
• CVE-2022-49351: net: altera: Fix refcount leak in altera_tse_mdio_create (bsc#1237939).
• CVE-2022-49385: driver: base: fix UAF when driver_attach failed (bsc#1237951).
• CVE-2022-49390: macsec: fix UAF bug for real_dev (bsc#1238233).
• CVE-2022-49411: bfq: Make sure bfqg for which we are queueing requests is online (bsc#1238307).
• CVE-2022-49442: drivers/base/node.c: fix compaction sysfs file leak (bsc#1238243).
• CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
• CVE-2022-49478: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init (bsc#1238000).
• CVE-2022-49489: drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm runtime resume (bsc#1238244).
• CVE-2022-49504: scsi: lpfc: Inhibit aborts if external loopback plug is inserted (bsc#1238835).
• CVE-2022-49521: scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() (bsc#1238938).
• CVE-2022-49525: media: cx25821: Fix the warning when removing the module (bsc#1238022).
• CVE-2022-49534: scsi: lpfc: Protect memory leak for NPIV ports sending PLOGI_RJT (bsc#1238893).
• CVE-2022-49535: scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI (bsc#1238937).
• CVE-2022-49536: scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock (bsc#1238838).
• CVE-2022-49537: scsi: lpfc: Fix call trace observed during I/O with CMF enabled (bsc#1238930).
• CVE-2022-49542: scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg() (bsc#1238722).
• CVE-2022-49561: netfilter: conntrack: re-fetch conntrack after insertion (bsc#1238537).
• CVE-2022-49590: igmp: Fix data-races around sysctl_igmp_llm_reports (bsc#1238844).
• CVE-2022-49658: bpf, selftests: Add verifier test case for imm=0,umin=0,umax=1 scalar (bsc#1238803).
• CVE-2022-49668: PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events (bsc#1237957).
• CVE-2022-49693: drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf (bsc#1237954).
• CVE-2022-49725: i40e: Fix call trace in setup_tx_descriptors…