RHSA-2025:6966
Vulnerability from csaf_opensuse - Published: 2025-05-13 08:28 - Updated: 2026-11-12 17:01A flaw was found in the Linux kernel's xen-netfront component. During a live migration of a virtual machine, the Networked Asynchronous Packet Interface (NAPI) for the old network shared ring (sring) is not properly removed before a new one is established. A local attacker with low privileges could exploit this timing issue by enabling `busy_poll` or `busy_read` when resuming a virtual machine. This can lead to a NULL pointer dereference, causing a system crash and a denial of service.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.6.0.GA:kernel-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-64k-debug-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-64k-debug-devel-matched-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-64k-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-64k-devel-matched-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-devel-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-devel-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-devel-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-devel-matched-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-devel-matched-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-devel-matched-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debug-devel-matched-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debuginfo-common-aarch64-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debuginfo-common-ppc64le-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debuginfo-common-s390x-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-debuginfo-common-x86_64-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-devel-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-devel-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-devel-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-devel-matched-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-devel-matched-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-devel-matched-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-devel-matched-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-doc-0:5.14.0-570.12.1.el9_6.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-rt-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-rt-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-zfcpdump-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-zfcpdump-devel-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:kernel-zfcpdump-devel-matched-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:perf-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:perf-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:perf-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:perf-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:python3-perf-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:python3-perf-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:python3-perf-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:python3-perf-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:rtla-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:rtla-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:rtla-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:rtla-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:rv-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:rv-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:rv-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.6.0.GA:rv-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-0:5.14.0-570.12.1.el9_6.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-debug-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-debug-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-debug-modules-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-debug-modules-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-debug-modules-extra-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-modules-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-modules-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-64k-modules-extra-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-abi-stablelists-0:5.14.0-570.12.1.el9_6.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-core-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-core-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-core-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-core-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-core-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-core-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-extra-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-extra-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-extra-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-modules-extra-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debug-uki-virt-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debuginfo-common-aarch64-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debuginfo-common-ppc64le-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debuginfo-common-s390x-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-debuginfo-common-x86_64-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-core-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-core-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-extra-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-extra-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-extra-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-modules-extra-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-rt-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-rt-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-libs-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-libs-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-tools-libs-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-uki-virt-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-uki-virt-addons-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-zfcpdump-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-zfcpdump-core-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-zfcpdump-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-zfcpdump-modules-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-zfcpdump-modules-core-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:kernel-zfcpdump-modules-extra-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debuginfo-common-aarch64-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debuginfo-common-ppc64le-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debuginfo-common-s390x-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-debuginfo-common-x86_64-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-rt-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-rt-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-tools-libs-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-tools-libs-devel-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-tools-libs-devel-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:kernel-zfcpdump-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:libperf-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:libperf-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:libperf-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:libperf-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-debuginfo-common-x86_64-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debug-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debug-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debug-devel-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debug-kvm-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debug-modules-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debug-modules-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debug-modules-extra-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-devel-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-kvm-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-modules-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-modules-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-rt-modules-extra-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-debuginfo-common-aarch64-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-debuginfo-common-x86_64-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-debug-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-debug-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-debug-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-debug-modules-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-debug-modules-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-debug-modules-extra-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-modules-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-modules-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-64k-modules-extra-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-devel-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-modules-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-modules-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-modules-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-modules-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-modules-extra-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debug-modules-extra-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-devel-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-devel-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-modules-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-modules-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-modules-core-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-modules-core-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-modules-extra-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-rt-modules-extra-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:kernel-tools-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:libperf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.6.0.GA:python3-perf-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
A flaw was found in the Linux kernel's fscache component. A race condition can occur when a cached object is being discarded while another process attempts to use it. This timing issue can lead to a null pointer dereference, causing the system to crash and resulting in a denial of service.
A flaw was found in the Linux kernel's tracing component. A local attacker can exploit this vulnerability by repeatedly adding and removing dynamic tracing events. This action can lead to the reuse of event type numbers, causing the kernel to crash and resulting in a denial of service. Additionally, it may lead to information disclosure by misinterpreting data in the tracing ring buffer.
A flaw was found in the Linux kernel's `net: tun` module. A use-after-free vulnerability exists in the `tun_detach()` function. An attacker with administrative (root) privileges could exploit this by causing a network structure to be prematurely released and then accessed, leading to a system crash (denial of service). This vulnerability could potentially be leveraged for arbitrary code execution.
A flaw was found in the `hwmon` (hardware monitoring) subsystem of the Linux kernel, specifically within the `ibmpex` driver. This vulnerability is a Use-After-Free (UAF) error, which occurs when the system attempts to use memory that has already been released. An attacker with administrative privileges could exploit this flaw, potentially leading to a system crash or other unpredictable behavior.
In the Linux kernel, the following vulnerability has been resolved: erofs/zmap.c: Fix incorrect offset calculation Effective offset to add to length was being incorrectly calculated, which resulted in iomap->length being set to 0, triggering a WARN_ON in iomap_iter_done(). Fix that, and describe it in comments. This was reported as a crash by syzbot under an issue about a warning encountered in iomap_iter_done(), but unrelated to erofs. C reproducer: https://syzkaller.appspot.com/text?tag=ReproC&x=1037a6b2880000 Kernel config: https://syzkaller.appspot.com/text?tag=KernelConfig&x=e2021a61197ebe02 Dashboard link: https://syzkaller.appspot.com/bug?extid=a8e049cd3abd342936b6
CWE-682 - Incorrect CalculationIn the Linux kernel, the following vulnerability has been resolved: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud The page table check trigger BUG_ON() unexpectedly when collapse hugepage: ------------[ cut here ]------------ kernel BUG at mm/page_table_check.c:82! Internal error: Oops - BUG: 00000000f2000800 [#1] SMP Dumping ftrace buffer: (ftrace buffer empty) Modules linked in: CPU: 6 PID: 68 Comm: khugepaged Not tainted 6.1.0-rc3+ #750 Hardware name: linux,dummy-virt (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : page_table_check_clear.isra.0+0x258/0x3f0 lr : page_table_check_clear.isra.0+0x240/0x3f0 [...] Call trace: page_table_check_clear.isra.0+0x258/0x3f0 __page_table_check_pmd_clear+0xbc/0x108 pmdp_collapse_flush+0xb0/0x160 collapse_huge_page+0xa08/0x1080 hpage_collapse_scan_pmd+0xf30/0x1590 khugepaged_scan_mm_slot.constprop.0+0x52c/0xac8 khugepaged+0x338/0x518 kthread+0x278/0x2f8 ret_from_fork+0x10/0x20 [...] Since pmd_user_accessible_page() doesn't check if a pmd is leaf, it decrease file_map_count for a non-leaf pmd comes from collapse_huge_page(). and so trigger BUG_ON() unexpectedly. Fix this problem by using pmd_leaf() insteal of pmd_present() in pmd_user_accessible_page(). Moreover, use pud_leaf() for pud_user_accessible_page() too.
A flaw was found in the Linux kernel. On IBM zSystems (s390x) architectures, improper management of the stack pointer register can cause kernel stack corruption during execution. A local user can trigger this vulnerability to crash the operating system, resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: erofs: fix missing xas_retry() in fscache mode The xarray iteration only holds the RCU read lock and thus may encounter XA_RETRY_ENTRY if there's process modifying the xarray concurrently. This will cause oops when referring to the invalid entry. Fix this by adding the missing xas_retry(), which will make the iteration wind back to the root node if XA_RETRY_ENTRY is encountered.
In the Linux kernel, the following vulnerability has been resolved: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done.
In the Linux kernel, the following vulnerability has been resolved: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init Every iteration of for_each_available_child_of_node() decrements the reference count of the previous node. When breaking early from a for_each_available_child_of_node() loop, we need to explicitly call of_node_put() on the child node. Add missing of_node_put() to avoid refcount leak.
In the Linux kernel, the following vulnerability has been resolved: of: check previous kernel's ima-kexec-buffer against memory bounds Presently ima_get_kexec_buffer() doesn't check if the previous kernel's ima-kexec-buffer lies outside the addressable memory range. This can result in a kernel panic if the new kernel is booted with 'mem=X' arg and the ima-kexec-buffer was allocated beyond that range by the previous kernel. The panic is usually of the form below: $ sudo kexec --initrd initrd vmlinux --append='mem=16G' <snip> BUG: Unable to handle kernel data access on read at 0xc000c01fff7f0000 Faulting instruction address: 0xc000000000837974 Oops: Kernel access of bad area, sig: 11 [#1] <snip> NIP [c000000000837974] ima_restore_measurement_list+0x94/0x6c0 LR [c00000000083b55c] ima_load_kexec_buffer+0xac/0x160 Call Trace: [c00000000371fa80] [c00000000083b55c] ima_load_kexec_buffer+0xac/0x160 [c00000000371fb00] [c0000000020512c4] ima_init+0x80/0x108 [c00000000371fb70] [c0000000020514dc] init_ima+0x4c/0x120 [c00000000371fbf0] [c000000000012240] do_one_initcall+0x60/0x2c0 [c00000000371fcc0] [c000000002004ad0] kernel_init_freeable+0x344/0x3ec [c00000000371fda0] [c0000000000128a4] kernel_init+0x34/0x1b0 [c00000000371fe10] [c00000000000ce64] ret_from_kernel_thread+0x5c/0x64 Instruction dump: f92100b8 f92100c0 90e10090 910100a0 4182050c 282a0017 3bc00000 40810330 7c0802a6 fb610198 7c9b2378 f80101d0 <a1240000> 2c090001 40820614 e9240010 ---[ end trace 0000000000000000 ]--- Fix this issue by checking returned PFN range of previous kernel's ima-kexec-buffer with page_is_ram() to ensure correct memory bounds.
In the Linux kernel, the following vulnerability has been resolved: coresight: Clear the connection field properly coresight devices track their connections (output connections) and hold a reference to the fwnode. When a device goes away, we walk through the devices on the coresight bus and make sure that the references are dropped. This happens both ways: a) For all output connections from the device, drop the reference to the target device via coresight_release_platform_data() b) Iterate over all the devices on the coresight bus and drop the reference to fwnode if *this* device is the target of the output connection, via coresight_remove_conns()->coresight_remove_match(). However, the coresight_remove_match() doesn't clear the fwnode field, after dropping the reference, this causes use-after-free and additional refcount drops on the fwnode. e.g., if we have two devices, A and B, with a connection, A -> B. If we remove B first, B would clear the reference on B, from A via coresight_remove_match(). But when A is removed, it still has a connection with fwnode still pointing to B. Thus it tries to drops the reference in coresight_release_platform_data(), raising the bells like : [ 91.990153] ------------[ cut here ]------------ [ 91.990163] refcount_t: addition on 0; use-after-free. [ 91.990212] WARNING: CPU: 0 PID: 461 at lib/refcount.c:25 refcount_warn_saturate+0xa0/0x144 [ 91.990260] Modules linked in: coresight_funnel coresight_replicator coresight_etm4x(-) crct10dif_ce coresight ip_tables x_tables ipv6 [last unloaded: coresight_cpu_debug] [ 91.990398] CPU: 0 PID: 461 Comm: rmmod Tainted: G W T 5.19.0-rc2+ #53 [ 91.990418] Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Feb 1 2019 [ 91.990434] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 91.990454] pc : refcount_warn_saturate+0xa0/0x144 [ 91.990476] lr : refcount_warn_saturate+0xa0/0x144 [ 91.990496] sp : ffff80000c843640 [ 91.990509] x29: ffff80000c843640 x28: ffff800009957c28 x27: ffff80000c8439a8 [ 91.990560] x26: ffff00097eff1990 x25: ffff8000092b6ad8 x24: ffff00097eff19a8 [ 91.990610] x23: ffff80000c8439a8 x22: 0000000000000000 x21: ffff80000c8439c2 [ 91.990659] x20: 0000000000000000 x19: ffff00097eff1a10 x18: ffff80000ab99c40 [ 91.990708] x17: 0000000000000000 x16: 0000000000000000 x15: ffff80000abf6fa0 [ 91.990756] x14: 000000000000001d x13: 0a2e656572662d72 x12: 657466612d657375 [ 91.990805] x11: 203b30206e6f206e x10: 6f69746964646120 x9 : ffff8000081aba28 [ 91.990854] x8 : 206e6f206e6f6974 x7 : 69646461203a745f x6 : 746e756f63666572 [ 91.990903] x5 : ffff00097648ec58 x4 : 0000000000000000 x3 : 0000000000000027 [ 91.990952] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00080260ba00 [ 91.991000] Call trace: [ 91.991012] refcount_warn_saturate+0xa0/0x144 [ 91.991034] kobject_get+0xac/0xb0 [ 91.991055] of_node_get+0x2c/0x40 [ 91.991076] of_fwnode_get+0x40/0x60 [ 91.991094] fwnode_handle_get+0x3c/0x60 [ 91.991116] fwnode_get_nth_parent+0xf4/0x110 [ 91.991137] fwnode_full_name_string+0x48/0xc0 [ 91.991158] device_node_string+0x41c/0x530 [ 91.991178] pointer+0x320/0x3ec [ 91.991198] vsnprintf+0x23c/0x750 [ 91.991217] vprintk_store+0x104/0x4b0 [ 91.991238] vprintk_emit+0x8c/0x360 [ 91.991257] vprintk_default+0x44/0x50 [ 91.991276] vprintk+0xcc/0xf0 [ 91.991295] _printk+0x68/0x90 [ 91.991315] of_node_release+0x13c/0x14c [ 91.991334] kobject_put+0x98/0x114 [ 91.991354] of_node_put+0x24/0x34 [ 91.991372] of_fwnode_put+0x40/0x5c [ 91.991390] fwnode_handle_put+0x38/0x50 [ 91.991411] coresight_release_platform_data+0x74/0xb0 [coresight] [ 91.991472] coresight_unregister+0x64/0xcc [coresight] [ 91.991525] etm4_remove_dev+0x64/0x78 [coresight_etm4x] [ 91.991563] etm4_remove_amba+0x1c/0x2c [coresight_etm4x] [ 91.991598] amba_remove+0x3c/0x19c ---truncated---
A flaw was found in the Linux kernel. A local user can trigger a Denial of Service (DoS) in the coresight: trbe module. This occurs when the module is removed, as it improperly manages CPU hotplug instances, leading to a system warning and an error.
A flaw was found in the Linux kernel's Remote Processor Messaging (rpmsg) character device driver. When a remote processor device is stopped before closing an active character device endpoint, the driver attempts to release the default endpoint twice. This improper cleanup causes a reference counter underflow, leading to a use-after-free vulnerability. A local user can exploit this issue to trigger a kernel crash, resulting in a Denial of Service (DoS), or potentially corrupt system memory.
A context violation bug was found in the Linux kernel's CoreSight CTI (Cross Trigger Interface) driver in the hardware enable/disable functions. These functions are called from atomic context but attempt runtime PM operations that can sleep when communicating with firmware. This causes "sleeping function called from invalid context" errors and system hangs when enabling CoreSight tracing, particularly on ARM Juno platforms, resulting in denial of service.
In the Linux kernel, the following vulnerability has been resolved: lib/fonts: fix undefined behavior in bit shift for get_default_font Shifting signed 32-bit value by 31 bits is undefined, so changing significant bit to unsigned. The UBSAN warning calltrace like below: UBSAN: shift-out-of-bounds in lib/fonts/fonts.c:139:20 left shift of 1 by 31 places cannot be represented in type 'int' <TASK> dump_stack_lvl+0x7d/0xa5 dump_stack+0x15/0x1b ubsan_epilogue+0xe/0x4e __ubsan_handle_shift_out_of_bounds+0x1e7/0x20c get_default_font+0x1c7/0x1f0 fbcon_startup+0x347/0x3a0 do_take_over_console+0xce/0x270 do_fbcon_takeover+0xa1/0x170 do_fb_registered+0x2a8/0x340 fbcon_fb_registered+0x47/0xe0 register_framebuffer+0x294/0x4a0 __drm_fb_helper_initial_config_and_unlock+0x43c/0x880 [drm_kms_helper] drm_fb_helper_initial_config+0x52/0x80 [drm_kms_helper] drm_fbdev_client_hotplug+0x156/0x1b0 [drm_kms_helper] drm_fbdev_generic_setup+0xfc/0x290 [drm_kms_helper] bochs_pci_probe+0x6ca/0x772 [bochs] local_pci_probe+0x4d/0xb0 pci_device_probe+0x119/0x320 really_probe+0x181/0x550 __driver_probe_device+0xc6/0x220 driver_probe_device+0x32/0x100 __driver_attach+0x195/0x200 bus_for_each_dev+0xbb/0x120 driver_attach+0x27/0x30 bus_add_driver+0x22e/0x2f0 driver_register+0xa9/0x190 __pci_register_driver+0x90/0xa0 bochs_pci_driver_init+0x52/0x1000 [bochs] do_one_initcall+0x76/0x430 do_init_module+0x61/0x28a load_module+0x1f82/0x2e50 __do_sys_finit_module+0xf8/0x190 __x64_sys_finit_module+0x23/0x30 do_syscall_64+0x58/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK>
A flaw was found in the Linux kernel's `pci_endpoint_test` module. A local attacker with low privileges could exploit this vulnerability by providing a zero-length Direct Memory Access (DMA) mapping to the `dma_map_single()` function. This improper input validation can lead to a kernel panic, resulting in a Denial of Service (DoS) on the affected system.
A flaw was found in the Linux kernel's erofs filesystem. A local user can trigger a memory leak by exploiting a condition in the `z_erofs_register_pcluster()` function where a pcluster's block address is zero, leading to an unreleased reference count. This vulnerability can result in resource exhaustion, causing a Denial of Service (DoS) on the system.
A resource leak flaw was found in the Linux kernel's EROFS filesystem. When z_erofs_get_extent_compressedlen() fails, the corresponding meta buffer is not properly unmapped, leading to a memory leak over time.
CWE-772 - Missing Release of Resource after Effective LifetimeCVE-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.
[REJECTED CVE] In the Linux kernel, the following vulnerability has been resolved: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.
A flaw was found in the QED SR-IOV support in the Linux kernel. Improper validation of the value returned from the qed_iov_get_vf_info function can cause a NULL pointer dereference and result in a denial of service.
In the Linux kernel, the following vulnerability has been resolved: fs: prevent out-of-bounds array speculation when closing a file descriptor Google-Bug-Id: 114199369
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: qcom: Fix potential memory leak Function dwc3_qcom_probe() allocates memory for resource structure which is pointed by parent_res pointer. This memory is not freed. This leads to memory leak. Use stack memory to prevent memory leak. Found by Linux Verification Center (linuxtesting.org) with SVACE.
In the Linux kernel, the following vulnerability has been resolved: ovl: fix null pointer dereference in ovl_permission() Following process: P1 P2 path_lookupat link_path_walk inode_permission ovl_permission ovl_i_path_real(inode, &realpath) path->dentry = ovl_i_dentry_upper(inode) drop_cache __dentry_kill(ovl_dentry) iput(ovl_inode) ovl_destroy_inode(ovl_inode) dput(oi->__upperdentry) dentry_kill(upperdentry) dentry_unlink_inode upperdentry->d_inode = NULL realinode = d_inode(realpath.dentry) // return NULL inode_permission(realinode) inode->i_sb // NULL pointer dereference , will trigger an null pointer dereference at realinode: [ 335.664979] BUG: kernel NULL pointer dereference, address: 0000000000000002 [ 335.668032] CPU: 0 PID: 2592 Comm: ls Not tainted 6.3.0 [ 335.669956] RIP: 0010:inode_permission+0x33/0x2c0 [ 335.678939] Call Trace: [ 335.679165] <TASK> [ 335.679371] ovl_permission+0xde/0x320 [ 335.679723] inode_permission+0x15e/0x2c0 [ 335.680090] link_path_walk+0x115/0x550 [ 335.680771] path_lookupat.isra.0+0xb2/0x200 [ 335.681170] filename_lookup+0xda/0x240 [ 335.681922] vfs_statx+0xa6/0x1f0 [ 335.682233] vfs_fstatat+0x7b/0xb0 Fetch a reproducer in [Link]. Use the helper ovl_i_path_realinode() to get realinode and then do non-nullptr checking.
In the Linux kernel, the following vulnerability has been resolved: coresight: Fix memory leak in acpi_buffer->pointer There are memory leaks reported by kmemleak: ... unreferenced object 0xffff00213c141000 (size 1024): comm "systemd-udevd", pid 2123, jiffies 4294909467 (age 6062.160s) hex dump (first 32 bytes): 04 00 00 00 02 00 00 00 18 10 14 3c 21 00 ff ff ...........<!... 00 00 00 00 00 00 00 00 03 00 00 00 10 00 00 00 ................ backtrace: [<000000004b7c9001>] __kmem_cache_alloc_node+0x2f8/0x348 [<00000000b0fc7ceb>] __kmalloc+0x58/0x108 [<0000000064ff4695>] acpi_os_allocate+0x2c/0x68 [<000000007d57d116>] acpi_ut_initialize_buffer+0x54/0xe0 [<0000000024583908>] acpi_evaluate_object+0x388/0x438 [<0000000017b2e72b>] acpi_evaluate_object_typed+0xe8/0x240 [<000000005df0eac2>] coresight_get_platform_data+0x1b4/0x988 [coresight] ... The ACPI buffer memory (buf.pointer) should be freed. But the buffer is also used after returning from acpi_get_dsd_graph(). Move the temporary variables buf to acpi_coresight_parse_graph(), and free it before the function return to prevent memory leak.
A flaw was found in the Linux kernel's cdns3 USB driver. During the device resume process, the pm_runtime_set_active function was incorrectly called from within a spin lock, which is an atomic operation. This improper handling can lead to a system crash, resulting in a Denial of Service (DoS). A local attacker could potentially trigger this condition.
In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix handling of lrbp->cmd ufshcd_queuecommand() may be called two times in a row for a SCSI command before it is completed. Hence make the following changes: - In the functions that submit a command, do not check the old value of lrbp->cmd nor clear lrbp->cmd in error paths. - In ufshcd_release_scsi_cmd(), do not clear lrbp->cmd. See also scsi_send_eh_cmnd(). This commit prevents that the following appears if a command times out: WARNING: at drivers/ufs/core/ufshcd.c:2965 ufshcd_queuecommand+0x6f8/0x9a8 Call trace: ufshcd_queuecommand+0x6f8/0x9a8 scsi_send_eh_cmnd+0x2c0/0x960 scsi_eh_test_devices+0x100/0x314 scsi_eh_ready_devs+0xd90/0x114c scsi_error_handler+0x2b4/0xb70 kthread+0x16c/0x1e0
CWE-821 - Incorrect SynchronizationIn the Linux kernel, the following vulnerability has been resolved: media: v4l2-mem2mem: add lock to protect parameter num_rdy Getting below error when using KCSAN to check the driver. Adding lock to protect parameter num_rdy when getting the value with function: v4l2_m2m_num_src_bufs_ready/v4l2_m2m_num_dst_bufs_ready. kworker/u16:3: [name:report&]BUG: KCSAN: data-race in v4l2_m2m_buf_queue kworker/u16:3: [name:report&] kworker/u16:3: [name:report&]read-write to 0xffffff8105f35b94 of 1 bytes by task 20865 on cpu 7: kworker/u16:3: v4l2_m2m_buf_queue+0xd8/0x10c
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: initialize damo_filter->list from damos_new_filter() damos_new_filter() is not initializing the list field of newly allocated filter object. However, DAMON sysfs interface and DAMON_RECLAIM are not initializing it after calling damos_new_filter(). As a result, accessing uninitialized memory is possible. Actually, adding multiple DAMOS filters via DAMON sysfs interface caused NULL pointer dereferencing. Initialize the field just after the allocation from damos_new_filter().
A resource leak was found in the Linux kernel's s390 cryptographic device driver in the device creation path. When the dev_set_name function fails during creation of a zcrypt device node, the zcdn_create function returns an error without freeing the newly allocated device structure and associated resources. This creates a permanent memory leak, leading to resource exhaustion and denial of service.
In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: mcs: Fix NULL pointer dereferences When system is rebooted after creating macsec interface below NULL pointer dereference crashes occurred. This patch fixes those crashes by using correct order of teardown [ 3324.406942] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 3324.415726] Mem abort info: [ 3324.418510] ESR = 0x96000006 [ 3324.421557] EC = 0x25: DABT (current EL), IL = 32 bits [ 3324.426865] SET = 0, FnV = 0 [ 3324.429913] EA = 0, S1PTW = 0 [ 3324.433047] Data abort info: [ 3324.435921] ISV = 0, ISS = 0x00000006 [ 3324.439748] CM = 0, WnR = 0 .... [ 3324.575915] Call trace: [ 3324.578353] cn10k_mdo_del_secy+0x24/0x180 [ 3324.582440] macsec_common_dellink+0xec/0x120 [ 3324.586788] macsec_notify+0x17c/0x1c0 [ 3324.590529] raw_notifier_call_chain+0x50/0x70 [ 3324.594965] call_netdevice_notifiers_info+0x34/0x7c [ 3324.599921] rollback_registered_many+0x354/0x5bc [ 3324.604616] unregister_netdevice_queue+0x88/0x10c [ 3324.609399] unregister_netdev+0x20/0x30 [ 3324.613313] otx2_remove+0x8c/0x310 [ 3324.616794] pci_device_shutdown+0x30/0x70 [ 3324.620882] device_shutdown+0x11c/0x204 [ 966.664930] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 966.673712] Mem abort info: [ 966.676497] ESR = 0x96000006 [ 966.679543] EC = 0x25: DABT (current EL), IL = 32 bits [ 966.684848] SET = 0, FnV = 0 [ 966.687895] EA = 0, S1PTW = 0 [ 966.691028] Data abort info: [ 966.693900] ISV = 0, ISS = 0x00000006 [ 966.697729] CM = 0, WnR = 0 [ 966.833467] Call trace: [ 966.835904] cn10k_mdo_stop+0x20/0xa0 [ 966.839557] macsec_dev_stop+0xe8/0x11c [ 966.843384] __dev_close_many+0xbc/0x140 [ 966.847298] dev_close_many+0x84/0x120 [ 966.851039] rollback_registered_many+0x114/0x5bc [ 966.855735] unregister_netdevice_many.part.0+0x14/0xa0 [ 966.860952] unregister_netdevice_many+0x18/0x24 [ 966.865560] macsec_notify+0x1ac/0x1c0 [ 966.869303] raw_notifier_call_chain+0x50/0x70 [ 966.873738] call_netdevice_notifiers_info+0x34/0x7c [ 966.878694] rollback_registered_many+0x354/0x5bc [ 966.883390] unregister_netdevice_queue+0x88/0x10c [ 966.888173] unregister_netdev+0x20/0x30 [ 966.892090] otx2_remove+0x8c/0x310 [ 966.895571] pci_device_shutdown+0x30/0x70 [ 966.899660] device_shutdown+0x11c/0x204 [ 966.903574] __do_sys_reboot+0x208/0x290 [ 966.907487] __arm64_sys_reboot+0x20/0x30 [ 966.911489] el0_svc_handler+0x80/0x1c0 [ 966.915316] el0_svc+0x8/0x180 [ 966.918362] Code: f9400000 f9400a64 91220014 f94b3403 (f9400060) [ 966.924448] ---[ end trace 341778e799c3d8d7 ]---
A bounds-checking error was found in the Linux kernel Marvell OcteonTX2 network driver's initialization code. On systems with newer CN10K RPM or CN10KB RPM_USX hardware, a local user with privileges to initialize the driver can trigger driver probe, causing the driver to make incorrect assumptions about hardware topology and access Coherent Global Interconnect eXchange blocks and Logical MAC interfaces using invalid array indices, which leads to out-of-bounds memory access and denial of service through kernel panic.
A kernel warning vulnerability was found in the s390 architecture idle handling in the Linux kernel. The arch_cpu_idle() function was not marked as noinstr (no instrumentation), causing RCU and tracing warnings when ftrace is enabled. This can trigger kernel warnings and potential issues with tracing in idle paths on s390 systems.
A logic flaw was found in the Linux kernel's arm64 memory management subsystem. The virtual address range sanity check in create_mapping_noalloc() and update_mapping_prot() uses an incorrect condition that only excludes the KASAN shadow region and module region, rather than properly validating addresses translated via TTBR1. This check was the result of historical code changes that inadvertently introduced an erroneous condition.
A flaw was discovered in the virtio_pmem driver in the Linux kernel, where flush block I/O requests did not have the required REQ_OP_WRITE operation code assigned before submission. Under workloads involving persistent memory block devices — for example, running mkfs.xfs on a pmem device,this omission can lead to bio submission warnings and improper block I/O handling.
A kernel crash vulnerability was found in the Linux kernel's s390 dcssblk driver. Missing dax_remove_host() calls in the device removal path, combined with broken error handling in the device add path, cause stale xarray entries and list_add corruption. When a previously used gendisk pointer is reused, the kernel crashes with list corruption during subsequent device operations.
A reference count leak was found in the ARM AMBA bus driver. When AMBA devices are created from device tree, the of_node reference count is incremented but never decremented in amba_device_release(), causing gradual memory leaks.
CWE-911 - Improper Update of Reference CountIn the Linux kernel’s s390/vmem subsystem, a flaw exists in the handling of virtual memory area initialization when debug pagealloc is enabled. Under certain conditions, the kernel may access memory after it has been freed or mishandled during early boot or subsystem initialization, resulting in a use-after-free condition that can cause an early kernel crash or undefined behavior on affected s390 systems.
A flaw was found in the OverlayFS (ovl) component of the Linux kernel. A local user can trigger a null pointer dereference by performing a specific sequence of file system operations. This vulnerability occurs when the ovl_get_acl_rcu() function attempts to access a real inode that has been set to NULL due to a race condition during inode destruction. Successful exploitation leads to a kernel crash, causing a Denial of Service (DoS).
A stack trace handling issue was found in ARM64 kernels. Without CONFIG_FUNCTION_GRAPH_TRACER, the IRQ entry function is not properly marked, causing filter_irq_stacks() to fail and potentially causing stack depot overflow warnings under KASAN.
CWE-440 - Expected Behavior ViolationA flaw was found in the Linux kernel’s nouveau module. An out-of-bounds access issue can be triggered when the Output Resource is zero, resulting in a denial of service.
A flaw was found in the Linux kernel's Bluetooth subsystem. When closing a Synchronous Connection-Oriented (SCO) socket, a race condition between socket cleanup and a delayed timeout worker can cause the kernel to reference memory that has already been released. A local user could exploit this use-after-free vulnerability to crash the system, resulting in a Denial of Service (DoS), or potentially execute arbitrary code.
A flaw was found in the Linux kernel's net: phy: micrel component. Specifically, within the lan8814_get_sig_rx() and lan8814_get_sig_tx() functions, a null pointer dereference can occur if ptp_parse_header() returns a NULL ptp_header due to an abnormal or corrupted packet. A remote attacker could exploit this by sending specially crafted network packets, leading to a system crash and a denial of service.
A NULL pointer dereference flaw was found in btintel_read_version in the Linux kernel. This issue may result in a crash.
A flaw was found in the Linux kernel's Shared Memory Communications (SMC) subsystem. An unprivileged local user can cause a Denial of Service (DoS) by repeatedly creating network namespaces, triggering severe lock contention on core networking locks. This issue occurs because the SMC network initialization routine unnecessarily acquires the routing netlink (rtnl) lock even when no network devices are present, degrading system responsiveness and stalling network operations.
A denial of service vulnerability was found in the Linux kernel. No input validation is performed in the Bluetooth hci_sock function. This vulnerability could lead to a crash, resulting in the loss of system availability.
CVE-2024-35964 is a vulnerability in the Linux kernel’s Bluetooth ISO implementation. It occurs because the setsockopt function does not properly validate the size of user-provided data before copying it into kernel memory. This flaw can lead to buffer overflows, potentially resulting in crashes or code execution.
CVE-2024-35965 is a vulnerability in the Linux kernel's Bluetooth L2CAP implementation, caused by inadequate input length validation in the setsockopt function. This flaw allows overly large user-provided data to be copied into kernel memory, potentially leading to buffer overflows, system instability, or privilege escalation. The issue has been fixed by adding proper checks to ensure data size is within acceptable limits. Users should update their Linux kernel to the patched version to mitigate this risk.
This is a vulnerability in the Linux kernel's Bluetooth RFCOMM protocol. It occurs because the rfcomm_sock_setsockopt_old() function fails to properly validate the length of user-supplied data, leading to out-of-bounds memory reads. This flaw could result in system instability or crashes.
This CVE pertains to a vulnerability in the Linux kernel's Bluetooth subsystem, specifically within the SCO (Synchronous Connection-Oriented) protocol. The issue arises from the sco_sock_setsockopt() function, which copies data without properly validating the length of user input. This oversight can lead to a slab-out-of-bounds read, potentially causing system instability or crashes.
This CVE identifies a memory leak in the Linux kernel's Bluetooth subsystem, specifically within the hci_req_sync_complete() function. The issue arises because the function fails to release the previous synchronization request state before assigning a new one, leading to increased memory usage over time. This flaw can degrade system performance and potentially cause a denial of service.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HCI: Fix potential null-ptr-deref Fix potential null-ptr-deref in hci_le_big_sync_established_evt().
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: msft: fix slab-use-after-free in msft_do_close() Tying the msft->data lifetime to hdev by freeing it in hci_release_dev() to fix the following case: [use] msft_do_close() msft = hdev->msft_data; if (!msft) ...(1) <- passed. return; mutex_lock(&msft->filter_lock); ...(4) <- used after freed. [free] msft_unregister() msft = hdev->msft_data; hdev->msft_data = NULL; ...(2) kfree(msft); ...(3) <- msft is freed. ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0x8f/0xc30 kernel/locking/mutex.c:752 Read of size 8 at addr ffff888106cbbca8 by task kworker/u5:2/309
A use-after-free vulnerability exists in the Bluetooth stack of the Linux kernel. The l2cap_connect() does not return void during the function return, potentially leading to a loss of system availability.
A flaw was found in the Linux kernel's Bluetooth QCA driver. This vulnerability is caused by missing sanity checks when parsing firmware files before downloading them. A local attacker with low privileges could exploit this to corrupt memory beyond a vmalloced buffer, potentially leading to a system compromise affecting confidentiality, integrity, and availability.
in linux kernel bluetooth L2CAP, l2cap_le_flowctl_init() can cause both div-by-zero and an integer overflow since hdev->le_mtu may not fall in the valid range.
A buffer overflow flaw was found in of_modalias() in the Linux kernel, occurring after the first snprintf() call. This issue could result in loss of availability of the system.
A flaw was found in the Linux kernel's `sock_map` component. A local attacker could exploit a race condition between the `sock_map_close` and `sk_psock_put` functions. This race condition can lead to a null pointer dereference, which triggers a kernel warning and may result in a denial of service.
A vulnerability was found in the Linux kernel's DMA engine component in the irq_process_work_list() function. A possible use-after-free condition can occur during list iteration, which is because a descriptor may be freed while another thread is reusing it, potentially leading to access to freed memory.
A flaw was found in the Linux kernel in which certain sequences of network namespace activity can cause a use-after-free, resulting in a denial of service.
A flaw was found in the Linux kernel's Bluetooth Logical Link Control and Adaptation Protocol (L2CAP) implementation. A race condition between closing a socket and processing incoming packets allows kernel worker threads to access socket structures after they have been freed. A local attacker could exploit this timing issue to cause memory corruption, leading to a system crash and Denial of Service (DoS).
A flaw was found in the Linux kernel's net/iucv component. This vulnerability arises when a specific kernel configuration (CONFIG_CPUMASK_OFFSTACK=y) is enabled, allowing for explicit allocation of cpumask variables directly on the system's memory stack. An attacker could exploit this to trigger a stack overflow, potentially leading to a Denial of Service (DoS) condition, which would make the system unavailable.
A vulnerability was found in the Linux kernel's bluetooth subsystem in the function hci_le_big_sync_established_evt() where a lack of proper checks does not validate whether a received connection handle exceeds the maximum allowed value. This could lead to system instability or crashes.
In the Linux kernel, the following vulnerability has been resolved: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race Ensure that `i2c_lock' is held when setting interrupt latch and mask in pca953x_irq_bus_sync_unlock() in order to avoid races. The other (non-probe) call site pca953x_gpio_set_multiple() ensures the lock is held before calling pca953x_write_regs(). The problem occurred when a request raced against irq_bus_sync_unlock() approximately once per thousand reboots on an i.MX8MP based system. * Normal case 0-0022: write register AI|3a {03,02,00,00,01} Input latch P0 0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0 0-0022: write register AI|08 {ff,00,00,00,00} Output P3 0-0022: write register AI|12 {fc,00,00,00,00} Config P3 * Race case 0-0022: write register AI|08 {ff,00,00,00,00} Output P3 0-0022: write register AI|08 {03,02,00,00,01} *** Wrong register *** 0-0022: write register AI|12 {fc,00,00,00,00} Config P3 0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0
A flaw was found in the Linux kernel. The file descriptor duplication mechanism in the do_dup2() function does not sanitize array indexing against speculative execution. A local user can exploit this flaw through processor branch mispredictions to trigger speculative out-of-bounds memory reads, potentially leading to a Denial of Service (DoS) or information disclosure through side-channel observation.
In the Linux kernel, the following vulnerability has been resolved: ASoC: TAS2781: Fix tasdev_load_calibrated_data(). This function has a reversed if statement resulting in a no-op or leading to a NULL dereference.
ice in linux kernel permits VF driver to request more than designated limit of FDIR filters, which can lead to resource exhaustion for other VFs.
In the Linux kernel, the following vulnerability has been resolved: block: fix deadlock between sd_remove & sd_release Our test report the following hung task: [ 2538.459400] INFO: task "kworker/0:0":7 blocked for more than 188 seconds. [ 2538.459427] Call trace: [ 2538.459430] __switch_to+0x174/0x338 [ 2538.459436] __schedule+0x628/0x9c4 [ 2538.459442] schedule+0x7c/0xe8 [ 2538.459447] schedule_preempt_disabled+0x24/0x40 [ 2538.459453] __mutex_lock+0x3ec/0xf04 [ 2538.459456] __mutex_lock_slowpath+0x14/0x24 [ 2538.459459] mutex_lock+0x30/0xd8 [ 2538.459462] del_gendisk+0xdc/0x350 [ 2538.459466] sd_remove+0x30/0x60 [ 2538.459470] device_release_driver_internal+0x1c4/0x2c4 [ 2538.459474] device_release_driver+0x18/0x28 [ 2538.459478] bus_remove_device+0x15c/0x174 [ 2538.459483] device_del+0x1d0/0x358 [ 2538.459488] __scsi_remove_device+0xa8/0x198 [ 2538.459493] scsi_forget_host+0x50/0x70 [ 2538.459497] scsi_remove_host+0x80/0x180 [ 2538.459502] usb_stor_disconnect+0x68/0xf4 [ 2538.459506] usb_unbind_interface+0xd4/0x280 [ 2538.459510] device_release_driver_internal+0x1c4/0x2c4 [ 2538.459514] device_release_driver+0x18/0x28 [ 2538.459518] bus_remove_device+0x15c/0x174 [ 2538.459523] device_del+0x1d0/0x358 [ 2538.459528] usb_disable_device+0x84/0x194 [ 2538.459532] usb_disconnect+0xec/0x300 [ 2538.459537] hub_event+0xb80/0x1870 [ 2538.459541] process_scheduled_works+0x248/0x4dc [ 2538.459545] worker_thread+0x244/0x334 [ 2538.459549] kthread+0x114/0x1bc [ 2538.461001] INFO: task "fsck.":15415 blocked for more than 188 seconds. [ 2538.461014] Call trace: [ 2538.461016] __switch_to+0x174/0x338 [ 2538.461021] __schedule+0x628/0x9c4 [ 2538.461025] schedule+0x7c/0xe8 [ 2538.461030] blk_queue_enter+0xc4/0x160 [ 2538.461034] blk_mq_alloc_request+0x120/0x1d4 [ 2538.461037] scsi_execute_cmd+0x7c/0x23c [ 2538.461040] ioctl_internal_command+0x5c/0x164 [ 2538.461046] scsi_set_medium_removal+0x5c/0xb0 [ 2538.461051] sd_release+0x50/0x94 [ 2538.461054] blkdev_put+0x190/0x28c [ 2538.461058] blkdev_release+0x28/0x40 [ 2538.461063] __fput+0xf8/0x2a8 [ 2538.461066] __fput_sync+0x28/0x5c [ 2538.461070] __arm64_sys_close+0x84/0xe8 [ 2538.461073] invoke_syscall+0x58/0x114 [ 2538.461078] el0_svc_common+0xac/0xe0 [ 2538.461082] do_el0_svc+0x1c/0x28 [ 2538.461087] el0_svc+0x38/0x68 [ 2538.461090] el0t_64_sync_handler+0x68/0xbc [ 2538.461093] el0t_64_sync+0x1a8/0x1ac T1: T2: sd_remove del_gendisk __blk_mark_disk_dead blk_freeze_queue_start ++q->mq_freeze_depth bdev_release mutex_lock(&disk->open_mutex) sd_release scsi_execute_cmd blk_queue_enter wait_event(!q->mq_freeze_depth) mutex_lock(&disk->open_mutex) SCSI does not set GD_OWNS_QUEUE, so QUEUE_FLAG_DYING is not set in this scenario. This is a classic ABBA deadlock. To fix the deadlock, make sure we don't try to acquire disk->open_mutex after freezing the queue.
A use-after-free flaw was found in concurrent DPC and hot-removal in the Linux kernel. This issue may result in a crash.
The syzbot constructs a directory that has no dirblock but is non-inline, i.e. the first directory block is a hole. And no errors are reported when creating files in this directory. Then, we get a directory block without '.' and '..' but with a valid dentry. This may cause some code that relies on dot or dotdot (such as make_indexed_dir()) to crash.
A flaw was found in the Linux kernel's ext4 filesystem. When converting a directory to an indexed format, the system incorrectly assumes the presence of "dot" and "dotdot" entries. A local attacker could create a specially crafted filesystem image that, when processed during a rename operation, triggers an out-of-bounds access. This vulnerability can lead to a system crash, resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: sysctl: always initialize i_uid/i_gid Always initialize i_uid/i_gid inside the sysfs core so set_ownership() can safely skip setting them. Commit 5ec27ec735ba ("fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes.") added defaults for i_uid/i_gid when set_ownership() was not implemented. It also missed adjusting net_ctl_set_ownership() to use the same default values in case the computation of a better value failed.
A potential deadlock on __exfat_get_dentry_set was found in the Linux kernel. This may lead to decreased Availability.
In the Linux kernel, the following vulnerability has been resolved: mm/mglru: fix div-by-zero in vmpressure_calc_level() evict_folios() uses a second pass to reclaim folios that have gone through page writeback and become clean before it finishes the first pass, since folio_rotate_reclaimable() cannot handle those folios due to the isolation. The second pass tries to avoid potential double counting by deducting scan_control->nr_scanned. However, this can result in underflow of nr_scanned, under a condition where shrink_folio_list() does not increment nr_scanned, i.e., when folio_trylock() fails. The underflow can cause the divisor, i.e., scale=scanned+reclaimed in vmpressure_calc_level(), to become zero, resulting in the following crash: [exception RIP: vmpressure_work_fn+101] process_one_work at ffffffffa3313f2b Since scan_control->nr_scanned has no established semantics, the potential double counting has minimal risks. Therefore, fix the problem by not deducting scan_control->nr_scanned in evict_folios().
In the Linux kernel, the following vulnerability has been resolved: net: flow_dissector: use DEBUG_NET_WARN_ON_ONCE The following splat is easy to reproduce upstream as well as in -stable kernels. Florian Westphal provided the following commit: d1dab4f71d37 ("net: add and use __skb_get_hash_symmetric_net") but this complementary fix has been also suggested by Willem de Bruijn and it can be easily backported to -stable kernel which consists in using DEBUG_NET_WARN_ON_ONCE instead to silence the following splat given __skb_get_hash() is used by the nftables tracing infrastructure to to identify packets in traces. [69133.561393] ------------[ cut here ]------------ [69133.561404] WARNING: CPU: 0 PID: 43576 at net/core/flow_dissector.c:1104 __skb_flow_dissect+0x134f/ [...] [69133.561944] CPU: 0 PID: 43576 Comm: socat Not tainted 6.10.0-rc7+ #379 [69133.561959] RIP: 0010:__skb_flow_dissect+0x134f/0x2ad0 [69133.561970] Code: 83 f9 04 0f 84 b3 00 00 00 45 85 c9 0f 84 aa 00 00 00 41 83 f9 02 0f 84 81 fc ff ff 44 0f b7 b4 24 80 00 00 00 e9 8b f9 ff ff <0f> 0b e9 20 f3 ff ff 41 f6 c6 20 0f 84 e4 ef ff ff 48 8d 7b 12 e8 [69133.561979] RSP: 0018:ffffc90000006fc0 EFLAGS: 00010246 [69133.561988] RAX: 0000000000000000 RBX: ffffffff82f33e20 RCX: ffffffff81ab7e19 [69133.561994] RDX: dffffc0000000000 RSI: ffffc90000007388 RDI: ffff888103a1b418 [69133.562001] RBP: ffffc90000007310 R08: 0000000000000000 R09: 0000000000000000 [69133.562007] R10: ffffc90000007388 R11: ffffffff810cface R12: ffff888103a1b400 [69133.562013] R13: 0000000000000000 R14: ffffffff82f33e2a R15: ffffffff82f33e28 [69133.562020] FS: 00007f40f7131740(0000) GS:ffff888390800000(0000) knlGS:0000000000000000 [69133.562027] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [69133.562033] CR2: 00007f40f7346ee0 CR3: 000000015d200001 CR4: 00000000001706f0 [69133.562040] Call Trace: [69133.562044] <IRQ> [69133.562049] ? __warn+0x9f/0x1a0 [ 1211.841384] ? __skb_flow_dissect+0x107e/0x2860 [...] [ 1211.841496] ? bpf_flow_dissect+0x160/0x160 [ 1211.841753] __skb_get_hash+0x97/0x280 [ 1211.841765] ? __skb_get_hash_symmetric+0x230/0x230 [ 1211.841776] ? mod_find+0xbf/0xe0 [ 1211.841786] ? get_stack_info_noinstr+0x12/0xe0 [ 1211.841798] ? bpf_ksym_find+0x56/0xe0 [ 1211.841807] ? __rcu_read_unlock+0x2a/0x70 [ 1211.841819] nft_trace_init+0x1b9/0x1c0 [nf_tables] [ 1211.841895] ? nft_trace_notify+0x830/0x830 [nf_tables] [ 1211.841964] ? get_stack_info+0x2b/0x80 [ 1211.841975] ? nft_do_chain_arp+0x80/0x80 [nf_tables] [ 1211.842044] nft_do_chain+0x79c/0x850 [nf_tables]
In the Linux kernel, the following vulnerability has been resolved: dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume rm-raid devices will occasionally trigger the following warning when being resumed after a table load because DM_RECOVERY_RUNNING is set: WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid] The failing check is: WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)); This check is designed to make sure that the sync thread isn't registered, but md_check_recovery can set MD_RECOVERY_RUNNING without the sync_thread ever getting registered. Instead of checking if MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.
A flaw was found in the Linux kernel. A local attacker with elevated privileges could exploit a null pointer dereference vulnerability within the `scsi: lpfc` component. This occurs when memory allocation fails in the `lpfc_xcvr_data_show` function, causing a critical pointer to become null. Subsequent operations attempt to use this null pointer, which can lead to a system crash and result in a denial of service.
A NULL pointer dereference was found in the Linux kernel in case of DT error in ks_pcie_setup_rc_app_regs(). This may lead to a crash.
In the Linux kernel, the following vulnerability has been resolved: ext4: fix infinite loop when replaying fast_commit When doing fast_commit replay an infinite loop may occur due to an uninitialized extent_status struct. ext4_ext_determine_insert_hole() does not detect the replay and calls ext4_es_find_extent_range(), which will return immediately without initializing the 'es' variable. Because 'es' contains garbage, an integer overflow may happen causing an infinite loop in this function, easily reproducible using fstest generic/039. This commit fixes this issue by unconditionally initializing the structure in function ext4_es_find_extent_range(). Thanks to Zhang Yi, for figuring out the real problem!
A flaw was found in the Linux kernel's eXpress Data Path (XDP) subsystem. A local user with permissions to modify network interface settings could exploit this vulnerability to cause a Denial of Service (DoS) and crash the system. When cleaning up network memory resources during interface reconfiguration or teardown, the kernel attempts to acquire a blocking lock while in a non-blocking execution context. This invalid locking sequence can lead to a kernel hang or panic, disrupting host availability.
linux kernel's lib objagg can incorrectly permit object nesting in an unallowed circumstance, based on lack of appropriate checks stemming from assumption violations. The incorrect object creation from this assumption can lead to general protection fault.
A use-after-free (UAF) flaw was found in the proc_cpuset_show() function. This issue can allow an attacker to access the css of the root caused by a race condition when the cgroup_root should be freed when it is unmounted from the resource.
A flaw was found in the Linux kernel's device resource management (devres) component. When devm_free_percpu() is invoked to release allocated per-CPU memory, the kernel fails to free the underlying memory resources properly. A local user could exploit this flaw to continuously leak system memory, potentially resulting in resource exhaustion and a Denial of Service (DoS).
Improper handling of seqpacket_allow initialization was found in the Linux kernel in drivers/vhost/vsock.c.
A vulnerability was found in the Linux kernel. The fix addresses a race condition during file execution (exec), where a file’s permissions could change between an initial check and execution, potentially allowing unauthorized privilege escalation. Specifically, a non-privileged user could gain root access by exploiting a brief window during which file permissions are modified, such as when package managers update executables with setuid.
Bluetooth in the Linux kernel does not check for a NULL value, which could lead to dereferencing a null pointed and an eventual crash.
A denial of service vulnerability exists in the Linux kernel. A possible divide-by-0 is in the padata_mt_helper() function when the ps->chunk_size is 0. This vulnerability could result in a loss of system availability.
[REJECTED CVE] A NULL pointer dereference vulnerability has been identified in the Linux Kernel's ext4 filesystem. The issue occurs during concurrent write operations with inline data, where an ext4_force_shutdown is triggered due to inconsistencies like "block bitmap and bg descriptor inconsistent." This shutdown disrupts inline data handling, failing to restore the EXT4_STATE_MAY_INLINE_DATA flag. As a result, subsequent operations, such as in ext4_da_write_end, may attempt to dereference an unset page folio private pointer, leading to potential kernel crashes.
bpf in linux kernel permits passing in a modified CONST_PTR_TO_DYNPTR to a global function as an argument. BPF helpers can use the modified CONST_PTR_TO_DYNPTR within a global function context, which can lead to out of bounds memory accesses.
A flaw was found in the Linux kernel's MD (Multiple Device) RAID5 implementation. A local attacker, with privileges to manage RAID arrays, could trigger a kernel panic by reassembling a RAID5 array after an aborted reshape operation. This occurs due to an inconsistency between the `raid_disks` and `reshape position` values, leading to a failed integrity check during a subsequent reshape. Successful exploitation results in a system crash, causing a Denial of Service (DoS).
A flaw was found in the Linux kernel's General Purpose Input/Output (GPIO) subsystem. A local user can exploit this vulnerability by providing an out-of-range offset to the `gpio_ioctl()` function. This can lead to a speculative read of memory outside the intended GPIO descriptor array, potentially disclosing sensitive information through speculative execution side channels.
A flaw was found in the Linux kernel's Intel Infrastructure Data Path Function (idpf) network driver. This vulnerability can lead to a Denial of Service (DoS) caused by a system crash or potential memory corruption. During network queue teardown, interrupt vector resources are freed prematurely, leaving active pointers referencing already-released memory. A local user with administrative privileges could trigger this condition by manipulating network device queues.
A possible use-after-free was found in the Linux kernel in net/bridge/br_multicast.c.
A flaw was found in the Linux kernel's driver core, which can lead to a Denial of Service (DoS). A race condition exists between reading device event attributes in sysfs and detaching a device driver. A local user could trigger this flaw by accessing device attributes while a driver is being unbound or unloaded, causing a circular locking deadlock that hangs the system.
CWE-667 - Improper LockingA flaw was found in the Linux kernel. An unbalanced decrement and increment of the sched_smt_present counter can occur during CPU deactivation if the cpuset_cpu_inactive() function fails. A local attacker could exploit this condition, leading to a kernel warning and potentially a denial of service (DoS) as the system becomes unstable or crashes.
A flaw was found in the Linux kernel's Intel Infrastructure Data Path Function (idpf) driver. This vulnerability can lead to a Denial of Service (DoS) when a local privileged user initiates a network device soft reset. Due to improper memory management during the reset procedure, internal pointers are left referencing temporary structures after they are freed, triggering a use-after-free condition that causes a kernel crash.
In the Linux kernel, the following vulnerability has been resolved: cgroup/cpuset: fix panic caused by partcmd_update We find a bug as below: BUG: unable to handle page fault for address: 00000003 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 358 Comm: bash Tainted: G W I 6.6.0-10893-g60d6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4 RIP: 0010:partition_sched_domains_locked+0x483/0x600 Code: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9 RSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202 RAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000002fe80 RBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000 R10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002 R13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0 Call Trace: <TASK> ? show_regs+0x8c/0xa0 ? __die_body+0x23/0xa0 ? __die+0x3a/0x50 ? page_fault_oops+0x1d2/0x5c0 ? partition_sched_domains_locked+0x483/0x600 ? search_module_extables+0x2a/0xb0 ? search_exception_tables+0x67/0x90 ? kernelmode_fixup_or_oops+0x144/0x1b0 ? __bad_area_nosemaphore+0x211/0x360 ? up_read+0x3b/0x50 ? bad_area_nosemaphore+0x1a/0x30 ? exc_page_fault+0x890/0xd90 ? __lock_acquire.constprop.0+0x24f/0x8d0 ? __lock_acquire.constprop.0+0x24f/0x8d0 ? asm_exc_page_fault+0x26/0x30 ? partition_sched_domains_locked+0x483/0x600 ? partition_sched_domains_locked+0xf0/0x600 rebuild_sched_domains_locked+0x806/0xdc0 update_partition_sd_lb+0x118/0x130 cpuset_write_resmask+0xffc/0x1420 cgroup_file_write+0xb2/0x290 kernfs_fop_write_iter+0x194/0x290 new_sync_write+0xeb/0x160 vfs_write+0x16f/0x1d0 ksys_write+0x81/0x180 __x64_sys_write+0x21/0x30 x64_sys_call+0x2f25/0x4630 do_syscall_64+0x44/0xb0 entry_SYSCALL_64_after_hwframe+0x78/0xe2 RIP: 0033:0x7f44a553c887 It can be reproduced with cammands: cd /sys/fs/cgroup/ mkdir test cd test/ echo +cpuset > ../cgroup.subtree_control echo root > cpuset.cpus.partition cat /sys/fs/cgroup/cpuset.cpus.effective 0-3 echo 0-3 > cpuset.cpus // taking away all cpus from root This issue is caused by the incorrect rebuilding of scheduling domains. In this scenario, test/cpuset.cpus.partition should be an invalid root and should not trigger the rebuilding of scheduling domains. When calling update_parent_effective_cpumask with partcmd_update, if newmask is not null, it should recheck newmask whether there are cpus is available for parect/cs that has tasks.
A possible use-after-free was found in the Linux kernel in net/ipv6/ip6_output.c.
A flaw was found in the Linux kernel's bonding module. A local attacker with low privileges could exploit a null pointer dereference by manipulating network operations. This vulnerability can cause the system to crash, leading to a Denial of Service (DoS).
A race condition vulnerability was found in the Linux kernel. A race condition in the `fscache_cookie` subsystem leads to a NULL pointer dereference. The issue occurred when multiple processes accessed a cached file while it was being withdrawn, causing the cache's metadata to clear prematurely.
A flaw was found in the Linux kernel's Multipath TCP (MPTCP) path manager. A remote attacker could potentially exploit an issue where the `add_addr_accepted` counter is incorrectly decremented during subflow removal. This can lead to an inconsistent state within the MPTCP connection, potentially resulting in a denial of service.
A flaw was found in the Linux kernel's Multipath TCP (MPTCP) Path Manager. When a 'signal' endpoint is removed, the `local_addr_used` counter is incorrectly decremented, even though this counter is intended for 'subflow' endpoints. This miscounting can lead to an inconsistent state in the MPTCP Path Manager, potentially allowing a local attacker to cause a Denial of Service (DoS) by disrupting network connectivity.
A flaw use after free in the Linux kernel Network emulator (NETEM) functionality was found. A local user could use this flaw to crash the system or potentially escalate their privileges on the system.
Incorrect mappings in __vmap_pages_range_noflush() in the Linux kernel, may lead to memory corruption.
A flaw was found in the Linux kernel. Specifically, a double-free vulnerability exists in the `aacraid` SCSI driver. This occurs during probe failure when the `aac_init_adapter()` function frees memory for `aac_dev::queues` but fails to clear the pointer, leading `aac_probe_one()` to attempt a second free of the same memory. A local attacker could exploit this memory corruption to cause a denial of service (DoS) or potentially achieve arbitrary code execution.
A flaw was found in the Linux kernel's USB dwc3 core. During runtime suspend, the USB core could attempt to access an invalid event buffer address. This issue, particularly affecting Exynos platforms, can lead to System Memory Management Unit (SMMU) faults and other memory-related problems, potentially causing system instability or denial of service.
A flaw incorrect behavior in the Linux kernel Multipath TCP (MPTCP) functionality was found in the way. A local user could use this flaw to crash the system.
A flaw was found in the Linux kernel's `drm/amdgpu` component. A local attacker could exploit an out-of-bounds read vulnerability when processing `mc_data`. This could lead to the disclosure of sensitive information and potentially cause a denial of service.
A flaw was found in the Linux kernel's `amdgpu` graphics driver. This issue involves an out-of-bounds read when handling microcode (ucode) that was identified as a warning. While not a direct security vulnerability on its own, this flaw could potentially be leveraged by a local attacker with low privileges to trigger further issues that might lead to information disclosure or a denial of service.
A flaw was found in the `drm/amdgpu` component of the Linux kernel. An improper range check of the `fb_channel_number` could allow a local attacker to perform an out-of-bounds read. This could lead to information disclosure or a denial of service (DoS).
A flaw was found in the `drm/amdgpu` component of the Linux kernel. This out-of-bounds write vulnerability occurs due to an improper check of the ring type value. A local attacker with high privileges could exploit this flaw to cause data corruption, system instability, or potentially achieve privilege escalation.
A flaw was found in the Linux kernel. A local attacker with low privileges could exploit an out-of-bounds read vulnerability in the interrupt map walk function (`of_irq_parse_raw`). This flaw occurs when a device address is improperly handled, potentially leading to the disclosure of sensitive information and causing the system to become unavailable (denial of service).
A flaw was found in the Linux kernel's `uinput` interface. A local user could exploit this vulnerability by attempting to set up a `uinput` device with an unreasonably large number of slots. This action triggers a memory allocation failure, which can place a significant burden on the system, potentially leading to a Denial of Service (DoS).
A flaw was found in the Linux kernel's HID (Human Interface Device) subsystem, specifically within the driver for the Cougar 500k Gaming Keyboard. The `report_fixup` function failed to validate the size of the report descriptor before processing it. This oversight could allow a local attacker to trigger a slab-out-of-bounds read, potentially leading to information disclosure or a denial of service.
A flaw was found in the Linux kernel's PCI subsystem. A local attacker could exploit a missing bridge lock in the `pci_bus_lock()` function. This vulnerability allows users of `pci_reset_bus()` to trigger unlocked secondary bus resets, which can lead to a system crash, resulting in a denial of service.
A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) subsystem. This vulnerability allows BPF operations related to lwt_seg6local_prog_ops to be invoked via bpf_test_run() without proper initialization of a critical per-CPU variable. This could lead to a denial of service.
This CVE has been marked as Rejected by the assigning CNA.
No description is available for this CVE.
A flaw was found and resolved in the Linux kernel. DIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large negative number such as -9223372036854775808 is provided by the user.
A flaw was found in the Linux kernel's Powernv hotplug driver. This vulnerability allows a local attacker to trigger a system crash by attempting to remove or disable a PCIe device from the system. The issue arises from the driver trying to access a memory location that has already been cleared, leading to a null pointer dereference. This can result in a denial of service, making the system unavailable.
A flaw was found in the Linux kernel's `tcp_bpf` component. A local attacker with low privileges could exploit a vulnerability in the `tcp_bpf_sendmsg()` function. This flaw occurs when messages are handled in a specific way, leading to an unexpected negative return value. Successful exploitation can cause a kernel bug, resulting in a system crash and a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF The fscache_cookie_lru_timer is initialized when the fscache module is inserted, but is not deleted when the fscache module is removed. If timer_reduce() is called before removing the fscache module, the fscache_cookie_lru_timer will be added to the timer list of the current cpu. Afterwards, a use-after-free will be triggered in the softIRQ after removing the fscache module, as follows: ================================================================== BUG: unable to handle page fault for address: fffffbfff803c9e9 PF: supervisor read access in kernel mode PF: error_code(0x0000) - not-present page PGD 21ffea067 P4D 21ffea067 PUD 21ffe6067 PMD 110a7c067 PTE 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Tainted: G W 6.11.0-rc3 #855 Tainted: [W]=WARN RIP: 0010:__run_timer_base.part.0+0x254/0x8a0 Call Trace: <IRQ> tmigr_handle_remote_up+0x627/0x810 __walk_groups.isra.0+0x47/0x140 tmigr_handle_remote+0x1fa/0x2f0 handle_softirqs+0x180/0x590 irq_exit_rcu+0x84/0xb0 sysvec_apic_timer_interrupt+0x6e/0x90 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1a/0x20 RIP: 0010:default_idle+0xf/0x20 default_idle_call+0x38/0x60 do_idle+0x2b5/0x300 cpu_startup_entry+0x54/0x60 start_secondary+0x20d/0x280 common_startup_64+0x13e/0x148 </TASK> Modules linked in: [last unloaded: netfs] ================================================================== Therefore delete fscache_cookie_lru_timer when removing the fscahe module.
A flaw was found in the Linux kernel's userfaultfd component. A local user could exploit a race condition in the handling of huge page table entries (PMDs). This vulnerability can lead to a kernel crash, resulting in a Denial of Service (DoS). In older kernel versions, this flaw could also potentially cause memory corruption by misinterpreting memory regions.
A use-after-free vulnerability was found in the Linux kernel. If netem_dequeue() enqueues a packet to inner qdisc and that qdisc returns __NET_XMIT_STOLEN, the packet is dropped but qdisc_tree_reduce_backlog() is not called to update the parent's q.qlen.
A flaw was found in the `drm/amdgpu` component of the Linux kernel. This vulnerability occurs due to a missing null pointer check when dereferencing `amdgpu_hive_info *hive`. A local attacker could exploit this flaw to cause a system crash, leading to a denial of service (DoS).
A flaw was found in the Linux kernel's amdgpu graphics driver. A local attacker could exploit a division by zero error by triggering an invalid partition mode. This could lead to a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's `drm/amd/amdgpu` component. This vulnerability occurs due to insufficient validation of a `tbo resource pointer`. A local attacker could exploit this missing check to cause a system crash, leading to a denial of service.
A flaw was found in the Linux kernel's `drm/amdgpu` component. A local attacker with low privileges could trigger a null pointer dereference by interacting with the `nbio_v7_4` functionality when the `ras_manager` object is null. This could lead to a system crash, resulting in a denial of service.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn: remove irq disabling in vcn 5 suspend We do not directly enable/disable VCN IRQ in vcn 5.0.0. And we do not handle the IRQ state as well. So the calls to disable IRQ and set state are removed. This effectively gets rid of the warining of "WARN_ON(!amdgpu_irq_enabled(adev, src, type))" in amdgpu_irq_put().
A flaw was found in the Linux kernel, specifically within the ACPI (Advanced Configuration and Power Interface) CPU hotplug functionality. This vulnerability occurs when the system attempts to retrieve CPU information, and a missing CPU entry can lead to a NULL pointer dereference. A local attacker could potentially exploit this to trigger a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the `sch_cake` component of the Linux kernel. A local attacker could exploit a vulnerability in the bulk flow accounting logic, specifically during hash collision handling when host fairness is disabled. This can lead to an array out-of-bounds write due to a spurious decrement and wrap-around of a counter. If the `qdisc` (queueing discipline) is subsequently reconfigured to enable host fairness, the retained wrapped-around value is used as an array index, potentially causing a denial of service or information disclosure.
A flaw was found in the `drm/amdgpu` driver of the Linux kernel. A local attacker could exploit this vulnerability by triggering a null pointer dereference. This could lead to a system crash, causing a denial of service (DoS) on the affected system.
No description is available for this CVE.
A flaw was found in the Linux kernel. An out-of-bounds write vulnerability exists in the `nxp-fspi` driver when handling data that is not 4-byte aligned during write operations to the TX FIFO. A local attacker with administrative privileges could exploit this flaw, potentially leading to a system crash (denial of service) or arbitrary code execution.
in cpuhp_setup_state() a requisite condition of "hyperv_init_cpuhp > 0" for the hyperv case will never be true, and then hv_cpu_die() won't be called on all CPUs and the VP assist page will not be reset. This leads to corruption of the previous VP assist page and ultimately panic if the kexec kernel is using that memory. The hyperv_init_cpuhp condition should be removed entirely.
A flaw was found in the AMD Radeon graphics card driver in the Linux kernel. Out-of-bounds access can be triggered due to arrays being created based on the wrong number of maximum DMUB notification types available, resulting in a denial of service.
A flaw was found in the Linux kernel's pin multiplexing (pinmux) subsystem. A race condition can occur when concurrent processes attempt to request state changes for the same hardware pin without proper locking. A local attacker could exploit this timing window to trigger a null-pointer dereference, resulting in a kernel crash and a Denial of Service (DoS).
A flaw was found in the Linux kernel's fsnotify subsystem. When a parent directory stops watching its children, a race condition can occur during the clearing of PARENT_WATCHED flags. This contention on the inode->i_lock can lead to system unresponsiveness or softlockups, effectively causing a Denial of Service (DoS) for a local user.
A flaw was found in the Linux kernel. A race condition in the `__genradix_ptr_alloc()` function, responsible for allocating nodes in the generic radix tree, can occur when increasing the tree depth. This race can lead to a preallocated node retaining a pointer to an old root instead of being properly zeroed. An attacker could potentially exploit this to cause system instability or a denial of service.
A flaw was found in the Linux kernel related to the order of rate limits for ICMP messages. The sequence in which rate limiters are applied potentially allows a side-channel attack, resulting in information disclosure.
A flaw was found in the Netfilter and IPV6 functionality in the Linux kernel leading to a leak of 4 random bits. This issue may allow a remote user to preform an unauthorized read of random bits from the server.
In the Linux kernel, the following vulnerability has been resolved: vdpa/mlx5: Fix invalid mr resource destroy Certain error paths from mlx5_vdpa_dev_add() can end up releasing mr resources which never got initialized in the first place. This patch adds the missing check in mlx5_vdpa_destroy_mr_resources() to block releasing non-initialized mr resources. Reference trace: mlx5_core 0000:08:00.2: mlx5_vdpa_dev_add:3274:(pid 2700) warning: No mac address provisioned? BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 140216067 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 8 PID: 2700 Comm: vdpa Kdump: loaded Not tainted 5.14.0-496.el9.x86_64 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:vhost_iotlb_del_range+0xf/0xe0 [vhost_iotlb] Code: [...] RSP: 0018:ff1c823ac23077f0 EFLAGS: 00010246 RAX: ffffffffc1a21a60 RBX: ffffffff899567a0 RCX: 0000000000000000 RDX: ffffffffffffffff RSI: 0000000000000000 RDI: 0000000000000000 RBP: ff1bda1f7c21e800 R08: 0000000000000000 R09: ff1c823ac2307670 R10: ff1c823ac2307668 R11: ffffffff8a9e7b68 R12: 0000000000000000 R13: 0000000000000000 R14: ff1bda1f43e341a0 R15: 00000000ffffffea FS: 00007f56eba7c740(0000) GS:ff1bda269f800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000104d90001 CR4: 0000000000771ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ? show_trace_log_lvl+0x1c4/0x2df ? show_trace_log_lvl+0x1c4/0x2df ? mlx5_vdpa_free+0x3d/0x150 [mlx5_vdpa] ? __die_body.cold+0x8/0xd ? page_fault_oops+0x134/0x170 ? __irq_work_queue_local+0x2b/0xc0 ? irq_work_queue+0x2c/0x50 ? exc_page_fault+0x62/0x150 ? asm_exc_page_fault+0x22/0x30 ? __pfx_mlx5_vdpa_free+0x10/0x10 [mlx5_vdpa] ? vhost_iotlb_del_range+0xf/0xe0 [vhost_iotlb] mlx5_vdpa_free+0x3d/0x150 [mlx5_vdpa] vdpa_release_dev+0x1e/0x50 [vdpa] device_release+0x31/0x90 kobject_cleanup+0x37/0x130 mlx5_vdpa_dev_add+0x2d2/0x7a0 [mlx5_vdpa] vdpa_nl_cmd_dev_add_set_doit+0x277/0x4c0 [vdpa] genl_family_rcv_msg_doit+0xd9/0x130 genl_family_rcv_msg+0x14d/0x220 ? __pfx_vdpa_nl_cmd_dev_add_set_doit+0x10/0x10 [vdpa] ? _copy_to_user+0x1a/0x30 ? move_addr_to_user+0x4b/0xe0 genl_rcv_msg+0x47/0xa0 ? __import_iovec+0x46/0x150 ? __pfx_genl_rcv_msg+0x10/0x10 netlink_rcv_skb+0x54/0x100 genl_rcv+0x24/0x40 netlink_unicast+0x245/0x370 netlink_sendmsg+0x206/0x440 __sys_sendto+0x1dc/0x1f0 ? do_read_fault+0x10c/0x1d0 ? do_pte_missing+0x10d/0x190 __x64_sys_sendto+0x20/0x30 do_syscall_64+0x5c/0xf0 ? __count_memcg_events+0x4f/0xb0 ? mm_account_fault+0x6c/0x100 ? handle_mm_fault+0x116/0x270 ? do_user_addr_fault+0x1d6/0x6a0 ? do_syscall_64+0x6b/0xf0 ? clear_bhb_loop+0x25/0x80 ? clear_bhb_loop+0x25/0x80 ? clear_bhb_loop+0x25/0x80 ? clear_bhb_loop+0x25/0x80 ? clear_bhb_loop+0x25/0x80 entry_SYSCALL_64_after_hwframe+0x78/0x80
A flaw was found in the Linux kernel's nfsd component. A local attacker with low privileges could manipulate the `main.sqlite` file, causing a zero-length name to be processed. This improper handling leads to a null pointer dereference in the `nfs4_client_to_reclaim()` function, which can result in a system crash and a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: ext4: check stripe size compatibility on remount as well We disable stripe size in __ext4_fill_super if it is not a multiple of the cluster ratio however this check is missed when trying to remount. This can leave us with cases where stripe < cluster_ratio after remount:set making EXT4_B2C(sbi->s_stripe) become 0 that can cause some unforeseen bugs like divide by 0. Fix that by adding the check in remount path as well.
A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) and Linux Security Module (LSM) subsystems. A privileged local attacker could exploit this by attaching a BPF program that returns a positive number to the file_alloc_security hook. This misinterpretation of the return value by the file system can lead to a kernel panic, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's block device subsystem. An invalid pointer dereference could occur within the `blk_add_partition()` function due to incorrect error handling. A local attacker could exploit this vulnerability to cause a system crash, leading to a denial of service.
A flaw was found in the Budget Fair Queueing (BFQ) I/O scheduler in the Linux kernel. Handling merged chains of BFQ queues can cause a use-after-free condition and result in a denial of service.
A flaw was found in the Linux kernel's `sock_map` component, which handles network-related data structures. A local user could exploit this vulnerability by destroying a `sock_map` with a large number of buckets. This improper resource handling can lead to a soft lockup, causing the system to become unresponsive and resulting in a denial of service.
A flaw was found in the Linux kernel's mac80211 wireless subsystem. A local attacker with low privileges could trigger a condition where the system attempts to transmit data with interrupts disabled during the `ieee80211_do_stop()` function. This incorrect handling of network packet buffers (SKBs) can lead to system instability or a denial of service (DoS), making the system unresponsive.
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7915: fix oops on non-dbdc mt7986 mt7915_band_config() sets band_idx = 1 on the main phy for mt7986 with MT7975_ONE_ADIE or MT7976_ONE_ADIE. Commit 0335c034e726 ("wifi: mt76: fix race condition related to checking tx queue fill status") introduced a dereference of the phys array indirectly indexed by band_idx via wcid->phy_idx in mt76_wcid_cleanup(). This caused the following Oops on affected mt7986 devices: Unable to handle kernel read from unreadable memory at virtual address 0000000000000024 Mem abort info: ESR = 0x0000000096000005 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x05: level 1 translation fault Data abort info: ISV = 0, ISS = 0x00000005 CM = 0, WnR = 0 user pgtable: 4k pages, 39-bit VAs, pgdp=0000000042545000 [0000000000000024] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000 Internal error: Oops: 0000000096000005 [#1] SMP Modules linked in: ... mt7915e mt76_connac_lib mt76 mac80211 cfg80211 ... CPU: 2 PID: 1631 Comm: hostapd Not tainted 5.15.150 #0 Hardware name: ZyXEL EX5700 (Telenor) (DT) pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : mt76_wcid_cleanup+0x84/0x22c [mt76] lr : mt76_wcid_cleanup+0x64/0x22c [mt76] sp : ffffffc00a803700 x29: ffffffc00a803700 x28: ffffff80008f7300 x27: ffffff80003f3c00 x26: ffffff80000a7880 x25: ffffffc008c26e00 x24: 0000000000000001 x23: ffffffc000a68114 x22: 0000000000000000 x21: ffffff8004172cc8 x20: ffffffc00a803748 x19: ffffff8004152020 x18: 0000000000000000 x17: 00000000000017c0 x16: ffffffc008ef5000 x15: 0000000000000be0 x14: ffffff8004172e28 x13: ffffff8004172e28 x12: 0000000000000000 x11: 0000000000000000 x10: ffffff8004172e30 x9 : ffffff8004172e28 x8 : 0000000000000000 x7 : ffffff8004156020 x6 : 0000000000000000 x5 : 0000000000000031 x4 : 0000000000000000 x3 : 0000000000000001 x2 : 0000000000000000 x1 : ffffff80008f7300 x0 : 0000000000000024 Call trace: mt76_wcid_cleanup+0x84/0x22c [mt76] __mt76_sta_remove+0x70/0xbc [mt76] mt76_sta_state+0x8c/0x1a4 [mt76] mt7915_eeprom_get_power_delta+0x11e4/0x23a0 [mt7915e] drv_sta_state+0x144/0x274 [mac80211] sta_info_move_state+0x1cc/0x2a4 [mac80211] sta_set_sinfo+0xaf8/0xc24 [mac80211] sta_info_destroy_addr_bss+0x4c/0x6c [mac80211] ieee80211_color_change_finish+0x1c08/0x1e70 [mac80211] cfg80211_check_station_change+0x1360/0x4710 [cfg80211] genl_family_rcv_msg_doit+0xb4/0x110 genl_rcv_msg+0xd0/0x1bc netlink_rcv_skb+0x58/0x120 genl_rcv+0x34/0x50 netlink_unicast+0x1f0/0x2ec netlink_sendmsg+0x198/0x3d0 ____sys_sendmsg+0x1b0/0x210 ___sys_sendmsg+0x80/0xf0 __sys_sendmsg+0x44/0xa0 __arm64_sys_sendmsg+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x40/0xd0 el0_svc+0x14/0x4c el0t_64_sync_handler+0x100/0x110 el0t_64_sync+0x15c/0x160 Code: d2800002 910092c0 52800023 f9800011 (885f7c01) ---[ end trace 7e42dd9a39ed2281 ]--- Fix by using mt76_dev_phy() which will map band_idx to the correct phy for all hardware combinations.
A use-after-free flaw was found in the Linux kernel's mac80211-based wireless driver when firmware loading fails. This issue could allow a local user to crash the system as result of driver failure on an error path during power on.
A flaw was found in the Linux kernel's iommufd component. A local user could exploit this vulnerability by supplying specially crafted input values during an input/output virtual address (IOVA) allocation. This manipulation causes an overflow in the ALIGN() function, leading to the corruption of the selected memory area. The primary consequence of this flaw is a denial of service (DoS), which could make the system unavailable.
A flaw was found in the Linux kernel's Network File System Daemon (nfsd) component. This vulnerability occurs when the system attempts to allocate buffer space but fails, yet a related lookup operation succeeds. This leads to a resource leak where a cache entry is acquired but not properly released. A local attacker could exploit this issue to cause a Denial of Service (DoS) by exhausting system resources.
A flaw was found in the Linux kernel's mac80211 Wi-Fi subsystem. Incorrect handling of rate mask settings during off-channel transmissions could lead to unsupported rate warnings. This issue may result in a denial of service (DoS) for affected systems.
CWE-755 - Improper Handling of Exceptional ConditionsA flaw was found in the padata (parallel algorithm data) subsystem in the Linux kernel. An integer overflow can be triggered when processing more than 2^32 (~4GiB) padata objects, causing a deadlock in the serialization process, potentially resulting in a denial of service.
A flaw was found in the remap_file_pages function in mm/mmap.c in the Linux kernel, where it does not properly restrict execute access. This vulnerability allows local users to bypass intended SELinux W^X policy restrictions.
A use-after-free flaw was found in drivers/vhost/vdpa.c in the Linux kernel.
A flaw was found in the Linux kernel's rtw89 wireless driver. A local user can cause a Denial of Service (DoS) through a system crash triggered by a null pointer dereference. This issue occurs because the driver fails to properly validate the return value when handling wireless probe request frames.
A flaw was found in the Linux kernel's NVMe over RDMA (Remote Direct Memory Access) driver. The kernel may hang indefinitely during controller setup failure or teardown because the driver fails to resume the administrative queue before destroying it. This condition prevents pending requests from draining properly, allowing an attacker or network failure to cause a Denial of Service (DoS).
A flaw was found in the Linux kernel's Trusted Platform Module (TPM) driver. When a TPM command transmission fails, the driver does not properly clean up allocated resources, leading to a leak of transient handles. This resource exhaustion can result in a denial of service, making the TPM device unavailable for further operations.
A flaw was found in the Linux kernel's handling of Intel Software Guard Extensions (SGX) Non-Uniform Memory Access (NUMA) node search. When a system's current NUMA node lacks an Enclave Page Cache (EPC) section configured by firmware, and all other EPC sections are fully utilized, a local user could trigger a condition where the CPU becomes stuck in an indefinite loop. This issue can lead to a soft lockup, resulting in a Denial of Service (DoS) for the affected system.
A flaw was found in the Linux kernel. This vulnerability occurs in the ACPI (Advanced Configuration and Power Interface) system file system (sysfs) when processing the `_STR` method. If a non-buffer object is returned, the system attempts to access invalid memory. A local attacker could exploit this to cause the system to crash, leading to a denial of service, and potentially gain access to sensitive information.
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix helper writes to read-only maps Lonial found an issue that despite user- and BPF-side frozen BPF map (like in case of .rodata), it was still possible to write into it from a BPF program side through specific helpers having ARG_PTR_TO_{LONG,INT} as arguments. In check_func_arg() when the argument is as mentioned, the meta->raw_mode is never set. Later, check_helper_mem_access(), under the case of PTR_TO_MAP_VALUE as register base type, it assumes BPF_READ for the subsequent call to check_map_access_type() and given the BPF map is read-only it succeeds. The helpers really need to be annotated as ARG_PTR_TO_{LONG,INT} | MEM_UNINIT when results are written into them as opposed to read out of them. The latter indicates that it's okay to pass a pointer to uninitialized memory as the memory is written to anyway. However, ARG_PTR_TO_{LONG,INT} is a special case of ARG_PTR_TO_FIXED_SIZE_MEM just with additional alignment requirement. So it is better to just get rid of the ARG_PTR_TO_{LONG,INT} special cases altogether and reuse the fixed size memory types. For this, add MEM_ALIGNED to additionally ensure alignment given these helpers write directly into the args via *<ptr> = val. The .arg*_size has been initialized reflecting the actual sizeof(*<ptr>). MEM_ALIGNED can only be used in combination with MEM_FIXED_SIZE annotated argument types, since in !MEM_FIXED_SIZE cases the verifier does not know the buffer size a priori and therefore cannot blindly write *<ptr> = val.
A flaw was found in the `intel_rapl` driver within the `powercap` subsystem of the Linux kernel. An off-by-one error in the `get_rpi()` function, caused by an incorrect array boundary check, could allow a local attacker to perform an out-of-bounds read or write. This vulnerability may lead to information disclosure or a denial of service (DoS) on the affected system.
A flaw was found in the Linux kernel's cachefiles component. A local attacker could exploit a dentry (directory entry) leak caused by a concurrency issue between a lookup cookie and a cull operation. This flaw prevents the proper release of a reference count, which can lead to resource exhaustion and a denial of service when the affected filesystem is unmounted.
In the Linux kernel, the following vulnerability has been resolved: nfsd: map the EBADMSG to nfserr_io to avoid warning Ext4 will throw -EBADMSG through ext4_readdir when a checksum error occurs, resulting in the following WARNING. Fix it by mapping EBADMSG to nfserr_io. nfsd_buffered_readdir iterate_dir // -EBADMSG -74 ext4_readdir // .iterate_shared ext4_dx_readdir ext4_htree_fill_tree htree_dirblock_to_tree ext4_read_dirblock __ext4_read_dirblock ext4_dirblock_csum_verify warn_no_space_for_csum __warn_no_space_for_csum return ERR_PTR(-EFSBADCRC) // -EBADMSG -74 nfserrno // WARNING [ 161.115610] ------------[ cut here ]------------ [ 161.116465] nfsd: non-standard errno: -74 [ 161.117315] WARNING: CPU: 1 PID: 780 at fs/nfsd/nfsproc.c:878 nfserrno+0x9d/0xd0 [ 161.118596] Modules linked in: [ 161.119243] CPU: 1 PID: 780 Comm: nfsd Not tainted 5.10.0-00014-g79679361fd5d #138 [ 161.120684] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qe mu.org 04/01/2014 [ 161.123601] RIP: 0010:nfserrno+0x9d/0xd0 [ 161.124676] Code: 0f 87 da 30 dd 00 83 e3 01 b8 00 00 00 05 75 d7 44 89 ee 48 c7 c7 c0 57 24 98 89 44 24 04 c6 05 ce 2b 61 03 01 e8 99 20 d8 00 <0f> 0b 8b 44 24 04 eb b5 4c 89 e6 48 c7 c7 a0 6d a4 99 e8 cc 15 33 [ 161.127797] RSP: 0018:ffffc90000e2f9c0 EFLAGS: 00010286 [ 161.128794] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [ 161.130089] RDX: 1ffff1103ee16f6d RSI: 0000000000000008 RDI: fffff520001c5f2a [ 161.131379] RBP: 0000000000000022 R08: 0000000000000001 R09: ffff8881f70c1827 [ 161.132664] R10: ffffed103ee18304 R11: 0000000000000001 R12: 0000000000000021 [ 161.133949] R13: 00000000ffffffb6 R14: ffff8881317c0000 R15: ffffc90000e2fbd8 [ 161.135244] FS: 0000000000000000(0000) GS:ffff8881f7080000(0000) knlGS:0000000000000000 [ 161.136695] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 161.137761] CR2: 00007fcaad70b348 CR3: 0000000144256006 CR4: 0000000000770ee0 [ 161.139041] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 161.140291] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 161.141519] PKRU: 55555554 [ 161.142076] Call Trace: [ 161.142575] ? __warn+0x9b/0x140 [ 161.143229] ? nfserrno+0x9d/0xd0 [ 161.143872] ? report_bug+0x125/0x150 [ 161.144595] ? handle_bug+0x41/0x90 [ 161.145284] ? exc_invalid_op+0x14/0x70 [ 161.146009] ? asm_exc_invalid_op+0x12/0x20 [ 161.146816] ? nfserrno+0x9d/0xd0 [ 161.147487] nfsd_buffered_readdir+0x28b/0x2b0 [ 161.148333] ? nfsd4_encode_dirent_fattr+0x380/0x380 [ 161.149258] ? nfsd_buffered_filldir+0xf0/0xf0 [ 161.150093] ? wait_for_concurrent_writes+0x170/0x170 [ 161.151004] ? generic_file_llseek_size+0x48/0x160 [ 161.151895] nfsd_readdir+0x132/0x190 [ 161.152606] ? nfsd4_encode_dirent_fattr+0x380/0x380 [ 161.153516] ? nfsd_unlink+0x380/0x380 [ 161.154256] ? override_creds+0x45/0x60 [ 161.155006] nfsd4_encode_readdir+0x21a/0x3d0 [ 161.155850] ? nfsd4_encode_readlink+0x210/0x210 [ 161.156731] ? write_bytes_to_xdr_buf+0x97/0xe0 [ 161.157598] ? __write_bytes_to_xdr_buf+0xd0/0xd0 [ 161.158494] ? lock_downgrade+0x90/0x90 [ 161.159232] ? nfs4svc_decode_voidarg+0x10/0x10 [ 161.160092] nfsd4_encode_operation+0x15a/0x440 [ 161.160959] nfsd4_proc_compound+0x718/0xe90 [ 161.161818] nfsd_dispatch+0x18e/0x2c0 [ 161.162586] svc_process_common+0x786/0xc50 [ 161.163403] ? nfsd_svc+0x380/0x380 [ 161.164137] ? svc_printk+0x160/0x160 [ 161.164846] ? svc_xprt_do_enqueue.part.0+0x365/0x380 [ 161.165808] ? nfsd_svc+0x380/0x380 [ 161.166523] ? rcu_is_watching+0x23/0x40 [ 161.167309] svc_process+0x1a5/0x200 [ 161.168019] nfsd+0x1f5/0x380 [ 161.168663] ? nfsd_shutdown_threads+0x260/0x260 [ 161.169554] kthread+0x1c4/0x210 [ 161.170224] ? kthread_insert_work_sanity_check+0x80/0x80 [ 161.171246] ret_from_fork+0x1f/0x30
CWE-354 - Improper Validation of Integrity Check ValueIn the Linux kernel, the following vulnerability has been resolved: resource: fix region_intersects() vs add_memory_driver_managed() On a system with CXL memory, the resource tree (/proc/iomem) related to CXL memory may look like something as follows. 490000000-50fffffff : CXL Window 0 490000000-50fffffff : region0 490000000-50fffffff : dax0.0 490000000-50fffffff : System RAM (kmem) Because drivers/dax/kmem.c calls add_memory_driver_managed() during onlining CXL memory, which makes "System RAM (kmem)" a descendant of "CXL Window X". This confuses region_intersects(), which expects all "System RAM" resources to be at the top level of iomem_resource. This can lead to bugs. For example, when the following command line is executed to write some memory in CXL memory range via /dev/mem, $ dd if=data of=/dev/mem bs=$((1 << 10)) seek=$((0x490000000 >> 10)) count=1 dd: error writing '/dev/mem': Bad address 1+0 records in 0+0 records out 0 bytes copied, 0.0283507 s, 0.0 kB/s the command fails as expected. However, the error code is wrong. It should be "Operation not permitted" instead of "Bad address". More seriously, the /dev/mem permission checking in devmem_is_allowed() passes incorrectly. Although the accessing is prevented later because ioremap() isn't allowed to map system RAM, it is a potential security issue. During command executing, the following warning is reported in the kernel log for calling ioremap() on system RAM. ioremap on RAM at 0x0000000490000000 - 0x0000000490000fff WARNING: CPU: 2 PID: 416 at arch/x86/mm/ioremap.c:216 __ioremap_caller.constprop.0+0x131/0x35d Call Trace: memremap+0xcb/0x184 xlate_dev_mem_ptr+0x25/0x2f write_mem+0x94/0xfb vfs_write+0x128/0x26d ksys_write+0xac/0xfe do_syscall_64+0x9a/0xfd entry_SYSCALL_64_after_hwframe+0x4b/0x53 The details of command execution process are as follows. In the above resource tree, "System RAM" is a descendant of "CXL Window 0" instead of a top level resource. So, region_intersects() will report no System RAM resources in the CXL memory region incorrectly, because it only checks the top level resources. Consequently, devmem_is_allowed() will return 1 (allow access via /dev/mem) for CXL memory region incorrectly. Fortunately, ioremap() doesn't allow to map System RAM and reject the access. So, region_intersects() needs to be fixed to work correctly with the resource tree with "System RAM" not at top level as above. To fix it, if we found a unmatched resource in the top level, we will continue to search matched resources in its descendant resources. So, we will not miss any matched resources in resource tree anymore. In the new implementation, an example resource tree |------------- "CXL Window 0" ------------| |-- "System RAM" --| will behave similar as the following fake resource tree for region_intersects(, IORESOURCE_SYSTEM_RAM, ), |-- "System RAM" --||-- "CXL Window 0a" --| Where "CXL Window 0a" is part of the original "CXL Window 0" that isn't covered by "System RAM".
A flaw was found in the Linux kernel's ext4 filesystem. When the `ext4_find_extent()` function reallocates a path, it fails to update the original path pointer. A local attacker could exploit this by triggering a specific sequence of filesystem operations, leading to a null pointer dereference and causing a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's ext4 filesystem. This flaw occurs due to a double `brelse()` operation on a buffer in the extents path, meaning the same memory buffer is released twice. An attacker with administrative (root) privileges could exploit this vulnerability, leading to a system crash and a Denial of Service (DoS).
A flaw was found in the Linux kernel's ext4 filesystem driver. When modifying filesystem structures during extent allocation, the kernel fails to update an internal path reference after reallocation, resulting in a use-after-free vulnerability where memory is accessed after being deallocated. A local user with write privileges on an ext4 filesystem can exploit this issue during writeback or block mapping operations to cause a Denial of Service (DoS) by crashing the kernel, or potentially corrupt system memory.
A flaw was found in the Linux kernel's `ext4` filesystem. A memory corruption vulnerability, specifically a use-after-free, exists in the `ext4_split_extent_at()` function. This issue arises when an error during file extent creation causes the system to attempt to use memory that has already been released. An attacker with administrative privileges could exploit this to potentially cause a system crash or disclose sensitive information.
In the Linux kernel, the following vulnerability has been resolved: mm, slub: avoid zeroing kmalloc redzone Since commit 946fa0dbf2d8 ("mm/slub: extend redzone check to extra allocated kmalloc space than requested"), setting orig_size treats the wasted space (object_size - orig_size) as a redzone. However with init_on_free=1 we clear the full object->size, including the redzone. Additionally we clear the object metadata, including the stored orig_size, making it zero, which makes check_object() treat the whole object as a redzone. These issues lead to the following BUG report with "slub_debug=FUZ init_on_free=1": [ 0.000000] ============================================================================= [ 0.000000] BUG kmalloc-8 (Not tainted): kmalloc Redzone overwritten [ 0.000000] ----------------------------------------------------------------------------- [ 0.000000] [ 0.000000] 0xffff000010032858-0xffff00001003285f @offset=2136. First byte 0x0 instead of 0xcc [ 0.000000] FIX kmalloc-8: Restoring kmalloc Redzone 0xffff000010032858-0xffff00001003285f=0xcc [ 0.000000] Slab 0xfffffdffc0400c80 objects=36 used=23 fp=0xffff000010032a18 flags=0x3fffe0000000200(workingset|node=0|zone=0|lastcpupid=0x1ffff) [ 0.000000] Object 0xffff000010032858 @offset=2136 fp=0xffff0000100328c8 [ 0.000000] [ 0.000000] Redzone ffff000010032850: cc cc cc cc cc cc cc cc ........ [ 0.000000] Object ffff000010032858: cc cc cc cc cc cc cc cc ........ [ 0.000000] Redzone ffff000010032860: cc cc cc cc cc cc cc cc ........ [ 0.000000] Padding ffff0000100328b4: 00 00 00 00 00 00 00 00 00 00 00 00 ............ [ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.11.0-rc3-next-20240814-00004-g61844c55c3f4 #144 [ 0.000000] Hardware name: NXP i.MX95 19X19 board (DT) [ 0.000000] Call trace: [ 0.000000] dump_backtrace+0x90/0xe8 [ 0.000000] show_stack+0x18/0x24 [ 0.000000] dump_stack_lvl+0x74/0x8c [ 0.000000] dump_stack+0x18/0x24 [ 0.000000] print_trailer+0x150/0x218 [ 0.000000] check_object+0xe4/0x454 [ 0.000000] free_to_partial_list+0x2f8/0x5ec To address the issue, use orig_size to clear the used area. And restore the value of orig_size after clear the remaining area. When CONFIG_SLUB_DEBUG not defined, (get_orig_size()' directly returns s->object_size. So when using memset to init the area, the size can simply be orig_size, as orig_size returns object_size when CONFIG_SLUB_DEBUG not enabled. And orig_size can never be bigger than object_size.
A flaw was found in the Linux kernel. A local attacker with privileges to manage virtual machines could exploit this vulnerability by attaching a specific Intel Speed Select Technology (ISST) PCI device to a virtual machine. This action triggers a memory error known as a slab-out-of-bounds, which can cause the system to crash. The primary consequence of this flaw is a denial of service, making the system unavailable.
A flaw was found in the Linux kernel's ext4 filesystem. This use-after-free vulnerability occurs in the ext4_ext_show_leaf() function when a previously freed or reallocated memory path is incorrectly used. This issue is only triggered when the EXT_DEBUG option is enabled, which means it does not affect the system's normal operation or functionality in typical production environments. Exploitation would require administrative or root privileges.
A flaw was found in the Linux kernel's `drm/amdgpu` component. A missing list empty check in certain scenarios can lead to a null pointer dereference. This vulnerability could allow a local attacker to cause a system crash, resulting in a denial of service.
A flaw was found in the Linux kernel's x86 IO-APIC (Input/Output Advanced Programmable Interrupt Controller) component. A local attacker with low privileges could trigger an interrupt allocation failure under specific runtime conditions. This failure would lead to a kernel panic, resulting in a Denial of Service (DoS) for the affected system.
A flaw was found in the Linux kernel's wifi: rtw89 component. A local attacker with low privileges could exploit an out-of-bounds read vulnerability when loading TX power firmware elements. This flaw, caused by a loop reading beyond a valid memory region, may lead to information disclosure or denial of service.
A flaw was found in the Linux kernel in which certain wireless functionality could cause a null pointer dereference, resulting in a system crash.
A flaw was found in the Linux kernel's ath11k wireless driver. During packet receive processing, the driver uses an incorrect ring identifier when updating error statistics, resulting in an out-of-bounds array access. An attacker within wireless network range could potentially trigger this error path under specific conditions, leading to a system crash and denial of service (DoS) or memory corruption.
A flaw was found in the Linux kernel's `blk_iocost` subsystem. This vulnerability, caused by out-of-bounds shifts within the `ioc_forgive_debts()` function, can lead to undefined behavior. A local attacker could exploit this to cause a Denial of Service (DoS), making the system unavailable.
A flaw was found in the Linux kernel. A local user can trigger a kernel crash by performing specific memory operations involving `hugetlb` (a memory management feature) during the hot-removal of a memory device. This issue arises when the `dump_mapping()` function attempts to access an invalid memory address, leading to a Denial of Service (DoS) for the system.
In the Linux kernel, the following vulnerability has been resolved: ACPI: PAD: fix crash in exit_round_robin() The kernel occasionally crashes in cpumask_clear_cpu(), which is called within exit_round_robin(), because when executing clear_bit(nr, addr) with nr set to 0xffffffff, the address calculation may cause misalignment within the memory, leading to access to an invalid memory address. ---------- BUG: unable to handle kernel paging request at ffffffffe0740618 ... CPU: 3 PID: 2919323 Comm: acpi_pad/14 Kdump: loaded Tainted: G OE X --------- - - 4.18.0-425.19.2.el8_7.x86_64 #1 ... RIP: 0010:power_saving_thread+0x313/0x411 [acpi_pad] Code: 89 cd 48 89 d3 eb d1 48 c7 c7 55 70 72 c0 e8 64 86 b0 e4 c6 05 0d a1 02 00 01 e9 bc fd ff ff 45 89 e4 42 8b 04 a5 20 82 72 c0 <f0> 48 0f b3 05 f4 9c 01 00 42 c7 04 a5 20 82 72 c0 ff ff ff ff 31 RSP: 0018:ff72a5d51fa77ec8 EFLAGS: 00010202 RAX: 00000000ffffffff RBX: ff462981e5d8cb80 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000246 RDI: 0000000000000246 RBP: ff46297556959d80 R08: 0000000000000382 R09: ff46297c8d0f38d8 R10: 0000000000000000 R11: 0000000000000001 R12: 000000000000000e R13: 0000000000000000 R14: ffffffffffffffff R15: 000000000000000e FS: 0000000000000000(0000) GS:ff46297a800c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffe0740618 CR3: 0000007e20410004 CR4: 0000000000771ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ? acpi_pad_add+0x120/0x120 [acpi_pad] kthread+0x10b/0x130 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x1f/0x40 ... CR2: ffffffffe0740618 crash> dis -lr ffffffffc0726923 ... /usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./include/linux/cpumask.h: 114 0xffffffffc0726918 <power_saving_thread+776>: mov %r12d,%r12d /usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./include/linux/cpumask.h: 325 0xffffffffc072691b <power_saving_thread+779>: mov -0x3f8d7de0(,%r12,4),%eax /usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./arch/x86/include/asm/bitops.h: 80 0xffffffffc0726923 <power_saving_thread+787>: lock btr %rax,0x19cf4(%rip) # 0xffffffffc0740620 <pad_busy_cpus_bits> crash> px tsk_in_cpu[14] $66 = 0xffffffff crash> px 0xffffffffc072692c+0x19cf4 $99 = 0xffffffffc0740620 crash> sym 0xffffffffc0740620 ffffffffc0740620 (b) pad_busy_cpus_bits [acpi_pad] crash> px pad_busy_cpus_bits[0] $42 = 0xfffc0 ---------- To fix this, ensure that tsk_in_cpu[tsk_index] != -1 before calling cpumask_clear_cpu() in exit_round_robin(), just as it is done in round_robin_cpu(). [ rjw: Subject edit, avoid updates to the same value ]
A flaw was found in the Linux kernel's cfg80211 Wi-Fi subsystem. A local user could trigger a system crash, leading to a Denial of Service (DoS), due to an incorrect channel definition during the Channel Availability Check (CAC) startup when operating in a mode other than Access Point (AP) mode. This issue occurs because the channel definition is not properly set, resulting in a null channel pointer at the end of the CAC process.
A flaw was found in the Linux kernel's `ath9k_htc` Wi-Fi driver. An issue exists where the `skb_trim()` function, used for resetting the length of a socket buffer (skb) before resubmitting a USB Request Block (urb), can encounter an uninitialized length value in certain error conditions. A local attacker could potentially exploit this vulnerability to cause a denial of service by triggering these error paths.
A flaw was found in the Linux kernel's Realtek wireless driver (rtw89). When a system resumes from sleep using Wake on Wireless LAN (WoWLAN), an error recovery failure can cause the driver to attempt to add a network interface to an internal list twice. This issue leads to a kernel panic and results in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: ppp: do not assume bh is held in ppp_channel_bridge_input() Networking receive path is usually handled from BH handler. However, some protocols need to acquire the socket lock, and packets might be stored in the socket backlog is the socket was owned by a user process. In this case, release_sock(), __release_sock(), and sk_backlog_rcv() might call the sk->sk_backlog_rcv() handler in process context. sybot caught ppp was not considering this case in ppp_channel_bridge_input() : WARNING: inconsistent lock state 6.11.0-rc7-syzkaller-g5f5673607153 #0 Not tainted -------------------------------- inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage. ksoftirqd/1/24 [HC0[0]:SC1[1]:HE1:SE0] takes: ffff0000db7f11e0 (&pch->downl){+.?.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline] ffff0000db7f11e0 (&pch->downl){+.?.}-{2:2}, at: ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2272 [inline] ffff0000db7f11e0 (&pch->downl){+.?.}-{2:2}, at: ppp_input+0x16c/0x854 drivers/net/ppp/ppp_generic.c:2304 {SOFTIRQ-ON-W} state was registered at: lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5759 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline] _raw_spin_lock+0x48/0x60 kernel/locking/spinlock.c:154 spin_lock include/linux/spinlock.h:351 [inline] ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2272 [inline] ppp_input+0x16c/0x854 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0xfc/0x314 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv include/net/sock.h:1111 [inline] __release_sock+0x1a8/0x3d8 net/core/sock.c:3004 release_sock+0x68/0x1b8 net/core/sock.c:3558 pppoe_sendmsg+0xc8/0x5d8 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] __sys_sendto+0x374/0x4f4 net/socket.c:2204 __do_sys_sendto net/socket.c:2216 [inline] __se_sys_sendto net/socket.c:2212 [inline] __arm64_sys_sendto+0xd8/0xf8 net/socket.c:2212 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 irq event stamp: 282914 hardirqs last enabled at (282914): [<ffff80008b42e30c>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline] hardirqs last enabled at (282914): [<ffff80008b42e30c>] _raw_spin_unlock_irqrestore+0x38/0x98 kernel/locking/spinlock.c:194 hardirqs last disabled at (282913): [<ffff80008b42e13c>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline] hardirqs last disabled at (282913): [<ffff80008b42e13c>] _raw_spin_lock_irqsave+0x2c/0x7c kernel/locking/spinlock.c:162 softirqs last enabled at (282904): [<ffff8000801f8e88>] softirq_handle_end kernel/softirq.c:400 [inline] softirqs last enabled at (282904): [<ffff8000801f8e88>] handle_softirqs+0xa3c/0xbfc kernel/softirq.c:582 softirqs last disabled at (282909): [<ffff8000801fbdf8>] run_ksoftirqd+0x70/0x158 kernel/softirq.c:928 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&pch->downl); <Interrupt> lock(&pch->downl); *** DEADLOCK *** 1 lock held by ksoftirqd/1/24: #0: ffff80008f74dfa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x10/0x4c include/linux/rcupdate.h:325 stack backtrace: CPU: 1 UID: 0 PID: 24 Comm: ksoftirqd/1 Not tainted 6.11.0-rc7-syzkaller-g5f5673607153 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:319 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:326 __dump_sta ---truncated---
A flaw was found in the Linux kernel's network handling, specifically within the `qdisc_pkt_len_init()` function. A local user could exploit this by crafting a malicious Generic Segmentation Offload (GSO) packet. Insufficient sanity checks in the `virtio_net_hdr_to_skb()` function allow for an underflow in the packet length calculation. This underflow can lead to a denial of service (DoS) condition, making the system unavailable.
A flaw was found in the Linux kernel's Bluetooth L2CAP (Logical Link Control and Adaptation Protocol) component. This use-after-free vulnerability in the l2cap_connect function could allow a local attacker with administrative privileges to cause a denial of service or potentially execute arbitrary code.
A flaw was found in the Linux kernel's Bluetooth subsystem. When removing a Bluetooth controller while synchronous commands remain queued, the management interface does not properly handle the pending operations. A local user can exploit this condition to cause memory corruption, resulting in a system crash and a denial of service (DoS).
In the Linux kernel, the following vulnerability has been resolved: static_call: Replace pointless WARN_ON() in static_call_module_notify() static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That's not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn().
A flaw was found in the `jbd2` component of the Linux kernel. When an input/output (I/O) error occurs during the journal cleanup process, the system may continue to wait for journal space that cannot be freed. This improper error handling can lead to a system becoming unresponsive or experiencing a denial of service (DoS) condition.
A flaw was found in the Linux kernel's ext4 file system. This vulnerability allows a local user to cause a Denial of Service (DoS) or kernel memory corruption through a use-after-free condition. When an ext4 file system mount operation fails, an input/output (I/O) error can restart an error-reporting timer after it was scheduled for cancellation, leaving it running after the associated memory structure has been freed. A local user with permissions to mount storage devices could exploit this issue by mounting a corrupted file system image, resulting in an operating system crash.
A flaw was found in the Linux kernel's Advanced Configuration and Power Interface (ACPI) Component Architecture (ACPICA). A missing check for a null return value from a memory allocation function (`ACPI_ALLOCATE_ZEROED()`) in the `acpi_db_convert_to_package()` function can lead to a null pointer dereference. This vulnerability could allow a local attacker to cause a system crash, resulting in a denial of service.
No description is available for this CVE.
A flaw was found in the Linux kernel's ext4 filesystem. This vulnerability occurs when an attempt is made to mount an ext4 filesystem using the DX_HASH_SIPHASH default hash version on a filesystem that does not have the casefold feature enabled. Under these specific conditions, the mounting process will fail, leading to a denial of service by preventing access to the filesystem.
A flaw was found in the Linux kernel's `drm/amd/display` component. This vulnerability occurs because the `dml2_core_shared_mode_support` and `dml_core_mode_support` functions attempt to access an array element beyond its allocated size. A local attacker could potentially exploit this out-of-bounds write, leading to a system crash or denial of service.
A flaw was found in the Linux kernel's r8169 network driver. On systems using Realtek RTL8125 network adapters, the driver does not allocate a buffer large enough to store hardware tally counter values. As a result, the network adapter can perform Direct Memory Access (DMA) writes into unallocated memory, leading to kernel memory corruption and a potential Denial of Service (DoS) via a system crash.
A flaw was found in the Linux kernel's Network File System Daemon (NFSD). An attacker can exploit this by initiating an unlimited number of concurrent asynchronous copy operations. This can lead to resource exhaustion and a Denial of Service (DoS) condition, making the system unresponsive to legitimate requests.
A flaw was found in the Linux kernel's uprobes subsystem. When allocating memory for user space probes, the kernel maps an uninitialized memory page into a user space virtual memory area (VMA). A local user can exploit this vulnerability to read uninitialized memory contents, resulting in an information disclosure that may expose sensitive kernel data.
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Fix zero-division error when disabling tc cbs The commit b8c43360f6e4 ("net: stmmac: No need to calculate speed divider when offload is disabled") allows the "port_transmit_rate_kbps" to be set to a value of 0, which is then passed to the "div_s64" function when tc-cbs is disabled. This leads to a zero-division error. When tc-cbs is disabled, the idleslope, sendslope, and credit values the credit values are not required to be configured. Therefore, adding a return statement after setting the txQ mode to DCB when tc-cbs is disabled would prevent a zero-division error.
A flaw was found in the ext4 file system component of the Linux kernel. Improper pointer handling during journal replay operations can trigger a double-free condition, where the system attempts to release the same memory block twice. A local user could exploit this vulnerability by mounting a specially crafted or corrupted file system image, causing a kernel crash and resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's drm/amdkfd component. This use-after-free vulnerability occurs in the amdkfd_free_gtt_mem function due to incorrect pointer handling. An attacker with administrative privileges could exploit this flaw, potentially leading to information disclosure or a denial of service.
This CVE has been marked as Rejected by the assigning CNA.
A flaw was found in the Linux kernel's block subsystem. A local attacker with sufficient privileges could exploit an integer overflow vulnerability in the `BLKSECDISCARD` ioctl. This could lead to a near infinite loop within the `blkdev_issue_secure_erase()` function, resulting in a Denial of Service (DoS) for the affected system.
No description is available for this CVE.
A flaw was found in the Linux kernel's AFS (Andrew File System) module. This vulnerability occurs in the afs_wait_for_operation() function, where the op->server pointer is not properly validated for NULL before being used. A local attacker with low privileges could exploit this flaw, leading to a system crash and resulting in a denial of service.
In the Linux kernel, the following vulnerability has been resolved: static_call: Handle module init failure correctly in static_call_del_module() Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain. If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries. This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod. The problem is that key::mods is not a individual struct member of struct static_call_key, it's part of a union to save space: union { /* bit 0: 0 = mods, 1 = sites */ unsigned long type; struct static_call_mod *mods; struct static_call_site *sites; }; key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set. As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus. Cure it by checking whether the key has a sites or a mods pointer. If it's a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit. If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing. A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can't match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.
A flaw was found in the kernel's ext4 filesystem. When an EXT4_IOC_MIGRATE ioctl (input/output control) operation, requiring synchronous updates, races with a write(2) system call, it can lead to a deadlock. This deadlock occurs specifically when the CONFIG_PROVE_LOCKING option is enabled, potentially causing a Denial of Service (DoS) by making the system unresponsive.
A flaw was found in the Linux kernel's mwifiex Wi-Fi driver. A local attacker could exploit a field-spanning write vulnerability within the `mwifiex_cmd_802_11_scan_ext()` function. This issue could lead to a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's AMD P-State processor frequency driver. A local user could exploit this flaw to cause a Denial of Service (DoS) by crashing the system. This issue occurs because the driver fails to validate the return value of an internal CPU lookup function, leading to a null-pointer dereference.
In the Linux kernel, the following vulnerability has been resolved: exfat: fix memory leak in exfat_load_bitmap() If the first directory entry in the root directory is not a bitmap directory entry, 'bh' will not be released and reassigned, which will cause a memory leak.
A flaw was found in the Linux kernel. When the ext4 filesystem's fast-commit feature is enabled, a local attacker could trigger a condition where an uninitialized lock is accessed during the filesystem's replay path. This can lead to a system crash, resulting in a denial of service.
An inode corruption flaw was found in the Linux kernel's Ext4 file system functionality related to how a user can interrupt a write using the dax_iomap_rw()function. This flaw allows a local user to make non-fatal mistakes with Ext4, leading to a file system denial of service.
This CVE has been marked as Rejected by the assigning CNA.
In the Linux kernel, the following vulnerability has been resolved: kthread: unpark only parked kthread Calling into kthread unparking unconditionally is mostly harmless when the kthread is already unparked. The wake up is then simply ignored because the target is not in TASK_PARKED state. However if the kthread is per CPU, the wake up is preceded by a call to kthread_bind() which expects the task to be inactive and in TASK_PARKED state, which obviously isn't the case if it is unparked. As a result, calling kthread_stop() on an unparked per-cpu kthread triggers such a warning: WARNING: CPU: 0 PID: 11 at kernel/kthread.c:525 __kthread_bind_mask kernel/kthread.c:525 <TASK> kthread_stop+0x17a/0x630 kernel/kthread.c:707 destroy_workqueue+0x136/0xc40 kernel/workqueue.c:5810 wg_destruct+0x1e2/0x2e0 drivers/net/wireguard/device.c:257 netdev_run_todo+0xe1a/0x1000 net/core/dev.c:10693 default_device_exit_batch+0xa14/0xa90 net/core/dev.c:11769 ops_exit_list net/core/net_namespace.c:178 [inline] cleanup_net+0x89d/0xcc0 net/core/net_namespace.c:640 process_one_work kernel/workqueue.c:3231 [inline] process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312 worker_thread+0x86d/0xd70 kernel/workqueue.c:3393 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Fix this with skipping unecessary unparking while stopping a kthread.
In the Linux kernel, the following vulnerability has been resolved: device-dax: correct pgoff align in dax_set_mapping() pgoff should be aligned using ALIGN_DOWN() instead of ALIGN(). Otherwise, vmf->address not aligned to fault_size will be aligned to the next alignment, that can result in memory failure getting the wrong address. It's a subtle situation that only can be observed in page_mapped_in_vma() after the page is page fault handled by dev_dax_huge_fault. Generally, there is little chance to perform page_mapped_in_vma in dev-dax's page unless in specific error injection to the dax device to trigger an MCE - memory-failure. In that case, page_mapped_in_vma() will be triggered to determine which task is accessing the failure address and kill that task in the end. We used self-developed dax device (which is 2M aligned mapping) , to perform error injection to random address. It turned out that error injected to non-2M-aligned address was causing endless MCE until panic. Because page_mapped_in_vma() kept resulting wrong address and the task accessing the failure address was never killed properly: [ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.049006] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.448042] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.792026] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.162502] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.461116] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.764730] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.042128] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.464293] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.818090] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3787.085297] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page: Recovered It took us several weeks to pinpoint this problem, but we eventually used bpftrace to trace the page fault and mce address and successfully identified the issue. Joao added: ; Likely we never reproduce in production because we always pin : device-dax regions in the region align they provide (Qemu does : similarly with prealloc in hugetlb/file backed memory). I think this : bug requires that we touch *unpinned* device-dax regions unaligned to : the device-dax selected alignment (page size i.e. 4K/2M/1G)
A flaw was found in the Linux kernel's network physical layer (PHY) driver. When a PHY device is unregistered, a missing step to remove its associated LED entry from a list can occur. This vulnerability can be triggered in a specific scenario where a PHY port is repeatedly brought down and up, and its kernel module is removed and re-added. Successful exploitation of this flaw leads to a kernel panic, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's networking subsystem. An unsafe list iteration occurs when unregistering a Generic Netlink (genetlink) family while active listeners are still attached, leading to invalid memory access during element removal. A local user could exploit this issue to crash the system, leading to a Denial of Service (DoS).
A flaw was found in the Linux kernel's thermal core component. A local attacker could exploit a use-after-free vulnerability, where a memory object is accessed after it has been released. This improper handling of the thermal zone object during unregistration can lead to a system crash, resulting in a denial of service.
A flaw was found in the Linux kernel's thermal management component. This vulnerability arises from improper handling of thermal zone objects, where an object could be accessed after it has been released. A local attacker could potentially exploit this to cause a system crash, leading to a denial of service.
A flaw was found in the Linux kernel's Bluetooth subsystem. When an Asynchronous Connection-Less (ACL) connection is destroyed while the `hci_enhanced_setup_sync` function is processing a command, it can lead to a use-after-free (UAF) condition. An adjacent attacker could exploit this vulnerability to cause a denial of service (DoS), disclose sensitive information, or potentially execute arbitrary code.
A flaw was found in the Linux kernel. The `slhc_remember()` function, which handles Serial Line Internet Protocol (SLIP) header compression, did not properly validate incoming packet sizes and headers. A local attacker could exploit this by sending specially crafted malicious packets, leading to an uninitialized memory read and potentially causing a denial of service.
A flaw was found in the Linux kernel's Point-to-Point Protocol (PPP) implementation. A local attacker can exploit this vulnerability by sending a specially crafted message with a zero size to the `pppoe_sendmsg()` function, which leads to an uninitialized value being used in the `ppp_async_encode()` function. This can result in information disclosure and a denial of service (DoS).
In the Linux kernel, the following vulnerability has been resolved: netfilter: xtables: avoid NFPROTO_UNSPEC where needed syzbot managed to call xt_cluster match via ebtables: WARNING: CPU: 0 PID: 11 at net/netfilter/xt_cluster.c:72 xt_cluster_mt+0x196/0x780 [..] ebt_do_table+0x174b/0x2a40 Module registers to NFPROTO_UNSPEC, but it assumes ipv4/ipv6 packet processing. As this is only useful to restrict locally terminating TCP/UDP traffic, register this for ipv4 and ipv6 family only. Pablo points out that this is a general issue, direct users of the set/getsockopt interface can call into targets/matches that were only intended for use with ip(6)tables. Check all UNSPEC matches and targets for similar issues: - matches and targets are fine except if they assume skb_network_header() is valid -- this is only true when called from inet layer: ip(6) stack pulls the ip/ipv6 header into linear data area. - targets that return XT_CONTINUE or other xtables verdicts must be restricted too, they are incompatbile with the ebtables traverser, e.g. EBT_CONTINUE is a completely different value than XT_CONTINUE. Most matches/targets are changed to register for NFPROTO_IPV4/IPV6, as they are provided for use by ip(6)tables. The MARK target is also used by arptables, so register for NFPROTO_ARP too. While at it, bail out if connbytes fails to enable the corresponding conntrack family. This change passes the selftests in iptables.git.
A flaw was found in the Linux kernel's network scheduler. A local attacker with low privileges could exploit a vulnerability related to the handling of the `TCA_STAB` traffic control attribute when used with certain queueing disciplines (qdiscs) like TBF and SFQ. This improper handling can lead to a kernel NULL pointer dereference, causing the system to crash and resulting in a denial of service.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change rfcomm_sk_state_change attempts to use sock_lock so it must never be called with it locked but rfcomm_sock_ioctl always attempt to lock it causing the following trace: ====================================================== WARNING: possible circular locking dependency detected 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted ------------------------------------------------------ syz-executor386/5093 is trying to acquire lock: ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline] ffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73 but task is already holding lock: ffff88807badfd28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491
A flaw was found in the Linux kernel's NFSv4 component. A local user, when copying files on an NFS client's mountpoint to another location on the same NFS server, can trigger a null-pointer dereference. This vulnerability can lead to a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's Server Message Block (SMB) client. An authenticated local attacker with administrative or root privileges could trigger a use-after-free vulnerability during asynchronous decryption of large reads. This flaw could lead to a system crash, resulting in a denial of service (DoS).
A flaw was found in the Linux kernel, specifically within the driver core bus API. An issue in the `bus_register()` function can lead to a double free vulnerability. A local attacker with administrative privileges could exploit this to cause memory corruption, potentially resulting in a denial of service or other unpredictable system behavior.
A flaw was found in the Linux kernel's USB Type-C (tipd) driver. When the tps6598x module is removed, the system attempts to free an Interrupt Request (IRQ) even if one was not previously allocated. This improper resource handling can lead to a system warning and potential instability, which may result in a denial of service.
A flaw was found in the Linux kernel's serial subsystem. This vulnerability occurs in the `uart_shutdown()` function, where a null pointer dereference can happen if the `HUPCL` flag is set. A local attacker could potentially exploit this flaw to cause a system crash, leading to a Denial of Service (DoS).
A flaw was found in the zram component of the Linux kernel. When a zram device with multiple streams is reset, the secondary algorithm names are not properly freed. This oversight leads to a memory leak, which a local attacker could potentially exploit to cause a Denial of Service (DoS) by exhausting system memory.
An out-of-bounds overflow vulnerability was found in the Linux kernel. When Uprobe needs to fetch args into a per-CPU buffer and then copy to a ring buffer, sometimes user-space strings and arrays can be very large, but the size of the per-CPU buffer is only page size and checking is not performed, so an overflow can occur. This can result in a loss of confidentiality, availability, and integrity
A user after free vulnerability exists in the linux kernel such that when gsm_cleanup_mux is called,the gsm_msg on the tx_ctrl_list is not freed,resulting in loss of availability of the system.
An out-of-bounds array access memory flaw was found in the Linux kernel. When snprintf() returns the would-be-printed size, not the actual output size, the length calculation can still go over the given limit and cause an overflow, resulting in loss of availability of the system.
A flaw was found in the Linux kernel's xHCI (eXtensible Host Controller Interface) Tegra driver. When USB virtualization is enabled and USB2 ports are shared across virtual functions, an incorrect port number check can lead to invalid memory access. A local attacker with high privileges could exploit this vulnerability to cause a system crash (Denial of Service) or potentially disclose sensitive information.
A flaw was found in the Linux kernel's Bluetooth ISO subsystem. When the debug file system (debugfs) is not enabled, a logic error can cause the ISO subsystem to be initialized multiple times. This issue can be exploited by a local attacker with low privileges, leading to a kernel error that crashes the system. The primary consequence is a denial of service, making the system unavailable.
A flaw was found in the Linux kernel's Bluetooth subsystem. The Bluetooth module fails to properly unregister protocol structures upon module unload. A local user with administrative privileges can trigger this flaw by unloading and reloading the module, which leads to memory corruption. This issue causes a system crash, resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: blk-mq: setup queue ->tag_set before initializing hctx Commit 7b815817aa58 ("blk-mq: add helper for checking if one CPU is mapped to specified hctx") needs to check queue mapping via tag set in hctx's cpuhp handler. However, q->tag_set may not be setup yet when the cpuhp handler is enabled, then kernel oops is triggered. Fix the issue by setup queue tag_set before initializing hctx.
In the Linux kernel, the following vulnerability has been resolved: blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race We're seeing crashes from rq_qos_wake_function that look like this: BUG: unable to handle page fault for address: ffffafe180a40084 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 100000067 P4D 100000067 PUD 10027c067 PMD 10115d067 PTE 0 Oops: Oops: 0002 [#1] PREEMPT SMP PTI CPU: 17 UID: 0 PID: 0 Comm: swapper/17 Not tainted 6.12.0-rc3-00013-geca631b8fe80 #11 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:_raw_spin_lock_irqsave+0x1d/0x40 Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 54 9c 41 5c fa 65 ff 05 62 97 30 4c 31 c0 ba 01 00 00 00 <f0> 0f b1 17 75 0a 4c 89 e0 41 5c c3 cc cc cc cc 89 c6 e8 2c 0b 00 RSP: 0018:ffffafe180580ca0 EFLAGS: 00010046 RAX: 0000000000000000 RBX: ffffafe180a3f7a8 RCX: 0000000000000011 RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffffafe180a40084 RBP: 0000000000000000 R08: 00000000001e7240 R09: 0000000000000011 R10: 0000000000000028 R11: 0000000000000888 R12: 0000000000000002 R13: ffffafe180a40084 R14: 0000000000000000 R15: 0000000000000003 FS: 0000000000000000(0000) GS:ffff9aaf1f280000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffafe180a40084 CR3: 000000010e428002 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> try_to_wake_up+0x5a/0x6a0 rq_qos_wake_function+0x71/0x80 __wake_up_common+0x75/0xa0 __wake_up+0x36/0x60 scale_up.part.0+0x50/0x110 wb_timer_fn+0x227/0x450 ... So rq_qos_wake_function() calls wake_up_process(data->task), which calls try_to_wake_up(), which faults in raw_spin_lock_irqsave(&p->pi_lock). p comes from data->task, and data comes from the waitqueue entry, which is stored on the waiter's stack in rq_qos_wait(). Analyzing the core dump with drgn, I found that the waiter had already woken up and moved on to a completely unrelated code path, clobbering what was previously data->task. Meanwhile, the waker was passing the clobbered garbage in data->task to wake_up_process(), leading to the crash. What's happening is that in between rq_qos_wake_function() deleting the waitqueue entry and calling wake_up_process(), rq_qos_wait() is finding that it already got a token and returning. The race looks like this: rq_qos_wait() rq_qos_wake_function() ============================================================== prepare_to_wait_exclusive() data->got_token = true; list_del_init(&curr->entry); if (data.got_token) break; finish_wait(&rqw->wait, &data.wq); ^- returns immediately because list_empty_careful(&wq_entry->entry) is true ... return, go do something else ... wake_up_process(data->task) (NO LONGER VALID!)-^ Normally, finish_wait() is supposed to synchronize against the waker. But, as noted above, it is returning immediately because the waitqueue entry has already been removed from the waitqueue. The bug is that rq_qos_wake_function() is accessing the waitqueue entry AFTER deleting it. Note that autoremove_wake_function() wakes the waiter and THEN deletes the waitqueue entry, which is the proper order. Fix it by swapping the order. We also need to use list_del_init_careful() to match the list_empty_careful() in finish_wait().
In the Linux kernel, the following vulnerability has been resolved: thermal: intel: int340x: processor: Fix warning during module unload The processor_thermal driver uses pcim_device_enable() to enable a PCI device, which means the device will be automatically disabled on driver detach. Thus there is no need to call pci_disable_device() again on it. With recent PCI device resource management improvements, e.g. commit f748a07a0b64 ("PCI: Remove legacy pcim_release()"), this problem is exposed and triggers the warining below. [ 224.010735] proc_thermal_pci 0000:00:04.0: disabling already-disabled device [ 224.010747] WARNING: CPU: 8 PID: 4442 at drivers/pci/pci.c:2250 pci_disable_device+0xe5/0x100 ... [ 224.010844] Call Trace: [ 224.010845] <TASK> [ 224.010847] ? show_regs+0x6d/0x80 [ 224.010851] ? __warn+0x8c/0x140 [ 224.010854] ? pci_disable_device+0xe5/0x100 [ 224.010856] ? report_bug+0x1c9/0x1e0 [ 224.010859] ? handle_bug+0x46/0x80 [ 224.010862] ? exc_invalid_op+0x1d/0x80 [ 224.010863] ? asm_exc_invalid_op+0x1f/0x30 [ 224.010867] ? pci_disable_device+0xe5/0x100 [ 224.010869] ? pci_disable_device+0xe5/0x100 [ 224.010871] ? kfree+0x21a/0x2b0 [ 224.010873] pcim_disable_device+0x20/0x30 [ 224.010875] devm_action_release+0x16/0x20 [ 224.010878] release_nodes+0x47/0xc0 [ 224.010880] devres_release_all+0x9f/0xe0 [ 224.010883] device_unbind_cleanup+0x12/0x80 [ 224.010885] device_release_driver_internal+0x1ca/0x210 [ 224.010887] driver_detach+0x4e/0xa0 [ 224.010889] bus_remove_driver+0x6f/0xf0 [ 224.010890] driver_unregister+0x35/0x60 [ 224.010892] pci_unregister_driver+0x44/0x90 [ 224.010894] proc_thermal_pci_driver_exit+0x14/0x5f0 [processor_thermal_device_pci] ... [ 224.010921] ---[ end trace 0000000000000000 ]--- Remove the excess pci_disable_device() calls. [ rjw: Subject and changelog edits ]
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix incorrect pci_for_each_dma_alias() for non-PCI devices Previously, the domain_context_clear() function incorrectly called pci_for_each_dma_alias() to set up context entries for non-PCI devices. This could lead to kernel hangs or other unexpected behavior. Add a check to only call pci_for_each_dma_alias() for PCI devices. For non-PCI devices, domain_context_clear_one() is called directly.
A flaw was found in the Linux kernel's handling of user address masking on x86 architectures. This vulnerability, similar to "Meltdown Lite," allows for speculative execution (a CPU optimization technique) to be exploited due to incorrect handling of non-canonical memory accesses in kernel space. A local attacker with low privileges could leverage this issue to potentially leak sensitive data from kernel memory. This affects AMD Zen 5 and newer processors, where the speculation window remains open.
A vulnerability was found in the Linux kernel. This issue occurs due to a race condition between the laundromat thread handling revoking delegations and the `free_stateid` operation, leading to a use-after-free issue. The error occurs when a freed stateid is accessed by another operation, which can cause memory corruption.
In the Linux kernel, the following vulnerability has been resolved: platform/x86/intel/pmc: Fix pmc_core_iounmap to call iounmap for valid addresses Commit 50c6dbdfd16e ("x86/ioremap: Improve iounmap() address range checks") introduces a WARN when adrress ranges of iounmap are invalid. On Thinkpad P1 Gen 7 (Meteor Lake-P) this caused the following warning to appear: WARNING: CPU: 7 PID: 713 at arch/x86/mm/ioremap.c:461 iounmap+0x58/0x1f0 Modules linked in: rfkill(+) snd_timer(+) fjes(+) snd soundcore intel_pmc_core(+) int3403_thermal(+) int340x_thermal_zone intel_vsec pmt_telemetry acpi_pad pmt_class acpi_tad int3400_thermal acpi_thermal_rel joydev loop nfnetlink zram xe drm_suballoc_helper nouveau i915 mxm_wmi drm_ttm_helper gpu_sched drm_gpuvm drm_exec drm_buddy i2c_algo_bit crct10dif_pclmul crc32_pclmul ttm crc32c_intel polyval_clmulni rtsx_pci_sdmmc ucsi_acpi polyval_generic mmc_core hid_multitouch drm_display_helper ghash_clmulni_intel typec_ucsi nvme sha512_ssse3 video sha256_ssse3 nvme_core intel_vpu sha1_ssse3 rtsx_pci cec typec nvme_auth i2c_hid_acpi i2c_hid wmi pinctrl_meteorlake serio_raw ip6_tables ip_tables fuse CPU: 7 UID: 0 PID: 713 Comm: (udev-worker) Not tainted 6.12.0-rc2iounmap+ #42 Hardware name: LENOVO 21KWCTO1WW/21KWCTO1WW, BIOS N48ET19W (1.06 ) 07/18/2024 RIP: 0010:iounmap+0x58/0x1f0 Code: 85 6a 01 00 00 48 8b 05 e6 e2 28 04 48 39 c5 72 19 eb 26 cc cc cc 48 ba 00 00 00 00 00 00 32 00 48 8d 44 02 ff 48 39 c5 72 23 <0f> 0b 48 83 c4 08 5b 5d 41 5c c3 cc cc cc cc 48 ba 00 00 00 00 00 RSP: 0018:ffff888131eff038 EFLAGS: 00010207 RAX: ffffc90000000000 RBX: 0000000000000000 RCX: ffff888e33b80000 RDX: dffffc0000000000 RSI: ffff888e33bc29c0 RDI: 0000000000000000 RBP: 0000000000000000 R08: ffff8881598a8000 R09: ffff888e2ccedc10 R10: 0000000000000003 R11: ffffffffb3367634 R12: 00000000fe000000 R13: ffff888101d0da28 R14: ffffffffc2e437e0 R15: ffff888110b03b28 FS: 00007f3c1d4b3980(0000) GS:ffff888e33b80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005651cfc93578 CR3: 0000000124e4c002 CR4: 0000000000f70ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> ? __warn.cold+0xb6/0x176 ? iounmap+0x58/0x1f0 ? report_bug+0x1f4/0x2b0 ? handle_bug+0x58/0x90 ? exc_invalid_op+0x17/0x40 ? asm_exc_invalid_op+0x1a/0x20 ? iounmap+0x58/0x1f0 pmc_core_ssram_get_pmc+0x477/0x6c0 [intel_pmc_core] ? __pfx_pmc_core_ssram_get_pmc+0x10/0x10 [intel_pmc_core] ? __pfx_do_pci_enable_device+0x10/0x10 ? pci_wait_for_pending+0x60/0x110 ? pci_enable_device_flags+0x1e3/0x2e0 ? __pfx_mtl_core_init+0x10/0x10 [intel_pmc_core] pmc_core_ssram_init+0x7f/0x110 [intel_pmc_core] mtl_core_init+0xda/0x130 [intel_pmc_core] ? __mutex_init+0xb9/0x130 pmc_core_probe+0x27e/0x10b0 [intel_pmc_core] ? _raw_spin_lock_irqsave+0x96/0xf0 ? __pfx_pmc_core_probe+0x10/0x10 [intel_pmc_core] ? __pfx_mutex_unlock+0x10/0x10 ? __pfx_mutex_lock+0x10/0x10 ? device_pm_check_callbacks+0x82/0x370 ? acpi_dev_pm_attach+0x234/0x2b0 platform_probe+0x9f/0x150 really_probe+0x1e0/0x8a0 __driver_probe_device+0x18c/0x370 ? __pfx___driver_attach+0x10/0x10 driver_probe_device+0x4a/0x120 __driver_attach+0x190/0x4a0 ? __pfx___driver_attach+0x10/0x10 bus_for_each_dev+0x103/0x180 ? __pfx_bus_for_each_dev+0x10/0x10 ? klist_add_tail+0x136/0x270 bus_add_driver+0x2fc/0x540 driver_register+0x1a5/0x360 ? __pfx_pmc_core_driver_init+0x10/0x10 [intel_pmc_core] do_one_initcall+0xa4/0x380 ? __pfx_do_one_initcall+0x10/0x10 ? kasan_unpoison+0x44/0x70 do_init_module+0x296/0x800 load_module+0x5090/0x6ce0 ? __pfx_load_module+0x10/0x10 ? ima_post_read_file+0x193/0x200 ? __pfx_ima_post_read_file+0x10/0x10 ? rw_verify_area+0x152/0x4c0 ? kernel_read_file+0x257/0x750 ? __pfx_kernel_read_file+0x10/0x10 ? __pfx_filemap_get_read_batch+0x10/0x10 ? init_module_from_file+0xd1/0x130 init_module_from_file+0xd1/0x130 ? __pfx_init_module_from_file+0x10/0 ---truncated---
A flaw was found in the Linux kernel's `md/raid10` component. A local attacker could trigger a null pointer dereference in the `raid10_size()` function. This occurs when an internal function returns zero, but a critical data structure remains uninitialized, leading to a system crash. This vulnerability can result in a Denial of Service (DoS).
A flaw was found in the Linux kernel's drm/amd graphics driver. If a system's BIOS (Basic Input/Output System) provides malformed data in response to an ATIF (AMD Thermal and Interrupt Function) ACPI (Advanced Configuration and Power Interface) method call, it can lead to a NULL pointer dereference. This vulnerability could allow a local attacker with low privileges to cause a system crash, resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: smb: client: Handle kstrdup failures for passwords In smb3_reconfigure(), after duplicating ctx->password and ctx->password2 with kstrdup(), we need to check for allocation failures. If ses->password allocation fails, return -ENOMEM. If ses->password2 allocation fails, free ses->password, set it to NULL, and return -ENOMEM.
A flaw was found in the Linux kernel's Network File System daemon (nfsd). A race condition between terminating the NFS service and concurrent kernel memory reclaim operations can cause the system to access memory after it has been released. A local user with administrative privileges can trigger this flaw during service shutdown, leading to a Denial of Service (DoS) via a system crash or kernel memory corruption.
A use-after-free vulnerability was found in the taprio_dump() function in the Linux kernel.
A flaw was found in the Linux kernel's Time-Aware Priority (taprio) network scheduling module. A race condition during schedule updates allows memory to be accessed after it has been released. A local attacker with network configuration privileges could exploit this vulnerability to trigger a Denial of Service (DoS) or potentially execute arbitrary code.
A flaw was found in the Wireless Wide Area Network (WWAN) subsystem of the Linux kernel. This vulnerability, an out-of-bounds read, occurs when the system incorrectly processes network communication attributes due to an improperly sized variable. A local attacker with low privileges could exploit this to read sensitive information from memory. Successful exploitation could also lead to a system crash, resulting in a denial of service.
A flaw was found in the Linux kernel's netfilter subsystem. When attaching an extended Berkeley Packet Filter (eBPF) link, the kernel fails to acquire a reference counter on the associated network namespace. If the network namespace is torn down before the link is released, a local user can trigger a use-after-free condition when unregistering the netfilter hook. This memory corruption can lead to a system crash, resulting in a Denial of Service (DoS) or potential privilege escalation.
A flaw was found in the Linux kernel's ACPI Platform Runtime Mechanism (PRM) functionality. The Platform Runtime Mechanism Translator (PRMT) incorrectly attempts to use conventional memory instead of runtime memory for EFI (Extensible Firmware Interface) runtime services, specifically for the PRM handler and its context. This misconfiguration can lead to a paging request error when the PRM handler is invoked. A local attacker could potentially exploit this to cause a system crash, resulting in a denial of service.
A flaw was found in the Linux kernel's Universal Disk Format (UDF) file system. A local user could trigger information disclosure or a Denial of Service (DoS) by mounting a specially crafted file system image. This issue occurs due to an integer overflow when computing allocation extent lengths, causing the kernel to read uninitialized memory.
A flaw was found in the Linux kernel's USB Type-C alternate mode (altmode) driver. A local attacker could exploit a use-after-free vulnerability when the altmode device release refers to its parent without maintaining a proper reference. This could lead to a system crash, resulting in a denial of service.
A flaw was found in the cifs module in the Linux kernel. When building SMB2_IOCTL requests using encryption, either enforced by the server or using the 'seal' mount option, an out-of-bounds write can be triggered when the user passes an input buffer greater than 328 bytes, resulting in memory corruption and a kernel crash.
A doubly freeing memory vulnerability exists in the Linux kernel smb client. After the first successful memory allocation for 'ea', the second memory release for 'ea' will result in double free, leading to loss of availability of the system.
A flaw was found in the Linux kernel's SCSI target core. When memory allocation for device queues fails within the `target_alloc_device()` function, the system attempts to free an uninitialized device transport structure. This can lead to a null pointer dereference, allowing a local attacker with low privileges to cause a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) subsystem. When packet redirection occurs using device maps, the kernel fails to properly initialize the receive queue structure for subsequent programs. A local user capable of running BPF programs can exploit this vulnerability by accessing ingress interface metadata after a redirect, triggering a NULL pointer dereference that crashes the system and results in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: bpf: Make sure internal and UAPI bpf_redirect flags don't overlap The bpf_redirect_info is shared between the SKB and XDP redirect paths, and the two paths use the same numeric flag values in the ri->flags field (specifically, BPF_F_BROADCAST == BPF_F_NEXTHOP). This means that if skb bpf_redirect_neigh() is used with a non-NULL params argument and, subsequently, an XDP redirect is performed using the same bpf_redirect_info struct, the XDP path will get confused and end up crashing, which syzbot managed to trigger. With the stack-allocated bpf_redirect_info, the structure is no longer shared between the SKB and XDP paths, so the crash doesn't happen anymore. However, different code paths using identically-numbered flag values in the same struct field still seems like a bit of a mess, so this patch cleans that up by moving the flag definitions together and redefining the three flags in BPF_F_REDIRECT_INTERNAL to not overlap with the flags used for XDP. It also adds a BUILD_BUG_ON() check to make sure the overlap is not re-introduced by mistake.
A flaw was found in the Linux kernel's `vsock` component. A local attacker can exploit an imbalance in the `rx_bytes` tracking mechanism, specifically after `vsock_transport::read_skb()` fails to update the received bytes count when a packet is dequeued. This can lead to a warning message indicating an empty receive queue with non-zero `rx_bytes`, potentially resulting in a denial of service (DoS) for the system.
A flaw was found in the Linux kernel. On certain ARM64 systems, the memfd_secret() system call, intended to create secure memory regions, may appear to function correctly but fails to remove the memory from the direct map. This silent failure means that memory designated as secret is not properly protected. An attacker could potentially exploit this to access sensitive information stored in these supposedly secure memory areas, leading to information disclosure.
A flaw was found in the Linux kernel's networking component. When a network socket fails to be created, a reference to a previously freed memory location, known as a "dangling pointer," is not properly cleared. This oversight could allow a local attacker with low privileges to cause the system to become unstable or crash, leading to a denial of service (DoS).
A flaw was found in the Linux kernel's AMD Sensor Fusion Hub (SFH) Human Interface Device (HID) driver. Improper memory cleanup during the device's initialization process can lead to memory errors and system instability. A local attacker with low privileges could exploit this to trigger page faults, cause the Btrfs file system to become read-only, or lead to Btrfs disk corruption, effectively causing a Denial of Service (DoS) and potential data loss.
A flaw was found in the Linux kernel's handling of filesystem errors. When a filesystem encounters an error and is configured to remount as read-only, the kernel's attempt to apply this setting can conflict with other filesystem operations, specifically during filesystem freezing. This conflict can lead to system instability, potentially resulting in a denial of service where the system becomes unresponsive.
In the Linux kernel, the following vulnerability has been resolved: pinctrl: intel: platform: fix error path in device_for_each_child_node() The device_for_each_child_node() loop requires calls to fwnode_handle_put() upon early returns to decrement the refcount of the child node and avoid leaking memory if that error path is triggered. There is one early returns within that loop in intel_platform_pinctrl_prepare_community(), but fwnode_handle_put() is missing. Instead of adding the missing call, the scoped version of the loop can be used to simplify the code and avoid mistakes in the future if new early returns are added, as the child node is only used for parsing, and it is never assigned.
A flaw was found in the Linux kernel's memory management, specifically in how it handles HugeTLB (Huge Transparent Large Block) pages during the `swapoff` operation. A local user can trigger this by allocating anonymous HugeTLB memory, swapping out other anonymous memory, and then executing the `swapoff` command. This can lead to a 'bad pud error' and prevent the HugeTLB pages from being properly freed, resulting in a memory leak and a denial of service.
A flaw was found in the Linux kernel's maple tree implementation. A local attacker could exploit a tree corruption bug when performing a spanning store operation across two leaf nodes under specific conditions. This can lead to the mistaken duplication of entries, resulting in maple tree corruption. This corruption may allow an attacker to cause a denial of service or potentially gain unauthorized access to sensitive information.
In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Fix encoder->possible_clones Include the encoder itself in its possible_clones bitmask. In the past nothing validated that drivers were populating possible_clones correctly, but that changed in commit 74d2aacbe840 ("drm: Validate encoder->possible_clones"). Looks like radeon never got the memo and is still not following the rules 100% correctly. This results in some warnings during driver initialization: Bogus possible_clones: [ENCODER:46:TV-46] possible_clones=0x4 (full encoder mask=0x7) WARNING: CPU: 0 PID: 170 at drivers/gpu/drm/drm_mode_config.c:615 drm_mode_config_validate+0x113/0x39c ... (cherry picked from commit 3b6e7d40649c0d75572039aff9d0911864c689db)
A flaw was found in the nvmet-auth component of the Linux kernel. An authenticated local attacker with administrative privileges could trigger a double free vulnerability by repeatedly calling nvmet_setup_dhgroup(). This could lead to a denial of service (DoS) or potentially arbitrary code execution.
In the Linux kernel, the following vulnerability has been resolved: xfs: fix finding a last resort AG in xfs_filestream_pick_ag When the main loop in xfs_filestream_pick_ag fails to find a suitable AG it tries to just pick the online AG. But the loop for that uses args->pag as loop iterator while the later code expects pag to be set. Fix this by reusing the max_pag case for this last resort, and also add a check for impossible case of no AG just to make sure that the uninitialized pag doesn't even escape in theory.
A flaw was found in the Linux kernel's memory management subsystem. Under heavy memory pressure, atomic memory allocation requests can fail to access designated emergency memory reserves despite free memory being available. This condition can prevent the system from allocating memory during critical operations such as network packet processing, potentially resulting in dropped packets and a Denial of Service (DoS).
CWE-20 - Improper Input ValidationA flaw was found in the Linux kernel's shared memory subsystem. A local attacker can trigger a race condition by performing simultaneous file modifications and attribute queries on shared memory files. This timing conflict can result in reading inconsistent file metadata, potentially leading to unexpected system behavior.
CWE-362 - Concurrent Execution using Shared Resource with Improper SynchronizationA flaw was found in the Linux kernel's wifi: cfg80211 subsystem. A local attacker with administrative privileges could exploit this vulnerability. When a wireless device (wdev/netdev) is unregistered, its cqm_config pointer is freed but not cleared. If the same device is re-registered in another network namespace and subsequently destroyed, it leads to a double-free. This can result in a system crash (denial of service) or potentially allow for arbitrary code execution.
A flaw was found in the Linux kernel. Memory allocated for the MSDU (MAC Service Data Unit) context during management packet transmission is not properly freed upon completion or cleanup. A local attacker could exploit this memory leak to exhaust system resources, leading to a denial of service (DoS).
A flaw was found in the Linux kernel's Wi-Fi subsystem. This vulnerability occurs when a stopped virtual interface (vif) is improperly passed to the Wi-Fi driver's power management function. This can lead to the use of uninitialized data, potentially causing the system to crash and resulting in a Denial of Service (DoS). A local attacker could exploit this flaw.
A flaw was found in the Linux kernel's netfilter component, specifically within the `nf_reject_ipv6` module. This vulnerability arises when the system attempts to process an IPv6 packet where the network device's header length is unexpectedly zero, leading to a kernel crash. A remote attacker could exploit this flaw by sending a specially crafted IPv6 packet, resulting in a Denial of Service (DoS) on the affected system.
A use-after-free vulnerability was found in the Linux kernel. The metadata_dst, which is used to store the SCI value for macsec offload, is freed by metadata_dst_free() in macsec_free_netdev(), while the driver still uses it to send the packet.
A flaw was found in the Linux kernel. A local user can cause a Denial of Service (DoS) by exhausting the pending signal queue limit. Due to an issue where resource limits are enforced unconditionally even for signals intended to override them, the kernel fails to allocate necessary resources when delivering critical signals with their metadata. This prevents applications from properly receiving fault information, leading to unexpected application crashes or unstable behavior.
A flaw was found in the Linux kernel. A local user can trigger a Denial of Service (DoS) due to improper bounds checking in the file mapping subsystem. When a read operation is initiated with a file position near the upper limit of the file system and a read length that overflows that boundary, the filemap_read() function enters an infinite loop, resulting in a system hang.
A flaw was found in the Linux kernel's Device Mapper cache (dm-cache) component. This flaw allows a local user with storage configuration privileges to cause a Denial of Service (DoS) or potentially disclose sensitive system information. The vulnerability occurs when a caching device is resized prior to its initial resume, causing the kernel to omit required size checks and fail to allocate adequate internal data structures. Operating on the misconfigured device triggers an out-of-bounds memory access that can crash the system.
A flaw was found in the Linux kernel's AMD GPU driver. A local user with administrative privileges could trigger a buffer overflow by requesting an oversized read operation through the debugfs interface. This vulnerability could lead to memory corruption, potentially causing a system crash and resulting in a denial of service (DoS).
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) subsystem. Due to improper chunk size validation when handling out-of-the-blue packets in the sctp_sf_ootb() function, the kernel can read uninitialized memory. An attacker could exploit this vulnerability by sending specially crafted SCTP packets, causing a kernel crash and resulting in a denial of service (DoS).
A flaw was found in the Linux kernel's IPv4 tunneling subsystem. A local user can trigger an improper lock validation condition during IP tunnel lookup operations when managing network links. This issue generates a suspicious lock warning that can result in a Denial of Service (DoS) on systems configured to panic on kernel warnings.
A flaw was found in the Linux kernel's IPv4 tunneling subsystem. Certain code paths during tunnel initialization traverse network device lists without holding the required Read-Copy-Update (RCU) read lock. A local user could exploit this flaw while configuring network interfaces, potentially leading to kernel instability and a Denial of Service (DoS).
CWE-662 - Improper SynchronizationA flaw was found in the Linux kernel's network scheduling subsystem. When configuring traffic control rules with identical ingress and egress block identifiers, an error-handling failure prevents network flow blocks from properly unbinding on failure. A local user with network administration privileges can exploit this flaw to cause a Denial of Service (DoS), leaving the network device in an irrecoverable state until the driver is reloaded or the system is rebooted.
In the Linux kernel, the following vulnerability has been resolved: mptcp: init: protect sched with rcu_read_lock Enabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT creates this splat when an MPTCP socket is created: ============================= WARNING: suspicious RCU usage 6.12.0-rc2+ #11 Not tainted ----------------------------- net/mptcp/sched.c:44 RCU-list traversed in non-reader section!! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 no locks held by mptcp_connect/176. stack backtrace: CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:123) lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822) mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7)) mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1)) ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28) inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386) ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1)) __sock_create (net/socket.c:1576) __sys_socket (net/socket.c:1671) ? __pfx___sys_socket (net/socket.c:1712) ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1)) __x64_sys_socket (net/socket.c:1728) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) That's because when the socket is initialised, rcu_read_lock() is not used despite the explicit comment written above the declaration of mptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the warning.
CWE-667 - Improper LockingA flaw was found in the Linux kernel's Intel i915 graphics driver. A missing validation check on the display encoder within the High-bandwidth Digital Content Protection (HDCP) component allows a local authenticated attacker to trigger a null pointer dereference. This flaw can cause a kernel crash, resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: drm/i915/hdcp: Add encoder check in intel_hdcp_get_capability Sometimes during hotplug scenario or suspend/resume scenario encoder is not always initialized when intel_hdcp_get_capability add a check to avoid kernel null pointer dereference.
A flaw was found in the Linux kernel's iwlwifi driver. This vulnerability can lead to a Denial of Service (DoS) when constructing a 6 GHz wireless scan. Due to an 8-bit loop counter, discovering more than 255 co-located access points (APs) causes the driver to enter an infinite loop. An attacker within wireless range broadcasting numerous access points can trigger this condition to hang the system.
A flaw was found in the packet scheduler API in the Linux kernel. An invalid assumption about qdiscs with major handle ffff allows qdiscs, such as DRR, that maintain an active class list to cause a use-after-free with a dangling class pointer.
A flaw was found in the Linux kernel's Intel Wi-Fi driver (iwlwifi). This vulnerability allows a local user to cause a Denial of Service (DoS) or system instability through improper memory and buffer management. During firmware recovery operations, the driver fails to validate the response packet size and fails to free the allocated memory buffer, leading to resource leaks and crashes.
A flaw was found in the Linux kernel's AMD GPU driver. A failure to properly handle error returns during ACPI (Advanced Configuration and Power Interface) object evaluation can result in a NULL pointer dereference when specific interface features are unsupported. A local user could exploit this flaw to crash the system, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's USB DesignWare Core 3 (dwc3) driver. When a system suspend is initiated while the USB controller is already in a low-power runtime suspended state, the driver attempts to access unpowered device hardware registers, leading to a kernel crash. A local user with system privileges could exploit this issue by triggering a system suspend, resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Detect when STB is not available Loading the amd_pmc module as: amd_pmc enable_stb=1 ...can result in the following messages in the kernel ring buffer: amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340 Further debugging reveals that this occurs when the requests for S2D_PHYS_ADDR_LOW and S2D_PHYS_ADDR_HIGH return a value of 0, indicating that the STB is inaccessible. To prevent the ioremap warning and provide clarity to the user, handle the invalid address and display an error message.
A flaw was found in the Linux kernel's iwlwifi wireless driver. The driver fails to properly release link mapping resources when an Access Point (AP) is removed or stopped. A local privileged user could exploit this flaw by stopping a wireless AP, leading to a Denial of Service (DoS) condition where the device cannot restart the access point without reloading the driver or rebooting the system.
A flaw was found in the Linux kernel's virtio_net network driver. The driver does not properly validate the hash key length during device initialization. A local user could exploit this vulnerability when setting or reading the hash key, triggering out-of-bounds memory access. This flaw primarily results in a Denial of Service (DoS) through a system crash, or potentially exposes sensitive kernel memory.
A flaw was found in the Linux kernel's Trusted Platform Module (TPM) driver. A race condition during power management suspend operations allows hardware random number generator requests to execute while the TPM chip is suspending. A local user could exploit this flaw to cause improper hardware access, leading to a Denial of Service (DoS) such as a system crash or hang.
A flaw was found in the Linux kernel. A local user can exploit this vulnerability to trigger a Denial of Service (DoS) through a system crash. The issue occurs in the Berkeley Packet Filter (BPF) socket map subsystem, where the kernel incorrectly assumes that all monitored sockets are standard Internet sockets when checking Transport Layer Security (TLS) context data. When non-Internet communication sockets are processed, the kernel dereferences an invalid memory address, leading to a kernel page fault and system failure.
A flaw was found in the NVMe multipath support in the Linux kernel. A deadlock can be triggered when an error occurs in the partition scan within the controller's scan_work context, potentially resulting in a denial of service.
A flaw was found in the Linux kernel's Server Message Block (SMB) client. Improper reference counting allows kernel sockets to persist after their associated network namespace has been released. A local attacker with permission to create and destroy network namespaces—such as in containerized environments—can trigger this use-after-free condition during unmounting or reconnection attempts. This flaw primarily results in a system crash leading to a Denial of Service (DoS), with a potential risk of arbitrary memory corruption.
A flaw was found in the Linux kernel's memory management subsystem. A local attacker can trigger flawed error-handling paths during memory mapping operations, resulting in resource leaks and inconsistent internal state. This issue may lead to system instability and a denial of service (DoS).
In the Linux kernel, the following vulnerability has been resolved: mm: krealloc: Fix MTE false alarm in __do_krealloc This patch addresses an issue introduced by commit 1a83a716ec233 ("mm: krealloc: consider spare memory for __GFP_ZERO") which causes MTE (Memory Tagging Extension) to falsely report a slab-out-of-bounds error. The problem occurs when zeroing out spare memory in __do_krealloc. The original code only considered software-based KASAN and did not account for MTE. It does not reset the KASAN tag before calling memset, leading to a mismatch between the pointer tag and the memory tag, resulting in a false positive. Example of the error: ================================================================== swapper/0: BUG: KASAN: slab-out-of-bounds in __memset+0x84/0x188 swapper/0: Write at addr f4ffff8005f0fdf0 by task swapper/0/1 swapper/0: Pointer tag: [f4], memory tag: [fe] swapper/0: swapper/0: CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12. swapper/0: Hardware name: MT6991(ENG) (DT) swapper/0: Call trace: swapper/0: dump_backtrace+0xfc/0x17c swapper/0: show_stack+0x18/0x28 swapper/0: dump_stack_lvl+0x40/0xa0 swapper/0: print_report+0x1b8/0x71c swapper/0: kasan_report+0xec/0x14c swapper/0: __do_kernel_fault+0x60/0x29c swapper/0: do_bad_area+0x30/0xdc swapper/0: do_tag_check_fault+0x20/0x34 swapper/0: do_mem_abort+0x58/0x104 swapper/0: el1_abort+0x3c/0x5c swapper/0: el1h_64_sync_handler+0x80/0xcc swapper/0: el1h_64_sync+0x68/0x6c swapper/0: __memset+0x84/0x188 swapper/0: btf_populate_kfunc_set+0x280/0x3d8 swapper/0: __register_btf_kfunc_id_set+0x43c/0x468 swapper/0: register_btf_kfunc_id_set+0x48/0x60 swapper/0: register_nf_nat_bpf+0x1c/0x40 swapper/0: nf_nat_init+0xc0/0x128 swapper/0: do_one_initcall+0x184/0x464 swapper/0: do_initcall_level+0xdc/0x1b0 swapper/0: do_initcalls+0x70/0xc0 swapper/0: do_basic_setup+0x1c/0x28 swapper/0: kernel_init_freeable+0x144/0x1b8 swapper/0: kernel_init+0x20/0x1a8 swapper/0: ret_from_fork+0x10/0x20 ==================================================================
CWE-119 - Improper Restriction of Operations within the Bounds of a Memory BufferA flaw was found in the Linux kernel's Hyper-V socket (hv_sock) driver. When a socket connection is released, the transport pointer is not properly cleared, creating a dangling pointer that references already released memory. A local attacker could exploit this issue to trigger memory corruption, leading to a system crash and Denial of Service (DoS).
A flaw was found in the Linux kernel's memory management subsystem. When certain memory pages are freed while still marked as locked in memory, the kernel detects an inconsistent page state and permanently takes those pages out of service. A local user could exploit this vulnerability through specific memory operations to trigger kernel warnings and cause memory leaks, potentially leading to a denial of service (DoS).
A flaw was found in the Linux kernel. The virtio-pci Virtual Data Path Acceleration (vp_vdpa) driver fails to properly null-terminate its device identifier array. A local user could exploit this flaw to cause the kernel to read out-of-bounds memory, resulting in a Denial of Service (DoS) via a system crash.
A flaw was found in the Linux kernel's virtio virtual socket (vsock) implementation. This vulnerability can lead to a Denial of Service (DoS) caused by memory exhaustion. When an error occurs during zero-copy network transmissions (MSG_ZEROCOPY), the kernel fails to properly release allocated socket memory buffers. A local user can exploit this flaw by repeatedly triggering transmission errors, resulting in a memory leak that can degrade performance or render the system unresponsive.
A flaw was found in the Linux kernel's Virtual Socket (vsock) implementation. When zero-copy data transfers are used, completion notifications placed on a socket's error queue are not cleared when the socket is closed. A local user can exploit this flaw to trigger an uncollected memory leak, potentially leading to system memory exhaustion and a Denial of Service (DoS).
A flaw was found in the Linux kernel's Mellanox mlx5 network driver. An uninitialized pointer is improperly accessed within the driver's error-handling path when adding connection tracking rules. A local user can exploit this vulnerability during a rule configuration failure, triggering a null pointer dereference that causes a system crash and Denial of Service (DoS).
A flaw was found in the Linux kernel's Mellanox (mlx5) network driver. This vulnerability can lead to a Denial of Service (DoS) when a race condition is triggered during the concurrent deletion and addition of matching network flow steering rules. A local user with network configuration privileges could exploit improper locking of flow table entries to trigger a kernel crash.
A flaw was found in the Linux kernel's Multipath TCP (MPTCP) implementation. Due to improper handling of racing socket disconnect events, the kernel fails to handle error returns appropriately, leading to a division-by-zero error during TCP window calculations. A local attacker can exploit this issue to trigger a system crash, resulting in a denial of service (DoS).
A flaw was found in the Linux kernel. This vulnerability may allow a local user to cause a denial of service (DoS) through a system crash. A race condition occurs when concurrent threads process incoming IPv6 network traffic on a listening socket without adequate locking, leading to corrupted socket memory accounting.
A flaw was found in the Linux kernel's i.MX93 power domain driver. An improper loop condition in the device removal routine prevents the loop from terminating. A local attacker could exploit this flaw during device unbinding or removal to trigger a kernel panic, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's shared memory (shmem) subsystem. When a temporary in-memory filesystem (tmpfs) is exported over Network File System (NFS), retrieving file attributes can cause a deadlock condition. A user accessing the affected share can trigger this flaw to hang the system, resulting in a denial of service (DoS).
A flaw was found in the Linux kernel's netfilter ipset subsystem. A missing range check when handling IP address parameters allows user-supplied network attributes to bypass validation, resulting in memory corruption. A local attacker with network administration privileges, or an unprivileged user utilizing user namespaces, could exploit this flaw to achieve privilege escalation or cause a Denial of Service (DoS) by crashing the system.
A flaw was found in the Linux kernel's initramfs (initial RAM file system) extraction mechanism. When unpacking an archive, the kernel fails to verify that a filename is properly null-terminated before processing it. A privileged local user capable of modifying the boot archive could supply a specially crafted file to trigger an out-of-bounds read. This flaw can lead to the disclosure of uninitialized memory or cause a denial of service (DoS) through a system crash.
A flaw was found in the Linux kernel's Network File System daemon (NFSD). An integer overflow vulnerability exists in the callback response decoding process when handling excessively large tag lengths. A remote attacker could exploit this flaw by sending a specially crafted callback response to the NFS server, potentially resulting in a system crash and a Denial of Service (DoS).
A flaw was found in the Linux kernel's PCIe Tegra194 controller driver, which can lead to a Denial of Service (DoS). When operating in endpoint mode, the driver executes cleanup routines that access hardware registers after the connected host asserts a reset signal and disables the reference clock. Because the endpoint device relies on this host clock to remain operational, accessing registers without an active clock causes the system to crash.
A flaw was found in the Linux kernel's ath9k wireless driver. A local user can exploit missing range validation of the endpoint identifier during device communication, leading to an out-of-bounds array access. This vulnerability can lead to a Denial of Service (DoS) by crashing the kernel and may potentially disclose sensitive kernel memory.
A flaw was found in the Linux kernel. A race condition exists in the Read-Copy Update (RCU) subsystem during deferred memory freeing operations due to missing synchronization locks. A local user could exploit this vulnerability to cause a Denial of Service (DoS) through a kernel crash or system instability.
A flaw was found in the Linux kernel's BlueField Error Detection and Correction (EDAC) driver. A local user can trigger an integer overflow when the driver queries dual in-line memory module (DIMM) information, potentially leading to a Denial of Service (DoS). Due to an insufficiently sized variable, bit-shift operations truncate the memory controller index before passing it to system firmware, causing corrupted requests and resulting in system instability.
CWE-190 - Integer Overflow or WraparoundIn the Linux kernel, the following vulnerability has been resolved: net: sched: fix ordering of qlen adjustment Changes to sch->q.qlen around qdisc_tree_reduce_backlog() need to happen _before_ a call to said function because otherwise it may fail to notify parent qdiscs when the child is about to become empty.
A flaw was found in the Linux kernel's Budget Fair Queue (BFQ) I/O scheduler. Missing locking when dereferencing queue structures shared across multiple tasks can lead to a use-after-free condition during concurrent operations. A local attacker could exploit this vulnerability to crash the system, resulting in a Denial of Service (DoS), or potentially execute arbitrary code.
A flaw was found in the Linux kernel's Network File System (NFS) client. When multiple threads concurrently attempt to open files and are aborted before receiving a server response, a race condition can cause the system to reference already freed memory. A local user could exploit this vulnerability to cause a system crash, resulting in a denial of service (DoS), or potentially execute arbitrary code.
A flaw was found in the Linux kernel's SUNRPC (Sun Remote Procedure Call) subsystem. A local user can cause a Denial of Service (DoS) by reading RPC cache entries, triggering a use-after-free condition where memory is accessed after being marked for release. This issue occurs because the cache display mechanism fails to ensure an entry is active before incrementing its reference count, leading to an unexpected system crash or potential memory leak.
A flaw was found in the Linux kernel's SMB/CIFS client. A race condition can occur during unmount operations when closing cached directories while concurrent background directory cleanup or server reconnection tasks are underway. This timing error prevents cached directory entries from being released properly, triggering a kernel crash. An authorized local user can trigger this issue during share unmount operations, resulting in a Denial of Service (DoS).
A deadlock condition exists in the Linux kernel. During the probe of rtl8192cu, the driver ends-up performing an refuse read procedure and the read_efuse() function calls read_efuse_byte() based on the efuse size.
A flaw was found in the Linux kernel's PCI subsystem. During device hot-removal, a race condition can cause the system to release a PCI bus structure while it is still referenced by an active slot. A local user capable of triggering device removal or hot-unplug operations could exploit this use-after-free condition to crash the kernel, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's USB Type-C driver. A local user with administrative privileges can exploit this flaw by providing a crafted command through the debug file system (debugfs). This issue results in an array underflow and out-of-bounds memory access, which may lead to a system crash and Denial of Service (DoS).
A flaw was found in the Linux kernel's Bluetooth subsystem. A local user with administrative privileges can trigger a use-after-free condition by issuing Bluetooth power configuration commands while the controller interface is closing. This flaw allows an attacker to cause a Denial of Service (DoS) through a system crash or potentially execute arbitrary code by dereferencing freed kernel memory.
A double free vulnerability was found in the Linux kernel. In lan78xx_probe(), the `buf` buffer is freed twice: once implicitly through `usb_free_urb(dev->urb_intr)` with the `URB_FREE_BUFFER` flag and again explicitly by `kfree(buf)`, resulting in loss of availability of the system.
A flaw was found in the Linux kernel's Network File System daemon (nfsd). A local user can trigger a use-after-free condition when export cache entries are prematurely released during read operations. This issue may lead to memory corruption, potentially causing a system crash and resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's zram driver. This vulnerability can lead to a Denial of Service (DoS) by causing a system crash. During device initialization, a timing window allows a local user to access the device attributes through the sysfs interface before compression algorithms are properly initialized, triggering a NULL pointer dereference.
A flaw was found in the Linux kernel's mlx5 InfiniBand driver. This flaw allows a local user to cause a Denial of Service (DoS) by triggering a system crash. A race condition between device deregistration and background event handling can cause tasks to execute after the hardware device has been unregistered, resulting in a null-pointer dereference and kernel panic.
A flaw was found in the Linux kernel's s390 IOMMU (Input-Output Memory Management Unit) subsystem. When a PCI (Peripheral Component Interconnect) device is unexpectedly removed while in use (surprise hot-unplugged), the kernel fails to attach a memory domain to the missing hardware, resulting in a use-after-free condition. A local privileged user could trigger this flaw to crash the operating system, leading to a denial of service (DoS).
A flaw was found in the Linux kernel's Bluetooth subsystem. When removing a Bluetooth connection while its parent controller device is being unregistered, improper reference counting can cause the system to retain a reference to memory that has already been released. A local user with administrative privileges could exploit this flaw to trigger a use-after-free condition, leading to a Denial of Service (DoS) through a system crash or potential kernel memory corruption.
A flaw was found in the Linux kernel's Non-Volatile Memory Express (NVMe) target subsystem. When updating the subsystem discovery configuration, the nvmet_root_discovery_nqn_store function incorrectly treats dynamically allocated memory as a fixed-size buffer, leading to a heap-based buffer overflow. A local privileged user can exploit this vulnerability by submitting an oversized string through the storage configuration interface, causing memory corruption that may result in a Denial of Service (DoS) via a system crash.
A flaw was found in the Linux kernel's Bluetooth subsystem. A circular locking dependency between socket and device locks during Bluetooth Isochronous (ISO) communication can lead to a deadlock. A local attacker with permission to create Bluetooth sockets on a system with an active Bluetooth adapter can exploit this flaw to cause a system hang, resulting in a Denial of Service (DoS).
[REJECTED CVE] A vulnerability was suspected in the Linux kernel's SMB client module related to TCP timers and potential deadlocks after module removal (rmmod cifs). The issue stemmed from incorrect manual manipulation of sk->sk_net_refcnt, which led to TCP timers not being properly cleared, causing lockdep warnings and deadlocks. However, this was an internal kernel misconfiguration affecting cleanup behavior rather than a security flaw exploitable by an attacker. Since no privilege escalation or data exposure was possible, this does not qualify as a security vulnerability.
CWE-667 - Improper LockingA flaw was found in the Linux kernel's Realtek Wi-Fi driver (rtw89). A local user could cause a Denial of Service (DoS) by triggering a condition where memory allocation fails within the driver. Because the driver does not check whether the memory allocation succeeded before using it, an allocation failure results in a null pointer dereference that crashes the system.
A flaw was found in the Linux kernel's udmabuf driver. This vulnerability allows a local user to cause a denial of service (DoS) by requesting large buffer allocations. Because the driver relies on physically contiguous memory allocations with strict size limits, requesting buffers that exceed kernel page allocation boundaries fails and triggers kernel warnings.
A flaw was found in the AMD GPU driver within the Linux kernel. A use-after-free condition occurs during device teardown or hot-unplug operations because the driver releases graphics scheduling structures before all associated tasks are finalized. A local attacker with administrative privileges could exploit this flaw by removing or resetting the device, causing a kernel crash and resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's Network File System daemon (nfsd). This flaw allows a local authenticated user to cause a Denial of Service (DoS) by crashing the operating system. By reading export status files while cache entries expire, improper reference count handling can trigger a use-after-free memory error.
A vulnerability was found in the i3c_master_put_i3c_addrs() function in the Linux kernel's i3c driver. A memory management issue can occur due to a copy-paste error between "dyn_addr" and "init_dyn_addr", which leads to incorrect handling of memory, potentially causing resource mismanagement and instability within the system.
A use-after-free list corruption vulnerability was found in the Linux kernel. If an allocated object fails in alloc_consistency_checks, all objects of the slab will be marked as used and the slab will be removed from the partial list. When an object belonging to the slab gets freed later, the remove_full() function is called. Since the slab is neither on the partial list nor on the full list, it eventually leads to a list corruption.
A flaw was found in the Linux kernel's OverlayFS subsystem. A local attacker with administrative privileges or the ability to create unprivileged user namespaces can exploit this flaw by mounting an OverlayFS file system containing lower directory entries that lack valid lookup operations. Processing these invalid entries can trigger internal kernel faults, resulting in a system crash and a Denial of Service (DoS).
A use-after-free vulnerability was found in the Linux kernel. The Bluetooth firmware isn't checked if skb contains an ACL header, otherwise the code may attempt to access some uninitialized or invalid memory past the valid skb->data.
A flaw was found in the Bluetooth subsystem of the Linux kernel, in the handling of delayed work within the hci_conn (Host Controller Interface connection) structure. The kernel used cancel_delayed_work_sync() when shutting down a connection, which cancels ongoing work but allows rescheduling. This could result in use-after-free conditions if the work is resubmitted after the associated object has been freed. Replacing it with disable_delayed_work_sync() prevents further scheduling, ensuring proper cleanup. A local attacker could potentially exploit this to trigger a use-after-free, leading to a denial of service or possible code execution.
A flaw was found in the Linux kernel's IPv6 networking component. When creating a network socket, an error during initialization can leave an invalid reference to memory that has already been released. A local user could exploit this use-after-free flaw to cause a denial of service (DoS) through a system crash or potentially escalate privileges on the system.
A flaw was found in the Linux kernel. A local user can exploit this vulnerability to cause a Denial of Service (DoS) or potentially leak sensitive system memory. When an error occurs during network socket creation in the inet_create() function, the kernel frees the allocated socket object without clearing the corresponding pointer, leading to a use-after-free condition.
A user-after-free vulnerability was found in the linux kernel. sock_init_data() attaches the allocated sk object to the provided sock object. If ieee802154_create() fails later, the allocated sk object is freed, but the dangling pointer remains in the provided sock object, leading to a crash and loss of availability of the system.
A flaw was found in the Linux kernel's Bluetooth Radio Frequency Communication (RFCOMM) subsystem. When an error occurs during socket allocation, an internal socket object is freed while leaving an invalid reference in the parent socket structure. A local attacker can exploit this dangling pointer to cause memory corruption, potentially leading to a system crash and Denial of Service (DoS) or privilege escalation.
A flaw was found in the Linux kernel's Bluetooth subsystem. During socket initialization, an error handling failure leaves behind a reference to freed memory. A local user could exploit this use-after-free condition to cause a denial of service (DoS) or potentially achieve privilege escalation.
A flaw was found in the Linux kernel. A local user can cause a Denial of Service (DoS) by crashing the system during page migration operations. The issue stems from the memory policy subsystem incorrectly assuming an address space contains at least one virtual memory area, resulting in a null pointer dereference when attempting to access non-existent memory mappings.
A flaw was found in the Linux kernel. A local user can cause kernel memory corruption or a Denial of Service (DoS) due to an out-of-bounds write vulnerability in the socket map (XSK) component. When deleting elements from an XSK map, an integer type conversion error allows a negative index value to bypass bounds checking. This flaw enables an attacker to trigger an unauthorized memory write, leading to memory corruption or a system crash.
A flaw was found in the Linux kernel's DisplayPort Multi-Stream Transport (DP MST) subsystem. When processing sideband communication from a connected display device, the driver fails to properly validate that the message body contains the required minimum length. An attacker with physical access attaching a malicious display device, or a local privileged user, can exploit this vulnerability to trigger an out-of-bounds memory write. This issue can result in memory corruption, leading to a system crash and Denial of Service (DoS), or potentially arbitrary code execution.
A flaw was found in the Linux kernel's qla2xxx driver. This vulnerability can lead to a Denial of Service (DoS) through a system crash. A race condition occurs during module unloading when terminating internal driver threads, allowing a local user with administrative privileges to trigger a use-after-free condition.
A flaw was found in the Linux kernel's SCSI generic (sg) driver. A local user could exploit this flaw to cause a Denial of Service (DoS) via a system crash or potentially achieve privilege escalation. The issue arises from improper ordering between reference counting cleanup and mutex operations in the sg_release() function, which can prematurely free device data structures while they are still being accessed, resulting in a use-after-free condition.
A flaw was found in the Transparent Inter-Process Communication (TIPC) subsystem in the Linux kernel. A race condition occurs during the cleanup of UDP (User Datagram Protocol) bearer sockets, resulting in a use-after-free vulnerability. An attacker could exploit this issue during connection shutdown to cause a denial of service (DoS) via a kernel crash or potentially cause memory corruption.
A flaw was found in the Linux kernel's IPv6 networking subsystem. A local user may cause a Denial of Service (DoS) through an unreleased memory leak. When handling path Maximum Transmission Unit (MTU) changes alongside connection timeouts, the kernel fails to properly balance reference counts for expired IPv6 route cache entries. Over time, these accumulated leaked route objects prevent network namespace cleanup and exhaust system memory.
A denial of service vulnerability was found in the Linux kernel. icmp_route_lookup() creates input routes for locally generated packets during xfrm relookup ICMP traffic. Then it will set the input route (dst->out = ip_rt_bug) to skb for DESTUNREACH, leading to loss of availability of the system.
A flaw was found in the Linux kernel's MediaTek Bluetooth driver. When handling device coredump diagnostic data, an internal network buffer can be accessed after it has already been released, leading to a use-after-free condition. An attacker with access to a system running affected MediaTek Bluetooth hardware could trigger this vulnerability to cause memory corruption, resulting in a kernel crash and a denial of service (DoS).
A flaw was found in the Linux kernel's Bluetooth subsystem. Improper Read-Copy Update (RCU) synchronization during Bluetooth Host Controller Interface (HCI) event list processing can result in invalid memory dereferences. A local attacker could exploit this issue to trigger a system crash, resulting in a denial of service (DoS).
A flaw was found in the Linux kernel's wireless (nl80211) subsystem. An off-by-one boundary validation error in the handling of link attribute identifiers allows a local user to cause an out-of-bounds memory read by sending specially crafted netlink messages. Exploitation of this vulnerability can lead to a system crash, causing a Denial of Service (DoS), or potentially expose sensitive kernel memory.
A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) sockmap subsystem. A race condition can occur when an element in a BPF map is replaced while a socket is simultaneously being closed, leading to improper reference counting. This issue results in a use-after-free condition, where the system accesses memory after it has been released. A local user could exploit this vulnerability to cause a Denial of Service (DoS) by crashing the kernel, or potentially achieve privilege escalation.
A flaw was found in the Linux kernel's i915 graphics driver. When capturing GPU error information, the driver fails to verify that an execution context structure is present before logging diagnostic details, resulting in a null-pointer dereference. A local user on a system equipped with Intel graphics hardware can trigger this condition to crash the system, leading to a Denial of Service (DoS).
A flaw was found in the Linux kernel's SunRPC (Sun Remote Procedure Call) subsystem. During transport connection resets, socket timeout flags are not properly cleared, leading to an invalid memory dereference when processing subsequent network requests. A local user capable of triggering or timing network disconnects could exploit this vulnerability to crash the system, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's RAM disk driver (brd). This vulnerability allows a local user to cause a denial of service (DoS) or potentially execute arbitrary code. During module initialization, if an error occurs, the driver releases partially created disk devices while they may still be referenced, resulting in a use-after-free memory flaw when the device is subsequently accessed or closed.
A flaw was found in the Linux kernel's Server Message Block (SMB) client. An authenticated local attacker interacting with active network shares can trigger a race condition when opening cached directories during an SMB lease break. This failure to release internal connection references causes a memory and resource leak over time, which can lead to a Denial of Service (DoS) through kernel resource exhaustion.
A flaw was found in the Linux kernel's MediaTek Bluetooth USB driver. When a MediaTek Bluetooth device is disconnected, the driver fails to properly release a dedicated interrupt interface before unregistering the host controller interface. A local user capable of physically removing or virtually detaching the USB device can trigger this flaw, causing a kernel panic that leads to a denial of service (DoS).
A flaw was found in the Linux kernel's PCI (Peripheral Component Interconnect) Message Signaled Interrupts (MSI) subsystem. When configuring device interrupts on architectures that do not support interrupt domains, the kernel fails to handle the absence of legacy fallback support properly. A local user could exploit this condition to trigger an unexpected kernel warning, potentially causing a Denial of Service (DoS) on systems configured to halt on kernel warnings.
A flaw was found in the Linux kernel's Network File System daemon (NFSD). This issue can lead to a Denial of Service (DoS) through kernel memory exhaustion when processing concurrent file open operations. A race condition during state handling causes the server to abandon and fail to release allocated memory objects. An authorized client can exploit this flaw by issuing multiple simultaneous open requests, gradually consuming server memory.
A flaw was found in the Linux kernel's netfilter subsystem. A local user can trigger an unnecessary kernel warning assertion by processing socket rules within deeply nested control groups (cgroups). This issue may lead to a Denial of Service (DoS) by causing a system crash if the kernel is configured to treat warnings as fatal errors.
A flaw was found in the Linux kernel's DisplayPort Multi-Stream Transport (DP MST) subsystem. A local attacker can cause a Denial of Service (DoS) by triggering a race condition between request processing and topology removal. This flaw leads to dereferencing a null pointer or accessing memory that has already been freed, resulting in a system crash or kernel instability.
A flaw was found in the PCI-imx6 module in the Linux kernel. The suspend/resume support is missing in the i.MX6QDL platforms, allowing certain drivers, such as ath10k and iwlwifi, to crash after resuming, causing a kernel hang and a denial of service.
A flaw was found in the Linux kernel's virtio-net driver. When allocating network receive buffers under conditions where memory allocations are restricted to a single page, the driver prepends Direct Memory Access (DMA) metadata without properly accounting for the total buffer size. This flaw can cause a buffer overflow during network traffic processing, leading to a system crash and a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: smc: Handle missing SCM device Commit ca61d6836e6f ("firmware: qcom: scm: fix a NULL-pointer dereference") makes it explicit that qcom_scm_get_tzmem_pool() can return NULL, therefore its users should handle this.
A flaw was found in the Linux kernel's Bluetooth subsystem. A local attacker on a system with active Bluetooth hardware can trigger a denial of service (DoS) by interacting with Bluetooth isochronous (ISO) sockets. When an error occurs during socket handling, the kernel fails to release internal device references, resulting in resource leaks that prevent device cleanup and exhaust system resources.
A flaw was found in the Linux kernel's memory management subsystem. Under severe memory pressure, particularly on systems configured without swap space, improper evaluation of reclaimable memory zones causes direct reclaim operations to enter an infinite loop. A local user could exploit this condition by generating high memory demand, causing the system to hang and resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: fix sleeping function called from invalid context at print message Address a bug in the kernel that triggers a "sleeping function called from invalid context" warning when /sys/kernel/debug/kmemleak is printed under specific conditions: - CONFIG_PREEMPT_RT=y - Set SELinux as the LSM for the system - Set kptr_restrict to 1 - kmemleak buffer contains at least one item BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 136, name: cat preempt_count: 1, expected: 0 RCU nest depth: 2, expected: 2 6 locks held by cat/136: #0: ffff32e64bcbf950 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xb8/0xe30 #1: ffffafe6aaa9dea0 (scan_mutex){+.+.}-{3:3}, at: kmemleak_seq_start+0x34/0x128 #3: ffff32e6546b1cd0 (&object->lock){....}-{2:2}, at: kmemleak_seq_show+0x3c/0x1e0 #4: ffffafe6aa8d8560 (rcu_read_lock){....}-{1:2}, at: has_ns_capability_noaudit+0x8/0x1b0 #5: ffffafe6aabbc0f8 (notif_lock){+.+.}-{2:2}, at: avc_compute_av+0xc4/0x3d0 irq event stamp: 136660 hardirqs last enabled at (136659): [<ffffafe6a80fd7a0>] _raw_spin_unlock_irqrestore+0xa8/0xd8 hardirqs last disabled at (136660): [<ffffafe6a80fd85c>] _raw_spin_lock_irqsave+0x8c/0xb0 softirqs last enabled at (0): [<ffffafe6a5d50b28>] copy_process+0x11d8/0x3df8 softirqs last disabled at (0): [<0000000000000000>] 0x0 Preemption disabled at: [<ffffafe6a6598a4c>] kmemleak_seq_show+0x3c/0x1e0 CPU: 1 UID: 0 PID: 136 Comm: cat Tainted: G E 6.11.0-rt7+ #34 Tainted: [E]=UNSIGNED_MODULE Hardware name: linux,dummy-virt (DT) Call trace: dump_backtrace+0xa0/0x128 show_stack+0x1c/0x30 dump_stack_lvl+0xe8/0x198 dump_stack+0x18/0x20 rt_spin_lock+0x8c/0x1a8 avc_perm_nonode+0xa0/0x150 cred_has_capability.isra.0+0x118/0x218 selinux_capable+0x50/0x80 security_capable+0x7c/0xd0 has_ns_capability_noaudit+0x94/0x1b0 has_capability_noaudit+0x20/0x30 restricted_pointer+0x21c/0x4b0 pointer+0x298/0x760 vsnprintf+0x330/0xf70 seq_printf+0x178/0x218 print_unreferenced+0x1a4/0x2d0 kmemleak_seq_show+0xd0/0x1e0 seq_read_iter+0x354/0xe30 seq_read+0x250/0x378 full_proxy_read+0xd8/0x148 vfs_read+0x190/0x918 ksys_read+0xf0/0x1e0 __arm64_sys_read+0x70/0xa8 invoke_syscall.constprop.0+0xd4/0x1d8 el0_svc+0x50/0x158 el0t_64_sync+0x17c/0x180 %pS and %pK, in the same back trace line, are redundant, and %pS can void %pK service in certain contexts. %pS alone already provides the necessary information, and if it cannot resolve the symbol, it falls back to printing the raw address voiding the original intent behind the %pK. Additionally, %pK requires a privilege check CAP_SYSLOG enforced through the LSM, which can trigger a "sleeping function called from invalid context" warning under RT_PREEMPT kernels when the check occurs in an atomic context. This issue may also affect other LSMs. This change avoids the unnecessary privilege check and resolves the sleeping function warning without any loss of information.
CWE-20 - Improper Input ValidationA flaw was found in the Linux kernel workqueue subsystem. A local user can cause a Denial of Service (DoS) by initiating specific hardware or subsystem routines that trigger background task cancellations. During these cancellations, memory reclaim dependency checks are improperly applied to safe operations, which can result in kernel warnings and system instability.
A flaw was found in the Linux kernel. A local user with access to the Remote Direct Memory Access (RDMA) user verbs interface can cause a denial of service (DoS) by exploiting an integer overflow vulnerability. When processing user-provided request sizes, the kernel fails to prevent arithmetic wrapping during request validation. An attacker can supply specially crafted input values to trigger an unexpected system crash.
[REJECTED CVE] A vulnerability was identified in the Linux kernel's Bluetooth: hci_core package, where a sleeping function (mutex_lock) was improperly invoked from an invalid context within the HCI event handling workqueue, potentially leading to kernel warnings or deadlocks. An attacker exploiting this flaw could trigger crafted Bluetooth events or malformed packets to indirectly cause system instability or denial of service through workqueue execution paths.
CWE-662 - Improper SynchronizationA flaw was found in the Linux kernel's wireless configuration subsystem (cfg80211). A local user with permissions to manage wireless network interfaces could cause a Denial of Service (DoS) by initiating a wireless link deletion operation. Because the subsystem clears the active link identifier before cleanup routines finish, required cleanup handlers fail internal kernel checks, leading to kernel warnings and potential system instability.
In the Linux kernel, the following vulnerability has been resolved: net: restrict SO_REUSEPORT to inet sockets After blamed commit, crypto sockets could accidentally be destroyed from RCU call back, as spotted by zyzbot [1]. Trying to acquire a mutex in RCU callback is not allowed. Restrict SO_REUSEPORT socket option to inet sockets. v1 of this patch supported TCP, UDP and SCTP sockets, but fcnal-test.sh test needed RAW and ICMP support. [1] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:562 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 24, name: ksoftirqd/1 preempt_count: 100, expected: 0 RCU nest depth: 0, expected: 0 1 lock held by ksoftirqd/1/24: #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline] #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2561 [inline] #0: ffffffff8e937ba0 (rcu_callback){....}-{0:0}, at: rcu_core+0xa37/0x17a0 kernel/rcu/tree.c:2823 Preemption disabled at: [<ffffffff8161c8c8>] softirq_handle_begin kernel/softirq.c:402 [inline] [<ffffffff8161c8c8>] handle_softirqs+0x128/0x9b0 kernel/softirq.c:537 CPU: 1 UID: 0 PID: 24 Comm: ksoftirqd/1 Not tainted 6.13.0-rc3-syzkaller-00174-ga024e377efed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 __might_resched+0x5d4/0x780 kernel/sched/core.c:8758 __mutex_lock_common kernel/locking/mutex.c:562 [inline] __mutex_lock+0x131/0xee0 kernel/locking/mutex.c:735 crypto_put_default_null_skcipher+0x18/0x70 crypto/crypto_null.c:179 aead_release+0x3d/0x50 crypto/algif_aead.c:489 alg_do_release crypto/af_alg.c:118 [inline] alg_sock_destruct+0x86/0xc0 crypto/af_alg.c:502 __sk_destruct+0x58/0x5f0 net/core/sock.c:2260 rcu_do_batch kernel/rcu/tree.c:2567 [inline] rcu_core+0xaaa/0x17a0 kernel/rcu/tree.c:2823 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:561 run_ksoftirqd+0xca/0x130 kernel/softirq.c:950 smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK>
A flaw was found in the Linux kernel's device-mapper array component. This vulnerability allows a local attacker with administrative privileges to cause a denial of service (DoS) by loading or activating a storage device with corrupted array metadata. When encountering read errors on damaged storage blocks, the kernel incorrectly attempts to release an invalid block reference twice, resulting in a system crash.
In the Linux kernel, the following vulnerability has been resolved: selinux: ignore unknown extended permissions When evaluating extended permissions, ignore unknown permissions instead of calling BUG(). This commit ensures that future permissions can be added without interfering with older kernels.
A flaw was found in the Linux kernel's exFAT file system driver. A local user could exploit this vulnerability by mounting and accessing a corrupted or specially crafted exFAT storage volume containing self-referencing cluster chains. When reading the affected directory, the driver enters an infinite loop while retaining file system locks, preventing other tasks from proceeding and leading to a kernel hang that results in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc A NULL sock pointer is passed into l2cap_sock_alloc() when it is called from l2cap_sock_new_connection_cb() and the error handling paths should also be aware of it. Seemingly a more elegant solution would be to swap bt_sock_alloc() and l2cap_chan_create() calls since they are not interdependent to that moment but then l2cap_chan_create() adds the soon to be deallocated and still dummy-initialized channel to the global list accessible by many L2CAP paths. The channel would be removed from the list in short period of time but be a bit more straight-forward here and just check for NULL instead of changing the order of function calls. Found by Linux Verification Center (linuxtesting.org) with SVACE static analysis tool.
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: tests: Fix potential NULL dereference in test_cfg80211_parse_colocated_ap() kunit_kzalloc() may return NULL, dereferencing it without NULL check may lead to NULL dereference. Add a NULL check for ies.
A vulnerability was found in the Linux kernel's vmxnet3 network driver in the `vmxnet3_xdp_xmit_frame()` function. An incorrect DMA address calculation caused by the use of a fixed (rather than dynamic) offset leads to a corrupt packet being sent out and subsequently dropped on the path. This can lead to system instability and a denial of service caused by persistent packet loss.
The Linux Kernel lockdown mode for kernel versions starting on 6.12 and above for Fedora Linux has the lockdown mode disabled without any warning. This may allow an attacker to gain access to sensitive information such kernel memory mappings, I/O ports, BPF and kprobes. Additionally unsigned modules can be loaded, leading to execution of untrusted code breaking breaking any Secure Boot protection. This vulnerability affects only Fedora Linux.
A flaw was found in the Linux kernel's AFS (Andrew File System) implementation. This vulnerability can lead to a Denial of Service (DoS) due to improper validation of cell name lengths. A local user or remote service providing a cell name that exceeds the maximum filename length supported by the process filesystem (/proc) triggers a kernel warning and causes directory and mount point creation to fail.
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: dwmac-tegra: Read iommu stream id from device tree Nvidia's Tegra MGBE controllers require the IOMMU "Stream ID" (SID) to be written to the MGBE_WRAP_AXI_ASID0_CTRL register. The current driver is hard coded to use MGBE0's SID for all controllers. This causes softirq time outs and kernel panics when using controllers other than MGBE0. Example dmesg errors when an ethernet cable is connected to MGBE1: [ 116.133290] tegra-mgbe 6910000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx [ 121.851283] tegra-mgbe 6910000.ethernet eth1: NETDEV WATCHDOG: CPU: 5: transmit queue 0 timed out 5690 ms [ 121.851782] tegra-mgbe 6910000.ethernet eth1: Reset adapter. [ 121.892464] tegra-mgbe 6910000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 121.905920] tegra-mgbe 6910000.ethernet eth1: PHY [stmmac-1:00] driver [Aquantia AQR113] (irq=171) [ 121.907356] tegra-mgbe 6910000.ethernet eth1: Enabling Safety Features [ 121.907578] tegra-mgbe 6910000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported [ 121.908399] tegra-mgbe 6910000.ethernet eth1: registered PTP clock [ 121.908582] tegra-mgbe 6910000.ethernet eth1: configuring for phy/10gbase-r link mode [ 125.961292] tegra-mgbe 6910000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx [ 181.921198] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 181.921404] rcu: 7-....: (1 GPs behind) idle=540c/1/0x4000000000000002 softirq=1748/1749 fqs=2337 [ 181.921684] rcu: (detected by 4, t=6002 jiffies, g=1357, q=1254 ncpus=8) [ 181.921878] Sending NMI from CPU 4 to CPUs 7: [ 181.921886] NMI backtrace for cpu 7 [ 181.922131] CPU: 7 UID: 0 PID: 0 Comm: swapper/7 Kdump: loaded Not tainted 6.13.0-rc3+ #6 [ 181.922390] Hardware name: NVIDIA CTI Forge + Orin AGX/Jetson, BIOS 202402.1-Unknown 10/28/2024 [ 181.922658] pstate: 40400009 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 181.922847] pc : handle_softirqs+0x98/0x368 [ 181.922978] lr : __do_softirq+0x18/0x20 [ 181.923095] sp : ffff80008003bf50 [ 181.923189] x29: ffff80008003bf50 x28: 0000000000000008 x27: 0000000000000000 [ 181.923379] x26: ffffce78ea277000 x25: 0000000000000000 x24: 0000001c61befda0 [ 181.924486] x23: 0000000060400009 x22: ffffce78e99918bc x21: ffff80008018bd70 [ 181.925568] x20: ffffce78e8bb00d8 x19: ffff80008018bc20 x18: 0000000000000000 [ 181.926655] x17: ffff318ebe7d3000 x16: ffff800080038000 x15: 0000000000000000 [ 181.931455] x14: ffff000080816680 x13: ffff318ebe7d3000 x12: 000000003464d91d [ 181.938628] x11: 0000000000000040 x10: ffff000080165a70 x9 : ffffce78e8bb0160 [ 181.945804] x8 : ffff8000827b3160 x7 : f9157b241586f343 x6 : eeb6502a01c81c74 [ 181.953068] x5 : a4acfcdd2e8096bb x4 : ffffce78ea277340 x3 : 00000000ffffd1e1 [ 181.960329] x2 : 0000000000000101 x1 : ffffce78ea277340 x0 : ffff318ebe7d3000 [ 181.967591] Call trace: [ 181.970043] handle_softirqs+0x98/0x368 (P) [ 181.974240] __do_softirq+0x18/0x20 [ 181.977743] ____do_softirq+0x14/0x28 [ 181.981415] call_on_irq_stack+0x24/0x30 [ 181.985180] do_softirq_own_stack+0x20/0x30 [ 181.989379] __irq_exit_rcu+0x114/0x140 [ 181.993142] irq_exit_rcu+0x14/0x28 [ 181.996816] el1_interrupt+0x44/0xb8 [ 182.000316] el1h_64_irq_handler+0x14/0x20 [ 182.004343] el1h_64_irq+0x80/0x88 [ 182.007755] cpuidle_enter_state+0xc4/0x4a8 (P) [ 182.012305] cpuidle_enter+0x3c/0x58 [ 182.015980] cpuidle_idle_call+0x128/0x1c0 [ 182.020005] do_idle+0xe0/0xf0 [ 182.023155] cpu_startup_entry+0x3c/0x48 [ 182.026917] secondary_start_kernel+0xdc/0x120 [ 182.031379] __secondary_switched+0x74/0x78 [ 212.971162] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 7-.... } 6103 jiffies s: 417 root: 0x80/. [ 212.985935] rcu: blocking rcu_node structures (internal RCU debug): [ 212.992758] Sending NMI from CPU 0 to CPUs 7: [ 212.998539] NMI backtrace for cpu 7 [ 213.004304] CPU: 7 UID: 0 PI ---truncated---
A flaw was found in the Linux kernel's virtual socket (vsock) implementation. A local attacker can cause a Denial of Service (DoS) by crashing the operating system through a null-pointer dereference. This issue occurs when socket data or buffer checks are performed on a virtual socket that has been detached from its underlying transport mechanism during state transitions.
A flaw was found in the Linux kernel's i.MX8MP block controller driver. A local privileged user could cause a Denial of Service (DoS) during driver removal or system shutdown routines. Because the teardown function lacks a proper loop termination condition, the driver continues iterating past valid memory boundaries. This out-of-bounds access causes the kernel to crash.
A flaw was found in the Linux kernel. A local user could exploit this flaw to cause a Denial of Service (DoS) by crashing the system. The vulnerability exists within the virtual socket (VSOCK) subsystem due to improper handling of incoming packets when transport bindings change during interrupted connection attempts, resulting in a null pointer dereference.
A flaw was found in the quatech2 module in the Linux kernel. An incorrect check for invalid port numbers can cause a NULL pointer dereference and result in a denial of service.
In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in __read_vmcore (part 2) Since commit 5cbcb62dddf5 ("fs/proc: fix softlockup in __read_vmcore") the number of softlockups in __read_vmcore at kdump time have gone down, but they still happen sometimes. In a memory constrained environment like the kdump image, a softlockup is not just a harmless message, but it can interfere with things like RCU freeing memory, causing the crashdump to get stuck. The second loop in __read_vmcore has a lot more opportunities for natural sleep points, like scheduling out while waiting for a data write to happen, but apparently that is not always enough. Add a cond_resched() to the second loop in __read_vmcore to (hopefully) get rid of the softlockups.
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix a WARN during dereg_mr for DM type Memory regions (MR) of type DM (device memory) do not have an associated umem. In the __mlx5_ib_dereg_mr() -> mlx5_free_priv_descs() flow, the code incorrectly takes the wrong branch, attempting to call dma_unmap_single() on a DMA address that is not mapped. This results in a WARN [1], as shown below. The issue is resolved by properly accounting for the DM type and ensuring the correct branch is selected in mlx5_free_priv_descs(). [1] WARNING: CPU: 12 PID: 1346 at drivers/iommu/dma-iommu.c:1230 iommu_dma_unmap_page+0x79/0x90 Modules linked in: ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_mangle xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry ovelay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core fuse mlx5_core CPU: 12 UID: 0 PID: 1346 Comm: ibv_rc_pingpong Not tainted 6.12.0-rc7+ #1631 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:iommu_dma_unmap_page+0x79/0x90 Code: 2b 49 3b 29 72 26 49 3b 69 08 73 20 4d 89 f0 44 89 e9 4c 89 e2 48 89 ee 48 89 df 5b 5d 41 5c 41 5d 41 5e 41 5f e9 07 b8 88 ff <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 66 0f 1f 44 00 RSP: 0018:ffffc90001913a10 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88810194b0a8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001 RBP: ffff88810194b0a8 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f537abdd740(0000) GS:ffff88885fb00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f537aeb8000 CR3: 000000010c248001 CR4: 0000000000372eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __warn+0x84/0x190 ? iommu_dma_unmap_page+0x79/0x90 ? report_bug+0xf8/0x1c0 ? handle_bug+0x55/0x90 ? exc_invalid_op+0x13/0x60 ? asm_exc_invalid_op+0x16/0x20 ? iommu_dma_unmap_page+0x79/0x90 dma_unmap_page_attrs+0xe6/0x290 mlx5_free_priv_descs+0xb0/0xe0 [mlx5_ib] __mlx5_ib_dereg_mr+0x37e/0x520 [mlx5_ib] ? _raw_spin_unlock_irq+0x24/0x40 ? wait_for_completion+0xfe/0x130 ? rdma_restrack_put+0x63/0xe0 [ib_core] ib_dereg_mr_user+0x5f/0x120 [ib_core] ? lock_release+0xc6/0x280 destroy_hw_idr_uobject+0x1d/0x60 [ib_uverbs] uverbs_destroy_uobject+0x58/0x1d0 [ib_uverbs] uobj_destroy+0x3f/0x70 [ib_uverbs] ib_uverbs_cmd_verbs+0x3e4/0xbb0 [ib_uverbs] ? __pfx_uverbs_destroy_def_handler+0x10/0x10 [ib_uverbs] ? lock_acquire+0xc1/0x2f0 ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0x116/0x170 [ib_uverbs] ? lock_release+0xc6/0x280 ib_uverbs_ioctl+0xe7/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] __x64_sys_ioctl+0x1b0/0xa70 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f537adaf17b Code: 0f 1e fa 48 8b 05 1d ad 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ed ac 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffff218f0b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffff218f1d8 RCX: 00007f537adaf17b RDX: 00007ffff218f1c0 RSI: 00000000c0181b01 RDI: 0000000000000003 RBP: 00007ffff218f1a0 R08: 00007f537aa8d010 R09: 0000561ee2e4f270 R10: 00007f537aace3a8 R11: 0000000000000246 R12: 00007ffff218f190 R13: 000000000000001c R14: 0000561ee2e4d7c0 R15: 00007ffff218f450 </TASK>
CWE-703 - Improper Check or Handling of Exceptional ConditionsA flaw was found in the Linux kernel's extended Berkeley Packet Filter (eBPF) subsystem. When processing programs that use the `may_goto` instruction, extra stack space is allocated without properly updating the stack size index, triggering an out-of-bounds memory read in the interpreter array. A local user with privileges to load eBPF programs could exploit this vulnerability by submitting a crafted program, causing a system crash that leads to a Denial of Service (DoS) or potentially leaking sensitive kernel memory.
A flaw was found in the Linux kernel on the s390 architecture. A local user with low privileges could trigger a vulnerability by enabling ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP. This issue arises because kernel page table entries are modified without properly flushing the Translation Lookaside Buffer (TLB), which can lead to system crashes and potential data corruption. This could result in a denial of service.
A memory and information leak vulnerability was found in the Linux kernel's CIFS/SMB3 filesystem driver. When smb3_reconfigure() fails during smb3_sync_session_ctx_passwords(), the newly allocated password buffers (new_password and new_password2) are not freed or securely erased. This causes a memory leak and leaves sensitive password data in kernel memory that could potentially be exposed.
Loading 36.0 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.