{"id":"CVE-2026-72047","summary":"ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nieee802154: ca8210: fix pointer truncation in kfifo on 64-bit\n\nca8210_test_int_driver_write() and ca8210_test_int_user_read() exchange\na kmalloc'd buffer pointer through a struct kfifo, but pass a literal\n'4' as the byte count to kfifo_in()/kfifo_out().\n\nThis is correct on 32-bit (pointer = 4 bytes), but on 64-bit only the\nlow 4 bytes of the 8-byte pointer are written into the FIFO. The reader\nthen reads back 4 bytes into an 8-byte local pointer variable, leaving\nthe upper 4 bytes uninitialized stack data. The first dereference of\nthe reconstructed pointer (fifo_buffer[1]) accesses an arbitrary kernel\naddress and generally results in an oops.\n\nUse sizeof(fifo_buffer) so the byte count matches pointer width on every\narchitecture.\n\nThe driver has no architecture restriction in Kconfig, so any 64-bit\nbuild with CONFIG_IEEE802154_CA8210_DEBUGFS=y is exposed. Issue has\nbeen latent since the driver was added in 2017 because it is most\ncommonly deployed on 32-bit MCUs.\n\nFound via a custom Coccinelle semantic patch hunting for short-byte\nkfifo I/O on byte-mode kfifos used to shuttle pointers.","modified":"2026-08-18T03:31:24.221524944Z","published":"2026-08-15T05:52:05.510Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72047.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/093aacb0c56d5c693e3169a0224062e77c3fd0c0"},{"type":"WEB","url":"https://git.kernel.org/stable/c/1fe2643d0b24ca3cdd61a31a45c2d3233dc6cbfe"},{"type":"WEB","url":"https://git.kernel.org/stable/c/2059c28bd725beded01277cdf1f67be33e714323"},{"type":"WEB","url":"https://git.kernel.org/stable/c/2c1664ccfae653979b38788211240b5a1ee317ed"},{"type":"WEB","url":"https://git.kernel.org/stable/c/65dc342274a01616f5c17105f7360a3b4bfd7a3d"},{"type":"WEB","url":"https://git.kernel.org/stable/c/6d7f7bcf225b2d566176bf6229dbd1252940cb3c"},{"type":"WEB","url":"https://git.kernel.org/stable/c/87dab14a4f68895d6f4d798e6ee3556cd64e8c72"},{"type":"WEB","url":"https://git.kernel.org/stable/c/d8ce67fa6a5e6929f5414e933ff9665176c2bce6"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72047.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72047"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"ded845a781a578dfb0b5b2c138e5a067aa3b1242"},{"fixed":"2c1664ccfae653979b38788211240b5a1ee317ed"},{"fixed":"093aacb0c56d5c693e3169a0224062e77c3fd0c0"},{"fixed":"87dab14a4f68895d6f4d798e6ee3556cd64e8c72"},{"fixed":"1fe2643d0b24ca3cdd61a31a45c2d3233dc6cbfe"},{"fixed":"65dc342274a01616f5c17105f7360a3b4bfd7a3d"},{"fixed":"2059c28bd725beded01277cdf1f67be33e714323"},{"fixed":"d8ce67fa6a5e6929f5414e933ff9665176c2bce6"},{"fixed":"6d7f7bcf225b2d566176bf6229dbd1252940cb3c"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72047.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.12.0"},{"fixed":"5.10.261"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.212"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.178"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.145"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.97"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.40"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.5"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72047.json"}}],"schema_version":"1.9.0"}