KEYS: trusted: Do not use WARN when encode fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f2219745250f388edacabe6cca73654131c67d0a · < 050bf3c793a07f96bd1e2fd62e1447f731ed733b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KEYS: trusted: Do not use WARN when encode fails
When asn1_encode_sequence() fails, WARN is not the correct solution.
1. asn1_encode_sequence() is not an internal function (located in lib/asn1_encode.c). 2. Location is known, which makes the stack trace useless. 3. Results a crash if panic_on_warn is set.
It is also noteworthy that the use of WARN is undocumented, and it should be avoided unless there is a carefully considered rationale to use it.
Replace WARN with pr_err, and print the return value instead, which is only useful piece of information.
From the CVE record · Linux
The Linux kernel's trusted keys code uses WARN when ASN.1 sequence encoding fails. If panic_on_warn is enabled, triggering that failure can crash the system. The input does not specify how the failure can be triggered or whether access or user interaction is required.
Operators running the Linux kernel should check their vendor's advisory for affected versions; none are specified in the input.