dbcve.org
Debian LinuxOperating system · Debian

CVE-2015-8312

HIGH · 7.8 CVSS v3.0 Published 2016-05-13
Fix available
A fix is available. Upgrade to after 1.6.15 or later.
See remediation →
80/100
Remediation priority · High
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
Off-by-one error in afs_pioctl.c in OpenAFS before 1.6.16 might allow local users to cause a denial of service (memory overwrite and system crash) via a pioctl with an input buffer size of 4096 bytes.

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

An off-by-one error in afs_pioctl.c in OpenAFS before version 1.6.16 allows local users to cause a denial of service via memory overwrite and system crash by sending a pioctl with an input buffer size of 4096 bytes.

MitigationUpgrade OpenAFS to version 1.6.16 or later to patch the off-by-one error in the pioctl handler.

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
Debian LinuxOperating system
Affected:= 8.0= 9.0
OpenafsApplication
Affected:<= 1.6.15

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Verify OpenAFS installation
    Run 'dpkg -l openafs-client openafs-krb5' on Debian or check for /usr/vice/etc/AFS directory existence. Also check 'which afs' or look for afs daemon processes with 'ps aux | grep afs'.
    Affected if OpenAFS software is installed on the system
  2. Check OpenAFS version
    Run 'dpkg -l openafs-client' on Debian or use 'afsctl version' or check /usr/vice/etc/AFS/ThisCell. Version information may also appear in 'dmesg' when the kernel module loads.
    Affected if Installed version is 1.6.15 or earlier, or unknown/unspecified version on Debian 8.0 or 9.0 with OpenAFS
  3. Confirm pioctl interface is accessible
    Check if the AFS client is actively running: 'ps aux | grep afs' should show afsd or similar daemon processes. Also verify /proc/fs/openafs/ exists, indicating the AFS kernel module is loaded.
    Affected if AFS client daemon is running and the pioctl interface is active (required for exploitation)
  4. Verify kernel module is loaded
    Run 'lsmod | grep afs' or check 'cat /proc/modules | grep afs' to see if the openafs kernel module is loaded into the kernel.
    Affected if The OpenAFS kernel module is loaded in memory

A system is affected if OpenAFS version 1.6.15 or earlier is installed, the AFS client is actively running with the pioctl interface accessible, and the kernel module is loaded.

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
Upgrade available Upgrade to a release after 1.6.15
Interim mitigation

Upgrade OpenAFS to version 1.6.16 or later to patch the off-by-one error in the pioctl handler.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8312 — 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-2015-8312 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