huzaifas-sidhpurwala/security-commit huggingface dataset:
CVE-2023-52624: kernel: drm/amd/display: Wake DMCUB before executing GPINT commands
Component: kernel
Severity: Low
CWE: CWE-99 (Improper Control of Resource Identifiers ('Resource Injection'))
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-03-26T00:00:00+00:00

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

drm/amd/display: Wake DMCUB before executing GPINT commands

[Why]
DMCUB can be in idle when we attempt to interface with the HW through
the GPINT mailbox resulting in a system hang.

[How]
Add dc_wake_and_execute_gpint() to wrap the wake, execute, sleep
sequence.

If the GPINT executes successfully then DMCUB will be put back into
sleep after the optional response is returned.

It functions similar to the inbox command interface.


Affected upstream versions: 4.15
Fixed upstream versions: 0, 6.7.3, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 2ef98c6d753a744e333b7e34b9cf687040fba57d
CVE-2023-52625: kernel: drm/amd/display: Refactor DMCUB enter/exit idle interface
Component: kernel
Severity: Low
CWE: CWE-99 (Improper Control of Resource Identifiers ('Resource Injection'))
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-03-26T00:00:00+00:00

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

drm/amd/display: Refactor DMCUB enter/exit idle interface

[Why]
We can hang in place trying to send commands when the DMCUB isn't
powered on.

[How]
We need to exit out of the idle state prior to sending a command,
but the process that performs the exit also invokes a command itself.

Fixing this issue involves the following:

1. Using a software state to track whether or not we need to start
   the process to exit idle or notify idle.

It's possible for the hardware to have exited an idle state without
driver knowledge, but entering one is always restricted to a driver
allow - which makes the SW state vs HW state mismatch issue purely one
of optimization, which should seldomly be hit, if at all.

2. Refactor any instances of exit/notify idle to use a single wrapper
   that maintains this SW state.

This works simialr to dc_allow_idle_optimizations, but works at the
DMCUB level and makes sure the state is marked prior to any notify/exit
idle so we don't enter an infinite loop.

3. Make sure we exit out of idle prior to sending any commands or
   waiting for DMCUB idle.

This patch takes care of 1/2. A future patch will take care of wrapping
DMCUB command submission with calls to this new interface.


Affected upstream versions: 4.15
Fixed upstream versions: 0, 6.7.3, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 820c3870c491946a78950cdf961bf40e28c1025f
CVE-2023-52626: kernel: net/mlx5e: Fix operation precedence bug in port timestamping napi_poll context
Component: kernel
Severity: Moderate
CWE: CWE-125 (Out-of-bounds Read)
CVSS v3: 6 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H)
Public date: 2024-03-26T00:00:00+00:00

An operation precedence flaw was found in the Linux kernel’s Mellanox Technologies networking driver. This flaw allows a local user to crash the system or potentially gain access to data that should not be accessible.


Affected upstream versions: 6.6.3 < 6.6.15, 6.5.13 < 6.6, 6.7
Fixed upstream versions: 0, 6.6, 6.6.15, 6.7.3, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 40e0d0746390c5b0c31144f4f1688d72f3f8d790
CVE-2023-52628: kernel: netfilter: nftables: exthdr: fix 4-byte stack OOB write
Component: kernel
Severity: Moderate
CWE: CWE-787 (Out-of-bounds Write)
CVSS v3: 7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H)
Public date: 2024-03-28T00:00:00+00:00

An out-of-bounds write flaw was found in the Linux kernel’s Netfilter functionality. This flaw allows a local user to crash or potentially escalate their privileges on the system.

Statement: This issue is fixed in Red Hat Enterprise Linux 9.

Affected upstream versions: 4.1
Fixed upstream versions: 0, 4.19.316, 5.10.198, 5.15.132, 5.4.279, 6.1.54, 6.5.4, 6.6
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 28a97c43c9e32f437ebb8d6126f9bb7f3ca9521a
CVE-2023-52632: kernel: drm/amdkfd: lock dependency warning with srcu
Component: kernel
Severity: Low
CWE: CWE-667 (Improper Locking)
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-04-02T00:00:00+00:00

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

drm/amdkfd: Fix lock dependency warning with srcu

======================================================
WARNING: possible circular locking dependency detected
6.5.0-kfd-yangp #2289 Not tainted
------------------------------------------------------
kworker/0:2/996 is trying to acquire lock:
        (srcu){.+.+}-{0:0}, at: __synchronize_srcu+0x5/0x1a0

but task is already holding lock:
        ((work_completion)(&svms->deferred_list_work)){+.+.}-{0:0}, at:
	process_one_work+0x211/0x560

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #3 ((work_completion)(&svms->deferred_list_work)){+.+.}-{0:0}:
        __flush_work+0x88/0x4f0
        svm_range_list_lock_and_flush_work+0x3d/0x110 [amdgpu]
        svm_range_set_attr+0xd6/0x14c0 [amdgpu]
        kfd_ioctl+0x1d1/0x630 [amdgpu]
        __x64_sys_ioctl+0x88/0xc0

-> #2 (&info->lock#2){+.+.}-{3:3}:
        __mutex_lock+0x99/0xc70
        amdgpu_amdkfd_gpuvm_restore_process_bos+0x54/0x740 [amdgpu]
        restore_process_helper+0x22/0x80 [amdgpu]
        restore_process_worker+0x2d/0xa0 [amdgpu]
        process_one_work+0x29b/0x560
        worker_thread+0x3d/0x3d0

-> #1 ((work_completion)(&(&process->restore_work)->work)){+.+.}-{0:0}:
        __flush_work+0x88/0x4f0
        __cancel_work_timer+0x12c/0x1c0
        kfd_process_notifier_release_internal+0x37/0x1f0 [amdgpu]
        __mmu_notifier_release+0xad/0x240
        exit_mmap+0x6a/0x3a0
        mmput+0x6a/0x120
        do_exit+0x322/0xb90
        do_group_exit+0x37/0xa0
        __x64_sys_exit_group+0x18/0x20
        do_syscall_64+0x38/0x80

-> #0 (srcu){.+.+}-{0:0}:
        __lock_acquire+0x1521/0x2510
        lock_sync+0x5f/0x90
        __synchronize_srcu+0x4f/0x1a0
        __mmu_notifier_release+0x128/0x240
        exit_mmap+0x6a/0x3a0
        mmput+0x6a/0x120
        svm_range_deferred_list_work+0x19f/0x350 [amdgpu]
        process_one_work+0x29b/0x560
        worker_thread+0x3d/0x3d0

other info that might help us debug this:
Chain exists of:
  srcu --> &info->lock#2 --> (work_completion)(&svms->deferred_list_work)

Possible unsafe locking scenario:

        CPU0                    CPU1
        ----                    ----
        lock((work_completion)(&svms->deferred_list_work));
                        lock(&info->lock#2);
			lock((work_completion)(&svms->deferred_list_work));
        sync(srcu);


Affected upstream versions: 5.14
Fixed upstream versions: 0, 6.1.77, 6.6.16, 6.7.4, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: b602f098f716723fa5c6c96a486e0afba83b7b94
CVE-2023-52634: kernel: drm/amd/display: Fix disable_otg_wa logic
Component: kernel
Severity: Low
CWE: CWE-99 (Improper Control of Resource Identifiers ('Resource Injection'))
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-04-02T00:00:00+00:00

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

drm/amd/display: Fix disable_otg_wa logic

[Why]
When switching to another HDMI mode, we are unnecesarilly
disabling/enabling FIFO causing both HPO and DIG registers to be set at
the same time when only HPO is supposed to be set.

This can lead to a system hang the next time we change refresh rates as
there are cases when we don't disable OTG/FIFO but FIFO is enabled when
it isn't supposed to be.

[How]
Removing the enable/disable FIFO entirely.


Affected upstream versions: 6.7
Fixed upstream versions: 0, 6.7.4, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: ce29728ef6485a367934cc100249c66dd3cde5b6
CVE-2023-52635: kernel: PM / devfreq: Synchronize devfreq_monitor_[start/stop]
Component: kernel
Severity: Moderate
CWE: CWE-414 (Missing Lock Check)
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-04-02T00:00:00+00:00

A flaw was found in the Linux kernel resulting from race conditions and a lack of synchronization in handling the delayed work timers in the devfreq component. This issue can lead to inconsistencies and a corruption of the timer list.

Statement: Red Hat Enterprise Linux 8 is not affected by this vulnerability, as the default configuration does not set CONFIG_PM_DEVFREQ.

Affected upstream versions: 3.8
Fixed upstream versions: 0, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 3399cc7013e761fee9d6eec795e9b31ab0cbe475
CVE-2023-52638: kernel: can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock
Component: kernel
Severity: Moderate
CWE: CWE-833 (Deadlock)
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-04-03T00:00:00+00:00

A vulnerability was found in the Linux kernel's Controller Area Network (CAN) protocol, within the J1939 protocol implementation. This issue occurs due to a potential deadlock caused by a race condition involving three locks: j1939_socks_lock, active_session_list_lock, and sk_session_queue_lock. This issue was identified in a Syzbot bug report.


Affected upstream versions: 5.15
Fixed upstream versions: 0, 5.15.149, 6.1.79, 6.6.18, 6.7.6, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 03358aba991668d3bb2c65b3c82aa32c36851170
CVE-2023-52639: kernel: KVM: s390: vsie: fix race during shadow creation
Component: kernel
Severity: Low
CWE: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))
CVSS v3: 4.7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-04-03T00:00:00+00:00

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

KVM: s390: vsie: fix race during shadow creation

Right now it is possible to see gmap->private being zero in
kvm_s390_vsie_gmap_notifier resulting in a crash.  This is due to the
fact that we add gmap->private == kvm after creation:

static int acquire_gmap_shadow(struct kvm_vcpu *vcpu,
                               struct vsie_page *vsie_page)
{
[...]
        gmap = gmap_shadow(vcpu->arch.gmap, asce, edat);
        if (IS_ERR(gmap))
                return PTR_ERR(gmap);
        gmap->private = vcpu->kvm;

Let children inherit the private field of the parent.


Affected upstream versions: 4.8
Fixed upstream versions: 0, 6.1.82, 6.6.22, 6.7.6, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 5df3b81a567eb565029563f26f374ae3803a1dfc
CVE-2023-52643: kernel: iio: core: fix memleak in iio_device_register_sysfs
Component: kernel
Severity: Low
CWE: CWE-402 (Transmission of Private Resources into a New Sphere ('Resource Leak'))
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N)
Public date: 2024-04-17T00:00:00+00:00

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

iio: core: fix memleak in iio_device_register_sysfs

When iio_device_register_sysfs_group() fails, we should
free iio_dev_opaque->chan_attr_group.attrs to prevent
potential memleak.


Affected upstream versions: 5.13
Fixed upstream versions: 0, 5.15.149, 6.1.79, 6.6.18, 6.7.6, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 1c6d19c8cbf6abcea2c8fca2db26abca2cbf0363
CVE-2023-52649: kernel: drm/vkms: Avoid reading beyond LUT array
Component: kernel
Severity: Moderate
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-01T00:00:00+00:00

An array read overflow vulnerability was found in drivers/gpu/drm/vkms/vkms_composer.c in the Linux kernel. This issue may lead to a crash.


Affected upstream versions: 6.6
Fixed upstream versions: 0, 6.6.23, 6.7.11, 6.8.2, 6.9
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 9556c167673057d48ce4a0da675026fe046654c1
CVE-2023-52650: kernel: drm/tegra: dsi: Add missing check for of_find_device_by_node
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-01T00:00:00+00:00

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

drm/tegra: dsi: Add missing check for of_find_device_by_node

The Linux kernel CVE team has assigned CVE-2023-52650 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024050109-CVE-2023-52650-e2d1@gregkh/T


Affected upstream versions: 3.19
Fixed upstream versions: 0, 4.19.311, 5.10.214, 5.15.153, 5.4.273, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 47a13d0b9d8527518639ab5c39667f69d6203e80
CVE-2023-52653: kernel: SUNRPC: fix a memleak in gss_import_v2_context
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-01T00:00:00+00:00

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

SUNRPC: fix a memleak in gss_import_v2_context

The ctx->mech_used.data allocated by kmemdup is not freed in neither
gss_import_v2_context nor it only caller gss_krb5_import_sec_context,
which frees ctx on error.

Thus, this patch reform the last call of gss_import_v2_context to the
gss_krb5_import_ctx_v2, preventing the memleak while keepping the return
formation.


Affected upstream versions: 2.6.35
Fixed upstream versions: 0, 6.6.23, 6.7.11, 6.8.2, 6.9
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 99044c01ed5329e73651c054d8a4baacdbb1a27c
CVE-2023-52656: kernel: io_uring: drop any code related to SCM_RIGHTS
Component: kernel
Severity: Moderate
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-13T00:00:00+00:00

A flaw was found in the Linux kernel that addresses the removal of dead code related to `SCM_RIGHTS` support within the `io_uring`. This code was deemed unnecessary after the kernel dropped the ability to pass `io_uring` file descriptors over `SCM_RIGHTS`. The vulnerability was assigned CVE status due to removing this code, which was part of a cleanup process following the resolution of a previous CVE (CVE-2023-52654).


Affected upstream versions: 5.1
Fixed upstream versions: 0, 5.10.214, 5.15.153, 5.4.273, 6.1.83, 6.6.23, 6.7.11, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: cfb24022bb2c31f1f555dc6bc3cc5e2547446fb3
CVE-2023-52658: kernel: Revert &#34;net/mlx5: Block entering switchdev mode with ns inconsistency&#34;
Component: kernel
Severity: Moderate
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

CVE-2023-52658 is a vulnerability in the Linux kernel's Mellanox MLX5 driver, specifically related to the switchdev mode. A previous commit intended to block entering switchdev mode due to namespace inconsistencies inadvertently caused system crashes. To address this, the problematic commit was reverted, restoring stability. Users should update their Linux kernel to a version that includes this reversion to ensure reliable operation.


Affected upstream versions: 6.1.22 < 6.1.162, 6.2.9 < 6.3, 6.3
Fixed upstream versions: 0, 6.1.162, 6.3, 6.6.22, 6.7.10, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 136ccb2041a5d1a475f845d3bc138550be6f5daa
CVE-2023-52659: kernel: x86/mm: Ensure input to pfn_to_kaddr() is treated as a 64-bit type
Component: kernel
Severity: Moderate
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

A vulnerability in the Linux kernel affected the x86/mm code, specifically in the `pfn_to_kaddr()` macro. The issue arises when the macro does not correctly handle input as a 64-bit type, causing crashes on 64-bit platforms, especially for SEV-SNP guests, when processing addresses above the 1TB range.


Affected upstream versions: 6.5
Fixed upstream versions: 0, 6.6.23, 6.7.11, 6.8.2, 6.9
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 325956b0173f11e98f90462be4829a8b8b0682ce
CVE-2023-52661: kernel: drm/tegra: rgb: Fix missing clk_put() in the error handling paths of tegra_dc_rgb_probe()
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

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

drm/tegra: rgb: Fix missing clk_put() in the error handling paths of tegra_dc_rgb_probe()

The Linux kernel CVE team has assigned CVE-2023-52661 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024051738-CVE-2023-52661-5539@gregkh/T


Affected upstream versions: 5.17
Fixed upstream versions: 0, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 5c8dc26e31b8b410ad1895e0d314def50c76eed0
CVE-2023-52662: kernel: drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

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

drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node

The Linux kernel CVE team has assigned CVE-2023-52662 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2023-52662-1536@gregkh/T


Affected upstream versions: 5.14
Fixed upstream versions: 0, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 03b1072616a8f7d6e8594f643b416a9467c83fbf
CVE-2023-52663: kernel: ASoC: SOF: amd: Fix memory leak in amd_sof_acp_probe()
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

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

ASoC: SOF: amd: Fix memory leak in amd_sof_acp_probe()

The Linux kernel CVE team has assigned CVE-2023-52663 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2023-52663-1045@gregkh/T


Affected upstream versions: 6.6
Fixed upstream versions: 0, 6.6.23, 6.7.11, 6.8.2, 6.9
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 88028c45d5871dfc449b2b0a27abf6428453a5ec
CVE-2023-52664: kernel: net: atlantic: eliminate double free in error handling logic
Component: kernel
Severity: Moderate
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

A double free vulnerability exists in the linux kernel error handling logic such that aq_ring_free could be called multiple times on the same ring,if the system is under stress and gets a memory allocation error.This vulnerability could lead to the loss of system availability.


Affected upstream versions: 4.11
Fixed upstream versions: 0, 6.1.77, 6.6.16, 6.7.4, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 0edb3ae8bfa31cd544b0c195bdec00e036002b5d
CVE-2023-52667: kernel: net/mlx5e: fix a potential double-free in fs_any_create_groups
Component: kernel
Severity: Moderate
CWE: CWE-415 (Double Free)
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

A double-free flaw was found in the Linux kernel ConnectX-4 and Connect-IB cards in the Mellanox driver. This issue could allow a local user to crash the system.

Statement: Red Hat Enterprise Linux 8 and 9 versions are affected.

Affected upstream versions: 5.13
Fixed upstream versions: 0, 5.15.149, 6.1.76, 6.6.15, 6.7.3, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 72a729868592752b5a294d27453da264106983b1
CVE-2023-52669: kernel: crypto: s390/aes - Fix buffer overread in CTR mode
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

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

crypto: s390/aes - Fix buffer overread in CTR mode

When processing the last block, the s390 ctr code will always read
a whole block, even if there isn't a whole block of data left.  Fix
this by using the actual length left and copy it into a buffer first
for processing.


Affected upstream versions: 3.0
Fixed upstream versions: 0, 5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: cd51e26a3b89706beec64f2d8296cfb1c34e0c79
CVE-2023-52672: kernel: pipe: wakeup wr_wait after setting max_usage
Component: kernel
Severity: Moderate
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

CVE-2023-52672 is a vulnerability in the Linux kernel's pipe subsystem caused by a regression in how pipes are resized. When a pipe is full and resized, incorrect handling of wakeups for writers can lead to deadlocks or system lockups. This issue has been resolved by ensuring that the pipe's usage limits are updated before wakeup calls are triggered, avoiding race conditions. Updating to a patched kernel version will mitigate this vulnerability and ensure system stability.


Affected upstream versions: 5.8
Fixed upstream versions: 0, 5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 162ae0e78bdabf84ef10c1293c4ed7865cb7d3c8
CVE-2023-52674: kernel: ALSA: scarlett2: Add clamp() in scarlett2_mixer_ctl_put()
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

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

ALSA: scarlett2: Add clamp() in scarlett2_mixer_ctl_put()

The Linux kernel CVE team has assigned CVE-2023-52674 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024051747-CVE-2023-52674-2aec@gregkh/T


Affected upstream versions: 5.4
Fixed upstream versions: 0, 5.15.148, 6.1.75, 6.6.14, 6.7.2, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: e517645ead5ea22c69d2a44694baa23fe1ce7c2b
CVE-2023-52675: kernel: powerpc/imc-pmu: Add a null pointer check in update_events_in_group()
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-17T00:00:00+00:00

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

powerpc/imc-pmu: Add a null pointer check in update_events_in_group()

kasprintf() returns a pointer to dynamically allocated memory
which can be NULL upon failure.


Affected upstream versions: 4.14
Fixed upstream versions: 0, 4.19.306, 5.10.209, 5.15.148, 5.4.268, 6.1.75, 6.6.14, 6.7.2, 6.8
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 75fc599bcdcb1de093c9ced2e3cccc832f3787f3