In the Linux kernel, the following vulnerability has been resolved:
ocfs2/heartbeat: unlink live slots when their node is missing
o2hb_shutdown_slot() returns immediately when its node is no longer in the
configfs registry. A slot can still be linked in o2hb_live_slots when
that lookup fails. Region teardown or startup-error cleanup then frees
the slot array without removing its embedded list member.
With the same peer live in another region, the next list update can follow
a predecessor into the freed array. Reusing the node number can also make
a later insertion encounter that stale member.
Always remove the slot under o2hb_live_lock, even when node lookup fails.
Preserve aggregate membership accounting and the last-region DOWN
callback: the existing callback interface explicitly permits a NULL node
for DOWN events. Only drop the node reference when lookup returned one.
This closes both normal release and startup-abort paths without changing
the publication or callback locking protocol.
Also require a configured node before admitting a new live slot in
o2hb_check_slot(). The early live-bitmap check is not held through
admission: the last live slot in another region can be removed in between.
Without a node, admission can then queue an UP event with a NULL argument
and hit the event helper's BUG_ON. Existing live slots can still leave
and generate NULL-node DOWN events.
A controlled probe-instrumented test reproduced this while stopping one of
two regions after removing the peer from configfs. Its KASAN report
includes:
BUG: KASAN: slab-use-after-free in __list_del_entry_valid_or_report+0x1e0/0x210
Read of size 8 at addr ffff888106a4ac60 by task o2hb-pmbd0058_b/497
Call Trace:
<TASK>
dump_stack_lvl+0x93/0xd0
print_report+0xce/0x630
kasan_report+0xe0/0x110
__list_del_entry_valid_or_report+0x1e0/0x210
o2hb_do_disk_heartbeat+0x1591/0x2c50
o2hb_thread+0x1ed/0xe70
kthread+0x351/0x460
ret_from_fork+0x659/0x940
ret_from_fork_asm+0x1a/0x30
</TASK>
Allocated by task 491:
kasan_save_stack+0x33/0x60
kasan_save_track+0x14/0x30
__kasan_kmalloc+0xaa/0xb0
__kmalloc_noprof+0x2de/0x780
o2hb_region_dev_store+0x7c2/0x1b60
configfs_write_iter+0x2f9/0x4f0
vfs_write+0x639/0x1010
ksys_write+0x111/0x200
do_syscall_64+0x114/0x620
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Freed by task 491:
kasan_save_stack+0x33/0x60
kasan_save_track+0x14/0x30
kasan_save_free_info+0x3b/0x60
__kasan_slab_free+0x5f/0x80
kfree+0x308/0x580
o2hb_unmap_slot_data+0x1db/0x330
o2hb_region_release+0x14b/0x4f0
config_item_cleanup+0x14b/0x230
config_item_put+0x79/0x90
configfs_rmdir+0x58a/0x910
vfs_rmdir+0x2e8/0x820
filename_rmdir+0x3b1/0x520
__x64_sys_rmdir+0x4b/0x70
do_syscall_64+0x114/0x620
entry_SYSCALL_64_after_hwframe+0x77/0x7f
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.