nday
CVE-2026-99558

blk-crypto: fix NULL deref and UAF in __blk_crypto_evict_key()

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-19T14:45Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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

blk-crypto: fix NULL deref and UAF in __blk_crypto_evict_key()

Sashiko reported a possible NULL pointer dereference, triggered by the following flow:

dm-inlinecrypt ctor            # first use of the fallback
 ├─ blk_crypto_init_key()      # succeeds, ctx->key.size != 0
 ├─ blk_crypto_start_using_key()
 │   ├─ hw-wrapped key: -EOPNOTSUPP
 │   │    # profile never allocated (NULL)
 │   └─ raw key: fallback_start_using_mode()
 │      └─ blk_crypto_fallback_init() fails
 │         └─ kfree(profile)   # not NULLed
 ├─ goto bad
 └─ inlinecrypt_dtr()          # evicts whenever key.size is set
    └─ blk_crypto_evict_key()
       └─ blk_crypto_config_supported_natively() = false
          └─ blk_crypto_fallback_evict_key()
             └─ __blk_crypto_evict_key(blk_crypto_fallback_profile)
                └─ profile->num_slots # BOOM!!!

This issue can be reproduced using the following commands:

dd if=/dev/zero of=/tmp/backing bs=1M count=64
LOOP=$(losetup -f --show /tmp/backing)
SZ=$(blockdev --getsz $LOOP)
KEY=$(head -c 64 /dev/urandom | od -An -tx1 | tr -d ' \n')
dmsetup create ic --table "0 $SZ inlinecrypt aes-xts-plain64 \
  $KEY 0 $LOOP 0 1 keytype:hw-wrapped"

And the following oops is triggered:

==================================================================
blk-crypto: loop0: no support for wrapped keys
Oops: general protection fault, probably for non-canonical address
      0xdffffc000000000b: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000058-0x000000000000005f]
CPU: 5 UID: 0 PID: 901 Comm: dmsetup 7.3.0-rc3 #1 PREEMPT(lazy)
RIP: 0010:__blk_crypto_evict_key+0x2e/0x3b0
Call Trace:
 blk_crypto_evict_key+0x24c/0x320
 inlinecrypt_dtr+0xf6/0x160
 inlinecrypt_ctr+0x2d3/0xbd0
 dm_table_add_target+0x661/0xf40
 table_load+0x1c4/0x490
 ctl_ioctl+0x32f/0x5f0
 dm_ctl_ioctl+0xe/0x20
==================================================================

dm-inlinecrypt is the only caller that can evict a key that was never started, as fscrypt frees such a key without evicting it.

Fix this by returning early from blk_crypto_fallback_evict_key() when tfms_inited[] is not set for the key's mode. tfms_inited[] is only set after blk_crypto_fallback_init() has successfully initialized the profile, so the crash above is no longer reachable.

The bug has been latent since commit c984ff1423ae ("blk-crypto: dynamically allocate fallback profile") was merged in v6.5, and only became actually triggerable when commit e7f57d2c47e2 ("dm-inlinecrypt: add target for inline block device encryption") was merged in v7.2.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , observed live · raw
{
  "id": 484874,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-99558",
  "occurred_at": "2026-11-19T14:45:29.873Z",
  "observed_at": "2026-11-19T15:00:30.436713Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2026-11-19T14:45:29.873Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.