In the Linux kernel, the following vulnerability has been resolved:
mptcp: hold MP_JOIN msk ref when cloning reqsk
TCP request migration clones pending request sockets with
inet_reqsk_clone(). For MPTCP MP_JOIN requests this byte-copies
subflow_req->msk, but the clone does not own a reference.
The original and cloned requests can consequently drop the same msk
reference, leaving one request with a dangling pointer. This manifests as
a KASAN slab-use-after-free in subflow_req_destructor():
BUG: KASAN: slab-use-after-free in subflow_req_destructor (net/mptcp/subflow.c:45)
Write of size 4 at addr ff1100010e008d40 by task swapper/0/0
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc5-00353-gc27e36054537 #10 PREEMPT(full)
Call Trace:
subflow_req_destructor (net/mptcp/subflow.c:45)
subflow_v4_req_destructor (net/mptcp/subflow.c:694)
__reqsk_free (net/ipv4/inet_connection_sock.c:906)
reqsk_timer_handler (include/net/request_sock.h:137 net/ipv4/inet_connection_sock.c:1147)
Allocated by task 10014:
sk_prot_alloc (net/core/sock.c:2246)
sk_clone (net/core/sock.c:2488)
mptcp_sk_clone_init (include/net/sock.h:1848 net/mptcp/protocol.c:3564)
subflow_syn_recv_sock (net/mptcp/subflow.c:883)
tcp_check_req (net/ipv4/tcp_minisocks.c:934)
Freed by task 0:
slab_free_after_rcu_debug (include/linux/kasan.h:235 mm/slub.c:2677 mm/slub.c:6439)
rcu_core (kernel/rcu/tree.c:2645 kernel/rcu/tree.c:2897)
Last potentially related work creation:
kmem_cache_free (mm/slub.c:2638 mm/slub.c:6377 mm/slub.c:6504)
__sk_destruct (net/core/sock.c:2289 net/core/sock.c:2391)
sk_destruct (net/core/sock.c:2419)
__sk_free (net/core/sock.c:2430)
sk_free (net/core/sock.c:2441)
mptcp_close (include/net/sock.h:2020 net/mptcp/protocol.c:3399)
inet_release (net/ipv4/af_inet.c:442)
The buggy address belongs to the cache MPTCP of size 2968
The buggy address is 128 bytes inside a freed 2968-byte region
A non-NULL subflow_req->msk means that the request owns one reference. The
third ACK can concurrently transfer the original request reference to the
child and release it, so taking an unconditional hold on the copied pointer
is unsafe.
MPTCP sockets use SLAB_TYPESAFE_BY_RCU and all current inet_reqsk_clone()
callers run in an RCU read-side critical section. Document and
lockdep-check that calling-context requirement. Read the pointer from the
original request and acquire a reference only if it is still live. Use
refcount_inc_not_zero_acquire() so the subsequent ownership validation
cannot be reordered before the try-get, then re-read the original request
to verify that it still owns the same msk. If either check fails, clear the
clone pointer; otherwise its normal destructor balances the new reference.
Mark the ownership-transfer store with WRITE_ONCE() to match the lockless
reads.
The following patch completes the clone fixup for MP_CAPABLE token
ownership. Both patches carry the same Fixes tag and are required for
stable backports.
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.