Skip to main content
Mallory
HighPublic exploit

Linux kernel CAN BCM integer overflow in net/can/bcm.c

IdentifiersCVE-2010-2959CWE-190· Integer Overflow or Wraparound

CVE-2010-2959 is an integer overflow vulnerability in net/can/bcm.c in the Linux kernel Controller Area Network (CAN) Broadcast Manager (BCM) implementation. In vulnerable kernel versions (before 2.6.27.53; 2.6.32.x before 2.6.32.21; 2.6.34.x before 2.6.34.6; and 2.6.35.x before 2.6.35.4), crafted CAN traffic can trigger an integer overflow in BCM processing, leading to memory corruption. This can be exploited to cause a kernel crash (denial of service) and, depending on conditions, potentially achieve arbitrary code execution in kernel context.

Share:
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.

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.

An attacker able to deliver crafted CAN BCM traffic to a vulnerable Linux kernel can trigger memory corruption resulting in a system crash (kernel panic/DoS) and may be able to execute arbitrary code in kernel context, implying full system compromise (e.g., ring-0 code execution) if exploitation is successful.

Mitigation

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

Reduce exposure of the CAN subsystem to untrusted traffic: disable CAN/BCM support if not required (e.g., unload/blacklist CAN-related kernel modules such as can_bcm where applicable), restrict access to CAN interfaces to trusted processes/users, and ensure CAN networks are physically/logically segmented so untrusted parties cannot inject CAN frames. Where feasible, apply network/host controls to prevent untrusted CAN message injection into the host’s CAN interface.

Remediation

Patch, then assume compromise.

Upgrade the Linux kernel to a version containing the fix: 2.6.27.53 or later in the 2.6.27 line; 2.6.32.21 or later in the 2.6.32 line; 2.6.34.6 or later in the 2.6.34 line; or 2.6.35.4 or later in the 2.6.35 line (or any newer maintained kernel). Apply vendor-provided kernel security updates for affected distributions.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

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
DebianDebian Linuxoperating_system
Fedora ProjectFedoraoperating_system
LinuxLinux Kerneloperating_system
OpensuseOpensuseoperating_system
SuseLinux Enterprise Desktopoperating_system
SuseLinux Enterprise High Availability Extensionoperating_system
SuseLinux Enterprise Real Timeoperating_system
SuseLinux Enterprise Serveroperating_system

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

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.
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 malware1

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 activity2

Community discussion across Reddit, Mastodon, and other social sources.