CVE-2026-72047: ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit

Published Aug 15, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit

ca8210testintdriverwrite() and ca8210testintuserread() exchange a kmalloc'd buffer pointer through a struct kfifo, but pass a literal '4' as the byte count to kfifoin()/kfifoout().

This is correct on 32-bit (pointer = 4 bytes), but on 64-bit only the low 4 bytes of the 8-byte pointer are written into the FIFO. The reader then reads back 4 bytes into an 8-byte local pointer variable, leaving the upper 4 bytes uninitialized stack data. The first dereference of the reconstructed pointer (fifobuffer[1]) accesses an arbitrary kernel address and generally results in an oops.

Use sizeof(fifobuffer) so the byte count matches pointer width on every architecture.

The driver has no architecture restriction in Kconfig, so any 64-bit build with CONFIGIEEE802154CA8210DEBUGFS=y is exposed. Issue has been latent since the driver was added in 2017 because it is most commonly deployed on 32-bit MCUs.

Found via a custom Coccinelle semantic patch hunting for short-byte kfifo I/O on byte-mode kfifos used to shuttle pointers.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Change ca8210 byte-mode kfifo calls to use sizeof(fifo_buffer) as the kfifo_in()/kfifo_out() byte count instead of the literal ‘4’, so the byte count matches pointer width on 64-bit systems (prevents pointer truncation/oops).

    ca8210 kfifo usage kfifo_in()/kfifo_out() byte-count argument = sizeof(fifo_buffer)

Event History

Aug 15, 2026
CVE Published
via MITRE·05:52 AM
Data Sourced
via MITRE·05:52 AM
Description
Data Sourced
via NVD·06:21 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-72047?

The severity of CVE-2026-72047 is rated at risk level 43.

2

How do I fix CVE-2026-72047?

You can fix CVE-2026-72047 by updating to the patched version of the Linux kernel that addresses the pointer truncation issue.

3

What systems are affected by CVE-2026-72047?

CVE-2026-72047 affects the Linux kernel when using the ieee802154 subsystem.

4

What are the potential impacts of CVE-2026-72047?

The potential impact of CVE-2026-72047 includes buffer overflow vulnerabilities that could lead to memory corruption.

5

When was CVE-2026-72047 published?

CVE-2026-72047 was published on August 15, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203