Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63831mac802154: llsec: add skb_cow_data() before in-place crypto

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63831, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.31% · top 76% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 – < 3a2b378b3a9ca75d3518d879148d2ad25b5714a9
    • affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 – < 7a831bcd0486788283ef35e396d4282ee01bb0d5
    • affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 – < ff976ef7c39199ebff33c18034636595016db9f0
    • affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 – < e28e7fd34c449028325322a3f5127b92594b7396
    • affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 – < 993fd674fe85d114e6a8d3963033d4fbbc2170a8
    • affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 – < bd968bdd568beacfdf98ec537a87527e85f1d0cf
    • affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 – < 86d531337ea1ba02d9f2bc830d07c683d9bfaade
    • affected 03556e4d0dbbbf4af9df76f4a3839c86f6afb015 – < 84a04eb5b210643bd67aab81ff805d32f62aa865
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.260 – ≤ 5.10.*
    • unaffected 5.15.211 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.38 – ≤ 6.18.*
    • unaffected 7.1.3 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63831 badge
[![CVE-2026-63831](https://cveledger.app/badge/CVE-2026-63831.svg)](https://cveledger.app/cve/CVE-2026-63831)

Record last updated .