Skip to content
Threat Brief

← All advisories

CVE-2026-99765

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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 (generate_node_acls=1) login that allocates a dynamic NodeACL populates that ACL's per-LUN dev entries in core_tpg_add_node_to_devs() *before* the ACL is linked onto tpg->acl_node_list by target_add_node_acl(): core_tpg_check_initiator_node_acl(): ... core_tpg_add_node_to_devs(acl, tpg, NULL); /* builds deves */ target_add_node_acl(acl); /* only now listed */ The LUN teardown sweep, core_clear_lun_from_tpg(), enumerates only tpg->acl_node_list, 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 se_lun->lun_deve_list after core_tpg_remove_lun() frees the se_lun; when the same unpacked_lun is later re-added and the se_lun is reallocated at the same address, the stale dev entry is rediscovered by target_nacl_find_deve() and core_enable_device_list_for_node() corrupts lun_deve_list: BUG: KASAN: slab-use-after-free ... core_enable_device_list_for_node+0x5ce/0x880 core_tpg_add_node_to_devs+0x169/0x190 core_dev_add_lun+0x146/0x190 target_fabric_port_link+0xe9/0x1b0 configfs_symlink+0x381/0xae0 __x64_sys_symlink+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 se_lun->lun_shutdown and guarded the *explicit* ACL MappedLUN path (target_fabric_mappedlun_link()), but the demo-mode automatic path, core_tpg_add_node_to_devs() -> core_enable_device_list_for_node(), was never given the equivalent guard, and the publish-after-populate ordering in core_tpg_check_initiator_node_acl() was left unchanged. Fix it in three cooperating parts: 1) Publish the dynamic NodeACL onto acl_node_list *before* creating its dev entries, so the teardown sweep can observe them. 2) Refuse to attach a dev entry to an se_lun that is shutting down, checked under nacl->lun_entry_mutex -- the same lock the sweep takes -- so once the sweep has passed an ACL any later enable for that LUN observes lun_shutdown and skips it. 3) In core_enable_device_list_for_node(), insert the new dev entry onto lun->lun_deve_list while still holding nacl->lun_entry_mutex, in both the replace and the new-entry branch. Previously the entry was added to nacl->lun_entry_hlist under the mutex but to lun->lun_deve_list 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, core_disable_device_list_for_node() it (list_del() on the not-yet- linked lun_link succeeds and the entry is freed), and then the enable would list_add_tail() the freed entry back onto lun_deve_list. Linking both lists under the mutex makes enable and the sweep mutually exclusive, closing that window. core_tpg_add_node_to_devs() already ignores the return value of core_enable_device_list_for_node(), so a shutting-down LUN is simply skipped.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 3.10.108 before 3.113.11CVE Program
LinuxLinuxfrom 3.18.64 before 3.193.19CVE Program
LinuxLinuxfrom 4.1.47 before 4.24.2CVE Program
LinuxLinuxfrom 4.10.12 before 4.114.11CVE Program
LinuxLinuxfrom 4.4.81 before 4.54.5CVE Program
LinuxLinuxfrom 4.9.24 before 4.104.10CVE Program
LinuxLinuxfrom 49cb77e297dc611a1b795cfeb79452b3002bd331 before c8b6eec86742f736a913aba7d7c1d0cedb1d7751c8b6eec86742f736a913aba7d7c1d0cedb1d7751CVE Program
LinuxLinuxfrom 49cb77e297dc611a1b795cfeb79452b3002bd331 before 78ad4413fab0cbd42c7280b5069ed2dd3f03916278ad4413fab0cbd42c7280b5069ed2dd3f039162CVE Program
LinuxLinuxfrom 49cb77e297dc611a1b795cfeb79452b3002bd331 before 6a6e7d7230cd4e0a6c003bae5b85bf37a1e77b946a6e7d7230cd4e0a6c003bae5b85bf37a1e77b94CVE Program
LinuxLinux003bea4a702279fc339a0d2f1262e907364a2c73Not documentedCVE Program
LinuxLinux22113847cd117b26bd14316f735af79fc37cb6beNot documentedCVE Program
LinuxLinux2bf7791c6a5ec21228383f5a1fb5c443c3336622Not documentedCVE Program
LinuxLinux4.11Not documentedCVE Program
LinuxLinux8adc614240f1e2b793949d4efd9d344c970c116fNot documentedCVE Program
LinuxLinux92f8aa7bb825eafc3686cdda6dbbce44d8b35e75Not documentedCVE Program
LinuxLinuxca84f64e33058df99a8fa8ff88fc4c01b2fd8b17Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.11Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references