Bug 1454757 (CVE-2017-9211)

Summary: CVE-2017-9211 kernel: Null pointer dereference due to missing key-size check in setkey function
Product: [Other] Security Response Reporter: Adam Mariš <amaris>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aquini, bhu, dhoward, fhrbata, gansalmon, hwkernel-mgr, iboverma, ichavero, itamar, jforbes, jkacur, jonathan, jross, jwboyer, kernel-maint, kernel-mgr, lgoncalv, madhu.chinakonda, mchehab, mcressma, nmurray, pholasek, ptalbert, rvrbovsk, slawomir, williams, wmealing
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
The crypto_skcipher_init_tfm function in crypto/skcipher.c in the Linux kernel through 4.11.2 relies on a setkey function that lacks a key-size check, which allows local users to cause a denial of service (NULL pointer dereference) via a crafted application.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-27 10:52:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1454759, 1458154, 1458155, 1458156    
Bug Blocks: 1454767    

Description Adam Mariš 2017-05-23 12:37:51 UTC
The crypto_skcipher_init_tfm function in crypto/skcipher.c in the Linux kernel through 4.11.2 relies on a setkey function that lacks a key-size check, which allows local users to cause a denial of service (NULL pointer dereference) via a crafted application.

Upstream patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/crypto?id=9933e113c2e87a9f46a40fde8dafbf801dca1ab9

Comment 1 Adam Mariš 2017-05-23 12:38:54 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1454759]

Comment 5 Justin M. Forbes 2018-01-29 17:29:19 UTC
This was fixed for fedora with the 4.11.4 stable updates.