Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-9986

kernel: Double fetch in the intr function in sound/oss/msnd_pinnacle.c

Overview

Published
28 Jun 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
3 OS packages
4 Linux distributions
Yes Fix available

Description

The intr function in sound/oss/msnd_pinnacle.c in the Linux kernel through 4.11.7 allows local users to cause a denial of service (over-boundary access) or possibly have unspecified other impact by changing the value of a message queue head pointer between two kernel reads of that value, aka a "double fetch" vulnerability.

Source: OX vulnerability database

Severity

7.8 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
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

Weakness: CWE-125

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

debian 4 releases · 1 package

fixed 4
linux
debian fixes for CVE-2017-9986
ReleasePackageFixed in
11 linux 4.15.4-1
12 linux 4.15.4-1
13 linux 4.15.4-1
14 linux 4.15.4-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2017-9986
ReleasePackageFixed in
linux 4.15.4-1

root.io debian 3 releases · 1 package

fixed 3
rootio-linux
root.io debian fixes for CVE-2017-9986
ReleasePackageFixed in
11 rootio-linux 4.15.4-1
12 rootio-linux 4.15.4-1
13 rootio-linux 4.15.4-1

ubuntu 1 release · 1 package

fixed 1
linux-snapdragon
ubuntu fixes for CVE-2017-9986
ReleasePackageFixed in
18.04 linux-snapdragon 4.15.0-1053.57

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.