Kernel memory disclosure via unchecked firmware index
Published May 28, 2026 · Updated May 28, 2026
Out-of-bounds read in the Linux Kernel b43 wireless driver allows local users to read beyond its key array via a firmware-supplied index. In b43_rx(), a firmware-controlled index can exceed the 58-entry dev->key array because B43_WARN_ON records the condition without stopping the array access in production builds. Exposure requires the b43 driver, compatible Broadcom hardware, and firmware returning an invalid index; the published mechanism establishes memory disclosure but documents no code-execution path.
Summary
What happened
Out-of-bounds read in the Linux Kernel b43 wireless driver allows local users to read beyond its key array via a firmware-supplied index. In b43_rx(), a firmware-controlled index can exceed the 58-entry dev->key array because B43_WARN_ON records the condition without stopping the array access in production builds. Exposure requires the b43 driver, compatible Broadcom hardware, and firmware returning an invalid index; the published mechanism establishes memory disclosure but documents no code-execution path.
The record
- CVE
- CVE-2026-46122
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-129
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.24
- Affected versionversion=e4d6b7951812d98417feb10784e400e253caf633 <1e9e55cf66f0fa4799f4d86ef3aaba8e606b5c14
- Affected versionversion=e4d6b7951812d98417feb10784e400e253caf633 <1f4f78bf8549e6ac4f04fba4176854f3a6e0c332
- Affected versionversion=e4d6b7951812d98417feb10784e400e253caf633 <219ba67e69e49681e48c822d6eaafb5def032f34
- Affected versionversion=e4d6b7951812d98417feb10784e400e253caf633 <c3d7b90dc95020cd9282c4630e402fe224f7644e
- Affected versionversion=e4d6b7951812d98417feb10784e400e253caf633 <d7029879bafdac2006c67553807d122283dc6cbf
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo