LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22978: wifi: avoid kernel-infoleak from struct iw_point

In the Linux kernel, the following vulnerability has been resolved: wifi: avoid kernel-infoleak from struct iw_point struct iw_point has a 32bit hole on 64bit arches. struct iw_point { void __user *pointer; /* Pointer to the data (in user space) */ __u16 length; /* number of fields or size in bytes */ __u16 flags; /* Optional params */ }; Make sure to zero the structure to avoid disclosing 32bits of kernel data to user space.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22978 is a Linux kernel Wi-Fi information leak. On 64-bit systems, an uninitialized padding area in struct iw_point could expose 32 bits of kernel data to user space. The source bundle does not show remote exploitation, privilege escalation, CVSS scoring, or active exploitation.

Executive priority

Handle through normal kernel patch management unless local attackers are a major concern. The issue is a real kernel information leak, but current sources do not show active exploitation or severe impact indicators.

Technical view

The issue is in Linux kernel wireless handling around struct iw_point. Because the structure has a 32-bit hole on 64-bit architectures, failing to zero it can disclose kernel memory to user space. The fix described is to zero the structure before returning it.

Likely exposure

Exposure is most relevant to Linux systems using affected kernel builds with the wireless code path present. The bundle lists Linux as affected and provides stable kernel fix commits, but distro backport status and exact deployed exposure require local verification.

Exploitation context

The bundle supports a local user-space kernel information disclosure only. It does not cite KEV listing, public exploitation, remote attack, code execution, or privilege escalation. Treat exploitation impact as uncertain beyond limited kernel data disclosure.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. Key gaps are CVSS, CWE, precise branch range semantics, exploitability conditions, and whether leaked 32 bits are attacker-useful in realistic configurations.

Mitigation direction

  • Apply a vendor-supported Linux kernel update containing the referenced stable fixes.
  • For custom kernels, incorporate the matching upstream stable commit for the maintained branch.
  • Check Linux distribution advisories for backported fixes and package-specific version mapping.
  • Prioritize laptops, workstations, and embedded systems where wireless interfaces are enabled.

Validation and detection

  • Inventory Linux kernel versions across systems with wireless support enabled.
  • Map deployed kernels to vendor advisories or the referenced stable commits.
  • Confirm patched builds include the iw_point zero-initialization fix.
  • Review vulnerability scanner findings against actual distro backport metadata.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-22978 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4, 87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4, 87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4, 87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4, 87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4, 87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4, 87de87d5e47f94b4ea647a5bd1bc8dc1f7930db4unaffected
LinuxLinux2.6.27, 0, 5.10.248, 5.15.198, 6.1.161, 6.6.121, 6.12.66, 6.18.6, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.