What is the severity of CVE-2016-6350?

CVE-2016-6350 is classified as a denial of service vulnerability that allows local users to cause a system crash on OpenBSD versions 5.8 and 5.9.

How does CVE-2016-6350 exploit a vulnerability?

CVE-2016-6350 is exploited through a sysctl call with a path beginning with 10,9, leading to a null pointer dereference.

What versions of OpenBSD are affected by CVE-2016-6350?

CVE-2016-6350 affects OpenBSD 5.8 and 5.9.

How do I fix CVE-2016-6350?

To mitigate CVE-2016-6350, users should upgrade to the latest patched version of OpenBSD that addresses this vulnerability.

Can CVE-2016-6350 be exploited remotely?

CVE-2016-6350 cannot be exploited remotely as it requires local user access to the affected system.

Vulnerability/
CVE-2016-6350

medium

5.5

CWE

476

7/3/2017

6/8/2024

CVE-2016-6350: Null Pointer Dereference

First published: Tue Mar 07 2017(Updated: )

OpenBSD 5.8 and 5.9 allows local users to cause a denial of service (NULL pointer dereference and panic) via a sysctl call with a path starting with 10,9.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
OpenBSD	=5.8
OpenBSD	=5.9

Remedy

http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/kern/vfs_subr.c.diff?r1=1.248&r2=1.249

Remedy

http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/tmpfs/tmpfs_vfsops.c.diff?r1=1.9&r2=1.10

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6350?
CVE-2016-6350 is classified as a denial of service vulnerability that allows local users to cause a system crash on OpenBSD versions 5.8 and 5.9.
How does CVE-2016-6350 exploit a vulnerability?
CVE-2016-6350 is exploited through a sysctl call with a path beginning with 10,9, leading to a null pointer dereference.
What versions of OpenBSD are affected by CVE-2016-6350?
CVE-2016-6350 affects OpenBSD 5.8 and 5.9.
How do I fix CVE-2016-6350?
To mitigate CVE-2016-6350, users should upgrade to the latest patched version of OpenBSD that addresses this vulnerability.
Can CVE-2016-6350 be exploited remotely?
CVE-2016-6350 cannot be exploited remotely as it requires local user access to the affected system.

agent/type
agent/softwarecombine
agent/remedy
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/weakness
agent/last-modified-date
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/openbsd
canonical/openbsd
version/openbsd/5.8
version/openbsd/5.9

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-6350?
CVE-2016-6350 is classified as a denial of service vulnerability that allows local users to cause a system crash on OpenBSD versions 5.8 and 5.9.
How does CVE-2016-6350 exploit a vulnerability?
CVE-2016-6350 is exploited through a sysctl call with a path beginning with 10,9, leading to a null pointer dereference.
What versions of OpenBSD are affected by CVE-2016-6350?
CVE-2016-6350 affects OpenBSD 5.8 and 5.9.
How do I fix CVE-2016-6350?
To mitigate CVE-2016-6350, users should upgrade to the latest patched version of OpenBSD that addresses this vulnerability.
Can CVE-2016-6350 be exploited remotely?
CVE-2016-6350 cannot be exploited remotely as it requires local user access to the affected system.