Skip to content
Systems

CVE-2026-72029

HIGH
High
EPSS 0.40%Patch availableAug 17, 2026

Linux iosm wwan decoder allows out-of-bounds reads and softirq DoS via crafted modem data.

common questions

Is CVE-2026-72029 being exploited?

Not confirmed. CVE-2026-72029 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.

How severe is CVE-2026-72029?

CVE-2026-72029 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72029?

Yes. A fix has been recorded for CVE-2026-72029. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72029 affect?

CVE-2026-72029 affects Linux kernel (iosm wwan driver), Embedded gateways/routers with iosm, Devices using affected cellular modems. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72029?

Apply vendor/kernel updates ASAP; isolate untrusted modems and monitor dmesg/syslog.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (iosm wwan driver)Embedded gateways/routers with iosmDevices using affected cellular modems
impact

Device-supplied indexes/lengths can cause OOB reads (info leak/crash) and an infinite softirq loop causing DoS; attacker controlling modem/downlink can trigger.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 1f52d7b622854b8bd7a1be3de095ca2e1f77098e and < 155851e501d6c649cbcfcca6472dc26269b04b6b
  • affected>= 1f52d7b622854b8bd7a1be3de095ca2e1f77098e and < 2b822df8e498aa6ca828e16afd8ffec27f7e4c88
  • affected>= 1f52d7b622854b8bd7a1be3de095ca2e1f77098e and < 55cfea8e8d9117ad086d1e1a0ff87f306f8e3ad0
  • affected>= 1f52d7b622854b8bd7a1be3de095ca2e1f77098e and < 07f5eb6d268a37bd9e131079489655cd599182e0
  • affected>= 1f52d7b622854b8bd7a1be3de095ca2e1f77098e and < 77f0023f22f6a2616ae128e9c93961b24ae52611
  • affected>= 1f52d7b622854b8bd7a1be3de095ca2e1f77098e and < 526b8ef54668780c8f69e0211c342763d5dcbad1
  • affected5.18
vendor says fixed in< 5.18, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free