Home / CVE DB / CVE-2016-4486
Standard
Vulnerability Identifier

CVE-2016-4486

2016-05-23
Severity Assessment
LOW
CVSS v3.x Score
Clinical Analysis (Description)

The rtnl_fill_link_ifmap function in net/core/rtnetlink.c in the Linux kernel before 4.5.5 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel stack memory by reading a Netlink message.

Vector Sequencing

Attack Parameters

Impact Consequences

Technical Impact

CVSS v2 Score (Legacy)
2.1

For backward compatibility

EPSS Probability
0.52%

Percentile: 66.9%

Weakness Classification

CWE-CWE-200

Affected Population

Affected Configurations

Total: 14 detected entries

Software List Scrollable
ca
ubuntu_linux
Vendor: canonical • v14.04
no
suse_linux_enterprise_real_time_extension
Vendor: novell • v12.0
no
suse_linux_enterprise_live_patching
Vendor: novell • v12.0
no
suse_linux_enterprise_server
Vendor: novell • v11.0
ca
ubuntu_linux
Vendor: canonical • v16.04
no
suse_linux_enterprise_module_for_public_cloud
Vendor: novell • v12.0
no
suse_linux_enterprise_software_development_kit
Vendor: novell • v11.0
no
suse_linux_enterprise_server
Vendor: novell • v12.0
no
suse_linux_enterprise_workstation_extension
Vendor: novell • v12.0
no
suse_linux_enterprise_desktop
Vendor: novell • v12.0
ca
ubuntu_linux
Vendor: canonical • v15.10
ca
ubuntu_linux
Vendor: canonical • v12.04
no
suse_linux_enterprise_debuginfo
Vendor: novell • v11.0
no
suse_linux_enterprise_software_development_kit
Vendor: novell • v12.0
Timeline

Time Line

PUBLICATION
23 May 2016
MODIFICATION
12 Apr 2025
Impact Statistics

Key Metrics

CVSS Score
LOW
Products
14
Affected
Public Exploit Available
Remediation Protocol

Recommended Solution

No automatic solution found. Check vendor references.
Patch Library
No direct patch listed in database.
Recommended Actions for Administrators

Immediate Action Plan

1. Inventory

Identify all affected systems in your infrastructure.

2. Assessment

Assess exposure and criticality for your organization.

3. Mitigation

Apply patches or available workarounds.

4. Verification

Test and confirm effectiveness of applied measures.