BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2016
CVE-2015-8963High confidence

Affected product: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Unknown · Unknown

7.0HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 1.43% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

11 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 7 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.4.4.2-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.4.4.2-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.4.4.2-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.4.4.2-1Debian Security Tracker ↗Source updated 22 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 21 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 21 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 21 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 21 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 21 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 21 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 21 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2015-8819

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Race condition in kernel/events/core.c in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (use-after-free) by leveraging incorrect handling of an swevent data structure during a CPU unplug operation.

What

Race condition in kernel/events/core.c in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (use-after-free) by leveraging incorrect handling of an swevent data structure during a CPU unplug operation.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may disrupt the affected service.

What

Race condition in kernel/events/core.c in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (use-after-free) by leveraging incorrect handling of an swevent data structure during a CPU unplug operation.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → disrupt the affected service
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedDenial of serviceCWE-362
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Canadian Centre for Cyber Security · English · AV16-182Android security bulletin – November 2016

Number: AV16-182 Date: 8 November 2016 Purpose The purpose of this advisory is to bring attention to the Android Security Bulletin for November. Assessment The Android Security Bulletin addresses security updates for 48 vulnerabilities (15 Critical, 23 High, and 10 Moderate). The 15 vulnerabilities tagged as critical have the possibility of remote code execution and/or privilege escalation. CVE References: CVE-2012-6702, CVE-2014-9675, CVE-2014-9908, CVE-2015-0410, CVE-2015-1283, CVE-2015-8961, CVE-2015-8962, CVE-2015-8963, CVE-2015-8964, CVE-2016-0718, CVE-2016-2184, CVE-2016-3904, CVE-2016-3906, CVE-2016-3907, CVE-2016-5195, CVE-2016-5300, CVE-2016-6136, CVE-2016-6698, CVE-2016-6699, CVE-2016-6700, CVE-2016-6701, CVE-2016-6702, CVE-2016-6703, CVE-2016-6704, CVE-2016-6705, CVE-2016-6706, CVE-2016-6707, CVE-2016-6708, CVE-2016-6709, CVE-2016-6710, CVE-2016-6711, CVE-2016-6712, CVE-2016-6713, CVE-2016-6714, CVE-2016-6715, CVE-2016-6716, CVE-2016-6717, CVE-2016-6718, CVE-2016-6719, CVE-2016-6720, CVE-2016-6721, CVE-2016-6722, CVE-2016-6723, CVE-2016-6724, CVE-2016-6725, CVE-2016-6726, CVE-2016-6727, CVE-2016-6728, CVE-2016-6729, CVE-2016-6730, CVE-2016-6731, CVE

Official advisory ↗
CERT-FR · French · CERTFR-2017-AVI-233Multiples vulnérabilités dans le noyau Linux d'Ubuntu

2017 https://usn.ubuntu.com/usn/usn-3364-1/ Bulletin de sécurité Ubuntu USN-3364-2 du 24 juillet 2017 https://usn.ubuntu.com/usn/usn-3364-2/ Bulletin de sécurité Ubuntu USN-3364-3 du 25 juillet 2017 https://usn.ubuntu.com/usn/usn-3364-3/ Bulletin de sécurité Ubuntu USN-3371-1 du 28 juillet 2017 https://usn.ubuntu.com/usn/usn-3371-1/ Référence CVE CVE-2014-9900 https://www.cve.org/CVERecord?id=CVE-2014-9900 Référence CVE CVE-2015-8944 https://www.cve.org/CVERecord?id=CVE-2015-8944 Référence CVE CVE-2015-8955 https://www.cve.org/CVERecord?id=CVE-2015-8955 Référence CVE CVE-2015-8962 https://www.cve.org/CVERecord?id=CVE-2015-8962 Référence CVE CVE-2015-8963 https://www.cve.org/CVERecord?id=CVE-2015-8963 Référence CVE CVE-2015-8964 https://www.cve.org/CVERecord?id=CVE-2015-8964 Référence CVE CVE-2015-8966 https://www.cve.org/CVERecord?id=CVE-2015-8966 Référence CVE CVE-2015-8967 https://www.cve.org/CVERecord?id=CVE-2015-8967 Référence CVE CVE-2016-10088 https://www.cve.org/CVERecord?id=CVE-2016-10088 Référence CVE CVE-2016-10208 https://www.cve.org/CVERecord?id=CVE-2016-10208 Référence CVE CVE-2016-8405 https://www.cve.org/CVERecord?id=CVE-2016-8405 Référence CVE CVE-2016-8636 https://www.cve.org/CVERecord?id=CVE-2016-8636 Référence CVE CVE-2016-9083 https://www.cve.org/CVERecord?id=CVE-2016-908

Official advisory ↗
CERT-FR · French · CERTFR-2017-AVI-053Multiples vulnérabilités dans le noyau Linux de SUSE

ttent à un attaquant de provoquer une exécution de code arbitraire à distance, une exécution de code arbitraire et un déni de service. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité SUSE SUSE-SU-2017:0471-1 du 15 février 2017 https://www.suse.com//support/update/announcement/2017/suse-su-20170471-1.html Référence CVE CVE-2014-9904 https://www.cve.org/CVERecord?id=CVE-2014-9904 Référence CVE CVE-2015-8956 https://www.cve.org/CVERecord?id=CVE-2015-8956 Référence CVE CVE-2015-8962 https://www.cve.org/CVERecord?id=CVE-2015-8962 Référence CVE CVE-2015-8963 https://www.cve.org/CVERecord?id=CVE-2015-8963 Référence CVE CVE-2015-8964 https://www.cve.org/CVERecord?id=CVE-2015-8964 Référence CVE CVE-2016-1008 https://www.cve.org/CVERecord?id=CVE-2016-1008 Référence CVE CVE-2016-4470 https://www.cve.org/CVERecord?id=CVE-2016-4470 Référence CVE CVE-2016-4998 https://www.cve.org/CVERecord?id=CVE-2016-4998 Référence CVE CVE-2016-5696 https://www.cve.org/CVERecord?id=CVE-2016-5696 Référence CVE CVE-2016-5828 https://www.cve.org/CVERecord?id=CVE-2016-5828 Référence CVE CVE-2016-5829 https://www.cve.org/CVERecord?id=CVE-2016-5829 Référence CVE CVE-2016-6130 https://www.cve.org/CVERecord?id=CVE-2016-6130 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2017-AVI-050Multiples vulnérabilités dans le noyau Linux SUSE

De multiples vulnérabilités ont été corrigées dans le noyau Linux de SUSE . Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une exécution de code arbitraire et un déni de service.

Official advisory ↗
CERT-FR · French · CERTFR-2017-AVI-042Multiples vulnérabilités dans le noyau Linux de Suse

Enterprise Real Time Extension 12-SP1 Résumé De multiples vulnérabilités ont été corrigées dans le noyau Linux de Suse . Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une exécution de code arbitraire et un déni de service. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Suse suse-su-20170407-1 du 06 février 2017 https://www.suse.com//support/update/announcement/2017/suse-su-20170407-1.html Référence CVE CVE-2015-8962 https://www.cve.org/CVERecord?id=CVE-2015-8962 Référence CVE CVE-2015-8963 https://www.cve.org/CVERecord?id=CVE-2015-8963 Référence CVE CVE-2015-8964 https://www.cve.org/CVERecord?id=CVE-2015-8964 Référence CVE CVE-2016-1008 https://www.cve.org/CVERecord?id=CVE-2016-1008 Référence CVE CVE-2016-7910 https://www.cve.org/CVERecord?id=CVE-2016-7910 Référence CVE CVE-2016-7911 https://www.cve.org/CVERecord?id=CVE-2016-7911 Référence CVE CVE-2016-7913 https://www.cve.org/CVERecord?id=CVE-2016-7913 Référence CVE CVE-2016-7914 https://www.cve.org/CVERecord?id=CVE-2016-7914 Référence CVE CVE-2016-8399 https://www.cve.org/CVERecord?id=CVE-2016-8399 Référence CVE CVE-2016-8632 https://www.cve.org/CVERecord?id=CVE-2016-8632 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2016-AVI-370Multiples vulnérabilités dans Google Android (Nexus)

n Bulletin de sécurité Google du 07 novembre 2016 https://source.android.com/security/bulletin/2016-11-01.html Référence CVE CVE-2012-6702 https://www.cve.org/CVERecord?id=CVE-2012-6702 Référence CVE CVE-2014-9675 https://www.cve.org/CVERecord?id=CVE-2014-9675 Référence CVE CVE-2014-9908 https://www.cve.org/CVERecord?id=CVE-2014-9908 Référence CVE CVE-2015-0410 https://www.cve.org/CVERecord?id=CVE-2015-0410 Référence CVE CVE-2015-1283 https://www.cve.org/CVERecord?id=CVE-2015-1283 Référence CVE CVE-2015-8961 https://www.cve.org/CVERecord?id=CVE-2015-8961 Référence CVE CVE-2015-8962 https://www.cve.org/CVERecord?id=CVE-2015-8962 Référence CVE CVE-2015-8963 https://www.cve.org/CVERecord?id=CVE-2015-8963 Référence CVE CVE-2015-8964 https://www.cve.org/CVERecord?id=CVE-2015-8964 Référence CVE CVE-2016-0718 https://www.cve.org/CVERecord?id=CVE-2016-0718 Référence CVE CVE-2016-2184 https://www.cve.org/CVERecord?id=CVE-2016-2184 Référence CVE CVE-2016-3906 https://www.cve.org/CVERecord?id=CVE-2016-3906 Référence CVE CVE-2016-3907 https://www.cve.org/CVERecord?id=CVE-2016-3907 Référence CVE CVE-2016-5195 https://www.cve.org/CVERecord?id=CVE-2016-5195 Référence CVE CVE-2016-5300 https://www.cve.org/CVERecord?id=CVE-2016-5300 Référence CVE CVE-2016-6136 https://www.cve.org/CVERecord?id=CVE-2016-6136 Ré

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2015-007295Linux Kernel の kernel/events/core.c における権限を取得される脆弱性

Linux Kernel の kernel/events/core.c には、競合状態により、権限を取得される、またはサービス運用妨害 (解放済みメモリの使用 (use-after-free)) 状態にされる脆弱性が存在します。 補足情報 : CWE による脆弱性タイプは、CWE-416: Use After Free (解放済みメモリの使用) と識別されています。 https://cwe.mitre.org/data/definitions/416.html

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
n/a
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 16 Nov 2016 · Last source change 15 Oct 2024, 19:01 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2015-8819
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2015-8819 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2015-8819"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/commit?id=12ca6ad2e3a896256f086497a7c7406a547ee373; added patch: github.com/12ca6ad2e3a896256f086497a7c7406a547ee373; 1 further additions.
    Before
    no authoritative guidance recorded
    After
    patch: git.kernel.org/commit?id=12ca6ad2e3a896256f086497a7c7406a547ee373 · patch: github.com/12ca6ad2e3a896256f086497a7c7406a547ee373 · remediation: git.kernel.org/commit?id=12ca6ad2e3a896256f086497a7c7406a547ee373
    git.kernel.org ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    git.kernel.org ↗
  5. CVSS scoreCVSS scoring authority changed from CISA ADP to NIST NVD; the displayed base score remained 7.0.
    Before
    7.0 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H)
    After
    7.0 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H)
    NIST NVD ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2015-8963 · cve.blacktree.nl