RHSA-2024:0575
Vulnerability from csaf_redhat - Published: 2024-01-30 13:28 - Updated: 2026-11-11 18:39A flaw was found in the Linux kernel. This flaw allows a local attacker to escalate privileges or cause a Denial of Service (DoS) on the system. When a storage device is detached while writeback operations are actively completing, a race condition causes the kernel to access previously deallocated memory (a use-after-free condition). By triggering this timing condition, an attacker could crash the system or potentially execute arbitrary code.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.43.1.el8_8.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-abi-stablelists-0:4.18.0-477.43.1.el8_8.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-common-aarch64-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-common-ppc64le-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-common-s390x-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-common-x86_64-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-doc-0:4.18.0-477.43.1.el8_8.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-core-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-debuginfo-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-devel-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-modules-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-modules-extra-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.43.1.el8_8.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-common-aarch64-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-common-ppc64le-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-common-x86_64-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.43.1.el8_8.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.43.1.el8_8.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.43.1.el8_8.x86_64 | — |
Vendor Fix
fix
|
A vulnerabilty was found in Linux Kernel, where a speculative pointer dereference problem exists in the Linux Kernel on the do_prlimit() function. The resource argument value is controlled and is used in pointer arithmetic for the 'rlim' variable and can be used to leak the contents.
A memory corruption flaw was found in the Linux kernel’s human interface device (HID) subsystem in how a user inserts a malicious USB device. This flaw allows a local user to crash or potentially escalate their privileges on the system.
A memory leak flaw was found in the Linux kernel's TLS protocol. This issue could allow a local user unauthorized access to some memory.
CWE-843 - Access of Resource Using Incompatible TypeA use-after-free flaw was found in asus_kbd_backlight_set in drivers/hid/hid-asus.c in the Linux Kernel. This issue could allow an attacker to crash the system when plugging in or disconnecting a malicious USB device, which may lead to a kernel information leak problem.
A use-after-free flaw was found in vhost_net_set_backend in drivers/vhost/net.c in the virtio network subcomponent in the Linux kernel due to a double fget. This issue could allow a local attacker to crash the system, and could lead to a kernel information leak problem.
A use-after-free flaw was found in xgene_hwmon_remove in drivers/hwmon/xgene-hwmon.c in the Hardware Monitoring Linux Kernel driver (xgene-hwmon). This flaw could allow a local attacker to crash the system due to a race problem, possibly leading to a kernel information leak.
A use-after-free flaw was found in iscsi_sw_tcp_session_create in drivers/scsi/iscsi_tcp.c in the SCSI sub-component in the Linux Kernel. This issue could allow an attacker to leak kernel internal information.
An incorrect verifier pruning flaw was found in BPF in the Linux Kernel that may lead to unsafe code paths incorrectly marked as safe, resulting in arbitrary read/writes in kernel memory, lateral privilege escalation, and container escape.
A use-after-free flaw was found in r592_remove in drivers/memstick/host/r592.c in media access in the Linux Kernel. This issue may allow a local attacker to crash the system at device disconnect, possibly leading to a kernel information leak.
A use-after-free flaw was found in vcs_read in drivers/tty/vt/vc_screen.c in vc_screen in the Linux Kernel. This issue may allow an attacker with local user access to cause a system crash or leak internal kernel information.
An out-of-bounds memory write flaw was found in qfq_change_agg in net/sched/sch_qfq.c in the Traffic Control (QoS) subsystem in the Linux kernel. This flaw allows a local user to crash or potentially escalate their privileges on the system.
A flaw was found in the Linux kernel’s IP framework for transforming packets (XFRM subsystem). This issue may allow a malicious user with CAP_NET_ADMIN privileges to directly dereference a NULL pointer in xfrm_update_ae_params(), leading to a possible kernel crash and denial of service.
An out-of-bounds memory access flaw was found in the Linux kernel’s TUN/TAP device driver functionality in how a user generates a malicious (too big) networking packet when napi frags is enabled. This flaw allows a local user to crash or potentially escalate their privileges on the system.
A use-after-free vulnerability was found in the siano smsusb module in the Linux kernel. The bug occurs during device initialization when the siano device is plugged in. This flaw allows a local user to crash the system, causing a denial of service condition.
A use-after-free flaw was found in the Linux kernel's af_unix component that allows local privilege escalation. The unix_stream_sendpage() function tries to add data to the last skb in the peer's recv queue without locking the queue. This issue leads to a race condition where the unix_stream_sendpage() function could access a skb that is being released by garbage collection, resulting in a use-after-free issue.
A use-after-free flaw was found in the Linux kernel's net/sched: sch_hfsc (HFSC qdisc traffic control) component that can be exploited to achieve local privilege escalation. If a class with a link-sharing curve, for example, with the HFSC_FSC flag set, has a parent without a link-sharing curve, then init_vf() will call vttree_insert() on the parent, but vttree_remove() will be skipped in update_vf(). This leaves a dangling pointer that can cause a use-after-free issue.
A use-after-free vulnerability was found in drivers/nvme/target/tcp.c` in `nvmet_tcp_free_crypto` due to a logical bug in the NVMe/TCP subsystem in the Linux kernel. This issue may allow a malicious user to cause a use-after-free and double-free problem, which may permit remote code execution or lead to local privilege escalation.
A flaw was found in the Linux kernel's Performance Events system component. A condition can be triggered that allows data to be written past the end or before the beginning of the intended memory buffer. This issue may lead to a system crash, code execution, or local privilege escalation.
A denial of service flaw was found in atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel. This issue may allow a local attacker to cause a denial of service due to type confusion. Non-negative numbers could indicate a TC_ACT_SHOT condition rather than valid classification results.
A double-free flaw was found in the Linux kernel when the MPLS implementation handled sysctl allocation failures. This issue could allow a local user to cause a denial of service or possibly execute arbitrary code.
A NULL pointer dereference flaw was found in the az6027 driver in drivers/media/usb/dev-usb/az6027.c in the Linux Kernel. The message from user space is not checked properly before transferring into the device. This flaw allows a local user to crash the system or potentially cause a denial of service.
An out-of-bounds memory access flaw was found in the Linux kernel’s traffic control (QoS) subsystem in how a user triggers the qfq_change_class function with an incorrect MTU value of the network device used as lmax. This flaw allows a local user to crash or potentially escalate their privileges on the system.
A race condition vulnerability was found in the Linux kernel's Qualcomm EMAC Gigabit Ethernet Controller when the user physically removes the device before cleanup in the emac_remove function. This flaw can eventually result in a use-after-free issue, possibly leading to a system crash or other undefined behaviors.
A race condition was found in the Linux kernel's saa7134 device driver. This occurs when removing the module before cleanup in the saa7134_finidev function which can result in a use-after-free issue, possibly leading to a system crash or other undefined behaviors.
A race condition was found in the Linux kernel's dm1105 device driver when removing the module before cleanup in the dm1105_remove function. This can result in a use-after-free issue, possibly leading to a system crash or other undefined behaviors.
A race condition was found in the Linux kernel's r592 device driver, when removing the module before cleanup in the r592_remove function. This can result in a use-after-free issue, possibly leading to a system crash or other undefined behaviors.
A flaw was found in igb_configure_rx_ring in drivers/net/ethernet/intel/igb/igb_main.c in the IGB driver in the Linux kernel. An overflow of the contents from a packet that is too large will overflow into the kernel's ring buffer, leading to a system integrity issue.
A buffer overflow and null pointer dereference flaw was found in the Linux kernel's Secure Encrypted Virtualization (SEV) implementation for AMD functionality. This issue occurs when a user in SEV guest VM accesses MMIO registers, which could allow a local user to crash the system or escalate their privileges on the system.
A flaw was found in the Linux kernel's virtual console screen driver. A race condition during console operations can allow console data memory to be released while still being accessed during a read operation. An authenticated local user with access to virtual console devices could exploit this issue to trigger a use-after-free condition, leading to a kernel crash and Denial of Service (DoS).
A vulnerability was found in the Linux kernel's iscsi tcp drivers. Improper resource allocation management can lead to a use-after-free scenario, triggered when the userspace attempts to access the session host's `ipaddress` attribute while the kernel is performing a session teardown via `iscsi_session_teardown()`.
A flaw was found in the Linux kernel's Internet Small Computer System Interface (iSCSI) TCP subsystem. A local user can cause a Denial of Service (DoS) or potentially achieve privilege escalation by triggering a use-after-free vulnerability. This issue occurs due to a race condition when an iSCSI session is disconnected while another process queries the host IP address attribute through the sysfs virtual file system, causing the kernel to access memory that has already been deallocated.
In the Linux kernel, the following vulnerability has been resolved: xfrm: add NULL check in xfrm_update_ae_params Normally, x->replay_esn and x->preplay_esn should be allocated at xfrm_alloc_replay_state_esn(...) in xfrm_state_construct(...), hence the xfrm_update_ae_params(...) is okay to update them. However, the current implementation of xfrm_new_ae(...) allows a malicious user to directly dereference a NULL pointer and crash the kernel like below. BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 8253067 P4D 8253067 PUD 8e0e067 PMD 0 Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 PID: 98 Comm: poc.npd Not tainted 6.4.0-rc7-00072-gdad9774deaf1 #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.o4 RIP: 0010:memcpy_orig+0xad/0x140 Code: e8 4c 89 5f e0 48 8d 7f e0 73 d2 83 c2 20 48 29 d6 48 29 d7 83 fa 10 72 34 4c 8b 06 4c 8b 4e 08 c RSP: 0018:ffff888008f57658 EFLAGS: 00000202 RAX: 0000000000000000 RBX: ffff888008bd0000 RCX: ffffffff8238e571 RDX: 0000000000000018 RSI: ffff888007f64844 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff888008f57818 R13: ffff888007f64aa4 R14: 0000000000000000 R15: 0000000000000000 FS: 00000000014013c0(0000) GS:ffff88806d600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000054d8000 CR4: 00000000000006f0 Call Trace: <TASK> ? __die+0x1f/0x70 ? page_fault_oops+0x1e8/0x500 ? __pfx_is_prefetch.constprop.0+0x10/0x10 ? __pfx_page_fault_oops+0x10/0x10 ? _raw_spin_unlock_irqrestore+0x11/0x40 ? fixup_exception+0x36/0x460 ? _raw_spin_unlock_irqrestore+0x11/0x40 ? exc_page_fault+0x5e/0xc0 ? asm_exc_page_fault+0x26/0x30 ? xfrm_update_ae_params+0xd1/0x260 ? memcpy_orig+0xad/0x140 ? __pfx__raw_spin_lock_bh+0x10/0x10 xfrm_update_ae_params+0xe7/0x260 xfrm_new_ae+0x298/0x4e0 ? __pfx_xfrm_new_ae+0x10/0x10 ? __pfx_xfrm_new_ae+0x10/0x10 xfrm_user_rcv_msg+0x25a/0x410 ? __pfx_xfrm_user_rcv_msg+0x10/0x10 ? __alloc_skb+0xcf/0x210 ? stack_trace_save+0x90/0xd0 ? filter_irq_stacks+0x1c/0x70 ? __stack_depot_save+0x39/0x4e0 ? __kasan_slab_free+0x10a/0x190 ? kmem_cache_free+0x9c/0x340 ? netlink_recvmsg+0x23c/0x660 ? sock_recvmsg+0xeb/0xf0 ? __sys_recvfrom+0x13c/0x1f0 ? __x64_sys_recvfrom+0x71/0x90 ? do_syscall_64+0x3f/0x90 ? entry_SYSCALL_64_after_hwframe+0x72/0xdc ? copyout+0x3e/0x50 netlink_rcv_skb+0xd6/0x210 ? __pfx_xfrm_user_rcv_msg+0x10/0x10 ? __pfx_netlink_rcv_skb+0x10/0x10 ? __pfx_sock_has_perm+0x10/0x10 ? mutex_lock+0x8d/0xe0 ? __pfx_mutex_lock+0x10/0x10 xfrm_netlink_rcv+0x44/0x50 netlink_unicast+0x36f/0x4c0 ? __pfx_netlink_unicast+0x10/0x10 ? netlink_recvmsg+0x500/0x660 netlink_sendmsg+0x3b7/0x700 This Null-ptr-deref bug is assigned CVE-2023-3772. And this commit adds additional NULL check in xfrm_update_ae_params to fix the NPD.
In the Linux kernel, the following vulnerability has been resolved: sctp: check send stream number after wait_for_sndbuf This patch fixes a corner case where the asoc out stream count may change after wait_for_sndbuf. When the main thread in the client starts a connection, if its out stream count is set to N while the in stream count in the server is set to N - 2, another thread in the client keeps sending the msgs with stream number N - 1, and waits for sndbuf before processing INIT_ACK. However, after processing INIT_ACK, the out stream count in the client is shrunk to N - 2, the same to the in stream count in the server. The crash occurs when the thread waiting for sndbuf is awake and sends the msg in a non-existing stream(N - 1), the call trace is as below: KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f] Call Trace: <TASK> sctp_cmd_send_msg net/sctp/sm_sideeffect.c:1114 [inline] sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1777 [inline] sctp_side_effects net/sctp/sm_sideeffect.c:1199 [inline] sctp_do_sm+0x197d/0x5310 net/sctp/sm_sideeffect.c:1170 sctp_primitive_SEND+0x9f/0xc0 net/sctp/primitive.c:163 sctp_sendmsg_to_asoc+0x10eb/0x1a30 net/sctp/socket.c:1868 sctp_sendmsg+0x8d4/0x1d90 net/sctp/socket.c:2026 inet_sendmsg+0x9d/0xe0 net/ipv4/af_inet.c:825 sock_sendmsg_nosec net/socket.c:722 [inline] sock_sendmsg+0xde/0x190 net/socket.c:745 The fix is to add an unlikely check for the send stream number after the thread wakes up from the wait_for_sndbuf.
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. An attacker can trigger a Denial of Service (DoS) or potentially expose sensitive kernel memory by sending malformed SCTP packets. Because the kernel fails to properly validate buffer boundaries when processing incoming data chunks, an out-of-bounds memory read occurs. This vulnerability can lead to a system crash, disrupting services on the affected host.
A flaw was found in the Linux kernel's handling of AMD Secure Encrypted Virtualization (SEV). When processing unaligned memory addresses, the kernel miscalculates memory encryption boundaries by tracking page counts instead of exact byte sizes. During the live migration of a virtual machine, this error causes memory pages to be incorrectly marked as decrypted, leading to guest memory corruption and a Denial of Service (DoS).
Loading 1.5 MB of JSON…
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.