# CVE-2026-43279: ALSA: usb-audio: Add sanity check for OOB writes at silencing > A missing sanity check in the Linux kernel's ALSA USB audio driver allows out-of-bounds writes, leading to a system crash. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 May 2026 - **Updated:** 19 Oct 2026 - **Also known as:** BELL-CVE-2026-43279, DEBIAN-CVE-2026-43279, GHSA-2hw8-5267-5p9j, RHSA-2026:44522, RHSA-2026:46461, ROOT-OS-DEBIAN-11-CVE-2026-43279, ROOT-OS-UBUNTU-2204-CVE-2026-43279, ROOT-OS-UBUNTU-2404-CVE-2026-43279, UBUNTU-CVE-2026-43279 ## What is CVE-2026-43279? CVE-2026-43279 is a high-severity memory corruption vulnerability in Linux kernel, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Add sanity check for OOB writes at silencing At silencing the playback URB packets in the implicit fb mode before the actual playback, we blindly assume that the received packets fit with the buffer size. But when the setup in the capture stream differs from the playback stream (e.g. due to the USB core limitation of max packet size), such an inconsistency may lead to OOB writes to the buffer, resulting in a crash. For addressing it, add a sanity check of the transfer buffer size at prepare_silent_urb(), and stop the data copy if the received data overflows. Also, report back the transfer error properly from there, too. Note that this doesn't fix the root cause of the playback error itself, but this merely covers the kernel Oops. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2026-43279? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bpftool` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `bpftool-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-abi-whitelists` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-bootwrapper` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-debug` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-debug-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-debug-devel` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-debuginfo-common-ppc64` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-debuginfo-common-s390x` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-devel` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-doc` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-kdump` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-kdump-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-kdump-devel` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-tools` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-tools-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-tools-libs` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-tools-libs-devel` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `perf` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `perf-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `python-perf` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `python-perf-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:3.10.0-1160.157.1.el7 | | `kernel-rt` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-debug` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-debug-debuginfo` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-debug-devel` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-debuginfo` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-debuginfo-common-x86_64` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-devel` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-doc` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-trace` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-trace-debuginfo` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | | `kernel-rt-trace-devel` | Red Hat:rhel_extras_rt_els:7 | All versions | 0:3.10.0-1160.157.1.rt56.1309.el7 | Products: Linux kernel. ## How do I fix CVE-2026-43279? Apply the vendor's patch. ## Is CVE-2026-43279 being exploited? There is no known exploitation of CVE-2026-43279 in the wild and no public exploit code. ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-43279 and fix it if it is affected. What it is: CVE-2026-43279 is a high-severity memory corruption vulnerability in Linux kernel, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-43279 in the wild and no public exploit code. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-43279/ (Markdown: https://insights.sbomify.com/CVE-2026-43279/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43279 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43279 - OSV: https://osv.dev/vulnerability/CVE-2026-43279 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-43279/ Summaries are generated and may contain mistakes; the official description above is the record.