staging: rtl8723bs: fix missing shared-key auth challenge length check
Summary
| CVE | CVE-2026-74649 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-22 16:16:38 UTC |
| Updated | 2026-08-22 16:16:38 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
staging: rtl8723bs: fix missing shared-key auth challenge length check
The WEP shared-key authentication handler uses the challenge-text
element's attacker-controlled length without checking it against the
fixed 128-byte chg_txt buffer.
In OnAuthClient() the length from rtw_get_ie() - up to 255 - is used
to perform memcpy() into the 128-byte pmlmeinfo->chg_txt, so a
malicious AP sending a malformed WLAN_EID_CHALLENGE element can
overflow/underfill chg_txt by up to 127 bytes. It is reachable over the
air, before association, during shared-key authentication. In the case
of an overflow, the driver can write out of bounds. In the case of an
underfill, the driver can echo stale buffer memory.
The challenge text is defined to be exactly 128 octets, which is
already provided as the WLAN_AUTH_CHALLENGE_LEN define; require the
element to be exactly that length before use. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b 39ae1033071001af9bb4573ebdbb43bbbe88f749 git |
Not specified |
| CNA |
Linux |
Linux |
affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b 4d018e7d7d908bdfcb5ecfa922b1d5cb9ddb3722 git |
Not specified |
| CNA |
Linux |
Linux |
affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b 4ba402fd47009d20e51dbfc934abb562098ea35b git |
Not specified |
| CNA |
Linux |
Linux |
affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b 87c2f073d2aaea041d531b8e579c47570b54b3b7 git |
Not specified |
| CNA |
Linux |
Linux |
affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b a28a4b0592e4a37ea471bc0d308513a93133ce7e git |
Not specified |
| CNA |
Linux |
Linux |
affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b 6235b5156b48ed5d1ce3410d8f0b2fd67d30d944 git |
Not specified |
| CNA |
Linux |
Linux |
affected 554c0a3abf216c991c5ebddcdb2c08689ecd290b 2c56ef658ac8c6bca36bc5574715e8f717207c6c git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.12 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.12 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.216 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.183 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.152 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.104 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.45 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.9 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/87c2f073d2aaea041d531b8e579c47570b54b3b7 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a28a4b0592e4a37ea471bc0d308513a93133ce7e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6235b5156b48ed5d1ce3410d8f0b2fd67d30d944 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/39ae1033071001af9bb4573ebdbb43bbbe88f749 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4d018e7d7d908bdfcb5ecfa922b1d5cb9ddb3722 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4ba402fd47009d20e51dbfc934abb562098ea35b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2c56ef658ac8c6bca36bc5574715e8f717207c6c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.