Bug 1959657 (CVE-2020-24588) - CVE-2020-24588 kernel: wifi frame payload being parsed incorrectly as an L2 frame
Summary: CVE-2020-24588 kernel: wifi frame payload being parsed incorrectly as an L2 f...
Keywords:
Status: NEW
Alias: CVE-2020-24588
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1960122 1960123 1978181 1960121 1960124
Blocks: 1959275
TreeView+ depends on / blocked
 
Reported: 2021-05-12 03:45 UTC by Wade Mealing
Modified: 2021-09-15 05:47 UTC (History)
41 users (show)

Fixed In Version: kernel 5.13 rc5
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the Linux kernels wifi implementation. An attacker within wireless broadcast range can inject custom data into the wireless communication circumventing checks on the data. This can cause the frame to pass checks and be considered a valid frame of a different type.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Wade Mealing 2021-05-12 03:45:56 UTC
A flaw was found in the Linux kernels wifi implementation. An attacker within wireless broadcast range can inject custom data into the wireless communication circumventing checks on the data.  This can cause the frame to pass checks and be considered a valid frame of a different type.

Upstream fix:
https://lore.kernel.org/linux-wireless/20210511200110.25d93176ddaf.I9e265b597f2cd23eb44573f35b625947b386a9de@changeid/

Comment 6 Wade Mealing 2021-05-13 05:42:44 UTC
Mitigation:

Mitigation for this issue is either not available or the currently available options does not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Comment 7 Wade Mealing 2021-05-13 05:44:27 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1960121]

Comment 12 Justin M. Forbes 2021-06-29 16:16:45 UTC
This was fixed for Fedora in the 5.12.9 stable kernel updates.


Note You need to log in before you can comment on or make changes to this bug.