Menu

Star on GitHub · 3.2k

CVE-2016-2547

5.1 · MEDIUM

sound/core/timer.c in the Linux kernel before 4.4.1 employs a locking approach that does not consider slave timer instances, which allows local users to cause a denial of service (race condition, u…

Published Apr 27, 2016CWE-362EPSS 0.34%

Overview

CVE-2016-2547 is a medium-severity vulnerability. It was published on April 27, 2016 and has a CVSS 3.0 base score of 5.1 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 5.1, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

sound/core/timer.c in the Linux kernel before 4.4.1 employs a locking approach that does not consider slave timer instances, which allows local users to cause a denial of service (race condition, use-after-free, and system crash) via a crafted ioctl call.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-2547?

CVE-2016-2547 is a medium-severity vulnerability. It was published on April 27, 2016 and has a CVSS 3.0 base score of 5.1 (MEDIUM).

How severe is CVE-2016-2547?

This vulnerability has a CVSS 3.0 base score of 5.1, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-2547?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-2547?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-2547 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2016

View all