dbcve.org
Linux KernelOperating system · Linux

CVE-2011-3593

MEDIUM · 5.7 CVSS v2.0 Published 2013-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A certain Red Hat patch to the vlan_hwaccel_do_receive function in net/8021q/vlan_core.c in the Linux kernel 2.6.32 on Red Hat Enterprise Linux (RHEL) 6 allows remote attackers to cause a denial of service (system crash) via priority-tagged VLAN frames.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the vlan_hwaccel_do_receive function in net/8021q/vlan_core.c of Linux kernel 2.6.32 on RHEL 6 allows remote attackers to crash the system by sending specially crafted priority-tagged VLAN frames. The flaw exists in how the kernel handles VLAN packet processing with priority tags.

MitigationApply the Red Hat kernel security update for CVE-2011-3593 to patch the vulnerable vlan_hwaccel_do_receive function. Organizations running RHEL 6 with VLAN interfaces should prioritize patching as the attack vector is network-adjacent remote DoS.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:= 2.6.32
Enterprise LinuxOperating system
Affected:= 6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:A/AC:M/Au:N/C:N/I:N/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the running kernel version
    Run 'uname -r' or check '/proc/version' to determine the exact kernel version
    Affected if The kernel version is exactly 2.6.32 or matches the RHEL 6.0 kernel baseline
  2. Confirm the operating system is RHEL 6
    Run 'cat /etc/redhat-release' or 'cat /etc/os-release' to verify the OS version
    Affected if The system is Red Hat Enterprise Linux 6.0 or equivalent CentOS/Oracle Linux 6
  3. Determine if VLAN interfaces are configured
    Run 'ip link show' or 'ls /proc/net/vlan/' to list active VLAN interfaces
    Affected if Any VLAN interfaces (such as eth0.100, bond0.50, etc.) are present and active on the system
  4. Check if 8021q kernel module is loaded
    Run 'lsmod | grep 8021q' to see if the VLAN module is currently loaded in memory
    Affected if The 8021q module is loaded and the system is processing VLAN-tagged network traffic
  5. Verify VLAN configuration in network scripts
    Check /etc/sysconfig/network-scripts/ for ifcfg-* files containing VLAN_ID= or VLAN=yes directives
    Affected if VLAN interfaces are configured in the network scripts and enabled at boot

A system is affected if it runs Linux kernel 2.6.32 on RHEL 6 and has VLAN interfaces actively configured or the 8021q module loaded, as the vulnerability triggers when processing priority-tagged VLAN frames on such configurations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Red Hat kernel security update for CVE-2011-3593 to patch the vulnerable vlan_hwaccel_do_receive function. Organizations running RHEL 6 with VLAN interfaces should prioritize patching as the attack vector is network-adjacent remote DoS.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-3593 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data