Linux KernelOperating system · Linux
CVE-2013-2895
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 · unediteddrivers/hid/hid-logitech-dj.c in the Human Interface Device (HID) subsystem in the Linux kernel through 3.11, when CONFIG_HID_LOGITECH_DJ is enabled, allows physically proximate attackers to cause a denial of service (NULL pointer dereference and OOPS) or obtain sensitive information from kernel memory via a crafted device.
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 confidenceA NULL pointer dereference vulnerability exists in the hid-logitech-dj driver within the Linux kernel HID subsystem (through 3.11) when CONFIG_HID_LOGITECH_DJ is enabled. A physically proximate attacker with a crafted malicious HID device can trigger the NULL pointer dereference, causing a kernel OOPS (denial of service) or potentially read sensitive kernel memory contents.
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
<= 3.11= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.6= 3.0.7= 3.0.8= 3.0.9= 3.0.10CVSS 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- Complete
AV:L/AC:M/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify kernel versionRun 'uname -r' to get the running kernel version. Compare it against the affected range: versions <= 3.11, including all 3.0.x versions listed.Affected if The kernel version is 3.11 or earlier, or specifically any 3.0.x version.
-
Check if CONFIG_HID_LOGITECH_DJ is enabledLook for the kernel configuration file: run 'cat /boot/config-$(uname -r)' or 'zcat /proc/config.gz' (if available). Search for 'CONFIG_HID_LOGITECH_DJ' in the output.Affected if CONFIG_HID_LOGITECH_DJ is set to 'y' (built-in) or 'm' (module).
-
Determine if the driver is activeRun 'lsmod | grep hid_logitech_dj' to see if the module is currently loaded. If the kernel config showed '=y', the driver is built-in and always active.Affected if The module 'hid_logitech_dj' is loaded, or the driver is built into the kernel (CONFIG_HID_LOGITECH_DJ=y).
You are affected if your kernel version is 3.11 or earlier and the hid-logitech-dj driver is enabled (CONFIG_HID_LOGITECH_DJ is set to y or m), regardless of whether the module is currently loaded.
Generated from the published advisory. Verify against your own configuration.
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 dataApply a kernel security update that patches the hid-logitech-dj driver, or disable the CONFIG_HID_LOGITECH_DJ kernel configuration option if Logitech wireless devices are not required. For high-security environments, combine with physical access controls to prevent unauthorized device connection.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2895 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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