CVE-2022-50550

Root has patched CVE-2022-50550 in the linux package for Root:Debian:11. Multiple fixed versions available.

Root has patched CVE-2022-50550 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.

In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on add_disk() failures When a gendisk is successfully initialized but add_disk() fails such as when a loop device has invalid number of minor device numbers specified, blkcg_init_disk() is called during init and then blkcg_exit_disk() during error handling. Unfortunately, iolatency gets initialized in the former but doesn't get cleaned up in the latter. This is because, in non-error cases, the cleanup is performed by del_gendisk() calling rq_qos_exit(), the assumption being that rq_qos policies, iolatency being one of them, can only be activated once the disk is fully registered and visible. That assumption is true for wbt and iocost, but not so for iolatency as it gets initialized before add_disk() is called. It is desirable to lazy-init rq_qos policies because they are optional features and add to hot path overhead once initialized - each IO has to walk all the registered rq_qos policies. So, we want to switch iolatency to lazy init too. However, that's a bigger change. As a fix for the immediate problem, let's just add an extra call to rq_qos_exit() in blkcg_exit_disk(). This is safe because duplicate calls to rq_qos_exit() become noop's.

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

blk-iolatency: Fix memory leak on add_disk() failures

When a gendisk is successfully initialized but add_disk() fails such as when a loop device has invalid number of minor device numbers specified, blkcg_init_disk() is called during init and then blkcg_exit_disk() during error handling. Unfortunately, iolatency gets initialized in the former but doesn't get cleaned up in the latter.

This is because, in non-error cases, the cleanup is performed by del_gendisk() calling rq_qos_exit(), the assumption being that rq_qos policies, iolatency being one of them, can only be activated once the disk is fully registered and visible. That assumption is true for wbt and iocost, but not so for iolatency as it gets initialized before add_disk() is called.

It is desirable to lazy-init rq_qos policies because they are optional features and add to hot path overhead once initialized - each IO has to walk all the registered rq_qos policies. So, we want to switch iolatency to lazy init too. However, that's a bigger change. As a fix for the immediate problem, let's just add an extra call to rq_qos_exit() in blkcg_exit_disk(). This is safe because duplicate calls to rq_qos_exit() become noop's.

• md/raid1,raid10: strip REQ_NOWAIT from member bios {CVE-2025-22125}
• md/raid1: fix data lost for writemostly rdev {CVE-2025-22125}
• md/raid1,raid10: don't handle IO error for REQ_RAHEAD and REQ_NOWAIT {CVE-2025-22125}
• md/raid1,raid10: don't ignore IO flags {CVE-2025-22125}
• net/sched: netem: fix queue limit check to include reordered packets {CVE-2026-52984}
• netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() {CVE-2025-21703}
• net/sched: netem: account for backlog updates from child qdisc {CVE-2024-56770}
• drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check {CVE-2026-89818}
• drm/amdgpu/vcn4: Avoid overflow on msg bound check {CVE-2026-46199}
• drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg {CVE-2026-46199}
• drm/amdgpu/vcn3: Avoid overflow on msg bound check {CVE-2026-46230}
• drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg {CVE-2026-46230}
• vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE {CVE-2022-48862}
• vhost: handle error while adding split ranges to iotlb {CVE-2022-48862}
• vhost: allow batching hint without size {CVE-2022-48862}
• vhost: fix hung thread due to erroneous iotlb entries {CVE-2022-48862}
• md raid: fix hang when stopping arrays with metadata through dm-raid {CVE-2026-43309}
• dm raid: use proper md_ro_state enumerators {CVE-2026-43309}
• i40e: When removing VF MAC filters, only check PF-set MAC {CVE-2024-26830}
• i40e: Fix VF MAC filter removal {CVE-2024-26830}
• i40e: Do not allow untrusted VF to remove administratively set MAC {CVE-2024-26830}
• netlink: make sure we allow at least one dump skb {CVE-2025-38465}
• netlink: avoid infinite retry looping in netlink_unicast() {CVE-2025-38465}
• netlink: Fix rmem check in netlink_broadcast_deliver(). {CVE-2025-38465}
• netlink: Fix wraparounds of sk->sk_rmem_alloc. {CVE-2025-38465}
• ipv6: fix possible infinite loop in rt6_fill_node() {CVE-2024-56703}
• ipv6: prevent infinite loop in rt6_nlmsg_size() {CVE-2024-56703}
• ipv6: Fix soft lockups in fib6_select_path under high next hop churn {CVE-2024-56703}
• qede: fix out-of-bounds check for cqe->len_list[] {CVE-2025-40252}
• net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() {CVE-2025-40252}
• scsi: lpfc: apply the HBA_SETUP dev_loss check to SLI4 only {CVE-2024-49891}
• scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths {CVE-2024-49891}
• ext4: fix string copying in parse_apply_sb_mount_options() {CVE-2025-71123}
• ext4: avoid potential buffer over-read in parse_apply_sb_mount_options() {CVE-2025-40198}
• openvswitch: vport: fix self-deadlock on release of tunnel ports {CVE-2026-31678}
• openvswitch: defer tunnel netdev_put to RCU release {CVE-2026-31678}
• blk-iolatency: Fix memory leak on add_disk() failures {CVE-2022-50550}
• drm/vkms: Fix use after free and double free on init error {CVE-2025-22097}
• iommu/amd: move wait_on_sem() out of spinlock {CVE-2026-43253}
• fbdev: bitblit: bound-check glyph index in bit_cursor() {CVE-2026-74635}
• KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page {CVE-2026-80726}
• wifi: nl80211: reject beacons with bad HE operation {CVE-2026-97517}
• sctp: prevent peer transport count overflow {CVE-2026-74469}
• IB/isert: reject login PDUs declaring more data than was received {CVE-2026-90413}
• sctp: validate embedded address parameter length {CVE-2026-74287}
• tcp: fix use-after-free of retransmit_skb_hint in tcp_send_synack() {CVE-2026-98374}
• ALSA: usb-audio: Fix a DMA to stack memory bug {CVE-2024-53197}
• ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices {CVE-2024-53197}
• USB: core: Limit the length of unkillable synchronous timeouts {CVE-2026-43428}
• ext4: refresh inline data size before write operations {CVE-2025-68264}
• net, bpf: check master for NULL in xdp_master_redirect() {CVE-2026-64545}
• iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() {CVE-2026-31505}
• dm cache: fix…

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

blk-iolatency: Fix memory leak on add_disk() failures

When a gendisk is successfully initialized but add_disk() fails such as when a loop device has invalid number of minor device numbers specified, blkcg_init_disk() is called during init and then blkcg_exit_disk() during error handling. Unfortunately, iolatency gets initialized in the former but doesn't get cleaned up in the latter.

This is because, in non-error cases, the cleanup is performed by del_gendisk() calling rq_qos_exit(), the assumption being that rq_qos policies, iolatency being one of them, can only be activated once the disk is fully registered and visible. That assumption is true for wbt and iocost, but not so for iolatency as it gets initialized before add_disk() is called.

It is desirable to lazy-init rq_qos policies because they are optional features and add to hot path overhead once initialized - each IO has to walk all the registered rq_qos policies. So, we want to switch iolatency to lazy init too. However, that's a bigger change. As a fix for the immediate problem, let's just add an extra call to rq_qos_exit() in blkcg_exit_disk(). This is safe because duplicate calls to rq_qos_exit() become noop's.