CVE-2015-3331

N/A

Published: May 27, 2015 at 10:00 AM UTC

Updated: June 17, 2026 at 12:25 AM UTC

3 products affected across 3 vendorsLinux KernelDebian LinuxUbuntu Linux

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 10%

Description

The __driver_rfc4106_decrypt function in arch/x86/crypto/aesni-intel_glue.c in the Linux kernel before 3.19.3 does not properly determine the memory locations used for encrypted data, which allows context-dependent attackers to cause a denial of service (buffer overflow and system crash) or possibly execute arbitrary code by triggering a crypto API call, as demonstrated by use of a libkcapi test program with an AF_ALG(aead) socket.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Ubuntu Linux · Canonicalrubygems

95%

12.04

Debian Linux · Debiandrupal

95%

7.0 8.0

Linux Kernel · Linux

95%

v < 3.2.693.12 ≤ v < 3.12.403.13 ≤ v < 3.14.373.15 ≤ v < 3.16.353.17 ≤ v < 3.18.113.19 ≤ v < 3.19.33.3 ≤ v < 3.4.1083.5 ≤ v < 3.10.73

Affected range stops below 3.10.73, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.12.40, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.14.37, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.16.35, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.18.11, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.19.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.2.69, so it looks safe — our inference, not a vendor statement

Affected range stops below 3.4.108, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references