High

Out-of-bounds write in Linux kernel dpaa2-switch

IdentifiersCVE-2026-43205CWE-787· Out-of-bounds Write

CVE-2026-43205 is a kernel memory corruption vulnerability in the Linux kernel's dpaa2-switch driver. The driver retrieves the number of switch interfaces from firmware through dpsw_get_attributes() and stores it in sw_attr.num_ifs, but failed to validate that value against the fixed maximum interface count, DPSW_MAX_IF, which is 64. That untrusted value is later used to control iteration in dpaa2_switch_fdb_get_flood_cfg(), which writes interface identifiers into a fixed-size if_id array sized for 64 entries. If firmware reports num_ifs greater than or equal to the maximum, the code can write past the end of the array. The flaw also affects the boundary case where num_ifs equals the maximum: after filling all available slots with matching ports, the function appends the control interface at index num_ifs, causing a one-entry overflow. The issue was resolved by adding bounds validation for num_ifs during dpaa2_switch_init().

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause kernel memory corruption through an out-of-bounds write in the dpaa2-switch driver. Depending on runtime conditions and what adjacent kernel memory is overwritten, impact may include kernel crashes, denial of service, data corruption, or potentially privilege escalation and arbitrary code execution in kernel context.

Mitigation

If you can’t patch tonight, do this now.

If an immediate patch cannot be applied, reduce exposure by disabling or avoiding use of affected dpaa2-switch functionality on systems that rely on this driver, and avoid deploying affected kernels in environments where firmware-provided switch attributes cannot be fully trusted. Restrict administrative changes involving the affected switching subsystem until patched kernels are installed. Because this is a kernel-space memory corruption issue, mitigation short of patching is limited.

Remediation

Patch, then assume compromise.

Apply a kernel update that includes the dpaa2-switch fix for CVE-2026-43205. The corrective change validates the firmware-supplied num_ifs value during dpaa2_switch_init() and rejects values greater than or equal to DPSW_MAX_IF, including the functionally unsafe boundary case where num_ifs equals 64. On vendor-distributed systems, install the relevant fixed kernel package from the operating system supplier and reboot to load the updated kernel.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

LinuxLinux Kerneloperating_system

Rocky LinuxRocky Linuxoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app

redhat accessNews

May 28, 2026

RHSA-2026:21557 - Security Advisory - Red Hat Customer Portal

A Linux kernel dpaa2-switch vulnerability that can cause kernel memory corruption via an out-of-bounds write.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity