| Revision Date: | 2015-05-27 | Version: | 1 | | Title: | CVE-2015-3331 on Ubuntu 16.04 LTS (xenial) - medium. | | 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. A memory corruption issue was discovered in AES decryption when using the Intel AES-NI accelerated code path. A remote attacker could exploit this flaw to cause a denial of service (system crash) or potentially escalate privileges on Intel base machines with AEC-GCM mode IPSec security association.
| | Family: | unix | Class: | vulnerability | | Status: | | Reference(s): | CVE-2015-3331
| | Platform(s): | Ubuntu 16.04 LTS
| Product(s): | | | Definition Synopsis | | Ubuntu 16.04 LTS (xenial) is installed. AND Package Information
linux package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19').
OR linux-aws package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1001.10').
OR linux-flo: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'abandoned').
OR linux-gke package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1003.3').
OR linux-goldfish: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'abandoned').
OR linux-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~16.04.1').
OR linux-mako: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'abandoned').
OR linux-meta package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19').
OR linux-meta-aws package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1001.10').
OR linux-meta-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~16.04.1').
OR linux-meta-raspi2 package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-1013.19').
OR linux-meta-snapdragon package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1012.12').
OR linux-raspi2 package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-1013.19').
OR linux-signed package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19').
OR linux-signed-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~16.04.1').
OR linux-snapdragon package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1012.12').
|
|