Skip to main content
Menu
CVEs

Linux kernel use-after-free in SCSI target demo-mode ACL entries

CVE-2026-99765Published November 20, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 3.11, 3.19, 4.2, 4.5, 4.10, and 1 more
Who is exposed
Not reported

Summary

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.

What to do

Upgrade to a fixed version: 3.11, 3.19, 4.2, 4.5, 4.10, or one of 1 more.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99765 (scsi: target: Fix demo-mode dynamic ACL dev-entry UAF vs LUN teardown), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99765 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 3.10.108, fixed in 3.11; from 3.18.64, fixed in 3.19; from 4.1.47, fixed in 4.2; from 4.4.81, fixed in 4.5; from 4.9.24, fixed in 4.10; from 4.10.12, fixed in 4.11
- Linux Linux: versions 4.11
Fixed versions: 3.11, 3.19, 4.2, 4.5, 4.10, 4.11.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99765 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99765 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/c8b6eec86742f736a913aba7d7c1d0cedb1d7751
- https://git.kernel.org/stable/c/78ad4413fab0cbd42c7280b5069ed2dd3f039162
- https://git.kernel.org/stable/c/6a6e7d7230cd4e0a6c003bae5b85bf37a1e77b94
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99765
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99765"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-99765

Is CVE-2026-99765 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-99765?

Linux: from 3.10.108 before 3.11; from 3.18.64 before 3.19; from 4.1.47 before 4.2; from 4.4.81 before 4.5; from 4.9.24 before 4.10; from 4.10.12 before 4.11. Linux: version 4.11.

Source: cve.now feed data

How do I fix CVE-2026-99765?

Upgrade to a fixed version: 3.11, 3.19, 4.2, 4.5, 4.10, or one of 1 more.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.