RHSA-2026:75747
Vulnerability from csaf_redhat - Published: 2026-10-05 12:22 - Updated: 2026-10-05 16:48A flaw was addressed in the Linux kernel’s nvme-pci driver related to how the driver calculated the worst-case number of PRP (Physical Region Page) lists required for a given I/O request. The implementation previously rounded the allocation to one list instead of correctly converting the maximum size into bytes before computing the divisor. Under certain rare conditions (for example, a 4 MiB transfer split across many physical segments on a queue that does not support SGLs), this calculation error could result in memory being corrupted beyond the size provided by the mempool. This memory corruption has been observed using kfence
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:bpftool-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:bpftool-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:bpftool-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:bpftool-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-0:4.18.0-553.171.1.el8_10.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-abi-stablelists-0:4.18.0-553.171.1.el8_10.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-core-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-core-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-core-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-core-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-core-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-core-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-core-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-core-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-devel-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-devel-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-devel-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-devel-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-modules-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-modules-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-modules-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-modules-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-modules-extra-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-modules-extra-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-modules-extra-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debug-modules-extra-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debuginfo-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debuginfo-common-aarch64-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debuginfo-common-ppc64le-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debuginfo-common-s390x-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-debuginfo-common-x86_64-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-devel-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-devel-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-devel-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-devel-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-doc-0:4.18.0-553.171.1.el8_10.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-modules-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-modules-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-modules-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-modules-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-modules-extra-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-modules-extra-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-modules-extra-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-modules-extra-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-libs-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-libs-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-tools-libs-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-zfcpdump-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-zfcpdump-core-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-zfcpdump-debuginfo-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-zfcpdump-devel-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-zfcpdump-modules-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:kernel-zfcpdump-modules-extra-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:perf-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:perf-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:perf-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:perf-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:perf-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:perf-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:perf-debuginfo-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:perf-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:python3-perf-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:python3-perf-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:python3-perf-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:python3-perf-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:python3-perf-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:python3-perf-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:python3-perf-debuginfo-0:4.18.0-553.171.1.el8_10.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.10.0.Z.MAIN.EUS:python3-perf-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debuginfo-common-aarch64-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debuginfo-common-ppc64le-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-debuginfo-common-x86_64-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-tools-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-tools-libs-devel-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-tools-libs-devel-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:kernel-tools-libs-devel-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:perf-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:perf-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:perf-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:python3-perf-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:python3-perf-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-8.10.0.Z.MAIN.EUS:python3-perf-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 | — |
Vendor Fix
fix
Workaround
|
A flaw was found in the Linux kernel's Remote Direct Memory Access (RDMA) bnxt_re driver. A local user could exploit a race condition that occurs when a Queue Pair (QP) is destroyed, but completion queue (CQ) polling continues. This can lead to a kernel panic, resulting in a Denial of Service (DoS) on the system.
A use-after-free flaw was identified in the Linux kernel’s media tuner (xc5000) driver. In the vulnerable code path, xc5000_release() calls cancel_delayed_work() to cancel a pending delayed work item (timer_sleep) without guaranteeing that the work handler has fully completed. Under a race condition, the underlying xc5000_priv structure may be freed while the delayed work item is still active, potentially resulting in a use-after-free when the work item subsequently dereferences the freed memory.
A flaw was found in the Linux kernel’s Global File System 2 implementation affecting distributed lock manager (DLM) handling in the gdlm_put_lock() function. During an unmount operation, if the DFL_UNMOUNT flag is set but the lockspace has not yet been fully released, remote callbacks (gdlm_ast() or gdlm_bast()) may still be invoked. This can result in dereferencing a freed glock (GFS2 lock) object, leading to undefined behavior and potential kernel instability or crashes.
A flaw was found in the Linux kernel's Quick Fair Queuing (QFQ) scheduler. The QFQ class deactivation logic incorrectly relies on a child qdisc's queue length (qlen) to determine if a class is active. A local user with `CAP_NET_ADMIN` capabilities can manipulate the child qlen into an unexpected state. This manipulation can destabilize the scheduling behavior, leading to traffic disruption or a Denial of Service (DoS) in the networking stack.
A flaw was found in the Linux kernel's Remote Direct Memory Access (RDMA) subsystem, specifically within the `ib_uverbs_post_send` function. A local user can exploit this vulnerability by providing an invalid work queue element size (`wqe_size`) from userspace without proper validation. This can lead to an out-of-bounds read from kernel heap memory, potentially disclosing sensitive kernel information to the user. Additionally, an excessively large `wqe_size` could trigger a kernel warning.
A flaw was found in the Linux kernel's GFS2 file system. During filesystem shutdown, quota data objects were freed without being properly removed from the Least Recently Used (LRU) list. This oversight could lead to a use-after-free vulnerability, where the system attempts to access memory that has already been released. Such a condition can cause system instability, crashes, or potentially allow a local attacker to escalate privileges or execute arbitrary code.
A flaw was found in the Linux kernel. A race condition in the `act_ct` module, specifically during the flow table lookup, can lead to a Use-After-Free (UAF) vulnerability. This occurs because a critical lock is released prematurely, allowing a memory object to be freed while still in use. An attacker could potentially exploit this to achieve privilege escalation.
A flaw was found in the Linux kernel's `af_alg` cryptography module. This vulnerability involves an arithmetic overflow when processing associated data lengths during the transmit buffer size check. A remote attacker could exploit this flaw by providing a specially crafted associated data length, potentially leading to a denial of service (DoS) due to system instability.
A flaw was found in the Linux kernel's Global File System 2 (GFS2) component. The `gfs2_logd()` function, responsible for log flushing, calls several log flushing functions without holding the required lock. This omission allows concurrent transactions to access shared resources without proper exclusion, which could lead to race conditions. Such conditions may result in system instability or data corruption, potentially causing a Denial of Service (DoS).
A flaw was found in the Linux kernel's mlx5 driver. The mlx5_query_nic_vport_mac_list function, which handles querying network interface card (NIC) virtual port (vport) MAC addresses, incorrectly sizes its internal buffer. When a Virtual Function (VF) vport is queried with a larger configured maximum, the firmware response can overflow this buffer. This leads to a memory corruption issue, specifically a slab-out-of-bounds error, which could potentially be exploited by an attacker to cause a denial of service or other system instability.
A flaw was found in the Linux kernel's IP Virtual Server (IPVS) component. During the `ip_vs_edit_service()` operation, the `svc->scheduler` pointer is cleared too late when unbinding an old scheduler. This improper handling allows packets to access previously freed scheduler data, leading to a use-after-free vulnerability. This can result in system instability or a denial of service.
A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) module, specifically within the Secure Virtual Machine (SVM) component. The `sev_dbg_crypt()` function, when handling encryption, incorrectly calculates the transfer length, leading to a page overflow. This memory corruption can result in a use-after-free condition. A local attacker could exploit this vulnerability to cause a denial of service or potentially escalate privileges.
A flaw was found in the Linux kernel's IP Generic Routing Encapsulation (ip_gre) component. This vulnerability allows a local attacker with network administration capabilities in one network namespace to modify a tunnel residing in a different network namespace where they lack privileges. This is due to an insufficient capability check in the `changelink()` function, which only verifies permissions in the device's network namespace and not the tunnel's. Successful exploitation could lead to unauthorized alteration of network tunnel configurations, potentially causing network disruption or redirection of traffic.
A flaw was found in the Linux kernel's `tunnels` module. This vulnerability occurs when the `iptunnel_pmtud_check_icmp()` function is called without the `skb transport header` being properly set. An attacker could exploit this condition to trigger an out-of-bound memory access, which may lead to system instability or a denial of service.
A flaw was found in the Linux kernel's tunnels module. This vulnerability, categorized as a Use-After-Free (UAF), arises from improper handling of network header pointers during certain packet processing operations. Specifically, functions responsible for building Internet Control Message Protocol (ICMP) packets for Path MTU Discovery (PMTUD) cache header information before memory reallocations, which can lead to the use of freed memory. A local attacker could potentially leverage this to cause a system crash, resulting in a denial of service.
A flaw was found in the Linux kernel's VXLAN (Virtual Extensible LAN) implementation. A local attacker, with `CAP_NET_ADMIN` (network administration capability) in one network namespace, could exploit an incorrect privilege check in the `rtnl changelink` path. This allows the attacker to modify the configuration of a VXLAN device whose underlying network interface resides in a different network namespace where the attacker lacks the necessary privileges, potentially leading to unauthorized network configuration changes.
A flaw was found in the Linux kernel's `ip6_gre` and `ip6erspan` tunnel drivers. The `changelink` functions in these drivers do not adequately verify administrative capabilities (`CAP_NET_ADMIN`) across different network namespaces. This allows a local attacker, who has `CAP_NET_ADMIN` in one network namespace but not in the tunnel's network namespace, to modify the tunnel's configuration. This could lead to unauthorized changes to network tunnel settings.
A flaw was found in the Linux kernel's netfilter component, specifically within the `nf_queue` functionality. When a bridged packet is queued to NFQUEUE, it can retain a reference to a bridge's private fake destination ('dst') even after the bridge teardown has begun. This can lead to a use-after-free vulnerability, where memory is accessed after it has been deallocated, potentially causing system instability or a denial of service.
A flaw was found in KVM (Kernel-based Virtual Machine). When the Advanced Virtual Interrupt Controller (AVIC) is inhibited while a nested guest (L2) is active, KVM fails to properly update x2APIC MSR intercepts for the primary guest (L1). This allows the L1 guest to read the host's APIC state, send arbitrary interrupts, and change task priority, ultimately leading to a Denial of Service (DoS) of the host system.
A flaw was found in the Linux kernel's netfilter Session Initiation Protocol (SIP) connection tracking module (nf_conntrack_sip). A remote attacker could send specially crafted SIP messages that cause an integer overflow during Network Address Translation (NAT) rewrite delta calculations. This overflow leads to a use-after-free vulnerability, which can result in memory corruption and potentially a denial of service or arbitrary code execution.
A flaw was found in the Linux kernel's IP Virtual Server (IPVS) component. When processing Internet Control Message Protocol (ICMP) errors for tunneled packets, the system can incorrectly use a stale IPv4 option offset. A remote attacker could exploit this by sending a specially crafted ICMP packet, leading to a stack out-of-bounds write. This vulnerability could result in a denial of service or potentially arbitrary code execution.
A flaw was found in the Linux kernel's ipvlan component. The ipvlan devices do not properly inherit `needed_headroom` and `needed_tailroom` from the physical device (`phy_dev`). This can lead to insufficient space being reserved for packet headers and trailers, potentially causing memory corruption, such as KASAN slab-use-after-free crashes, and resulting in a denial of service.
A flaw was found in the netfilter flowtable component of the Linux kernel. This vulnerability occurs due to a timing issue where the system's garbage collection can free a network flow while it is still being set up. This can lead to a 'use-after-free' condition, where the system attempts to access memory that has already been released. This memory corruption could potentially result in a system crash (denial of service) or, in certain circumstances, allow for arbitrary code execution.
A flaw was found in the Linux kernel's KVM s390 Virtual Shared Inter-Partition Emulation (VSIE) component. When shadowing crypto access bits from a format0 apcb, stale crypto bits were not properly cleared. This oversight could allow a nested guest to potentially access a device that should no longer be available, leading to unauthorized information disclosure or access to resources.
A flaw was found in the Linux kernel's NVMe (Non-Volatile Memory Express) over TCP (nvme-tcp) component. A malicious NVMe controller can exploit this vulnerability by sending a Ready to Transfer (R2T) command for a read request. The host system, failing to properly validate the request direction, will then send the contents of its read destination buffer to the controller. This can lead to the disclosure of stale kernel memory data, potentially revealing sensitive information.
A flaw was found in the NVMe (Non-Volatile Memory Express) driver of the Linux kernel. The nvme_alloc_ns() function's error handling path fails to wait for all SRCU (Sleepable Read-Copy Update) readers to complete before freeing a namespace structure. This oversight allows a concurrent reader to access a freed memory region, leading to a use-after-free vulnerability. A local attacker could potentially exploit this to cause a system crash or achieve arbitrary code execution.
A flaw was found in the Linux kernel's NVMe (Non-Volatile Memory Express) input/output control (ioctl) handling. An unprivileged local user could exploit this vulnerability by bypassing access checks in the `NVME_IOCTL_SUBMIT_IO` function. This allows them to perform unauthorized I/O operations on a partition device or write to a read-only file descriptor, potentially leading to privilege escalation or unauthorized data modification.
A flaw was found in the Linux kernel's netfilter connection tracking subsystem. The TCP option processing mechanism improperly assumes memory alignment when reading packet headers. A remote attacker could exploit this vulnerability by sending crafted TCP packets with misaligned SACK options through a system running conntrack (e.g., Linux firewall/NAT using iptables/nftables), causing a memory access fault that leads to a kernel panic and Denial of Service (DoS).
Loading 1.3 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.