LiveActive security incident?Get immediate response
CVE Record

CVE-2014-4171: mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range not...

mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range notification and hole punching, which allows local users to cause a denial of service (i_mutex hold) by using the mmap system call to access a hole, as demonstrated by interfering with intended shmem activity by blocking completion of (1) an MADV_REMOVE madvise call or (2) an FALLOC_FL_PUNCH_HOLE fallocate call.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a local denial-of-service flaw in Linux shared-memory handling. A user who already has access to a system could interfere with certain memory/file operations and cause affected kernel activity to hang. It is not described as remote code execution or privilege escalation, but it can disrupt availability on shared or multi-user Linux systems. Exposure is most likely on older Linux kernels at or before 3.15.1, or downstream distribution kernels before Red Hat, SUSE, or Ubuntu fixes were applied. Systems with local shell, application, or tenant access are the relevant scope. Purely remote unauthenticated exposure is not supported by the sources. Handle through normal kernel patch governance, with faster action for shared or multi-user Linux systems. The business risk is service disruption by an already-local user, not confirmed remote compromise. Lack of CVSS and exploit evidence lowers urgency, but old unpatched kernels should not remain in production. Mitigation focus: Apply vendor kernel updates from Red Hat, SUSE, Ubuntu, or the relevant distribution.; Reboot into the fixed kernel after package installation.; Prioritize shared, multi-user, and tenant-hosting Linux systems..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2014-4171 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.