CVE-2023-52775

net/smc: avoid data corruption caused by decline

8.2 HighFix available

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

net/smc: avoid data corruption caused by decline

We found a data corruption issue during testing of SMC-R on Redis applications.

The benchmark has a low probability of reporting a strange error as shown below.

"Error: Protocol error, got "\xe2" as reply type byte"

Finally, we found that the retrieved error data was as follows:

0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2

It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations:

client server ¦ clc proposal -------------> ¦ clc accept <------------- ¦ clc confirm -------------> wait llc confirm send llc confirm ¦failed llc confirm ¦ x------ (after 2s)timeout wait llc confirm rsp

wait decline

(after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <--------------

As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection.

This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout).

This issue requires an immediate solution, since the protocol updates involve a more long-term solution.

Attack profile

How easy it is to exploit

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None

What an attacker can affect

Confidentiality: None
Integrity: High
Availability: Low

Exploit likelihood

0.67%Up 0.6 points since May 22, 2024

What each source reports

CVE List Score used 8.2

net/smc: avoid data corruption caused by decline

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

net/smc: avoid data corruption caused by decline

We found a data corruption issue during testing of SMC-R on Redis applications.

The benchmark has a low probability of reporting a strange error as shown below.

"Error: Protocol error, got "\xe2" as reply type byte"

Finally, we found that the retrieved error data was as follows:

0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2

It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations:

wait decline

(after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <--------------

As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection.

This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout).

This issue requires an immediate solution, since the protocol updates involve a more long-term solution.

Record: CVE-2023-52775
CVSS 3.1: 8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Updated: 2026-11-02

EUVDEUVD-2023-59492 8.2

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

net/smc: avoid data corruption caused by decline

We found a data corruption issue during testing of SMC-R on Redis applications.

The benchmark has a low probability of reporting a strange error as shown below.

"Error: Protocol error, got "\xe2" as reply type byte"

Finally, we found that the retrieved error data was as follows:

0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2

It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations:

wait decline

(after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <--------------

As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection.

This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout).

This issue requires an immediate solution, since the protocol updates involve a more long-term solution.

Record: EUVD-2023-59492
CVSS 3.1: 8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Updated: 2026-11-02

GitHub AdvisoriesGHSA-mxqp-c4m3-mg6r 7.8

In the Linux kernel, the following vulnerability has been resolved: net/smc: avoid data...

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

net/smc: avoid data corruption caused by decline

We found a data corruption issue during testing of SMC-R on Redis applications.

The benchmark has a low probability of reporting a strange error as shown below.

"Error: Protocol error, got "\xe2" as reply type byte"

Finally, we found that the retrieved error data was as follows:

0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2

It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations:

wait decline

(after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <--------------

As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection.

This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout).

This issue requires an immediate solution, since the protocol updates involve a more long-term solution.

Record: GHSA-mxqp-c4m3-mg6r
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-787
Updated: 2026-11-02

NVD 8.2

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

net/smc: avoid data corruption caused by decline

We found a data corruption issue during testing of SMC-R on Redis applications.

The benchmark has a low probability of reporting a strange error as shown below.

"Error: Protocol error, got "\xe2" as reply type byte"

Finally, we found that the retrieved error data was as follows:

0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2

It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations:

wait decline

(after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <--------------

As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection.

This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout).

This issue requires an immediate solution, since the protocol updates involve a more long-term solution.

Record: CVE-2023-52775
CVSS 3.1: 8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-787
Updated: 2026-11-02

OSVBELL-CVE-2023-52775 7.8

Record: BELL-CVE-2023-52775
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

OSV 8.2

net/smc: avoid data corruption caused by decline

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

net/smc: avoid data corruption caused by decline

We found a data corruption issue during testing of SMC-R on Redis applications.

The benchmark has a low probability of reporting a strange error as shown below.

"Error: Protocol error, got "\xe2" as reply type byte"

Finally, we found that the retrieved error data was as follows:

0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2

It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations:

wait decline

(after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <--------------

As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection.

This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout).

This issue requires an immediate solution, since the protocol updates involve a more long-term solution.

Record: CVE-2023-52775
CVSS 3.1: 8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Updated: 2026-11-02

Show 19 moreShow less

OSVDEBIAN-CVE-2023-52775 7.8

In the Linux kernel, the following vulnerability has been resolved: net/smc: avoid data corruption caused by decline We found a data corruption issue during testing of SMC-R on Redis applications. The benchmark has a low probability of reporting a strange error as shown below. "Error: Protocol error, got "\xe2" as reply type byte" Finally, we found that the retrieved error data was as follows: 0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2 It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations: client server ¦ clc proposal -------------> ¦ clc accept <------------- ¦ clc confirm -------------> wait llc confirm send llc confirm ¦failed llc confirm ¦ x------ (after 2s)timeout wait llc confirm rsp wait decline (after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <-------------- As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection. This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout). This issue requires an immediate solution, since the protocol updates involve a more long-term solution.

Record: DEBIAN-CVE-2023-52775
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

OSVOESA-2024-1706 0.0

kernel security update

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

net/mlx5e: Fix use-after-free of encap entry in neigh update handler

Function mlx5e_rep_neigh_update() wasn't updated to accommodate rtnl lock removal from TC filter update path and properly handle concurrent encap entry insertion/deletion which can lead to following use-after-free:

[23827.464923] ================================================================== [23827.469446] BUG: KASAN: use-after-free in mlx5e_encap_take+0x72/0x140 [mlx5_core] [23827.470971] Read of size 4 at addr ffff8881d132228c by task kworker/u20:6/21635 [23827.472251] [23827.472615] CPU: 9 PID: 21635 Comm: kworker/u20:6 Not tainted 5.13.0-rc3+ #5 [23827.473788] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [23827.475639] Workqueue: mlx5e mlx5e_rep_neigh_update [mlx5_core] [23827.476731] Call Trace: [23827.477260] dump_stack+0xbb/0x107 [23827.477906] print_address_description.constprop.0+0x18/0x140 [23827.478896] ? mlx5e_encap_take+0x72/0x140 [mlx5_core] [23827.479879] ? mlx5e_encap_take+0x72/0x140 [mlx5_core] [23827.480905] kasan_report.cold+0x7c/0xd8 [23827.481701] ? mlx5e_encap_take+0x72/0x140 [mlx5_core] [23827.482744] kasan_check_range+0x145/0x1a0 [23827.493112] mlx5e_encap_take+0x72/0x140 [mlx5_core] [23827.494054] ? mlx5e_tc_tun_encap_info_equal_generic+0x140/0x140 [mlx5_core] [23827.495296] mlx5e_rep_neigh_update+0x41e/0x5e0 [mlx5_core] [23827.496338] ? mlx5e_rep_neigh_entry_release+0xb80/0xb80 [mlx5_core] [23827.497486] ? read_word_at_a_time+0xe/0x20 [23827.498250] ? strscpy+0xa0/0x2a0 [23827.498889] process_one_work+0x8ac/0x14e0 [23827.499638] ? lockdep_hardirqs_on_prepare+0x400/0x400 [23827.500537] ? pwq_dec_nr_in_flight+0x2c0/0x2c0 [23827.501359] ? rwlock_bug.part.0+0x90/0x90 [23827.502116] worker_thread+0x53b/0x1220 [23827.502831] ? process_one_work+0x14e0/0x14e0 [23827.503627] kthread+0x328/0x3f0 [23827.504254] ? _raw_spin_unlock_irq+0x24/0x40 [23827.505065] ? __kthread_bind_mask+0x90/0x90 [23827.505912] ret_from_fork+0x1f/0x30 [23827.506621] [23827.506987] Allocated by task 28248: [23827.507694] kasan_save_stack+0x1b/0x40 [23827.508476] __kasan_kmalloc+0x7c/0x90 [23827.509197] mlx5e_attach_encap+0xde1/0x1d40 [mlx5_core] [23827.510194] mlx5e_tc_add_fdb_flow+0x397/0xc40 [mlx5_core] [23827.511218] __mlx5e_add_fdb_flow+0x519/0xb30 [mlx5_core] [23827.512234] mlx5e_configure_flower+0x191c/0x4870 [mlx5_core] [23827.513298] tc_setup_cb_add+0x1d5/0x420 [23827.514023] fl_hw_replace_filter+0x382/0x6a0 [cls_flower] [23827.514975] fl_change+0x2ceb/0x4a51 [cls_flower] [23827.515821] tc_new_tfilter+0x89a/0x2070 [23827.516548] rtnetlink_rcv_msg+0x644/0x8c0 [23827.517300] netlink_rcv_skb+0x11d/0x340 [23827.518021] netlink_unicast+0x42b/0x700 [23827.518742] netlink_sendmsg+0x743/0xc20 [23827.519467] sock_sendmsg+0xb2/0xe0 [23827.520131] ____sys_sendmsg+0x590/0x770 [23827.520851] ___sys_sendmsg+0xd8/0x160 [23827.521552] __sys_sendmsg+0xb7/0x140 [23827.522238] do_syscall_64+0x3a/0x70 [23827.522907] entry_SYSCALL_64_after_hwframe+0x44/0xae [23827.523797] [23827.524163] Freed by task 25948: [23827.524780] kasan_save_stack+0x1b/0x40 [23827.525488] kasan_set_track+0x1c/0x30 [23827.526187] kasan_set_free_info+0x20/0x30 [23827.526968] __kasan_slab_free+0xed/0x130 [23827.527709] slab_free_freelist_hook+0xcf/0x1d0 [23827.528528] kmem_cache_free_bulk+0x33a/0x6e0 [23827.529317] kfree_rcu_work+0x55f/0xb70 [23827.530024] process_one_work+0x8ac/0x14e0 [23827.530770] worker_thread+0x53b/0x1220 [23827.531480] kthread+0x328/0x3f0 [23827.532114] ret_from_fork+0x1f/0x30 [23827.532785] [23827.533147] Last potentially related work creation: [23827.534007] kasan_save_stack+0x1b/0x40 [23827.534710] kasan_record_aux_stack+0xab/0xc0 …

Record: OESA-2024-1706
CVSS 3.1: 0.0 NoneCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N
Updated: 2026-11-02

OSVOESA-2024-1707 0.0

kernel security update

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

net/mlx5e: Fix use-after-free of encap entry in neigh update handler

Record: OESA-2024-1707
CVSS 3.1: 0.0 NoneCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N
Updated: 2026-11-02

OSVRHSA-2024:10771 7.8

Red Hat Security Advisory: kernel security update

Record: RHSA-2024:10771
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

OSVRHSA-2024:5101 7.8

Red Hat Security Advisory: kernel security update

Record: RHSA-2024:5101
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

OSVRHSA-2024:9315 7.8

Red Hat Security Advisory: kernel security update

Record: RHSA-2024:9315
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

OSVUBUNTU-CVE-2023-52775 7.8

Record: UBUNTU-CVE-2023-52775
CVSS 3.1: 7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1: 8.2 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Updated: 2026-11-11

OSVALSA-2024:5101 No score

Important: kernel security update

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

Security Fix(es):

kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)
kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
(CVE-2023-28746)
(CVE-2023-52847)
(CVE-2021-47548)
(CVE-2024-36921)
(CVE-2024-26921)
(CVE-2021-47579)
(CVE-2024-36927)
(CVE-2024-39276)
(CVE-2024-33621)
(CVE-2024-27010)
(CVE-2024-26960)
(CVE-2024-38596)
(CVE-2022-48743)
(CVE-2024-26733)
(CVE-2024-26586)
(CVE-2024-26698)
(CVE-2023-52619)

Bug Fix(es):

AlmaLinux8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:AlmaLinux-17678)
[AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:AlmaLinux-23841)
[almalinux8] gfs2: Fix glock shrinker (JIRA:AlmaLinux-32941)
lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:AlmaLinux-33437)
[Hyper-V][AlmaLinux-8.10.z] Update hv_netvsc driver to TOT (JIRA:AlmaLinux-39074)
Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:AlmaLinux-40167)
blk-cgroup: Properly propagate the iostat update up the hierarchy [almalinux-8.10.z] (JIRA:AlmaLinux-40939)
(JIRA:AlmaLinux-31798)
(JIRA:AlmaLinux-10263)
(JIRA:AlmaLinux-40901)
(JIRA:AlmaLinux-43547)
(JIRA:AlmaLinux-34876)

Enhancement(s):

[RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:AlmaLinux-19723)

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

Record: ALSA-2024:5101
Updated: 2026-11-02

OSVCLSA-2025-1763722365 No score

kernel: Fix of 63 CVEs

wifi: mwifiex: Fix OOB and integer underflow when rx packets {CVE-2023-53226} {CVE-2023-53226}
wifi: mac80211: check S1G action frame size {CVE-2023-53257} {CVE-2023-53257}
wifi: cfg80211: fix use-after-free in cmp_bss() {CVE-2025-39864} {CVE-2025-39864}
partitions: mac: fix handling of bogus partition table {CVE-2025-21772} {CVE-2025-21772}
wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() {CVE-2024-58014} {CVE-2024-58014}
wifi: at76c50x: fix use after free access in at76_disconnect {CVE-2025-37796} {CVE-2025-37796}
dma-direct: Leak pages on dma_set_decrypted() failure {CVE-2024-35939} {CVE-2024-35939}
Bluetooth: L2CAP: Fix user-after-free {CVE-2022-50386} {CVE-2022-50386}
efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare {CVE-2025-39817} {CVE-2025-39817}
wifi: cfg80211: check A-MSDU format more carefully {CVE-2024-35937} {CVE-2024-35937}
nfs: fix UAF in direct writes {CVE-2024-26958} {CVE-2024-26958}
wifi: iwlwifi: mvm: guard against invalid STA ID on removal {CVE-2024-36921} {CVE-2024-36921}
net/smc: avoid data corruption caused by decline {CVE-2023-52775} {CVE-2023-52775}
bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() {CVE-2024-39487} {CVE-2024-39487}
scsi: qedi: Fix crash while reading debugfs attribute {CVE-2024-40978} {CVE-2024-40978}
mac802154: fix llsec key resources release in mac802154_llsec_key_del {CVE-2024-26961} {CVE-2024-26961}
platform/x86: wmi: Fix opening of char device {CVE-2023-52864} {CVE-2023-52864}
net/sched: act_mirred: don't override retval if we already lost the skb {CVE-2024-26739} {CVE-2024-26739}
drm/dp_mst: Fix resetting msg rx state after topology removal {CVE-2024-57876} {CVE-2024-57876}
net/mlx5: Add a timeout to acquire the command queue semaphore {CVE-2024-38556} {CVE-2024-38556}
of: Fix double free in of_parse_phandle_with_args_map {CVE-2023-52679} {CVE-2023-52679}
xhci: Handle TD clearing for multiple streams case {CVE-2024-40927} {CVE-2024-40927}
wifi: mac80211: fix potential key use-after-free {CVE-2023-52530} {CVE-2023-52530}
net: openvswitch: Fix Use-After-Free in ovs_ct_exit {CVE-2024-27395} {CVE-2024-27395}
r8169: Fix possible ring buffer corruption on fragmented Tx packets. {CVE-2024-38586} {CVE-2024-38586}
media: gspca: cpia1: shift-out-of-bounds in set_flicker {CVE-2023-52764} {CVE-2023-52764}
media: bttv: fix use after free error due to btv->timeout timer {CVE-2023-52847} {CVE-2023-52847}
vsock: Fix transport_* TOCTOU {CVE-2025-38461} {CVE-2025-38461}
ppdev: Add an error check in register_device {CVE-2024-36015} {CVE-2024-36015}
HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556} {CVE-2025-38556}
iio: adc: at91: call input_free_device() on allocated iio_dev {CVE-2024-57904} {CVE-2024-57904}
perf/aux: Fix AUX buffer serialization {CVE-2024-46713} {CVE-2024-46713}
net_sched: hfsc: Fix a UAF vulnerability in class handling {CVE-2025-37797} {CVE-2025-37797}
wifi: rtlwifi: remove unused check_buddy_priv {CVE-2024-58072} {CVE-2024-58072}
wifi: rtlwifi: remove unused dualmac control leftovers {CVE-2024-58072} {CVE-2024-58072}
wifi: rtlwifi: remove unused timer and related code {CVE-2024-58072} {CVE-2024-58072}
ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() {CVE-2025-22121} {CVE-2025-22121}
ext4: move where set the MAY_INLINE_DATA flag is set {CVE-2025-22121} {CVE-2025-22121}
ext4: introduce ITAIL helper {CVE-2025-22121} {CVE-2025-22121}
ext4: improve xattr consistency checking and error reporting {CVE-2025-22121} {CVE-2025-22121}
mm: fix zswap writeback race condition {CVE-2023-53178} {CVE-2023-53178}
fs: fix UAF/GPF bug in nilfs_mdt_destroy {CVE-2022-50367} {CVE-2022-50367}
ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control
ALSA: usb-audio: Validate UAC3 cluster segment descriptors {CVE-2025-39757} {CVE-2025-39757}
smb: client: fix use-after-free in cifs_oplock_break {CVE-2025-38527} {CVE-2025-38527} -…

Record: CLSA-2025-1763722365
Updated: 2026-11-02

OSVRLSA-2024:5101 No score

Important: kernel security update

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

Security Fix(es):

kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)
kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
(CVE-2023-28746)
(CVE-2023-52847)
(CVE-2021-47548)
(CVE-2024-36921)
(CVE-2024-26921)
(CVE-2021-47579)
(CVE-2024-36927)
(CVE-2024-39276)
(CVE-2024-33621)
(CVE-2024-27010)
(CVE-2024-26960)
(CVE-2024-38596)
(CVE-2022-48743)
(CVE-2024-26733)
(CVE-2024-26586)
(CVE-2024-26698)
(CVE-2023-52619)

Bug Fix(es):

Rocky Linux8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:Rocky Linux-17678)
[AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:Rocky Linux-23841)
[rhel8] gfs2: Fix glock shrinker (JIRA:Rocky Linux-32941)
lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:Rocky Linux-33437)
[Hyper-V][Rocky Linux-8.10.z] Update hv_netvsc driver to TOT (JIRA:Rocky Linux-39074)
Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:Rocky Linux-40167)
blk-cgroup: Properly propagate the iostat update up the hierarchy [rhel-8.10.z] (JIRA:Rocky Linux-40939)
(JIRA:Rocky Linux-31798)
(JIRA:Rocky Linux-10263)
(JIRA:Rocky Linux-40901)
(JIRA:Rocky Linux-43547)
(JIRA:Rocky Linux-34876)

Enhancement(s):

[RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:Rocky Linux-19723)

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

Record: RLSA-2024:5101
Updated: 2026-11-02

OSVRXSA-2024:5101 No score

Important: kernel security update

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

Security Fix(es):

kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)
kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
(CVE-2023-28746)
(CVE-2023-52847)
(CVE-2021-47548)
(CVE-2024-36921)
(CVE-2024-26921)
(CVE-2021-47579)
(CVE-2024-36927)
(CVE-2024-39276)
(CVE-2024-33621)
(CVE-2024-27010)
(CVE-2024-26960)
(CVE-2024-38596)
(CVE-2022-48743)
(CVE-2024-26733)
(CVE-2024-26586)
(CVE-2024-26698)
(CVE-2023-52619)

Bug Fix(es):

Rocky Linux SIG Cloud8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:Rocky Linux SIG Cloud-17678)
[AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:Rocky Linux SIG Cloud-23841)
[rhel8] gfs2: Fix glock shrinker (JIRA:Rocky Linux SIG Cloud-32941)
lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:Rocky Linux SIG Cloud-33437)
[Hyper-V][Rocky Linux SIG Cloud-8.10.z] Update hv_netvsc driver to TOT (JIRA:Rocky Linux SIG Cloud-39074)
Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:Rocky Linux SIG Cloud-40167)
blk-cgroup: Properly propagate the iostat update up the hierarchy [rhel-8.10.z] (JIRA:Rocky Linux SIG Cloud-40939)
(JIRA:Rocky Linux SIG Cloud-31798)
(JIRA:Rocky Linux SIG Cloud-10263)
(JIRA:Rocky Linux SIG Cloud-40901)
(JIRA:Rocky Linux SIG Cloud-43547)
(JIRA:Rocky Linux SIG Cloud-34876)

Enhancement(s):

[RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:Rocky Linux SIG Cloud-19723)

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

Record: RXSA-2024:5101
Updated: 2026-11-02

OSVSUSE-SU-2024:2802-1 No score