In the Linux kernel, the following vulnerability has been resolved:
ocfs2/cluster: unlink socket containers before releasing resources
A socket container's node and socket must remain alive while the
container is on sock_containers. The debugfs formatter reads sc_node
and sc_sock under o2net_debug_lock without taking their references, but
sc_kref_release() releases both before taking that lock to unlink the
container.
With CONFIG_DEBUG_FS enabled, a synchronous sender can retain its last
socket-container reference after o2net_disconnect_node() has detached
the connection and flushed o2net_wq. The caller runs outside that
workqueue. After the sender removes its configfs dependency, node
removal can proceed without waiting for the sender's final sc_put():
Sender (final sc_put) Configfs rmdir Debugfs reader
-------------------- -------------- --------------
o2nm_undepend_item()
Drop node item refs
o2nm_node_put()
[node can be freed]
sc_seq_show()
Lock debug lock
Read sc_node->nd_name
Unlock debug lock
sc_node = NULL
o2net_debug_del_sc()
The earlier socket release has a similar window. The container is
still selectable while its socket has been released and sc_sock has
not yet been cleared:
Sender (final sc_put) Debugfs reader
-------------------- --------------
sock_release(sc->sc_sock)
[socket can be freed]
sc_seq_show()
Lock debug lock
Read sc_sock->sk fields
Unlock debug lock
sc_sock = NULL
...
o2net_debug_del_sc()
Move o2net_debug_del_sc() before releasing either resource. Unlinking
under the existing debug lock waits for an active formatter to finish
and prevents later readers from selecting the container. This covers
both socket fields and node fields, including nd_num in the stats
formatter.
KASAN report as below:
BUG: KASAN: slab-use-after-free in string+0x42b/0x470
Read of size 1 at addr ffff88810f56fc90 by task python3/506
CPU: 0 UID: 0 PID: 506 Comm: python3 Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy)
Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
<TASK>
dump_stack_lvl+0x93/0xd0
print_report+0xce/0x630
kasan_report+0xe0/0x110
string+0x42b/0x470
vsnprintf+0x330/0x1110
seq_printf+0x1a8/0x260
sc_seq_show+0x604/0x9f0
seq_read_iter+0x480/0x1110
seq_read+0x362/0x5a0
full_proxy_read+0x11f/0x180
vfs_read+0x1a0/0xc20
ksys_read+0x111/0x200
do_syscall_64+0x114/0x620
entry_SYSCALL_64_after_hwframe+0x77/0x7f
(User register dump omitted.)
</TASK>
Allocated by task 497:
kasan_save_stack+0x33/0x60
kasan_save_track+0x14/0x30
__kasan_kmalloc+0xaa/0xb0
__kmalloc_cache_noprof+0x28d/0x610
o2nm_node_group_make_item+0xea/0x1a0
configfs_mkdir+0x762/0xca0
vfs_mkdir+0x399/0x7e0
filename_mkdirat+0x129/0x450
__x64_sys_mkdir+0x70/0xa0
do_syscall_64+0x114/0x620
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Freed by task 505:
kasan_save_stack+0x33/0x60
kasan_save_track+0x14/0x30
kasan_save_free_info+0x3b/0x60
__kasan_slab_free+0x5f/0x80
kfree+0x308/0x580
config_item_cleanup+0x14b/0x230
config_item_put+0x79/0x90
sc_put+0x454/0x6e0
o2net_send_message_vec+0x63d/0x1560
o2net_send_message+0xa6/0xe0
validation_send_write+0x17f/0x1d0
full_proxy_write+0x11f/0x180
vfs_write+0x25a/0x1010
ksys_write+
---truncated---
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.