AZL-115100: CVE-2026-99558 affecting package kernel 6.6.161.1-1

Published Nov 19, 2026
·
Updated

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

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

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

dm-inlinecrypt ctor # first use of the fallback ├─ blkcryptoinitkey() # succeeds, ctx->key.size != 0 ├─ blkcryptostartusingkey() │ ├─ hw-wrapped key: -EOPNOTSUPP │ │ # profile never allocated (NULL) │ └─ raw key: fallbackstartusingmode() │ └─ blkcryptofallbackinit() fails │ └─ kfree(profile) # not NULLed ├─ goto bad └─ inlinecryptdtr() # evicts whenever key.size is set └─ blkcryptoevictkey() └─ blkcryptoconfigsupportednatively() = false └─ blkcryptofallbackevictkey() └─ blkcryptoevictkey(blkcryptofallbackprofile) └─ profile->numslots # 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:blkcryptoevictkey+0x2e/0x3b0 Call Trace: blkcryptoevictkey+0x24c/0x320 inlinecryptdtr+0xf6/0x160 inlinecryptctr+0x2d3/0xbd0 dmtableaddtarget+0x661/0xf40 tableload+0x1c4/0x490 ctlioctl+0x32f/0x5f0 dmctlioctl+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 blkcryptofallbackevictkey() when tfmsinited[] is not set for the key's mode. tfmsinited[] is only set after blkcryptofallbackinit() 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.

Affected Software

1 affected component
azure-linux/kernel<=6.6.161.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    In blk_crypto_fallback_evict_key(), return early when tfms_inited[] is not set for the key's mode.

Event History

Nov 19, 2026
Advisory Published
via OSV·03:18 PM
Data Sourced
via OSV·03:18 PM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203