Affected: Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts

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

xsk: fix refcount underflow in error path

Fix a refcount underflow problem reported by syzbot that can happen when a system is running out of memory. If xp_alloc_tx_descs() fails, and it can only fail due to not having enough memory, then the error path is triggered. In this error path, the refcount of the pool is decremented as it has incremented before. However, the reference to the pool in the socket was not nulled. This means that when the socket is closed later, the socket teardown logic will think that there is a pool attached to the socket and try to decrease the refcount again, leading to a refcount underflow.

I chose this fix as it involved adding just a single line. Another option would have been to move xp_get_pool() and the assignment of xs->pool to after the if-statement and using xs_umem->pool instead of xs->pool in the whole if-statement resulting in somewhat simpler code, but this would have led to much more churn in the code base perhaps making it harder to backport.

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

xsk: fix refcount underflow in error path

Fix a refcount underflow problem reported by syzbot that can happen when a system is running out of memory. If xp_alloc_tx_descs() fails, and it can only fail due to not having enough memory, then the error path is triggered. In this error path, the refcount of the pool is decremented as it has incremented before. However, the reference to the pool in the socket was not nulled. This means that when the socket is closed later, the socket teardown logic will think that there is a pool attached to the socket and try to decrease the refcount again, leading to a refcount underflow.

I chose this fix as it involved adding just a single line. Another option would have been to move xp_get_pool() and the assignment of xs->pool to after the if-statement and using xs_umem->pool instead of xs->pool in the whole if-statement resulting in somewhat simpler code, but this would have led to much more churn in the code base perhaps making it harder to backport.

kernel: OOB writes in parse_hid_report_descriptor in drivers/input/tablet/gtco.c kernel: out of bounds read in drivers/media/usb/dvb-usb/technisat-usb2.c kernel: use-after-free in read in vt_do_kdgkb_ioctl kernel: a race out-of-bound read in vt kernel: improper input validation may lead to privilege escalation kernel: Linux ebpf logic vulnerability leads to critical memory read and write gaining root privileges kernel: use-after-free in l1oip timer handlers kernel: local privileges escalation in kernel/bpf/verifier.c kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: highmem: fix checks in __kmap_local_sched_{in,out} kernel: mm/slub: add missing TID updates on slab deactivation kernel: VMCI: Use threaded irqs instead of tasklets kernel: ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init() kernel: tty: n_gsm: add sanity check for gsm->receive in gsm_receive_buf() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted kernel: usb: host: Fix refcount leak in ehci_hcd_ppc_of_probe kernel: media: dvbdev: adopts refcnt to avoid UAF kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value kernel: ext4: fix null-ptr-deref in ext4_write_info kernel: ext4: init quota for 'old.inode' in 'ext4_rename' kern…

Affected: Rocky Linux:8: kernel

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

Security Fix(es):

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.

Additional Changes:

For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.

Security update for the Linux Kernel

Affected: Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 108 more

In the Linux kernel, the following vulnerability has been resolved: xsk: fix refcount underflow in error path Fix a refcount underflow problem reported by syzbot that can happen when a system is running out of memory. If xp_alloc_tx_descs() fails, and it can only fail due to not having enough memory, then the error path is triggered. In this error path, the refcount of the pool is decremented as it has incremented before. However, the reference to the pool in the socket was not nulled. This means that when the socket is closed later, the socket teardown logic will think that there is a pool attached to the socket and try to decrease the refcount again, leading to a refcount underflow. I chose this fix as it involved adding just a single line. Another option would have been to move xp_get_pool() and the assignment of xs->pool to after the if-statement and using xs_umem->pool instead of xs->pool in the whole if-statement resulting in somewhat simpler code, but this would have led to much more churn in the code base perhaps making it harder to backport.

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff oder andere, nicht näher spezifizierte Angriffe durchzuführen.