mac802154: llsec: add skb_cow_data() before in-place crypto
Summary
| CVE | CVE-2026-63831 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-19 12:16:56 UTC |
| Updated | 2026-07-20 15:16:49 UTC |
| Description | 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. This is the same pattern used by: - ESP (net/ipv4/esp4.c, net/ipv6/esp6.c) - MACsec (drivers/net/macsec.c) - WireGuard (drivers/net/wireguard/receive.c) - TIPC (net/tipc/crypto.c) Without this guard, in-place crypto on shared skb data leads to: - Silent data corruption of other skb clones - Use-after-free when the crypto API scatterwalk writes through a page that has already been freed by another clone's kfree_skb() - Kernel crashes under concurrent 802.15.4 traffic with security enabled (KASAN/KMSAN reports slab-use-after-free) Found by 0sec (https://0sec.ai) using automated source analysis. |
Risk And Classification
Primary CVSS: v3.1 8.8 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.001690000 probability, percentile 0.065260000 (date 2026-07-20)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 8.8 | HIGH | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 8.8 | HIGH | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
AdjacentAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 3a2b378b3a9ca75d3518d879148d2ad25b5714a9 git | Not specified |
| CNA | Linux | Linux | affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 7a831bcd0486788283ef35e396d4282ee01bb0d5 git | Not specified |
| CNA | Linux | Linux | affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 ff976ef7c39199ebff33c18034636595016db9f0 git | Not specified |
| CNA | Linux | Linux | affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 e28e7fd34c449028325322a3f5127b92594b7396 git | Not specified |
| CNA | Linux | Linux | affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 993fd674fe85d114e6a8d3963033d4fbbc2170a8 git | Not specified |
| CNA | Linux | Linux | affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 bd968bdd568beacfdf98ec537a87527e85f1d0cf git | Not specified |
| CNA | Linux | Linux | affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 86d531337ea1ba02d9f2bc830d07c683d9bfaade git | Not specified |
| CNA | Linux | Linux | affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 84a04eb5b210643bd67aab81ff805d32f62aa865 git | Not specified |
| CNA | Linux | Linux | affected 3.16 | Not specified |
| CNA | Linux | Linux | unaffected 3.16 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.260 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.211 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.177 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.144 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.95 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.38 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.3 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/3a2b378b3a9ca75d3518d879148d2ad25b5714a9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/86d531337ea1ba02d9f2bc830d07c683d9bfaade | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ff976ef7c39199ebff33c18034636595016db9f0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/993fd674fe85d114e6a8d3963033d4fbbc2170a8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/84a04eb5b210643bd67aab81ff805d32f62aa865 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e28e7fd34c449028325322a3f5127b92594b7396 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7a831bcd0486788283ef35e396d4282ee01bb0d5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/bd968bdd568beacfdf98ec537a87527e85f1d0cf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.