Amazon Linux 2023 Security Advisory: ALAS-2024-585
Advisory Release Date: 2024-04-10 22:17 Pacific
Advisory Updated Date: 2024-07-03 22:12 Pacific
FAQs regarding Amazon Linux ALAS/CVE Severity
2024-07-03: CVE-2024-26643 was added to this advisory.
2024-07-03: CVE-2024-26642 was added to this advisory.
2024-07-03: CVE-2024-36031 was added to this advisory.
2024-06-06: CVE-2024-35801 was added to this advisory.
2024-06-06: CVE-2024-35809 was added to this advisory.
2024-05-23: CVE-2024-26883 was added to this advisory.
2024-05-23: CVE-2024-26865 was added to this advisory.
2024-05-23: CVE-2024-26815 was added to this advisory.
2024-05-23: CVE-2024-26898 was added to this advisory.
Integer Overflow or Wraparound vulnerability in Linux kernel on x86 and ARM (md, raid, raid5 modules) allows Forced Integer Overflow. (CVE-2024-23307)
A malicious hypervisor can potentially break confidentiality and integrity of Linux SEV-SNP guests by injecting interrupts. (CVE-2024-25742)
In the Linux kernel, the following vulnerability has been resolved:
net: tls: handle backlogging of crypto requests
Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our
requests to the crypto API, crypto_aead_{encrypt,decrypt} can return
-EBUSY instead of -EINPROGRESS in valid situations. For example, when
the cryptd queue for AESNI is full (easy to trigger with an
artificially low cryptd.cryptd_max_cpu_qlen), requests will be enqueued
to the backlog but still processed. In that case, the async callback
will also be called twice: first with err == -EINPROGRESS, which it
seems we can just ignore, then with err == 0.
Compared to Sabrina's original patch this version uses the new
tls_*crypt_async_wait() helpers and converts the EBUSY to
EINPROGRESS to avoid having to modify all the error handling
paths. The handling is identical. (CVE-2024-26584)
In the Linux kernel, the following vulnerability has been resolved:
tls: fix race between tx work scheduling and socket close
Similarly to previous commit, the submitting thread (recvmsg/sendmsg)
may exit as soon as the async crypto handler calls complete().
Reorder scheduling the work before calling complete().
This seems more logical in the first place, as it's
the inverse order of what the submitting thread will do. (CVE-2024-26585)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: disallow anonymous set with timeout flag (CVE-2024-26642)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout (CVE-2024-26643)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: taprio: proper TCA_TAPRIO_TC_ENTRY_INDEX check (CVE-2024-26815)
In the Linux kernel, the following vulnerability has been resolved: rds: tcp: Fix use-after-free of net in reqsk_timer_handler(). syzkaller reported a warning of netns tracker [0] followed by KASAN splat [1] and another ref tracker warning [1]. syzkaller could not find a repro, but in the log, the only suspicious sequence was as follows: 18:26:22 executing program 1: r0 = socket$inet6_mptcp(0xa, 0x1, 0x106) ... connect$inet6(r0, &(0x7f0000000080)={0xa, 0x4001, 0x0, @loopback}, 0x1c) (async) The notable thing here is 0x4001 in connect(), which is RDS_TCP_PORT. (CVE-2024-26865)
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix stackmap overflow check on 32-bit arches (CVE-2024-26883)
In the Linux kernel, the following vulnerability has been resolved:
aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts (CVE-2024-26898)
In the Linux kernel, the following vulnerability has been resolved:
x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
In the Linux kernel, the following vulnerability has been resolved:
PCI/PM: Drain runtime-idle callbacks before driver removal (CVE-2024-35809)
In the Linux kernel, the following vulnerability has been resolved:
keys: Fix overwrite of key expiration on instantiation (CVE-2024-36031)
Affected Packages:
kernel
Issue Correction:
Run dnf update kernel --releasever 2023.4.20240416 to update your system.
aarch64:
kernel-libbpf-6.1.84-99.169.amzn2023.aarch64
kernel-modules-extra-common-6.1.84-99.169.amzn2023.aarch64
kernel-tools-6.1.84-99.169.amzn2023.aarch64
kernel-libbpf-devel-6.1.84-99.169.amzn2023.aarch64
python3-perf-6.1.84-99.169.amzn2023.aarch64
bpftool-6.1.84-99.169.amzn2023.aarch64
kernel-tools-debuginfo-6.1.84-99.169.amzn2023.aarch64
bpftool-debuginfo-6.1.84-99.169.amzn2023.aarch64
kernel-livepatch-6.1.84-99.169-1.0-0.amzn2023.aarch64
kernel-modules-extra-6.1.84-99.169.amzn2023.aarch64
perf-6.1.84-99.169.amzn2023.aarch64
perf-debuginfo-6.1.84-99.169.amzn2023.aarch64
kernel-tools-devel-6.1.84-99.169.amzn2023.aarch64
kernel-headers-6.1.84-99.169.amzn2023.aarch64
kernel-libbpf-static-6.1.84-99.169.amzn2023.aarch64
python3-perf-debuginfo-6.1.84-99.169.amzn2023.aarch64
kernel-debuginfo-6.1.84-99.169.amzn2023.aarch64
kernel-6.1.84-99.169.amzn2023.aarch64
kernel-debuginfo-common-aarch64-6.1.84-99.169.amzn2023.aarch64
kernel-devel-6.1.84-99.169.amzn2023.aarch64
src:
kernel-6.1.84-99.169.amzn2023.src
x86_64:
kernel-libbpf-devel-6.1.84-99.169.amzn2023.x86_64
bpftool-debuginfo-6.1.84-99.169.amzn2023.x86_64
kernel-libbpf-static-6.1.84-99.169.amzn2023.x86_64
python3-perf-6.1.84-99.169.amzn2023.x86_64
kernel-headers-6.1.84-99.169.amzn2023.x86_64
kernel-libbpf-6.1.84-99.169.amzn2023.x86_64
kernel-tools-debuginfo-6.1.84-99.169.amzn2023.x86_64
kernel-tools-6.1.84-99.169.amzn2023.x86_64
kernel-modules-extra-common-6.1.84-99.169.amzn2023.x86_64
kernel-tools-devel-6.1.84-99.169.amzn2023.x86_64
bpftool-6.1.84-99.169.amzn2023.x86_64
kernel-livepatch-6.1.84-99.169-1.0-0.amzn2023.x86_64
python3-perf-debuginfo-6.1.84-99.169.amzn2023.x86_64
perf-debuginfo-6.1.84-99.169.amzn2023.x86_64
perf-6.1.84-99.169.amzn2023.x86_64
kernel-modules-extra-6.1.84-99.169.amzn2023.x86_64
kernel-debuginfo-6.1.84-99.169.amzn2023.x86_64
kernel-6.1.84-99.169.amzn2023.x86_64
kernel-debuginfo-common-x86_64-6.1.84-99.169.amzn2023.x86_64
kernel-devel-6.1.84-99.169.amzn2023.x86_64