CVE-2022-48887

In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Remove rcu locks from user resources User resource lookups used rcu to avoid two extra atomics. Unfortunately the rcu paths were buggy and it was easy to make the driver crash by submitting command buffers from two different threads. Because the lookups never show up in performance profiles replace them with a regular spin lock which fixes the races in accesses to those shared resources. Fixes kernel oops'es in IGT's vmwgfx execution_buffer stress test and seen crashes with apps using shared resources.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

drm/vmwgfx: Remove rcu locks from user resources

User resource lookups used rcu to avoid two extra atomics. Unfortunately the rcu paths were buggy and it was easy to make the driver crash by submitting command buffers from two different threads. Because the lookups never show up in performance profiles replace them with a regular spin lock which fixes the races in accesses to those shared resources.

Fixes kernel oops'es in IGT's vmwgfx execution_buffer stress test and seen crashes with apps using shared resources.(CVE-2022-48887)

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

btrfs: do not start relocation until in progress drops are done

We hit a bug with a recovering relocation on mount for one of our file systems in production. I reproduced this locally by injecting errors into snapshot delete with balance running at the same time. This presented as an error while looking up an extent item

WARNING: CPU: 5 PID: 1501 at fs/btrfs/extent-tree.c:866 lookup_inline_extent_backref+0x647/0x680 CPU: 5 PID: 1501 Comm: btrfs-balance Not tainted 5.16.0-rc8+ #8 RIP: 0010:lookup_inline_extent_backref+0x647/0x680 RSP: 0018:ffffae0a023ab960 EFLAGS: 00010202 RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 000000000000000c RDI: 0000000000000000 RBP: ffff943fd2a39b60 R08: 0000000000000000 R09: 0000000000000001 R10: 0001434088152de0 R11: 0000000000000000 R12: 0000000001d05000 R13: ffff943fd2a39b60 R14: ffff943fdb96f2a0 R15: ffff9442fc923000 FS: 0000000000000000(0000) GS:ffff944e9eb40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1157b1fca8 CR3: 000000010f092000 CR4: 0000000000350ee0 Call Trace: <TASK> insert_inline_extent_backref+0x46/0xd0 __btrfs_inc_extent_ref.isra.0+0x5f/0x200 ? btrfs_merge_delayed_refs+0x164/0x190 __btrfs_run_delayed_refs+0x561/0xfa0 ? btrfs_search_slot+0x7b4/0xb30 ? btrfs_update_root+0x1a9/0x2c0 btrfs_run_delayed_refs+0x73/0x1f0 ? btrfs_update_root+0x1a9/0x2c0 btrfs_commit_transaction+0x50/0xa50 ? btrfs_update_reloc_root+0x122/0x220 prepare_to_merge+0x29f/0x320 relocate_block_group+0x2b8/0x550 btrfs_relocate_block_group+0x1a6/0x350 btrfs_relocate_chunk+0x27/0xe0 btrfs_balance+0x777/0xe60 balance_kthread+0x35/0x50 ? btrfs_balance+0xe60/0xe60 kthread+0x16b/0x190 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 </TASK>

Normally snapshot deletion and relocation are excluded from running at the same time by the fs_info->cleaner_mutex. However if we had a pending balance waiting to get the ->cleaner_mutex, and a snapshot deletion was running, and then the box crashed, we would come up in a state where we have a half deleted snapshot.

Again, in the normal case the snapshot deletion needs to complete before relocation can start, but in this case relocation could very well start before the snapshot deletion completes, as we simply add the root to the dead roots list and wait for the next time the cleaner runs to clean up the snapshot.

Fix this by setting a bit on the fs_info if we have any DEAD_ROOT's that had a pending drop_progress key. If they do then we know we were in the middle of the drop operation and set a flag on the fs_info. Then balance can wait until this flag is cleared to start up again.

If there are DEAD_ROOT's that don't have a drop_progress set then we're safe to start balance right away as we'll be properly protected by the cleaner_mutex.(CVE-2022-48901)

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

btrfs: do not WARN_ON() if we have PageError set

Whenever we do any extent buffer operations we call assert_eb_page_uptodate() to complain loudly…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

dmaengine: idxd: Prevent use after free on completion memory

On driver unload any pending descriptors are flushed at the time the interrupt is freed: idxd_dmaengine_drv_remove() -> drv_disable_wq() -> idxd_wq_free_irq() -> idxd_flush_pending_descs().

If there are any descriptors present that need to be flushed this flow triggers a "not present" page fault as below:

BUG: unable to handle page fault for address: ff391c97c70c9040 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page

The address that triggers the fault is the address of the descriptor that was freed moments earlier via: drv_disable_wq()->idxd_wq_free_resources()

Fix the use after free by freeing the descriptors after any possible usage. This is done after idxd_wq_reset() to ensure that the memory remains accessible during possible completion writes by the device.(CVE-2022-48867)

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

drm/vmwgfx: Remove rcu locks from user resources

User resource lookups used rcu to avoid two extra atomics. Unfortunately the rcu paths were buggy and it was easy to make the driver crash by submitting command buffers from two different threads. Because the lookups never show up in performance profiles replace them with a regular spin lock which fixes the races in accesses to those shared resources.

Fixes kernel oops'es in IGT's vmwgfx execution_buffer stress test and seen crashes with apps using shared resources.(CVE-2022-48887)

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

btrfs: do not start relocation until in progress drops are done

We hit a bug with a recovering relocation on mount for one of our file systems in production. I reproduced this locally by injecting errors into snapshot delete with balance running at the same time. This presented as an error while looking up an extent item

WARNING: CPU: 5 PID: 1501 at fs/btrfs/extent-tree.c:866 lookup_inline_extent_backref+0x647/0x680 CPU: 5 PID: 1501 Comm: btrfs-balance Not tainted 5.16.0-rc8+ #8 RIP: 0010:lookup_inline_extent_backref+0x647/0x680 RSP: 0018:ffffae0a023ab960 EFLAGS: 00010202 RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 000000000000000c RDI: 0000000000000000 RBP: ffff943fd2a39b60 R08: 0000000000000000 R09: 0000000000000001 R10: 0001434088152de0 R11: 0000000000000000 R12: 0000000001d05000 R13: ffff943fd2a39b60 R14: ffff943fdb96f2a0 R15: ffff9442fc923000 FS: 0000000000000000(0000) GS:ffff944e9eb40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1157b1fca8 CR3: 000000010f092000 CR4: 0000000000350ee0 Call Trace: <TASK> insert_inline_extent_backref+0x46/0xd0 __btrfs_inc_extent_ref.isra.0+0x5f/0x200 ? btrfs_merge_delayed_refs+0x164/0x190 __btrfs_run_delayed_refs+0x561/0xfa0 ? btrfs_search_slot+0x7b4/0xb30 ? btrfs_update_root+0x1a9/0x2c0 btrfs_run_delayed_refs+0x73/0x1f0 ? btrfs_update_root+0x1a9/0x2c0 btrfs_commit_transaction+0x50/0xa50 ? btrfs_update_reloc_root+0x122/0x220 prepare_to_merge+0x29f/0x320 relocate_block_group+0x2b8/0x550 btrfs_relocate_block_group+0x1a6/0x350 btrfs_relocate_chunk+0x27/0xe0 btrfs_balance+0x777/0xe60 balance_kthread+0x35/0x50 ? btrfs_balance+0xe60/0xe60 kthread+0x16b/0x190 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 </TASK>

Normally snapshot deletion and relocation are excluded from running at the same time by the fs_info->cleaner_mutex. However if we had a pending balance waiting to get the ->cleaner_mutex, and a snapshot deletion was running, and then the box crashed, we would come up in a state where we have a half deleted snapshot. …

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

dmaengine: idxd: Prevent use after free on completion memory

On driver unload any pending descriptors are flushed at the time the interrupt is freed: idxd_dmaengine_drv_remove() -> drv_disable_wq() -> idxd_wq_free_irq() -> idxd_flush_pending_descs().

If there are any descriptors present that need to be flushed this flow triggers a "not present" page fault as below:

BUG: unable to handle page fault for address: ff391c97c70c9040 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page

The address that triggers the fault is the address of the descriptor that was freed moments earlier via: drv_disable_wq()->idxd_wq_free_resources()

Fix the use after free by freeing the descriptors after any possible usage. This is done after idxd_wq_reset() to ensure that the memory remains accessible during possible completion writes by the device.(CVE-2022-48867)

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

drm/vmwgfx: Remove rcu locks from user resources

User resource lookups used rcu to avoid two extra atomics. Unfortunately the rcu paths were buggy and it was easy to make the driver crash by submitting command buffers from two different threads. Because the lookups never show up in performance profiles replace them with a regular spin lock which fixes the races in accesses to those shared resources.

Fixes kernel oops'es in IGT's vmwgfx execution_buffer stress test and seen crashes with apps using shared resources.(CVE-2022-48887)

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

btrfs: do not start relocation until in progress drops are done

We hit a bug with a recovering relocation on mount for one of our file systems in production. I reproduced this locally by injecting errors into snapshot delete with balance running at the same time. This presented as an error while looking up an extent item

WARNING: CPU: 5 PID: 1501 at fs/btrfs/extent-tree.c:866 lookup_inline_extent_backref+0x647/0x680 CPU: 5 PID: 1501 Comm: btrfs-balance Not tainted 5.16.0-rc8+ #8 RIP: 0010:lookup_inline_extent_backref+0x647/0x680 RSP: 0018:ffffae0a023ab960 EFLAGS: 00010202 RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 000000000000000c RDI: 0000000000000000 RBP: ffff943fd2a39b60 R08: 0000000000000000 R09: 0000000000000001 R10: 0001434088152de0 R11: 0000000000000000 R12: 0000000001d05000 R13: ffff943fd2a39b60 R14: ffff943fdb96f2a0 R15: ffff9442fc923000 FS: 0000000000000000(0000) GS:ffff944e9eb40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1157b1fca8 CR3: 000000010f092000 CR4: 0000000000350ee0 Call Trace: <TASK> insert_inline_extent_backref+0x46/0xd0 __btrfs_inc_extent_ref.isra.0+0x5f/0x200 ? btrfs_merge_delayed_refs+0x164/0x190 __btrfs_run_delayed_refs+0x561/0xfa0 ? btrfs_search_slot+0x7b4/0xb30 ? btrfs_update_root+0x1a9/0x2c0 btrfs_run_delayed_refs+0x73/0x1f0 ? btrfs_update_root+0x1a9/0x2c0 btrfs_commit_transaction+0x50/0xa50 ? btrfs_update_reloc_root+0x122/0x220 prepare_to_merge+0x29f/0x320 relocate_block_group+0x2b8/0x550 btrfs_relocate_block_group+0x1a6/0x350 btrfs_relocate_chunk+0x27/0xe0 btrfs_balance+0x777/0xe60 balance_kthread+0x35/0x50 ? btrfs_balance+0xe60/0xe60 kthread+0x16b/0x190 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 </TASK>

Normally snapshot deletion and relocation are excluded from running at the same time by the fs_info->cleaner_mutex. However if we had a pending balance waiting to get the ->cleaner_mutex, and a snapshot deletion was running, and then the box crashed, we would come up in a state where we have a half deleted snapshot. …

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

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

In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Remove rcu locks from user resources User resource lookups used rcu to avoid two extra atomics. Unfortunately the rcu paths were buggy and it was easy to make the driver crash by submitting command buffers from two different threads. Because the lookups never show up in performance profiles replace them with a regular spin lock which fixes the races in accesses to those shared resources. Fixes kernel oops'es in IGT's vmwgfx execution_buffer stress test and seen crashes with apps using shared resources.

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

The following security bugs were fixed:

• CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
• CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).
• CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).
• CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
• CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
• CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
• CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
• CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).
• CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
• CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).
• CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).
• CVE-2024-44939: fix null ptr deref in dtInsertEntry (bsc#1229820).
• CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).
• CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
• CVE-2024-43902: Add null checker before passing variables (bsc#1229767).
• CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)
• CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
• CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)
• CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
• CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).
• CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).
• CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
• CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
• CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).
• CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
• CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
• CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)
• CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).
• CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).
• CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).
• CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
• CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
• CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)
• CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
• CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
• CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)
• CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).
• CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
• CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
• CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
• CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
• CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
• CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
• CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290 git-fixes).
• CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
• CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
• CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
• CVE-2024-27016: Validate pppoe header (bsc#1223807).
• CVE-2024-35945: Prevent nullptr exceptions on ISR (bsc#1224639).
• CVE-2023-52581: Fix memleak when more than 255…

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

The following security bugs were fixed:

• CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
• CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).
• CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).
• CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
• CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
• CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
• CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
• CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).
• CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
• CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).
• CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).
• CVE-2024-44939: Fix null ptr deref in dtInsertEntry (bsc#1229820).
• CVE-2024-41087: Fix double free on error (bsc#1228466).
• CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
• CVE-2024-43902: Add null checker before passing variables (bsc#1229767).
• CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)
• CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
• CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)
• CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
• CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).
• CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).
• CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
• CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
• CVE-2024-26812: struct virqfd kABI workaround (bsc#1222808).
• CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
• CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
• CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)
• CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).
• CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).
• CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).
• CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
• CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
• CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)
• CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
• CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
• CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)
• CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).
• CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
• CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
• CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
• CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
• CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
• CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
• CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290).
• CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
• CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
• CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
• CVE-2024-27016: Validate pppoe header (bsc#1223807).
• CVE-2024-35945: Prevent nullptr exceptions on ISR (bsc#1224639).
• CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).…

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

The following security bugs were fixed:

• CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
• CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).
• CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).
• CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
• CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
• CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
• CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch (bsc#1226798)
• CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
• CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).
• CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
• CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).
• CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).
• CVE-2024-44939: Fix null ptr deref in dtInsertEntry (bsc#1229820).
• CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).
• CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
• CVE-2024-43902: Add null checker before passing variables (bsc#1229767).
• CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)
• CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
• CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)
• CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
• CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).
• CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).
• CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
• CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
• CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).
• CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
• CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
• CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)
• CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).
• CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).
• CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).
• CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
• CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
• CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)
• CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
• CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
• CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)
• CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).
• CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
• CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
• CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
• CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
• CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
• CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
• CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290 git-fixes).
• CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
• CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
• CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
• CVE-2024-27016: Validate pppoe header (bsc#1223807). -…