dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2025-29338

MEDIUM · 5.6 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NXP moal.ko Wi-Fi driver 5.1.7.10 FW version from v17.92.1.p149.43 To v17.92.1.p149.157 was discovered to contain a buffer overflow via the mod_para parameter in the woal_init_module_param function.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability exists in the NXP moal.ko Wi-Fi driver (versions 5.1.7.10 with firmware between v17.92.1.p149.43 and v17.92.1.p149.157). The overflow occurs in the woal_init_module_param function through improper bounds checking on the mod_para parameter, potentially allowing local or adjacent attackers to execute code or cause denial of service.

MitigationUpdate the Wi-Fi driver firmware to a version beyond v17.92.1.p149.157 from NXP or the device manufacturer. Until patched, restrict network access and minimize exposure of affected wireless interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the NXP moal.ko Wi-Fi driver is loaded
    Run 'lsmod | grep moal' to list loaded kernel modules, or check /proc/modules for 'moal'
    Affected if The moal module appears in the loaded module list - the driver must be active for the vulnerability to be exploitable
  2. Determine the installed driver version
    Run 'modinfo moal' or check the module file version in /lib/modules/$(uname -r)/kernel/drivers/net/wireless/
    Affected if The driver version reported is exactly 5.1.7.10 (this is the only confirmed vulnerable driver version)
  3. Query the wireless firmware version
    Use 'iw list' or check /sys/class/net/*/device/firmware_version, or run 'ethtool -i <interface>' on the wireless interface
    Affected if The firmware version falls within the range v17.92.1.p149.43 through v17.92.1.p149.157 inclusive
  4. Verify the vulnerable function can be triggered
    Check if the wireless interface is present via 'ip link show' or 'iw dev', as the woal_init_module_param function executes during module initialization
    Affected if A wireless interface managed by the moal driver exists and is exposed - the overflow occurs during module parameter handling at load time
  5. Confirm module parameter exposure
    Run 'modinfo moal' to list module parameters; the vulnerability involves improper bounds checking on the mod_para parameter
    Affected if The moal module accepts mod_para parameters and the driver is built with the vulnerable code path

You are affected if the moal.ko driver version 5.1.7.10 is loaded with firmware version between v17.92.1.p149.43 and v17.92.1.p149.157 - both conditions must be true simultaneously.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Wi-Fi driver firmware to a version beyond v17.92.1.p149.157 from NXP or the device manufacturer. Until patched, restrict network access and minimize exposure of affected wireless interfaces.

Recommended fix Moderate confidence

Any NXP moal.ko Wi-Fi driver release with firmware version newer than v17.92.1.p149.157 (e.g., v17.92.1.p149.158 or later)

  1. Identify the current moal.ko driver version and firmware version currently installed on the affected system
  2. Contact NXP directly or visit the official NXP support website to obtain the latest fixed driver/firmware version
  3. Download the updated moal.ko driver package with a firmware version newer than v17.92.1.p149.157
  4. Unload the existing wireless driver module: sudo modprobe -r moal (or reboot into a recovery mode)
  5. Install the updated moal.ko driver following NXP's installation documentation
  6. Reboot the system to load the new kernel module
  7. Verify the driver loaded successfully and confirm the new firmware version matches a version beyond v17.92.1.p149.157
Caveat Kernel driver updates may require matching firmware versions; ensure host driver and firmware are from the same release to avoid compatibility issues

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29338 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29338 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data