AZL-115678: CVE-2026-99765 affecting package kernel 6.6.161.1-1

Published Nov 20, 2026
·
Updated

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

scsi: target: Fix demo-mode dynamic ACL dev-entry UAF vs LUN teardown

A demo-mode (generatenodeacls=1) login that allocates a dynamic NodeACL populates that ACL's per-LUN dev entries in coretpgaddnodetodevs() before the ACL is linked onto tpg->aclnodelist by targetaddnodeacl():

coretpgcheckinitiatornodeacl(): ... coretpgaddnodetodevs(acl, tpg, NULL); / builds deves / targetaddnodeacl(acl); / only now listed /

The LUN teardown sweep, coreclearlunfromtpg(), enumerates only tpg->aclnodelist, so a dev entry whose ACL is still in the window above is invisible to the sweep and is never disabled. It is left on the selun->lundevelist after coretpgremovelun() frees the selun; when the same unpackedlun is later re-added and the selun is reallocated at the same address, the stale dev entry is rediscovered by targetnaclfinddeve() and coreenabledevicelistfornode() corrupts lundevelist:

BUG: KASAN: slab-use-after-free ... coreenabledevicelistfornode+0x5ce/0x880 coretpgaddnodetodevs+0x169/0x190 coredevaddlun+0x146/0x190 targetfabricportlink+0xe9/0x1b0 configfssymlink+0x381/0xae0 x64syssymlink+0x55/0x80

The demo-mode login path that drives the ACL/dev-entry creation is reachable by an unauthenticated initiator; the colliding LUN add/remove is a local configfs operation.

Commit 49cb77e297dc ("target: Avoid mappedlun symlink creation during lun shutdown") introduced selun->lunshutdown and guarded the explicit ACL MappedLUN path (targetfabricmappedlunlink()), but the demo-mode automatic path, coretpgaddnodetodevs() -> coreenabledevicelistfornode(), was never given the equivalent guard, and the publish-after-populate ordering in coretpgcheckinitiatornodeacl() was left unchanged.

Fix it in three cooperating parts:

1) Publish the dynamic NodeACL onto aclnodelist before creating its dev entries, so the teardown sweep can observe them.

2) Refuse to attach a dev entry to an selun that is shutting down, checked under nacl->lunentrymutex -- the same lock the sweep takes -- so once the sweep has passed an ACL any later enable for that LUN observes lunshutdown and skips it.

3) In coreenabledevicelistfornode(), insert the new dev entry onto lun->lundevelist while still holding nacl->lunentrymutex, in both the replace and the new-entry branch. Previously the entry was added to nacl->lunentryhlist under the mutex but to lun->lundevelist only after dropping it; with the ACL now published early, the sweep could take the mutex in that gap, find the entry on the hlist, coredisabledevicelistfornode() it (listdel() on the not-yet- linked lunlink succeeds and the entry is freed), and then the enable would listaddtail() the freed entry back onto lundevelist. Linking both lists under the mutex makes enable and the sweep mutually exclusive, closing that window.

coretpgaddnodetodevs() already ignores the return value of coreenabledevicelistfornode(), so a shutting-down LUN is simply skipped.

Affected Software

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

Event History

Nov 20, 2026
Advisory Published
via OSV·06:18 AM
Data Sourced
via OSV·06:18 AM
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