Kernel out-of-bounds read via unchecked EEPROM counts
Published Oct 6, 2026 · Updated Oct 6, 2026
An out-of-bounds read in the Linux p54 wireless driver allows attackers to trigger a kernel memory over-read with malformed device EEPROM data. The p54_convert_rev0() and p54_convert_rev1() functions use channel and points-per-channel counts from a calibration entry without checking that the entry contains the declared data. Triggering the read requires a p54-supported device with a malformed EEPROM entry; the published reproducer demonstrates the over-read, not data disclosure or code execution.
Summary
What happened
An out-of-bounds read in the Linux p54 wireless driver allows attackers to trigger a kernel memory over-read with malformed device EEPROM data. The p54_convert_rev0() and p54_convert_rev1() functions use channel and points-per-channel counts from a calibration entry without checking that the entry contains the declared data. Triggering the read requires a p54-supported device with a malformed EEPROM entry; the published reproducer demonstrates the over-read, not data disclosure or code execution.
The record
- CVE
- CVE-2026-98188
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 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=eff1a59c48e3c6a006eb4fe5f2e405a996f2259d <03d313e3dfb49a44c10a5c423452967694fb85e2
- Affected versionversion=eff1a59c48e3c6a006eb4fe5f2e405a996f2259d <3bdcc4d61212b001b8752d80036509b4974ce16c
- Affected versionversion=eff1a59c48e3c6a006eb4fe5f2e405a996f2259d <41cdf14bf4b52fbe4673a172c2a6ad756cb08111
- Affected versionversion=eff1a59c48e3c6a006eb4fe5f2e405a996f2259d <42f4b03971f9d6329c4cbd1ea5155210d16ab65b
- Affected versionversion=eff1a59c48e3c6a006eb4fe5f2e405a996f2259d <4d767d6f8753db22bfc14c2724bd9cee677ffb03
- Affected versionversion=eff1a59c48e3c6a006eb4fe5f2e405a996f2259d <81084c967c18233b19799a0c3352ebac043f31e2
- Affected versionversion=eff1a59c48e3c6a006eb4fe5f2e405a996f2259d <b0c906107150b16925ee66da09127259864c7f36
- Affected versionversion=eff1a59c48e3c6a006eb4fe5f2e405a996f2259d <ce858fa6b8a214dee5adb82358885fa024cdd887
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started