Kernel information disclosure via uninitialized structure padding
Published Jan 23, 2026 · Updated Jan 23, 2026
Information disclosure in the Linux Kernel allows local users to read 32 bits of kernel data through affected wireless ioctl paths. The WEXT compatibility paths in net/wireless/wext-core.c and wext-priv.c populate struct iw_point without clearing its four-byte padding, exposing residual kernel memory to user space. Exploitation requires a low-privileged local user on a 64-bit system that can invoke the affected wireless ioctl paths; the reported consequence is limited to disclosure.
Summary
What happened
Information disclosure in the Linux Kernel allows local users to read 32 bits of kernel data through affected wireless ioctl paths. The WEXT compatibility paths in net/wireless/wext-core.c and wext-priv.c populate struct iw_point without clearing its four-byte padding, exposing residual kernel memory to user space. Exploitation requires a low-privileged local user on a 64-bit system that can invoke the affected wireless ioctl paths; the reported consequence is limited to disclosure.
The record
- CVE
- CVE-2026-22978
- Published
- Jan 23, 2026
- Updated
- Jan 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2026CVE publishedPublication date reported by the CVE source.
- Jan 23, 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.27
- Affected versionversion=87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4 <024f71a57d563fbe162e528c8bf2d27e9cac7c7b
- Affected versionversion=87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4 <21cbf883d073abbfe09e3924466aa5e0449e7261
- Affected versionversion=87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4 <442ceac0393185e9982323f6682a52a53e8462b1
- Affected versionversion=87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4 <a3827e310b5a73535646ef4a552d53b3c8bf74f6
- Affected versionversion=87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4 <d21ec867d84c9f3a9845d7d8c90c9ce35dbe48f8
- Affected versionversion=87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4 <d943b5f592767b107ba8c12a902f17431350378c
- Affected versionversion=87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4 <e3c35177103ead4658b8a62f41e3080d45885464
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
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo