Summary
This update for the Linux Kernel 4.12.14-122_201 fixes several issues.
The following security issues were fixed:
- CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index (bsc#1231204).
- CVE-2024-50302: HID: core: zero-initialize the report buffer (bsc#1233679).
- CVE-2022-48792: scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task (bsc#1228017).
- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance. (bsc#1229640).
- CVE-2021-47496: Fix flipped sign in tls_err_abort() calls (bsc#1225354)
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLE Live Patching 12 SP5 Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_54 | 14-2.1 |
Vulnerabilities 5
-
Medium 5.5CVE-2024-50302 Exploited
HID: core: zero-initialize the report buffer
In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be …
KEV Mar 4, 2025 -
Critical 9.8
net/tls: Fix flipped sign in tls_err_abort() calls
In the Linux kernel, the following vulnerability has been resolved: net/tls: Fix flipped sign in tls_err_abort() calls sk->sk_err appears to expect a positive value, a convention that ktls doesn't always follow and that leads to memory corruption in other cod…
-
High 7.8
scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task
In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_c…
-
High 7.8
netfilter: nf_queue: fix possible use-after-free
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_queue: fix possible use-after-free Eric Dumazet says: The sock_hold() side seems suspect, because there is no guarantee that sk_refcnt is not already 0. On failure, we cannot qu…
-
High 7.8
drm/amd/display: Check gpio_id before used as array index
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRU…
References
-
report
https://bugzilla.suse.com/1227656
-
report
https://bugzilla.suse.com/1228017
-
report
https://bugzilla.suse.com/1229640
-
report
https://bugzilla.suse.com/1231204
-
report
https://bugzilla.suse.com/1233679
-
web
https://www.suse.com/security/cve/CVE-2021-47496
-
web
https://www.suse.com/security/cve/CVE-2022-48792
-
web
https://www.suse.com/security/cve/CVE-2022-48911
-
web
https://www.suse.com/security/cve/CVE-2024-46818
-
web
https://www.suse.com/security/cve/CVE-2024-50302