CVE-2026-15461
The Sierra Wireless HL78xx modem GNSS driver (drivers/modem/hl78xx/, later drivers/modem/vendor_standalone/hl78xx/) embeds a generic struct gnss_nmea0183_match_data match_data inside struct hl78xx_gnss_data. The generic NMEA0183 match helper (drivers/gnss/gnss_nmea0183_match.c) requires that context to be the first member because its callbacks cast user_data directly to struct gnss_nmea0183_match_data . In the affected releases match_data was the second member (after const struct device dev), so it sat at a non-zero offset while gnss_nmea0183_match_init() initialized it at the correct address. The registered NMEA handlers instead pass the whole device data object (data->devices.gnss->data, offset 0), producing an offset-shifted type confusion between where state is initialized and where the parse callbacks read and write it. When NMEA sentences from the GNSS receiver are parsed, the GGA/RMC callbacks write parsed fix data into the wrong location within the struct, and the GSV callback (gnss_nmea0183_match_gsv_callback, active under CONFIG_GNSS_SATELLITES) reads its satellites pointer and bound from the wrong offsets — non-pointer bytes of struct hl78xx_gnss_data — and then writes parsed struct gnss_satellite entries through that bogus pointer. This is a write through an uninitialized/wild pointer with a garbage bound. The NMEA handlers are registered by default (CONFIG_HL78XX_GNSS_SOURCE_NMEA is the default GNSS source) on devices using the HL78xx GNSS. The driver runs in kernel context and the NMEA data originates from the GNSS radio front-end, so a party able to influence the GNSS signal (for example GNSS/GPS spoofing at radio proximity) can drive the kernel-side parser into the faulty write. The most likely impact is a crash (denial of service) because the bogus pointer resolves to a fixed near-NULL value, with adjacent-memory corruption possible on MMU-less targets. Confidentiality is not affected. Exploitation requires the satellites feature to be enabled and active, so attack complexity is high.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.3
- CVSS vector
- CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- CWE
- CWE-843
- Published
- 2026-09-10
- Last modified
- 2026-09-10
Affected products
- zephyrproject zephyr
Weakness type
Related vulnerabilities
- CVE-2026-45764 — Suricata http2: protocol-change type confusion can lead to denial of service
- CVE-2026-45762 — Suricata defrag: missing address-family check can lead to remote crash
- CVE-2026-87528 — Type confusion in Rust in Google Chrome on on Windows prior to 153.0.8010.36 allowed a remote...
- CVE-2026-87636 — Type confusion in XML in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to...
- CVE-2026-87612 — Type confusion in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute...
- CVE-2026-87564 — Type confusion in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to read...
- CVE-2026-80161 — Acrobat Reader | Access of Resource Using Incompatible Type ('Type Confusion') (CWE-843)
- CVE-2026-81401 — Microsoft Excel Information Disclosure Vulnerability