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.
Your early warning system for new security vulnerabilities
Open BETA
Every day brings a flood of new vulnerabilities, roughly 100 CVEs daily. Which one will really affect you?
Attacks on known but unpatched vulnerabilities (Common Vulnerabilities and Exposures, or CVEs for short) are among the most common entry points for hackers. Companies must continuously check for such vulnerabilities. Does this affect our products? Which versions are affected? How critical is it?
As the window between publication and exploitation by attackers keeps shrinking, companies are under more pressure than ever to find a high-quality solution for managing these risks as quickly as possible. However, IT teams are heavily time-constrained, making manual tracking of all relevant CVEs nearly impossible.
100+ new CVEs per day
Most CVEs are irrelevant to your infrastructure
Time-to-exploit < 5 days
Attackers are exploiting vulnerabilities faster than ever before
Manual research is time-consuming
Vendor websites, RSS feeds, and blogs need to be searched daily
Vulnerability scanners are lagging behind
Plugin development isn't progressing fast enough to identify risks in a timely manner
CVE Alarm provides you with immediate notifications of relevant security vulnerabilities
CVE Alarm continuously monitors all newly published CVEs and automatically compares them with the products you use. You will only be notified if a relevant vulnerability affects your systems and meets your defined criteria.
Real-time notification
Direct email notification without delay
Product-based filters
Only CVEs that actually affect your infrastructure
Custom criteria
Filter by CVSS-Score, exposure, products, and vendors
Team-oriented & multi-tenant capable
Assign products or alerts to specific teams or customers
More time to act
Administrators can review and install updates faster
Time savings
No more manually reviewing the flood of new CVE information
Three steps for better patch planning
With CVE Alarm you will easily receive relevant security alerts for your infrastructure.
Subscribe To Products
Select the IT products you use. From Apache to VMware – all critical assets are monitored.
Define Criteria
Set product-specific filters based on criticality (CVSS ≥ 7.0 (high)). You will only receive relevant alerts.
Get Notified
Receive an immediate notification as soon as a matching CVE appears. Recipients can be defined individually for each product.
Be faster than the attackers
With CVE information, you have more time for patch planning and can close security gaps before they are exploited.
Designed for the target group companies and service providers
Whether a global Security Operations Center or a small IT team, CVE Alarm supports CVE monitoring for organizations of all sizes.
Companies with their own IT infrastructure
Medium-sized to large companies that need to proactively monitor their vulnerabilities
Administrators
IT professionals responsible for infrastructure security and maintenance
Security teams and cybersecurity experts
Security Operations Centers (SOCs) and Computer Emergency Response Teams (CERTs) that require CVE information for proactive security measures
Chief Information Security Officers (CISOs) & IT managers
Decision-makers who need an overview of critical vulnerabilities
Security service providers
Managed service providers (MSPs) and security consultancies that manage multiple clients and need to monitor CVEs
From experience to innovation. About us and CVE Alarm.
CVE Alarm is a product of AVABIS GmbH and was developed in collaboration with IT security experts.
AVABIS GmbH – Who are we? We, AVABIS GmbH, are an experienced partner for IT quality assurance. Our focus is on software testing and software development. Our clients, corporations from various industries, have trusted us for more than ten years.
CVE Alarm – How did the idea come about? In our daily project work, we repeatedly witnessed the significant uncertainty surrounding new security alerts. We saw how much time teams have to invest to determine whether a published vulnerability even affects their own system landscape. Based on these experiences, we know how time-consuming it is to gather, evaluate, and prioritize information from diverse sources under time pressure.
This made us realize that the real problem is not a lack of information, but rather an overabundance of it.
This led to the idea of developing a product that enables companies to manage this information overload and maintain control over their IT security.
Developed and operated in Germany Our systems run on German IT infrastructure, and we adhere to high security and data protection standards. This ensures data sovereignty, clear responsibilities, and reliability, especially for organizations with their own security teams or CERT structures.
Get in contact with our team
Do you have questions about CVE Alarm or would you like a personal consultation? We're happy to help.
Please use our contact form.
An error occurred while processing the form, please check your entries.
Thank you for getting in contact with our company
We have received your message and looking forward to speaking with you. We will get back to you personally as soon as possible.