New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 900902 link

Starred by 1 user
Status: WontFix
Owner:
zsm@chromium.org
Closed: Nov 1
Cc:
wonderfly@google.com
█ sawlani@google.com
groeck@chromium.org
allenwebb@google.com
chromeos-kernel-security-bug-access@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug-Security



Sign in to add a comment

CVE-2018-14619 CrOS: Vulnerability reported in Linux kernel

Project Member Reported by vomit.go...@appspot.gserviceaccount.com, Nov 1 
VOMIT (go/vomit) has received an external vulnerability report for the Linux kernel. 

Advisory: CVE-2018-14619
  Details: http://vomit.googleplex.com/advisory?id=CVE/CVE-2018-14619
  CVSS severity score: 7.2/10.0
  Description:

A flaw was found in the crypto subsystem of the Linux kernel before version kernel-4.15-rc4. The "null skcipher" was being dropped when each af_alg_ctx was freed instead of when the aead_tfm was freed. This can cause the null skcipher to be freed while it is still in use leading to a local user being able to crash the system or possibly escalate privileges.



This bug was filed by http://go/vomit
Please contact us at vomit-team@google.com if you need any assistance.

Comment 1 by allenwebb@chromium.org, Nov 1

Cc: allenwebb@google.com
Labels: Security_Impact-Stable Security_Severity-Low Pri-3
Owner: groeck@chromium.org
Status: Assigned (was: Untriaged)
Feel free to reassign as necessary.

This looks like this only has DoS potential. We do build the af_alg module and it looks like it is used by bluez.

Comment 2 by zsm@google.com, Nov 1

Cc: groeck@chromium.org wonderfly@google.com sawlani@google.com
Labels: -Security_Impact-Stable Security_Impact-None
Owner: zsm@chromium.org
Status: WontFix (was: Assigned)
The upstream commit is b32a7dc8ae("crypto: algif_aead - fix reference counting of null skcipher")

This commit is present in v4.14, and on cros/chromeos-4.19. 

Unless I'm missing something, CONFIG_CRYPTO_USER_API_AEAD does not seem to be set in any of the chromeos kernels; crypto/algif_aead.o is not linked in.

Marking as WontFix.
►

Sign in to add a comment