High [CVE-2026-63831] add skb_cow_data before in-place crypto
This high-severity Red Hat Linux advisory covers CVE-2026-63831 affecting Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Red Hat Linux Linux Kernel publishes the next one.
See Red Hat Linux Linux Kernel's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Summary
In the Linux kernel, the following vulnerability has been resolved: mac802154: llsec: add skb_cow_data() before in-place crypto llsec_do_encrypt_unauth(), llsec_do_encrypt_auth(), llsec_do_decrypt_unauth(), and llsec_do_decrypt_auth() all perform in-place cryptographic transformations on skb data.
They build a scatterlist with sg_init_one() pointing into the skb's linear data area and then pass the same scatterlist as both src and dst to the crypto API (e.g. crypto_skcipher_encrypt/decrypt, crypto_aead_encrypt/decrypt).
On the RX path, __ieee802154_rx_handle_packet() clones the received skb before handing it to each subscriber via ieee802154_subif_frame(). The cloned skb shares the same underlying data buffer via reference counting.
When llsec_do_decrypt() subsequently modifies this shared buffer in place, it corrupts data that other clones -- potentially belonging to other sockets or subsystems -- still reference. On the TX path, similar data sharing can occur when an skb's head has been cloned (skb_cloned() returns true).
The fix is to call skb_cow_data() before performing any in-place crypto operation. skb_cow_data() ensures that the skb's data area is not shared: if the skb head is cloned or the data spans multiple fragments, it copies the data into a private buffer that can be safely modified in place.
- 802.15.4
Official advisory · high-confidence parse· fetched 7 days ago·verify at source
- kernel-0:6.12.0-211.59.1.el10_2
- kernel-0:6.12.0-55.113.1.el10_0
- kernel-rt-0:4.18.0-553.167.1.rt7.508.el8_10
- kernel-0:4.18.0-553.167.1.el8_10
- kernel-0:4.18.0-305.216.1.el8_4
- kernel-0:4.18.0-372.225.1.el8_6
- kernel-0:5.14.0-687.51.1.el9_8
- kernel-0:5.14.0-427.158.1.el9_4
- kernel-0:5.14.0-570.152.1.el9_6
- RHSA-2026:71233
- RHSA-2026:88687
- RHSA-2026:71016
- RHSA-2026:71213
- RHSA-2026:91585
- RHSA-2026:91493
- RHSA-2026:71232
- RHSA-2026:91489
- RHSA-2026:91492
Official advisory · high-confidence parse· fetched 7 days ago·verify at source
Mitigation
Upgrade to a fixed release: kernel-0:6.12.0-211.59.1.el10_2, kernel-0:6.12.0-55.113.1.el10_0, kernel-rt-0:4.18.0-553.167.1.rt7.508.el8_10, kernel-0:4.18.0-553.167.1.el8_10, kernel-0:4.18.0-305.216.1.el8_4, kernel-0:4.18.0-372.225.1.el8_6. That is the remediation for this advisory.
The vendor advisory may list interim mitigations or workarounds not captured here. Review it before change work.
Official advisory · high-confidence parse· fetched 7 days ago·verify at source
More Red Hat Linux advisories
- CVE-2026-46300May 13, 2026"Fragnesia" is a variant of Dirty Frag vulnerability in the ESP/XFRM leading to Local
- CVE-2026-31431Apr 22, 2026algif_aead - Revert to operating out-of-place
- CVE-2026-34486Apr 9, 2026Missing Encryption of Sensitive Data due to EncryptInterceptor bypass
- CVE-2025-31277Mar 18, 2026Processing maliciously crafted web content may lead to memory corruption
- CVE-2026-53362Jul 4, 2026account for fraggap on the paged allocation path
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.